[ https://issues.jboss.org/browse/WFLY-3801?page=com.atlassian.jira.plugin.... ] Tom Jenkinson edited comment on WFLY-3801 at 10/22/14 10:54 AM: ---------------------------------------------------------------- Hi Scott, I will tackle both your comments here. Yes the warning is meaningful, getStatus was called in an undefined transaction context and so resulted in various warnings. The spec compliant way to obtain the status during afterCompletion (at least insofar as JTA is concerned) is to use the value provided as the parameter of afterCompletion. I am still left wondering why HHH needs to know the status during .close(). It looks like if discardOnClose is set to true it would not need to call getStatus: https://github.com/hibernate/hibernate-orm/blob/master/hibernate-entityma... Also, I mentioned on the chat room, I thought that HHH has its own sync registered with the transaction, couldn't it do its transaction status oriented close behaviour with that if it really does need the status? was (Author: tomjenkinson): Hi Scott, I will tackle both your comments here. Yes the warning is meaningful, getStatus was called in an undefined transaction context and so resulted in various warnings. The spec compliant way to obtain the status during afterCompletion (at least insofar as JTA is concerned) is to use the value provided as the parameter of afterCompletion. I am still left wondering why HHH needs to know the status during .close(). It looks like if discardOnClose is set to true it would not need to call getStatus: https://github.com/hibernate/hibernate-orm/blob/master/hibernate-entityma... Also, I mentioned on the forum, I thought that HHH has its own sync registered with the transaction, couldn't it do its transaction status oriented close behaviour with that if it really does need the status? -- This message was sent by Atlassian JIRA (v6.3.1#6329)