Hours later I give up and just fixed my app to connection and disconnect from
the session for each method call... which actually simplifies things for me
alot. Anyways... now I am getting this baby:
<snip>
java.rmi.ServerException: Application Error: tried to enter Stateful bean with
different transaction context; nested exception is:
java.rmi.RemoteException: Application Error: tried to enter Stateful
bean with different transaction context
at
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:140)
at
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:167)
at
org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:61)
at
org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:166)
at
org.jboss.ejb.StatefulSessionContainer.invoke(StatefulSessionContainer.java:380)
at org.jboss.ejb.Container.invoke(Container.java:705)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
at
org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:98)
at
org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:102)
at
org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:73)
at
org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:76)
at
org.jboss.proxy.ejb.StatefulSessionInterceptor.invoke(StatefulSessionInterceptor.java:117)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:76)
at $Proxy25.send(Unknown Source)
</snip>
I am guess this is the exception that pops out when there is concurrent access
to a SFSB... can someone confirm this for me.
--jason
On Friday 24 May 2002 05:56 am, David Jencks wrote:
> I looked at the jmsra code a bit. You should be able to hold onto the
> session over method calls (new feature w/ new jca impl) but not anything
> you get from the session, such as the sender. The session may be
> associated with different physical connections on each (SFSB) call, and the
> sender will be tied to the physical connection it was originally created
> from.
>
> david jencks
>
> On 2002.05.24 03:41:03 -0400 Jason Dillon wrote:
> > Or perhaps I am not using the JMS resource propertly within the bean...
> >
> > Should I be able to save a QueueSession and QueueSender as fields and use
> > them
> > over multipule calls inside of a SFSB? Or do I need to recreate the
> > session
> > and sender each time?
> >
> > If that is the case it rather sucks... what a pain...
> >
> > --jason
> >
> > On Friday 24 May 2002 12:22 am, Jason Dillon wrote:
> > > After thinking about this somemore, and enabling thread info in
> >
> > server.log
> >
> > > I realize now that the timer is not an issue, there is never an
> >
> > instance
> >
> > > where the timer thread attempts to use the wrapper over the SFSB... the
> > > work completes too fast.
> > >
> > > And due to the fact that I sync'd the wrapper methods it appears that
> >
> > this
> >
> > > problem happens simply because the invoke happened in a seperate
> >
> > thread.
> >
> > > Unfortunatly it does not really narrow the problem space to debug. The
> >
> > JMS
> >
> > > RA does not function with out a TX, it does not attempt to start one if
> > > there isn't one already... so it just fails.
> > >
> > > Is it possible that there is something a miss with the bits which setup
> >
> > the
> >
> > > tx for the SFSB? Or would I see other problems when the SFSB
> >
> > commits... I
> >
> > > think this is the case, but I am not sure.
> > >
> > > If that is true, and the SFSB does have a TX, then it must be the JMS
> >
> > RA or
> >
> > > JBossMQ which is at fault... and I don't really know how to isolate
> >
> > which
> >
> > > it is at this point. If I don't use the JMS RA, then I have to
> >
> > implement
> >
> > > all of the XA stuff myself, which I am sure to mess up.
> > >
> > > Any clue on how I could narrow the problem space any?
> > >
> > > I am running the same test again with trace enabled for org.jboss.mq
> >
> > and
> >
> > > org.jboss.resource.adapter.jms. With the added log messages for the
> >
> > JMS RA
> >
> > > I might be able to see a problem... but who knows.
> > >
> > > --jason
> > >
> > > On Thursday 23 May 2002 08:26 pm, Scott M Stark wrote:
> > > > If the only cause of this can be use by multiple threads, then
> >
> > updating
> >
> > > > the error message to indicate incorrect usage would be good.
> > > >
> > > > xxxxxxxxxxxxxxxxxxxxxxxx
> > > > Scott Stark
> > > > Chief Technology Officer
> > > > JBoss Group, LLC
> > > > xxxxxxxxxxxxxxxxxxxxxxxx
> > > > ----- Original Message -----
> > > > From: "Jason Dillon" <[EMAIL PROTECTED]>
> > > > To: <[EMAIL PROTECTED]>; "Scott M Stark"
> > > > <[EMAIL PROTECTED]>
> > > > Sent: Thursday, May 23, 2002 8:18 PM
> > > > Subject: Re: [JBoss-dev] Seeing occasional Invalid tx id with JMS RA
> > > >
> > > >
> > > > Does this mean we should not try to produce more meaningful error
> > > > messages when this does happen... or just leave it as is?
> > > >
> > > > --jason
> > > >
> > > > On Thursday 23 May 2002 08:00 pm, Scott M Stark wrote:
> > > > > I don't see sufficient justification to go beyond the spec here so
> > > > > let's just leave it.
> > > > >
> > > > > xxxxxxxxxxxxxxxxxxxxxxxx
> > > > > Scott Stark
> > > > > Chief Technology Officer
> > > > > JBoss Group, LLC
> > > > > xxxxxxxxxxxxxxxxxxxxxxxx
> > > > > ----- Original Message -----
> > > > > From: "Hiram Chirino" <[EMAIL PROTECTED]>
> > > > > To: <[EMAIL PROTECTED]>
> > > > > Sent: Thursday, May 23, 2002 7:45 PM
> > > > > Subject: RE: [JBoss-dev] Seeing occasional Invalid tx id with JMS
> >
> > RA
> >
> > > > > > He who codes wins the vote. This issue does not bother me enough
> >
> > to
> >
> > > > > change
> > > > >
> > > > > > anything.
> > > > > >
> > > > > > Regards,
> > > > > > Hiram
> > > > > >
> > > > > > >From: David Maplesden <[EMAIL PROTECTED]>
> > > > > > >Reply-To: [EMAIL PROTECTED]
> > > > > > >To: "'[EMAIL PROTECTED]'"
> > > > > > ><[EMAIL PROTECTED]>
> > > > > > >Subject: RE: [JBoss-dev] Seeing occasional Invalid tx id with
> >
> > JMS RA
> >
> > > > > > >Date: Fri, 24 May 2002 14:35:21 +1200
> > > > > > >
> > > > > > >I understand the pros and cons, I am just saying what I feel.
> >
> > You
> >
> > > > > > > can outvote me if you wish.
> > > > > > >
> > > > > > >David
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Hiram Chirino [mailto:[EMAIL PROTECTED]]
> > > > > > > > Sent: Friday, May 24, 2002 2:14 PM
> > > > > > > > To: [EMAIL PROTECTED]
> > > > > > > > Subject: RE: [JBoss-dev] Seeing occasional Invalid tx id with
> >
> > JMS
> >
> > > > > > > > RA
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Think about it this way... somebody creates a simple servlet
> > > > > > > > that creates a
> > > > > > > > unit of work by sending 2 messages and then commits the work.
> > > > > > > > Somebody that
> > > > > > > > does not know the spec to will might cache that session in a
> > > >
> > > > instance
> > > >
> > > > > > > > variable. If 2 requests come in at the same time, they will
> > > > > > > > screw each
> > > > > > > > other up seriously. The first request might commit his 2
> > > > > > > > messages and some
> > > > > > > > of the messages the 2nd thread was creating.
> > > > > > > >
> > > > > > > > So the question is, should we try to make the session
> > > > > > > > thread-safe for the
> > > > > > > > power users out there that MIGHT know how stuff is working
> > > > > > > > under the covers.
> > > > > > > > Or should we make the session check conncurent access
> >
> > better to
> >
> > > > let
> > > >
> > > > > > > > beginer user know when he has potentialy made a semantical
> >
> > error.
> >
> > > > > > > > Regards,
> > > > > > > > Hiram
> > > > > > > >
> > > > > > > > >From: David Maplesden <[EMAIL PROTECTED]>
> > > > > > > > >Reply-To: [EMAIL PROTECTED]
> > > > > > > > >To: "'[EMAIL PROTECTED]'"
> > > > > > > > ><[EMAIL PROTECTED]>
> > > > > > > > >Subject: RE: [JBoss-dev] Seeing occasional Invalid tx id
> >
> > with
> >
> > > > > > > > > JMS
> > > >
> > > > RA
> > > >
> > > > > > > > >Date: Fri, 24 May 2002 13:36:43 +1200
> > > > > > > > >
> > > > > > > > >I hate to disagree with Scott and Hiram but I feel that just
> > > > > > > >
> > > > > > > > because the
> > > > > > > >
> > > > > > > > >spec says Sessions should only be used in 1 thread does not
> > > > > > > >
> > > > > > > > neccessarily
> > > > > > > >
> > > > > > > > >mean that we should restrict their usage as such.
> > > > > > > > >
> > > > > > > > >I know a Session only makes sense in the context of a single
> > > > > > > >
> > > > > > > > process, but
> > > > > > > >
> > > > > > > > >this might still entail the usage of a couple of different
> > > > > > > >
> > > > > > > > threads. I
> > > > > > > >
> > > > > > > > >don't
> > > > > > > > >think we should place any restrictions on the usage of
> > > > > > > >
> > > > > > > > Sessions as long as
> > > > > > > >
> > > > > > > > >they work, and I believe making sendMessage() synchronized
> > > > > > > >
> > > > > > > > will do the
> > > > > > > >
> > > > > > > > >trick.
> > > > > > > > >
> > > > > > > > >This can be just one more area where JBoss goes "Beyond the
> > > > > > > >
> > > > > > > > Spec" but hey I
> > > > > > > >
> > > > > > > > >leave the final decision up to someone else.
> > > > > > > > >
> > > > > > > > >David.
> > > > > > > > >
> > > > > > > > >---
> > > > > > > > >Outgoing mail is certified Virus Free.
> > > > > > > > >Checked by AVG anti-virus system (http://www.grisoft.com).
> > > > > > > > >Version: 6.0.362 / Virus Database: 199 - Release Date:
> >
> > 5/7/2002
> >
> > > > > > > > >____________________________________________________________
> > > > > > > > >___
> > > > > > > > >
> > > > > > > > >Don't miss the 2002 Sprint PCS Application Developer's
> > > > > > > > > Conference August 25-28 in Las Vegas --
> > > > > > >
> > > > > > >http://devcon.sprintpcs.com/adp/index.cfm
> > > > > > >
> > > > > > > >_______________________________________________
> > > > > > > >Jboss-development mailing list
> > > > > > > >[EMAIL PROTECTED]
> > > > > > > >https://lists.sourceforge.net/lists/listinfo/jboss-development
> > > > > > >
> > > > > > >________________________________________________________________
> > > > > > >_ MSN Photos is the easiest way to share and print your photos:
> > > > > > > http://photos.msn.com/support/worldwide.aspx
> > > > > > >
> > > > > > >
> > > > > > >_______________________________________________________________
> > > > > > >
> > > > > > >Don't miss the 2002 Sprint PCS Application Developer's
> >
> > Conference
> >
> > > > > > >August 25-28 in Las Vegas --
> > > > > > > http://devcon.sprintpcs.com/adp/index.cfm
> > > > > > >
> > > > > > >_______________________________________________
> > > > > > >Jboss-development mailing list
> > > > > > >[EMAIL PROTECTED]
> > > > > > >https://lists.sourceforge.net/lists/listinfo/jboss-development
> > > > > > >
> > > > > > >---
> > > > > > >Incoming mail is certified Virus Free.
> > > > > > >Checked by AVG anti-virus system (http://www.grisoft.com).
> > > > > > >Version: 6.0.362 / Virus Database: 199 - Release Date: 5/7/2002
> > > > > > >
> > > > > > >
> > > > > > >---
> > > > > > >Outgoing mail is certified Virus Free.
> > > > > > >Checked by AVG anti-virus system (http://www.grisoft.com).
> > > > > > >Version: 6.0.362 / Virus Database: 199 - Release Date: 5/7/2002
> > > > > > >
> > > > > > >
> > > > > > >_______________________________________________________________
> > > > > > >
> > > > > > >Don't miss the 2002 Sprint PCS Application Developer's
> >
> > Conference
> >
> > > > > > >August 25-28 in Las Vegas --
> > > > > > > http://devcon.sprintpcs.com/adp/index.cfm
> > > > > > >
> > > > > > >_______________________________________________
> > > > > > >Jboss-development mailing list
> > > > > > >[EMAIL PROTECTED]
> > > > > > >https://lists.sourceforge.net/lists/listinfo/jboss-development
> > > > > >
> > > > > > _________________________________________________________________
> > > > > > MSN Photos is the easiest way to share and print your photos:
> > > > > > http://photos.msn.com/support/worldwide.aspx
> > > > > >
> > > > > >
> > > > > > _______________________________________________________________
> > > > > >
> > > > > > Don't miss the 2002 Sprint PCS Application Developer's Conference
> > > > > > August 25-28 in Las Vegas --
> > > > > > http://devcon.sprintpcs.com/adp/index.cfm
> > > > > >
> > > > > > _______________________________________________
> > > > > > Jboss-development mailing list
> > > > > > [EMAIL PROTECTED]
> > > > > > https://lists.sourceforge.net/lists/listinfo/jboss-development
> > > > >
> > > > > _______________________________________________________________
> > > > >
> > > > > Don't miss the 2002 Sprint PCS Application Developer's Conference
> > > > > August 25-28 in Las Vegas --
> > > > > http://devcon.sprintpcs.com/adp/index.cfm
> > > > >
> > > > > _______________________________________________
> > > > > Jboss-development mailing list
> > > > > [EMAIL PROTECTED]
> > > > > https://lists.sourceforge.net/lists/listinfo/jboss-development
> > > >
> > > > _______________________________________________________________
> > > >
> > > > Don't miss the 2002 Sprint PCS Application Developer's Conference
> > > > August 25-28 in Las Vegas --
> > > > http://devcon.sprintpcs.com/adp/index.cfm
> > > >
> > > > _______________________________________________
> > > > Jboss-development mailing list
> > > > [EMAIL PROTECTED]
> > > > https://lists.sourceforge.net/lists/listinfo/jboss-development
> > >
> > > _______________________________________________________________
> > >
> > > Don't miss the 2002 Sprint PCS Application Developer's Conference
> > > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
> > >
> > > _______________________________________________
> > > Jboss-development mailing list
> > > [EMAIL PROTECTED]
> > > https://lists.sourceforge.net/lists/listinfo/jboss-development
> >
> > _______________________________________________________________
> >
> > Don't miss the 2002 Sprint PCS Application Developer's Conference
> > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
> >
> > _______________________________________________
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/jboss-development
>
> _______________________________________________________________
>
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
