[esb-issues] [JBoss JIRA] Commented: (JBESB-880) The ESB is blocked under heavy load when using JMS

Mon Sep 17 02:56:11 EDT 2007

    [ http://jira.jboss.com/jira/browse/JBESB-880?page=comments#action_12377073 ] 

Jiri Pechanec commented on JBESB-880:
-------------------------------------

I have tried to test different conditions - pregenerated backlog of messages and start of the applications and I have run into the same issues. Moreover the client code opens only one JMS session that uses for send ing messages in the batch. I do not expect the JBM would internally open and close TCP connection per message instead of per session.

> The ESB is blocked under heavy load when using JMS
> --------------------------------------------------
>
>                 Key: JBESB-880
>                 URL: http://jira.jboss.com/jira/browse/JBESB-880
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Rosetta, Transports
>    Affects Versions: 4.2 Milestone Release 3
>         Environment: RHEL 5, PostgreSQL
>            Reporter: Jiri Pechanec
>         Assigned To: Kevin Conner
>            Priority: Blocker
>             Fix For: 4.2.1 IR1
>
>
> When the ESB is forced to process a huge batch of messages then it blocks completely.
> The ESB configuration was just one service with one listener and gateway. Both gateway and listener are using JMS. The testing was executed twice using one and then four threads per listener and gateway.
> The service contains two actions that serves only for message counting.
> If you try to send 10000 messages sized around 20 KB it will probaly block after few minutes of processing. The ESB do not respond to TERM signal and even JMX console is not available. The only solution is to kill process violently. With the smaller messages the block does not happend or happends after bigger amount of messages.
> The sender is generating following log messages
> [Timer-1][BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 201d592a: detected failure on control connection Thread[control: Socket[addr=/10.34.34.47,port=2660,localport=51957],5,main]: requesting new control connection
> We can not exclude problem in JBoss Messaging itself but when we tried to use plain JMS without ESB we were able to send/receive 300000 messages without any problem.
> Moreover the more messages were processed the longer time it takes for the next batch to be processed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira