axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Asankha C. Perera (JIRA)" <>
Subject [jira] Commented: (AXIS2-2819) Faulty handling of JMS asynchronous calls
Date Wed, 04 Jul 2007 12:25:04 GMT


Asankha C. Perera commented on AXIS2-2819:


I do not think this is a blocker, so I would like the priority of this reduced. Also you do
not state how this could be reproduced. Is it when the client is expecting a synchronous response
- but through a custom defined queue or topic instead of a temporary queue?


> Faulty handling of JMS asynchronous calls
> -----------------------------------------
>                 Key: AXIS2-2819
>                 URL:
>             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
>            Priority: Blocker
>             Fix For: 1.3
> 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(
> 	at java.util.AbstractList.add(
> 	at org.apache.axis2.client.Options.addRelatesTo(
> 	at org.apache.axis2.handlers.addressing.AddressingInHandler.extractRelatesToInformation(
> 	at org.apache.axis2.handlers.addressing.AddressingInHandler.extractAddressingInformation(
> 	at org.apache.axis2.handlers.addressing.AddressingInHandler.invoke(
> 	at org.apache.axis2.engine.Phase.invoke(
> 	at org.apache.axis2.engine.AxisEngine.invoke(
> 	at org.apache.axis2.engine.AxisEngine.receive(
> 	at org.apache.axis2.transport.jms.JMSMessageReceiver$
> 	at$Worker.runTask(
> 	at$
> 	at
> 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.

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

View raw message