Ganesh,
What do you mean by x concurrent threads: Are you using 7 or more
threads for simulating concurrent client load or is it the JBI component
thread pool size you are refering too?
Could you enabled DEBUG logging en check if all the MEPs are handled
correctly (i.e. every exchange ends with a DONE message)? I see you are
using sendSync, so if some MessageExchange never end with DONE/ERROR,
this is going to lock up threads.
Which version of ServiceMix are you using?
Regards,
Gert
navigator09 wrote:
Hi,
I am load testing the following configuration
from("jbi:endpoint:http://foo.bar.org/Pipeline/Endpoint?mep=in-out";).
to("jbi:endpoint:http://www.icenigrid.org/service/gridsam/JobSubmission/JobSubmission?mep=in-out";).
convertBodyTo(DOMSource.class).
to("log:jobsubmissionoutput").
to("jbi:endpoint:http://foo.bar.org/EventProcessor/EventProcessorendpoint";).
The entire flow works well with 7 concurrent threads. But when I try with
more threads , the flow works fine till
jbi:endpoint:http://www.icenigrid.org/service/gridsam/JobSubmission/JobSubmission?mep=in-out
end point. The response from this end point is not forwrded to the event
processor end point and I get the following message
19:02:04,500 | DEBUG | pool-flow.seda.servicemix-camel-thread-3 |
SecuredBroker | mix.jbi.security.SecuredBroker 72 | service
name :{http://foo.bar.org}EventProcessor
19:02:04,500 | DEBUG | pool-flow.seda.servicemix-camel-thread-6 |
DeliveryChannelImpl | .messaging.DeliveryChannelImpl 693 | Waiting for
exchange ID:10.20.3.92-11e881736ec-2:19 (de1520) to be answered in
DeliveryChannel{servicemix-camel} from sendSync
Then after waiting for around 10 minutes the the thread expires ( as
configured in component.properties). Why is the event processor not being
processed properly for 10 and above concorrent threads.
Regards,
Ganesh
