JBOSS SHUTTING DOWN

[reji_mathai]

Hi Guys,

I am facing a peculiar problem.
My JBOSS application server just shuts down sometimes.

In fact it performs a smooth shutdown.

It has been hosted on Linux machine with about 256 MB RAM.
We have deployed a couple of Message driven beans and an equal number of topics in the server.

The log file just shows the follwing..


[Default] Shutting down
[Service Control] Stopping 48 MBeans
[MailService] Stopping
[MailService] Mail service 'Mail' removed from JNDI
[MailService] Stopped
[RMIConnectorService] Stopping
[RMIConnectorService] Stopped
[JMXAdaptorService] Stopping
[JMXAdaptorService] Stopped
[AutoDeployer] Stopping
[AutoDeployer] Stopped
[JmsXA] Stopping
[JmsXA] org.jboss.pool.connector.jboss.MinervaXACM shut down.
[JmsXA] Connection factory 'JmsXA' shut down.
[JmsXA] Stopped
[MinervaDS] Stopping
[MinervaDS] org.jboss.pool.connector.jboss.MinervaSharedLocalCM shut down.
[MinervaDS] Connection factory 'MinervaDS' shut down.
[MinervaDS] Stopped
[MinervaXACMFactory] Stopping
[MinervaXACMFactory] Connection manager factory 'MinervaXACMFactory' removed from JNDI
[MinervaXACMFactory] Stopped
[MinervaSharedLocalCMFactory] Stopping
[MinervaSharedLocalCMFactory] Connection manager factory 'MinervaSharedLocalCMFactory' removed fro
m JNDI
[MinervaSharedLocalCMFactory] Stopped

.
.
.
.
.
.
.
.
.
.
StateManager] Destroyed
[JBossMQService] Destroying
[JBossMQService] Destroyed
[EmbeddedTomcatServiceSX] Destroying
[EmbeddedTomcatServiceSX] Destroyed
[ContainerFactory] Destroying
[ContainerFactory] Destroyed
[ServerDataCollector] Destroying
[ServerDataCollector] Destroyed
[XADataSourceLoader] Destroying
[XADataSourceLoader] Destroyed
[JdbcProvider] Destroying
[JdbcProvider] Destroyed
[JaasSecurityManagerService] Destroying
[JaasSecurityManagerService] Destroyed
[ClientUserTransactionService] Destroying
[ClientUserTransactionService] Destroyed
[TransactionManagerService] Destroying
[TransactionManagerService] Destroyed
[JNDIView] Destroying
[JNDIView] Destroyed
[NamingService] Destroying
[NamingService] Destroyed
[WebService] Destroying
[WebService] Destroyed
[Service Control] Destroyed 48 services
[Default] Shutdown complete



Has anybody encountered this before ?


Regards
Reji

[anne-claire]

Hello!

We have the same problem with JMS. It stops properly but without apparent reason and we have no warning or error in the logs generated.
Our OS is Solaris 8, we are using JDK 1.3.1 and Jboss 2.2.1. And what about you?


AC

[jlar310]

I'm having the same problem on Solaris 7/JDK 1.3.1/Jboss 2.4.4. I've noticed that when this happens, it shuts down
almost exactly 60 seconds after startup. If I make it past that point, it stays up indefinitely.

Any insight into this problem would be greatly appreciated.

Jeff

[mdagosta]

I have a similar problem too.

When the machine boots, it starts JBoss no problem. Then JBoss spontaneously turns itself off. I don't get it either.

Mike

[mdagosta]

I am having a similar problem on machine bootup.

JBoss will start, then suddently shutdown without reason.

When I start JBoss by hand, I never have problems. This o happens only when the machine is booting and starts JBoss.

Mike

[mdagosta]

I am having a similar problem on machine bootup.

JBoss will start, then suddently shutdown without reason.

When I start JBoss by hand, I never have problems. This o happens only when the machine is booting and starts JBoss.

Mike

[joelvogt]

Hmmm.. okay just out of interest, what method are you using to start jboss. ie, init.d script or manually?

[gwoodward]

I am having a similar problem; JBoss will stop after 15 minutes to an hour of operation, for no apparent reason. It actually goes through a clean shutdown, according to the logs. I am using JBoss 3.0.0 on Linux with JDK 1.4. Thanks for any help you may be able to provide.

Regards,
Greg

[sulik]

Has anyone found a fix for this problem?

We're running into it as well.

Jboss 2.4.4/tomcat 3.2.3/HP-UX 11i/HP JVM 1.3.1-05
Jboss 2.4.4/tomcat 3.2.3/Solaris 8/Sun JVM 1.3.1-01

Can't seem to narrow down the "why" -- think it may be something to do with system resources, but just guessing.

Suggestions? Ideas? Solutions?

Lori

[mikefinn]

Not to state the obvious, but has anyone tried turning the logging detail up - say to DEBUG for org.jboss category, to get add'l stuff from the log?

It's worth a shot.

Mike

[adrian.brock]

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/jboss-system/src/main/org/jboss/system/server/ServerImpl.java.diff?r1=1.16.2.3&r2=1.16.2.4

Regards,
Adrian

[sulik]

Hello folks,

I do believe I've found the problem...

Search your config files for the following 2 port numbers:

8007 --> the ajp12 default port
8009 --> the ajp13 default port

By default, those 2 ports are used as the ajp ports, AKA the "tomcat shutdown port" according to the comments!

Sooo, looks like when you tell jboss to shutdown, somehow or other that port is being used to alert tomcat to shut down.

Which is fine if you're the only instance running on the box. However, if multiple instances of tomcat are running (or mult of the jboss/tomcat combo), then when the 2nd environment shuts down, it send a shutdown command to the first unknowingly, which shuts IT down too..

Find & grep for port 8007 and 8009, change them to 2 unused ports, and this problem should go away.

I have been able to reproduce this problem at will. And, fixed it by reassigning those default ports.

For JBoss 2.4.4/tomcat 3.2.3, there's 5 files to edit:
tomcat/conf/server.xml
tomcat/conf/tomcat.conf
tomcat/conf/tomcat.properties
tomcat/conf/workers.properties
tomcat/conf/wrapper.properties

May be more or less files, in older/new combinations of jboss/tomcat :)

Lori