tomcat does not start

[Bluescreen]

tomcat does not work.
/etc/init.d/scalix-tomcat start
/etc/init.d/scalix-tomcat status

Code: Select all

Instance (server) is not running


less /var/opt/scalix/sr/tomcat/logs/catalina.2007-02-20.log

Code: Select all

SCHWERWIEGEND: Exception sending context initialized event to listener instance
of class com.oddpost.server.Config
java.lang.RuntimeException: INVALID WEB SERVER CONFIGURATION!
invalid version of activation.jar! Expected version 1.0.2, but was [1.6.0]
        at com.oddpost.util.GeneralUtils.checkJarVersion(GeneralUtils.java:293)
        at com.oddpost.server.Resource.checkJarVersions(Resource.java:637)
        at com.oddpost.server.Resource.init(Resource.java:60)
        at com.oddpost.server.Config.contextInitialized(Config.java:16)
        at org.apache.catalina.core.StandardContext.listenerStart(StandardContex
t.java:3729)
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:4
183)
        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase
.java:759)
        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:73
9)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)


[Bluescreen]

Idea?

[mito]

If you figure it out... let me know...

Every time I try to upgrade my production box, I get the same problem:
viewtopic.php?t=5926

I was trying to do the upgrade the same time as an OS changeover (From FC4 to CentOS 4.4) but have since just transfered to the new OS and stayed at Scalix 10. I think I am going to wait until the next patch is released (they said they hoped to have one out in March) before trying it again.

Let me know if you figure it out!

Mito

[les]

[quote="Bluescreen"]tomcat does not work.
/etc/init.d/scalix-tomcat start
/etc/init.d/scalix-tomcat status

Code: Select all

Instance (server) is not running


I found a bug for the status command recently, and it was just to do with reporting the pid of tomcat. In my case tomcat was actually running but the status command said it wasn't. It was all down to the number of characters in the pid...5 would work, 4 wouldn't.

Bug report with resolution here....http://bugzilla.scalix.com/show_bug.cgi?id=14659

You can check whether tomcat is running yourself by.....

cat /var/opt/scalix/XX/tomcat/tomcat.pid

replace XX with your directory name. That gives you "the pid" of tomcat.

Then

ps --pid "the pid"

should show you....
PID TTY TIME CMD
"the pid" ? 00:01:25 java

And you can see java is running.

Hope that helps.

[florian]

yup. and the status command script willl be fixed in 11.0.2 and we'll hopefully ship that next week.

Florian.