You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Gerald Loeffler (JIRA)" <ji...@apache.org> on 2007/03/14 22:21:09 UTC
[jira] Created: (SYNAPSE-68) JMSSender for one-way messages expects
reply
JMSSender for one-way messages expects reply
--------------------------------------------
Key: SYNAPSE-68
URL: https://issues.apache.org/jira/browse/SYNAPSE-68
Project: Synapse
Issue Type: Bug
Components: Core
Affects Versions: 0.91
Reporter: Gerald Loeffler
My set-up is really simple:
-----------------------
<proxy name="proxy" transports="http">
<target endpoint="jms_endpoint" />
<wsdl key="wsdl_with_one_way_op" />
</proxy>
-----------------------
The only special thing is that the operation defined in the WSDL and
invoked by the client is one-way (an in-only MEP).
I experience that a one-way message (to an in-only MEP) that is sent
to a JMS destination via JMSSender causes JMSSender to wait for a
response message on a reply
queue. Of course this does not make sense, and indeed the blocking JMS
receive of that reply message ultimately times out with this error:
-----------------------
DEBUG [13 Mar 20:33:13] JMSSender - JMSSender invoke()
DEBUG [13 Mar 20:33:13] JMSSender - [Client]Sending message to
destination : TOPIC.T_INT_CLIENT_EVT
DEBUG [13 Mar 20:33:13] JMSSender - Waiting for a maximum of 30000ms
for a response message to destination : QUEUE.JMS_TQ3
WARN [13 Mar 20:33:43] JMSSender - Did not receive a JMS response
within 30000 ms to destination : TOPIC.T_INT_CLIENT_EVT
-----------------------
Very briefly looking at the code for
org.apache.axis2.transport.jms.JMSSender in the trunk it indeed seems
that JMSSender sets the flag "waitForResponse" to true regardless of
whether the messages is one-way (to an in-only MEP) or not.
Asankha replied:
------------------------------
The problem here is that you do not define to Synapse which operation to
invoke with the WSDL, or if its IN only or IN-OUT. I guess we could
specify this within the endpoint definition, or maybe even set the
replyTo header to none to indicate that the message is not expecting a
reply?
------------------------------
Paul replied:
------------------------------
As a post 1.0 we need to be able to read the WSDL definition and use
that. In the meantime, I suggest we add an explicit marker to endpoint
to indicate not to expect a response.
I don't go for the none approach.... it seems counter-intuitive to me.
That seems to be telling the target what to do, not Synapse.
------------------------------
--
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: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
[jira] Resolved: (SYNAPSE-68) JMSSender for one-way messages
expects reply
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SYNAPSE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Asankha C. Perera resolved SYNAPSE-68.
--------------------------------------
Resolution: Invalid
Assignee: Asankha C. Perera
Caused by https://issues.apache.org/jira/browse/AXIS2-2434 and fixed on Axis2
> JMSSender for one-way messages expects reply
> --------------------------------------------
>
> Key: SYNAPSE-68
> URL: https://issues.apache.org/jira/browse/SYNAPSE-68
> Project: Synapse
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.91
> Reporter: Gerald Loeffler
> Assigned To: Asankha C. Perera
>
> My set-up is really simple:
> -----------------------
> <proxy name="proxy" transports="http">
> <target endpoint="jms_endpoint" />
> <wsdl key="wsdl_with_one_way_op" />
> </proxy>
> -----------------------
> The only special thing is that the operation defined in the WSDL and
> invoked by the client is one-way (an in-only MEP).
> I experience that a one-way message (to an in-only MEP) that is sent
> to a JMS destination via JMSSender causes JMSSender to wait for a
> response message on a reply
> queue. Of course this does not make sense, and indeed the blocking JMS
> receive of that reply message ultimately times out with this error:
> -----------------------
> DEBUG [13 Mar 20:33:13] JMSSender - JMSSender invoke()
> DEBUG [13 Mar 20:33:13] JMSSender - [Client]Sending message to
> destination : TOPIC.T_INT_CLIENT_EVT
> DEBUG [13 Mar 20:33:13] JMSSender - Waiting for a maximum of 30000ms
> for a response message to destination : QUEUE.JMS_TQ3
> WARN [13 Mar 20:33:43] JMSSender - Did not receive a JMS response
> within 30000 ms to destination : TOPIC.T_INT_CLIENT_EVT
> -----------------------
> Very briefly looking at the code for
> org.apache.axis2.transport.jms.JMSSender in the trunk it indeed seems
> that JMSSender sets the flag "waitForResponse" to true regardless of
> whether the messages is one-way (to an in-only MEP) or not.
> Asankha replied:
> ------------------------------
> The problem here is that you do not define to Synapse which operation to
> invoke with the WSDL, or if its IN only or IN-OUT. I guess we could
> specify this within the endpoint definition, or maybe even set the
> replyTo header to none to indicate that the message is not expecting a
> reply?
> ------------------------------
> Paul replied:
> ------------------------------
> As a post 1.0 we need to be able to read the WSDL definition and use
> that. In the meantime, I suggest we add an explicit marker to endpoint
> to indicate not to expect a response.
> I don't go for the none approach.... it seems counter-intuitive to me.
> That seems to be telling the target what to do, not Synapse.
> ------------------------------
--
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: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org