tomcat connection/port problem

2003-07-24 Thread Astrid Wagner 
Hi,
I use tomcat 4.1.24, jdk 1.4.0 and Apache 1.3 on Solaris 8.
I am able to run a servlet with my configuration but when I submit in 
this first page I receive an errror.
The catalina.out log file simply says:
Jul 24, 2003 8:53:58 AM org.apache.commons.modeler.Registry loadRegistry
INFO: Loading registry information
Jul 24, 2003 8:53:58 AM org.apache.commons.modeler.Registry getRegistry
INFO: Creating new Registry instance
Jul 24, 2003 8:54:01 AM org.apache.commons.modeler.Registry getServer
INFO: Creating MBeanServer
Jul 24, 2003 8:54:04 AM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on port 8080
Starting service Tomcat-Standalone
Apache Tomcat/4.1.24
Jul 24, 2003 8:54:31 AM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on port 8080
Jul 24, 2003 8:54:32 AM org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on /0.0.0.0:8009
Jul 24, 2003 8:54:32 AM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=44/437  
config=/home/oraedt/app/oracle/product/9iAS_1.0.2.2/jaka
rta-tomcat-4.1.24/conf/jk2.properties
[EMAIL PROTECTED](): empty constructor:  // this is  printout 
from my code
[EMAIL PROTECTED]() start:  // this 
is  printout from my code
[EMAIL PROTECTED]() before getting system.mode: // this is 
printout from my code
Stopping service Tomcat-Standalone

The mod_jk printout says this :
[Thu Jul 24 09:01:26 2003]  [jk_ajp_common.c (642)]: sending to ajp13 #79
[Thu Jul 24 09:01:27 2003]  [jk_ajp_common.c (681)]: ERROR: can't 
receive the response mes
sage from tomcat, network problems or tomcat is down.
...

I remember having seen some port 8080 in use problem error message but 
not in the above test.
Apache is configured to run on a different port (7778) and server.xml has:
 Service name=Tomcat-Standalone
   !-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 --
   Connector className=org.apache.coyote.tomcat4.CoyoteConnector
  port=8080 minProcessors=5 maxProcessors=75
  enableLookups=true redirectPort=8443
  acceptCount=100 debug=0 connectionTimeout=2
  useURIValidationHack=false disableUploadTimeout=true /
   !-- Note : To disable connection timeouts, set connectionTimeout value
to -1 --
   !-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 --
   Connector className=org.apache.coyote.tomcat4.CoyoteConnector
  port=8009 minProcessors=5 maxProcessors=75
  enableLookups=true redirectPort=8443
  acceptCount=10 debug=0 connectionTimeout=0
  useURIValidationHack=false
  
protocolHandlerClassName=org.apache.jk.server.JkCoyoteHandler/
 /Service

Do I have to use a different connector? Why does the problem occur not 
right away if it is a port problem?
The error comes when I try to read an external java resource bundle 
(.properties file) even
though this may not have sth. to do with the error because the resource 
bundle is successfully found
prior to the error.
Thanks for your help.

BTW: Is it advisable to use the above configuration since we have an 
quite old version of Apache?
E.g Has anyone experienced mayor problems running relativly new versions 
of tomcat with an old 1.3
Apache version??

Astrid

RE: tomcat connection/port problem

2003-07-24 Thread Ralph Einfeldt 
What makes you so shure that you have a port problem ?
I think that you are searching in the wrong direction.

As I understand the log message mod_jk complains about
not getting an answer from tomcat after it successfully
sent a request to tomcat. At this point I cann't imagine 
a port problem (with that the request would have failed,
not the response)

This can have several causes:
- tomcat is down (e.g. jvm crash)
- the thread is not responding at all (deadlock)
- the thread is not responding quick enough (it take to long to create the response)
- ...

 -Original Message-
 From: Astrid Wagner [mailto:[EMAIL PROTECTED]
 Sent: Thursday, July 24, 2003 9:25 AM
 To: [EMAIL PROTECTED]
 Subject: tomcat connection/port problem
 
 
 [Thu Jul 24 09:01:26 2003]  [jk_ajp_common.c (642)]: sending 
 to ajp13 #79
 [Thu Jul 24 09:01:27 2003]  [jk_ajp_common.c (681)]: ERROR: can't 
 receive the response message from tomcat, network problems or tomcat is down.
 ...
 

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

Re: tomcat connection/port problem

2003-07-24 Thread Astrid Wagner 
Yes you are rigth.  The resource property was not found in
in the resource file that's why it crashed. I simply thought
I would get some java error (and not only that tomcat was shut down)
that would have made it easier for me to debug.
Sorry for the confusion.
Astrid
Ralph Einfeldt wrote:

What makes you so shure that you have a port problem ?
I think that you are searching in the wrong direction.
As I understand the log message mod_jk complains about
not getting an answer from tomcat after it successfully
sent a request to tomcat. At this point I cann't imagine 
a port problem (with that the request would have failed,
not the response)

This can have several causes:
- tomcat is down (e.g. jvm crash)
- the thread is not responding at all (deadlock)
- the thread is not responding quick enough (it take to long to create the response)
- ...
 

-Original Message-
From: Astrid Wagner [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 24, 2003 9:25 AM
To: [EMAIL PROTECTED]
Subject: tomcat connection/port problem
[Thu Jul 24 09:01:26 2003]  [jk_ajp_common.c (642)]: sending 
to ajp13 #79
[Thu Jul 24 09:01:27 2003]  [jk_ajp_common.c (681)]: ERROR: can't 
receive the response message from tomcat, network problems or tomcat is down.
...

   

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