We have a flex application integrated with java-spring using BlazeDS. The application provides the user a JMS interaction screen where the user has to enter parameters like url and queue details and a message will be posted on to that queue.
The problem is that whenever the server layer (java) takes time to respond, somehow another request gets sent to the server.
The log looks like this:
2011-10-11 03:17:19 INFO [[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'] - JanusFilter.processJanusPrincipal -> janusPrincipal====D
2011-10-11 03:17:19 INFO [[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'] - TraceLoggerUtil.logBefore -> Start of JMSClientServiceImpl.sendJMSMessage
2011-10-11 03:17:19 INFO [[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'] - JMSClientServiceImpl.sendJMSMessage -> :: Sending JMS message
2011-10-11 03:22:19 INFO [[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'] - JanusFilter.processJanusPrincipal -> janusPrincipal====D
2011-10-11 03:22:19 INFO [[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'] - TraceLoggerUtil.logBefore -> Start of JMSClientServiceImpl.sendJMSMessage
2011-10-11 03:22:19 INFO [[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'] - JMSClientServiceImpl.sendJMSMessage -> :: Sending JMS message
Is there some sort of property in Flex's Remote Object or BlazeDS that makes this retry possible?
Notice there is an interval of 5 mins.
0
