Tomcat on linux : IBM JDK 1.3.1 -

[Asif Chowdhary]

Hi,

I am installing tomcat on RH9. 
Tomcat version is 4.1.27 and the file is jakarta-tomcat-4.1.27.tar.gz

The installation works with JDK 1.4

but tomcat does not start when I try to use JDK 1.3.1
The browser returns the message Unable to connect to localhost with
http://localhost:8080/.


Any suggestions.


Asif 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat on linux : IBM JDK 1.3.1 -

[Shapira, Yoav]

Hi,

but tomcat does not start when I try to use JDK 1.3.1
The browser returns the message Unable to connect to localhost with
http://localhost:8080/.

What do the logs say?

Yoav Shapira



This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tomcat on linux : IBM JDK 1.3.1 -

[Chong Yu Meng]

Asif Chowdhary wrote:

Hi,

I am installing tomcat on RH9. 
Tomcat version is 4.1.27 and the file is jakarta-tomcat-4.1.27.tar.gz

The installation works with JDK 1.4

but tomcat does not start when I try to use JDK 1.3.1
The browser returns the message Unable to connect to localhost with
http://localhost:8080/.
Any suggestions.

 

You will need Java 1.4.1, or else disable NPTL for RH9 and Fedora Core 
1, or you will get seg faults. I've written 2 docs, one for IBM Java and 
one for Tomcat 4/5, and posted it on my website (see signature below).

--
We must respect the other fellow's religion, but only in the sense and
to the extent that we respect his theory that his wife is beautiful and
his children are smart. 
	-- Henry Mencken
++
| Pascal Chong   |
| email: [EMAIL PROTECTED]  |
||
| Please visit my site at : http://cymulacrum.net|
| If you're using my documentation, please read the Terms and|
| and Conditions at http://cymulacrum.net/terms.html |
++



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat on linux : IBM JDK 1.3.1 -

[Asif Chowdhary]

Nothing gets written to the log file.
Catalina.out is created and the process seems to start
when I issue the grep command.



-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 10, 2004 11:51 AM
To: Tomcat Users List
Subject: RE: Tomcat on linux : IBM JDK 1.3.1 - 



Hi,

but tomcat does not start when I try to use JDK 1.3.1
The browser returns the message Unable to connect to localhost with
http://localhost:8080/.

What do the logs say?

Yoav Shapira



This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat on linux : IBM JDK 1.3.1 -

[Lerias, Hugo]

Are you trying to use IBM jdk 1.3 on red hat 9?

Hugo

