I already went through this page quoted by you, and additionally through the page:
The point 8 on this FAQ talks about configuring JBoss 4 to inturrupt threads after a specified timeout. By default JBoss 4 doesn't interrupt threads until directed to do so using the "InterruptThreads" attribute set to "true" in jboss-service.xml. The same attribute when used with a "false" value in JBoss 3.2.6 won't work.
The essense is that is there any way I can make JBoss 3.2.6 behave as JBoss 4 in case of transactions, i.e., method trasaction timeouts to be infinite.
Regards & Thanx,
why the change to default of InterruptThreads?
And, would that solve sajid's and my problems?
Thanx and rgds, Ales
It's generally a really bad idea to just arbitrarily interrupt threads. The transaction service does not have the necessary semantic information to know that sending a kill/hup to a thread will not cause unrecoverable data corruption. Only the application has that knowledge.
Therefore by default, JBoss Transactions will not do this when a timeout occurs. It will rollback the transaction and threads will have to find out that is the case lazily. If you want to interrupt threads, then you can do so by registering application specific handlers with JBossTS.
In general, if you are using transactions in JBoss 4, I'd recommend moving to JBoss Transactions.