Axis2 replyDestination

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Axis2 replyDestination

Anil Kotla
Hello,

We have an in-out operation which was working perfectly in 1.6.0. The response we built was not being sent anywhere as we did not specify a replyDestination.

I have upgraded to 1.7.1 from 1.6.0 and the upgrade is causing an unknown error message from JMS Receiver. The only way it works is adding a transport.jms.ReplyDestination because JMS Sender is expecting outtransportinfo which is eventually returning a nullpointer. This is supposed to be optional as mentioned in the documentation. If I add replyDestination my response is being sent to the queue specified in replyDestination. I can convert the operation into in-only but I want the flexibility to not send the reply to any queue and be able to use the operation both synchronously/asynchronusly. Appreciate your help in this regard.

Here is a stack trace to help.

2017-04-07T09:59:18,368 [jms-Worker-2] ERROR [] org.apache.axis2.transport.jms.JMSMessageReceiver - Unknown error processing message
java.lang.NullPointerException
at org.apache.axis2.transport.jms.JMSSender.sendMessage(JMSSender.java:148) ~[axis2-transport-jms-1.7.1.jar:?]
at org.apache.axis2.transport.base.AbstractTransportSender.invoke(AbstractTransportSender.java:119) ~[axis2-transport-base-1.7.1.jar:?]
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:431) ~[axis2-kernel-1.7.1.jar:1.7.1]
at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:43) ~[axis2-kernel-1.7.1.jar:1.7.1]
at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:106) ~[axis2-kernel-1.7.1.jar:1.7.1]
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:169) ~[axis2-kernel-1.7.1.jar:1.7.1]
at org.apache.axis2.transport.base.AbstractTransportListener.handleIncomingMessage(AbstractTransportListener.java:328) ~[axis2-transport-base-1.7.1.jar:?]
at org.apache.axis2.transport.jms.JMSMessageReceiver.processThoughEngine(JMSMessageReceiver.java:200) ~[axis2-transport-jms-1.7.1.jar:?]
at org.apache.axis2.transport.jms.JMSMessageReceiver.onMessage(JMSMessageReceiver.java:122) [axis2-transport-jms-1.7.1.jar:?]
at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.handleMessage(ServiceTaskManager.java:533) [axis2-transport-jms-1.7.1.jar:?]
at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:436) [axis2-transport-jms-1.7.1.jar:?]
at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:173) [axis2-transport-base-1.7.1.jar:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_121]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_121]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_121]
2017-04-07T09:59:18,471 [jms-Worker-2] DEBUG [] org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask - Session for message : ID:414d51205441583336202020202020208ba7e558ee736e21 rolled back


Thanks
Anil