-Original Message-
From: Asif Chowdhary [mailto:[EMAIL PROTECTED] 
Sent: Mittwoch, 10. März 2004 17:42
To: [EMAIL PROTECTED]
Subject: Tomcat on linux : IBM JDK 1.3.1 - 


Hi,

I am installing tomcat on RH9. 
Tomcat version is 4.1.27 and the file is jakarta-tomcat-4.1.27.tar.gz

The installation works with JDK 1.4

but tomcat does not start when I try to use JDK 1.3.1
The browser returns the message Unable to connect to localhost with 
http://localhost:8080/.


Any suggestions.


Asif 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat on linux : IBM JDK 1.3.1 -

[Lerias, Hugo]

Take a look at this post:
http://www.linux-sxs.org/programming/ibm-java.html#APPENDIX_A

Cheers,
Hugo

-Original Message-
From: Lerias, Hugo 
Sent: Mittwoch, 10. März 2004 17:55
To: 'Tomcat Users List'
Subject: RE: Tomcat on linux : IBM JDK 1.3.1 - 


Are you trying to use IBM jdk 1.3 on red hat 9?

Hugo

-Original Message-
From: Asif Chowdhary [mailto:[EMAIL PROTECTED] 
Sent: Mittwoch, 10. März 2004 17:42
To: [EMAIL PROTECTED]
Subject: Tomcat on linux : IBM JDK 1.3.1 - 


Hi,

I am installing tomcat on RH9. 
Tomcat version is 4.1.27 and the file is jakarta-tomcat-4.1.27.tar.gz

The installation works with JDK 1.4

but tomcat does not start when I try to use JDK 1.3.1
The browser returns the message Unable to connect to localhost with 
http://localhost:8080/.


Any suggestions.


Asif 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat on linux : IBM JDK 1.3.1 -

[Shapira, Yoav]

Hi,

Nothing gets written to the log file.
Catalina.out is created and the process seems to start
when I issue the grep command.

Are the tomcat ports bound?

You may wish to set debug=99 on the various containers in server.xml
to maybe get more debugging information.

Yoav Shapira



This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat on linux : IBM JDK 1.3.1 -

[Asif Chowdhary]

Thank you.

setting the LD_ASSUME_KERNEL=2.2.5 in the user profile works.


-Original Message-
From: Lerias, Hugo [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 10, 2004 11:57 AM
To: Lerias, Hugo; Tomcat Users List
Subject: RE: Tomcat on linux : IBM JDK 1.3.1 - 


Take a look at this post:
http://www.linux-sxs.org/programming/ibm-java.html#APPENDIX_A

Cheers,
Hugo

-Original Message-
From: Lerias, Hugo 
Sent: Mittwoch, 10. März 2004 17:55
To: 'Tomcat Users List'
Subject: RE: Tomcat on linux : IBM JDK 1.3.1 - 


Are you trying to use IBM jdk 1.3 on red hat 9?

Hugo

-Original Message-
From: Asif Chowdhary [mailto:[EMAIL PROTECTED] 
Sent: Mittwoch, 10. März 2004 17:42
To: [EMAIL PROTECTED]
Subject: Tomcat on linux : IBM JDK 1.3.1 - 


Hi,

I am installing tomcat on RH9. 
Tomcat version is 4.1.27 and the file is jakarta-tomcat-4.1.27.tar.gz

The installation works with JDK 1.4

but tomcat does not start when I try to use JDK 1.3.1
The browser returns the message Unable to connect to localhost with 
http://localhost:8080/.


Any suggestions.


Asif 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

src/jakarta-tomcat-connectors/util/build.xml bug with IBM jdk 1.4

[Gianluca Toso]

Problem build tomcat 5.0.16 with IBMJava2-SDK 1.4.1 on intel.
ant from src abort on src/jakarta-tomcat-connectors/util/build.xml, so I
have tried ant from this dir:

[EMAIL PROTECTED]:~/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/
util=ant   
Buildfile: build.xml

detect:

build-prepare:
[mkdir] Created dir:
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/build
[mkdir] Created dir:
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/build/classes
[mkdir] Created dir:
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/build/lib

build-main:
 [echo] - Java-utils -
 [echo] -- puretls.present = ${puretls.present}
 [echo] -- jsse.present = true /usr/share/java/jsse-1.0.3/lib/jsse.jar
 [echo] -- commons-logging = true
 [echo] -- jmx = true /usr/share/java/mx4j-1.1.1/lib/mx4j-jmx.jar
 [echo] -- modeler = ${modeler.present}
/usr/share/java/commons-modeler-1.1M1/commons-modeler.jar
 [echo] -- JDK14 = true
[javac] Compiling 71 source files to
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/build/classes
[javac]
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/java/org/apache/tomcat/util/net/jsse/JSSE13SocketFactory.java:105: cannot
resolve symbol
[javac] symbol  : class Sun 
[javac] location: package provider
[javac] Security.addProvider (new
sun.security.provider.Sun());
[javac]^
[javac]
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/java/org/apache/tomcat/util/net/jsse/JSSE13SocketFactory.java:106: package
com.sun.net.ssl.internal.ssl does not exist
[javac] Security.addProvider (new
com.sun.net.ssl.internal.ssl.Provider());
[javac] 
 ^

[...]

[javac] Note:
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/java/org/apache/tomcat/util/threads/ThreadPool.java uses or overrides a
deprecated API.
[javac] Note: Recompile with -deprecation for details.
[javac] 9 errors

BUILD FAILED
file:/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors
/util/build.xml:67: Compile failed; see the compiler error output for
details.

Total time: 10 seconds

A second attempt (without a clean) fail too:
[EMAIL PROTECTED]:~/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/
util=ant
Buildfile: build.xml

detect:

build-prepare:

build-main:
 [echo] - Java-utils -
 [echo] -- puretls.present = ${puretls.present}
 [echo] -- jsse.present = true /usr/share/java/jsse-1.0.3/lib/jsse.jar
 [echo] -- commons-logging = true
 [echo] -- jmx = true /usr/share/java/mx4j-1.1.1/lib/mx4j-jmx.jar
 [echo] -- modeler = ${modeler.present}
/usr/share/java/commons-modeler-1.1M1/commons-modeler.jar
 [echo] -- JDK14 = true
[javac] Compiling 68 source files to
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/build/classes
[javac]
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/java/org/apache/tomcat/util/net/jsse/JSSE13SocketFactory.java:105: cannot
resolve symbol
[javac] symbol  : class Sun 
[javac] location: package provider
[javac] Security.addProvider (new
sun.security.provider.Sun());
[javac]^


It try to compile JSSE for jdk  1.4 (JSSE13*) with jdk 1.4 too.
I have added:
exclude name=**/util/net/jsse/JSSE13* if=jdk1.4.present /
after:
exclude name=**/util/net/jsse/JSSE14* unless=jdk1.4.present
/

(patch attached)

First ant fail, but the second attempt no:
[EMAIL PROTECTED]:~/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/
util=ant
Buildfile: build.xml

detect:

build-prepare:
[mkdir] Created dir:
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/build
[mkdir] Created dir:
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/build/classes
[mkdir] Created dir:
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/build/lib

build-main:
 [echo] - Java-utils -
 [echo] -- puretls.present = ${puretls.present}
 [echo] -- jsse.present = true /usr/share/java/jsse-1.0.3/lib/jsse.jar
 [echo] -- commons-logging = true
 [echo] -- jmx = true /usr/share/java/mx4j-1.1.1/lib/mx4j-jmx.jar
 [echo] -- modeler = ${modeler.present}
/usr/share/java/commons-modeler-1.1M1/commons-modeler.jar
 [echo] -- JDK14 = true
[javac] Compiling 69 source files to
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util
/build/classes
[javac]
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/util

Re: src/jakarta-tomcat-connectors/util/build.xml bug with IBM jdk 1.4

[Gianluca Toso]

In data Sat, 27 Dec 2003 19:24:33 +0100
Gianluca Toso scrisse:

 Problem build tomcat 5.0.16 with IBMJava2-SDK 1.4.1 on intel.
 ant from src abort on src/jakarta-tomcat-connectors/util/build.xml, so I
 have tried ant from this dir:
[...]

 /usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/ut
 il/java/org/apache/tomcat/util/net/jsse/JSSE13SocketFactory.java:105:
 cannot resolve symbol
 [javac] symbol  : class Sun 
 [javac] location: package provider
 [javac] Security.addProvider (new
 sun.security.provider.Sun());

 It try to compile JSSE for jdk  1.4 (JSSE13*) with jdk 1.4 too.
 I have added:
 exclude name=**/util/net/jsse/JSSE13* if=jdk1.4.present
 /
 after:
 exclude name=**/util/net/jsse/JSSE14*
 unless=jdk1.4.present
 /

I don't understand why, but it seems to include the support for JDK  1.4
even if compiled with JDK 1.4.x
So I have restored build.xml and modified JSSE13SocketFactory.java in order
to work with the JDK of IBM.

One of the reasons to compile sources would have to be to be able to choose
which features to include/to exclude and to obtain optimized binaries for
own system? 
IMHO would be useful one first phase style autoconf or at least one
explanation on how to make this with ant and the several one
build.properties. 
What of it you say?  I'm in mistake?

-- 
Gianluca Toso


jakarta-tomcat-5.0.16-src_ibmjdk14.patch-2.gz
Description: Binary data


pgp0.pgp
Description: PGP signature

Re: src/jakarta-tomcat-connectors/util/build.xml bug with IBM jdk 1.4

[Jacob Kjome]

You should report this as a bug and attach the patch you provided here to 
the bug, otherwise it may get lost in the shuffle.

http://issues.apache.org/bugzilla/

Jake

At 11:33 PM 12/27/2003 +0100, you wrote:
In data Sat, 27 Dec 2003 19:24:33 +0100
Gianluca Toso scrisse:
 Problem build tomcat 5.0.16 with IBMJava2-SDK 1.4.1 on intel.
 ant from src abort on src/jakarta-tomcat-connectors/util/build.xml, so I
 have tried ant from this dir:
[...]
 /usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/ut
 il/java/org/apache/tomcat/util/net/jsse/JSSE13SocketFactory.java:105:
 cannot resolve symbol
 [javac] symbol  : class Sun
 [javac] location: package provider
 [javac] Security.addProvider (new
 sun.security.provider.Sun());
 It try to compile JSSE for jdk  1.4 (JSSE13*) with jdk 1.4 too.
 I have added:
 exclude name=**/util/net/jsse/JSSE13* if=jdk1.4.present
 /
 after:
 exclude name=**/util/net/jsse/JSSE14*
 unless=jdk1.4.present
 /
I don't understand why, but it seems to include the support for JDK  1.4
even if compiled with JDK 1.4.x
So I have restored build.xml and modified JSSE13SocketFactory.java in order
to work with the JDK of IBM.
One of the reasons to compile sources would have to be to be able to choose
which features to include/to exclude and to obtain optimized binaries for
own system?
IMHO would be useful one first phase style autoconf or at least one
explanation on how to make this with ant and the several one
build.properties.
What of it you say?  I'm in mistake?
--
Gianluca Toso


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: src/jakarta-tomcat-connectors/util/build.xml bug with IBM jdk 1.4

[Bill Barker]

Gianluca Toso [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
 In data Sat, 27 Dec 2003 19:24:33 +0100
 Gianluca Toso scrisse:

  Problem build tomcat 5.0.16 with IBMJava2-SDK 1.4.1 on intel.
  ant from src abort on src/jakarta-tomcat-connectors/util/build.xml, so
I
  have tried ant from this dir:
 [...]

 
/usr/local/src/jakarta-tomcat-5.0.16-src/src/jakarta-tomcat-connectors/ut
  il/java/org/apache/tomcat/util/net/jsse/JSSE13SocketFactory.java:105:
  cannot resolve symbol
  [javac] symbol  : class Sun
  [javac] location: package provider
  [javac] Security.addProvider (new
  sun.security.provider.Sun());

  It try to compile JSSE for jdk  1.4 (JSSE13*) with jdk 1.4 too.
  I have added:
  exclude name=**/util/net/jsse/JSSE13* if=jdk1.4.present
  /
  after:
  exclude name=**/util/net/jsse/JSSE14*
  unless=jdk1.4.present
  /

 I don't understand why, but it seems to include the support for JDK  1.4
 even if compiled with JDK 1.4.x
 So I have restored build.xml and modified JSSE13SocketFactory.java in
order
 to work with the JDK of IBM.


Well, the reason is that the binary release version of Tomcat shouldn't
depend on SDK version that it was compiled with.  Don't bother with Jacob's
recommendation to submit it to Bugzilla, since I will resolve it as WONTFIX.
It is easy enough to include the JDK 1.3 classes in the build, and they
won't be used in a 1.4 environment.

 One of the reasons to compile sources would have to be to be able to
choose
 which features to include/to exclude and to obtain optimized binaries
for
 own system?
 IMHO would be useful one first phase style autoconf or at least one
 explanation on how to make this with ant and the several one
 build.properties.
 What of it you say?  I'm in mistake?

 -- 
 Gianluca Toso





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Tomcat5, SSL, IBM JDK 1.4 and Linux

[Halstead, Chris]

Thanks Bill.  I actually stumbled across that nugget on a Resin discussion list around 
1AM and got it working.  Thank the gods for Google.

The interesting thing is that while IE, Netscape and Opera all fail to work with the 
setting sslProtocol=TLS I had no problems at all connecting with Mozilla Firebird.  
There were no issues with wget either.  Go figure.

Since the IBM JDK is becoming more popular perhaps there should be something in the 
docs about 'IbmX509' and 'SSL' when using it.  If I get a spare moment I'll try to 
work up a doc patch.

Thanks again for the quick reply.

-chris


 -Original Message-
 From: Bill Barker [mailto:[EMAIL PROTECTED]
 Sent: Thursday, September 25, 2003 11:16 PM
 To: [EMAIL PROTECTED]
 Subject: Re: Tomcat5, SSL, IBM JDK 1.4 and Linux
 
 
 It seems that IBM's JSSE implementation has some limitations 
 using the TLS
 protocol.  However, Tomcat seems to work fine if you change the
 sslProtocol=SSL.
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Tomcat5, SSL, IBM JDK 1.4 and Linux

[Halstead, Chris]

OK, I'm tearing my hair out here ;-)

What's the secret to making SSL work in Tomcat 5.0.12 when running on Linux with IBM 
JDK 1.4?  I have followed the steps to the letter (thrice) and have nothing to show 
for it yet.  I found that you need to set algorithm to IbmX509 in the connector def, 
which stopped me from getting IOExceptions in JSSE14SocketFactory.init().  After doing 
that, the connector initializes and binds to the port, but attempts to connect with a 
browser immediately fail.  Netscape is nice enough to let me know that it could find 
no ciphers in common with the server, whereas IE just fails.  Non-secure works great.

I followed the exact same steps on a Sun box running Sun's 1.4 JDK (with the exact 
same install set, tarred and moved), and all works just fine.

This happens identically on an i386 machine as well as on an s/390 Linux partition.

I even tried plopping the JSSE stuff in JAVA_HOME/jre/lib/ext, but no joy.

I have tried using a self-signed cert as well as a demo cert from Verisign.

What on earth am I missing?

-chris

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tomcat5, SSL, IBM JDK 1.4 and Linux

[Bill Barker]

It seems that IBM's JSSE implementation has some limitations using the TLS
protocol.  However, Tomcat seems to work fine if you change the
sslProtocol=SSL.

Halstead, Chris [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
OK, I'm tearing my hair out here ;-)

What's the secret to making SSL work in Tomcat 5.0.12 when running on Linux
with IBM JDK 1.4?  I have followed the steps to the letter (thrice) and have
nothing to show for it yet.  I found that you need to set algorithm to
IbmX509 in the connector def, which stopped me from getting IOExceptions
in JSSE14SocketFactory.init().  After doing that, the connector initializes
and binds to the port, but attempts to connect with a browser immediately
fail.  Netscape is nice enough to let me know that it could find no ciphers
in common with the server, whereas IE just fails.  Non-secure works great.

I followed the exact same steps on a Sun box running Sun's 1.4 JDK (with the
exact same install set, tarred and moved), and all works just fine.

This happens identically on an i386 machine as well as on an s/390 Linux
partition.

I even tried plopping the JSSE stuff in JAVA_HOME/jre/lib/ext, but no joy.

I have tried using a self-signed cert as well as a demo cert from Verisign.

What on earth am I missing?

-chris




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

tomcat 4.1.24 ssl with ibm jdk 1.4

[Francois Lascelles]

I use tomcat 4.1.24 on a linux box and cannot get ssl going with ibm jvm
1.4.
I DID set the algorithm=IbmX509 in the Factory element of server.xml
and I also tried to copy jsse jars to server/lib directory but I always
end up getting the following error message.

NoClassDefFound : sun/security/provider/Sun
At
org.apache.tomcat.util.net.jsse.JSSEImplementation.getServerSocketFactor
y(JSSEImplementation.java 90)

-fl



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: tomcat 4.1.24 ssl with ibm jdk 1.4

[Bill Barker]

With 4.1.26 you should be able to use IBM's 1.4 JVM with the jsse jar in
server/lib.  It will work without the jsee jar anywhere on the machine in
4.1.27.  If you need it before then, you can grab the source files from the
CVS and compile the fixed version yourself.

Francois Lascelles [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]

 I use tomcat 4.1.24 on a linux box and cannot get ssl going with ibm jvm
 1.4.
 I DID set the algorithm=IbmX509 in the Factory element of server.xml
 and I also tried to copy jsse jars to server/lib directory but I always
 end up getting the following error message.

 NoClassDefFound : sun/security/provider/Sun
 At
 org.apache.tomcat.util.net.jsse.JSSEImplementation.getServerSocketFactor
 y(JSSEImplementation.java 90)

 -fl




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Debian, Apache 2.0.44, Tomcat 4.1.24, IBM JDK 1.4, JNI inprocess

[Peter H.]

Hello,

Does someone use IBM JDK 1.4 with tomcat 4.1.24 and apache 2.0.44
Can't startup JVM exit -1 message...
Compiled jni*.so and

maybe its the problem because the ././classic/jvm*.so is used?
I thought jdk1.4 stops supporting classic jvm...
Greetings and thanks
Peter








_
Fotos  -  MSN Fotos das virtuelle Fotoalbum. Allen Freunden zeigen oder 
einfach online entwickeln lassen:  
http://photos.msn.de/support/worldwide.aspx

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Debian, Apache 2.0.44, Tomcat 4.1.24, IBM JDK 1.4, JNI inprocess

[Richard Dunn]

On Thursday 03 April 2003 08:08, Peter H. wrote:
 Hello,

 Does someone use IBM JDK 1.4 with tomcat 4.1.24 and apache 2.0.44
 Can't startup JVM exit -1 message...

I tried this setup a couple days ago (on Redhat 8.0) and it worked fine, but I 
am using the mod_jk.so connector. I have not tried the JNI approach. I did 
notice my applications ran much slower than under the Sun 1.4.1 (both _01 and 
_02 versions) so I went back to the Sun jdk (despite reports of StringBuffer 
related memory leaks).

I am now on the Apache 2.0.45 and it is working fine.


 Compiled jni*.so and

 maybe its the problem because the ././classic/jvm*.so is used?
 I thought jdk1.4 stops supporting classic jvm...


 Greetings and thanks
 Peter


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Debian, Apache 2.0.44, Tomcat 4.1.24, IBM JDK 1.4, JNI inprocess

[Peter H.]

Would be nice hint if sun's jvm runs under debian...heard it doesn't
You know about this rumor?
Thanks






From: Richard Dunn [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: Re: Debian, Apache 2.0.44, Tomcat 4.1.24, IBM JDK 1.4, JNI 
inprocess
Date: Thu, 3 Apr 2003 08:45:37 -0700

On Thursday 03 April 2003 08:08, Peter H. wrote:
 Hello,

 Does someone use IBM JDK 1.4 with tomcat 4.1.24 and apache 2.0.44
 Can't startup JVM exit -1 message...
I tried this setup a couple days ago (on Redhat 8.0) and it worked fine, 
but I
am using the mod_jk.so connector. I have not tried the JNI approach. I did
notice my applications ran much slower than under the Sun 1.4.1 (both _01 
and
_02 versions) so I went back to the Sun jdk (despite reports of 
StringBuffer
related memory leaks).

I am now on the Apache 2.0.45 and it is working fine.


 Compiled jni*.so and

 maybe its the problem because the ././classic/jvm*.so is used?
 I thought jdk1.4 stops supporting classic jvm...


 Greetings and thanks
 Peter
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


_
MSN Hotmail  -  Absolut kostenfrei! Der weltweit größte E-Mail-Anbieter im 
Netz:  http://www.msn.de/hotmail

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Debian, Apache 2.0.44, Tomcat 4.1.24, IBM JDK 1.4, JNI inprocess

[Richard Dunn]

On Thursday 03 April 2003 10:00, Peter H. wrote:
 Would be nice hint if sun's jvm runs under debian...heard it doesn't
 You know about this rumor?


It has been  1 year since I last used Debian, so I am not aware of this 
rumor. I hope it is not the case. I have been using the above configuration 
(except NOT as JNI) on Redhat 8, and SUSE 8 and have had no problems.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Debian, Apache 2.0.44, Tomcat 4.1.24, IBM JDK 1.4, JNI inprocess

[Januski, Ken]

I've always used the Blackdown JVM on Debian. But I use it sporadically so I
can't say I'm up to date on it or any other JVMs for Debian. But I know I
chose it for a reason, probably because the Debian Users List recommended
it.

I'm sure you'd get a quick answer on the Debian User list.


-Original Message-
From: Richard Dunn [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 03, 2003 12:46 PM
To: Tomcat Users List
Subject: Re: Debian, Apache 2.0.44, Tomcat 4.1.24, IBM JDK 1.4, JNI
inprocess


On Thursday 03 April 2003 10:00, Peter H. wrote:
 Would be nice hint if sun's jvm runs under debian...heard it doesn't
 You know about this rumor?


It has been  1 year since I last used Debian, so I am not aware of this 
rumor. I hope it is not the case. I have been using the above configuration 
(except NOT as JNI) on Redhat 8, and SUSE 8 and have had no problems.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Debian, Apache 2.0.44, Tomcat 4.1.24, IBM JDK 1.4, JNI inprocess

[Richard Dunn]

On Thursday 03 April 2003 10:46, Richard Dunn wrote:
 On Thursday 03 April 2003 10:00, Peter H. wrote:
  Would be nice hint if sun's jvm runs under debian...heard it doesn't
  You know about this rumor?

 It has been  1 year since I last used Debian, so I am not aware of this
 rumor. I hope it is not the case. I have been using the above configuration
 (except NOT as JNI) on Redhat 8, and SUSE 8 and have had no problems.


Whoops. Clarification needed - other than JNI the above worked for me, except 
I went back to the Sun j2sdk1.4.1_02 for performance reasons. The 
functionality seemed to be fine on the IBM, just slower. My applications use 
a lot of XML, but I don't seem to have noticeable problems with the memory 
leaks I see reported on the Sun 1.4.1 JDK . I may not have the number of hits 
on my applications to cause the problems, although at least one of my sites 
gets 5000 hits per day, all processing XML.

 I am suprised with the relative slower performance of the IBM JDK 1.4.0 as 
the IBM 1.3 JDK seemed to be faster than Sun's 1.3 for my applications.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Debian, Apache 2.0.44, Tomcat 4.1.24, IBM JDK 1.4, JNI inprocess

[Michael Crozier]

And you should upgrade to apache 2.0.45 anyways, since there is apparently a 
un-announced security problem that was fixed.

On Thursday 03 April 2003 07:45 am, Richard Dunn wrote:
 On Thursday 03 April 2003 08:08, Peter H. wrote:
  Hello,
 
  Does someone use IBM JDK 1.4 with tomcat 4.1.24 and apache 2.0.44
  Can't startup JVM exit -1 message...

 I tried this setup a couple days ago (on Redhat 8.0) and it worked fine,
 but I am using the mod_jk.so connector. I have not tried the JNI approach.
 I did notice my applications ran much slower than under the Sun 1.4.1 (both
 _01 and _02 versions) so I went back to the Sun jdk (despite reports of
 StringBuffer related memory leaks).

 I am now on the Apache 2.0.45 and it is working fine.

  Compiled jni*.so and
 
  maybe its the problem because the ././classic/jvm*.so is used?
  I thought jdk1.4 stops supporting classic jvm...
 
 
  Greetings and thanks
  Peter

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

-- 
Michael Crozier
Conducive Technology Corporation

  First we were Sight  Sound,
  then we were Datalex,
  and temporarily Framework Technology.

http://www.conducivetech.com

Michael Crozier, [EMAIL PROTECTED]

Voice: 503.445.4233
Fax:   503.274.0939



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Debian, Apache 2.0.44, Tomcat 4.1.24, IBM JDK 1.4, JNI inprocess

[Michael Crozier]

I use Sun's JDK 1.4.01 on Debian without any problems (so far).


On Thursday 03 April 2003 09:00 am, Peter H. wrote:
 Would be nice hint if sun's jvm runs under debian...heard it doesn't
 You know about this rumor?

 Thanks






 From: Richard Dunn [EMAIL PROTECTED]

 Reply-To: [EMAIL PROTECTED]
 To: Tomcat Users List [EMAIL PROTECTED]
 Subject: Re: Debian, Apache 2.0.44, Tomcat 4.1.24, IBM JDK 1.4, JNI
 inprocess
 Date: Thu, 3 Apr 2003 08:45:37 -0700
 
 On Thursday 03 April 2003 08:08, Peter H. wrote:
   Hello,
  
   Does someone use IBM JDK 1.4 with tomcat 4.1.24 and apache 2.0.44
   Can't startup JVM exit -1 message...
 
 I tried this setup a couple days ago (on Redhat 8.0) and it worked fine,
 but I
 am using the mod_jk.so connector. I have not tried the JNI approach. I did
 notice my applications ran much slower than under the Sun 1.4.1 (both _01
 and
 _02 versions) so I went back to the Sun jdk (despite reports of
 StringBuffer
 related memory leaks).
 
 I am now on the Apache 2.0.45 and it is working fine.
 
   Compiled jni*.so and
  
   maybe its the problem because the ././classic/jvm*.so is used?
   I thought jdk1.4 stops supporting classic jvm...
  
  
   Greetings and thanks
   Peter
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

 _
 MSN Hotmail  -  Absolut kostenfrei! Der weltweit größte E-Mail-Anbieter im
 Netz:  http://www.msn.de/hotmail


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

-- 
Michael Crozier
Conducive Technology Corporation

  First we were Sight  Sound,
  then we were Datalex,
  and temporarily Framework Technology.

http://www.conducivetech.com

Michael Crozier, [EMAIL PROTECTED]

Voice: 503.445.4233
Fax:   503.274.0939



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Using Jikes with IBM JDK

[Brandon Cruz]

I am have been using the Jikes compiler for about a month.  Recently, we
switched to the IBM JDK and jikes will not compile any pages.  We get an
error like shown below...

StandardWrapperValve[jsp]: Servlet.service() for servlet jsp threw exception
org.apache.jasper.JasperException: Unable to compile class for JSP

An error occurred at line: -1 in the jsp file: null

Generated servlet error:
[javac] Compiling 1 source file
[javac]
/usr/local/tomcat4/work/www.hoosierinsuranceadvisors.com/SiteLever/page/dele
teVersion_jsp.java:0:0:0:0: Semantic Error: You need to modify your
classpath, sourcepath, bootclasspath, and/or extdirs setup. Package
java/lang could not be found in:
[javac]
/usr/java/IBMJava2-14/jre/lib/ext/ibmjceprovider.jar
[javac] /usr/java/IBMJava2-14/jre/lib/ext/gskikm.jar
[javac]
/usr/java/IBMJava2-14/jre/lib/ext/oldcertpath.jar
[javac] /usr/java/IBMJava2-14/jre/lib/ext/jaccess.jar
[javac] /usr/java/IBMJava2-14/jre/lib/ext/indicim.jar
[javac] /usr/java/IBMJava2-14/jre/lib/ext/ldapsec.jar
[javac] /usr/java/IBMJava2-14/lib/tools.jar
[javac] /usr/local/tomcat4/bin/bootstrap.jar
snip

For some reason, it does not look into the /usr/java/IBMJava2-14/jre/lib
where core.jar has the java/lang package.  Do I need to explicitly set the
classpath when using Jikes with IBM JDK?  Why would I not have to do this
when using the Sun JDK?

Brandon


--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]

Why do I need to set classpath for IBM JDK, but not Sun's?

[Brandon Cruz]

Does anyone know why I need to set a system classpath when using the IBM
JDK, but have no problems if I don't set a classpath when using the Sun
JDK's?

Does tomcat add jar files from the sun package based on file name?

For example, I see that the java/lang package is in rt.jar in sun's package,
but in core.jar in IBM's.



Brandon Cruz


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Q] Using IBM JDK with tomcat 3.3

[Sudhakar Chandra]

Hi,

Here is my setup:

tomcat: 
3.3a
mod_jk: 
3.3a
Sun JDK: 1.1.8v1
IBM JDK: 1.1.8
OS: Debian GNU/Linux testing

When I use Sun's JDK, the ajp12 and ajp13 workers start accepting 
connections.  Here are relevant bits from the log files:

Jdk11Compat: Installing jar protocol handler
2002-04-25 09:17:17 - SessionIdGenerator: Opening /dev/urandom
2002-04-25 09:17:24 - ServerXmlReader: Config=$TOMCAT_HOME/conf/server.xml
2002-04-25 09:17:24 - PathSetter: home=/usr/share/tomcat
2002-04-25 09:17:25 - ContextXmlReader: Context 
config=$TOMCAT_HOME/conf/apps-examples.xml
2002-04-25 09:17:25 - Ctx(/jsp) : Setting debug to 1
2002-04-25 09:17:25 - AutoWebApp: Auto-Adding DEFAULT:/
2002-04-25 09:17:25 - AutoWebApp: Loaded from config: DEFAULT:/examples
2002-04-25 09:17:25 - ContextManager: Tomcat configured and in stable state
2002-04-25 09:17:25 - ContextManager: Adding  DEFAULT:/examples
2002-04-25 09:17:25 - ContextManager: Adding  DEFAULT:/jsp
2002-04-25 09:17:25 - ContextManager: Adding  DEFAULT:/ROOT

thaths@daemon:[51] ~ $ telnet localhost 8007
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Connection closed by foreign host.
thaths@daemon:[52] ~ $ telnet localhost 8009
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Connection closed by foreign host.

However, when I start tomcat using IBM's JDK, ajp12 and ajp13 workers 
do not accept connections.  They don't even start up as far as I can 
tell.  Here are relevant bits from the log files:

Jdk11Compat: Installing jar protocol handler
2002-04-25 09:21:52 - SessionIdGenerator: Opening /dev/urandom
2002-04-25 09:22:02 - ServerXmlReader: Config=$TOMCAT_HOME/conf/server.xml
2002-04-25 09:22:02 - PathSetter: home=/usr/share/tomcat
2002-04-25 09:22:03 - ContextXmlReader: Context
config=$TOMCAT_HOME/conf/apps-examples.xml
2002-04-25 09:22:03 - Ctx(/jsp) : Setting debug to 1
2002-04-25 09:22:03 - AutoWebApp: Auto-Adding DEFAULT:/
2002-04-25 09:22:03 - AutoWebApp: Loaded from config: DEFAULT:/examples
2002-04-25 09:22:04 - ContextManager: Tomcat configured and in stable state
2002-04-25 09:22:04 - ContextManager: Adding  DEFAULT:/examples
2002-04-25 09:22:04 - ContextManager: Adding  DEFAULT:/jsp
2002-04-25 09:22:04 - ContextManager: Adding  DEFAULT:/ROOT

thaths@daemon:[55] ~ $ telnet localhost 8007
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
thaths@daemon:[56] ~ $ telnet localhost 8009
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused

I'd really like to work using the IBM JDK.  What am I doing wrong?  The 
configurations remain the same in both cases.  Your help would be 
greatly appreciated.

Thanks.

Thaths
-- 
Lisa:  I'm studying for the math fair.  If I win, I'll bring home a
brand new protractor.
Homer: Too bad we don't live on a farm.
thaths at aunet.org   Slacker At Large   http://www.aunet.org/~thaths/
Key fingerprint = 8A 84 2E 67 10 9A 64 03  24 38 B6 AB 1B 6E 8C E4


--
To unsubscribe:   mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]

RE: [Q] Using IBM JDK with tomcat 3.3

[Larry Isaacs]

Tomcat 3.3.x doesn't get a lot of testing against any 1.1.8
JDK.  What little testing it does get is done with Sun's
JDK 1.1.8.  This testing is done with a Tomcat that is built
with Sun's JDK 1.1.8.  The binary distribution is built
with Sun's JDK 1.3.1.  You might try building Tomcat 3.3 with
IBM's JDK and see if this succeeds and if so, does it still
run any better than the binary distribution you are using now.

Cheers,
Larry


 -Original Message-
 From: Sudhakar Chandra [mailto:[EMAIL PROTECTED]] 
 Sent: Thursday, April 25, 2002 12:37 PM
 To: [EMAIL PROTECTED]
 Subject: [Q] Using IBM JDK with tomcat 3.3
 
 
 Hi,
 
 Here is my setup:
 
 tomcat: 
 3.3a
 mod_jk: 
 3.3a
 Sun JDK: 1.1.8v1
 IBM JDK: 1.1.8
 OS: Debian GNU/Linux testing
 
 When I use Sun's JDK, the ajp12 and ajp13 workers start accepting 
 connections.  Here are relevant bits from the log files:
 
 Jdk11Compat: Installing jar protocol handler
 2002-04-25 09:17:17 - SessionIdGenerator: Opening /dev/urandom
 2002-04-25 09:17:24 - ServerXmlReader: 
 Config=$TOMCAT_HOME/conf/server.xml
 2002-04-25 09:17:24 - PathSetter: home=/usr/share/tomcat
 2002-04-25 09:17:25 - ContextXmlReader: Context 
 config=$TOMCAT_HOME/conf/apps-examples.xml
 2002-04-25 09:17:25 - Ctx(/jsp) : Setting debug to 1
 2002-04-25 09:17:25 - AutoWebApp: Auto-Adding DEFAULT:/
 2002-04-25 09:17:25 - AutoWebApp: Loaded from config: 
 DEFAULT:/examples
 2002-04-25 09:17:25 - ContextManager: Tomcat configured and 
 in stable state
 2002-04-25 09:17:25 - ContextManager: Adding  DEFAULT:/examples
 2002-04-25 09:17:25 - ContextManager: Adding  DEFAULT:/jsp
 2002-04-25 09:17:25 - ContextManager: Adding  DEFAULT:/ROOT
 
 thaths@daemon:[51] ~ $ telnet localhost 8007
 Trying 127.0.0.1...
 Connected to localhost.
 Escape character is '^]'.
 Connection closed by foreign host.
 thaths@daemon:[52] ~ $ telnet localhost 8009
 Trying 127.0.0.1...
 Connected to localhost.
 Escape character is '^]'.
 Connection closed by foreign host.
 
 However, when I start tomcat using IBM's JDK, ajp12 and ajp13 
 workers 
 do not accept connections.  They don't even start up as far as I can 
 tell.  Here are relevant bits from the log files:
 
 Jdk11Compat: Installing jar protocol handler
 2002-04-25 09:21:52 - SessionIdGenerator: Opening /dev/urandom
 2002-04-25 09:22:02 - ServerXmlReader: 
 Config=$TOMCAT_HOME/conf/server.xml
 2002-04-25 09:22:02 - PathSetter: home=/usr/share/tomcat
 2002-04-25 09:22:03 - ContextXmlReader: Context
 config=$TOMCAT_HOME/conf/apps-examples.xml
 2002-04-25 09:22:03 - Ctx(/jsp) : Setting debug to 1
 2002-04-25 09:22:03 - AutoWebApp: Auto-Adding DEFAULT:/
 2002-04-25 09:22:03 - AutoWebApp: Loaded from config: 
 DEFAULT:/examples
 2002-04-25 09:22:04 - ContextManager: Tomcat configured and 
 in stable state
 2002-04-25 09:22:04 - ContextManager: Adding  DEFAULT:/examples
 2002-04-25 09:22:04 - ContextManager: Adding  DEFAULT:/jsp
 2002-04-25 09:22:04 - ContextManager: Adding  DEFAULT:/ROOT
 
 thaths@daemon:[55] ~ $ telnet localhost 8007
 Trying 127.0.0.1...
 telnet: Unable to connect to remote host: Connection refused
 thaths@daemon:[56] ~ $ telnet localhost 8009
 Trying 127.0.0.1...
 telnet: Unable to connect to remote host: Connection refused
 
 I'd really like to work using the IBM JDK.  What am I doing 
 wrong?  The 
 configurations remain the same in both cases.  Your help would be 
 greatly appreciated.
 
 Thanks.
 
 Thaths
 -- 
 Lisa:  I'm studying for the math fair.  If I win, I'll bring home a
 brand new protractor.
 Homer: Too bad we don't live on a farm.
 thaths at aunet.org   Slacker At Large   http://www.aunet.org/~thaths/
 Key fingerprint = 8A 84 2E 67 10 9A 64 03  24 38 B6 AB 1B 6E 8C E4
 
 
 --
 To unsubscribe:   mailto:[EMAIL PROTECTED]
 For additional commands: mailto:[EMAIL PROTECTED]
 Troubles with the list: mailto:[EMAIL PROTECTED]
 

--
To unsubscribe:   mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]

Re: [Q] Using IBM JDK with tomcat 3.3

[Greg Bailey]

I'm not familiar with Debian but if it's a 2.4 Linux kernel, you may
need to set the environment variable LD_ASSUME_KERNEL=2.2.5 to get Java
applications (like Tomcat) to work.  Some JDK's (like IBM JDK 1.3 and
1.3.1) do this for you automatically.  I use IBM's JDK 1.3 with Tomcat
3.3a and 3.3.1 on a RedHat 7.2 system and it works great...

Greg Bailey


Subject:
[Q] Using IBM JDK with tomcat 3.3
From:
Sudhakar Chandra [EMAIL PROTECTED]
Date:
Thu, 25 Apr 2002 09:36:38 -0700
To:
[EMAIL PROTECTED]


Hi,

Here is my setup:

tomcat: 3.3a
mod_jk: 3.3a
Sun JDK: 1.1.8v1
IBM JDK: 1.1.8
OS: Debian GNU/Linux testing

When I use Sun's JDK, the ajp12 and ajp13 workers start accepting 
connections.  Here are relevant bits from the log files:

Jdk11Compat: Installing jar protocol handler
2002-04-25 09:17:17 - SessionIdGenerator: Opening /dev/urandom
2002-04-25 09:17:24 - ServerXmlReader: 
Config=$TOMCAT_HOME/conf/server.xml
2002-04-25 09:17:24 - PathSetter: home=/usr/share/tomcat
2002-04-25 09:17:25 - ContextXmlReader: Context 
config=$TOMCAT_HOME/conf/apps-examples.xml
2002-04-25 09:17:25 - Ctx(/jsp) : Setting debug to 1
2002-04-25 09:17:25 - AutoWebApp: Auto-Adding DEFAULT:/
2002-04-25 09:17:25 - AutoWebApp: Loaded from config: DEFAULT:/examples
2002-04-25 09:17:25 - ContextManager: Tomcat configured and in stable 
state
2002-04-25 09:17:25 - ContextManager: Adding  DEFAULT:/examples
2002-04-25 09:17:25 - ContextManager: Adding  DEFAULT:/jsp
2002-04-25 09:17:25 - ContextManager: Adding  DEFAULT:/ROOT

thaths@daemon:[51] ~ $ telnet localhost 8007
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Connection closed by foreign host.
thaths@daemon:[52] ~ $ telnet localhost 8009
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Connection closed by foreign host.

However, when I start tomcat using IBM's JDK, ajp12 and ajp13 
workers do not accept connections.  They don't even start up as far 
as I can tell.  Here are relevant bits from the log files:

Jdk11Compat: Installing jar protocol handler
2002-04-25 09:21:52 - SessionIdGenerator: Opening /dev/urandom
2002-04-25 09:22:02 - ServerXmlReader: 
Config=$TOMCAT_HOME/conf/server.xml
2002-04-25 09:22:02 - PathSetter: home=/usr/share/tomcat
2002-04-25 09:22:03 - ContextXmlReader: Context
config=$TOMCAT_HOME/conf/apps-examples.xml
2002-04-25 09:22:03 - Ctx(/jsp) : Setting debug to 1
2002-04-25 09:22:03 - AutoWebApp: Auto-Adding DEFAULT:/
2002-04-25 09:22:03 - AutoWebApp: Loaded from config: DEFAULT:/examples
2002-04-25 09:22:04 - ContextManager: Tomcat configured and in stable 
state
2002-04-25 09:22:04 - ContextManager: Adding  DEFAULT:/examples
2002-04-25 09:22:04 - ContextManager: Adding  DEFAULT:/jsp
2002-04-25 09:22:04 - ContextManager: Adding  DEFAULT:/ROOT

thaths@daemon:[55] ~ $ telnet localhost 8007
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
thaths@daemon:[56] ~ $ telnet localhost 8009
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused

I'd really like to work using the IBM JDK.  What am I doing wrong?  
The configurations remain the same in both cases.  Your help would be 
greatly appreciated.

Thanks.



--
To unsubscribe:   mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]

Re: [Q] Using IBM JDK with tomcat 3.3

[Sudhakar Chandra]

On 04/25/2002 11:19 AM, did Greg Bailey write (doodah! doodah!):
 I'm not familiar with Debian but if it's a 2.4 Linux kernel, you may
 need to set the environment variable LD_ASSUME_KERNEL=2.2.5 to get Java
 applications (like Tomcat) to work.  Some JDK's (like IBM JDK 1.3 and
 1.3.1) do this for you automatically.  I use IBM's JDK 1.3 with Tomcat
 3.3a and 3.3.1 on a RedHat 7.2 system and it works great...

