You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by nageshsrao <na...@yahoo.com> on 2007/07/09 14:37:05 UTC
core_output_filter error for apache/tomcat JK connector
we have upgraded our environment to following software specs.
on Redhat AS 3.0 (update 8), tomcat 5.5.23, apache 2.0.46 and JK 1.2.23
plugin. intermittently we see the following error in the error log of
tomcat and then the whole site just gets hung. and no users will be to
procede with any operation. this is suppose to go to Staging, could help us
getting this resolved.
[Mon Jul 09 11:27:19 2007] [info] (104)Connection reset by peer:
core_output_filter: writing data to the network
[Mon Jul 09 11:27:19 2007] [info] (32)Broken pipe: core_output_filter:
writing data to the network
[Mon Jul 09 11:27:23 2007] [info] (104)Connection reset by peer:
core_output_filter: writing data to the network
[Mon Jul 09 11:27:23 2007] [info] (32)Broken pipe: core_output_filter:
writing data to the network
let us know if any further information required, i will upload it
immediately.
--
View this message in context: http://www.nabble.com/core_output_filter-error-for-apache-tomcat-JK-connector-tf4048993.html#a11500807
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: core_output_filter error for apache/tomcat JK connector
Posted by nageshsrao <na...@yahoo.com>.
i think i goofed up while uploading the workers.properties. here is the one
i just picked from the server.
"site is hung up " means even the first page ( the login page) doesn't get
displayed on the browser. it just goes on and on..
- we can not connect to apache during this behaviour
- access_log has the log of our request. but no response
- i didn't try for non-tomcat resources ( static files ). i will try to do
that today
we plan to take downtime during the night hours today and i will turn the
debugging mode on and try setting up the JK timeout values and also will try
to access static files which are not on tomcat.
please take a look at the workers.properties and let me know if you find
anything unusual.
let us know if there any other debug parameters which we can set to more
information.
also as a information, this apache also has a weblogic plugin and even for
those pages we do not get any response during this state of apache
non-response.
I Thank you very much for closely following and helping up on this
regards,
nagesh http://www.nabble.com/file/p11518117/workers.properties
workers.properties
Rainer Jung-3 wrote:
>
> Your workers.properties don't look complete, for instance there is no
> worker.list in there, so all your worker definitions will not be
> functional.
>
> Have a look at the various timeouts mod_jk provides, especially
> connect_timeout and reply_timeout. You could also use apaches builtin
> server-status and mod_jk status worker to get an idea, what the web
> server is actually working on. Finally with an increased jk log level of
> info, you might get additional information.
>
> The Apache error simply looks like the client/browser didn't wait until
> it fully received the response. That's normal, especially if responses
> take too long. This should result in a hanging site.
>
> Maybe you can describe more pricisely, what you mean by "site is hung up".
>
> - can you connect to apache
> - dies it log your requests into the access log
> - if you connect with a technical browser like curl or telnet, do you
> get any answers for your requests
> - will requests for static ressources (I mean requests that do not match
> your forwarding rules) still work?
>
> Although I don't think this is the source of your problems, httpd 2.0.46
> is pretty outdated ...
>
> Regards,
>
> Rainer
>
> nageshsrao schrieb:
>> Hi, here are further information about the environment and answers to the
>> below question
>>
>> -Tomcat and apache are on two different servers ( separated by a
>> firewall)
>> -Tomcat 5.5.23 is running on Sun JDK 1.5.0_12
>> -Direct connection to tomcat http connector ( 8080 ) works fine.
>> -Yes, we are able to connect from Apache server to Tomcat server over JK
>> connector port 8009
>> -i haven't done any configuration on the tomcat side. and as for the
>> webserver, i have attached
>> the workers.properties file
>> - Thread dump of the tomcat ( during the hung condition ) does not show
>> anything unusual.
>> there are few normal requests.
>> -There is no error on mod_jk.log file, ( log level is set to error mode),
>> on
>> the apache error log
>> we see the following error.
>>
>> [Mon Jul 09 11:27:19 2007] [info] (104)Connection reset by peer:
>> core_output_filter: writing data to the network
>> [Mon Jul 09 11:27:19 2007] [info] (32)Broken pipe: core_output_filter:
>> writing data to the network
>> [Mon Jul 09 11:27:23 2007] [info] (104)Connection reset by peer:
>> core_output_filter: writing data to the network
>> [Mon Jul 09 11:27:23 2007] [info] (32)Broken pipe: core_output_filter:
>> writing data to the network
>>
>> - YES, restarting the apache server is the only option fix this
>> behaviour.
>>
>> This setup is suppose to go to Staging, so for now, we are using JK2
>> connector and it is running fine, but we want to back to JK 1.2 as JK2 is
>> not supported any more. with the jk2 connector the system is fine for
>> almost 18 hours now.
>> http://www.nabble.com/file/p11515063/workers.properties
>> workers.properties
>>
>>
>>
>> Rainer Jung-3 wrote:
>>> - Which version of Java?
>>> - What does a thread dump of Tomcat give (kill -QUIT, result goes to
>>> catalina.out)
>>> - Does direct connect to Tomcat http connector still work?
>>> - Can you still connect from the Apache server to the Tomcat jk
>>> connector via telnet?
>>> - What's the config of your jk conector (tomcat side) and of mod_jk?
>>> - What are the contents of the mod_jk log file and the Apache error log?
>>> - If it happens, will restarting only Apache fix the hang?
>>>
>>> nageshsrao wrote:
>>>> we have upgraded our environment to following software specs.
>>>>
>>>> on Redhat AS 3.0 (update 8), tomcat 5.5.23, apache 2.0.46 and JK
>>>> 1.2.23
>>>> plugin. intermittently we see the following error in the error log of
>>>> tomcat and then the whole site just gets hung. and no users will be to
>>>> procede with any operation. this is suppose to go to Staging, could
>>>> help
>>>> us
>>>> getting this resolved.
>>>>
>>>> [Mon Jul 09 11:27:19 2007] [info] (104)Connection reset by peer:
>>>> core_output_filter: writing data to the network
>>>> [Mon Jul 09 11:27:19 2007] [info] (32)Broken pipe: core_output_filter:
>>>> writing data to the network
>>>> [Mon Jul 09 11:27:23 2007] [info] (104)Connection reset by peer:
>>>> core_output_filter: writing data to the network
>>>> [Mon Jul 09 11:27:23 2007] [info] (32)Broken pipe: core_output_filter:
>>>> writing data to the network
>>>>
>>>> let us know if any further information required, i will upload it
>>>> immediately.
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/core_output_filter-error-for-apache-tomcat-JK-connector-tf4048993.html#a11518117
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: core_output_filter error for apache/tomcat JK connector
Posted by Rainer Jung <ra...@kippdata.de>.
Your workers.properties don't look complete, for instance there is no
worker.list in there, so all your worker definitions will not be functional.
Have a look at the various timeouts mod_jk provides, especially
connect_timeout and reply_timeout. You could also use apaches builtin
server-status and mod_jk status worker to get an idea, what the web
server is actually working on. Finally with an increased jk log level of
info, you might get additional information.
The Apache error simply looks like the client/browser didn't wait until
it fully received the response. That's normal, especially if responses
take too long. This should result in a hanging site.
Maybe you can describe more pricisely, what you mean by "site is hung up".
- can you connect to apache
- dies it log your requests into the access log
- if you connect with a technical browser like curl or telnet, do you
get any answers for your requests
- will requests for static ressources (I mean requests that do not match
your forwarding rules) still work?
Although I don't think this is the source of your problems, httpd 2.0.46
is pretty outdated ...
Regards,
Rainer
nageshsrao schrieb:
> Hi, here are further information about the environment and answers to the
> below question
>
> -Tomcat and apache are on two different servers ( separated by a firewall)
> -Tomcat 5.5.23 is running on Sun JDK 1.5.0_12
> -Direct connection to tomcat http connector ( 8080 ) works fine.
> -Yes, we are able to connect from Apache server to Tomcat server over JK
> connector port 8009
> -i haven't done any configuration on the tomcat side. and as for the
> webserver, i have attached
> the workers.properties file
> - Thread dump of the tomcat ( during the hung condition ) does not show
> anything unusual.
> there are few normal requests.
> -There is no error on mod_jk.log file, ( log level is set to error mode), on
> the apache error log
> we see the following error.
>
> [Mon Jul 09 11:27:19 2007] [info] (104)Connection reset by peer:
> core_output_filter: writing data to the network
> [Mon Jul 09 11:27:19 2007] [info] (32)Broken pipe: core_output_filter:
> writing data to the network
> [Mon Jul 09 11:27:23 2007] [info] (104)Connection reset by peer:
> core_output_filter: writing data to the network
> [Mon Jul 09 11:27:23 2007] [info] (32)Broken pipe: core_output_filter:
> writing data to the network
>
> - YES, restarting the apache server is the only option fix this behaviour.
>
> This setup is suppose to go to Staging, so for now, we are using JK2
> connector and it is running fine, but we want to back to JK 1.2 as JK2 is
> not supported any more. with the jk2 connector the system is fine for
> almost 18 hours now.
> http://www.nabble.com/file/p11515063/workers.properties workers.properties
>
>
>
> Rainer Jung-3 wrote:
>> - Which version of Java?
>> - What does a thread dump of Tomcat give (kill -QUIT, result goes to
>> catalina.out)
>> - Does direct connect to Tomcat http connector still work?
>> - Can you still connect from the Apache server to the Tomcat jk
>> connector via telnet?
>> - What's the config of your jk conector (tomcat side) and of mod_jk?
>> - What are the contents of the mod_jk log file and the Apache error log?
>> - If it happens, will restarting only Apache fix the hang?
>>
>> nageshsrao wrote:
>>> we have upgraded our environment to following software specs.
>>>
>>> on Redhat AS 3.0 (update 8), tomcat 5.5.23, apache 2.0.46 and JK 1.2.23
>>> plugin. intermittently we see the following error in the error log of
>>> tomcat and then the whole site just gets hung. and no users will be to
>>> procede with any operation. this is suppose to go to Staging, could help
>>> us
>>> getting this resolved.
>>>
>>> [Mon Jul 09 11:27:19 2007] [info] (104)Connection reset by peer:
>>> core_output_filter: writing data to the network
>>> [Mon Jul 09 11:27:19 2007] [info] (32)Broken pipe: core_output_filter:
>>> writing data to the network
>>> [Mon Jul 09 11:27:23 2007] [info] (104)Connection reset by peer:
>>> core_output_filter: writing data to the network
>>> [Mon Jul 09 11:27:23 2007] [info] (32)Broken pipe: core_output_filter:
>>> writing data to the network
>>>
>>> let us know if any further information required, i will upload it
>>> immediately.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: core_output_filter error for apache/tomcat JK connector
Posted by nageshsrao <na...@yahoo.com>.
Hi, here are further information about the environment and answers to the
below question
-Tomcat and apache are on two different servers ( separated by a firewall)
-Tomcat 5.5.23 is running on Sun JDK 1.5.0_12
-Direct connection to tomcat http connector ( 8080 ) works fine.
-Yes, we are able to connect from Apache server to Tomcat server over JK
connector port 8009
-i haven't done any configuration on the tomcat side. and as for the
webserver, i have attached
the workers.properties file
- Thread dump of the tomcat ( during the hung condition ) does not show
anything unusual.
there are few normal requests.
-There is no error on mod_jk.log file, ( log level is set to error mode), on
the apache error log
we see the following error.
[Mon Jul 09 11:27:19 2007] [info] (104)Connection reset by peer:
core_output_filter: writing data to the network
[Mon Jul 09 11:27:19 2007] [info] (32)Broken pipe: core_output_filter:
writing data to the network
[Mon Jul 09 11:27:23 2007] [info] (104)Connection reset by peer:
core_output_filter: writing data to the network
[Mon Jul 09 11:27:23 2007] [info] (32)Broken pipe: core_output_filter:
writing data to the network
- YES, restarting the apache server is the only option fix this behaviour.
This setup is suppose to go to Staging, so for now, we are using JK2
connector and it is running fine, but we want to back to JK 1.2 as JK2 is
not supported any more. with the jk2 connector the system is fine for
almost 18 hours now.
http://www.nabble.com/file/p11515063/workers.properties workers.properties
Rainer Jung-3 wrote:
>
> - Which version of Java?
> - What does a thread dump of Tomcat give (kill -QUIT, result goes to
> catalina.out)
> - Does direct connect to Tomcat http connector still work?
> - Can you still connect from the Apache server to the Tomcat jk
> connector via telnet?
> - What's the config of your jk conector (tomcat side) and of mod_jk?
> - What are the contents of the mod_jk log file and the Apache error log?
> - If it happens, will restarting only Apache fix the hang?
>
> nageshsrao wrote:
>>
>> we have upgraded our environment to following software specs.
>>
>> on Redhat AS 3.0 (update 8), tomcat 5.5.23, apache 2.0.46 and JK 1.2.23
>> plugin. intermittently we see the following error in the error log of
>> tomcat and then the whole site just gets hung. and no users will be to
>> procede with any operation. this is suppose to go to Staging, could help
>> us
>> getting this resolved.
>>
>> [Mon Jul 09 11:27:19 2007] [info] (104)Connection reset by peer:
>> core_output_filter: writing data to the network
>> [Mon Jul 09 11:27:19 2007] [info] (32)Broken pipe: core_output_filter:
>> writing data to the network
>> [Mon Jul 09 11:27:23 2007] [info] (104)Connection reset by peer:
>> core_output_filter: writing data to the network
>> [Mon Jul 09 11:27:23 2007] [info] (32)Broken pipe: core_output_filter:
>> writing data to the network
>>
>> let us know if any further information required, i will upload it
>> immediately.
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/core_output_filter-error-for-apache-tomcat-JK-connector-tf4048993.html#a11515063
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: core_output_filter error for apache/tomcat JK connector
Posted by Rainer Jung <ra...@kippdata.de>.
- Which version of Java?
- What does a thread dump of Tomcat give (kill -QUIT, result goes to
catalina.out)
- Does direct connect to Tomcat http connector still work?
- Can you still connect from the Apache server to the Tomcat jk
connector via telnet?
- What's the config of your jk conector (tomcat side) and of mod_jk?
- What are the contents of the mod_jk log file and the Apache error log?
- If it happens, will restarting only Apache fix the hang?
nageshsrao wrote:
>
> we have upgraded our environment to following software specs.
>
> on Redhat AS 3.0 (update 8), tomcat 5.5.23, apache 2.0.46 and JK 1.2.23
> plugin. intermittently we see the following error in the error log of
> tomcat and then the whole site just gets hung. and no users will be to
> procede with any operation. this is suppose to go to Staging, could help us
> getting this resolved.
>
> [Mon Jul 09 11:27:19 2007] [info] (104)Connection reset by peer:
> core_output_filter: writing data to the network
> [Mon Jul 09 11:27:19 2007] [info] (32)Broken pipe: core_output_filter:
> writing data to the network
> [Mon Jul 09 11:27:23 2007] [info] (104)Connection reset by peer:
> core_output_filter: writing data to the network
> [Mon Jul 09 11:27:23 2007] [info] (32)Broken pipe: core_output_filter:
> writing data to the network
>
> let us know if any further information required, i will upload it
> immediately.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org