Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: domain of codesmoker@hotmail.com
 designates 64.4.18.89 as permitted sender)
Message-ID: <BAY24-F397F8DE9C1CE7982DF0F63CF740@phx.gbl>
In-Reply-To: <0IBL00M3OOYIUD@chimmx02.algx.net>
From: "Didier McGillis" <codesmoker@hotmail.com>
To: tomcat-user@jakarta.apache.org
Bcc: 
Subject: RE: [OT]Attn developers of Tomcat and JK
Date: Tue, 08 Feb 2005 21:58:32 +0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed

Really this is way out of line.  As everyone has said this is a free product 
with no formalized support structure, and no claims of any support.  This 
list is here as a resource to those brave souls who are adventerous enough 
to work with the software.  I might be overstating things here but there 
should be no one here that is surprised that there is no corporate help desk 
here.  When I started out the only thing I had going for me was I was 
inquisitive and had access to log files, this list and google, thats all I 
needed.  Three things you can do that will answer your questiion.  Ask in a 
clear consise manner (I have had a problem with that on occasion), check and 
double check your settings (many times I have been the culprut in my own 
problem) and google the error.  :)

>From: Eric Sandusky <esandusky@configureone.com>
>Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
>To: 'Tomcat Users List' <tomcat-user@jakarta.apache.org>
>Subject: Attn developers of Tomcat and JK
>Date: Tue, 08 Feb 2005 10:11:03 -0600
>
>To the developers of Tomcat and JK:
>
>As I can sense that not one single person is willing to respond to this
>issue, I can only assume that this tomcat-user community is worthless.  Not
>only have I submitted this issue back 6 months ago, but a similar post was
>made by the user "A jie" twice within the last week.
>
>If you are too ashamed that your software is not reliable enough to be
>installed in a production environment, at least have the decency of telling
>us that.  When I have to deal with user session data being sent back to the
>wrong client, sessions getting lost, and numerous log errors stating that
>the request/response cannot be fulfilled, I can only come to one
>conclusion.. Tomcat and the JK/JK2 connector are not reliable.  See below
>and tell me that those messages would not cause problems for the client.
>
>[Mon Feb 07 13:30:20 2005] [info]  jk_open_socket::jk_connect.c (183):
>connect() failed errno = 61
>[Mon Feb 07 13:30:20 2005] [info]  ajp_connect_to_endpoint::jk_ajp_common.c
>(862): Failed connecting to tomcat. Tomcat is probably not started or is
>listening on the wrong host/port (127.0.0.1:8009). Failed errno = 61
>[Mon Feb 07 13:30:20 2005] [info]  ajp_send_request::jk_ajp_common.c 
>(1186):
>Error connecting to the Tomcat process.
>[Mon Feb 07 13:30:20 2005] [info]  ajp_service::jk_ajp_common.c (1665):
>Sending request to tomcat failed,  recoverable operation attempt=2
>[Mon Feb 07 13:30:20 2005] [error] ajp_service::jk_ajp_common.c (1673):
>Error connecting to tomcat. Tomcat is probably not started or is listening
>on the wrong port. worker=ajp13w failed errno = 61
>[Mon Feb 07 13:30:20 2005] [error] HttpExtensionProc::jk_isapi_plugin.c
>(937): service() failed
>
>If Tomcat + JK cannot process every request/response on a Windows server
>that is dual-xeon 3.0 Ghz processors with 4 GB of memory, then what machine
>would?
>
>And doesn't it seem strange how the JK2 project has been mysteriously
>abandoned?  Thanks for going off in a seemingly better direction only to
>jump ship and leave everyone SOL.  It makes me think that this whole Tomcat
>development effort is more of just a hobby and not something to be taken
>seriously.
>
>If anyone is willing to contact me on this issue, I would be more than 
>happy
>to talk one-on-one.  If you want to tell me that this is not the forum for
>ranting about Tomcat or JK, it should be.  If you want to blackball me from
>this community, go ahead, I'm not getting any help from it as it is.  I can
>only hope that this message reaches the people who supposedly support this
>software and lights a fire underneath them to improve it or tell us that it
>just doesn't work.
>
>Eric
>
>-----Original Message-----
>From: Eric Sandusky [mailto:esandusky@configureone.com]
>Sent: Wednesday, February 02, 2005 11:40 AM
>To: Tomcat Users List
>Subject: ISAPI redirector warnings
>
>While running Tomcat 5 with IIS and JK2..
>
>
>
>The Windows Application Logs often log several Warnings at the same point 
>in
>time, see below for example.  The problem is, these Warnings pile up in the
>Windows Event logs and force the Administrator to manually clear out the
>logs daily or weekly.
>
>
>
>I am not looking to simply suppress these messages, but find a solution to
>the actual problem.  This issue seems to occur at random and things such as
>session confusion (user A sees user B's data) and other noticeable issues
>happen at or around the same time as these warnings.
>
>
>
>What is the reason for these log entries?
>
>
>
>How can I eliminate these log entries?
>
>
>
>Error: [jk_worker_ajp13.c (648)]: ajp13.service() Error  forwarding
>ajp13:localhost:8009 1 0
>
>Error: [jk_worker_ajp13.c (546)]: ajp13.service() ajpGetReply recoverable
>error 3
>
>Error: [jk_handler_response.c (140)]: handler.response() Error sending
>response
>
>Error: [jk_service_iis.c (126)]: jk_ws_service_t::head,
>ServerSupportFunction failed
>
>Error: [jk_worker_ajp13.c (546)]: ajp13.service() ajpGetReply recoverable
>error 3
>
>Error: [jk_handler_response.c (140)]: handler.response() Error sending
>response
>
>Error: [jk_service_iis.c (126)]: jk_ws_service_t::head,
>ServerSupportFunction failed
>
>
>
>Configuration:
>
>Windows 2000 or Windows 2003 Server
>
>Apache Tomcat 5.0.25 or 5.0.28
>
>Microsoft IIS 5 or 6
>
>JK2 2.0.4 connector
>
>
>
>Workers2.properties
>
>[shm:]
>
>info=Shared memory file. Required for multiprocess servers
>
>file=d:\tomcat5.0.28\work\jk20.shm
>
>size=1000000
>
>
>
># Define the communication channel
>
>[channel.socket:localhost:8009]
>
>tomcatId=localhost:8009
>
>
>
>[ajp13:localhost:8009]
>
>channel=channel.socket:localhost:8009
>
>
>
>[uri:/Concept60/*]
>
>worker=ajp13:localhost:8009
>
>
>
>Server.xml
>
><Connector port="8088" maxThreads="150" minSpareThreads="25"
>maxSpareThreads="75"
>
>                enableLookups="false" redirectPort="8443" acceptCount="100"
>
>                debug="0" connectionTimeout="20000"
>
>                disableUploadTimeout="true" />
>
><Connector port="8009"
>
>                enableLookups="false" connectionTimeout="0"
>redirectPort="8443" debug="0"
>
>                protocol="AJP/1.3" />
>
>
>
>isapi_redirector2.reg
>
>[HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi
>Redirector\2.0]
>
>"workersFile"="d:\\tomcat5.0.28\\conf\\workers2.properties"
>
>"extensionUri"="/jakarta2/isapi_redirector2.dll"
>
>"logLevel"="debug"
>
>"serverRoot"="d:\\tomcat5.0.28\\"
>
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org