As a matter of fact, I am on kernel 2.4.17.  I trid setting 
LD_ASSUME_KERNEL, but it didn't work. :-(  Oh well.

S.
-- 
Lisa:  I'm studying for the math fair.  If I win, I'll bring home a
brand new protractor.
Homer: Too bad we don't live on a farm.
thaths at aunet.org   Slacker At Large   http://www.aunet.org/~thaths/
Key fingerprint = 8A 84 2E 67 10 9A 64 03  24 38 B6 AB 1B 6E 8C E4


--
To unsubscribe:   mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]

ibm jdk 1.3 or sun jdk 1.4 ?

[Ken Anderson]

Which is faster for a tomcat webapp?
IBM JDK 1.3 or SUN JDK 1.4?
Any reported problems with 1.4  Tomcat?
Any decent benchmarking tools I can download and test with myself?
Ken



--
To unsubscribe:   mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]

RE: ibm jdk 1.3 or sun jdk 1.4 ?

[Timlin, Bob]

I use Sun JDK 1.4 and am happy with the performance.

-Original Message-
From: Ken Anderson [mailto:[EMAIL PROTECTED]] 
Sent: Friday, April 26, 2002 1:29 PM
To: Tomcat Users List
Subject: ibm jdk 1.3 or sun jdk 1.4 ?

