wildfly-9.0.0.CR1 ERROR [org.jboss.as.txn] WFLYTX0003: APPLICATION ERROR: transaction still active in request with status 0

[pramanish]

Hi,

I am migrating my application from Wildfly 8.1.0.CR1 to Wildfly-9.0.0.CR1 and I am getting unexpected hibernate exceptions such as LazyInitializtionException and so on. But While going through Iogs,I am seeing one common error before each hibernate exception which is following "ERROR [org.jboss.as.txn] WFLYTX0003: APPLICATION ERROR: transaction still active in request with status 0". I doubt this is causing the unexpected hibernate exceptions.

The same code works fine in Wildfly 8.1.0.CR1 without any LazyInitializationException.

Any idea what can cause this error, is this error is known ?  Let me know If you need further information.

P.S: Log file is attached for the reference.

Thanks,

Manish

[smarlow]

Hi Manish,

Can you provide the entire exception call stack?

Scott

[pramanish]

HI Scott,

Thanks for looking into this. I have attached logs into the origianal post. This logs are captured by enabling com.arjuna trace level logs. Hope this will be helpful.

Please let me know your findings.

Thanks,

Manish

[smarlow]

org.jboss.as.txn.deployment.TransactionRollbackSetupAction seems to log that message and has a comment (at top of source file) "Setup action that makes sure that no transactions leak from EE requests".  An exception call stack would of been helpful here.  I'm not sure if the error message is warning that your application needs a change or if there is a bug in WildFly, running your application.  My guess is that TransactionRollbackSetupAction.changeDepth(-1) is prematurely determining that request processing is done.

Unless someone else knows, you might need to recreate with WildFly in a debugger to at least get a call stack (by setting a break point in the TransactionRollbackSetupAction.checkTransactionStatus()).

Have you built WildFly from source yet and run in a debugger?  https://community.jboss.org/wiki/HackingOnWildFly explains how to build WildFly from source.

[pramanish]

Hi Scott,

Thanks for the quick reply.

Even, I have faced the same issue with Wildfly 8.2.0.Final but not with Wildfly 8.1.0.CR1. Actually I have switched from Wildfly 8.1.0.CR1 to  Wildfly 8.2.0.Final and Wildlfy 9.0.0.CR1 because in later versions performance of JSF Ajax Partial Re-rendering is far better.

I have gone through your reply but I am not enough clear on how to fix the issues, is it caused because in my code something is there which doesn't support latest wildfly versions, Is this a known issue, If its known issue, Nobody has faced this issue since Wildfly 8.2.0.Final.

Please provide me more insight so that I can proceed with Wildfly 9.0.0.CR1.

I really appreciate your time and help.

[smarlow]

Have you built WildFly from source yet and run in a debugger?  https://community.jboss.org/wiki/HackingOnWildFly explains how to build WildFly from source. - See more at: https://developer.jboss.org/message/928771?et=watches.email.thread#928771

You could build WildFly from source and debug the class that I mentioned (while running your application).