Hi, We are using JBoss-3.2.3. We have an application deployed, in which we make use of JMS. Our application relies heavily on sending/receiving messages. We use the receive() API of the QueueReceiver which will wait till a message is received. This effectively, means that the Connection in which this receiver is created is not closed till the receive operation is complete. Naturally, we have started seeing the following exceptions:
| javax.jms.JMSException: Could not create a session: javax.resource.ResourceException: No ManagedConnections available within configured blocking timeout ( 5000 [ms] ) After having a look at some topics on this forum, we found that we will have to configure the max-pool-size and the blocking timeout in the jms-ds.xml file. I had a few questions regarding this: 1) How expensive is a JMS connection? Can i configure a very high value in the max-pool-size without running into any problems, say for example 200? And if yes, will the server be capable enough to make available these many JMS connections when the server is up? 2) Since jms-ds.xml is a file that will be used by ALL applications on the server, is there any other place, where the same setting can be done for our specific application, without affecting other applications? Thank you. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3919735#3919735 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3919735 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
