On 20.05.2009 07:20, pappu wrote:
Chuck,
---
If by Tomcat 5 you really mean Tomcat 5.0, please be aware that 5.0 has
not been supported for quite some time. You do need to move up.
---
Yes I do mean Tomcat 5.0. The reason why we are having this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pappu,
On 5/20/2009 1:20 AM, pappu wrote:
Yes I do mean Tomcat 5.0. The reason why we are having this version is
because we have Business Objects (Analytics Tool) configured to run on
tomcat and it only supports for Tomcat 5.0 and Tomcat 5.5. When
Hi,
We are running our application on Tomcat 5 and have authorization done by
IIS and have configured the IIS to tomcat communication using the
iisapi_Redirect.
We are facing this issue where we get the Request Entity too Large error
when we try for certain ids.
Since we are running on Tomcat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
AM,
On 5/19/2009 6:59 AM, pappu wrote:
We are running our application on Tomcat 5 and have authorization done by
IIS and have configured the IIS to tomcat communication using the
iisapi_Redirect.
We are facing this issue where we get the
Chris,
What mod_jk change? What does running Tomcat 5 (specifically) have to do
with it?
-
The link of tomcat below gives instructions on how to increase the
max_packet_size for AJP. This mentions that this is available only
From: pappu [mailto:anaga_mahade...@infosys.com]
Subject: Re: Request entity too large when using SSO (IIS Integrated
Windows authentication -Tomcat )
So we having Tomcat 5 means that we cannot change this.
If by Tomcat 5 you really mean Tomcat 5.0, please be aware that 5.0 has not
been
Chuck,
---
If by Tomcat 5 you really mean Tomcat 5.0, please be aware that 5.0 has
not been supported for quite some time. You do need to move up.
---
Yes I do mean Tomcat 5.0. The reason why we are having this version is
because we have Business Objects
Markus,
Is the header name called Authentication ? If so, we had this exact
same issue a few years ago. The length of this HTTP header was too long for
mod_jk to process and the request was getting dropped. I think you might be
able to configure the packet size of mod_jk now to get around this
On 17.04.2009 16:55, Scott Bradshaw wrote:
Markus,
Is the header name called Authentication ? If so, we had this exact
same issue a few years ago. The length of this HTTP header was too long for
mod_jk to process and the request was getting dropped. I think you might be
able to configure