Tomcat not starting

Question

Tomcat not starting

I am running MacOS X Server 10.4.3. In the admin server tool, I chose "Tomcat only" in the application server options. But when I start the service, JBoss starts instead of Tomcat, as can be seen in the boot.log file. But I don't get any error message.
Everything works when I start Tomcat by hand, with a "sudo ./startup.sh" in Tomcat/bin. So it looks like MacOS X Server is really not starting Tomcat.
Any idea how to fix this problem ? Thanks for any help.

Posted on Nov 4, 2005 10:56 AM

Reply

Answer 1

Nov 11, 2005 12:13 AM in response to Damien Guillaume

I am having the same problem. I even did a fresh install just in case it was a problem caused by an upgrade. I have done quite a bit of searching and have found no answer. It appears even with "Tomcat only" selected the Server Admin still launches Jboss with the local configuration. I have read all the documentation I could find and this appears to be a problem with the Server Admin and launchd. Has anyone been able to get this to work as it did in 10.3?

Reply

Answer 2

Dec 22, 2005 6:43 PM in response to Damien Guillaume

Since having upgraded from Panther (10.3) to Tiger (10.4), Tomcat has not been starting at system startup for me although it will start if I run
sudo SystemStarter start Tomcat
(I created my own SystemStarter item.) I also created a launchd item and it worked but only if I added a sleep statement to the end of startup.sh. I'm not sure if this problem is related but you could try adding a sleep statement to startup.sh. I am also going to try redirecting output from startup.sh to a file instead of the console. I'll let you know if anything works in case the problem is related.

G4 Tower Mac OS X (10.4)

Reply

Answer 3

Dec 22, 2005 8:07 PM in response to Bradley Ross

I resolved the problem with SystemStarter by setting the environmental variable JAVA_HOME (defined the shell variable and "export"ed it.) It would also be a good idea to insert a command in startup.sh that would add a line with the time and account name to a file so that you can see whether the program is actually being executed. It could be that startup.sh isn't being run but the other possibility is that it is being run but not running correctly.

G4 Tower Mac OS X (10.4.3)

Reply

Answer 4

Jan 12, 2006 2:47 AM in response to Damien Guillaume

Update 10.4.4 has not fixed the bug 😟
I use a custom launchd file in the meantime...

Reply

Answer 5

Apr 11, 2006 11:29 AM in response to Damien Guillaume

Upgraded to 10.4.6 and this still has not been fixed. I submitted a bug fix to Apple in November 2005 and have not received a reply. Anyone know anything about fixing this or a change you can make to use the Server Admin. I currently have a workaround but looking for a permanent fix to work with the Server Admin.

Reply