[
https://jira.jboss.org/jira/browse/JBPM-2472?page=com.atlassian.jira.plug...
]
Alejandro Guizar updated JBPM-2472:
-----------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Make JMS session creation configurable
--------------------------------------
Key: JBPM-2472
URL:
https://jira.jboss.org/jira/browse/JBPM-2472
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 3.3.1 GA, jBPM 3.2.5 GA
Environment: Weblogic 10.3
jBPM 3.3.1.GA
Reporter: Alejandro Guizar
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.7
Attachments: mylyn-context.zip
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
The kind of session (transacted vs. non-transacted) that jBPM uses is not configurable:
it is hard coded in JmsMessageService.java
session = connection.createSession(true, Session.SESSION_TRANSACTED);
That line was changed as follows to make async continuations work with Weblogic.
session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE) ;
The reason is that JBoss and Weblogic handle JMS sessions within a JTA transaction just
in the opposite way. For details read:
Weblogic:
http://e-docs.bea.com/wls/docs103/jms/trans.html#wp1025537
JBoss:
http://www.odi.ch/prog/jms-tx.php
--
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