[jbossts-issues] [JBoss JIRA] (JBTM-3339) ArjunaJTS/interop/glassfish hangs on CI

Michael Musgrove (Jira) issues at jboss.org
Tue Jun 30 05:36:48 EDT 2020


    [ https://issues.redhat.com/browse/JBTM-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14182567#comment-14182567 ] 

Michael Musgrove commented on JBTM-3339:
----------------------------------------

It is worth noting that the server never actually ran the ejb test:

 

> Failed to connect to the controller: Timeout waiting for the system to boot.

 

and the log store was uninitialised and the transaction subsystem did not seem to be initialised yet since the CLI showed "jts=false". This means the test didn't actually start since the steps are:

 

1. build wilfly and glassfish from source

2. start glassfish

3. start wildfly and run a cli script to configure it into JTS mode.

... etc

 

When I looked the wfly server had come up but hadn't made progress since the configure script had not set jts mode.  

> ArjunaJTS/interop/glassfish hangs on CI
> ---------------------------------------
>
>                 Key: JBTM-3339
>                 URL: https://issues.redhat.com/browse/JBTM-3339
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: Demonstrator
>    Affects Versions: 5.10.4.Final
>            Reporter: Michael Musgrove
>            Priority: Minor
>             Fix For: 6.later
>
>         Attachments: stacktraces
>
>
> The [WildFly to GlassFish interop quickstart|[https://github.com/jbosstm/quickstart/tree/master/ArjunaJTS/interop]] hung on CI. I am attaching the stackdumps but it doesn't look like Wilfly started fully so is probably an transient error. Since the quickstart is a demonstrator I am marking the priority as low. If it happens again we might want to increase its priority.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)



More information about the jbossts-issues mailing list