Which is faster for a tomcat webapp?
IBM JDK 1.3 or SUN JDK 1.4?
Any reported problems with 1.4  Tomcat?
Any decent benchmarking tools I can download and test with myself?
Ken



--
To unsubscribe:   mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]



--
To unsubscribe:   mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]

Have people used IBM JDK 1.3 with Tomcat4 with UTF8

[Antony Stace]

Hi

I have just installed IBMS JDK and am using it to run Tomcat 4.  I am getting a few 
exceptions
relating to the character encoding.  Can someone please tell me if it is possible to 
use
the IBM JDK 1.3 with UTF-8 for Tomcat 4

-- 


Cheers

Tony$B!#(B
-


_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
To unsubscribe:   mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]

SSL on Tomcat 4.0 with IBM JDK 1.3.0

[Mihai Gheorghiu]

I managed to start Tomcat 4.0.1 on my RH 7.0 box only after I replaced Sun's
JDK 1.3.1 with IBM's JDK 1.3.0.
This also avoids errors in some other packages (I'm experimenting with
Velocity).
So, if I want to have an SSL connection to TC 4.0.1 on IBM JDK 1.3.0, what
do I need to do?
Thank you all.


--
To unsubscribe:   mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]

Tomcat installer cannot find IBM JDK

[Graham Leggett]

