Part of this is my fault, I was throwing a Null Pointer Exception
from within my ejbStore method. There is also a bug in the
codepath which handles that exception. For some reason it
seems the context is still associated with the object even
though several of the important fields in the context get
nulled out. I'm on to bigger and better things, leaving
this to the pros!
Cheers
-----Original Message-----
From: Terry Child
To: jBoss
Sent: 8/29/00 8:16 AM
Subject: Re: [jBoss-User] Transaction problem?
Hi
The following when called from within a bean with a required TX returns
null for
tx. Is this related?
InitialContext ctx;
TransactionManager tm;
Transaction tx;
ctx = new InitialContext();
tm = (TransactionManager) ctx.lookup("TransactionManager");
tx = tm.getTransaction(); // <- returns null
Regards
Terry Child
----- Original Message -----
From: marc fleury <[EMAIL PROTECTED]>
To: jBoss <[EMAIL PROTECTED]>
Sent: Monday, August 28, 2000 10:01 PM
Subject: RE: [jBoss-User] Transaction problem?
> I'll test that... there is obviously a Tx duplication. I'll try to
track it
> tomorrow,
>
> marc
>
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Jay Walters
> > Sent: Monday, August 28, 2000 1:30 PM
> > To: 'jBoss'
> > Subject: [jBoss-User] Transaction problem?
> >
> >
> > I am running what should be this afternoon's CVS state - I did a
build
> > around 1:30 EDT.
> >
> > I have an BMP entity EJB and a client program which creates the
> > EJB and then
> > calls some methods on the entity bean. Something like ...
> >
> > t1 = home.create( 1, 0, 1 );
> > t1.addItem( 1, 5 );
> > t1.addItem( 2, 10 );
> >
> > The jBoss console displays ...
> >
> > [ejbw.Test] TX_REQUIRED for create
> > [ejbw.Test] Begin tx
> > [ejbw.Test] commiting
> > [ejbw.Test] beforeCompletion called
> > [ejbw.Test] afterCompletion called
> > [ejbw.Test] TX_REQUIRED for addItem
> > [ejbw.Test] Begin tx
> > [ejbw.Test] Tx is tx:Xid:1
> > [ejbw.Test] commiting
> > [ejbw.Test] beforeCompletion called
> > [ejbw.Test] afterCompletion called
> > [ejbw.Test] TX_REQUIRED for addItem
> > [ejbw.Test] Begin tx
> >
> > Then jBoss hangs (at least the thread for that client) gets stuck in
the
> > second addItem call with the following stack - the code at that line
is
> > doing a wait(5000) based on thinking some previous transaction is
still
> > accessing the object.
> >
> > "RMI TCP Connection(11)-127.0.0.1" daemon prio=5 tid=0x91a7428
nid=0xb78
> > waiting
> > on monitor [0x9c0f000..0x9c0fdc4]
> > at java.lang.Object.wait(Native Method)
> > at
> >
org.jboss.ejb.plugins.NoPassivationEntityInstanceCache.get(NoPassivat
> > ionEntityInstanceCache.java:158)
> > at
> >
org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke(EntityInstance
> > Interceptor.java:102)
> > at
> >
org.jboss.ejb.plugins.TxInterceptor.invokeNext(TxInterceptor.java:128
> > )
> > at
> >
org.jboss.ejb.plugins.TxInterceptor.runWithTransactions(TxInterceptor
> > .java:189)
> > at
> > org.jboss.ejb.plugins.TxInterceptor.invoke(TxInterceptor.java:96)
> > at
> >
org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.
> > java:140)
> > at
> > org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:156)
> > at
org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:320)
> > at
> >
org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPCon
> > tainerInvoker.java:200)
> > at
> >
org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPCon
> > tainerInvoker.java:177)
> > at java.lang.reflect.Method.invoke(Native Method)
> > at
> > sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:241)
> > at sun.rmi.transport.Transport$1.run(Transport.java:142)
> > at java.security.AccessController.doPrivileged(Native
Method)
> > at
sun.rmi.transport.Transport.serviceCall(Transport.java:139)
> > at
> >
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:4
> > 43)
> > at
> >
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport
> > .java:643)
> > at java.lang.Thread.run(Thread.java:484)
> >
> >
> >
> > --
> > --------------------------------------------------------------
> > To subscribe: [EMAIL PROTECTED]
> > To unsubscribe: [EMAIL PROTECTED]
> > Problems?: [EMAIL PROTECTED]
> >
> >
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
