lock in ReplyReceiver.getReply

[rarondini]

Hi all

I have an batch process running on JBoss 4.0.5 with JBoss Transaction 4.2.2 SP3. This process perform during one hour approximately.

So, I have been notated that after applications threads finish, the process is not finished. By command line kill -3 on process, I get the follow stack:

at org.jacorb.orb.giop.ReplyPlaceholder.getInputStream(ReplyPlaceholder.java:119)
- locked <0xad522e98> (a org.jacorb.orb.ReplyReceiver)
at org.jacorb.orb.ReplyReceiver.getReply(ReplyReceiver.java:277)
- locked <0xad522e98> (a org.jacorb.orb.ReplyReceiver)
at org.jacorb.orb.Delegate.invoke_internal(Delegate.java:963)


What happen with jacorb commit process ???

tks.

[rarondini]

Sorry.
The JBoss Transaction version is 4.2.3 SP3

[marklittle]

I'm afraid you'll have to give us a bit more information than this to go on. For example, can you attach a debugger and inspect the thread?

[rarondini]

No.. I'm not attach a debugger.

I susptected that process is to long (more than one hour), and by using "top" command on linux, the machine was total free.

After that, I call kill -3 on JVM process, and in full thread dump Java HotSpot did not appear none thread (or object) of my application. All threads in thread dump were of the arjuna...

P.S. Yesterday I had de same problem, but the arjuna commit conclude with success after 30 minutes.

[marklittle]

OK. Sorry, but until you can give us more information (and a test case would be useful too), it's not going to be possible for us to track this down.