[
https://issues.apache.org/jira/browse/AXIS2-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Daniels reopened AXIS2-2819:
---------------------------------
We don't know this is "fixed"
> Faulty handling of JMS asynchronous calls
> -----------------------------------------
>
> Key: AXIS2-2819
> URL: https://issues.apache.org/jira/browse/AXIS2-2819
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: Addressing
> Affects Versions: 1.2
> Environment: Windows XP / Active MQ 4.1.1 / Tomcat 5.5.17
> Reporter: Mathieu Chauvin
> Assignee: Asankha C. Perera
>
> When a JMS client gets its response from the reply queue, addressing module
> fails with the following Exception:
> Exception in thread "JMSWorker-1" java.lang.UnsupportedOperationException
> at java.util.AbstractList.add(AbstractList.java:151)
> at java.util.AbstractList.add(AbstractList.java:89)
> at org.apache.axis2.client.Options.addRelatesTo(Options.java:835)
> at
> org.apache.axis2.handlers.addressing.AddressingInHandler.extractRelatesToInformation(AddressingInHandler.java:248)
> at
> org.apache.axis2.handlers.addressing.AddressingInHandler.extractAddressingInformation(AddressingInHandler.java:169)
> at
> org.apache.axis2.handlers.addressing.AddressingInHandler.invoke(AddressingInHandler.java:95)
> at org.apache.axis2.engine.Phase.invoke(Phase.java:383)
> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:203)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:131)
> at
> org.apache.axis2.transport.jms.JMSMessageReceiver$Worker.run(JMSMessageReceiver.java:249)
> 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(Thread.java:595)
> It seems that the wsa:RelatesTo header (that is, by the way, already set in
> the relationships field of the Options class...) is beeing inserted in a List
> that cannot be modified.
> The Exception is raised from within the JMS listener thread, and can
> therefore not be caught nor handled in another Thread, which is, actually,
> another problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
