JMSTransport consumer consumes responses AND requests
-----------------------------------------------------
Key: XFIRE-865
URL: http://jira.codehaus.org/browse/XFIRE-865
Project: XFire
Issue Type: Bug
Components: JMS
Affects Versions: 1.2.4
Environment: WebLogic 9.2, JDK 1.5.0_09, Windows 2000 Server, Jetty,
Maven
Reporter: Sam Wilson
Assigned To: Dan Diephouse
If you create a simple Echo service project and fire it up using jetty:run on
two separate ports (so that there are two separate server instances) and then
fire up a client application and submit a request the request will be consumed
by one of the server instances and the response will be consumed by the other
and not the client.
Server Node 1 will log the following:
Received message
onMessage -> Source ID: 22B195AD-0581-4C96-7C83-638FB03BBEDE, Message ID: ID:<30
2719.1170776532757.0>
296735 [ExecuteThread: '3' for queue: 'default'] INFO com.ecount.service.echo.E
choServiceImpl - Received message: asdfasdf
296750 [ExecuteThread: '3' for queue: 'default'] INFO org.codehaus.xfire.transp
ort.jms.JMSChannel - Sent message: Source ID: 3FF43FFE-75A9-853A-D994-8579851EF
373 Destination: null JMSType: Echo
Server Node 2 will log the following:
Received message
onMessage -> Source ID: 3FF43FFE-75A9-853A-D994-8579851EF373, Message ID: ID:<30
2719.1170776532819.0>
294906 [ExecuteThread: '1' for queue: 'default'] INFO org.codehaus.xfire.handle
r.DefaultFaultHandler - Fault occurred!
org.codehaus.xfire.fault.XFireFault: Invalid operation: {http://ecount.com/Echo}
echoResponse
and the client will return Null
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