Hi all,

I just installed the IBM JDK v1.3 on a Windows 98 SE machine, then tried
to install Tomcat v4.0.1 from the .exe installer.

The installer complained that there was no JVM installed - when there
was. No clue was given by the installer as to why it could not find it,
or where it was looking.

Anyone else had a problem like this?

Regards,
Graham
-- 
-
[EMAIL PROTECTED]There's a moon
over Bourbon Street
tonight...


smime.p7s
Description: S/MIME Cryptographic Signature

RE: Tomcat installer cannot find IBM JDK

[Larry Isaacs]

I believe the installer is only looking for registry keys
for Sun's JDK.

Larry

 -Original Message-
 From: Graham Leggett [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, December 13, 2001 12:10 PM
 To: Tomcat User
 Subject: Tomcat installer cannot find IBM JDK
 
 
 Hi all,
 
 I just installed the IBM JDK v1.3 on a Windows 98 SE machine, 
 then tried
 to install Tomcat v4.0.1 from the .exe installer.
 
 The installer complained that there was no JVM installed - when there
 was. No clue was given by the installer as to why it could 
 not find it,
 or where it was looking.
 
 Anyone else had a problem like this?
 
 Regards,
 Graham
 -- 
 -
 [EMAIL PROTECTED]  There's a moon
   over Bourbon Street
   tonight...

--
To unsubscribe:   mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]

SUN JDK or IBM JDK?

[Philippe Muller]

when running the jakarta 3.2.3-1 rpm it says it is
assuming IBM JDK 1.3.0Does it matter if I run sun
JDK 1.3.1_01

__
Do You Yahoo!?
Find a job, post your resume.
http://careers.yahoo.com

--
To unsubscribe:   mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]

Re: SUN JDK or IBM JDK?

[Pier Fumagalli]

Philippe Muller at [EMAIL PROTECTED] wrote:

 when running the jakarta 3.2.3-1 rpm it says it is
 assuming IBM JDK 1.3.0Does it matter if I run sun
 JDK 1.3.1_01

Nope, but for sure the IBM's VM multi-threading implementation is better :)

Pier


--
To unsubscribe:   mailto:[EMAIL PROTECTED]
For additional commands: mailto:[EMAIL PROTECTED]
Troubles with the list: mailto:[EMAIL PROTECTED]

Tomcat 4 + IBM JDK + SMP

[Ernie]

Hello all,
Recently we decided we need a Java application, to be used with the Tomcat
servlet engine.  I had heard a few good things about IBM's JDK, so I went
with that.  This was a few weeks ago, and I chose tomcat 3.2.2 (the most
recently available).  The application (not written by me or my company)
seemed to work fine, except, in use it would get slower and slower, until
eventually a request would timeout, and the application would be
unreachable.  I tried various different changes, the major one being
switching to Sun's JDK, but that didn't seem to help matters any.

Last week, when tomcat 4.0 was released, I quickly installed that on our
test machine.  Other than a minor problem with the PrintWriter call,
everything seemed to work smoothly.  No more slowness, and everything
seemed fine (I should mention this is after having switched back to IBM's
JDK).  However, after some undetermined length of time, tomcat 4 seems to
simply stop responding to requests.  Telnetting to port 8080 and just
issuing a 'GET / HTTP/1.0' results in no response from the server at all.

Here are the specs of my environment:
2x400mhz PII processors
648mb ram
kernel 2.2.18 SMP
IBMJava2-SDK-1.3
Tomcat 4.0
glibc 2.1.3-22 (from redhat)

Also, when the system is in this state, nothing gets written in any log
file, except for this in the catalina log:
2001-09-24 10:46:47 HttpProcessor[8080][20] Starting background thread
2001-09-24 10:57:54 HttpProcessor[8080][21] Starting background thread

for each request, one of those will show up in the log, but nothing else
will happen.

Can anyone shed some light on this, or point me at a resource that might
help?  Could this be an smp problem?  Should I switch to sun's JDK, or one
from blackdown.org?  Is there some way i can make the JVM run only in
'uniprocessor' mode?  Am I insane??? :)

Thanks!

-e

Réf. : Tomcat 4 + IBM JDK + SMP

[joseph . vallot]

[EMAIL PROTECTED] wrote:

 Last week, when tomcat 4.0 was released, I quickly installed that on
 our test machine.  Other than a minor problem with the PrintWriter
 call, everything seemed to work smoothly.  No more slowness, and
 everything seemed fine (I should mention this is after having switched
 back to IBM's JDK).  However, after some undetermined length of time,
 tomcat 4 seems to simply stop responding to requests.  Telnetting to
 port 8080 and just issuing a 'GET / HTTP/1.0' results in no response
 from the server at all.

well, if you look at list archive (not far away: search tomcat
3.2.3hangs, AIX 4.3.3(jre 1.2.2 and 1.3.0) and tomcat 3.3b2 hangs too
:-( (Re: tomcat 3.2.3 hangs, AIX 4.3.3 (jre 1.2.2 and 1.3.0)) subjects
from last week to today), you'll read we encountered exactly the same
problem (I did not mentionned in my posts than we run tomcat on a SMP
AIX machine): I did write a simple sample that shows tomcat hangging.

Sorry to say I do not have any answer, and, personally, no alternative
JVM :-(( (anybody knows a non-IBM jvm ?).

talking about your case, I would run back to Sun's jvm (let me know if
that solve something).

--
Joseph Vallot




This message and any attachments (the message) is
intended solely for the addressees and is confidential. 
If you receive this message in error, please delete it and 
immediately notify the sender. Any use not in accord with 
its purpose, any dissemination or disclosure, either whole 
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message. 
BNP PARIBAS (and its subsidiaries) shall (will) not 
therefore be liable for the message if modified. 

-

Ce message et toutes les pieces jointes (ci-apres le 
message) sont etablis a l'intention exclusive de ses 
destinataires et sont confidentiels. Si vous recevez ce 
message par erreur, merci de le detruire et d'en avertir 
immediatement l'expediteur. Toute utilisation de ce 
message non conforme a sa destination, toute diffusion 
ou toute publication, totale ou partielle, est interdite, sauf 
autorisation expresse. L'internet ne permettant pas 
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce 
message, dans l'hypothese ou il aurait ete modifie.

Re: Tomcat 4 + IBM JDK + SMP

[Remy Maucherat]

 Hello all,
 Recently we decided we need a Java application, to be used with the Tomcat
 servlet engine.  I had heard a few good things about IBM's JDK, so I went
 with that.  This was a few weeks ago, and I chose tomcat 3.2.2 (the most
 recently available).  The application (not written by me or my company)
 seemed to work fine, except, in use it would get slower and slower, until
 eventually a request would timeout, and the application would be
 unreachable.  I tried various different changes, the major one being
 switching to Sun's JDK, but that didn't seem to help matters any.

 Last week, when tomcat 4.0 was released, I quickly installed that on our
 test machine.  Other than a minor problem with the PrintWriter call,
 everything seemed to work smoothly.  No more slowness, and everything
 seemed fine (I should mention this is after having switched back to IBM's
 JDK).  However, after some undetermined length of time, tomcat 4 seems to
 simply stop responding to requests.  Telnetting to port 8080 and just
 issuing a 'GET / HTTP/1.0' results in no response from the server at all.

 Here are the specs of my environment:
 2x400mhz PII processors
 648mb ram
 kernel 2.2.18 SMP
 IBMJava2-SDK-1.3
 Tomcat 4.0
 glibc 2.1.3-22 (from redhat)

 Also, when the system is in this state, nothing gets written in any log
 file, except for this in the catalina log:
 2001-09-24 10:46:47 HttpProcessor[8080][20] Starting background thread
 2001-09-24 10:57:54 HttpProcessor[8080][21] Starting background thread

 for each request, one of those will show up in the log, but nothing else
 will happen.

Is that really printed for each single request you make to Tomcat ? (It
really shouldn't - since that thing is printed each time we fork a new
processing thread in the HTTP connector -, and if it does, then it's the
root cause of the problem)

Remy

Re: Tomcat 4 + IBM JDK + SMP

[Ernie]

On Mon, 24 Sep 2001, Remy Maucherat wrote:
 Is that really printed for each single request you make to Tomcat ? (It
 really shouldn't - since that thing is printed each time we fork a new
 processing thread in the HTTP connector -, and if it does, then it's the
 root cause of the problem)

 Remy

Yes, once the server is hung, that shows up in the logs each and every
time.  If I run ab -n 5 -c 5 http://localhost:8080/  Then 5 log entries
will show up in the log file ...

So is there a solution?

-e

Tomcat 4.0-b5 fails on IBM JDK, but works on Sun JDK

[Steve Sullivan]

Hi, I'm running Tomcat 4.0-b5 on RedHat 7.1 on a Pentium.
When I run with Sun's JDK, everything works fine.
$ java -version
java version 1.4.0-beta
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-beta-b65)
Java HotSpot(TM) Client VM (build 1.4.0-beta-b65, mixed mode)

But when I run with IBM's JDK, Tomcat gets ClassLoader problems
(see log below).
$ java -version
java version 1.3.0
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0)
Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled: 
jitc))

I'd really rather use IBM's JDK, since in general it
is much more reliable than Sun's.  How can I get Tomcat
running with the IBM JDK?

Many thanks,
Steve

Extract from localhost_log.2001-08-27.txt: (scan down for exception)

2001-08-27 12:27:44 StandardHost[localhost]: Installing web application at context 
path /testappa from URL 
file:/stuff/tdtomcat/jakarta-tomcat-4.0-b5-src/build/webapps/testappa
2001-08-27 12:27:44 StandardManager[/testappa]: Seeding random number generator class 
java.security.SecureRandom
2001-08-27 12:27:44 StandardManager[/testappa]: Seeding of random number generator has 
been completed
2001-08-27 12:27:44 ContextConfig[/testappa]: Configured an authenticator for method 
BASIC
2001-08-27 12:27:44 StandardWrapper[/testappa:default]: Loading container servlet 
default
2001-08-27 12:27:44 default: init
2001-08-27 12:27:44 StandardWrapper[/testappa:invoker]: Loading container servlet 
invoker
2001-08-27 12:27:44 invoker: init
2001-08-27 12:27:44 StandardWrapper[/testappa:jsp]: Using Jasper classloader for 
servlet jsp
2001-08-27 12:27:44 jsp: init
2001-08-27 12:27:45 StandardWrapper[/testappa:Testapia]: Marking servlet Testapia as 
unavailable
2001-08-27 12:27:45 StandardContext[/testappa]: Servlet /testappa threw load() 
exception
javax.servlet.ServletException: Wrapper cannot find servlet class testpk/Testa or a 
class it depends on
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:797)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3277)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:785)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:413)
at org.apache.catalina.core.StandardHost.install(StandardHost.java:641)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:300)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:389)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:232)
at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:155)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1131)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:278)
at org.apache.catalina.core.StandardService.start(StandardService.java:353)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:458)
at org.apache.catalina.startup.Catalina.start(Catalina.java:725)
at org.apache.catalina.startup.Catalina.execute(Catalina.java:647)
at org.apache.catalina.startup.Catalina.process(Catalina.java:177)
at java.lang.reflect.Method.invoke(Native Method)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:196)
- Root Cause -
java.lang.ClassNotFoundException: testpk/Testa
at 
org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader.java(Compiled
 Code))
at 
org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader.java(Compiled
 Code))
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:792)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3277)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:785)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:413)
at org.apache.catalina.core.StandardHost.install(StandardHost.java:641)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:300)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:389)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:232)
at 
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:155)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1131)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:278)
at org.apache.catalina.core.StandardService.start(StandardService.java:353)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:458

AW: IBM JDK

[Kursad . Kayatuerk]

