Issues encountered while using Synapse as web app

[Pradeepta Bhattacharya <Pr...@aexp.com>]

Hello,

We are using Synapse (Synapse 2.1.0) for one of our big initiative and are using capabilities such as proxy service, mediators such as Iterate / aggregate mediators.
As we run in a restricted data center we have packaged Synapse as a war in our application ear and deployed in Websphere Application Server 6.1 . When we start the ear, synapse can be accessed through the default servlet channel or directly through synapse port (8280). What we have noticed is that there is a difference in behaviour between these two channels.

1) If I define a proxy which doesn't use mediators such as iterate or aggregator, the servlet channel works fine. The client ( in this case SoapUI) can send a request and recieve response.
2) In a scenario where we need to use split and aggregate EIP the server returns back a "HTTP/1.1 202 Accepted " to the client and the client terminates. The execution of various sequences continues even after the server returns back the initial response.
3) We also noticed that using the servlet transport we face issues with the aggregate as its not able to corelate messages printing out the following info in our logs -> Unable to find aggrgation correlation XPath or property

Note : These sequences and mediators are working perfectly if we use the Proxy Reciever channel i.e Synapse port 8280.

Could you please let us know how can we ensure that there is consistency in behaviour.

The scenarios that we have mentioned are easy to recreate, but if you need the sequence definations that we have defined please do let us know.

As we are contemplating on using synapse for a critical requirement, any help in resolving these issues is highly appreciated.

Thanks

Kind Regards
PB
< "java.net.BindException: Address already in use" withe WSO2 ESB v3.0.1 and JBoss 5.1.0-EAP<http://wso2.org/forum/thread/11929> DBReport Mediator Parameters Issue ><http://wso2.org/forum/thread/11962>


American Express made the following annotations on Wed Jun 01 2011 23:35:02 

****************************************************************************** 

"This message and any attachments are solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any disclosure, copying, use, or distribution of the information included in this message and any attachments is prohibited. If you have received this communication in error, please notify us by reply e-mail and immediately and permanently delete this message and any attachments. Thank you." 

American Express a ajout� le commentaire suivant le Wed Jun 01 2011 23:35:02 

Ce courrier et toute pi�ce jointe qu'il contient sont r�serv�s au seul destinataire indiqu� et peuvent renfermer des renseignements confidentiels et privil�gi�s. Si vous n'�tes pas le destinataire pr�vu, toute divulgation, duplication, utilisation ou distribution du courrier ou de toute pi�ce jointe est interdite. Si vous avez re�u cette communication par erreur, veuillez nous en aviser par courrier et d�truire imm�diatement le courrier et les pi�ces jointes. Merci. 

****************************************************************************** 
-------------------------------------------------------------------------------

Re: Issues encountered while using Synapse as web app

[Ruwan Linton <ru...@gmail.com>]

Hi Pradeepta,

Good to hear you are using Synapse.

Regarding the problem that you have encountered, the split aggregate pattern
is an asynchronous pattern, as you may already know, and to be frank it has
not been tested with the servlet transport. The NHTTP transport (port 8280
by default) is an asynchronous transport which fits well to this split
aggregate scenario. I suspect that the creation of new message contexts at
split of the incoming message causes the actual incoming message to be
returned and dropped which causes this problem. Do you have the
"continueParent" attribute in the iterate mediator configuration? if so what
is the value of it?

The behaviour that you have seen of the split-aggregate pattern, on the
servlet transport is sort of a known issue with certain configurations. May
I know why you want to expose both servlet transport and the nhttp transport
to receive messages? Considering the performance implications and the
functionality testing coverage of Synapse it is highly recommended that you
use the Nhttp transport in production.

If there is no specific reason to have both transports I suggest closing off
the servlet transport in the deployment, if at all possible??

May be if you can post a fragment of your configuration which causes this, I
should be able to inspect it and see whether it can be rectified.

Thanks,
Ruwan

On Thu, Jun 2, 2011 at 12:34 PM, Pradeepta Bhattacharya <
Pradeepta.Bhattacharya@aexp.com> wrote:

> Hello,
>
> We are using Synapse (Synapse 2.1.0) for one of our big initiative and are
> using capabilities such as proxy service, mediators such as Iterate /
> aggregate mediators.
> As we run in a restricted data center we have packaged Synapse as a war in
> our application ear and deployed in Websphere Application Server 6.1 . When
> we start the ear, synapse can be accessed through the default servlet
> channel or directly through synapse port (8280). What we have noticed is
> that there is a difference in behaviour between these two channels.
>
> 1) If I define a proxy which doesn't use mediators such as iterate or
> aggregator, the servlet channel works fine. The client ( in this case
> SoapUI) can send a request and recieve response.
> 2) In a scenario where we need to use split and aggregate EIP the server
> returns back a "HTTP/1.1 202 Accepted " to the client and the client
> terminates. The execution of various sequences continues even after the
> server returns back the initial response.
> 3) We also noticed that using the servlet transport we face issues with the
> aggregate as its not able to corelate messages printing out the following
> info in our logs -> Unable to find aggrgation correlation XPath or property
>
> Note : These sequences and mediators are working perfectly if we use the
> Proxy Reciever channel i.e Synapse port 8280.
>
> Could you please let us know how can we ensure that there is consistency in
> behaviour.
>
> The scenarios that we have mentioned are easy to recreate, but if you need
> the sequence definations that we have defined please do let us know.
>
> As we are contemplating on using synapse for a critical requirement, any
> help in resolving these issues is highly appreciated.
>
> Thanks
>
> Kind Regards
> PB
> < "java.net.BindException: Address already in use" withe WSO2 ESB v3.0.1
> and JBoss 5.1.0-EAP<http://wso2.org/forum/thread/11929> DBReport Mediator
> Parameters Issue ><http://wso2.org/forum/thread/11962>
>
>
> American Express made the following annotations on Wed Jun 01 2011 23:35:02
>
>
> ******************************************************************************
>
> "This message and any attachments are solely for the intended recipient and
> may contain confidential or privileged information. If you are not the
> intended recipient, any disclosure, copying, use, or distribution of the
> information included in this message and any attachments is prohibited. If
> you have received this communication in error, please notify us by reply
> e-mail and immediately and permanently delete this message and any
> attachments. Thank you."
>
> American Express a ajouté le commentaire suivant le Wed Jun 01 2011
> 23:35:02
>
> Ce courrier et toute pièce jointe qu'il contient sont réservés au seul
> destinataire indiqué et peuvent renfermer des renseignements confidentiels
> et privilégiés. Si vous n'êtes pas le destinataire prévu, toute divulgation,
> duplication, utilisation ou distribution du courrier ou de toute pièce
> jointe est interdite. Si vous avez reçu cette communication par erreur,
> veuillez nous en aviser par courrier et détruire immédiatement le courrier
> et les pièces jointes. Merci.
>
>
> ******************************************************************************
>
> -------------------------------------------------------------------------------
>
>


-- 
Ruwan Linton
Member, Apache Software Foundation; http://www.apache.org
<http://wso2.org>

phone: +94 11 282 7532
email: ruwan@blindvision.org; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
google: http://www.google.com/profiles/ruwan.linton
tweet: http://twitter.com/ruwanlinton