File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Spring and the fly likes Spring - BlazeDS Problem Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Frameworks » Spring
Bookmark "Spring - BlazeDS Problem" Watch "Spring - BlazeDS Problem" New topic
Author

Spring - BlazeDS Problem

Jennie Andrade
Greenhorn

Joined: May 09, 2008
Posts: 2
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 BlazeDS or the Message Broker that makes this retry possible?
Notice there is an interval of 5 mins.

We make use of SecureAMFChannel for connections.
 
wood burning stoves
 
subject: Spring - BlazeDS Problem
 
Similar Threads
org.springframework.transaction.jta.WebLogicJtaTransactionManager Spring - WebLogic 11g - Webservice
Flex - Blaze DS Service retry
startNodeManager.sh and startWeblogic.sh doesn't start to execute
webservice - spring -jws
weblogic admin server down