[esb-issues] [JBoss JIRA] Commented: (JBESB-1925) Tansactional InVM listener is never enabled
[
https://jira.jboss.org/jira/browse/JBESB-1925?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-1925:
-------------------------------------
This has been addressed with an explicit and implicit mechanism.
It is now possible for the service specification to include a "invmTransacted"
attribute which will explicitly set the transacted attribute of the listener.
If this attribute is not present then the existence of an other transacted transport (jms,
scheduled,sql) will implicitly enable the transacted attribute of the listener.
The bug in InVMCourier has also been addressed.
Tansactional InVM listener is never enabled
-------------------------------------------
Key: JBESB-1925
URL: https://jira.jboss.org/jira/browse/JBESB-1925
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.4
Reporter: Kevin Conner
Assignee: Kevin Conner
Fix For: 4.5, 4.4 CP1
The following is from an email from Martin Vecera
unfortunatelly it doesn't work with 4.4.
The output of jms_transacted QS with InVM set to GLOBAL is:
runtest:
[echo] Runs Test JMS Sender
[java] Connection Started
select:
[echo] Select * from jms_transacted_table
[sql] Executing commands
[sql] DATA_COLUMN
[sql] Hello Transacted JMS World] counter[1]
[sql]
[sql] 0 rows affected
[sql] 1 of 1 SQL statements executed successfully
truncate:
[echo] (clean up) Delete from jms_transacted_table
[sql] Executing commands
[sql] 1 rows affected
[sql] 1 of 1 SQL statements executed successfully
This indicates that the first try succeeded (Hello Transacted JMS World]
counter[1]). There should be "counter[5]".
--
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