I am using JBoss 2.4.3 using standard Log4J logger factories (rather than JBoss customised ones).

JBoss is reporting the following transaction timeout on a periodic basis.

2005-03-14 14:00:44,625 [Thread-49] WARN LoginP - Transaction XidImpl [FormatId=257, GlobalId=knowledge1//20790, BranchQual=] timed out. status=STATUS_ACTIVE

The message can be interpreted as implicating my LoginP session bean as the bean that started a transaction which then timed-out.

Yet - having done some testing around this area I believe this is somewhat misleading and that the Category logger for LoginP is being used incorrectly by JBoss? First and foremost because I don't believe any of the methods in this Session bean could be still running beyond the 16minute transaction timeout period.

My belief is that it could be using the category logger associated with the first transaction started when the application server started up?

Does anyone have any experience with JBoss 2.4.3 and is aware of the validity or not of this log message.

Thanks for all input,

Andy