[
http://jira.jboss.com/jira/browse/JBESB-557?page=comments#action_12361534 ]
Kevin Conner commented on JBESB-557:
------------------------------------
Burr, I have been running your startProcess for 10 mins now and the pool size is not
increasing. Can you double check at your end?
Please close this issue if you are happy with the fix.
BPM using JMS transports causes connection pool problem
-------------------------------------------------------
Key: JBESB-557
URL:
http://jira.jboss.com/jira/browse/JBESB-557
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: BPM
Affects Versions: 4.2 Milestone Release 1
Reporter: Burr Sutter
Assigned To: Kevin Conner
Fix For: 4.2 Milestone Release 2
Attachments: bpm_orchestrationJMS.zip
There is an attached project/quickstart that uses JMS queues for interaction between the
BPM feature and ESB. Tested on the ESB Server deployment option (not tested with AS nor
with BootStrapper).
ant deploy
ant deployProcess
ant startProcess
Now, run ant startProcess a several more times and it you'll connection pool errors.
It seems that a transaction or a connection are being held/left open.
Note: this must be tested on what is in trunk as of 5/4/2007. Not on MR1.
--
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