Stephen Byrne wrote:
> Have you successfully used a CometProcessor behind an AJP proxy?
I guess not. Sorry to waste your time... ;-)
--
Robin D. Wilson
Director of Web Development
KingsIsle Entertainment, Inc.
CELL: 512-426-3929
DESK: 512-623-5913
www.KingsIsle.com
-
t
KingsIsle Entertainment, Inc.
CELL: 512-426-3929
DESK: 512-623-5913
www.KingsIsle.com
-Original Message-
From: Stephen Byrne [mailto:step...@lincware.com]
Sent: Wednesday, January 27, 2010 9:54 AM
To: Tomcat Users List
Subject: Re: CometProcessor proxied through Apache httpd
Robin Wils
Have you tried using mod_proxy_ajp?
ProxyPass /some/path ajp://tomcat.host.domain:8009/some/other/path
--
Robin D. Wilson
Director of Web Development
KingsIsle Entertainment, Inc.
CELL: 512-426-3929
DESK: 512-623-5913
www.KingsIsle.com
-Original Message-
From: Stephen Byrne [mailto:ste
I agree with Peter, we need more information.
I will point out that we had a similar issue - during peak activity on our
site, and it related to sessions being created faster than Tomcat could get rid
of them (even though they were expired already). We used the "/manager/html"
app that comes wi
m
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Friday, January 15, 2010 9:13 AM
To: Tomcat Users List
Subject: Re: Updating Java
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robin,
On 1/14/2010 11:26 PM, Robin Wilson wrote:
> You could just
You could just download the Sun JDK rpm and manually install it using the
command line. Then point your "JAVA_HOME" environment variable to where you
installed it.
--
Robin D. Wilson
Director of Web Development
KingsIsle Entertainment, Inc.
CELL: 512-426-3929
DESK: 512-623-5913
www.KingsIsle.com
ld be
1. Refactor DeltaManager and BackupManager to defer the session creation
message until the request is complete
2. Then simply swap out the ReplicationValve with an implementation that
makes sense
Filip
On 01/12/2010 11:42 AM, Robin Wilson wrote:
> REPOSTING this so it won'
What is your actual goal (other than mapping port 80 to 8080)?
It sounds like you just want to be able to respond to incoming requests on port
80 - so you don't have to tell users to use ":8080" on their requests - is that
right?
If that's the case, you have a couple of options:
1) run tomcat
06 PM
To: Tomcat Users List
Subject: Re: More on Tomcat Sessions - limiting cluster session replication to
sessions that will last longer than 'n' duration
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robin,
On 1/12/2010 1:42 PM, Robin Wilson wrote:
> Earlier this week I posted
REPOSTING this so it won't be on the other thread - sorry about that.
Earlier this week I posted a question about how to prevent sessions from being
created in our Tapestry pages, and/or how to get Tomcat to get rid of a bunch
of '1-second' sessions we're creating during a load test because the
Earlier this week I posted a question about how to prevent sessions from being
created in our Tapestry pages, and/or how to get Tomcat to get rid of a bunch
of '1-second' sessions we're creating during a load test because the sessions
eventually fill up the heap. (They are being created faster t
We're running with -Xmx=6g right now. No problems. 64-bit RHEL
platform, so you may need a 64-bit OS for that.
--
Robin D. Wilson
On Jan 10, 2010, at 8:59 AM, "V Jayakumar" wrote:
>
> All
>
>
>
> Thank you all for the replies & the scripts.
>
>
>
> It is true that we can find the results th
until the load subsides; causing thrashing on
Garbage Collection
On 09.01.2010 12:13, Mark Thomas wrote:
> On 08/01/2010 23:07, Robin Wilson wrote:
>> OK, I made the following changes (1 at a time) to 'server.xml', and retested:
>>
>> &
: Re: When running under high load (via load generating tools), Tomcat
6.0.20 stops expiring sessions until the load subsides; causing thrashing on
Garbage Collection
On 08/01/2010 23:07, Robin Wilson wrote:
> OK, I made the following changes (1 at a time) to 'server.
rators, it only clears the sessions at a rate
of a few thousand every second.
--
Robin D. Wilson
Director of Web Development
KingsIsle Entertainment, Inc.
CELL: 512-426-3929
DESK: 512-623-5913
www.KingsIsle.com
-Original Message-
From: Robin Wilson [mailto:rwil...@kingsisle.com]
Sent: Friday,
homas [mailto:ma...@apache.org]
Sent: Friday, January 08, 2010 4:07 PM
To: Tomcat Users List
Subject: Re: When running under high load (via load generating tools), Tomcat
6.0.20 stops expiring sessions until the load subsides; causing thrashing on
Garbage Collection
On 08/01/2010 21:53, Robin W
I am trying to get a clustered Tomcat 6.0.20 environment to operate in a high
load environment. As part of the testing regime, we want to be able to run
continuous high load against a QA setup - and validate that Tomcat operates
continuously without a hiccup.
The SETUP:
1) Apache front-end (do
Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Monday, May 18, 2009 3:25 PM
To: Tomcat Users List
Subject: Re: Apache httpd vs Tomcat static content performance [Revised/Updated]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robin,
On 5/18/2009 4
Thanks! This information isn't useless... Of course, more detailed results,
after a longer test run would be more conclusive.
This appears to show that Apache is slightly faster (~4% or so) for files over
16KiB than Tomcat APR, and materially faster (~44% or more) than all other
configurations
I'm curious by your comment that Coyote/APR is performing on par with httpd,
from the results in your first message I saw it was a pretty big difference. Or
are you saying that wasn't using APR?
Also, I'd be curious about the big disparity between the 16MiB files and the
other 1MiB-32MiB files.
Web Development
KingsIsle Entertainment, Inc.
WORK: 512-623-5913
CELL: 512-426-3929
www.KingsIsle.com
-Original Message-
From: Robin Wilson [mailto:rwil...@kingsisle.com]
Sent: Friday, April 24, 2009 3:56 PM
To: users@tomcat.apache.org
Subject: org.apache.jk.common.ChannelSocket processCo
Actually,
AJAX requests would each be treated as separate requests - and (unless you are
using sticky sessions) they could get routed to any node. They could also fire
off independently within the code javascript code on the page - depending on
how they are coded.
--
Robin D. Wilson
Director of Web Devel
Also, you can have the browser 'install' the certificate from your self-signed
system - and it will no longer give you the error. This is only useful if you
_know_ the certificate is valid (as in, you are the one who created it).
Otherwise, you get into some serious security issues if you just s
We had a similar problem when our certificate was invalid. We updated our
certificate and the problem went away. I suspect, if you are not using a valid
certificate (from a real Certificate Authority - like VeriSign, or Thawte,
etc.), you would need to install the certificate you used on the apa
FYI, we've been using AJP (Apache 2.2.11, tomcat 6.0.18) for a while now, and
we've had issues with 503s as well. We think we've narrowed them down to
timeouts on our firewall between the Apache and Tomcat hosts. So we added
'keepalive' to the ProxyPass directives - and we're now monitoring to s
Users List
Subject: Re: Why we need two servers (httpd and tomcat)
Robin Wilson wrote:
> As for your assertion that 2 layers of security is just complexity
> and not more secure - you obviously haven't run many enterprise
> production systems. Security in an enterprise system is
Users List
Subject: Re: Why we need two servers (httpd and tomcat)
Robin Wilson wrote:
> For the record, my answer was neither stupid or reflexive.
And for the record, I personally did not think it was either.
I agree with Leon when he says that some people just automatically put
an Apache
For the record, my answer was neither stupid or reflexive. I simply pointed out
why someone might want 2 layers of servers (httpd and tomcat). And certainly,
my rationale is both sound and arguable at the same time.
As for your assertion that 2 layers of security is just complexity and not more
I can't answer for others - but one of the big values in a 'production'
environment is to separate concerns. The apache servers can sit in a different
DMZ area, and have only static (and unprotected) content on them. The tomcat
servers have another firewall between them and the apache servers -
1 0 Ok 18 0
22K
ajp://127.0.0.1:12003 s3 1 0 Ok 0 0 0
ajp://127.0.0.1:12004 s4 1 0 Ok 0 0
0
But there is nothing in the log as the one in BackupManager
(attributeReplaced..)
So, no
Did you comment out the line in 'context.xml'? If you
leave that it, it doesn't use the manager you defined for the cluster.
Also, is your web app defined as '' in the 'web.xml' file from
the webapp dir?
--
Robin D. Wilson
Director of Web Development
KingsIsle Entertainment, Inc.
WORK: 512-6
I'm trying to figure out what this means, and how to stop it... We're getting
following error repeated in our catalina.out logs:
Apr 24, 2009 8:42:24 AM org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
Apr 24, 2009 8:44:00 AM org.apache.jk.common.ChannelSock
33 matches
Mail list logo
