Bug#517832: jsvc: Tomcat5.5/s390 doesn't start with default JVM

[Michael Koch]

reassign 517832 gcj-4.4 4.4.1-1
thanks


Hello Guillaume,


On Mon, Mar 02, 2009 at 12:22:38PM +0000, Guillaume Lasmayous wrote:
> Package: jsvc
> Version: 1.0.2~svn20061127-9
> Severity: important
> 
> My Debian machine is installed as a guest of z/VM 5.4.
> I apt-get installed tomcat5.5, pulling in all required dependencies.
> At startup, tomcat5.5 fails with the following error in /var/log/daemon.log
> 
> Mar  2 09:22:04 debjava tomcat5.5: The java-gcj-compat-dev environment currently doesn't
> Mar  2 09:22:04 debjava tomcat5.5: support a security manager. See README.Debian.
> Mar  2 09:22:04 debjava jsvc.exec[6007]: Cannot dynamically link to /usr/lib/jvm/default-java/jre/lib/s390/client/libjvm.so
> Mar  2 09:22:04 debjava jsvc.exec[6007]: /usr/lib/libgcj.so.90: undefined symbol: __data_start
> 
> Using the script startup.sh in /usr/lib/tomcat5.5/bin, Tomcat5.5 starts successfully.
> 
> I did the same test on another machine using the IBM JDK 1.5 (31bits version) I downloaded from DW. It fails with a similar error:
> Feb 27 13:46:01 debian jsvc.exec[1040]: Cannot dynamically link to /usr/lib/j2sdk1.5-ibm/jre/bin/classic/libjvm.so

This is a problem in GCJ. A fix for this was lately commited to GCC trunk.
I'm nur sure if it was also backported to GCC/GCJ 4.4. I reassign the bug
to gcj-4.4 hereby to get this solved correctly.


Cheers,
Michael