jk2 problem
It seems as though my jk2 configuration isn't failing over properly. If a tomcat machine drops, it compensates properly. However, if a single application on one of the tomcat machines fails then apache/jk2 keeps that faulty app in the mix. When a user gets directed to a tomcat instance where the app is working, all is fine. However, jk2 still continues to route requests to the machine where the app is broken or missing.. is there something I can do to fix this? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat-IIS-JK2 : Problem on POST with Transfer-Encoding: chunked
I have successfully configured JK2 to have IIS working with Tomcat. However, I am having a problem: My servlet receives a HTTP request from client which contains an XML document in the request body. Whenever I post a request thru IIS with a header Transfer-Encoding: chunked, the body of the request is missing (HttpServletRequest.getInputStream() is empty) and my program can not continue because the XML document is not there. This works fine if I directly go to Tomcat. If I set the Content-Length to the header, I can retrieve the request body alright. Since the xml doc is dynamically generated each time and vary in size, I have to send it in chunks. There are some error messages in the JK2 log: Error: [jk_channel_apr_socket.c (488)]: channelApr.receive(): Error receiving message body -1 0 Error: [jk_workerEnv.c (492)]: workerEnv.processCallbacks() Error reading reply Error: [jk_worker_ajp13.c (546)]: ajp13.service() ajpGetReply recoverable error 12 I don't know which part I did wrong. Is the IIS configurations? or JK2? Please help and point me some directions. I am using: IIS5.0 Tomcat 4.1.30 JK2 2.0.4 and here is one of my sample request shown in the tcptrace: - Header POST /hctest/servlet/HandCloudServer HTTP/1.1 marshaller: HCLOUDSYNCMARSHALLER User-Agent: Jakarta Commons-HttpClient/2.0rc3 Host: localhost:8081 Transfer-Encoding: chunked Body 18c ?xml version=1.0 encoding=UTF-8?methodCallmethodNamesearch/methodNameparamsparams(Product_Id=100)/s/paramparamsProduct/s/paramparamarray/array/paramparamdt2004-07-22T21:50:20/dt/paramparamint0/int/paramparamint-1/int/param/params/methodCall 0 - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
jk2 problem (newbie)
Hello, I'm trying to integrate tomcat 5 to apache 2.0.48. When I start apache after tomcat, if I try to access jsp-examples, I get this error message: * Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, [EMAIL PROTECTED] and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. My jkstatus look good, it reports the error. here are my jk2.properties handler.list=apr,request,channelUnix # UNIX Domain socket location channelUnix.file=/usr/local/apache/jakarta-tomcat-5.0.19/work/jk2.socket # Dynamic Library serverRoot=/etc/httpd apr.NativeSo=/etc/httpd/modules/libjkjni.so *** and here is my workers2.properties [shm] info=Scoreboard. Required for reconfiguration and status with multiprocess servers file=/usr/local/apache/jakarta-tomcat-5.0.19/logs/jk2.shm size=1048576 debug=0 disabled=0 # UNIX domain socket [channel.un:/usr/local/apache/jakarta-tomcat-5.0.19/work/jk2.socket] tomcatId=localhost:8009 debug=0 # define the worker [ajp13://usr/local/apache/jakarta-tomcat-5.0.19/work/jk2.socket] channel=channel.un:/usr/local/apache/jakarta-tomcat-5.0.19/work/jk2.socket # Announce a status worker [status:status] info=Status worker. Displays runtime information. [uri:/jkstatus/*] group=status:status # Uri mapping [uri:/jsp-examples/*] * Here is my catalina.out *** Apr 24, 2004 9:27:58 AM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Apr 24, 2004 9:27:58 AM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 1684 ms Apr 24, 2004 9:27:59 AM org.apache.catalina.core.StandardService start INFO: Starting service Catalina Apr 24, 2004 9:27:59 AM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/5.0.19 Apr 24, 2004 9:27:59 AM org.apache.catalina.core.StandardHost start INFO: XML validation disabled Apr 24, 2004 9:27:59 AM org.apache.catalina.core.StandardHost getDeployer INFO: Create Host deployer for direct deployment ( non-jmx ) Apr 24, 2004 9:27:59 AM org.apache.catalina.core.StandardHostDeployer install INFO: Processing Context configuration file URL file:/usr/local/apache/jakarta-tomcat-5.0.19/conf/Catalina/localhost/admin.xml Apr 24, 2004 9:28:00 AM org.apache.struts.util.PropertyMessageResources init INFO: Initializing, config='org.apache.struts.util.LocalStrings', returnNull=true Apr 24, 2004 9:28:00 AM org.apache.struts.util.PropertyMessageResources init INFO: Initializing, config='org.apache.struts.action.ActionResources', returnNull=true Apr 24, 2004 9:28:00 AM org.apache.struts.util.PropertyMessageResources init INFO: Initializing, config='org.apache.webapp.admin.ApplicationResources', returnNull=true Apr 24, 2004 9:28:02 AM org.apache.catalina.core.StandardHostDeployer install INFO: Processing Context configuration file URL file:/usr/local/apache/jakarta-tomcat-5.0.19/conf/Catalina/localhost/balancer.xml Apr 24, 2004 9:28:03 AM org.apache.catalina.core.StandardHostDeployer install INFO: Processing Context configuration file URL file:/usr/local/apache/jakarta-tomcat-5.0.19/conf/Catalina/localhost/manager.xml Apr 24, 2004 9:28:03 AM org.apache.catalina.core.StandardHostDeployer install INFO: Installing web application at context path from URL file:/usr/local/apache/jakarta-tomcat-5.0.19/webapps/ROOT Apr 24, 2004 9:28:03 AM org.apache.catalina.core.StandardHostDeployer install INFO: Installing web application at context path /jsp-examples from URL file:/usr/local/apache/jakarta-tomcat-5.0.19/webapps/jsp-examples Apr 24, 2004 9:28:03 AM org.apache.catalina.core.StandardHostDeployer install INFO: Installing web application at context path /servlets-examples from URL file:/usr/local/apache/jakarta-tomcat-5.0.19/webapps/servlets-examples Apr 24, 2004 9:28:03 AM org.apache.catalina.core.StandardHostDeployer install INFO: Installing web application at context path /tomcat-docs from URL file:/usr/local/apache/jakarta-tomcat-5.0.19/webapps/tomcat-docs Apr 24, 2004 9:28:03 AM org.apache.catalina.core.StandardHostDeployer install INFO: Installing web application at context path /webdav from URL file:/usr/local/apache/jakarta-tomcat-5.0.19/webapps/webdav Apr 24, 2004 9:28:03 AM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Apr 24, 2004 9:28:04 AM org.apache.jk.server.JkMain start INFO: APR not loaded, disabling jni components: java.io.IOException: java.lang.UnsatisfiedLinkError: /usr/lib/httpd/modules/libjkjni.so: /usr/lib/httpd/modules/libjkjni.so: undefined symbol: apr_md5_final Apr 24, 2004 9:28:04 AM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on 0.0.0.0/0.0.0.0:8009 Apr 24, 2004 9:28:04 AM
JK2 Problem
Hello Everyone, I am having a configuration issue/question with the JK2 connector. I am running win 2k server w/IIS 5.0. I currently have JK 1 configured to proxy requests from IIS to a tomcat instance which is on a different server, however I need to upgrade to JK2 because the connector doesn't pass the query strings correctly. I have been trying to figure this out for a couple of weeks but It doesn't look like this is possible using the JK2 connector or I'm just not getting it. Has anyone done this? Can it be done? Thanks in advance, Justin
RE: JK2 Problem
I got a win2k server with iis5 working using this howto: http://www.reynir.net/tomcat/tomcat_IIS_service_jk2.html -Original Message- From: Woody, Justin D Mr NMR [mailto:[EMAIL PROTECTED] Sent: 27 August 2003 16:30 To: '[EMAIL PROTECTED]' Subject: JK2 Problem Hello Everyone, I am having a configuration issue/question with the JK2 connector. I am running win 2k server w/IIS 5.0. I currently have JK 1 configured to proxy requests from IIS to a tomcat instance which is on a different server, however I need to upgrade to JK2 because the connector doesn't pass the query strings correctly. I have been trying to figure this out for a couple of weeks but It doesn't look like this is possible using the JK2 connector or I'm just not getting it. Has anyone done this? Can it be done? Thanks in advance, Justin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
tomcat4.1 apache2 jk2 problem
!-- Server Configuration File for Tomcat 4.0 on Debian You can find more complete examples in /usr/share/doc/tomcat4/examples/. -- !-- A Server is a singleton element that represents the entire JVM, which may contain one or more Service instances. The Server listens for a shutdown command on the indicated port. Note: A Server is not itself a Container, so you may not define subcomponents such as Valves or Loggers at this level. -- Server port=8005 shutdown=SHUTDOWN debug=0 !-- A Service is a collection of one or more Connectors that share a single Container (and therefore the web applications visible within that Container). Normally, that Container is an Engine, but this is not required. Note: A Service is not itself a Container, so you may not define subcomponents such as Valves or Loggers at this level. -- !-- Define the Tomcat Stand-Alone Service -- Service name=Tomcat-Standalone !-- A Connector represents an endpoint by which requests are received and responses are returned. Each Connector passes requests on to the associated Container (normally an Engine) for processing. By default, a non-SSL HTTP/1.1 Connector is established on port 8180. You can also enable an SSL HTTP/1.1 Connector on port 8443 by following the instructions below and uncommenting the second Connector entry. SSL support requires the following steps (see the SSL Config HOWTO in the Tomcat 4.0 documentation bundle for more detailed instructions): * Download and install JSSE 1.0.2 or later, and put the JAR files into $JAVA_HOME/jre/lib/ext. * Execute: $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA with a password value of changeit for both the certificate and the keystore itself. By default, DNS lookups are enabled when a web application calls request.getRemoteHost(). This can have an adverse impact on performance, so you can disable it by setting the enableLookups attribute to false. When DNS lookups are disabled, request.getRemoteHost() will return the String version of the IP address of the remote client. -- !-- 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/ Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8180 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=2/ !-- Note : To disable connection timeouts, set connectionTimeout value to -1 -- !-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8180 -- !-- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8180 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=2/ -- !-- Define an SSL HTTP/1.1 Connector on port 8443 -- !-- Connector className=org.apache.catalina.connector.http.HttpConnector port=8443 minProcessors=5 maxProcessors=75 enableLookups=true acceptCount=10 debug=0 scheme=https secure=true Factory className=org.apache.catalina.net.SSLServerSocketFactory clientAuth=false protocol=TLS/ /Connector -- !-- Define an AJP 1.3 Connector on port 8009 -- !-- Debian specific note: If you enable this connector you must disable it in the tomcat (Tomcat 3.x) package. The package for the Apache connector module is libapache-mod-jk -- !-- Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=75 acceptCount=10 debug=0 address=127.0.0.1/ -- !-- Define a Proxied HTTP/1.1 Connector on port 8081 -- !-- See proxy documentation for more information about using this. -- !-- Connector className=org.apache.catalina.connector.http.HttpConnector port=8082 minProcessors=5 maxProcessors=75 enableLookups=true acceptCount=10 debug=0 connectionTimeout=6 proxyPort=80/ -- !-- Define a non-SSL HTTP/1.0 Test Connector on port 8082 -- !-- Connector className=org.apache.catalina.connector.http10.HttpConnector port=8083 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0/ -- !-- An Engine
Re: tomcat4.1 apache2 jk2 problem
Pieter Laeremans [EMAIL PROTECTED] writes: Ok, my jk2.properties and worker.properties files did get stripped here is there contents: jk2.properties __ # list of needed handlers. handler.list=apr,channelSocket,channelUnix,request # Set the default port for the channelSocket channelSocket.port=8009 # State where the UNIX domain socket is located channelUnix.file=/usr/share/tomcat4/work/jk2.socket # Dynamic library #serverRoot=/usr/local/apache2 #apr.NativeSo=/usr/local/tomcat/lib/libjkjni.so /etc/apache2/conf/workers2.properties _ # Shared memory handling. Needs to be set. [shm] file=/tmp/shm.file #size=1048576 size=104 # Example socket channel, explicitly set port and host. [channel.socket:localhost:8009] port=8009 host=127.0.0.1 # Example UNIX domain socket [channel.un:/usr/share/tomcat4/work/jk2.socket] tomcatId=localhost:8009 debug=0 # define the worker [ajp13:localhost:8009] channel=channel.un:/usr/share/tomcat4/work/jk2.socket # To use the TCP/IP socket instead, just comment out the above # line, and uncomment the one below #channel=channel.socket:localhost:8009 # Announce a status worker [status:status] # Uri mapping [uri:/examples/*] #worker=ajp13:localhost:8009 worker=ajp13:/usr/share/tomcat4/work/jk2.socket [uri:/status/*] worker=status:status [uri:/tomcat-docs/*] #worker=ajp13:localhost:8009 worker=ajp13:/usr/share/tomcat4/work/jk2.socket - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
CiscoLB jk2 problem
I need to let apache fail nicely when a tomcat instance has crashed, been stopped or is being restarted. Right now this is what happens through the jk2 connector: I stop apache:10061 - Connection refused I stop one tomcat webapp: HTTP Status 404 I stop the tomcat server: 500 Internal Server Error Directly to tomcat: I stop apache:Nothing happens, not using it :) I stop one tomcat webapp: HTTP Status 404 I stop the tomcat server: 10061 - Connection refused I would like to see apache return 10061 - Connection refused when I stop tomcat instead of error 500 because this can cause problems with the cisco load balancer noticing that a server has dropped out of the loop. We are doing a simple one apache - one tomcat setup on 6 machines that are HW load balanced. Each tomcat has multiple webapps each accessible through a virtual host. Do I just need to switch to JNI? My current workers2.properties: only at beginnin. In production uncomment it out [logger.apache2] level=DEBUG [shm] file=/ApacheGroup/Apache2/logs/jk2.shm size=1048576 # Example socket channel, override port and host. [channel.socket:localhost:8009] port=8009 host=wbdevweb5.guidestar.net # define the worker [ajp13:localhost:8009] channel=channel.socket:localhost:8009 # define the worker [status:status] # Uri mapping [uri:/jkstatus/*] worker=status:status # Uri mapping [uri:bdevweb5.guidestar.net/*] worker=ajp13:localhost:8009 [uri:bdevweb5/*] worker=ajp13:localhost:8009 My jk2.properties: handler.list=channelSocket,request channelSocket.port=8009 --Angus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: CiscoLB jk2 problem
Hi, This is why you want to spread your application across two or more tomcats. I'm not sure if you can tweak the behavior of the error because what you are getting is indeed a internal server error. If you are going to load balance you should try to load balance all the way down the stack. Try giving each apache two or more tomcats to send sessions too. JK2 will see that tomcat A is down and move to tomcat B. Your application monitoring software should then kick of an alert to notify someone that a tomcat is down and might need human intervention. -e On Thu, 31 Jul 2003, Angus Mezick wrote: I need to let apache fail nicely when a tomcat instance has crashed, been stopped or is being restarted. Right now this is what happens through the jk2 connector: I stop apache:10061 - Connection refused I stop one tomcat webapp: HTTP Status 404 I stop the tomcat server: 500 Internal Server Error Directly to tomcat: I stop apache:Nothing happens, not using it :) I stop one tomcat webapp: HTTP Status 404 I stop the tomcat server: 10061 - Connection refused I would like to see apache return 10061 - Connection refused when I stop tomcat instead of error 500 because this can cause problems with the cisco load balancer noticing that a server has dropped out of the loop. We are doing a simple one apache - one tomcat setup on 6 machines that are HW load balanced. Each tomcat has multiple webapps each accessible through a virtual host. Do I just need to switch to JNI? My current workers2.properties: only at beginnin. In production uncomment it out [logger.apache2] level=DEBUG [shm] file=/ApacheGroup/Apache2/logs/jk2.shm size=1048576 # Example socket channel, override port and host. [channel.socket:localhost:8009] port=8009 host=wbdevweb5.guidestar.net # define the worker [ajp13:localhost:8009] channel=channel.socket:localhost:8009 # define the worker [status:status] # Uri mapping [uri:/jkstatus/*] worker=status:status # Uri mapping [uri:bdevweb5.guidestar.net/*] worker=ajp13:localhost:8009 [uri:bdevweb5/*] worker=ajp13:localhost:8009 My jk2.properties: handler.list=channelSocket,request channelSocket.port=8009 --Angus - 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: CiscoLB jk2 problem
Dang, I forgot to mention that we have 6 machines set up like this (or to be set up like this). -Original Message- From: Eric J. Pinnell [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2003 2:18 PM To: Tomcat Users List Subject: Re: CiscoLB jk2 problem Hi, This is why you want to spread your application across two or more tomcats. I'm not sure if you can tweak the behavior of the error because what you are getting is indeed a internal server error. If you are going to load balance you should try to load balance all the way down the stack. Try giving each apache two or more tomcats to send sessions too. JK2 will see that tomcat A is down and move to tomcat B. Your application monitoring software should then kick of an alert to notify someone that a tomcat is down and might need human intervention. -e On Thu, 31 Jul 2003, Angus Mezick wrote: I need to let apache fail nicely when a tomcat instance has crashed, been stopped or is being restarted. Right now this is what happens through the jk2 connector: I stop apache:10061 - Connection refused I stop one tomcat webapp: HTTP Status 404 I stop the tomcat server: 500 Internal Server Error Directly to tomcat: I stop apache:Nothing happens, not using it :) I stop one tomcat webapp: HTTP Status 404 I stop the tomcat server: 10061 - Connection refused I would like to see apache return 10061 - Connection refused when I stop tomcat instead of error 500 because this can cause problems with the cisco load balancer noticing that a server has dropped out of the loop. We are doing a simple one apache - one tomcat setup on 6 machines that are HW load balanced. Each tomcat has multiple webapps each accessible through a virtual host. Do I just need to switch to JNI? My current workers2.properties: only at beginnin. In production uncomment it out [logger.apache2] level=DEBUG [shm] file=/ApacheGroup/Apache2/logs/jk2.shm size=1048576 # Example socket channel, override port and host. [channel.socket:localhost:8009] port=8009 host=wbdevweb5.guidestar.net # define the worker [ajp13:localhost:8009] channel=channel.socket:localhost:8009 # define the worker [status:status] # Uri mapping [uri:/jkstatus/*] worker=status:status # Uri mapping [uri:bdevweb5.guidestar.net/*] worker=ajp13:localhost:8009 [uri:bdevweb5/*] worker=ajp13:localhost:8009 My jk2.properties: handler.list=channelSocket,request channelSocket.port=8009 --Angus - 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]
RE: CiscoLB jk2 problem
No, I think you mentioned that. :) -e On Thu, 31 Jul 2003, Angus Mezick wrote: Dang, I forgot to mention that we have 6 machines set up like this (or to be set up like this). -Original Message- From: Eric J. Pinnell [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2003 2:18 PM To: Tomcat Users List Subject: Re: CiscoLB jk2 problem Hi, This is why you want to spread your application across two or more tomcats. I'm not sure if you can tweak the behavior of the error because what you are getting is indeed a internal server error. If you are going to load balance you should try to load balance all the way down the stack. Try giving each apache two or more tomcats to send sessions too. JK2 will see that tomcat A is down and move to tomcat B. Your application monitoring software should then kick of an alert to notify someone that a tomcat is down and might need human intervention. -e On Thu, 31 Jul 2003, Angus Mezick wrote: I need to let apache fail nicely when a tomcat instance has crashed, been stopped or is being restarted. Right now this is what happens through the jk2 connector: I stop apache:10061 - Connection refused I stop one tomcat webapp: HTTP Status 404 I stop the tomcat server: 500 Internal Server Error Directly to tomcat: I stop apache:Nothing happens, not using it :) I stop one tomcat webapp: HTTP Status 404 I stop the tomcat server: 10061 - Connection refused I would like to see apache return 10061 - Connection refused when I stop tomcat instead of error 500 because this can cause problems with the cisco load balancer noticing that a server has dropped out of the loop. We are doing a simple one apache - one tomcat setup on 6 machines that are HW load balanced. Each tomcat has multiple webapps each accessible through a virtual host. Do I just need to switch to JNI? My current workers2.properties: only at beginnin. In production uncomment it out [logger.apache2] level=DEBUG [shm] file=/ApacheGroup/Apache2/logs/jk2.shm size=1048576 # Example socket channel, override port and host. [channel.socket:localhost:8009] port=8009 host=wbdevweb5.guidestar.net # define the worker [ajp13:localhost:8009] channel=channel.socket:localhost:8009 # define the worker [status:status] # Uri mapping [uri:/jkstatus/*] worker=status:status # Uri mapping [uri:bdevweb5.guidestar.net/*] worker=ajp13:localhost:8009 [uri:bdevweb5/*] worker=ajp13:localhost:8009 My jk2.properties: handler.list=channelSocket,request channelSocket.port=8009 --Angus - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: CiscoLB jk2 problem
When Apache detects Tomcat is down, it has already accepted the connection (it cannot refuse it anymore). Otherwise, how would Apache know that the request was to forward to Tomcat, if it hadn't accepted the connection, and received the request through it? -- That means: You simply cannot. Protocol design prohibits it. Antonio Fiol Angus Mezick wrote: I need to let apache fail nicely when a tomcat instance has crashed, been stopped or is being restarted. Right now this is what happens through the jk2 connector: I stop apache:10061 - Connection refused I stop one tomcat webapp: HTTP Status 404 I stop the tomcat server: 500 Internal Server Error Directly to tomcat: I stop apache:Nothing happens, not using it :) I stop one tomcat webapp: HTTP Status 404 I stop the tomcat server: 10061 - Connection refused I would like to see apache return 10061 - Connection refused when I stop tomcat instead of error 500 because this can cause problems with the cisco load balancer noticing that a server has dropped out of the loop. We are doing a simple one apache - one tomcat setup on 6 machines that are HW load balanced. Each tomcat has multiple webapps each accessible through a virtual host. Do I just need to switch to JNI? My current workers2.properties: only at beginnin. In production uncomment it out [logger.apache2] level=DEBUG [shm] file=/ApacheGroup/Apache2/logs/jk2.shm size=1048576 # Example socket channel, override port and host. [channel.socket:localhost:8009] port=8009 host=wbdevweb5.guidestar.net # define the worker [ajp13:localhost:8009] channel=channel.socket:localhost:8009 # define the worker [status:status] # Uri mapping [uri:/jkstatus/*] worker=status:status # Uri mapping [uri:bdevweb5.guidestar.net/*] worker=ajp13:localhost:8009 [uri:bdevweb5/*] worker=ajp13:localhost:8009 My jk2.properties: handler.list=channelSocket,request channelSocket.port=8009 --Angus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] smime.p7s Description: S/MIME Cryptographic Signature
mod jk2 problem, segmetation fault
Hi there,
I have a problem with integrating tomcat and apache using jk2.
System configuration: suse 8.1
apache 1.3.26
tomcat 4.1.24
Correct me if I am wrong, but to establish link bw. apache and tomcat I
need to:
- add a connector in server.xml
Connector acceptCount=10 bufferSize=2048
className=org.apache.ajp.tomcat4.Ajp13Connector
port=8009 minProcessors=5 maxProcessors=75 debug=0
enableLookups=true
Factory
className=org.apache.catalina.net.DefaultServerSocketFactory/
/Connector
- load jk2 module in httpd.conf
- configure workers2.properties
[shm]
file=/srv/www/logs/jk2.shm
[channel.socket:192.168.230.14:8009]
info=Ajp13 forwarding over socket
tomcatId=192.168.230.14:8009
[uri:/examples/*]
info=Map the whole webapp
- configure jk2.properties
# Set the desired handler list
# handler.list=apr,request,channelJni
#
# Override the default port for the socketChannel
# channelSocket.port=8009
# Default:
# channelUnix.file=${jkHome}/work/jk2.socket
# Just to check if the the config is working
shm.file=/srv/www/logs/jk2.shm
# In order to enable jni use any channelJni directive
# channelJni.disabled = 0
# And one of the following directives:
# apr.jniModeSo=/opt/apache2/modules/mod_jk2.so
# If set to inprocess the mod_jk2 will Register natives itself
# This will enable the starting of the Tomcat from mod_jk2
# apr.jniModeSo=inprocess
It seems that in tomcat everything is fine (catalina.out after starting
tomcat ends with:
2003-07-01 17:24:33 HttpConnector[8443] Starting background thread
2003-07-01 17:24:34 HttpProcessor[8443][0] Starting background thread
2003-07-01 17:24:34 HttpProcessor[8443][1] Starting background thread
2003-07-01 17:24:34 HttpProcessor[8443][2] Starting background thread
2003-07-01 17:24:34 HttpProcessor[8443][3] Starting background thread
2003-07-01 17:24:34 HttpProcessor[8443][4] Starting background thread
2003-07-01 17:24:34 Ajp13Connector[8009] Opening server socket on all host
IP addresses
2003-07-01 17:24:34 Ajp13Connector[8009] Starting background thread
2003-07-01 17:24:34 Ajp13Processor[8009][0] Starting background thread
2003-07-01 17:24:34 Ajp13Processor[8009][1] Starting background thread
2003-07-01 17:24:34 Ajp13Processor[8009][2] Starting background thread
2003-07-01 17:24:34 Ajp13Processor[8009][3] Starting background thread
2003-07-01 17:24:34 Ajp13Processor[8009][4] Starting background thread
However in apache, there are some errors after restart:
[Tue Jul 01 14:47:08 2003] ( info) [mod_jk2.c (284)]: mod_jk child init
[Tue Jul 01 14:47:08 2003] ( info) [mod_jk2.c (292)]: mod_jk.post_config()
init worker env
[Tue Jul 01 14:47:08 2003] (error) [jk_logger_file.c (171)]: Can't open
log file ${serverRoot}/logs/mod_jk.log
[Tue Jul 01 14:47:08 2003] ( info) [jk_config_file.c (320)]: cfg.update()
Updating config /srv/www//conf/workers2.properties
[Tue Jul 01 14:47:08 2003] ( info) [jk_config_file.c (331)]:
config.setConfig(): Reading properties /srv/www//conf/workers2.
[Tue Jul 01 14:47:08 2003] (error) [jk_logger_file.c (171)]: Can't open
log file ${serverRoot}/logs/mod_jk.log
[Tue Jul 01 14:47:08 2003] (debug) [jk_uriMap.c (315)]: uriMap.init()
Fixing Host *
[Tue Jul 01 14:47:08 2003] ( info) [jk_workerEnv.c (403)]:
workerEnv.init() ok /srv/www//conf/workers2.properties
Create config for main host
[Tue Jul 01 14:47:09 2003] ( info) [mod_jk2.c (284)]: mod_jk child init
[Tue Jul 01 14:47:09 2003] ( info) [mod_jk2.c (292)]: mod_jk.post_config()
init worker env
[Tue Jul 01 14:47:09 2003] (error) [jk_logger_file.c (171)]: Can't open
log file ${serverRoot}/logs/mod_jk.log
[Tue Jul 01 14:47:09 2003] ( info) [jk_config_file.c (320)]: cfg.update()
Updating config /srv/www//conf/workers2.properties
[Tue Jul 01 14:47:09 2003] ( info) [jk_config_file.c (331)]:
config.setConfig(): Reading properties /srv/www//conf/workers2.
[Tue Jul 01 14:47:09 2003] (error) [jk_logger_file.c (171)]: Can't open
log file ${serverRoot}/logs/mod_jk.log
[Tue Jul 01 14:47:09 2003] (debug) [jk_uriMap.c (315)]: uriMap.init()
Fixing Host *
[Tue Jul 01 14:47:09 2003] ( info) [jk_workerEnv.c (403)]:
workerEnv.init() ok /srv/www//conf/workers2.properties
[Tue Jul 1 16:47:10 2003] [notice] Apache/1.3.26 (Linux/SuSE)
mod_jk2/2.0.0 configured -- resuming normal operations
[Tue Jul 1 16:47:10 2003] [notice] suEXEC mechanism enabled (wrapper:
/usr/sbin/suexec)
[Tue Jul 1 16:47:10 2003] [notice] Accept mutex: sysvsem (Default: sysvsem)
Finally when I try to open a page from tomcat without specifying port 8080
in apache a following error is added:
[Tue Jul 1 16:47:49 2003] [notice] child pid 16282 exit signal
Segmentation fault (11)
While in tomcat there is no information, that some page was requested.
Does anyone have any idea what is causing this Segmentation fault?
Regards,
Przemek
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
RE: mod jk2 problem, segmetation fault
Howdy,
However in apache, there are some errors after restart:
[Tue Jul 01 14:47:08 2003] ( info) [mod_jk2.c (284)]: mod_jk child
init
[Tue Jul 01 14:47:08 2003] ( info) [mod_jk2.c (292)]:
mod_jk.post_config()
init worker env
[Tue Jul 01 14:47:08 2003] (error) [jk_logger_file.c (171)]: Can't
open
log file ${serverRoot}/logs/mod_jk.log
[Tue Jul 01 14:47:08 2003] ( info) [jk_config_file.c (320)]:
cfg.update()
Updating config /srv/www//conf/workers2.properties
[Tue Jul 01 14:47:08 2003] ( info) [jk_config_file.c (331)]:
config.setConfig(): Reading properties /srv/www//conf/workers2.
[Tue Jul 01 14:47:08 2003] (error) [jk_logger_file.c (171)]: Can't
open
log file ${serverRoot}/logs/mod_jk.log
Stop. You might be in better shape if you can actually write to the log
file.
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: mod jk2 problem, segmetation fault
Step 1 is unnecessary.
Tomcat comes with a JK2 compatible connector enabled by default on port
8009. The class name for this connector is CoyoteConnector.
Ajp13Connector is for JK and is incompatible with JK2...it will never work.
If you need to use JK2, you don't need to do anything to server.xml except
make sure your Hosts and your Contexts are correct, everything else is done
on the Apache configuration side.
I don't know of any JK2 binaries for SuSe, so unless you built your own, I
would say your problem is a combination of an incompatible Apache module
and the configuration of Ajp13Connector.
Also, I am still not clear on the compatibility of JK2 (mod_jk2) with
Apache 1.x. My guess is you would be better off with mod_jk (JK).
John
On Tue, 01 Jul 2003 17:52:18 +0200, Przemys³aw Korona
[EMAIL PROTECTED] wrote:
Hi there,
I have a problem with integrating tomcat and apache using jk2.
System configuration: suse 8.1
apache 1.3.26
tomcat 4.1.24
Correct me if I am wrong, but to establish link bw. apache and tomcat I
need to:
- add a connector in server.xml
Connector acceptCount=10 bufferSize=2048
className=org.apache.ajp.tomcat4.Ajp13Connector port=8009
minProcessors=5 maxProcessors=75 debug=0 enableLookups=true
Factory className=org.apache.catalina.net.DefaultServerSocketFactory/
/Connector
- load jk2 module in httpd.conf
- configure workers2.properties
[shm]
file=/srv/www/logs/jk2.shm
[channel.socket:192.168.230.14:8009]
info=Ajp13 forwarding over socket
tomcatId=192.168.230.14:8009
[uri:/examples/*]
info=Map the whole webapp
- configure jk2.properties
# Set the desired handler list
# handler.list=apr,request,channelJni
#
# Override the default port for the socketChannel
# channelSocket.port=8009
# Default:
# channelUnix.file=${jkHome}/work/jk2.socket
# Just to check if the the config is working
shm.file=/srv/www/logs/jk2.shm
# In order to enable jni use any channelJni directive
# channelJni.disabled = 0
# And one of the following directives:
# apr.jniModeSo=/opt/apache2/modules/mod_jk2.so
# If set to inprocess the mod_jk2 will Register natives itself
# This will enable the starting of the Tomcat from mod_jk2
# apr.jniModeSo=inprocess
It seems that in tomcat everything is fine (catalina.out after starting
tomcat ends with:
2003-07-01 17:24:33 HttpConnector[8443] Starting background thread
2003-07-01 17:24:34 HttpProcessor[8443][0] Starting background thread
2003-07-01 17:24:34 HttpProcessor[8443][1] Starting background thread
2003-07-01 17:24:34 HttpProcessor[8443][2] Starting background thread
2003-07-01 17:24:34 HttpProcessor[8443][3] Starting background thread
2003-07-01 17:24:34 HttpProcessor[8443][4] Starting background thread
2003-07-01 17:24:34 Ajp13Connector[8009] Opening server socket on all
host IP addresses
2003-07-01 17:24:34 Ajp13Connector[8009] Starting background thread
2003-07-01 17:24:34 Ajp13Processor[8009][0] Starting background thread
2003-07-01 17:24:34 Ajp13Processor[8009][1] Starting background thread
2003-07-01 17:24:34 Ajp13Processor[8009][2] Starting background thread
2003-07-01 17:24:34 Ajp13Processor[8009][3] Starting background thread
2003-07-01 17:24:34 Ajp13Processor[8009][4] Starting background thread
However in apache, there are some errors after restart:
[Tue Jul 01 14:47:08 2003] ( info) [mod_jk2.c (284)]: mod_jk child init
[Tue Jul 01 14:47:08 2003] ( info) [mod_jk2.c (292)]:
mod_jk.post_config() init worker env
[Tue Jul 01 14:47:08 2003] (error) [jk_logger_file.c (171)]: Can't open
log file ${serverRoot}/logs/mod_jk.log
[Tue Jul 01 14:47:08 2003] ( info) [jk_config_file.c (320)]:
cfg.update() Updating config /srv/www//conf/workers2.properties
[Tue Jul 01 14:47:08 2003] ( info) [jk_config_file.c (331)]:
config.setConfig(): Reading properties /srv/www//conf/workers2.
[Tue Jul 01 14:47:08 2003] (error) [jk_logger_file.c (171)]: Can't open
log file ${serverRoot}/logs/mod_jk.log
[Tue Jul 01 14:47:08 2003] (debug) [jk_uriMap.c (315)]: uriMap.init()
Fixing Host *
[Tue Jul 01 14:47:08 2003] ( info) [jk_workerEnv.c (403)]:
workerEnv.init() ok /srv/www//conf/workers2.properties
Create config for main host
[Tue Jul 01 14:47:09 2003] ( info) [mod_jk2.c (284)]: mod_jk child init
[Tue Jul 01 14:47:09 2003] ( info) [mod_jk2.c (292)]:
mod_jk.post_config() init worker env
[Tue Jul 01 14:47:09 2003] (error) [jk_logger_file.c (171)]: Can't open
log file ${serverRoot}/logs/mod_jk.log
[Tue Jul 01 14:47:09 2003] ( info) [jk_config_file.c (320)]:
cfg.update() Updating config /srv/www//conf/workers2.properties
[Tue Jul 01 14:47:09 2003] ( info) [jk_config_file.c (331)]:
config.setConfig(): Reading properties /srv/www//conf/workers2.
[Tue Jul 01 14:47:09 2003] (error) [jk_logger_file.c (171)]: Can't open
log file ${serverRoot}/logs/mod_jk.log
[Tue Jul 01 14:47:09 2003] (debug) [jk_uriMap.c (315)]: uriMap.init()
Fixing Host *
[Tue Jul 01 14:47:09 2003] ( info) [jk_workerEnv.c (403)]:
Re: mod jk2 problem, segmetation fault
Thank you all, for your quick responses. Tomcat comes with a JK2 compatible connector enabled by default on port 8009. The class name for this connector is CoyoteConnector. You mean: org.apache.coyote.tomcat4.CoyoteConnector ? If you need to use JK2, you don't need to do anything to server.xml except make sure your Hosts and your Contexts are correct, everything else is done on the Apache configuration side. I guess I have this part ok, because on port 8080 it works fine. I don't know of any JK2 binaries for SuSe, so unless you built your own, I would say your problem is a combination of an incompatible Apache module and the configuration of Ajp13Connector. This apache module is jk2_mod.so? Should I compile it from the source? Also, I am still not clear on the compatibility of JK2 (mod_jk2) with Apache 1.x. My guess is you would be better off with mod_jk (JK). John It seems that I just have chosen a wrong tool. I just hope, this mod_jk works with ssl (documentation says it should ;-)) Thanks again Przemek - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod jk2 problem, segmetation fault
On Tue, 01 Jul 2003 18:27:47 +0200, Przemys³aw Korona [EMAIL PROTECTED] wrote: Thank you all, for your quick responses. Tomcat comes with a JK2 compatible connector enabled by default on port 8009. The class name for this connector is CoyoteConnector. You mean: org.apache.coyote.tomcat4.CoyoteConnector ? Right on. If you need to use JK2, you don't need to do anything to server.xml except make sure your Hosts and your Contexts are correct, everything else is done on the Apache configuration side. I guess I have this part ok, because on port 8080 it works fine. Right on...just make sure that there is a CoyoteConnector listening on 8009 (default) or any other port that you wish to use. When you are in production, you can disable the connector on 8080. It seems that I just have chosen a wrong tool. I just hope, this mod_jk works with ssl (documentation says it should ;-)) Thanks again Przemek JK should work fine with SSL...in an Apache + Connector + Tomcat environment, Apache does all of the SSL heavy-lifting. Communications between Apache and Tomcat via mod_jk and mod_jk2 are done without SSL. So, you just need to focus on getting Apache doing your SSL. If you need a HOWTO, check out mine: http://www.johnturner.com/howto They're for Red Hat, and Apache 2, but the steps are the same. The only differences would be which mod_jk.so file you use for Apache 1.3 on SuSE. John - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: mod jk2 problem, segmetation fault
Howdy, Actually I have found this not to be true (the part about you can use any port). There is some kind of limitation on how high the port you use can be. For example: 8009 works 14009 works 48009 doesn't. The apache error log says that it can't connect. According to tomcat the Connector is listening and a netstat shows the port in a LISTEN state. I have a random guess harkening back to my C days: 32767 won't work. Give it a shot. Has to do with 2^16 int size bytes used to store the port number. 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: mod jk2 problem, segmetation fault
John Turner wrote: Tomcat comes with a JK2 compatible connector enabled by default on port 8009. The class name for this connector is CoyoteConnector. Ajp13Connector is for JK and is incompatible with JK2...it will never work. Whoa! I couldn't get the CoyoteConnector to work with 4.0.4 (I got errors in catalina.out about the CoyoteConnector not being found), but the Ajp13Connector behaved fine with JK2 - at least I *thought* - we *have* had some odd things going on with Tomcat 4.0.4 lately, but attributed that to trying too many upgrades at one time (like JDK 1.3 - JDK 1.4, upgrade of an EDBC driver) as we didn't see anything obvious in any Tomcat or Apache logs...I can see (thru ps -ef) when Tomcat and/or Apache are/is running, and from the messages in the various logs, it appears things are working right, but...what would I see that might tell me that there was a problem with Ajp13Connector? Thanks! -- Lynn Hollerman. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: mod jk2 problem, segmetation fault
Hi, 14009 works 48009 doesn't. The apache error log says that it can't connect. According to tomcat the Connector is listening and a netstat shows the port in a LISTEN state. I have a random guess harkening back to my C days: 32767 won't work. Give it a shot. Has to do with 2^16 int size bytes used to store the port number. You got it. :) 32767 yes, 32768 no. So is this still a bug? or is this a workaround? -e - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: mod jk2 problem, segmetation fault
Howdy, Well, that provided a bit of amusement for today ;) ;) You can put in an enhancement request to use 32bits for the port number. It's a low-priority item, not sure it will be done any time soon. Yoav Shapira 14009 works 48009 doesn't. The apache error log says that it can't connect. According to tomcat the Connector is listening and a netstat shows the port in a LISTEN state. I have a random guess harkening back to my C days: 32767 won't work. Give it a shot. Has to do with 2^16 int size bytes used to store the port number. You got it. :) 32767 yes, 32768 no. So is this still a bug? or is this a workaround? 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: mod jk2 problem, segmetation fault
I could be wrong...it was my understanding that JK2 was only supported by CoyoteConnector. Since both, I believe, use the AJP13 protocol, I guess its possible that Ajp13Connector could/would/might work. I know more about what DOES work than what DOESN'T work. ;) In any case, my point (perhaps not clearly stated) was that: 1) there is no need to do anything in server.xml to allow a default Tomcat install to work with one of the connectors 2) Ajp13Connector is not the preferred connector for either JK or JK2 in recent versions of Tomcat ( 4.1.12?) There's bound to be people that have unusual/uncommon environments that work...but for people just getting started, I think its less traumatic to guide them towards the usual/common environments until they get some experience. John On Tue, 01 Jul 2003 12:32:12 -0500, Geralyn M Hollerman [EMAIL PROTECTED] wrote: John Turner wrote: Tomcat comes with a JK2 compatible connector enabled by default on port 8009. The class name for this connector is CoyoteConnector. Ajp13Connector is for JK and is incompatible with JK2...it will never work. Whoa! I couldn't get the CoyoteConnector to work with 4.0.4 (I got errors in catalina.out about the CoyoteConnector not being found), but the Ajp13Connector behaved fine with JK2 - at least I *thought* - we *have* had some odd things going on with Tomcat 4.0.4 lately, but attributed that to trying too many upgrades at one time (like JDK 1.3 - JDK 1.4, upgrade of an EDBC driver) as we didn't see anything obvious in any Tomcat or Apache logs...I can see (thru ps -ef) when Tomcat and/or Apache are/is running, and from the messages in the various logs, it appears things are working right, but...what would I see that might tell me that there was a problem with Ajp13Connector? Thanks! -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod jk2 problem, segmetation fault
I could be wrong...it was my understanding that JK2 was only supported by CoyoteConnector. Since both, I believe, use the AJP13 protocol, I guess its possible that Ajp13Connector could/would/might work. I know more about what DOES work than what DOESN'T work. ;) It works *sorta*. It connects and passes data but some freakish things happen once in a while. We had a problem with this configuration (JK2 to Ajp13Connector, that was put in by mistake) and it would do stuff like forget to pass HTTP headers every so often. Wierd stuff like that. -e - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod jk2 problem, segmetation fault
Cool, thanks for the confirmation. John On Tue, 1 Jul 2003 15:40:37 -0400 (EDT), Eric J. Pinnell [EMAIL PROTECTED] wrote: I could be wrong...it was my understanding that JK2 was only supported by CoyoteConnector. Since both, I believe, use the AJP13 protocol, I guess its possible that Ajp13Connector could/would/might work. I know more about what DOES work than what DOESN'T work. ;) It works *sorta*. It connects and passes data but some freakish things happen once in a while. We had a problem with this configuration (JK2 to Ajp13Connector, that was put in by mistake) and it would do stuff like forget to pass HTTP headers every so often. Wierd stuff like that. -e - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: mod jk2 problem, segmetation fault
Hi, For anyone that cares I changed the 'long's to 'unsigned short's with some advice from Jeff Trawick. Still looks good after a some load. It's not being hammered but it looks ok. -e On Tue, 1 Jul 2003, Eric J. Pinnell wrote: Hi, This tweak on jakarta-tomcat-connectors-jk2-2.0.2-src/jk/native2/common/jk_channel_socket.c seems to fix the high TCP port issue. Alhtough I haven't found any trouble with it yet I have never written anything for JK2 and am unfamiliar with it's inner workings. So I wouldn't bet the farm on it. bash-2.04$ diff jk_channel_socket.c.old jk_channel_socket.c.new 94c94 short port; --- long port; 110c110 short port, --- long port, 204c204 static int JK_METHOD jk2_channel_socket_resolve(jk_env_t *env, char *host, short port, --- static int JK_METHOD jk2_channel_socket_resolve(jk_env_t *env, char *host, long port, -e On Tue, 1 Jul 2003, Shapira, Yoav wrote: Howdy, Well, that provided a bit of amusement for today ;) ;) You can put in an enhancement request to use 32bits for the port number. It's a low-priority item, not sure it will be done any time soon. Yoav Shapira 14009 works 48009 doesn't. The apache error log says that it can't connect. According to tomcat the Connector is listening and a netstat shows the port in a LISTEN state. I have a random guess harkening back to my C days: 32767 won't work. Give it a shot. Has to do with 2^16 int size bytes used to store the port number. You got it. :) 32767 yes, 32768 no. So is this still a bug? or is this a workaround? 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JK2 Problem
Good day, Just wondering if anyone at all has successfully gotten mod_jk2 to work between Apache and Tomcat on W2K. I have installed Apache 2.0.43 right out of the box and Tomcat 4.1.24 here at the office. jk2.properties is as it comes in the installation. worker2.properties is as follows # Define the communication channel [channel.socket:localhost:8009] info=Ajp13 forwarding over socket tomcatId=localhost:8009 # Map the Tomcat examples webapp to the Web server uri space [uri:/examples/*] info=Map the whole webapp I get the following in the apache error logs [Wed Feb 05 10:31:23 2003] [error] workerEnv.init() create slot epStat.0 failed [Wed Feb 05 10:31:23 2003] [error] lb.service() worker failed 12 for ajp13:localhost:8009 [Wed Feb 05 10:31:23 2003] [error] lb.service() unrecoverable error... [Wed Feb 05 10:31:23 2003] [error] mod_jk.handler() Error connecting to tomcat 12 [Wed Feb 05 10:38:19 2003] [error] lb.getWorker() reenable ajp13:localhost:8009 [Wed Feb 05 10:38:19 2003] [error] workerEnv.init() create slot epStat.0 failed [Wed Feb 05 10:38:19 2003] [error] lb.service() worker failed 12 for ajp13:localhost:8009 [Wed Feb 05 10:38:19 2003] [error] lb.service() unrecoverable error... [Wed Feb 05 10:38:19 2003] [error] mod_jk.handler() Error connecting to tomcat 12 What is wrong? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
