Bug#292448: tomcat4 & free java
ms419@freezone.co.uk, 292448@bugs.debian.org
ms419@freezone.co.uk, 292448@bugs.debian.org
Wed Apr 13 21:03:38 2005
On Apr 11, 2005, at 12:24 PM, ms419@freezone.co.uk wrote:
> what about using SableVM?
>
> It should work according to these instructions -
> http://sablevm.org/wiki/Tomcat - at least for Tomcat 5 - but I kept
> getting the same error -
>
> Finally, I got wise & set JAVA_HOME in /etc/default/tomcat4 to
> "/usr/lib/sablevm" - now I think I'm getting somewhere because I get a
> different error -
>
>
> Using CATALINA_BASE: /var/lib/tomcat4
> Using CATALINA_HOME: /usr/share/tomcat4
> Using CATALINA_TMPDIR: /var/lib/tomcat4/temp
> Using JAVA_HOME: /usr/lib/sablevm
> Warning: -Xmx128M option not implemented in java-sablevm wrapper.
> Created MBeanServer with ID: [UID: 96640864,1113245812731,-32768]:fis:1
> Starting service Tomcat-Standalone
> Apache Tomcat/4.1
> Catalina.start: LifecycleException: Context startup failed due to
> previous errors
> LifecycleException: Context startup failed due to previous errors
> at org.apache.catalina.core.StandardContext.start
> (StandardContext.java:3578)
> at org.apache.catalina.core.ContainerBase.start
> (ContainerBase.java:1141)
> at org.apache.catalina.core.StandardHost.start
> (StandardHost.java:707)
> at org.apache.catalina.core.ContainerBase.start
> (ContainerBase.java:1141)
> at org.apache.catalina.core.StandardEngine.start
> (StandardEngine.java:316)
> at org.apache.catalina.core.StandardService.start
> (StandardService.java:450)
> at org.apache.catalina.core.StandardServer.start
> (StandardServer.java:2143)
> at org.apache.catalina.startup.Catalina.start (Catalina.java:463)
> at org.apache.catalina.startup.Catalina.execute (Catalina.java:350)
> at org.apache.catalina.startup.Catalina.process (Catalina.java:129)
> at java.lang.reflect.Method.invokeNative (Method.java)
> at java.lang.reflect.Method.invoke (Method.java:616)
> at org.apache.catalina.startup.Bootstrap.main (Bootstrap.java:156)
> at java.lang.VirtualMachine.invokeMain (VirtualMachine.java)
> at java.lang.VirtualMachine.main (VirtualMachine.java:108)
> Stopping service Tomcat-Standalone
> Catalina.stop: LifecycleException: Coyote connector has not been
> started
> LifecycleException: Coyote connector has not been started
> at org.apache.coyote.tomcat4.CoyoteConnector.stop
> (CoyoteConnector.java:1296)
> at org.apache.catalina.core.StandardService.stop
> (StandardService.java:499)
> at org.apache.catalina.core.StandardServer.stop
> (StandardServer.java:2178)
> at org.apache.catalina.startup.Catalina.start (Catalina.java:494)
> at org.apache.catalina.startup.Catalina.execute (Catalina.java:350)
> at org.apache.catalina.startup.Catalina.process (Catalina.java:129)
> at java.lang.reflect.Method.invokeNative (Method.java)
> at java.lang.reflect.Method.invoke (Method.java:616)
> at org.apache.catalina.startup.Bootstrap.main (Bootstrap.java:156)
> at java.lang.VirtualMachine.invokeMain (VirtualMachine.java)
> at java.lang.VirtualMachine.main (VirtualMachine.java:108)
>
>
> Any help with this?
This most recent error was bug #292448 - after installing
tomcat4-webapps, tomcat4 starts perfectly with
JAVA_HOME=/usr/lib/sablevm
Resolving bug #292448 would be awesome - packages shouldn't fail to
start in the absence of other merely "suggested" packages.
Perhaps JDK_DIRS in /etc/init.d/tomcat4 should include /usr/lib/sablevm
- & perhaps /usr/lib/fjsdk - if it worked : )
Many thanks free java faithful!
Jack