[jboss-user] [JBoss Messaging] - MDBs using RemoteJMSProvider seem to stop under large number of MDBs

[Mike Miller]

Mike Miller [http://community.jboss.org/people/mikemil] created the discussion

"MDBs using RemoteJMSProvider seem to stop under large number of MDBs"

To view the discussion, visit: http://community.jboss.org/message/546247#546247

--------------------------------------------------------------
Hi,

We are in the process of migrating  from JBoss MQ over to JBoss Messaging, running on 4.2.3 GA.   We are  using the jboss-remoting.jar from 2.2.3.  A little background, we have a  Central server and many Store servers.   We create transactions on the  Store servers, which then save to our database and then put the  transaction data on a local store queue.   On our Central server, we  have a set of MDBs using a Remote JMS Provider definition to actually  pull the transaction data out of the queue (mdb) and save it to our  Central server.    We have about 400 stores running and our Central  server.   For the most part, we are using the base configuration from  the JBoss documentation, with the exception that we are in a firewall  configuration so in the remoting configuration, we are setting the  secondaryBindPort and secondaryControlPort values to the same value,  27900 - based on some previous forum responses from Ron Sigal in the Remoting forums.

Our Central server deploys 400 MDBs, one pointed at each store server to pull transaction data from the Store servers.   Once the Central server gets started successfully we intermittently encounter problems where transaction stops being delivered to our MDBs running on Central.   This problem does not happen with lower numbers of Store servers, like 200.

We have noticed thru using JConsole that for each MDB pointing at a store, we are getting 4-5 threads created for each store: 
1) Connection Consumer for dest JBossQueue(mdb name here)
2) control:Socket[addr=store1/ipaddr of store1, port=27900, localport=xyz...]   --> appears only when store connected
3) control:Socket[addr=store1/ipaddr of store1, port=27900, localport=abc...]   --> appears only when store connected
4) WorkerThread#[idaddr of store1] --> this gets started the first time transaction data arrives from Store 1 and does not appear to go away
5) The MDB actually runs in a thread "JMS SessionPool Worker-z"

Is there some limitation on the number of remote MDBs that messaging can handle reliably?    Exact same code, config etc works with smaller numbers of MDBs.   With 400 MDBs it looks like just those could generate upto 2000 threads, assuming all stores are connected to our Central server.  Does this pose any problems for Messaging?



--------------------------------------------------------------

Reply to this message by going to Community
[http://community.jboss.org/message/546247#546247]

Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2042]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-user/attachments/20100604/98d4462b/attachment.html