Re: [Axis2]: Unable to process response message on JMS queue after client restart

[Asankha C. Perera]

Hi Afroz I need more information on this. Is it possible for you to share your client code? On the server side, I am assuming you are talking to an Axis2 JMS service - or is it something else which reads the JMS request off a queue and places another (new) JMS response back to another queue - using JMS correlation id's in sync? asankha Afroz Ahmed wrote: Hmm… No response. I would have thought that this is a common problem. Apache WSIF (Web Services Invocation Framework) has a concept of CorrelationService that lets you save the operation, possibly in a database  and retrieve it later, thus allowing you to map the request and response. Is there nothing of the same nature in Axis2.   Thanks Afroz   From: Afroz Ahmed [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 21, 2007 11:07 AM To: axis-user@ws.apache.org Subject: [Axis2]: Not able to process response message on JMS queue after client restart   Hi   We have a scenario where the service requester sends a message on a queue and the service processing takes a significant amount of time. The client is not expected to keep running all this time and can be stopped and restarted. When the client comes back up, it picks up the processed message (if any) from the response queue. However what is happening is that WS-Addressing module does not find a corresponding operation context and throws the following exception:   SEVERE: JMS Worker [JMSWorker-1] Encountered an Axis Fault : The [action] cannot be processed at the receiver. org.apache.axis2.AxisFault: The [action] cannot be processed at the receiver.       at org.apache.axis2.addressing.AddressingFaultsHelper.triggerAddressingFault(AddressingFaultsHelper.java:150)       at org.apache.axis2.addressing.AddressingFaultsHelper.triggerActionNotSupportedFault(AddressingFaultsHelper.java:125)       at org.apache.axis2.handlers.addressing.AddressingWSDLValidationHandler.checkAction(AddressingWSDLValidationHandler.java:109)       at org.apache.axis2.handlers.addressing.AddressingWSDLValidationHandler.invoke(AddressingWSDLValidationHandler.java:39)       at org.apache.axis2.engine.Phase.invoke(Phase.java:382)       at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:522)       at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:487)       at org.apache.axis2.transport.jms.JMSMessageReceiver$Worker.run(JMSMessageReceiver.java:198)       at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)       at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)       at java.lang.Thread.run(Unknown Source)     Does anybody have an idea if there is a way to overcome this problem?   Thanks Afroz   --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]