ustrated building jk2. Once I built it, I was
surprised that the configuration is so simple.
-Original Message-
From: Dennis Cartier [mailto:[EMAIL PROTECTED]
Sent: March 14, 2003 11:32 AM
To: Tomcat Users List
Subject: RE: Apache - Tomcat connectors
I agree. I struggled with JK2 for awhile
I agree. I struggled with JK2 for awhile but finally gave up and went back
to JK. The docs were very confusing and contradictory. I suppose I could
have appealed for help, but I got the impression that JK2 was still under
constant change and without being able to be self sufficient, I felt the
risk
Ian,
If you are stumped, you could try running a sniffer to see just what is included in
the response. Set-Cookie header or not. Tcpdump on any Unix box or Ethereal comes in
handy for this.
Dennis
-Original Message-
From: Ian Bruseker [mailto:[EMAIL PROTECTED]
Sent: Friday, March 14, 2
Thanks Bill. This is great. This has been bugging me for awhile.
Dennis
-Original Message-
From: news [mailto:[EMAIL PROTECTED] Behalf Of Bill Barker
Sent: Wednesday, March 12, 2003 3:46 AM
To: [EMAIL PROTECTED]
Subject: Re: Bad Cookie Handling in Tomcat & mod_Jk
"Denni
Hi Guys,
I have run across a situation a couple of times now that results in the
operation of my cluster being severely impacted. When a bad cookie comes
into 1 of the nodes, it crashes the coyote connector like so:
java.lang.IllegalArgumentException: Cookie name 7~?at1 is a reserved token
at ja
Hi Raj,
I just realized I did not answer your original question. That huge pause, I
would expect it would be garbage collection. You likely have lots of memory
in your tomcat box and it is taking a long time to garbage collect it.
If you switch to the incremental garbage collector (-Xincgc), you
Hi Raj,
Yikes! Six Apache's all going to 1 Tomcat sounds like a recipe for disaster
to me. In my experience, Apache handles load way better than Tomcat, so
having 1 or 2 Apache's and 5 or 6 Tomcat's sounds like a better setup.
Unless Tomcat is doing almost no work, it is going to be your bottlenec
I disagree. In my opinion you should play to the applications strengths, and
serving static content is NOT Tomcat's strength. When you throw in load
balancing and the ability to dynamically add and subtract Tomcat nodes out
of your pool by adjusting the Apache's on the front-end, the benefits becom
welcome.html
test.jsp
Thanks!
>From: "Dennis Cartier" <[EMAIL PROTECTED]>
>Reply-To: "Tomcat Users List" <[EMAIL PROTECTED]>
>To: "
test.jsp
Thanks!
>From: "Dennis Cartier" <[EMAIL PROTECTED]>
>Reply-To: "Tomcat Users List" <[EMAIL PROTECTED]>
>To: "Tomcat Users List" <[EMAIL PROTECTED]>
>Subject: RE: Simple W
Please post your web.xml from the WEB-INF dir in mig.war
-Original Message-
From: Manoj Kithany [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 14, 2003 12:42 PM
To: [EMAIL PROTECTED]
Subject: Re: Simple WAR on Apache + Tomcat + JBoss
I checked the mod_jk.log file and found following..
Hi Manjo,
It mostly looks OK to me. I run Tomcat 4.1.18 with JBoss 3.0.6.
Observations:
Of the following 3 lines, the last makes the previous 2 redundant
JKMount /mig/servlet/* ajp13
JKMount /mig/*.jsp ajp13
JKMount /mig/* ajp13
When you attempt to hit Tomcat through Apache, append a trailing
Hi,
I recently placed into service a cluster of 4 Tomcat 4.1.18/JBoss 3.0.6
servers. Yesterday an unexpected problem came up though. A user using NS
4.76 with a corrupted cookie file sent a HUGE cookie into Tomcat. The
servicing Coyote thread choked on it with the following stack trace.
2003-02-1
13 matches
Mail list logo
