[ http://jira.jboss.com/jira/browse/JBAS-497?page=history ]
Adrian Brock closed JBAS-497:
-----------------------------
Resolution: Out of Date
This was fixed 6 days *before* this bug report was initially created:
http://cvs.sourceforge.net/viewcvs.py/jboss/jboss/src/main/org/jboss/ejb/plugins/StatefulSessionInstanceInterceptor.java?only_with_tag=JBoss_3_2_4_RC2
but not in the 3.0.x branch.
> bug in stateful container (3.0.7)
> ---------------------------------
>
> Key: JBAS-497
> URL: http://jira.jboss.com/jira/browse/JBAS-497
> Project: JBoss Application Server
> Type: Bug
> Reporter: SourceForge User
> Assignee: Scott M Stark
>
>
> SourceForge Submitter: eprst .
> Hi
> There is an inconsistency between
> StatefulSessionContainer and
> StatefulSessionInstanceInterceptor which is a reason
> (IMHO) of
> pretty annoying bug - if one calls some business
> method of stateful
> bean in catch() after rollback exception, this bean is
> marked as used in transaction and afterCompletion is
> never called
> for it. Here's the problem location:
>
> ---StatefulSessionContainer.java---
> public Object invoke(Invocation mi)
> throws Exception
> {
> //wire the transaction on the context, this is
> how the instance remember the tx
> // Unlike Entity beans we can't do that in the
> previous interceptors (ordering)
> if (((EnterpriseContext)
> mi.getEnterpriseContext()).getTransaction() == null)
> ((EnterpriseContext)
> mi.getEnterpriseContext()).setTransaction(mi.getTransaction());
> ---
> ---StatefulSessionInstanceInterceptor.java---
> protected void register(EnterpriseContext ctx,
> Transaction tx, BeanLock lock)
> {
> // Create a new synchronization
> InstanceSynchronization synch = new
> InstanceSynchronization(tx, ctx, lock);
>
> try
> {
> // OSH: An extra check to avoid warning.
> // Can go when we are sure that we no longer get
> // the JTA violation warning.
> if (tx.getStatus() ==
> Status.STATUS_MARKED_ROLLBACK)
> {
>
> return;
> }
> ---
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development
