That is inside a filter-condition, there are different kind of messages that
are flowing thru synapse, in the case when the type is 1, that is where the
issue is.
For all other types of message is expected to be done, in the "else" section of
the filter. However when the type of is 1. Then only the application on target
endpoint is expected response.
So this config:
<filter source="get-property('com.jeppesen.jsi.message.Type')" regex="1">
<then>
<class name="com.jeppesen.jsi.synapse.ContentBasedRouter"/>
<drop/>
</then>
<else>
<class name="com.jeppesen.jsi.synapse.MonitorLogger">
<property name="TextLine" value="SyncAsync-Filter --
The message is asynchronous it will be delivered asynchronously.in other words;
if the message is synchronous it will NEVER be delivered."/>
<property name="QueueKey" value="JetPlan"/>
<property name="Recipient" value="JetPlan"/>
</class>
<property name="RESPONSE" value="true"/>
<header name="To" action="remove"/>
<class name="com.jeppesen.jsi.synapse.Responder">
<property name="ResponseCode" value="200"/>
</class>
<out>
<send/>
</out>
</else>
</filter>
Please advise.
Thanks,
Abid
-----Original Message-----
From: Sadeep Jayasumana [mailto:[email protected]]
Sent: Tuesday, July 12, 2011 12:22 AM
To: [email protected]
Subject: Re: Help needed
Hi Abid,
I see the following configuration in JetPlan-JSI-EntrySequence.
<property name="RESPONSE" value="true"/>
<header name="To" action="remove"/>
<class name="com.jeppesen.jsi.synapse.Responder">
<property name="ResponseCode" value="200"/>
</class>
<out>
<send/>
</out>
Could you explain the reason for setting the "RESPONSE" property to true
here? This property marks the message as a response message and sends back
to the synapse client. Is this the expected behavior?
Thanks,
Sadeep
On Mon, Jul 11, 2011 at 10:20 PM, Abid Khan-EXT <[email protected]>wrote:
> Sorry for got to attach.
>
>
>
>
> -----Original Message-----
> From: Abid Khan-EXT [mailto:[email protected]]
> Sent: Monday, July 11, 2011 10:38 AM
> To: [email protected]
> Subject: RE: Help needed
>
>
> The proxy config is like :
>
> <proxy name="JetPlan" transports="http">
> <target inSequence="JetPlan-JSI-EntrySequence"
> outSequence="JetPlanOutSeq"/>
> </proxy>
>
> I have attached the full synapse configuration too, just in case you need
> anything else.
>
> Thanks for helping,
> Abid
>
> -----Original Message-----
> From: Hiranya Jayathilaka [mailto:[email protected]]
> Sent: Monday, July 11, 2011 3:20 AM
> To: [email protected]
> Subject: Re: Help needed
>
> Any chance of taking a look at the full proxy config?
>
> Thanks,
> Hiranya
>
> On Sat, Jul 9, 2011 at 8:59 AM, Abid Khan-EXT <[email protected]
> >wrote:
>
> > Hello all,
> >
> > I am using Synapse 1.2.
> >
> > I just have run into a problem;
> >
> > I have a proxy that has target with "inSequense" and "outSequence",
> > "inSequence" also has a onErrorSequence.
> >
> > The <send..> mediator is the last mediator in the "inSequence".
> >
> > The problem is as soon as the message is sent, empty response is written
> to
> > the client, and when the endpoint returns the actual response, it cannot
> be
> > written and exception is logged "response is already committed..."
> >
> > My understanding was that outSequence would be initiated, and the client
> is
> > put on hold until after the response is received by synapse?
> >
> > Please help,
> >
> > Thanks,
> > Abid
> >
> >
> >
>
>
> --
> Hiranya Jayathilaka
> Senior Software Engineer;
> WSO2 Inc.; http://wso2.org
> E-mail: [email protected]; Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>
--
Sadeep
