You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@synapse.apache.org by Ian Carman <ij...@googlemail.com> on 2007/08/17 17:43:08 UTC
Problem specifying a fixed JMS queue as a reply destination
I'm trying to adapt sample 111 so that it uses a known JMS queue to return
the response rather than creating a temporary queue.
If I add a parameter to the end of the proxy definition as follows:
<parameter name="transport.jms.ReplyDestination">
StockQuoteResponse
</parameter>
It doesn't appear to have an affect on the JMS message sent.
I've also tried to achieve the same thing using a property mediator without
success.
I'd appreciate anyone being able to point out what I'm doing wrong or with
an example that might shed some light.
Thanks.
Ian.
Re: Problem specifying a fixed JMS queue as a reply destination
Posted by "Asankha C. Perera" <as...@wso2.com>.
Hi Ian
Great... will keep you posted
asankha
Ian Carman wrote:
> On 8/23/07, Ian Carman <ij...@googlemail.com> wrote:
>
>> If I understand correctly, Synapse will return the original message id in
>> the correlation id of the header. Let me know if I've got this wrong.
>>
>
>
> Asankha,
>
> Using a simple client and the JMS proxy I've verified that the way the
> correlation id is working as required. I look forward to testing the release
> that contains the reply-to destination fix when that becomes available.
>
> Thanks.
>
> Ian.
>
> Many thanks.
>
>> Ian.
>>
>> On 8/23/07, Asankha C. Perera <as...@wso2.com> wrote:
>>
>>> Hi Ian
>>>
>>>> I'm happy to wait now that I know it'll come along in the 1.0.1release. So
>>>> that I can manage expectations is there a timeframe when this is
>>>>
>>> likely to
>>>
>>>> appear?
>>>>
>>>>
>>> We have had to make quite a few changes already ( i.e. changing the
>>> Axis2
>>> dependency to version 1.3 from 1.2, support WAR deployment, JMS and
>>> VFS/File transport enhancements, etc) Thus we may decide to make it a
>>> 1.1 release probably targeted to end of October - to ensure a good round
>>>
>>> of testing as well. We will be releasing release candidates earlier and
>>> you could give us feedback to make sure the release would address your
>>> concerns correctly. Will this work for you?
>>>
>>>> One other question that's related. If a reply destination is
>>>>
>>> specified, is
>>>
>>>> the correlation id something that needs to be set or is this managed
>>>>
>>> by the
>>>
>>>> endpoint?
>>>>
>>>>
>>> Do you want to provide a custom correlation ID to the request message?
>>> If you want this could be done.. but usually this will not be a problem
>>> as the JMS service implementation would use whatever message ID of the
>>> incoming message as the correlation ID for the response message that it
>>> will write to the reply destination.
>>>
>>> asankha
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: synapse-user-help@ws.apache.org
>>>
>>>
>>>
>
>
Re: Problem specifying a fixed JMS queue as a reply destination
Posted by Ian Carman <ij...@googlemail.com>.
On 8/23/07, Ian Carman <ij...@googlemail.com> wrote:
>
>
> If I understand correctly, Synapse will return the original message id in
> the correlation id of the header. Let me know if I've got this wrong.
Asankha,
Using a simple client and the JMS proxy I've verified that the way the
correlation id is working as required. I look forward to testing the release
that contains the reply-to destination fix when that becomes available.
Thanks.
Ian.
Many thanks.
>
> Ian.
>
> On 8/23/07, Asankha C. Perera <as...@wso2.com> wrote:
> >
> > Hi Ian
> > > I'm happy to wait now that I know it'll come along in the 1.0.1release. So
> > > that I can manage expectations is there a timeframe when this is
> > likely to
> > > appear?
> > >
> > We have had to make quite a few changes already ( i.e. changing the
> > Axis2
> > dependency to version 1.3 from 1.2, support WAR deployment, JMS and
> > VFS/File transport enhancements, etc) Thus we may decide to make it a
> > 1.1 release probably targeted to end of October - to ensure a good round
> >
> > of testing as well. We will be releasing release candidates earlier and
> > you could give us feedback to make sure the release would address your
> > concerns correctly. Will this work for you?
> > > One other question that's related. If a reply destination is
> > specified, is
> > > the correlation id something that needs to be set or is this managed
> > by the
> > > endpoint?
> > >
> > Do you want to provide a custom correlation ID to the request message?
> > If you want this could be done.. but usually this will not be a problem
> > as the JMS service implementation would use whatever message ID of the
> > incoming message as the correlation ID for the response message that it
> > will write to the reply destination.
> >
> > asankha
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: synapse-user-help@ws.apache.org
> >
> >
>
Re: Problem specifying a fixed JMS queue as a reply destination
Posted by Ian Carman <ij...@googlemail.com>.
Asankha,
I think an October timeframe for a release fits within the constraints of
the project that we're working on. I'd be happy to test an earlier release
to verify that it addresses the issue we have at the moment.
In our scenario, an upstream application will be placing messages on a JMS
queue that will be relayed through a Synapse proxy using a HTTP transport to
a downstream web service. What I need to ensure is that the correlation id
in the JMS header of the response returned by Synapse contains a value that
can be used by the upstream application to match it to the original message
and that the response is placed back on the queue in the reply-to property.
If I understand correctly, Synapse will return the original message id in
the correlation id of the header. Let me know if I've got this wrong.
Many thanks.
Ian.
On 8/23/07, Asankha C. Perera <as...@wso2.com> wrote:
>
> Hi Ian
> > I'm happy to wait now that I know it'll come along in the 1.0.1 release.
> So
> > that I can manage expectations is there a timeframe when this is likely
> to
> > appear?
> >
> We have had to make quite a few changes already (i.e. changing the Axis2
> dependency to version 1.3 from 1.2, support WAR deployment, JMS and
> VFS/File transport enhancements, etc) Thus we may decide to make it a
> 1.1 release probably targeted to end of October - to ensure a good round
> of testing as well. We will be releasing release candidates earlier and
> you could give us feedback to make sure the release would address your
> concerns correctly. Will this work for you?
> > One other question that's related. If a reply destination is specified,
> is
> > the correlation id something that needs to be set or is this managed by
> the
> > endpoint?
> >
> Do you want to provide a custom correlation ID to the request message?
> If you want this could be done.. but usually this will not be a problem
> as the JMS service implementation would use whatever message ID of the
> incoming message as the correlation ID for the response message that it
> will write to the reply destination.
>
> asankha
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-user-help@ws.apache.org
>
>
Re: Problem specifying a fixed JMS queue as a reply destination
Posted by "Asankha C. Perera" <as...@wso2.com>.
Hi Ian
> I'm happy to wait now that I know it'll come along in the 1.0.1 release. So
> that I can manage expectations is there a timeframe when this is likely to
> appear?
>
We have had to make quite a few changes already (i.e. changing the Axis2
dependency to version 1.3 from 1.2, support WAR deployment, JMS and
VFS/File transport enhancements, etc) Thus we may decide to make it a
1.1 release probably targeted to end of October - to ensure a good round
of testing as well. We will be releasing release candidates earlier and
you could give us feedback to make sure the release would address your
concerns correctly. Will this work for you?
> One other question that's related. If a reply destination is specified, is
> the correlation id something that needs to be set or is this managed by the
> endpoint?
>
Do you want to provide a custom correlation ID to the request message?
If you want this could be done.. but usually this will not be a problem
as the JMS service implementation would use whatever message ID of the
incoming message as the correlation ID for the response message that it
will write to the reply destination.
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-user-help@ws.apache.org
Re: Problem specifying a fixed JMS queue as a reply destination
Posted by Ian Carman <ij...@googlemail.com>.
Asankha,
Thanks for the quick response.
I'm happy to wait now that I know it'll come along in the 1.0.1 release. So
that I can manage expectations is there a timeframe when this is likely to
appear?
One other question that's related. If a reply destination is specified, is
the correlation id something that needs to be set or is this managed by the
endpoint?
Ian.
On 8/17/07, Asankha C. Perera <as...@wso2.com> wrote:
>
> Hi Ian
>
> For your case, you should use the property mediator to set the reply
> destination name. However the 1.0 release had a bug where this property
> did not propagate to the endpoint when being sent. This bug is already
> fixed and will go into 1.0.1 as well as being already available in a
> fresh build off the source code. Let me know if you would like a binary
> of the relevant JAR file.
>
> asankha
>
> Ian Carman wrote:
> > I'm trying to adapt sample 111 so that it uses a known JMS queue to
> return
> > the response rather than creating a temporary queue.
> >
> > If I add a parameter to the end of the proxy definition as follows:
> >
> > <parameter name="transport.jms.ReplyDestination">
> > StockQuoteResponse
> > </parameter>
> >
> > It doesn't appear to have an affect on the JMS message sent.
> >
> > I've also tried to achieve the same thing using a property mediator
> without
> > success.
> >
> > I'd appreciate anyone being able to point out what I'm doing wrong or
> with
> > an example that might shed some light.
> >
> > Thanks.
> >
> > Ian.
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-user-help@ws.apache.org
>
>
Re: Problem specifying a fixed JMS queue as a reply destination
Posted by "Asankha C. Perera" <as...@wso2.com>.
Hi Ian
For your case, you should use the property mediator to set the reply
destination name. However the 1.0 release had a bug where this property
did not propagate to the endpoint when being sent. This bug is already
fixed and will go into 1.0.1 as well as being already available in a
fresh build off the source code. Let me know if you would like a binary
of the relevant JAR file.
asankha
Ian Carman wrote:
> I'm trying to adapt sample 111 so that it uses a known JMS queue to return
> the response rather than creating a temporary queue.
>
> If I add a parameter to the end of the proxy definition as follows:
>
> <parameter name="transport.jms.ReplyDestination">
> StockQuoteResponse
> </parameter>
>
> It doesn't appear to have an affect on the JMS message sent.
>
> I've also tried to achieve the same thing using a property mediator without
> success.
>
> I'd appreciate anyone being able to point out what I'm doing wrong or with
> an example that might shed some light.
>
> Thanks.
>
> Ian.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-user-help@ws.apache.org