Hi Isuru, With the fix added in [1] <https://github.com/wso2/wso2-axis2/pull/127/files#diff-e879bcfb53b9f28f45a2232b1fc8b95fR214>, there are test errors as the JMSSender waits for the response even for in-out message exchange pattern until the timeout. Apparently from the axis2-transport side, if we want to wait for the response (eg: out-in MEP), we set the reply destination [2] <https://github.com/wso2/wso2-axis2-transports/blob/master/modules/jms/src/main/java/org/apache/axis2/transport/jms/JMSSender.java#L268> defining where we need to expect the response from. And, if waiting is needed, it waits [3] <https://github.com/wso2/wso2-axis2-transports/blob/master/modules/jms/src/main/java/org/apache/axis2/transport/jms/JMSSender.java#L349> until the message is received from that destination until the timeout.
In the case of a in-out (request-response) MEP, even though we do not actually expect a response, with the added fix we are waiting until a response received. Hence, JMS tests are failing when we upgrade the latest axis2 version for wso2-axis2-transport. Could you please verify whether the waiting for a response is needed for *in-out* MEP scenarios? Thanks, Prabushi [1] - https://github.com/wso2/wso2-axis2/pull/127/files#diff-e879bcfb53b9f28f45a2232b1fc8b95fR214 [2] - https://github.com/wso2/wso2-axis2-transports/blob/master/modules/jms/src/main/java/org/apache/axis2/transport/jms/JMSSender.java#L268 [3] - https://github.com/wso2/wso2-axis2-transports/blob/master/modules/jms/src/main/java/org/apache/axis2/transport/jms/JMSSender.java#L349 On Tue, Mar 13, 2018 at 12:15 PM, Chanika Geeganage <chan...@wso2.com> wrote: > Yes, due to this issue, we had to go with 1.6.1-wso2v23 and kernel is > released with 1.6.1-wso2v23 > > On Tue, Mar 13, 2018 at 12:08 PM, Chamalee De Silva <chama...@wso2.com> > wrote: > >> Hi Chanika, >> Does it mean that the a downgrade to 1.6.1-wso2v23 or going for a newer >> version ? >> >> >> >> >> >> On Wed, Mar 7, 2018 at 5:24 PM, Chanika Geeganage <chan...@wso2.com> >> wrote: >> >>> Hi, >>> >>> I tried to upgrade the axis2 version (1.6.1-wso2v24) in >>> wso2-axis2-transport repo. I'm getting the following test failures in the >>> JMS transport test cases. >>> >>> org.apache.axis2.AxisFault: Did not receive a JMS response within 30000 >>> ms to destination : direct://amq.direct/TempQueue3 >>> 347121a-c9c8-44dc-b1c6-1df603d7d02c/tmp_8af87fef-ddef-4eb9-9 >>> 655-945482ad6941?exclusive='true'&autodelete='true' with JMS >>> correlation ID : ID:94912946-a240-4c95-b21b-f886c0aa9437 >>> at org.apache.axis2.transport.base.AbstractTransportSender.hand >>> leException(AbstractTransportSender.java:234) >>> at org.apache.axis2.transport.jms.JMSSender.waitForResponseAndP >>> rocess(JMSSender.java:415) >>> at org.apache.axis2.transport.jms.JMSSender.sendOverJMS(JMSSend >>> er.java:349) >>> at org.apache.axis2.transport.jms.JMSSender.sendMessage(JMSSend >>> er.java:205) >>> at org.apache.axis2.transport.base.AbstractTransportSender.invo >>> ke(AbstractTransportSender.java:119) >>> at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:525) >>> at org.apache.axis2.transport.base.AbstractTransportListener.ha >>> ndleIncomingMessage(AbstractTransportListener.java:336) >>> at org.apache.axis2.transport.jms.JMSMessageReceiver.processTho >>> ughEngine(JMSMessageReceiver.java:214) >>> at org.apache.axis2.transport.jms.JMSMessageReceiver.onMessage( >>> JMSMessageReceiver.java:124) >>> at org.apache.axis2.transport.jms.ServiceTaskManager$MessageLis >>> tenerTask.handleMessage(ServiceTaskManager.java:645) >>> at org.apache.axis2.transport.jms.ServiceTaskManager$MessageLis >>> tenerTask.run(ServiceTaskManager.java:526) >>> at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.r >>> un(NativeWorkerPool.java:172) >>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool >>> Executor.java:1142) >>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo >>> lExecutor.java:617) >>> at java.lang.Thread.run(Thread.java:745) >>> >>> Only the following PRs were merged after 1.6.1-wso2v23 release in axis2. >>> If I reverted the fix [1] and tests were passed. >>> >>> [1] https://github.com/wso2/wso2-axis2/pull/127/files >>> [2] https://github.com/wso2/wso2-axis2/pull/132/files >>> >>> -- >>> Best Regards.. >>> >>> Chanika Geeganage >>> +94773522586 <+94%2077%20352%202586> >>> WSO2, Inc.; http://wso2.com >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Thanks & Regards, >> >> *Chamalee De Silva* >> Senior Software Engineer >> *WS**O2* Inc. :http://wso2.com/ >> >> Office :- *+94 11 2145345 <%2B94%2011%202145345>* >> mobile :- *+94 7 <%2B94%2077%202782039>1 4315942* >> >> > > > -- > Best Regards.. > > Chanika Geeganage > +94773522586 <+94%2077%20352%202586> > WSO2, Inc.; http://wso2.com > > > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Prabushi Samarakoon* Software Engineer Mobile: +94715434580 Email: prabus...@wso2.com
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
