The OUT message was not received within: 20000 millis

[mantonec]

Hello,

i have built a complex application based on SY 0.7 that consists of several SY applications (let me call it "module").

Each module communicates with the others via JMS.

So each module receive a JMS message, perform some elaboration (with access on DB), and at the end publish a message for next module.

Each module contains a BPM component and a camel component.

Camel component uses a CustomCamel component to log messages via Asynchronous EJB into a dedicated JMS queue (centalized asynchronous logging famework)

Camel component is also used to publish the JMS message to a switchyard reference endpoint.

All works fine if i send one single message per time, or if i don't stress the application.

Once i stress the application with a huge amount of requests, i'm facing with the following error (see atached log).

On 200 messages sometimes happens that approximately 10 messages falls in error.

Moreover i have noticed that in module chain (moduleA --> JMS --> moduleB --> JMS --> moduleC), the last module starts to elaborate the first message only after that the previous modules finish to elaborate it's own last message.

Instead, since communication is JMS, i'm expecting that each module starts to work in parallel (with different messages of course).

I'm using the following configuration for each JMS service

<jms:concurrentConsumers>30</jms:concurrentConsumers>
<jms:maxConcurrentConsumers>40</jms:maxConcurrentConsumers>
<jms:disableReplyTo>true</jms:disableReplyTo>

Please, could someone give me some indication on how to identify the source of the problem ?

[kcbabo]

It's very difficult to say without seeing your application.  Can you provide a stripped down example which reproduces the issue?  You might want to consider bumping up to version 1.0.0.Final as 0.7 is a bit old now.

[mantonec]

Yes I know that it is very difficult, but from Exception is not clear the reason and the point where the error occurs.

So it becomes quite impossible to create a mock in order to reproduce the error.

I'm investigating further and i'll keep you informed if i discover something else.

In mean time please let me know if you have some suggestion on how to circumscribe the error.

I have also activated the Message Trace but without success.

Thaks a lot.