JBoss EAP 6.1 stopping with errors

[evapizana]

Hi everyone...

I am running JBos EAP 6.1 G.A. as a Widows service.

Right now I only have one application deployed. I'm able to launch the app correctly. But after a while, when I come back to the app, JBoss is no longer running.

When opening the error log file I get this:

[14:27:22,597 ERROR [org.jboss.as.txn] (http-mex-lap-bcwin04/10.22.170.115:8080-9) JBAS010151: Unable to get transaction state: java.lang.IllegalStateException
 at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
 at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.checkTransactionStatus(TransactionRollbackSetupAction.java:112)
 at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.teardown(TransactionRollbackSetupAction.java:66)
 at org.jboss.as.web.ThreadSetupBindingListener.unbind(ThreadSetupBindingListener.java:61) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:184) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
 at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
 at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
 at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
 at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_11]


14:27:22,650 ERROR [org.apache.catalina.connector] (http-mex-lap-bcwin04/10.22.170.115:8080-9) JBWEB001018: An exception or error occurred in the container during the request processing: java.lang.RuntimeException: java.lang.IllegalStateException
 at org.jboss.as.web.ThreadSetupBindingListener.unbind(ThreadSetupBindingListener.java:67) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:184) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
 at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
 at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
 at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
 at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_11]
Caused by: java.lang.IllegalStateException
 at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
 at org.jboss.as.connector.deployers.ra.processors.CachedConnectionManagerSetupProcessor$CachedConnectionManagerSetupAction.teardown(CachedConnectionManagerSetupProcessor.java:105)
 at org.jboss.as.web.ThreadSetupBindingListener.unbind(ThreadSetupBindingListener.java:61) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
 ... 8 more


14:27:23,010 INFO  [org.apache.coyote.http11] (MSC service thread 1-4) JBWEB003075: Coyote HTTP/1.1 pausing on: http-mex-lap-bcwin04/10.22.170.115:8080
14:27:23,020 INFO  [org.apache.coyote.http11] (MSC service thread 1-4) JBWEB003077: Coyote HTTP/1.1 stopping on : http-mex-lap-bcwin04/10.22.170.115:8080
14:27:23,048 INFO  [org.jboss.as] (MSC service thread 1-5) JBAS015950: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) stopped in 20084ms

Can anyone tell me why this might be happening?

And what can I do to avoid it?

Thanks,

Eva

[sfcoy]

Please attach the entire server.log to the discussion so that we can see what is happening.

Just attach the file, don't copy and paste it or rar it.

[evapizana]

Thank you Stephen,

Here you can find the log file.
Not thet I removed a good piece of log that was thrown by my app...

Thanks,

Eva

[ctomc]

Hi,

from log there is nothing really obvious what is going on that would cause jboss to shutdown.

Errors that you see in log on shutdown have noting to do with it,

they happen becouse of dependancies between deployments are not beeing shutdown in proper order and some components are already undeployed while are still needed for others that are undeploying.

That bug was already fixed in WildFly 8 alpha1

In any case that has noting to do with why server would automaticly shutdown, it all seems like clean server stop.

Maybe windows service is shuting it down? what kind of service are you using? the scripts provided by EAP or some other solution?

are there any "wrapper" logs that say something? or is there something in windows event log?

--

tomaz

[evapizana]

Hi Tomaz,

I've recently experienced this:

- The windows service is still running, but JBoss is not. I've created my own solution to start JBoss as a service. I create a config file to be able to start it. (I'm attaching the config file)

- And I'm also attaching the log I got this time that the service is running but not JBoss.

Thanks,

Eva