I am not sure what you think is interesting, but from time to time, when
large jobs are being processed and I end up with a hang I see this every
time (note that the line numbers are off by one... but that is not the
interesting bit):
<snip>
Full thread dump Classic VM (1.3.1-b24, green threads):
"RMI TCP Connection(42)-127.0.0.1" (TID:0x4143d208,
sys_thread_t:0x9144730, state:CW) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at
org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke(EntityInstanceInterceptor.java:183)
at
org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:97)
at
org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:153)
at
org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:62)
at
org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:127)
at
org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:195)
at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:373)
at
org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPContainerInvoker.java:360)
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:152)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:148)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:465)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:706)
at java.lang.Thread.run(Thread.java:484)
</snip>
on the MDB side I get things like this:
JMXAdaptorService [Thread-12] WARN - Transaction XidImpl [FormatId=257,
GlobalId=reason//48, BranchQual=] timed out. status=STATUS_ACTIVE
and on the spooler side I get:
Customer [Thread-20] WARN - Transaction XidImpl [FormatId=257,
GlobalId=reason//158, BranchQual=] timed out. status=STATUS_COMMITING
Customer [Thread-21] WARN - Transaction XidImpl [FormatId=257,
GlobalId=reason//159, BranchQual=] timed out. status=STATUS_ACTIVE
This is very, very weird, because the Customer entity is only used very
early on in the process. At other times I will get the same with a
Stateless session that controls the clients interation (via the web proxy).
*sigh*
I guess the only thing that I can really do here, is try and make a test to
reproduce this. I am still learning how the internals of the container
work, which is driving me a bit loony at the moment (topped off by a large
pill of stress and a dab of desperation).
--jason
On Wed, 11 Jul 2001, Scott M Stark wrote:
> Alright. Like I said the best starting point is a thread dump of the VM that
> appears to be hanging. Post it if you get one that looks interesting.
>
> ----- Original Message -----
> From: "Jason Dillon" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, July 11, 2001 10:47 PM
> Subject: Re: [JBoss-dev] EntityInstanceInterceptor change
>
>
> > It is complicated.
> >
>
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
