Solaris

Hmm, could be a problem with the owner and access mode of files. You started tomcat as root earlier, so the logfiles are most likely owner by root, especially catalina.out in /usr/local/tomcat5/logs.

Are there any scripts that you can find in the /etc/rc.* directories?

you need to update your PATH so that you can find the correct version of java.

Now, my path is already set ok.

Code:

echo $PATH
/usr/sbin:/usr/bin:/usr/jdk/instances/jdk1.6.0/bin:/bin:/usr/local/tomcat5/bin:/usr/sfw/bin:/usr/ccs/bin

---------- Post updated at 11:23 PM ---------- Previous update was at 10:44 PM ----------

I find another application startup script at /etc/rc3.d. That application uses old java jre and iPlanet web server.




---------- Post updated 02-09-10 at 12:11 AM ---------- Previous update was 02-08-10 at 11:23 PM ----------

Thanks for your advice. I've changed all permission to the new user a/c under tomcat5 folder already. Not sure why tomcat cannot startup after exported the JAVA_HOME, PATH, JDK paths.



---------- Post updated at 03:02 AM ---------- Previous update was at 12:11 AM ----------

I could startup tomcat & jdk properly now.
And new port is set in server.xml (since 8080 is used by other appl.) But the page could not be displayed in The UNIX and Linux Forums - Learn UNIX and Linux from Experts

Hi

This works for me on XP Home SP2.

That it fails for you on some machines and works on others points to a
configuration issue with those machines (maybe the Java 6 install?) rather than
a Tomcat issue or an issue with the service wrapper.

The tomcat users list is the best place to get further help with this issue.

Or you can try this.

If you Google a little or browse tomcat-user mailing list you'll discover that
I'm not the only one to experience this very same problem. It is for sure a
configuration-related issue, but the fact that it involves only Tomcat and only
on jdk 1.6 (with jdk 1.5 it works fine on the same machine) and that at least a
few people who are long-time Tomcat users have not been able so far to fix it,
should suggest to keep the bug open and investigate further. Bear in mind that
not many people have started using jdk 1.6, and those who are may be using
Tomcat 6, so it may end up that many more cases show up in the next weeks.

Thanks

Hannan Saleemi