It means you have problems with application deadlock.
I also encounted the same question.I think that the transaction is not committed.
If the tx is not committing in the tm timeout period, then this will also result. You need to either increase the default timeout or use an ejb method specific increased timeout.
Ok, i get it, but why am i getting the timeout? i know that you mean it could be due to my ejb methods, but if it happens because of some of my methods wouldnt it fails again even if i restart jboss? and it doesnt, and its weird it always happen after the server has been up for a long time (maybe a day or so)...
Sorry if all this sounds like a newbie and dumb questions for you, but is there a way i can get the stackTrace once the timeout has been reached? now i only get the message i post, so i have no idea at what point (or in what method) is this happen...
Thanx for your answers and time!
PD: also i feel that if increase the timeout period of the server, i´ll be only patching the problem, so the app will reach the time out anyway, only a little time later, or it will not?...