Re: Tomcat won't start with j2sdk 1.3.1 Linux
I have been using xerces with 1.3.1 albeit on WinNT and have no problems with it. You have to make sure in your tomcat.properties, wrapper.properties and tomcat.bat, you mention xerces.jar on the top where ever you configure the library files for example in tomcat.properties wrapper.classpath=c:\tomcat\lib\xerces.jar; wrapper.classpath= the xerces.jar needs to load up in the context first and everything should work Goodluck Kris --- pete [EMAIL PROTECTED] wrote: I get this. It sucks. The issue, for me at least, stems from the fact that i am running a Struts project, and i need to override the jaxp.jar classes with xerces parser classes. I previously did this by putting a jar named 0xerces.jar in the lib/ folder of my tomcat install, which worked fine, since those classes loaded before the ones specified in jaxp.jar. This worked great with IBM's JDK1.3.0 - never used Sun's 1.2.2 on Linux. However, since 'upgrading' to Sun's JDK1.3.1 with Hotspot, the JVM segfaults when tomcat starts up, giving the same error you describe. I'm not sure why this happens, but maybe 1.3.1 doesn't like having its classes overridden. There are 2 ways around this - invoke the JVM with the '-classic' switch, thus disabling the JIT, or to remove 0xerces.jar from lib/, which breaks my Struts projects. The third solution is not to use the JDK1.3.1 at all, and stick with the IBM JDK, which is my current course of action. Hope this helps, and i hope you find a better solution than i did. -Pete __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/
Re: Tomcat won't start with j2sdk 1.3.1 Linux
Switching to IBM's JDK 1.3 solved my problem of the HttpConnectionHandler not being able to start. Thank you! I was using Sun's JDK 1.3.0_02 and my problem arose when I upgraded to Sun's JDK1.3.1 Thanks again! - Original Message - From: pete [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, June 27, 2001 0:58 Subject: Re: Tomcat won't start with j2sdk 1.3.1 Linux I get this. It sucks. The issue, for me at least, stems from the fact that i am running a Struts project, and i need to override the jaxp.jar classes with xerces parser classes. I previously did this by putting a jar named 0xerces.jar in the lib/ folder of my tomcat install, which worked fine, since those classes loaded before the ones specified in jaxp.jar. This worked great with IBM's JDK1.3.0 - never used Sun's 1.2.2 on Linux. However, since 'upgrading' to Sun's JDK1.3.1 with Hotspot, the JVM segfaults when tomcat starts up, giving the same error you describe. I'm not sure why this happens, but maybe 1.3.1 doesn't like having its classes overridden. There are 2 ways around this - invoke the JVM with the '-classic' switch, thus disabling the JIT, or to remove 0xerces.jar from lib/, which breaks my Struts projects. The third solution is not to use the JDK1.3.1 at all, and stick with the IBM JDK, which is my current course of action. Hope this helps, and i hope you find a better solution than i did. -Pete
Re: Tomcat won't start with j2sdk 1.3.1 Linux
We've been using Sun's JDK 1.3.1 on Linux for a while now. Currently we use Tomcat 3.2.1 and xerces version 1.3.0. It seemed to work fine on RedHat 6.1 but on 7.1 there was a link that missing. I think I experienced the same seg fault issue that is referred to below. If this is the problem it can be fixed by doing the following as root: cd /lib/i686 The required link is libpthread.so. If it isn't there then create it: ln -s libpthread.so.0 libpthread.so Then run: /sbin/ldconfig This fixed the problem with regards to running 1.3.1 on RedHat Linux 7.1. Hope this helps. P. On Wed, 27 Jun 2001 11:33:37 -0400 Jeffrey Lam [EMAIL PROTECTED] wrote: JL Switching to IBM's JDK 1.3 solved my problem of the HttpConnectionHandler not JL being able to start. Thank you! JL JL I was using Sun's JDK 1.3.0_02 and my problem arose when I upgraded to Sun's JL JDK1.3.1 JL JL Thanks again! JL JL - Original Message - JL From: pete [EMAIL PROTECTED] JL To: [EMAIL PROTECTED] JL Cc: [EMAIL PROTECTED] JL Sent: Wednesday, June 27, 2001 0:58 JL Subject: Re: Tomcat won't start with j2sdk 1.3.1 Linux JL JL JL I get this. It sucks. JL JL The issue, for me at least, stems from the fact that i am running a JL Struts project, and i need to override the jaxp.jar classes with xerces JL parser classes. JL JL I previously did this by putting a jar named 0xerces.jar in the lib/ JL folder of my tomcat install, which worked fine, since those classes JL loaded before the ones specified in jaxp.jar. JL JL This worked great with IBM's JDK1.3.0 - never used Sun's 1.2.2 on Linux. JL JL However, since 'upgrading' to Sun's JDK1.3.1 with Hotspot, the JVM JL segfaults when tomcat starts up, giving the same error you describe. JL JL I'm not sure why this happens, but maybe 1.3.1 doesn't like having its JL classes overridden. JL JL There are 2 ways around this - invoke the JVM with the '-classic' JL switch, thus disabling the JIT, or to remove 0xerces.jar from lib/, JL which breaks my Struts projects. JL JL The third solution is not to use the JDK1.3.1 at all, and stick with the JL IBM JDK, which is my current course of action. JL JL Hope this helps, and i hope you find a better solution than i did. JL JL -Pete JL JL JL JL
Re: Tomcat won't start with j2sdk 1.3.1 Linux
Krishna Muthyala wrote: Yep, on WinNT this works fine. However, it has been a long time since i have used WinNT for anything on my servers, and i'm not about to go back there anytime soon. This issue is JVM-related, not classpath etc. anyway, since the JVM should not segfault, no matter which java classes (all compiled with JDK1.3.1 from source, no less) it tries to load. I have been using xerces with 1.3.1 albeit on WinNT and have no problems with it. You have to make sure in your tomcat.properties, wrapper.properties and tomcat.bat, you mention xerces.jar on the top where ever you configure the library files for example in tomcat.properties wrapper.classpath=c:\tomcat\lib\xerces.jar; wrapper.classpath= the xerces.jar needs to load up in the context first and everything should work Goodluck Kris --- pete [EMAIL PROTECTED] wrote: I get this. It sucks. The issue, for me at least, stems from the fact that i am running a Struts project, and i need to override the jaxp.jar classes with xerces parser classes. I previously did this by putting a jar named 0xerces.jar in the lib/ folder of my tomcat install, which worked fine, since those classes loaded before the ones specified in jaxp.jar. This worked great with IBM's JDK1.3.0 - never used Sun's 1.2.2 on Linux. However, since 'upgrading' to Sun's JDK1.3.1 with Hotspot, the JVM segfaults when tomcat starts up, giving the same error you describe. I'm not sure why this happens, but maybe 1.3.1 doesn't like having its classes overridden. There are 2 ways around this - invoke the JVM with the '-classic' switch, thus disabling the JIT, or to remove 0xerces.jar from lib/, which breaks my Struts projects. The third solution is not to use the JDK1.3.1 at all, and stick with the IBM JDK, which is my current course of action. Hope this helps, and i hope you find a better solution than i did. -Pete __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/
Re: Tomcat won't start with j2sdk 1.3.1 Linux
Tried that, no go. The odd thing is that JDK 1.3.1 will work quite happily without 0xerces.jar in the tomcat /lib folder. When i remove it, tomcat starts up normally. when i put it in, segfault. I added the symlink to /lib (I use Mandrake 8, not RH 7.1 so no i686 folder) and re-ran ldconfig. Same behaviour. This looks to be a bug with the Linux JDK1.3.1 -Pete We've been using Sun's JDK 1.3.1 on Linux for a while now. Currently we use Tomcat 3.2.1 and xerces version 1.3.0. It seemed to work fine on RedHat 6.1 but on 7.1 there was a link that missing. I think I experienced the same seg fault issue that is referred to below. If this is the problem it can be fixed by doing the following as root: cd /lib/i686 The required link is libpthread.so. If it isn't there then create it: ln -s libpthread.so.0 libpthread.so Then run: /sbin/ldconfig This fixed the problem with regards to running 1.3.1 on RedHat Linux 7.1. Hope this helps. P. On Wed, 27 Jun 2001 11:33:37 -0400 Jeffrey Lam [EMAIL PROTECTED] wrote: JL Switching to IBM's JDK 1.3 solved my problem of the HttpConnectionHandler not JL being able to start. Thank you! JL JL I was using Sun's JDK 1.3.0_02 and my problem arose when I upgraded to Sun's JL JDK1.3.1 JL JL Thanks again! JL JL - Original Message - JL From: pete [EMAIL PROTECTED] JL To: [EMAIL PROTECTED] JL Cc: [EMAIL PROTECTED] JL Sent: Wednesday, June 27, 2001 0:58 JL Subject: Re: Tomcat won't start with j2sdk 1.3.1 Linux JL JL JL I get this. It sucks. JL JL The issue, for me at least, stems from the fact that i am running a JL Struts project, and i need to override the jaxp.jar classes with xerces JL parser classes. JL JL I previously did this by putting a jar named 0xerces.jar in the lib/ JL folder of my tomcat install, which worked fine, since those classes JL loaded before the ones specified in jaxp.jar. JL JL This worked great with IBM's JDK1.3.0 - never used Sun's 1.2.2 on Linux. JL JL However, since 'upgrading' to Sun's JDK1.3.1 with Hotspot, the JVM JL segfaults when tomcat starts up, giving the same error you describe. JL JL I'm not sure why this happens, but maybe 1.3.1 doesn't like having its JL classes overridden. JL JL There are 2 ways around this - invoke the JVM with the '-classic' JL switch, thus disabling the JIT, or to remove 0xerces.jar from lib/, JL which breaks my Struts projects. JL JL The third solution is not to use the JDK1.3.1 at all, and stick with the JL IBM JDK, which is my current course of action. JL JL Hope this helps, and i hope you find a better solution than i did. JL JL -Pete JL JL JL JL
Re: Tomcat won't start with j2sdk 1.3.1 Linux
I get this. It sucks. The issue, for me at least, stems from the fact that i am running a Struts project, and i need to override the jaxp.jar classes with xerces parser classes. I previously did this by putting a jar named 0xerces.jar in the lib/ folder of my tomcat install, which worked fine, since those classes loaded before the ones specified in jaxp.jar. This worked great with IBM's JDK1.3.0 - never used Sun's 1.2.2 on Linux. However, since 'upgrading' to Sun's JDK1.3.1 with Hotspot, the JVM segfaults when tomcat starts up, giving the same error you describe. I'm not sure why this happens, but maybe 1.3.1 doesn't like having its classes overridden. There are 2 ways around this - invoke the JVM with the '-classic' switch, thus disabling the JIT, or to remove 0xerces.jar from lib/, which breaks my Struts projects. The third solution is not to use the JDK1.3.1 at all, and stick with the IBM JDK, which is my current course of action. Hope this helps, and i hope you find a better solution than i did. -Pete
Re: Tomcat won't start with j2sdk 1.3.1 Linux
Should I take the complete lack of any feedback on this subject to mean that no one
has tried Tomcat/Linux/j2sdk 1.3.1?
--- Forwarded message from Douglas E. Hornig ---
Date: 15 Jun 2001 12:45:17 EDT
From: Douglas E. Hornig
Subject: Tomcat won't start with j2sdk 1.3.1 Linux
To: [EMAIL PROTECTED]
Has anyone run Tomcat under linux with j2sdk 1.3.1-b24? I have been using Tomcat
3.2.1 (and now 3.2.2) happily for some time now with j2sdk 1.3 and linux (SuSE 7.1,
kernel 2.4.5). I decided to get current with my Java VM, but when I try to start up
Tomcat I get this error:
/usr/local/tomcat/bin/tomcat.sh: line 180: 20646 Segmentation fault $JAVACMD
$TOMCAT_OPTS -Dtomcat.home=${TOMCAT_HOME} org.apache.tomcat.startup.Tomcat $@
The only difference is the new Java SDK. Other Java applications run successfully
with the new SDK. I also have Tomcat 3.2.2/j2sdk 1.3.1-b24 running fine under Solaris
8.
Any ideas?
Thanks,
Douglas Hornig
Dartmouth-Hitchcock Medical Center
Tomcat won't start with j2sdk 1.3.1 Linux
Has anyone run Tomcat under linux with j2sdk 1.3.1-b24? I have been using Tomcat
3.2.1 (and now 3.2.2) happily for some time now with j2sdk 1.3 and linux (SuSE 7.1,
kernel 2.4.5). I decided to get current with my Java VM, but when I try to start up
Tomcat I get this error:
/usr/local/tomcat/bin/tomcat.sh: line 180: 20646 Segmentation fault $JAVACMD
$TOMCAT_OPTS -Dtomcat.home=${TOMCAT_HOME} org.apache.tomcat.startup.Tomcat $@
The only difference is the new Java SDK. Other Java applications run successfully
with the new SDK. I also have Tomcat 3.2.2/j2sdk 1.3.1-b24 running fine under Solaris
8.
Any ideas?
Thanks,
Douglas Hornig
Dartmouth-Hitchcock Medical Center
