[Installation, Configuration & Deployment] - JBoss automatic shutdown during boot
by scottlance
We are currently setting up JBoss 4.0.3SP1 for deployment. We are using RedHat 3.4.6-2. We are trying to setup JBoss so that it will automatically start during boot time, we've modified the jboss_init_redhat.sh and placed it in /etc/rc.d/init.d and did chkconfig and the whole deal.
When we reboot the machine, the service will only come up 50-75% of the time, the remainder it seems to come up and then automatically shutdown (see log below). This seems to happen about 30 seconds after JBoss has finsihed starting up. The next message is:
[org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread] Notified to shutdown
Has anyone seen this issue before? I've scoured the net and the forums looking for a solution and have yet to find one.
2006-08-02 11:56:11,249 DEBUG [org.jboss.deployment.MainDeployer] End deployment start on package: jboss-service.xml
2006-08-02 11:56:11,249 DEBUG [org.jboss.deployment.MainDeployer] Deployed package: file:/usr/jboss/jboss-4.0.3SP1/server/default/conf/jboss-service.xml
2006-08-02 11:56:11,252 DEBUG [org.jboss.web.tomcat.tc5.Tomcat5] Saw org.jboss.system.server.started notification, starting connectors
2006-08-02 11:56:11,293 INFO [org.apache.coyote.http11.Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-80
2006-08-02 11:56:11,904 INFO [org.apache.jk.common.ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
2006-08-02 11:56:11,922 INFO [org.apache.jk.server.JkMain] Jk running ID=0 time=0/48 config=null
2006-08-02 11:56:11,937 INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.0.3SP1 (build: CVSTag=JBoss_4_0_3_SP1 date=200510231054)] Started in 53s:631ms
2006-08-02 11:56:46,605 DEBUG
[org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread] Notified to shutdown
2006-08-02 11:56:46,606 INFO [org.jboss.system.server.Server] Runtime shutdown hook called, forceHalt: true
2006-08-02 11:56:46,607 INFO [org.jboss.system.server.Server] JBoss SHUTDOWN: Undeploying all packages
2006-08-02 11:56:46,608 DEBUG [org.jboss.deployment.MainDeployer] Undeploying file:/usr/jboss/jboss-4.0.3SP1/server/default/deploy/jmx-console.war/
2006-08-02 11:56:46,609 DEBUG [org.jboss.system.ServiceController] stopping service: jboss.web.deployment:war=jmx-console.war,id=-801867523
2006-08-02 11:56:46,609 DEBUG [org.jboss.system.ServiceController] stopping dependent services for: jboss.web.deployment:war=jmx-console.war,id=-801867523 dependent services are: []
2006-08-02 11:56:46,610 DEBUG [org.jboss.web.WebModule] Stopping jboss.web.deployment:war=jmx-console.war,id=-801867523
2006-08-02 11:56:46,610 INFO [org.jboss.web.tomcat.tc5.TomcatDeployer] undeploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
2006-08-02 11:56:46,636 DEBUG [org.jboss.web.WebModule] Stopped jboss.web.deployment:war=jmx-console.war,id=-801867523
2006-08-02 11:56:46,637 DEBUG [org.jboss.webservice.ServiceDeployer] handleNotification: org.jboss.deployment.SubDeployer.stop,jmx-console.war
2006-08-02 11:56:46,638 DEBUG [org.jboss.system.ServiceController] destroying service: jboss.web.deployment:war=jmx-console.war,id=-801867523
2006-08-02 11:56:46,638 DEBUG [org.jboss.system.ServiceController] destroying dependent services for: jboss.web.deployment:war=jmx-console.war,id=-801867523 dependent services are: []
2006-08-02 11:56:46,639 DEBUG [org.jboss.web.WebModule] Destroying jboss.web.deployment:war=jmx-console.war,id=-801867523
2006-08-02 11:56:46,639 DEBUG [org.jboss.web.WebModule] Destroyed jboss.web.deployment:war=jmx-console.war,id=-801867523
2006-08-02 11:56:46,640 DEBUG [org.jboss.system.ServiceController] removing service: jboss.web.deployment:war=jmx-console.war,id=-801867523
2006-08-02 11:56:46,640 DEBUG [org.jboss.system.ServiceController] removing already unregistered jboss.web.deployment:war=jmx-console.war,id=-801867523 from server
2006-08-02 11:56:46,640 DEBUG [org.jboss.webservice.ServiceDeployer] handleNotification: org.jboss.deployment.SubDeployer.destroy,jmx-console.war
2006-08-02 11:56:46,645 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] Unregistering cl=org.jboss.mx.loading.UnifiedClassLoader3@128340{ url=file:/usr/jboss/jboss-4.0.3SP1/server/default/deploy/jmx-console.war/ ,addedOrder=40}
2006-08-02 11:56:46,646 DEBUG [org.jboss.mx.loading.UnifiedLoaderRepository3] UnifiedLoaderRepository removed(true) org.jboss.mx.loading.UnifiedClassLoader3@128340{ url=file:/usr/jboss/jboss-4.0.3SP1/server/default/deploy/jmx-console.war/ ,addedOrder=40}
Thanks,
Scott Lance
Interchange Corp.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962642#3962642
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3962642
19 years, 9 months
[JBoss jBPM] - Re: monitoring piece of default webapp not displaying the co
by unome
anonymous wrote :
| Question: Do you save the PI after signalling it to go into the fork? I assume you do, but just want to be sure.
|
| Earlier I was not. Shame on me. I had a "State" node earlier. To make things easy I changed it to a Task-node and let the webapp handle the save (using the "Save and Close Task"). The "Save and Close task" propagates the execution into the fork, etc.
|
| Still, same behavior.
|
| I should have tried this earlier, but I'm next going to really simplify the process defn to just a start state, node and end state. Have an action handler on the node which posts a message (with the token id) on a JMS queue, have an MDB listening on this queue which will do some processing and then signal the token using the token id that it picked up. Deploy the par with the default webapp and go from there.
|
| If you or anyone come across something stupid that I've been doing, please point it out. Always appreciate it.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962636#3962636
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3962636
19 years, 9 months