[hibernate-dev] what does ""DEBUG [org.hibernate.engine.transaction.internal.TransactionCoordinatorImpl] (EJB default - 6) Skipping JTA sync registration due to auto join checking" mean?

[Scott Marlow]

Looks like we are creating a (container managed) transaction scoped 
entity manager (persistence context) inside the JTA transaction and we 
get the "Skipping JTA sync registration due to auto join checking" 
message logged quite a bit but no failures seem to be related to that. 
What are your persistence.xml settings?

With regard to the jira, I'll respond there about the transaction 
timeout error that your getting (this thread is more for answering my 
question about the above "Skipping JTA sync registration" message.)

On 08/20/2014 09:36 AM, Robert Heine wrote:
> Hi Scott,
>
> looks like the file got a immature <EOF>, I reattached the full log again.
>
> Can you please remove the defective log to reduce confusion? :)
>
> Thanks
> Rob
>
> On 20.08.2014 15:07, Scott Marlow wrote:
>> Hi Rob,
>>
>> I don't see the "com.microsoft.sqlserver.jdbc.SQLServerException: Das
>> Timeout für Sperranforderung wurde überschritten" error in the logs. Did
>> you get that when generating the latest log?
>>
>> Scott
>>
>> On 08/20/2014 05:37 AM, Robert Heine wrote:
>>> Hi Scott,
>>>
>>> I added the latest log with all required log levels to the jira ticket.
>>>
>>> Rob
>>>
>>> On 20.08.2014 03:40, Scott Marlow wrote:
>>>> On 08/19/2014 09:07 AM, Scott Marlow wrote:
>>>>> Hi Rob,
>>>>>
>>>>> The new logfile is missing TRACE logging for the other categories.
>>>>> Please attach a new log with TRACE enabled for:  org.jboss.jca,
>>>>> org.hibernate, org.jboss.as.jpa, com.arjuna
>>>>
>>>> Just add the log file with the above categories, to the WFLY-3619 jira
>>>> (not this email thread).
>>>>
>>>>>
>>>>> com.arjuna will show the transaction boundaries, org.jboss.jca will
>>>>> show
>>>>> connection pooling related information, org.jboss.as.jpa will us how
>>>>> the
>>>>> application requested the EE/JPA container to create the persistence
>>>>> context and of course, org.hibernate will show what is occurring in
>>>>> Hibernate ORM.
>>>>>
>>>>> Scott
>>>>
>>