Hi-
I've been testing a web application on:
Tomcat 6.0.32 (32-bit)
Sun/Oracle JRE 1.6.0_25 (32-bit)
Windows Server 2008 R2
The web application includes a ServletContextListener which creates a
Timer in the contextInitialized method to perform periodic maintenance.
To no avail, I spent quite
> From: Petr Hracek [mailto:phrac...@gmail.com]
> Subject: Re: HANDLER THREAD PROBLEM: java.io.IOException: Stream broken
> Upgrading to the latest version of tomcat is not so easy
> on the customer side.
Why not? 6.0.x is configured pretty much identically to 5.5.y.
> Under SLES10 there is t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 7/11/2011 4:54 PM, André Warnier wrote:
> I think that you need to scroll back in this thread (to July 8), and
> re-read an answer which Charles provided to a previous question of
> mine.
>
> A partial answer resides in this property, whic
Sai Pullabhotla wrote:
A little more info on the
org.apache.catalina.session.StandardSession.ACTIVITY_CHECK system
property:
The last time I said that the above property is keeping the session
alive, I was only partially correct. The way it is working is -
session is kept alive for the duration
I agree. At this point, I'm not so concerned about the Firefox issue.
I will start a separate thread on it later. I still would like to get
some help on keeping the session alive for the duration of the
configured timeout, after a response is sent for a large request. Any
ideas will be greatly appr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 7/11/2011 3:59 PM, André Warnier wrote:
> It seems like there are two quite different issues/discussions going
> on in this same thread, with the same subject line. It is a bit
> confusing, even if originally they relate to the same problem.
It seems like there are two quite different issues/discussions going on in this same
thread, with the same subject line.
It is a bit confusing, even if originally they relate to the same problem.
Would it not be better to split this ?
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sai,
On 7/11/2011 9:29 AM, Sai Pullabhotla wrote:
> I took the threaddump and found that Tomcat's http service thread is
> still blocked on the read from the client after we called the
> forward method. At least, that's how I interpreted this, but be
A little more info on the
org.apache.catalina.session.StandardSession.ACTIVITY_CHECK system
property:
The last time I said that the above property is keeping the session
alive, I was only partially correct. The way it is working is -
session is kept alive for the duration of the upload. The respo
2011/7/11 PJ Delsh :
> 2- I don't know where in the Tomcat logs or Apache config to look for the
> connector we are using.
In Tomcat logs when Tomcat is starting up and is opening ports.
For AJP connector and Tomcat 6 the following lines mean that it is
using Java (Bio) implementation of AJP con
Hi Filip,
I have tried the app with tomcat 6.0.32 and 7.0.16, and the result is the same.
I am not able to get it working with https. Http works just fine.
The use case I am trying to address is that, I want to send
notifications/events from a webapp to another webapp asynchronously. The 2
web
Petr Hracek wrote:
Upgrading to the latest version of tomcat is not so easy on the customer side.
It needs time therefore we have only tomcat 5.5 version. Under SLES10
there is tomcat 5.5 version on the SLES11 there is tomcat 6 version.
Allright then, we all have similar customer cases.
And I g
Upgrading to the latest version of tomcat is not so easy on the customer side.
It needs time therefore we have only tomcat 5.5 version. Under SLES10
there is tomcat 5.5 version on the SLES11 there is tomcat 6 version.
Dne 11. července 2011 15:56 Pid napsal(a):
> On 11/07/2011 14:30, Petr Hracek w
On 11/07/2011 15:10, PJ Delsh wrote:
>
> Konstantin,
> 1- We couldn't find anything useful in the Apache logs.
Log data is useful. Even if it doesn't /appear/ to show an error.
> 2- I don't know where in the Tomcat logs or Apache config to look for the
> connector we are using.
Carefully rem
Konstantin,
1- We couldn't find anything useful in the Apache logs.
2- I don't know where in the Tomcat logs or Apache config to look for the
connector we are using.
3- How can we connect to Tomcat via the non AJP (if we are using it) to see if
Tomcat responds?
4- What can I do with the thread
On 11/07/2011 14:30, Petr Hracek wrote:
> It seems that after upgrading to tomcat5.5 all is working.
> But some times ps -ef or top shown me that java process is consuming
> 100% CPU usage
> Before that there was used tomcat 3.2.1 version
> JRE which was used was 1.4.2.
Right...
So again I'll poi
It seems that after upgrading to tomcat5.5 all is working.
But some times ps -ef or top shown me that java process is consuming
100% CPU usage
Before that there was used tomcat 3.2.1 version
JRE which was used was 1.4.2.
Dne 11. července 2011 12:36 Pid napsal(a):
> On 11/07/2011 09:06, André War
Thanks, Chris!
I took the threaddump and found that Tomcat's http service thread is
still blocked on the read from the client after we called the forward
method. At least, that's how I interpreted this, but below is the
particular thread's dump:
"http-443-1" daemon prio=6 tid=0x4c20b000 n
2011/7/11 PJ Delsh :
>
> Thank you Konstantin and Chris.
>
> I have setup Apache 2.2.19 through mod_jk 1.2.21
> To enable compression on the SSL traffic, Apache and Tomcat are setup in a
> reverse proxy.
>
> 1- Should I take the thread dumps now, or when Tomcat is in the
> 'non-responding' state?
On 09/07/2011 00:40, charithsoori wrote:
> Hi,
> I am trying to run a web application which is which using JNA . My
> application work fins as standalone and when it configured as a web app
> tomcat it giving error "
>
> java.lang.NoClassDefFoundError:
> com/stibocatalog/hunspell/HunspellLibrary
On 11/07/2011 09:06, André Warnier wrote:
> Platform ?
> Tomcat version (x.y.z) ?
> Java version ?
> mod_jk/isapi version ?
>
> What are you/your component doing when the error happens ?
> I mean, does the error happen when a tau neutrino strikes the CPU, or
> when you pull the network cable, or w
Platform ?
Tomcat version (x.y.z) ?
Java version ?
mod_jk/isapi version ?
What are you/your component doing when the error happens ?
I mean, does the error happen when a tau neutrino strikes the CPU, or when you pull the
network cable, or when ?
And, why would you be *developing* under Tomcat
Dear users.
during the development of my component sometimes I am receiving following error:
HANDLER THREAD PROBLEM: java.io.IOException: Stream broken
java.io.IOException: Stream broken
at
org.apache.tomcat.service.connector.AJP12RequestAdapter.readNextRequest(Ajp12ConnectionHandler.java:426)
> Date: Fri, 8 Jul 2011 10:39:16 -0700
> From: its_toas...@yahoo.com
> Subject: Re: Deploying emboss in Opal2
> To: users@tomcat.apache.org
>
> - Original Message -
>
> > From: jeroen vannevel
> > To: users@tomcat.apache.org
> > Cc:
> > Sent: Friday, July 8, 2011 6:37 AM
> > Subject:
24 matches
Mail list logo
