[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jboss-development
Subject:    [JBoss-dev] [ jboss-Bugs-867506 ] Invalid Transaction Id
From:       "SourceForge.net" <noreply () sourceforge ! net>
Date:       2003-12-30 15:48:42
Message-ID: E1AbM6s-0004SP-00 () sc8-sf-web3 ! sourceforge ! net
[Download RAW message or body]

Bugs item #867506, was opened at 2003-12-30 06:57
Message generated for change (Comment added) made by ejort
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=867506&group_id=22866

Category: JBossMQ
Group: v3.2
> Status: Closed
> Resolution: Out of Date
Priority: 5
Submitted By: Srivatsan (srivatsanp)
> Assigned to: Adrian Brock (ejort)
Summary: Invalid Transaction Id

Initial Comment:


When multiple threads tries to publish messages, it
results in Invalid Transaction Id.
This occurs when JmsXA is used for creating the
connection, session. 
Each thread has its own connection, session, publisher
(These are not present as instance variables)

Scenario:

Tx.begin
   loop begin
     call a session bean's method
         The bean:
           looks up JmsXA, 
           creates a TopicConnection, TopicSession
(transacted=true), 
           publishes a message, 
           closes the Session, Connection
   loop end
Tx.commit

Create 'n' threads and do the above.
Please refer the attached log for the trace.

When I analyzed, it seems that when session.close() is
called and before tx.commit() is called, the same
SpySession  object is returned to some other Thread.

The attached zip contains the server.log, sources and
archives used for Testing.

First deploy publisher.jar
Then deploy service1.sar

JBoss version I am using is 3.2.1


----------------------------------------------------------------------

> Comment By: Adrian Brock (ejort)
Date: 2003-12-30 15:48

Message:
Logged In: YES 
user_id=9459

This was fixed 6 months ago.
http://cvs.sourceforge.net/viewcvs.py/jboss/jbossmq/src/main/org/jboss/mq/SpySession.java?r1=1.16.2.3&r2=1.16.2.4


You can workaround the problem by using
<track-connection-by-tx/>
in jms-ds.xml

Regards,
Adrian

----------------------------------------------------------------------

Comment By: Srivatsan (srivatsanp)
Date: 2003-12-30 13:14

Message:
Logged In: YES 
user_id=687037

After putting some prints & threaddumps, got the execution flow.
Please refer the attached InvalidTx-flow.txt for the flow.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=867506&group_id=22866


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development


[prev in list] [next in list] [prev in thread] [next in thread]