6:29 a.m.
Messages are returned to client from the wrong service
------------------------------------------------------
Key: JBESB-1774
URL: http://jira.jboss.com/jira/browse/JBESB-1774
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Process flow
Affects Versions: 4.2.1 CP1
Environment: Windows Server 2003
Reporter: Mika Leino
Attachments: service_A_jboss-esb.xml, service_B_jboss-esb.xml
We have a setup in which a client calls an ESB service (service A) with a webservice
interface and this service then calls on another ESB service (service B). Both of the
services have their action pipelines set to be "RequestResponse".
For some reason the first attempt to handle the client's message always fails as the
message is returned to the client from service B. As the message never returns to service
A it assumes an unresponsive EPR and resends the message which on the second attempt
returns to service A.
The first attempt looks like this:
client -> service A -> service B -> client
And the second like this:
(client ->) service A -> service B -> service A -> client
Unfortunately the client interpreters the first response as the one it is waiting for and
fails as service A has not made the necessary changes to the message. The second attempt
produces a valid response but the client is no longer listening for it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:29 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1774) Messages are returned to client from the wrong service
[ http://jira.jboss.com/jira/browse/JBESB-1774?page=all ]
Mika Leino updated JBESB-1774:
------------------------------
Attachment: service_A_jboss-esb.xml
Added the configuration of service A.
Messages are returned to client from the wrong service
------------------------------------------------------
Key: JBESB-1774
URL: http://jira.jboss.com/jira/browse/JBESB-1774
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.2.1 CP1
Environment: Windows Server 2003
Reporter: Mika Leino
Attachments: service_A_jboss-esb.xml, service_B_jboss-esb.xml
We have a setup in which a client calls an ESB service (service A) with a webservice
interface and this service then calls on another ESB service (service B). Both of the
services have their action pipelines set to be "RequestResponse".
For some reason the first attempt to handle the client's message always fails as the
message is returned to the client from service B. As the message never returns to service
A it assumes an unresponsive EPR and resends the message which on the second attempt
returns to service A.
The first attempt looks like this:
client -> service A -> service B -> client
And the second like this:
(client ->) service A -> service B -> service A -> client
Unfortunately the client interpreters the first response as the one it is waiting for and
fails as service A has not made the necessary changes to the message. The second attempt
produces a valid response but the client is no longer listening for it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:29 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1774) Messages are returned to client from the wrong service
[ http://jira.jboss.com/jira/browse/JBESB-1774?page=all ]
Mika Leino updated JBESB-1774:
------------------------------
Attachment: service_B_jboss-esb.xml
Added the configuration of service B.
Messages are returned to client from the wrong service
------------------------------------------------------
Key: JBESB-1774
URL: http://jira.jboss.com/jira/browse/JBESB-1774
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.2.1 CP1
Environment: Windows Server 2003
Reporter: Mika Leino
Attachments: service_A_jboss-esb.xml, service_B_jboss-esb.xml
We have a setup in which a client calls an ESB service (service A) with a webservice
interface and this service then calls on another ESB service (service B). Both of the
services have their action pipelines set to be "RequestResponse".
For some reason the first attempt to handle the client's message always fails as the
message is returned to the client from service B. As the message never returns to service
A it assumes an unresponsive EPR and resends the message which on the second attempt
returns to service A.
The first attempt looks like this:
client -> service A -> service B -> client
And the second like this:
(client ->) service A -> service B -> service A -> client
Unfortunately the client interpreters the first response as the one it is waiting for and
fails as service A has not made the necessary changes to the message. The second attempt
produces a valid response but the client is no longer listening for it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:35 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1774) Messages are returned to client from the wrong service
[ http://jira.jboss.com/jira/browse/JBESB-1774?page=all ]
Mika Leino updated JBESB-1774:
------------------------------
Component/s: Rosetta
(was: Process flow)
Messages are returned to client from the wrong service
------------------------------------------------------
Key: JBESB-1774
URL: http://jira.jboss.com/jira/browse/JBESB-1774
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1 CP1
Environment: Windows Server 2003
Reporter: Mika Leino
Attachments: service_A_jboss-esb.xml, service_B_jboss-esb.xml
We have a setup in which a client calls an ESB service (service A) with a webservice
interface and this service then calls on another ESB service (service B). Both of the
services have their action pipelines set to be "RequestResponse".
For some reason the first attempt to handle the client's message always fails as the
message is returned to the client from service B. As the message never returns to service
A it assumes an unresponsive EPR and resends the message which on the second attempt
returns to service A.
The first attempt looks like this:
client -> service A -> service B -> client
And the second like this:
(client ->) service A -> service B -> service A -> client
Unfortunately the client interpreters the first response as the one it is waiting for and
fails as service A has not made the necessary changes to the message. The second attempt
produces a valid response but the client is no longer listening for it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:55 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1774) Messages are returned to client from the wrong service
[ http://jira.jboss.com/jira/browse/JBESB-1774?page=comments#action_12414542 ]
Tom Fennelly commented on JBESB-1774:
-------------------------------------
By any chance, is Service A forwarding the messages it's receiving from the Client on
to Service B (with original addressing info - from, replyTo etc). If so, what you're
seeing makes sense. Try putting something into the pipeline that will ensure the messages
being routed to Service B are new message.
Messages are returned to client from the wrong service
------------------------------------------------------
Key: JBESB-1774
URL: http://jira.jboss.com/jira/browse/JBESB-1774
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1 CP1
Environment: Windows Server 2003
Reporter: Mika Leino
Attachments: service_A_jboss-esb.xml, service_B_jboss-esb.xml
We have a setup in which a client calls an ESB service (service A) with a webservice
interface and this service then calls on another ESB service (service B). Both of the
services have their action pipelines set to be "RequestResponse".
For some reason the first attempt to handle the client's message always fails as the
message is returned to the client from service B. As the message never returns to service
A it assumes an unresponsive EPR and resends the message which on the second attempt
returns to service A.
The first attempt looks like this:
client -> service A -> service B -> client
And the second like this:
(client ->) service A -> service B -> service A -> client
Unfortunately the client interpreters the first response as the one it is waiting for and
fails as service A has not made the necessary changes to the message. The second attempt
produces a valid response but the client is no longer listening for it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:17 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1774) Messages are returned to client from the wrong service
[ http://jira.jboss.com/jira/browse/JBESB-1774?page=comments#action_12414549 ]
Kevin Conner commented on JBESB-1774:
-------------------------------------
Can you also add your log file and an example showing the problem (or your configured esb
services)?
Messages are returned to client from the wrong service
------------------------------------------------------
Key: JBESB-1774
URL: http://jira.jboss.com/jira/browse/JBESB-1774
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1 CP1
Environment: Windows Server 2003
Reporter: Mika Leino
Attachments: service_A_jboss-esb.xml, service_B_jboss-esb.xml
We have a setup in which a client calls an ESB service (service A) with a webservice
interface and this service then calls on another ESB service (service B). Both of the
services have their action pipelines set to be "RequestResponse".
For some reason the first attempt to handle the client's message always fails as the
message is returned to the client from service B. As the message never returns to service
A it assumes an unresponsive EPR and resends the message which on the second attempt
returns to service A.
The first attempt looks like this:
client -> service A -> service B -> client
And the second like this:
(client ->) service A -> service B -> service A -> client
Unfortunately the client interpreters the first response as the one it is waiting for and
fails as service A has not made the necessary changes to the message. The second attempt
produces a valid response but the client is no longer listening for it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:24 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1774) Messages are returned to client from the wrong service
[ http://jira.jboss.com/jira/browse/JBESB-1774?page=all ]
Mika Leino updated JBESB-1774:
------------------------------
Attachment: service_A_jboss-esb.xml
Messages are returned to client from the wrong service
------------------------------------------------------
Key: JBESB-1774
URL: http://jira.jboss.com/jira/browse/JBESB-1774
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1 CP1
Environment: Windows Server 2003
Reporter: Mika Leino
Attachments: service_A_jboss-esb.xml, service_A_jboss-esb.xml,
service_B_jboss-esb.xml
We have a setup in which a client calls an ESB service (service A) with a webservice
interface and this service then calls on another ESB service (service B). Both of the
services have their action pipelines set to be "RequestResponse".
For some reason the first attempt to handle the client's message always fails as the
message is returned to the client from service B. As the message never returns to service
A it assumes an unresponsive EPR and resends the message which on the second attempt
returns to service A.
The first attempt looks like this:
client -> service A -> service B -> client
And the second like this:
(client ->) service A -> service B -> service A -> client
Unfortunately the client interpreters the first response as the one it is waiting for and
fails as service A has not made the necessary changes to the message. The second attempt
produces a valid response but the client is no longer listening for it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:26 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1774) Messages are returned to client from the wrong service
[ http://jira.jboss.com/jira/browse/JBESB-1774?page=all ]
Mika Leino updated JBESB-1774:
------------------------------
Attachment: service_B_jboss-esb.xml
Messages are returned to client from the wrong service
------------------------------------------------------
Key: JBESB-1774
URL: http://jira.jboss.com/jira/browse/JBESB-1774
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1 CP1
Environment: Windows Server 2003
Reporter: Mika Leino
Attachments: service_A_jboss-esb.xml, service_A_jboss-esb.xml,
service_B_jboss-esb.xml, service_B_jboss-esb.xml
We have a setup in which a client calls an ESB service (service A) with a webservice
interface and this service then calls on another ESB service (service B). Both of the
services have their action pipelines set to be "RequestResponse".
For some reason the first attempt to handle the client's message always fails as the
message is returned to the client from service B. As the message never returns to service
A it assumes an unresponsive EPR and resends the message which on the second attempt
returns to service A.
The first attempt looks like this:
client -> service A -> service B -> client
And the second like this:
(client ->) service A -> service B -> service A -> client
Unfortunately the client interpreters the first response as the one it is waiting for and
fails as service A has not made the necessary changes to the message. The second attempt
produces a valid response but the client is no longer listening for it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:40 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1774) Messages are returned to client from the wrong service
[ http://jira.jboss.com/jira/browse/JBESB-1774?page=all ]
Mika Leino updated JBESB-1774:
------------------------------
Attachment: services_log.txt
Messages are returned to client from the wrong service
------------------------------------------------------
Key: JBESB-1774
URL: http://jira.jboss.com/jira/browse/JBESB-1774
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1 CP1
Environment: Windows Server 2003
Reporter: Mika Leino
Attachments: service_A_jboss-esb.xml, service_A_jboss-esb.xml,
service_B_jboss-esb.xml, service_B_jboss-esb.xml, services_log.txt
We have a setup in which a client calls an ESB service (service A) with a webservice
interface and this service then calls on another ESB service (service B). Both of the
services have their action pipelines set to be "RequestResponse".
For some reason the first attempt to handle the client's message always fails as the
message is returned to the client from service B. As the message never returns to service
A it assumes an unresponsive EPR and resends the message which on the second attempt
returns to service A.
The first attempt looks like this:
client -> service A -> service B -> client
And the second like this:
(client ->) service A -> service B -> service A -> client
Unfortunately the client interpreters the first response as the one it is waiting for and
fails as service A has not made the necessary changes to the message. The second attempt
produces a valid response but the client is no longer listening for it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:57 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1774) Messages are returned to client from the wrong service
[ http://jira.jboss.com/jira/browse/JBESB-1774?page=comments#action_12414749 ]
Mika Leino commented on JBESB-1774:
-----------------------------------
I uploaded a log file and new service configurations to illustrate the problem. And yes,
the message going to service B is the same message that service A has received as our
understanding of the documentation has been that the message is returned to the client
invoking that service, in this case service A.
In our setup service A should do some additional work on the message before returning it
to the client and process all errors received from service B. The documentation states
that in "RequestResponse" action pipelines the message is returned to the client
after the last action and also that when invoking other services a service is acting as a
client to the service invoked. Thus it would seem logical that when service A invokes
service B with ServiceInvoker.deliverSync the message would be returned to service A
instead of the actual client.
Even if the behaviour of returning the message from service B to the client would be by
design this raises another issue in that the message is not routed identically when
retrying delivery. This might cause some unwanted results and is very misleading.
Messages are returned to client from the wrong service
------------------------------------------------------
Key: JBESB-1774
URL: http://jira.jboss.com/jira/browse/JBESB-1774
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1 CP1
Environment: Windows Server 2003
Reporter: Mika Leino
Attachments: service_A_jboss-esb.xml, service_A_jboss-esb.xml,
service_B_jboss-esb.xml, service_B_jboss-esb.xml, services_log.txt
We have a setup in which a client calls an ESB service (service A) with a webservice
interface and this service then calls on another ESB service (service B). Both of the
services have their action pipelines set to be "RequestResponse".
For some reason the first attempt to handle the client's message always fails as the
message is returned to the client from service B. As the message never returns to service
A it assumes an unresponsive EPR and resends the message which on the second attempt
returns to service A.
The first attempt looks like this:
client -> service A -> service B -> client
And the second like this:
(client ->) service A -> service B -> service A -> client
Unfortunately the client interpreters the first response as the one it is waiting for and
fails as service A has not made the necessary changes to the message. The second attempt
produces a valid response but the client is no longer listening for it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:59 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1774) Messages are returned to client from the wrong service
[
https://jira.jboss.org/jira/browse/JBESB-1774?page=com.atlassian.jira.plu...
]
Mark Little updated JBESB-1774:
-------------------------------
Fix Version/s: 4.6
Messages are returned to client from the wrong service
------------------------------------------------------
Key: JBESB-1774
URL: https://jira.jboss.org/jira/browse/JBESB-1774
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1 CP1
Environment: Windows Server 2003
Reporter: Mika Leino
Fix For: 4.6
Attachments: service_A_jboss-esb.xml, service_A_jboss-esb.xml,
service_B_jboss-esb.xml, service_B_jboss-esb.xml, services_log.txt
We have a setup in which a client calls an ESB service (service A) with a webservice
interface and this service then calls on another ESB service (service B). Both of the
services have their action pipelines set to be "RequestResponse".
For some reason the first attempt to handle the client's message always fails as the
message is returned to the client from service B. As the message never returns to service
A it assumes an unresponsive EPR and resends the message which on the second attempt
returns to service A.
The first attempt looks like this:
client -> service A -> service B -> client
And the second like this:
(client ->) service A -> service B -> service A -> client
Unfortunately the client interpreters the first response as the one it is waiting for and
fails as service A has not made the necessary changes to the message. The second attempt
produces a valid response but the client is no longer listening for it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:31 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-1774) Messages are returned to client from the wrong service
[
https://jira.jboss.org/jira/browse/JBESB-1774?page=com.atlassian.jira.plu...
]
Kevin Conner closed JBESB-1774.
-------------------------------
Resolution: Rejected
Service A has forwarded the same message to Service B, preserving the reply to EPR. It
should have reset the ReplyTo to null or created a new message.
The consequence of this action is that there are now two clients waiting for a response at
the same EPR, only one of which can receive it. In this instance it was the JBR gateway.
Messages are returned to client from the wrong service
------------------------------------------------------
Key: JBESB-1774
URL: https://jira.jboss.org/jira/browse/JBESB-1774
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1 CP1
Environment: Windows Server 2003
Reporter: Mika Leino
Fix For: 4.6
Attachments: service_A_jboss-esb.xml, service_A_jboss-esb.xml,
service_B_jboss-esb.xml, service_B_jboss-esb.xml, services_log.txt
We have a setup in which a client calls an ESB service (service A) with a webservice
interface and this service then calls on another ESB service (service B). Both of the
services have their action pipelines set to be "RequestResponse".
For some reason the first attempt to handle the client's message always fails as the
message is returned to the client from service B. As the message never returns to service
A it assumes an unresponsive EPR and resends the message which on the second attempt
returns to service A.
The first attempt looks like this:
client -> service A -> service B -> client
And the second like this:
(client ->) service A -> service B -> service A -> client
Unfortunately the client interpreters the first response as the one it is waiting for and
fails as service A has not made the necessary changes to the message. The second attempt
produces a valid response but the client is no longer listening for it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5669
days inactive
6027
days old
11 comments
4 participants
participants (4)
-
Kevin Conner (JIRA) -
Mark Little (JIRA)
-
Mika Leino (JIRA)
-
Tom Fennelly (JIRA)