Found the problem. I needed to increase the max-pool-size significantly (to
100 for now) to get past that bottleneck. I'll have to play with that number
until I find the optimal setup for my app.
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=395241
Here's a code snippet:
InitialContext iniCtx = new InitialContext();
|
| Object tmp = iniCtx.lookup("java:/JmsXA");
| QueueConnectionFactory qcf = (QueueConnectionFactory) tmp;
| QueueConnection jmsConn = qcf.createQueueConnection();
|
| jmsConn.start();
|
| Session sess = jmsCo
Yes, I'm using the JmsXA to create a connection on each request.
Any idea what the createQueueSession method might be waiting on?
Is there a connection pool setting that I should play with? I tried changing
the max-pool-size on the JmsXA resource but it didn't seem to have any effect.
Also, no
Interesting. Are you using the JCA adapter, i.e. "java:/JmsXA"? You should use
this to obtain a new JMS connection each time.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952178#3952178
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=post
