
|
If you were logged in you would be able to see more operations.
|
|
|
|
I'm running JMS messages from ActiveMQ (standalone, not VM) to Flex using Gravity.
When my application server loses the connection to ActiveMQ it automatically reconnects after a short time and continues to receive messages. However when this happens the Flex clients also lose their connection but never reconnect. The Flex app needs to be restarted to regain the connection.
Flex should reconnect automatically or otherwise nicely handle.
One way to reproduce:
Run ActiveMQ on localhost (or wherever)
Create a grails project
Install GDSFlex
Create Flex project and configure gravity with JMS to connect to ActiveMQ
Send messages to the relevant Topic. They will be handled by Flex.
Break the connection to ActiveMQ eg. by restarting ActiveMQ
Send messages to the relevant Topic. They will not be handled by Flex.
Reload Flex application
Send messages to the relevant Topic. They will be handled by Flex.
|
|
Description
|
I'm running JMS messages from ActiveMQ (standalone, not VM) to Flex using Gravity.
When my application server loses the connection to ActiveMQ it automatically reconnects after a short time and continues to receive messages. However when this happens the Flex clients also lose their connection but never reconnect. The Flex app needs to be restarted to regain the connection.
Flex should reconnect automatically or otherwise nicely handle.
One way to reproduce:
Run ActiveMQ on localhost (or wherever)
Create a grails project
Install GDSFlex
Create Flex project and configure gravity with JMS to connect to ActiveMQ
Send messages to the relevant Topic. They will be handled by Flex.
Break the connection to ActiveMQ eg. by restarting ActiveMQ
Send messages to the relevant Topic. They will not be handled by Flex.
Reload Flex application
Send messages to the relevant Topic. They will be handled by Flex. |
Show » |
Sort Order:
|
It looks like the same case than server failover when clustering ActiveMQ instances.