Not sure if you can disable it altogether. You could of course change it to a really large value. Or if it's an EJB, change the timeout locally with an annotation or deployment descriptor.
I have tried with values of 99999, 9999, 7200, 6000, 3200, 0, -1
It all translates to 300 seconds.
I read in some posts that the time out value can be set in certain classes.
That would be perfect.
Does anyone have an example of @TransactionTimeout(xxxx) (with imports) ?
I use JBoss 7 AS
The idea of having a global transaction time out limit with possible exeptions by class is fantastic.
It solves the age old problem of runaway transactions
Strange. Just yesterday I had timeouts on a 7.1.1 I solved by increasing the timeout from 300 to 600.
I'm not sure whether this is what are you looking for but there is an article on this in documentation:
Have you try to check the value of default timeout via jboss-cli?
I am 59 years old so I can't be a newby, maybe I am over the hill.
I retested with a timeout value of 7200 and it was ok.
Then I dropped the time out to 100 and I got the ususal errors (the error I got is related to a unique constraint violation because a new thread was started with a new Oracle sequence value)
I changed the timeout back to 7200 and all was ok again.
Thank you very much for your advise and apologies for wasting your time.
One think we have learned is that JBoss has this fantastic feature.
JBoss never ceases to amaze me.