Tomcat won't start automatically

Discuss installation of Scalix software

Moderators: ScalixSupport, admin

florian
Scalix
Scalix
Posts: 3852
Joined: Fri Dec 24, 2004 8:16 am
Location: Frankfurt, Germany
Contact:

Postby florian » Tue Jun 07, 2005 3:06 pm

BTW, I must add one remark....

for those who are still SuSE addicts - try to work yourself through the apache2 config file structure in SLES9 - I did integrate tomcat with Apache using the JK2 connector - had the hardest time ever to find which of the about 25 .conf files SuSE comes with is the best to change; will not post the full story here, but wasn't too much fun.

I wan't back my good old days of System V.3 simplicity....

-- F.
Florian von Kurnatowski, Die Harder!

DColeman
Posts: 19
Joined: Thu May 26, 2005 3:44 pm

Postby DColeman » Tue Jun 07, 2005 4:53 pm

Thanks for the info. I'm not too thrilled about reinstalling/reconfiguring from scratch and losing more days...

Here's a dumb question: Since Tomcat starts fine by manually running /opt/jakarta-tomcat-5.0.28/bin/startup.sh, isn't there just a way to simply "call" that startup.sh script when Linux starts?

For example, could I put a symbolic link in /etc/init.d to /opt/jakarta-tomcat-5.0.28/bin/startup.sh and then put symbolic links in the /etc/init.d/rcx.d subdirectories which "call" the symbolic link in /etc/init.d, which in turn "calls" /opt/jakarta-tomcat-5.0.28/bin/startup.sh?

This evaluation of Scalix is also our first attempt at implementing Linux, so I'm learning as I go...

DColeman
Posts: 19
Joined: Thu May 26, 2005 3:44 pm

Postby DColeman » Tue Jun 07, 2005 5:50 pm

Well I went ahead and tried my idea of using symbolic links and it seems to be working!

Can you think of any problems that this might create?

florian
Scalix
Scalix
Posts: 3852
Joined: Fri Dec 24, 2004 8:16 am
Location: Frankfurt, Germany
Contact:

Postby florian » Wed Jun 08, 2005 6:38 pm

The one thing that normally happens when you do this in the simplest possible way is that you lose some of your environment. When starting tomcat manually using startup.sh, tomcat inherits parts of "root"'s environment, including the PATH variable pointing to the Scalix directories. This is needed for SAC to function. If it is not set correctly, you are most likely to experience login failures with SAC, when then checking the caa.log file, you'll see error messages about commands not being found.

This can be fixed by putting in the PATH statement in the setclasspath.sh script, as per my previous comment.

Needless to say, standard installations like to have a "proper" start script that displays some things on startup and gives status information as well.

For an evaluation, everything that works in this area shoudl be fine...

Cheers,
Florian
Florian von Kurnatowski, Die Harder!

DColeman
Posts: 19
Joined: Thu May 26, 2005 3:44 pm

Postby DColeman » Thu Jun 09, 2005 3:26 pm

Thanks again for the input. We'll leave it like it is for the eval and install from scratch if we decide to purchase.


Return to “Installation”



Who is online

Users browsing this forum: No registered users and 6 guests