tomcat connector 4.1.29 problem

2003-11-05 Thread Phillip Qin
I upgraded tomcat from 4.1.24 to 4.1.29. There are two issues with the new
connector.

1. If I use the old connector 4.1.24 with tomcat 4.1.29, I got this error
but tomcat ran fine.

INFO: APR not loaded, disabling jni components: java.io.IOException:
java.lang.UnsatisfiedLinkError:
/usr/local/j2sdk1.4.2/jre/lib/i386/libjkjni.so: libapr-0.so.0: cannot open
shared object file: No such file or directory

2. So I built new connector 4.1.29 and restarted tomcat. I got the following
error and tomcat won't serve my webapps.

INFO: JK2: ajp13 listening on /0.0.0.0:8009
[Wed Nov 05 11:04:41 2003] ( info ) [jk_config_file.c (280)]
config.update(): Can't find config file
${serverRoot}/conf/workers2.properties
[Wed Nov 05 11:04:41 2003] ( info ) [jk_logger_file.c (184)]  Initializing
log file stderr
[Wed Nov 05 11:04:41 2003] ( info ) [jk_shm.c (333)]  shm.init(): shm file
not specified
[Wed Nov 05 11:04:41 2003] ( info ) [jk_workerEnv.c (412)]  workerEnv.init()
ok ${serverRoot}/conf/workers2.properties
Nov 5, 2003 11:04:41 AM org.apache.jk.apr.AprImpl init
INFO: JK2: Initialized apr
Nov 5, 2003 11:04:41 AM org.apache.jk.apr.AprImpl init
INFO: JK2: Initialized apr
Nov 5, 2003 11:04:41 AM org.apache.jk.server.JkMain start

workers2.properties is located in /usr/local/apache2/conf and readable by
everyone. I specified shm file in both jk2.properties and
workers2.properties. I found similar postings and replies on the list. That
didn't satisfy me. One suggestion is wrong location. If location is a
problem, why didn't 4.1.24 connector complain?

Does any body have a solution?



Re: tomcat connector 4.1.29 problem

2003-11-05 Thread Jeff Tulley
When you say you built the new connector, where did you get your source?
 From the HEAD of the repository?  I know there is some work going on
right now on the mod_jk2 connector, to move it to using the APR library
exclusively.  You might have gotten a version that is in transition.

Of course, the error on the older connector seems to indicate an APR
problem as well.

 [EMAIL PROTECTED] 11/5/03 9:36:15 AM 
I upgraded tomcat from 4.1.24 to 4.1.29. There are two issues with the
new
connector.

1. If I use the old connector 4.1.24 with tomcat 4.1.29, I got this
error
but tomcat ran fine.

INFO: APR not loaded, disabling jni components: java.io.IOException:
java.lang.UnsatisfiedLinkError:
/usr/local/j2sdk1.4.2/jre/lib/i386/libjkjni.so: libapr-0.so.0: cannot
open
shared object file: No such file or directory

2. So I built new connector 4.1.29 and restarted tomcat. I got the
following
error and tomcat won't serve my webapps.

INFO: JK2: ajp13 listening on /0.0.0.0:8009
[Wed Nov 05 11:04:41 2003] ( info ) [jk_config_file.c (280)]
config.update(): Can't find config file
${serverRoot}/conf/workers2.properties
[Wed Nov 05 11:04:41 2003] ( info ) [jk_logger_file.c (184)] 
Initializing
log file stderr
[Wed Nov 05 11:04:41 2003] ( info ) [jk_shm.c (333)]  shm.init(): shm
file
not specified
[Wed Nov 05 11:04:41 2003] ( info ) [jk_workerEnv.c (412)] 
workerEnv.init()
ok ${serverRoot}/conf/workers2.properties
Nov 5, 2003 11:04:41 AM org.apache.jk.apr.AprImpl init
INFO: JK2: Initialized apr
Nov 5, 2003 11:04:41 AM org.apache.jk.apr.AprImpl init
INFO: JK2: Initialized apr
Nov 5, 2003 11:04:41 AM org.apache.jk.server.JkMain start

workers2.properties is located in /usr/local/apache2/conf and readable
by
everyone. I specified shm file in both jk2.properties and
workers2.properties. I found similar postings and replies on the list.
That
didn't satisfy me. One suggestion is wrong location. If location is a
problem, why didn't 4.1.24 connector complain?

Does any body have a solution?


Jeff Tulley  ([EMAIL PROTECTED])
(801)861-5322
Novell, Inc., The Leading Provider of Net Business Solutions
http://www.novell.com

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



RE: tomcat connector 4.1.29 problem

2003-11-05 Thread Phillip Qin
I downloaded connector source from 

http://apache.mirror.secondchapter.info/jakarta/tomcat-4/v4.1.29/src/

Please ignore issue 1 since I don't use jni.

-Original Message-
From: Jeff Tulley [mailto:[EMAIL PROTECTED] 
Sent: November 5, 2003 1:52 PM
To: [EMAIL PROTECTED]
Subject: Re: tomcat connector 4.1.29 problem

When you say you built the new connector, where did you get your source?
 From the HEAD of the repository?  I know there is some work going on
right now on the mod_jk2 connector, to move it to using the APR library
exclusively.  You might have gotten a version that is in transition.

Of course, the error on the older connector seems to indicate an APR
problem as well.

 [EMAIL PROTECTED] 11/5/03 9:36:15 AM 
I upgraded tomcat from 4.1.24 to 4.1.29. There are two issues with the
new
connector.

1. If I use the old connector 4.1.24 with tomcat 4.1.29, I got this
error
but tomcat ran fine.

INFO: APR not loaded, disabling jni components: java.io.IOException:
java.lang.UnsatisfiedLinkError:
/usr/local/j2sdk1.4.2/jre/lib/i386/libjkjni.so: libapr-0.so.0: cannot
open
shared object file: No such file or directory

2. So I built new connector 4.1.29 and restarted tomcat. I got the
following
error and tomcat won't serve my webapps.

INFO: JK2: ajp13 listening on /0.0.0.0:8009
[Wed Nov 05 11:04:41 2003] ( info ) [jk_config_file.c (280)]
config.update(): Can't find config file
${serverRoot}/conf/workers2.properties
[Wed Nov 05 11:04:41 2003] ( info ) [jk_logger_file.c (184)] 
Initializing
log file stderr
[Wed Nov 05 11:04:41 2003] ( info ) [jk_shm.c (333)]  shm.init(): shm
file
not specified
[Wed Nov 05 11:04:41 2003] ( info ) [jk_workerEnv.c (412)] 
workerEnv.init()
ok ${serverRoot}/conf/workers2.properties
Nov 5, 2003 11:04:41 AM org.apache.jk.apr.AprImpl init
INFO: JK2: Initialized apr
Nov 5, 2003 11:04:41 AM org.apache.jk.apr.AprImpl init
INFO: JK2: Initialized apr
Nov 5, 2003 11:04:41 AM org.apache.jk.server.JkMain start

workers2.properties is located in /usr/local/apache2/conf and readable
by
everyone. I specified shm file in both jk2.properties and
workers2.properties. I found similar postings and replies on the list.
That
didn't satisfy me. One suggestion is wrong location. If location is a
problem, why didn't 4.1.24 connector complain?

Does any body have a solution?


Jeff Tulley  ([EMAIL PROTECTED])
(801)861-5322
Novell, Inc., The Leading Provider of Net Business Solutions
http://www.novell.com

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