For one year we are using it on our server. And this package is faster than
the sun's package.

-Ursprüngliche Nachricht-
Von: Mike McGuinness [mailto:[EMAIL PROTECTED]]
Gesendet am: Dienstag, 14. August 2001 18:21
An: [EMAIL PROTECTED]
Betreff: IBM JDK

Has anyone tried IBM jdk/runtime environment on Linux with Tomcat 3.2.3?

I'v got sun jdk 1.3, running on Red Hat 7.1, with apache 1.3.20, and 
tomcat 3.2.3.
I was wondering how or if IBM's jdk/runtime works.

Mike

Re: IBM JDK

[Paul Rubenis]

Another reason to use IBM's jdk is that IBM will support it.  They will
not support sun's jdk.  It doesn't hurt that IBM's jdk is a very good
implementation.

James, Stuart wrote:
 
 why would you want to run the IBM JDK ? is it faster/better than suns jdk ?
 

-- 
+-- mailto:[EMAIL PROTECTED] +
| Paul M Rubenis - System Administrator |
| Phone: (612) 624-8337 |
| Fax:   (612) 625-6853 |
+---+
| Any connection between your reality and mine is purely|
| coincidental. |

IBM JDK

[Mike McGuinness]

Has anyone tried IBM jdk/runtime environment on Linux with Tomcat 3.2.3?

I'v got sun jdk 1.3, running on Red Hat 7.1, with apache 1.3.20, and 
tomcat 3.2.3.
I was wondering how or if IBM's jdk/runtime works.

Mike

RE: IBM JDK

[Mike Jackson]

Works great for me.

--mikej
-=-
mike jackson
[EMAIL PROTECTED] 

 -Original Message-
 From: Mike McGuinness [mailto:[EMAIL PROTECTED]]
 Sent: Tuesday, August 14, 2001 9:21 AM
 To: [EMAIL PROTECTED]
 Subject: IBM JDK
 
 
 Has anyone tried IBM jdk/runtime environment on Linux with Tomcat 3.2.3?
 
 I'v got sun jdk 1.3, running on Red Hat 7.1, with apache 1.3.20, and 
 tomcat 3.2.3.
 I was wondering how or if IBM's jdk/runtime works.
 
 Mike
 

Re: IBM JDK

[Paul Rubenis]

