[
http://jira.jboss.com/jira/browse/EJBTHREE-898?page=comments#action_12416263 ]
Markus Dahm commented on EJBTHREE-898:
--------------------------------------
We had similar problems in the context of complex interaction with JMS messages, JBPM and
data base transactions. We noticed that in some
cases the message receiving transaction reported the describeed warning and another
transaction read stale old data from the database.
However, this did not happen always.
A workaround suggested by
http://www.seamframework.org/Community/AnyoneNoticeAnyJBPMProblemsWithNot...
seemed to resolve the problem:
We rewrote the message driven bean to use bean managed transactions and the warning
message disappeared.
Logging stays silent when a RuntimeException is thrown from
preDestroy method
-----------------------------------------------------------------------------
Key: EJBTHREE-898
URL:
http://jira.jboss.com/jira/browse/EJBTHREE-898
Project: EJB 3.0
Issue Type: Bug
Affects Versions: AS 4.2.0 GA
Reporter: Carlo de Wolf
Priority: Critical
Fix For: Branch_4_2
09:48:47,432 INFO [STDOUT] ContainedBean.preDestroy
09:48:47,432 WARN [arjLoggerI18N]
[com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_4]
TwoPhaseCoordinator.afterCompletion - returned failure for
com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple@1ccc3ea
--
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