9:12 a.m.
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: Mark Little
Priority: Blocker
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@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
9:14 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=all ]
Mark Little reassigned JBESB-880:
---------------------------------
Assignee: Kevin Conner (was: Mark Little)
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
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@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
9:14 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=all ]
Mark Little updated JBESB-880:
------------------------------
Fix Version/s: 4.2
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
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@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
9:49 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=comments#action_12373638 ]
Jiri Pechanec commented on JBESB-880:
-------------------------------------
New finding - in some cases the ESB recovers itself by waiting for more than half an hour
without requesting any operation. Even the JMX starts working again.
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
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@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
1:56 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=comments#action_12373669 ]
Kevin Conner commented on JBESB-880:
------------------------------------
Hiya Jiri.
Could you please attach your test case to this issue?
Thanks.
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
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@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
7:12 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=comments#action_12373732 ]
Len DiMaggio commented on JBESB-880:
------------------------------------
Note from Jirka on running the tests (he is in the ESB class in the UK next week)
1) Test environment is xen47.englab.brq.redhat.com user soaesb1 pw soaesb1
2) Dwonload file from there ee.tar
3) Unpack it to trunk/qa
4) cd EE/quickstarts/tests
5) ant rebuild-ng
6) Establish local web server that will make access to output/lib
7) Set appropriate property test.performance.urlprefix in target executng - it should be
url that allows access to esb files
8) Start ESB on xen47 using bin/run.sh -c mysql -b 0.0.0.0
9) Run ant -Dtestng.filter=Performance1Test -Dtest.performance.messagecount=1
-Dtest.performance.messagefile=25KB_message.xml executeng
message files are store in ../messages
10) When you finish the test then stop the ESB and clen the database using
mysql soaesb1_as -u soaesb1 --password=soaesb1 < ~/clear_jbm.sql
J.
Additional notes:
Just to conclude - Four tests exist:
1 - simple service testing, one service on real work done
2 - bpm_orchestaration2 converted to static esb configuration
3 - tests only transformarmation
4 - bpm_orchestartion2
Planned are one or two more test regarding web services performance
The test names are used here -Dtestng.filter=Performance1Test
Missing feature righ now - startup and shut down ESB on remote host to control testing,
remotely cleaning database
Probably requires some support Perl script
Note on step #7 above:
<ldimaggi_laptop> > 7) Set appropriate property test.performance.urlprefix in
target executng - it should be url that allows access to esb files
<ldimaggi_laptop> ------> Where is this property defined?
<jpechane> File build.xml, target executng, task testng and there is property
definition
<jpechane> It will be moved later to config file
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
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@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
11:13 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=comments#action_12373770 ]
Mark Little commented on JBESB-880:
-----------------------------------
I wonder if this is related to http://jira.jboss.com/jira/browse/JBESB-855
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
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@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
8:54 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=comments#action_12373816 ]
Kevin Conner commented on JBESB-880:
------------------------------------
Thanks for this Len, I'll go through it this weekend and try to reproduce it locally.
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
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@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
7:46 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=all ]
Kevin Conner updated JBESB-880:
-------------------------------
Fix Version/s: 4.2.1
(was: 4.2)
Haven't had a chance to reproduce this, will look at it as soon as the GA has gone
out.
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
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@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
12:31 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=all ]
Kevin Conner updated JBESB-880:
-------------------------------
Fix Version/s: 4.2.1 IR1
(was: 4.2.1)
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@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
3:50 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=comments#action_12376623 ]
Phillip Thurmond commented on JBESB-880:
----------------------------------------
I believe this issue is caused by the test client creating a large number of connections
to the server in a very small time. This can overload the server at the OS level and will
cause the JBoss instance to hang. I ran the test with a large number of messages
yesterday, and I was unable to reproduce the problem. Most likely, the problem will
return when the client is run on a host with a very fast connection to the server. I will
work with Jiri to reproduce and provide a fix.
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@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
4:02 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=comments#action_12376629 ]
Kevin Conner commented on JBESB-880:
------------------------------------
I have already downloaded Jiri's setup, from the site mentioned by Len, and will be
looking at this shortly.
Please let me know if you find out anything else.
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@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
8:56 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ 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@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
9 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=comments#action_12377074 ]
Jiri Pechanec commented on JBESB-880:
-------------------------------------
Moreover if the problem will be identified as described by Phillip it is then serious
issue with JBM internal implementation.
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@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
10:52 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=comments#action_12377080 ]
Kevin Conner commented on JBESB-880:
------------------------------------
My suspicion is that it is caused by the way in which we are using JBM internally. I will
be looking at this problem later this week.
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@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
11:53 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=comments#action_12377977 ]
Kevin Conner commented on JBESB-880:
------------------------------------
I spent a lot of time looking at this yesterday, reproducing the issue and profiling it.
At this stage it does not appear to be an issue with JBoss Messaging.
I'll make more progress on this later today.
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@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
2:02 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=comments#action_12378306 ]
Kevin Conner commented on JBESB-880:
------------------------------------
The ESB is not blocked but it is under a heavy load.
The majority of the time spent processing the requests appears to be taken up with the XML
serialisation/deserialisation process. Changing the message type to use SERIALIZED
instead of XML makes a dramatic difference in the overall time spent to process the
messages.
I'll have a look at the serialisation and see what can be done.
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@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
2:22 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=comments#action_12378311 ]
Tom Fennelly commented on JBESB-880:
------------------------------------
By any chance, would there still be some of the Message.Body byte[] code left lying around
in use i.e. some of the actions in question still serializing/deserializing the payload to
and from bytes every time as the Message moves along the action chain? This would also be
a killer, but easy to fix now I think.
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@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
2:58 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=comments#action_12378316 ]
Kevin Conner commented on JBESB-880:
------------------------------------
That is certainly one issue, the message does exist twice in the body. It does not appear
to be the major issue though.
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@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
3:49 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=comments#action_12378328 ]
Mark Little commented on JBESB-880:
-----------------------------------
I suspect it's there twice for backward compatibility. If it's been like that for
more than two GA releases, then we could remove one of the copies. Otherwise it'll
have to stay until 4.x, where x > 2.
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@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
10:35 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=all ]
Kevin Conner updated JBESB-880:
-------------------------------
Fix Version/s: 4.2.1 IR2
(was: 4.2.1 IR1)
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 IR2
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@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
2:34 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=all ]
Kevin Conner updated JBESB-880:
-------------------------------
Fix Version/s: 4.2.1
(was: 4.2.1 IR2)
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
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@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
4:59 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=all ]
Kevin Conner updated JBESB-880:
-------------------------------
Fix Version/s: 4.3
(was: 4.2.1)
I'm only part way through this and it will not be finished in time for the GA. It
will be covered by the first CP.
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.3
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@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
10:13 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=all ]
Mark Little updated JBESB-880:
------------------------------
Fix Version/s: 4.2.1 CP1
(was: 4.3)
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 CP1
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@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
12:50 p.m.
New subject: [JBoss JIRA] Work started: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=all ]
Work on JBESB-880 started by Kevin Conner.
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 CP1
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@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
6:02 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=comments#action_12392335 ]
Kevin Conner commented on JBESB-880:
------------------------------------
Message serialisation has now been changed to use StAX instead of DOM.
A simple serialisation/deserialisation test of a 35KB message, outside of the ESB, shows
the following improvements.
Old code
Time taken to serialise 100000 messages: 656s, 6ms/message
Time taken to deserialise 100000 messages: 446s, 4ms/message
Time taken to serialise/deserialise 100000 messages: 1102s, 11ms/message
New code
Time taken to serialise 100000 messages: 210s, 2ms/message
Time taken to deserialise 100000 messages: 73s, 737us/message
Time taken to serialise/deserialise 100000 messages: 282s, 2ms/message
This part has been committed in revision 17275.
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 CP1
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@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
3:32 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=all ]
Martin Vecera updated JBESB-880:
--------------------------------
Attachment: reports-080102.tar.bz2
JProfiler reports after the first fix - 08/01/02
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 CP1
Attachments: reports-080102.tar.bz2
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@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
5:19 p.m.
New subject: [JBoss JIRA] Work stopped: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=all ]
Work on JBESB-880 stopped by Kevin Conner.
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 CP1
Attachments: reports-080102.tar.bz2
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@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
10:43 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=all ]
Kevin Conner updated JBESB-880:
-------------------------------
Fix Version/s: 4.2.1 CP2
(was: 4.2.1 CP1)
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 CP2
Attachments: reports-080102.tar.bz2
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@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
5:33 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=all ]
Kevin Conner updated JBESB-880:
-------------------------------
Fix Version/s: 4.2.1 CP3
(was: 4.2.1 CP2)
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 CP3
Attachments: reports-080102.tar.bz2
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@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
6:57 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-880) The ESB is blocked under heavy load when using JMS
[ http://jira.jboss.com/jira/browse/JBESB-880?page=all ]
Kevin Conner updated JBESB-880:
-------------------------------
Fix Version/s: 4.2.1 CP4
(was: 4.2.1 CP3)
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 CP4
Attachments: reports-080102.tar.bz2
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@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
4:17 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-880) The ESB is blocked under heavy load when using JMS
[
https://jira.jboss.org/jira/browse/JBESB-880?page=com.atlassian.jira.plug...
]
Kevin Conner updated JBESB-880:
-------------------------------
Fix Version/s: 4.2.1 CP5
(was: 4.2.1 CP4)
The ESB is blocked under heavy load when using JMS
--------------------------------------------------
Key: JBESB-880
URL: https://jira.jboss.org/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
Assignee: Kevin Conner
Priority: Blocker
Fix For: 4.2.1 CP5
Attachments: reports-080102.tar.bz2
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@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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:38 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-880) The ESB is blocked under heavy load when using JMS
[
https://jira.jboss.org/jira/browse/JBESB-880?page=com.atlassian.jira.plug...
]
Kevin Conner updated JBESB-880:
-------------------------------
Fix Version/s: 4.2.1 CP6
(was: 4.2.1 CP5)
The ESB is blocked under heavy load when using JMS
--------------------------------------------------
Key: JBESB-880
URL: https://jira.jboss.org/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
Assignee: Kevin Conner
Priority: Blocker
Fix For: 4.2.1 CP6
Attachments: reports-080102.tar.bz2
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@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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:24 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-880) The ESB is blocked under heavy load when using JMS
[
https://jira.jboss.org/browse/JBESB-880?page=com.atlassian.jira.plugin.sy...
]
Jiri Pechanec closed JBESB-880.
-------------------------------
Resolution: Out of Date
The ESB is blocked under heavy load when using JMS
--------------------------------------------------
Key: JBESB-880
URL: https://jira.jboss.org/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
Assignee: Kevin Conner
Priority: Blocker
Fix For: 4.2.1 CP6
Attachments: reports-080102.tar.bz2
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@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:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4972
days inactive
6091
days old
33 comments
7 participants
participants (7)
-
Jiri Pechanec (JIRA) -
Kevin Conner (JIRA)
-
Len DiMaggio (JIRA)
-
Mark Little (JIRA)
-
Martin Vecera (JIRA)
-
Phillip Thurmond (JIRA)
-
Tom Fennelly (JIRA)