Bugs item #925399, was opened at 2004-03-29 16:23
Message generated for change (Comment added) made by wolfftw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=925399&group_id=22866

Category: JBossMQ
Group: v3.2
Status: Open
Resolution: Later
Priority: 5
Submitted By: Todd Wolff (wolfftw)
Assigned to: Nobody/Anonymous (nobody)
Summary: StdServerSession always transacted

Initial Comment:
OnMessage method always starts a transaction even 
though connection is non-XA and transacted set to 
false for ServerSessionPool.

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

>Comment By: Todd Wolff (wolfftw)
Date: 2004-04-02 15:52

Message:
Logged In: YES 
user_id=839156

No. I'm referring to the comment in the onMessage method of 
StdServerSession:

"... So, for the case where we do not have an XASession and 
the bean is not transacted, we have the unneeded overhead 
of creating a Transaction. I'm leaving it this way since it 
keeps the code simpler and that case should not be too 
common (JBossMQ provides XASessions)."

This precludes the use of ServerSessionPool for those of us 
that are writing message driven processes using POJO's, ie. 
not MDB's, and who are managing transactions explicitly via 
UserTransaction.

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

Comment By: Adrian Brock (ejort)
Date: 2004-04-01 21:07

Message:
Logged In: YES 
user_id=9459

I think you are referring to the following comment in
org.jboss.metadata.MessageDrivenMetaData?

      // My interpretation of the EJB and JMS spec leads
      // me to that CLIENT_ACK is the only possible
      // solution. A transaction is per session in JMS, and
      // it is not possible to get access to the transaction.
      // According to the JMS spec it is possible to
      // multithread handling of messages (but not session),
      // but there is NO transaction support for this.
      // I,e, we can not use the JMS transaction for
      // message ack: hence we must use manual ack.
      
      // But for NOT_SUPPORTED this is not true here we
      // should have AUTO_ACKNOWLEDGE_MODE
      
      // This is not true for now. For JBossMQ we relly
      // completely on transaction handling. For JBossMQ, the
      // ackmode is actually not relevant. We keep it here
      // anyway, if we find that this is needed for other
      // JMS provider, or is not good.


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

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


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to