0 Replies Latest reply on Sep 7, 2016 9:22 AM by rgiovanardi

Wildfly 8.2.1 hangs during boot

rgiovanardi Sep 7, 2016 9:22 AM

Hi all,

we are facing a problem with Wildfly 8.2.1: occasionally it didn't starts but hangs during boot, right after first application deployments.

Killing the JVM and starting again sometimes helps; other times we have to clean deployments from standalone-full-ha.xml file, start the Wildfly then deploy again the webapps.

We had the same problem using standalone-full-ha.xml and standalone.xml profile. After hanging a while, Wildfly logs are:

2016-09-06 17:33:23,101 WARN [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012117: TransactionReaper::check timeout for TX 0:ffffc0a83569:-6c981c1b:57cee045:59 in state RUN

2016-09-06 17:33:23,103 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012095: Abort of action id 0:ffffc0a83569:-6c981c1b:57cee045:59 invoked while multiple threads active within it.

2016-09-06 17:33:23,104 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012108: CheckedAction::check - atomic action 0:ffffc0a83569:-6c981c1b:57cee045:59 aborting with 1 threads active!

2016-09-06 17:33:23,104 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012121: TransactionReaper::doCancellations worker Thread[Transaction Reaper Worker 0,5,main] successfully canceled TX 0:ffffc0a83569:

-6c981c1b:57cee045:59

2016-09-06 17:33:23,243 WARN [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012117: TransactionReaper::check timeout for TX 0:ffffc0a83569:-6c981c1b:57cee045:5a in state RUN

2016-09-06 17:33:23,244 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012095: Abort of action id 0:ffffc0a83569:-6c981c1b:57cee045:5a invoked while multiple threads active within it.

2016-09-06 17:33:23,245 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012108: CheckedAction::check - atomic action 0:ffffc0a83569:-6c981c1b:57cee045:5a aborting with 1 threads active!

2016-09-06 17:33:23,245 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012121: TransactionReaper::doCancellations worker Thread[Transaction Reaper Worker 0,5,main] successfully canceled TX 0:ffffc0a83569:

-6c981c1b:57cee045:5a

2016-09-06 17:33:24,268 WARN [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012117: TransactionReaper::check timeout for TX 0:ffffc0a83569:-6c981c1b:57cee045:5b in state RUN

2016-09-06 17:33:24,270 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012095: Abort of action id 0:ffffc0a83569:-6c981c1b:57cee045:5b invoked while multiple threads active within it.

2016-09-06 17:33:24,270 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012108: CheckedAction::check - atomic action 0:ffffc0a83569:-6c981c1b:57cee045:5b aborting with 1 threads active!

2016-09-06 17:33:24,270 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012121: TransactionReaper::doCancellations worker Thread[Transaction Reaper Worker 0,5,main] successfully canceled TX 0:ffffc0a83569:

-6c981c1b:57cee045:5b

Attached you can find wildfly logs of a successful booting and a hang booting. Also, you can find our current standalone.xml configuration.

Logs are very different, also between successful bootings, but we noticed some things:

1) If we deploy only few number of web applications, Wildfly always boot (tested with 3 of them)

2) if we deploy all our set of web applications, Wildfly usually don't starts (tested with 17 of them). Of course we tried to deploy one application at a time (maybe a bugged one) but Wildfly always starts.

3) We tried to tune EJB cache in infinispan subsystem, with:

<file-store purge="true"/>

but didn't helps

4) We tried a performance tuning following that note: http://www.mastertheboss.com/jboss-server/jboss-performance/wildfly-performance-tuning .. still nothing

5) We changed JRE from 7 to jre8.101.. nothing

Do you have any idea about that problem?

Thanks in advance

Roberto