Does anyone have suggestions or ideas for this problem? I am only =20
able to run Tomcat (kaffe) on 2.6.16.x and prior UML kernels.
I have downgraded the host to 22.214.171.124-skas3-v8.2 but the problem =20
with 2.6.17 UML kernels still persists. I just tried upgrading the =20
guest to a stock 126.96.36.199 kernel without success.
I would really like to eventually upgrade my guest kernels beyond =20
2.6.26.x. However, this issues with Tomcat is a show stopper. Any =20
ideas or suggestions?
Quoting Anthony Brock <brocka@...>:
> I'm running Tomcat5 on a virtual server instance. I just tried to upgrade
> the UML kernel (and guest) to a 188.8.131.52 version. Previously the host was
> running 184.108.40.206-skas3-v8.2 and the guest was running 2.6.17-rc6. Both hos=
> and guest are Debian Etch distributions.
> However, with the host running 220.127.116.11-skas3-v9-pre9 and the guest runnin=
> a stock 18.104.22.168, I'm now experiencing a problem with Tomcat on startup.
> Unfortunately, I don't have enough knowledge of Tomcat to get more detail,
> but the following appears in the /var/log/tomcat5/catalina_2006-07-14.log
> Using CATALINA_BASE: /var/lib/tomcat5
> Using CATALINA_HOME: /usr/share/tomcat5
> Using CATALINA_TMPDIR: /var/lib/tomcat5/temp
> Using JAVA_HOME: /usr/lib/kaffe
> Using Security Manager
> Internal error: caught an unexpected exception.
> Please check your CLASSPATH and your installation.
> However, reversing the guest kernel back to 2.6.17-rc6 allows the Tomcat
> server to start normally (leaving the host at 22.214.171.124-skas3-v9-pre9).
> I haven't seen anything specific to Tomcat cross the list recently. Howeve=
> is there a known bug in the stock 126.96.36.199 kernel that would cause this
> behavior? Any suggestions on how to get more detailed information on the
> I originally attached a copy of the relevant config files for all 4 kernel=
> However, the message was moderated due to size. Please contact me if you
> would like copies of the configuration files for the different kernels.
> Also, it's worth noting that the configuration for both guest kernels are
> Any suggestions or advice is appreciated!