Status of cleanup after timeout issue?

[teknokrat]

What is the status of http://jira.jboss.org/jira/browse/JBAS-4481

We are using JBoss 4.2.2 and our app is being decimated by this issue.

cheers

[marklittle]

Are you sure it's this issue, or something like it? The issue is closed against AS 4.2.1GA, so it should be in 4.2.2 as well.

[teknokrat]

Interesting, let me tell you what we are seeing. Sporadically we get a warning in the logs that a transaction has timed out. If we go the jboss web-console and look at the status of the tomcat connectors then we see that the thread that was servicing that connection is in state S. It remains in this state until we restart the server. As the server runs, these 'dead' connections build up until the server stops responding.

Is this not the same issue?

[adinn]

Is this not the same issue?

Well it might be but then again . . .

Can you supply any info from the log file indicating what is happening before and after the transaction times out and the thread gets wedged. In particular, I'd be interested to see what the TransactionReaper thread is saying. Ta.

[teknokrat]

Its like this, we have an ejb that attempts to get data from a remote resource. This can take some time and unfortunately, for legacy reasons, happens inside a transaction. On occasion the transaction timeout is exceeded and we see in the logs

WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N:] [com.arjuna.ats.arjuna.coordinator.BasicAction_58] - Abort of action id a403267:a14:47d50c32:247 invoked while multiple threads active within it.

Looking in the tomcat status page we find

S 97208986 ms 0 KB 0 KB 62.40.38.158 www.***.com POST /**** HTTP/1.1

What kind of logging would you have us enable to provide you with more information?

[marklittle]

Turn on JBossTS logging. It's documented in the TS Administrator's guide.

[marklittle]

BTW, have you checked http://wiki.jboss.org/wiki/Wiki.jsp?page=TxMultipleThreads?

[teknokrat]

I have changed the debug level in jbossjta-properties.xml to 0xffffffff and added a debug category to logj.xml for com.arjuna.

Is this enough?

[marklittle]

If you're now getting lots of output from JBossTS then it's enough. However, did you check the wiki page I mentioned?

[teknokrat]

yes, i did. However, we are not seeing any exceptions being thrown in our code and most of the transactions complete just fine. we are adding more diagnostics though. so hopefully I will have more to report in a few days.