You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by Dalys Sebastian <se...@yahoo.com> on 2009/09/09 15:24:47 UTC

Ode times out when big messages are exchanged

I work with Ode 1.3.2. I am using Ode to orchestrate with other webservices that reside external to the Ode-Axis2 engine. Ode behaves normally when all my exchanges involve messages that are less than 2 MB.

But, when the message returned to me from the external service to Ode is beyong 3.5 MB, Ode times out with the following error printed out into my logs. 

ERROR org.apache.ode.bpel.engine.BpelRuntimeContextImpl  - Invalid response state for mex hqejbhcnphr4ks4dk0cuiu: ASYNC

Could anyone please help on this?

Thanks,
Dalys

Re: Ode times out when big messages are exchanged

Posted by Alexis Midon <mi...@intalio.com>.
Hi Dalys,
could you give us a log file please?

Alexis

On Wed, Sep 9, 2009 at 6:56 AM, Dalys Sebastian
<se...@yahoo.com>wrote:

> Some additional details on this problem:
>
> I have worked with the previous version of Ode and all the tests had
> succeeded. I switched to Ode1.3.2 to take advantage of ws-security and only
> then I started seeing the timeouts with big messages. Please note that this
> timeout occured with NO ws-security configured.
>
> The Ode engine is running on Tomcat 6.0.18. It's NOT in in-memory mode.
> It's configured to use SQLServer as its database.
>
> Thanks,
> Dalys
>
> --- On Wed, 9/9/09, Dalys Sebastian <se...@yahoo.com> wrote:
>
> > From: Dalys Sebastian <se...@yahoo.com>
> > Subject: Ode times out when big messages are exchanged
> > To: user@ode.apache.org
> > Date: Wednesday, September 9, 2009, 8:24 AM
> > I work with Ode 1.3.2. I am using Ode
> > to orchestrate with other webservices that reside external
> > to the Ode-Axis2 engine. Ode behaves normally when all my
> > exchanges involve messages that are less than 2 MB.
> >
> > But, when the message returned to me from the external
> > service to Ode is beyong 3.5 MB, Ode times out with the
> > following error printed out into my logs.
> >
> > ERROR
> > org.apache.ode.bpel.engine.BpelRuntimeContextImpl  -
> > Invalid response state for mex hqejbhcnphr4ks4dk0cuiu:
> > ASYNC
> >
> > Could anyone please help on this?
> >
> > Thanks,
> > Dalys
> >
> >
> >
> >
>
>
>
>

Re: Ode times out when big messages are exchanged

Posted by Dalys Sebastian <se...@yahoo.com>.
Some additional details on this problem: 

I have worked with the previous version of Ode and all the tests had succeeded. I switched to Ode1.3.2 to take advantage of ws-security and only then I started seeing the timeouts with big messages. Please note that this timeout occured with NO ws-security configured.

The Ode engine is running on Tomcat 6.0.18. It's NOT in in-memory mode. It's configured to use SQLServer as its database.

Thanks,
Dalys

--- On Wed, 9/9/09, Dalys Sebastian <se...@yahoo.com> wrote:

> From: Dalys Sebastian <se...@yahoo.com>
> Subject: Ode times out when big messages are exchanged
> To: user@ode.apache.org
> Date: Wednesday, September 9, 2009, 8:24 AM
> I work with Ode 1.3.2. I am using Ode
> to orchestrate with other webservices that reside external
> to the Ode-Axis2 engine. Ode behaves normally when all my
> exchanges involve messages that are less than 2 MB.
> 
> But, when the message returned to me from the external
> service to Ode is beyong 3.5 MB, Ode times out with the
> following error printed out into my logs. 
> 
> ERROR
> org.apache.ode.bpel.engine.BpelRuntimeContextImpl  -
> Invalid response state for mex hqejbhcnphr4ks4dk0cuiu:
> ASYNC
> 
> Could anyone please help on this?
> 
> Thanks,
> Dalys
> 
> 
>       
>