Hi Chema
My understanding is that once these options are confgured, the SAME session
data is stored across contexts separately for each user. There is no need to
do anything special - the session will be explicitly invalidated when the
user logs out, otherwise when the session timeout is excee
Hi Guys,
I hate to pick your brains on this as the customer should know how to do
this, but they tasked me to find out ;(
Is there any API or other method they can code that will give them an
indication of nearing this threshold? I know it's a crappy solution, but
I thought I'd ask anyway :) AFAI
2011/8/6 TAK, RUDRA (ATTSI) :
> Recently we upgraded to tomcat6.0.32 and Oracle 11R1 G. We have Apache vs
> 1.3.41 and OS AIX5.3.
Apache HTTPD version is seriously outdated. IIRC 1.3.x versions are no
mote supported.
Cannot say anything about your OS.
(And what version of Java are you using?)
T
Hi,
Recently we upgraded to tomcat6.0.32 and Oracle 11R1 G. We have Apache vs
1.3.41 and OS AIX5.3.
1) We are facing issues with web-interface not accessible sometimes even
when apache and tomcat are up. When we bounce them it use to become accessible.
2) Also observing high CPU uti
On Fri, Aug 5, 2011 at 2:41 PM, Christopher Schultz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Mohit,
>
> On 8/5/2011 5:05 PM, Mohit Anchlia wrote:
>> On Fri, Aug 5, 2011 at 1:37 PM, Christopher Schultz
>>> Uh, why not use an HTTP proxy instead of using HttpClient. Squid,
>>> Apa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mohit,
On 8/5/2011 5:05 PM, Mohit Anchlia wrote:
> On Fri, Aug 5, 2011 at 1:37 PM, Christopher Schultz
>> Uh, why not use an HTTP proxy instead of using HttpClient. Squid,
>> Apache httpd, countless LBs, and many others have this capability
>> without
On Fri, Aug 5, 2011 at 1:37 PM, Christopher Schultz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Mohit,
>
> On 8/5/2011 1:59 PM, Mohit Anchlia wrote:
>> This switch calls HttpClient Post calls using thread pools to send
>> the request to other systems.
>
> Uh, why not use an HTTP p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 8/5/2011 12:00 PM, Mark Thomas wrote:
> On 05/08/2011 16:56, Dante Bell wrote:
>> Thanks!
>>
>> Like I said, I'm an OS/HW guy, never looked at java b4!
>>
>> They are saying that the load test has 20 'connections' so I'm
>> guessing that's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mohit,
On 8/5/2011 1:59 PM, Mohit Anchlia wrote:
> This switch calls HttpClient Post calls using thread pools to send
> the request to other systems.
Uh, why not use an HTTP proxy instead of using HttpClient. Squid, Apache
httpd, countless LBs, and
Mohit Anchlia wrote:
We are developing a new system that will run in parallel with old
system. So some requests will go to new system and some old based on
configuration. We will put software switch software which will read
configuration and the request and decide which system this will go to.
Th
We are developing a new system that will run in parallel with old
system. So some requests will go to new system and some old based on
configuration. We will put software switch software which will read
configuration and the request and decide which system this will go to.
This switch calls HttpCli
- Original Message -
> From: "Caldarale, Charles R"
> To: Tomcat Users List
> Cc:
> Sent: Friday, August 5, 2011 9:38 AM
> Subject: RE: Urgent: Tomcat 6.0.20 on Solaris 10 Reaches max threads and is
> non responsive
>
> From: Mark Thomas [mailto:ma...@apache.org]
> Subject: Re: Urgen
- Original Message -
> From: Pid
> To: Tomcat Users List
> Cc:
> Sent: Friday, August 5, 2011 8:35 AM
> Subject: Re: Urgent: Tomcat 6.0.20 on Solaris 10 Reaches max threads and is
> non responsive
>
> On 05/08/2011 16:12, Mark Thomas wrote:
>> On 05/08/2011 15:34, Dante Bell wrote:
>
From: Mark Thomas [mailto:ma...@apache.org]
Subject: Re: Urgent: Tomcat 6.0.20 on Solaris 10 Reaches max threads and is non
responsive
> Now, is this a fixable thing within the Java stack? Or is it an
> application limitation?
The other option is re-write the STM Servlet(s) as non-STM.
What Ma
On 05/08/2011 16:59, Jarnagin.Andrew wrote:
>
> It is working for me now. I think it had to do with remnants of multiple JDK
> versions on my machine including RC Java 7 releases. It caused many
> exceptions to show in the console on start-up and a 404 response for
> http:localhost:8080. I un
On 05/08/2011 17:10, Dante Bell wrote:
> This is probably a really dumb question, but say they implement
> load-balanced Tomcat on 2 nodes for example. Would that then allow for
> greater than 20 STMs for the servlets?
It will allow them up to 20 concurrent requests per STM Servlet per
Tomcat inst
This is probably a really dumb question, but say they implement
load-balanced Tomcat on 2 nodes for example. Would that then allow for
greater than 20 STMs for the servlets?
On 08/05/2011 12:00 PM, Mark Thomas wrote:
> On 05/08/2011 16:56, Dante Bell wrote:
>> Thanks!
>>
>> Like I said, I'm an OS/
On 05/08/2011 16:56, Dante Bell wrote:
> Thanks!
>
> Like I said, I'm an OS/HW guy, never looked at java b4!
>
> They are saying that the load test has 20 'connections' so I'm guessing
> that's the 20 STMs.
>
> Now, is this a fixable thing within the Java stack? Or is it an
> application limitat
It is working for me now. I think it had to do with remnants of multiple JDK
versions on my machine including RC Java 7 releases. It caused many exceptions
to show in the console on start-up and a 404 response for http:localhost:8080.
I uninstalled and removed all Java from the host and insta
Thanks!
Like I said, I'm an OS/HW guy, never looked at java b4!
They are saying that the load test has 20 'connections' so I'm guessing
that's the 20 STMs.
Now, is this a fixable thing within the Java stack? Or is it an
application limitation?
Danté
On 08/05/2011 11:12 AM, Mark Thomas wrote:
>
Pid wrote:
On 05/08/2011 16:12, Mark Thomas wrote:
On 05/08/2011 15:34, Dante Bell wrote:
Hi,
I'm running out of ideas on what to try for this customer. Their load
tests show that Tomcat is getting to a point where it no longer services
requests.
Let me guess. It is fine for low loads but as
On 05/08/2011 16:12, Mark Thomas wrote:
> On 05/08/2011 15:34, Dante Bell wrote:
>> Hi,
>>
>> I'm running out of ideas on what to try for this customer. Their load
>> tests show that Tomcat is getting to a point where it no longer services
>> requests.
>
> Let me guess. It is fine for low loads bu
On 05/08/2011 15:34, Dante Bell wrote:
> Hi,
>
> I'm running out of ideas on what to try for this customer. Their load
> tests show that Tomcat is getting to a point where it no longer services
> requests.
Let me guess. It is fine for low loads but as soon as the load goes
above a certain number
Dante -
Take a real close look at the application running in Tomcat.
I've had similar issues where Tomcat was suddenly using all configured request
threads, but they were all waiting on something else to happen.
I found the problem to be a minor defect with the DB pooling code from the DB
vendor
After some testing, I determined that appending the session ID to the URL will
not work. I can, however, add the session ID as a new HTTP header, but I have
to determine which modules to use (mod_headers, mod_proxy, mod_proxy_http,
mod_proxy_balancer?) and how to configure sticky sessions using
On 4 Aug 2011, at 08:23, Javed wrote:
>
> I was using Tomcat 5.0.28 before using Tomcat 7.0.16. The application was
> working perfectly fine. Recently, we have migrated from Tomcat 5 to Tomcat
> 7.
>
> The application works fine for most of the part but gives problem with
> URLRewriteFilter.
> I
26 matches
Mail list logo