Works very well for me running tomcat 3.2.3, rh 6.2 and IBMJava2-13
(build 1.3.0, J2RE 1.3.0 IBM build cx130-20010329 (JIT enabled: jitc)

Mike McGuinness wrote:
 
 Has anyone tried IBM jdk/runtime environment on Linux with Tomcat 3.2.3?
 
 I'v got sun jdk 1.3, running on Red Hat 7.1, with apache 1.3.20, and
 tomcat 3.2.3.
 I was wondering how or if IBM's jdk/runtime works.
 
 Mike

-- 
+-- mailto:[EMAIL PROTECTED] +
| Paul M Rubenis - System Administrator |
| Phone: (612) 624-8337 |
| Fax:   (612) 625-6853 |
+---+
| Any connection between your reality and mine is purely|
| coincidental. |

RE: IBM JDK

[James, Stuart]

why would you want to run the IBM JDK ? is it faster/better than suns jdk ?

-Original Message-
From: Paul Rubenis [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 14, 2001 5:37 PM
To: [EMAIL PROTECTED]
Subject: Re: IBM JDK


Works very well for me running tomcat 3.2.3, rh 6.2 and IBMJava2-13
(build 1.3.0, J2RE 1.3.0 IBM build cx130-20010329 (JIT enabled: jitc)

Mike McGuinness wrote:
 
 Has anyone tried IBM jdk/runtime environment on Linux with Tomcat 3.2.3?
 
 I'v got sun jdk 1.3, running on Red Hat 7.1, with apache 1.3.20, and
 tomcat 3.2.3.
 I was wondering how or if IBM's jdk/runtime works.
 
 Mike

-- 
+-- mailto:[EMAIL PROTECTED] +
| Paul M Rubenis - System Administrator |
| Phone: (612) 624-8337 |
| Fax:   (612) 625-6853 |
+---+
| Any connection between your reality and mine is purely|
| coincidental. |


___
Email Disclaimer

This communication is for the attention of the
named recipient only and should not be passed
on to any other person. Information relating to
any company or security, is for information
purposes only and should not be interpreted as
a solicitation or offer to buy or sell any security.
The information on which this communication is based
has been obtained from sources we believe to be reliable,
but we do not guarantee its accuracy or completeness.
All expressions of opinion are subject to change
without notice.  All e-mail messages, and associated attachments,
are subject to interception and monitoring for lawful business purposes.
___

Re: IBM JDK

[Mike McGuinness]

Yes, based on my experience with certain applications the IBM jdk was
faster than sun's. Your mileage may vary.

The other reason is I'm porting my apache/tomcat application to AIX and
wanted to run IBM's jdk there.

Mike

The main reason is I am porting from Linix to AIX

James, Stuart wrote:

 why would you want to run the IBM JDK ? is it faster/better than suns jdk ?
 
 -Original Message-
 From: Paul Rubenis [mailto:[EMAIL PROTECTED]]
 Sent: Tuesday, August 14, 2001 5:37 PM
 To: [EMAIL PROTECTED]
 Subject: Re: IBM JDK
 
 
   Works very well for me running tomcat 3.2.3, rh 6.2 and IBMJava2-13
 (build 1.3.0, J2RE 1.3.0 IBM build cx130-20010329 (JIT enabled: jitc)
 
 Mike McGuinness wrote:
 
 Has anyone tried IBM jdk/runtime environment on Linux with Tomcat 3.2.3?
 
 I'v got sun jdk 1.3, running on Red Hat 7.1, with apache 1.3.20, and
 tomcat 3.2.3.
 I was wondering how or if IBM's jdk/runtime works.
 
 Mike
 

Re: IBM JDK

[Tim O'Neil]

At 09:36 AM 8/14/2001, you wrote:
 Works very well for me running tomcat 3.2.3, rh 6.2 and IBMJava2-13
(build 1.3.0, J2RE 1.3.0 IBM build cx130-20010329 (JIT enabled: jitc)

The IBM JVM is supposed to be considerably faster than Sun.

RE: IBM JDK

[Aravind Naidu]

Works great, similar environment to yours, except I am using the IBM HTTP
Server (modifid Apache) v1.3.19

My tests have shown that the IBM JDK is way faster than Sun's for my
application scenarios and you can also look at the Volano benchmarks.

Aravind

-Original Message-
From: Mike McGuinness [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 15 August 2001 00:21
To: [EMAIL PROTECTED]
Subject: IBM JDK


Has anyone tried IBM jdk/runtime environment on Linux with Tomcat 3.2.3?

I'v got sun jdk 1.3, running on Red Hat 7.1, with apache 1.3.20, and
tomcat 3.2.3.
I was wondering how or if IBM's jdk/runtime works.

Mike

RE: Compile JSP with Tomcat/IBM JDK 1.2.2/AIX4.3.3

[Klaas van der Ploeg]

  I wrote a class around the javac from IBM,...
 
 Is this javac from IBM freely redistributable?  I believe 
 the javac that
 comes with Sun's JDK is not.  That is the main reason for substituting
 javac with Jikes for many of us.

I don't quitte get that question, as everyone is able to download sun's jdk
from their site isn't it?? That's the same for the IBM jdk, with the only
difference that you have to register yourself before you can download it.

 
 And, if you do not plan to redistribute your application, why not use
 tools.jar?

You mean, the sun's javac compiler in the tools.jar? Mm... didn't thought
about that option.

 
 Also, do you plan to post your solution in how to - step by 
 step form
 so that users who encounter the same problem on AIX would benefit?
 

1. Copy JikesJavaCompiler.java from the Tomcat sources to
IBMJavaCompiler.java
2. Remove the packagename from the top of the file, or insert a new package
statement.
3. Add the -O option to the commandline String[] in compile()  (to
'optimize' compilation)
3. Compile your class  put it in a jar (jar -cvf )
4. Put the jar file in the tomcat/lib directory
5. Add jspCompilerPlugin parameter to web.xml and specify your classname
(IBMJavaCompiler)
6. Add jspCompilerPath parameter to web.xml and specify the executable of
the compiler ($IBMJDK_HOME/sh/javac)
7. Flush work directory
8. Start tomcat
9. Your jsp's are being compiled with ibm's compiler. If not, check
logs/jasper.log for initialization errors for your compiler.

That's it.

Rgrds,
Klaas

RE: Compile JSP with Tomcat/IBM JDK 1.2.2/AIX4.3.3

[Klaas van der Ploeg]

Hi,

I did not mean Jikes because I already have a javac (which comes with the
JDK), and I don't want to compile Jikes from source for the AIX platform.
But your directions pointed me in the right way:

I wrote a class around the javac from IBM, basically it's a copy of
JikesJavaCompiler, but with some modified command line parameters. I added
this class to my WAR, and modified application/web-inf/web.xml and added
jspCompilerPlugin and jspCompilerPath. And that works fine.

So, basically thanks for your suggestions, but I did it a bit different.
(And at least easier for AIX)

Rgrds,
Klaas

 -Original Message-
 From: Gautam Sinha [mailto:[EMAIL PROTECTED]]
 Sent: donderdag 2 augustus 2001 16:11
 To: [EMAIL PROTECTED]
 Subject: RE: Compile JSP with Tomcat/IBM JDK 1.2.2/AIX4.3.3
 
 
 I assume you mean the Jikes compiler when you say IBM's 
 javac compiler.
 Since you did not know the name of IBM's javac, you 
 probably could not
 perform an effective search of the tomcat user archives.
 
 I posted a solution to your problem recently.
 It is available in the tomcat-user archives at
 http://mikal.org/interests/java/tomcat/archive/view?mesg=35715
 
 You may replace Step 2 with the init-param tag as suggested 
 by Chris Brown in his follow-up posting.  He also points out certain
 issues that are worth knowing.
 
 http://mikal.org/interests/java/tomcat/archive/view?mesg=35737
 
 I have not tested the steps on the AIX platform, but they are tested
 on the Windows platform.
 
 Gautam
 
 -Original Message-
 From: Klaas van der Ploeg [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, August 02, 2001 1:35 AM
 To: [EMAIL PROTECTED]
 Subject: Compile JSP with Tomcat/IBM JDK 1.2.2/AIX4.3.3
 
 Hi All,
 
 I managed to install Tomcat 3.2.3 on AIX with IBM's JDK 1.2.2. I also
 deployed my application on it using a .war file. But, when I 
 request a jsp
 page, I get an exception sun.tools.javac.Main etc
 
 Of course, this is related to the fact that I'm not using sun's jdk.
 
 My question:
 - Can I configure Tomcat to use IBM's javac for compiling jsp's?
 - Can I use conf/web.xml (jspCompilerPlugin) to specify the 
 classname (I
 read that these directives are not working, is that correct?)?
 - What is the classname of the IBM javac compiler?
 
 Thanx for your help.
 
 Klaas
 

RE: Compile JSP with Tomcat/IBM JDK 1.2.2/AIX4.3.3

[Gautam Sinha]

Klaas,

 I wrote a class around the javac from IBM,...

Is this javac from IBM freely redistributable?  I believe the javac that
comes with Sun's JDK is not.  That is the main reason for substituting
javac with Jikes for many of us.

And, if you do not plan to redistribute your application, why not use
tools.jar?

Also, do you plan to post your solution in how to - step by step form
so that users who encounter the same problem on AIX would benefit?

Thanks,

Gautam

-Original Message-
From: Klaas van der Ploeg [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 06, 2001 3:11 AM
To: [EMAIL PROTECTED]
Subject: RE: Compile JSP with Tomcat/IBM JDK 1.2.2/AIX4.3.3

Hi,

I did not mean Jikes because I already have a javac (which comes with the
JDK), and I don't want to compile Jikes from source for the AIX platform.
But your directions pointed me in the right way:

I wrote a class around the javac from IBM, basically it's a copy of
JikesJavaCompiler, but with some modified command line parameters. I added
this class to my WAR, and modified application/web-inf/web.xml and added
jspCompilerPlugin and jspCompilerPath. And that works fine.

So, basically thanks for your suggestions, but I did it a bit different.
(And at least easier for AIX)

Rgrds,
Klaas

 -Original Message-
 From: Gautam Sinha [mailto:[EMAIL PROTECTED]]
 Sent: donderdag 2 augustus 2001 16:11
 To: [EMAIL PROTECTED]
 Subject: RE: Compile JSP with Tomcat/IBM JDK 1.2.2/AIX4.3.3


 I assume you mean the Jikes compiler when you say IBM's
 javac compiler.
 Since you did not know the name of IBM's javac, you
 probably could not
 perform an effective search of the tomcat user archives.

 I posted a solution to your problem recently.
 It is available in the tomcat-user archives at
 http://mikal.org/interests/java/tomcat/archive/view?mesg=35715

 You may replace Step 2 with the init-param tag as suggested
 by Chris Brown in his follow-up posting.  He also points out certain
 issues that are worth knowing.

 http://mikal.org/interests/java/tomcat/archive/view?mesg=35737

 I have not tested the steps on the AIX platform, but they are tested
 on the Windows platform.

 Gautam

 -Original Message-
 From: Klaas van der Ploeg [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, August 02, 2001 1:35 AM
 To: [EMAIL PROTECTED]
 Subject: Compile JSP with Tomcat/IBM JDK 1.2.2/AIX4.3.3

 Hi All,

 I managed to install Tomcat 3.2.3 on AIX with IBM's JDK 1.2.2. I also
 deployed my application on it using a .war file. But, when I
 request a jsp
 page, I get an exception sun.tools.javac.Main etc

 Of course, this is related to the fact that I'm not using sun's jdk.

 My question:
 - Can I configure Tomcat to use IBM's javac for compiling jsp's?
 - Can I use conf/web.xml (jspCompilerPlugin) to specify the
 classname (I
 read that these directives are not working, is that correct?)?
 - What is the classname of the IBM javac compiler?

 Thanx for your help.

 Klaas

Compile JSP with Tomcat/IBM JDK 1.2.2/AIX4.3.3

[Klaas van der Ploeg]

Hi All,

I managed to install Tomcat 3.2.3 on AIX with IBM's JDK 1.2.2. I also
deployed my application on it using a .war file. But, when I request a jsp
page, I get an exception sun.tools.javac.Main etc

Of course, this is related to the fact that I'm not using sun's jdk. 

My question:
- Can I configure Tomcat to use IBM's javac for compiling jsp's?
- Can I use conf/web.xml (jspCompilerPlugin) to specify the classname (I
read that these directives are not working, is that correct?)?
- What is the classname of the IBM javac compiler?

Thanx for your help.

Klaas

RE: Compile JSP with Tomcat/IBM JDK 1.2.2/AIX4.3.3

[Andrew Inggs]

Klaas van der Ploeg wrote:
 I managed to install Tomcat 3.2.3 on AIX with IBM's JDK 1.2.2. I also
 deployed my application on it using a .war file. But, when I 
 request a jsp page, I get an exception sun.tools.javac.Main etc
 
 Of course, this is related to the fact that I'm not using sun's jdk. 
 
 My question:
 - Can I configure Tomcat to use IBM's javac for compiling jsp's?
 - Can I use conf/web.xml (jspCompilerPlugin) to specify the 
 classname (I read that these directives are not working, is that
 correct?)?
 - What is the classname of the IBM javac compiler?

I don't know about using the javac from IBM, but you may want to
try using Jikes with Tomcat.  There is some info at
http://www.jguru.com/faq/view.jsp?EID=307643
but read the comments, because the answer is out of date for
Tomcat 3.2, which no longer reads TOMCAT_HOME/conf/web.xml.

More info on Jikes at
http://oss.software.ibm.com/developerworks/opensource/jikes/

-- Andrew

-- 
Tell the US to free Dmitry Sklyarov! http://www.freesklyarov.org

Re: Linux IBM JDK + Tomcat + SMP hangs

[Bill Graham]

hi Edward,

I've been having similar problems doing load testing
with standalone Tomcat 3.2.1 with the 2.2.16 kernal
with glibc2.1.3-15.

I downloaded the most recent build of IBM's VM,
cx130-20010207 and have been having much better
results as far as VM stability is concerned. I ran my
test on a uniprocessor kernal and got great results.
Changing to the SMP kernel, the VM's still stable, but
I'm getting a lot of NullPointerExceptions. I'm
looking into that now, I think it could be a Tomcat
problem though.

bill

--- Chong Yu Meng [EMAIL PROTECTED] wrote:
 Hello Edward :
 
 I believe your glibc version is causing the problems
 you are seeing. I never
 had any luck with glibc2.2 on my Caldera OpenLinux
 eDesktop 2.4 box. On the
 IBM Java on Linux newsgroup, someone claims to be
 successful using the i386
 version of glibc instead of i686, and I seem to
 remember someone on the same
 newsgroup saying that Red Hat has issued a fix for
 it.
 Hope this helps. For myself, I am still using
 glibc-2.1.3.
 
 Regards,
 Pascal Chong
 
 
 
 - Original Message -
 From: "Edward MacGillivray" [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Friday, March 23, 2001 8:35 AM
 Subject: Re: Linux IBM JDK + Tomcat + SMP hangs
 
 
  On Sun, 7 Jan 2001 22:42:18 -0500
   "brien" [EMAIL PROTECTED] wrote:
   Hi,
  
   I've been having a really tough time to say the
 least
   trying to get the
   IBM JDK 1.3 to work on an SMP machine under
 linux.  I
   don't think my
   problem is unique.  The JDK hangs, consuming 99%
 of the
   CPU.
  
   From what I can tell, this problem is specific
 to the
   IBM JDK 1.3 on SMP
   machines.  I've read just about every message on
 the ibm
   linux java
   newsgroup, and the typical solution offered is
 always to
   install
   glibc 2.1.3-21.  Without doing this I had
 instant hangs
   as soon as I ran
   tomcat.  After updating glibc, the hangs take a
 little
   while to occur, but
   they are still present and persistent.
  
   Unfortunately, I'm also bound to using DB2 on
 the
   database side, and
   IBM tech support has stated that they do not
 support
   sun's jdk.
  
   If anyone can help me out I'd greatly appreciate
 it.
  
   my environment is:
   dual p3/866 + 512mb (dell poweredge 2450)
   redhat linux 6.2
   kernel 2.2.16 SMP
   glibc-2.1.3-21
   apache tomcat 3.2.1 (also tried 3.1.1)
  
   IBM JDK:
   java version "1.3.0"
   Java(TM) 2 Runtime Environment, Standard Edition
 (build
   1.3.0)
   Classic VM (build 1.3.0, J2RE 1.3.0 IBM build
   cx130-20001124 (JIT enabled:
   jitc))
  
   brien
 
  Has anyone else had this problem? because it
 appears as
  though I am having it too.  I have search my
 archive of
  Tomcat-User posts and the web for information on
 Tomcat
  hanging under linux SMP.  I found the above post
 but no
  replies to it.
 
  I have successfully installed the webapp I have to
 three
  different single processor computers but the one I
 want it
  on is multi proc and does not want to work.  I
 have been
  working with Tomcat 3.1 on all of the single proc
 boxes and
  initially used 3.1 on the multi proc.  The
 application was
  able to function just as it had on the other boxes
 but
  within a few minutes the application had hung and
 was not
  responding to jsp or servlet requests.  When the
 application
  got to this state though the Tomcat program was
 unable to
  stop itself, so I had to start killing processes.
 
  I then figured that possibly it was 3.1 that had a
 problem,
  so I went and got Tomcat 3.2.1.  However, this was
 pretty
  much a step backward, because with 3.2.1 the
 webapp is never
  able to work.  What's worse is that running the
 Tomcat
  shutdown script, even immediately after running
 the startup
  script, Tomcat is unable to stop itself.
 
  I can't say that I have much experience with
 Tomcat 3.2.1,
  however the mod_jk.log file indicates that it is
 finding a
  worker and the web browser accessing the webapp
 spins until
  apache times out.  I am confident that Apache is
 configured
  properly.
 
  The box's environ is
  3 * p-pro/200 + 256Mb
  Redhat Linux 6.2, kernel 2.2.14smp
  Apache 1.2.19
  Tomcat 3.2.1 using mod_jk (also happens with 3.1
 using
  mod_jserv)
  glibc 2.2.2
 
  thanks
  mac
 


__
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail. 
http://personal.mail.yahoo.com/

Re: Linux IBM JDK + Tomcat + SMP hangs

[Edward MacGillivray]

On Sun, 7 Jan 2001 22:42:18 -0500
 "brien" [EMAIL PROTECTED] wrote:
 Hi,
 
 I've been having a really tough time to say the least
 trying to get the
 IBM JDK 1.3 to work on an SMP machine under linux.  I
 don't think my
 problem is unique.  The JDK hangs, consuming 99% of the
 CPU.
 
 From what I can tell, this problem is specific to the
 IBM JDK 1.3 on SMP
 machines.  I've read just about every message on the ibm
 linux java
 newsgroup, and the typical solution offered is always to
 install
 glibc 2.1.3-21.  Without doing this I had instant hangs
 as soon as I ran
 tomcat.  After updating glibc, the hangs take a little
 while to occur, but
 they are still present and persistent.
 
 Unfortunately, I'm also bound to using DB2 on the
 database side, and
 IBM tech support has stated that they do not support
 sun's jdk.
 
 If anyone can help me out I'd greatly appreciate it.
 
 my environment is:
 dual p3/866 + 512mb (dell poweredge 2450)
 redhat linux 6.2
 kernel 2.2.16 SMP
 glibc-2.1.3-21
 apache tomcat 3.2.1 (also tried 3.1.1)
 
 IBM JDK:
 java version "1.3.0"
 Java(TM) 2 Runtime Environment, Standard Edition (build
 1.3.0)
 Classic VM (build 1.3.0, J2RE 1.3.0 IBM build
 cx130-20001124 (JIT enabled:
 jitc))
 
 brien

Has anyone else had this problem? because it appears as
though I am having it too.  I have search my archive of
Tomcat-User posts and the web for information on Tomcat
hanging under linux SMP.  I found the above post but no
replies to it.

I have successfully installed the webapp I have to three
different single processor computers but the one I want it
on is multi proc and does not want to work.  I have been
working with Tomcat 3.1 on all of the single proc boxes and
initially used 3.1 on the multi proc.  The application was
able to function just as it had on the other boxes but
within a few minutes the application had hung and was not
responding to jsp or servlet requests.  When the application
got to this state though the Tomcat program was unable to
stop itself, so I had to start killing processes.

I then figured that possibly it was 3.1 that had a problem,
so I went and got Tomcat 3.2.1.  However, this was pretty
much a step backward, because with 3.2.1 the webapp is never
able to work.  What's worse is that running the Tomcat
shutdown script, even immediately after running the startup
script, Tomcat is unable to stop itself.

I can't say that I have much experience with Tomcat 3.2.1,
however the mod_jk.log file indicates that it is finding a
worker and the web browser accessing the webapp spins until
apache times out.  I am confident that Apache is configured
properly.

The box's environ is
3 * p-pro/200 + 256Mb
Redhat Linux 6.2, kernel 2.2.14smp
Apache 1.2.19
Tomcat 3.2.1 using mod_jk (also happens with 3.1 using
mod_jserv)
glibc 2.2.2

thanks
mac

Re: Linux IBM JDK + Tomcat + SMP hangs

[Jeff Turner]

It sounds like there's SMP bugs fixed in jdk1.3.1beta. Heard that on cocoon-dev
in this thread:

http://marc.theaimsgroup.com/?t=9850303674w=2r=1

"
..
linux 2.2.17
vm jdk1.3.1beta
(workaround for nasty linux SMP bug in SunVM causing segv)
..
"
  - Allan Erskine.

HTH,

--Jeff


On Thu, Mar 22, 2001 at 06:35:13PM -0600, Edward MacGillivray wrote:
 On Sun, 7 Jan 2001 22:42:18 -0500
  "brien" [EMAIL PROTECTED] wrote:
  Hi,
  
  I've been having a really tough time to say the least trying to get the IBM
  JDK 1.3 to work on an SMP machine under linux.  I don't think my problem is
  unique.  The JDK hangs, consuming 99% of the CPU.
  
  From what I can tell, this problem is specific to the
  IBM JDK 1.3 on SMP machines.  I've read just about every message on the ibm
  linux java newsgroup, and the typical solution offered is always to install
  glibc 2.1.3-21.  Without doing this I had instant hangs as soon as I ran
  tomcat.  After updating glibc, the hangs take a little while to occur, but
  they are still present and persistent.
  
  Unfortunately, I'm also bound to using DB2 on the database side, and IBM
  tech support has stated that they do not support sun's jdk.
  
  If anyone can help me out I'd greatly appreciate it.
  
  my environment is:
  dual p3/866 + 512mb (dell poweredge 2450)
  redhat linux 6.2
  kernel 2.2.16 SMP
  glibc-2.1.3-21
  apache tomcat 3.2.1 (also tried 3.1.1)
  
  IBM JDK:
  java version "1.3.0"
  Java(TM) 2 Runtime Environment, Standard Edition (build
  1.3.0)
  Classic VM (build 1.3.0, J2RE 1.3.0 IBM build
  cx130-20001124 (JIT enabled:
  jitc))
  
  brien
 
 Has anyone else had this problem? because it appears as
 though I am having it too.  I have search my archive of
 Tomcat-User posts and the web for information on Tomcat
 hanging under linux SMP.  I found the above post but no
 replies to it.
 
 I have successfully installed the webapp I have to three
 different single processor computers but the one I want it
 on is multi proc and does not want to work.  I have been
 working with Tomcat 3.1 on all of the single proc boxes and
 initially used 3.1 on the multi proc.  The application was
 able to function just as it had on the other boxes but
 within a few minutes the application had hung and was not
 responding to jsp or servlet requests.  When the application
 got to this state though the Tomcat program was unable to
 stop itself, so I had to start killing processes.
 
 I then figured that possibly it was 3.1 that had a problem,
 so I went and got Tomcat 3.2.1.  However, this was pretty
 much a step backward, because with 3.2.1 the webapp is never
 able to work.  What's worse is that running the Tomcat
 shutdown script, even immediately after running the startup
 script, Tomcat is unable to stop itself.
 
 I can't say that I have much experience with Tomcat 3.2.1,
 however the mod_jk.log file indicates that it is finding a
 worker and the web browser accessing the webapp spins until
 apache times out.  I am confident that Apache is configured
 properly.
 
 The box's environ is
 3 * p-pro/200 + 256Mb
 Redhat Linux 6.2, kernel 2.2.14smp
 Apache 1.2.19
 Tomcat 3.2.1 using mod_jk (also happens with 3.1 using
 mod_jserv)
 glibc 2.2.2
 
 thanks
 mac

Re: Linux IBM JDK + Tomcat + SMP hangs

[Chong Yu Meng]

Hello Edward :

I believe your glibc version is causing the problems you are seeing. I never
had any luck with glibc2.2 on my Caldera OpenLinux eDesktop 2.4 box. On the
IBM Java on Linux newsgroup, someone claims to be successful using the i386
version of glibc instead of i686, and I seem to remember someone on the same
newsgroup saying that Red Hat has issued a fix for it.
Hope this helps. For myself, I am still using glibc-2.1.3.

Regards,
Pascal Chong



- Original Message -
From: "Edward MacGillivray" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, March 23, 2001 8:35 AM
Subject: Re: Linux IBM JDK + Tomcat + SMP hangs


 On Sun, 7 Jan 2001 22:42:18 -0500
  "brien" [EMAIL PROTECTED] wrote:
  Hi,
 
  I've been having a really tough time to say the least
  trying to get the
  IBM JDK 1.3 to work on an SMP machine under linux.  I
  don't think my
  problem is unique.  The JDK hangs, consuming 99% of the
  CPU.
 
  From what I can tell, this problem is specific to the
  IBM JDK 1.3 on SMP
  machines.  I've read just about every message on the ibm
  linux java
  newsgroup, and the typical solution offered is always to
  install
  glibc 2.1.3-21.  Without doing this I had instant hangs
  as soon as I ran
  tomcat.  After updating glibc, the hangs take a little
  while to occur, but
  they are still present and persistent.
 
  Unfortunately, I'm also bound to using DB2 on the
  database side, and
  IBM tech support has stated that they do not support
  sun's jdk.
 
  If anyone can help me out I'd greatly appreciate it.
 
  my environment is:
  dual p3/866 + 512mb (dell poweredge 2450)
  redhat linux 6.2
  kernel 2.2.16 SMP
  glibc-2.1.3-21
  apache tomcat 3.2.1 (also tried 3.1.1)
 
  IBM JDK:
  java version "1.3.0"
  Java(TM) 2 Runtime Environment, Standard Edition (build
  1.3.0)
  Classic VM (build 1.3.0, J2RE 1.3.0 IBM build
  cx130-20001124 (JIT enabled:
  jitc))
 
  brien

 Has anyone else had this problem? because it appears as
 though I am having it too.  I have search my archive of
 Tomcat-User posts and the web for information on Tomcat
 hanging under linux SMP.  I found the above post but no
 replies to it.

 I have successfully installed the webapp I have to three
 different single processor computers but the one I want it
 on is multi proc and does not want to work.  I have been
 working with Tomcat 3.1 on all of the single proc boxes and
 initially used 3.1 on the multi proc.  The application was
 able to function just as it had on the other boxes but
 within a few minutes the application had hung and was not
 responding to jsp or servlet requests.  When the application
 got to this state though the Tomcat program was unable to
 stop itself, so I had to start killing processes.

 I then figured that possibly it was 3.1 that had a problem,
 so I went and got Tomcat 3.2.1.  However, this was pretty
 much a step backward, because with 3.2.1 the webapp is never
 able to work.  What's worse is that running the Tomcat
 shutdown script, even immediately after running the startup
 script, Tomcat is unable to stop itself.

 I can't say that I have much experience with Tomcat 3.2.1,
 however the mod_jk.log file indicates that it is finding a
 worker and the web browser accessing the webapp spins until
 apache times out.  I am confident that Apache is configured
 properly.

 The box's environ is
 3 * p-pro/200 + 256Mb
 Redhat Linux 6.2, kernel 2.2.14smp
 Apache 1.2.19
 Tomcat 3.2.1 using mod_jk (also happens with 3.1 using
 mod_jserv)
 glibc 2.2.2

 thanks
 mac

Re: IBM JDK 1.3 unexpected crash

[Holger Hartwig]

Hi 

have a look at http://www.volano.com/report.html

some interesting benchmarks

Holger

Todd Carmichael wrote:
 
 I have done some stress tests with Tomcat 3.2.1 and IBM VM 1.3 on a NT quad
 box.  This configuration performs quite well.  However, after a certain
 amount of time being stressed, the VM just crashes.  No informational,
 nothing just exits.  I have tried turning on verbose at the vm level with no
 luck.  Anyone had any experience with the IBM VM?
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, email: [EMAIL PROTECTED]

-- 
Holger Hartwig
b+m Informatik AG
http://www.bmiag.de, mailto:[EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

IBM JDK 1.3 unexpected crash

[Todd Carmichael]

I have done some stress tests with Tomcat 3.2.1 and IBM VM 1.3 on a NT quad
box.  This configuration performs quite well.  However, after a certain
amount of time being stressed, the VM just crashes.  No informational,
nothing just exits.  I have tried turning on verbose at the vm level with no
luck.  Anyone had any experience with the IBM VM?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Re: IBM JDK 1.3 unexpected crash

[David Crooke]

Interesting - we are currently running Sun's 1.2.2 VM and evaluating IBM 1.3 -
performance is pretty good, and so far no issues with the VM (Linux though, not
Windows).

Are you using a single VM with native threads, or just green? Conventional
wisdom use to be that green threads was the way to go for most web servlet
stuff.

Any JNI plugins? Some JDBC drivers can be flaky.

What about memory?

Todd Carmichael wrote:

 I have done some stress tests with Tomcat 3.2.1 and IBM VM 1.3 on a NT quad
 box.  This configuration performs quite well.  However, after a certain
 amount of time being stressed, the VM just crashes.  No informational,
 nothing just exits.  I have tried turning on verbose at the vm level with no
 luck.  Anyone had any experience with the IBM VM?

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, email: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Servlet preLoad difference between IBM JDK Sun JDK

[Kwan, Kenneth Y]

Recently I have tried IBM JDK1.3 to run my tomcat and everything seems ok.
However, when I wanted to pre-load a servlet from a package, I found that
the behavior of IBM¡¦s JDK  Sun¡¦s JDK are different where IBM¡¦s only
works with package.class while Sun¡¦s is package/class. Can anyone
advise which is correct?  

*** Cut from my web.xml ***

1)  Using Sun¡¦s JDK

servlet
servlet-name
MyInit
/servlet-name
servlet-class
Pkg/MyInit --diff in here
/servlet-class
load-on-startup
1
/load-on-startup
/servlet

2)  Using IBM¡¦s JDK
servlet
servlet-name
MyInit
/servlet-name
servlet-class
Pkg.MyInit  --diff in here
/servlet-class
load-on-startup
1
/load-on-startup
/servlet

Thanks

Kenneth

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Servlet preLoad difference between IBM JDK Sun JDK

[Kwan, Kenneth Y]

Recently I have tried IBM JDK1.3 to run my tomcat and everything seems ok.
However, when I wanted to pre-load a servlet from a package, I found that
the behavior of IBM¡¦s JDK  Sun¡¦s JDK are different where IBM¡¦s only
works with package.class while Sun¡¦s is package/class. Can anyone
advise which is correct?  

*** Cut from my web.xml ***

1)  Using Sun¡¦s JDK

servlet
servlet-name
MyInit
/servlet-name
servlet-class
Pkg/MyInit --diff in here
/servlet-class
load-on-startup
1
/load-on-startup
/servlet

2)  Using IBM¡¦s JDK
servlet
servlet-name
MyInit
/servlet-name
servlet-class
Pkg.MyInit  --diff in here
/servlet-class
load-on-startup
1
/load-on-startup
/servlet

Thanks

Kenneth

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Linux IBM JDK + Tomcat + SMP hangs

[brien]

Hi,

I've been having a really tough time to say the least trying to get the
IBM JDK 1.3 to work on an SMP machine under linux.  I don't think my
problem is unique.  The JDK hangs, consuming 99% of the CPU.

From what I can tell, this problem is specific to the IBM JDK 1.3 on SMP
machines.  I've read just about every message on the ibm linux java
newsgroup, and the typical solution offered is always to install
glibc 2.1.3-21.  Without doing this I had instant hangs as soon as I ran
tomcat.  After updating glibc, the hangs take a little while to occur, but
they are still present and persistent.

Unfortunately, I'm also bound to using DB2 on the database side, and
IBM tech support has stated that they do not support sun's jdk.

If anyone can help me out I'd greatly appreciate it.

my environment is:
dual p3/866 + 512mb (dell poweredge 2450)
redhat linux 6.2
kernel 2.2.16 SMP
glibc-2.1.3-21
apache tomcat 3.2.1 (also tried 3.1.1)

IBM JDK:
java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0)
Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cx130-20001124 (JIT enabled:
jitc))

brien

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]