axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anil Kotla (JIRA)" <>
Subject [jira] [Created] (AXIS2-5844) AXIS2 1.7.1 is forcing a replyDestination or else throwing Unknown error processing message
Date Fri, 07 Apr 2017 14:01:41 GMT
Anil Kotla created AXIS2-5844:

             Summary: AXIS2 1.7.1 is forcing a replyDestination or else throwing Unknown error
processing message
                 Key: AXIS2-5844
             Project: Axis2
          Issue Type: Bug
          Components: JMS transport
    Affects Versions: 1.7.1
            Reporter: Anil Kotla
            Priority: Blocker

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 Sender. The only way it works is adding a transport.jms.ReplyDestination. If I do that
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. 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
        at org.apache.axis2.transport.jms.JMSSender.sendMessage( ~[axis2-transport-jms-1.7.1.jar:?]
        at org.apache.axis2.transport.base.AbstractTransportSender.invoke(
        at org.apache.axis2.engine.AxisEngine.send( ~[axis2-kernel-1.7.1.jar:1.7.1]
        at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(
        at org.apache.axis2.receivers.AbstractMessageReceiver.receive(
        at org.apache.axis2.engine.AxisEngine.receive( ~[axis2-kernel-1.7.1.jar:1.7.1]
        at org.apache.axis2.transport.base.AbstractTransportListener.handleIncomingMessage(
        at org.apache.axis2.transport.jms.JMSMessageReceiver.processThoughEngine(
        at org.apache.axis2.transport.jms.JMSMessageReceiver.onMessage(
        at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.handleMessage(
        at org.apache.axis2.transport.jms.ServiceTaskManager$
        at org.apache.axis2.transport.base.threads.NativeWorkerPool$
        at java.util.concurrent.ThreadPoolExecutor.runWorker(
        at java.util.concurrent.ThreadPoolExecutor$
        at [?: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

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message