Re: service() failed with http error 413 - error log message from isapi_redirect.log file

2012-07-16 Thread ann ramos
Thanks Tim for your quick reply.  I have already increased the max_packet_size to the maximum allowable value way way before and it still comes up: worker.wlb.max_packet_size=65536 Yeah, I noticed the message about the hacking thing.  The website only runs internally.  I found a good explana

Re: service() failed with http error 413 - error log message from isapi_redirect.log file

2012-07-16 Thread Tim Watts
Hi Ann, On Mon, 2012-07-16 at 19:18 -0700, ann ramos wrote: > Hi, > > > > We are using HP Service Manager 9.2 system. The web client tier was > set up using Windows 2008 R2 64-bit, IIS 7.5, Tomcat 6 and Isapi > Redirector 1.2.30. > The client is accessing the site by https because we had crea

service() failed with http error 413 - error log message from isapi_redirect.log file

2012-07-16 Thread ann ramos
Hi, We are using HP Service Manager 9.2 system.  The web client tier was set up using Windows 2008 R2 64-bit, IIS 7.5, Tomcat 6 and Isapi Redirector 1.2.30. The client is accessing the site by https because we had created a certificate and binded it to the IIS.  Here are the steps that I used:

Re: OOME while expanding a war with tomcat 7.0.29 but not with tomcat 7.0.28

2012-07-16 Thread Rainer Jung
On 16.07.2012 19:35, Mark Thomas wrote: "CRANFORD, CHRIS" wrote: The OOME I am getting is coming from Heap, and that's even giving Tomcat 1GB of maximum heap. The instance seems to start successfully outside of the MyEclipse environment; however inside MyEclipse it fails miserably. The surpr

RE: OOME while expanding a war with tomcat 7.0.29 but not with tomcat 7.0.28

2012-07-16 Thread CRANFORD, CHRIS
Thanks Mark! -Original Message- From: Mark Thomas [mailto:ma...@apache.org] Sent: Monday, July 16, 2012 12:35 PM To: Tomcat Users List Subject: RE: OOME while expanding a war with tomcat 7.0.29 but not with tomcat 7.0.28 "CRANFORD, CHRIS" wrote: >The OOME I am getting is coming from H

RE: OOME while expanding a war with tomcat 7.0.29 but not with tomcat 7.0.28

2012-07-16 Thread Mark Thomas
"CRANFORD, CHRIS" wrote: >The OOME I am getting is coming from Heap, and that's even giving >Tomcat >1GB of maximum heap. The instance seems to start successfully outside >of the MyEclipse environment; however inside MyEclipse it fails >miserably. The surprising part of this is that the instanc

RE: Speeding up RMI calls

2012-07-16 Thread Andrew Kujtan
> -Original Message- > From: Pid [mailto:p...@pidster.com] > Sent: Thursday, July 12, 2012 5:22 PM > To: Tomcat Users List > Subject: Re: Speeding up RMI calls > > On 09/07/2012 16:55, Andrew Kujtan wrote: > > Tomcat Version: 7.0.27 > > > > OS: Windows XP/7 > > > > > > > > I'm fixing an

RE: Client Authentication using SSL

2012-07-16 Thread Jeffrey Janner
Thanks Chris, I'd seen a lot of traffic on the topic over the years, so knew someone had real-world experience on the subject. I'll check out what you did a little further. Of course, thinking on my proposed plan, a really uptight security admin might not think it all that more secure that basic-

RE: OOME while expanding a war with tomcat 7.0.29 but not with tomcat 7.0.28

2012-07-16 Thread CRANFORD, CHRIS
The OOME I am getting is coming from Heap, and that's even giving Tomcat 1GB of maximum heap. The instance seems to start successfully outside of the MyEclipse environment; however inside MyEclipse it fails miserably. The surprising part of this is that the instance has ran with half that amount

7.0.29 Multi-threaded deployment

2012-07-16 Thread CRANFORD, CHRIS
When upgrading from 7.0.26 to 7.0.29, MyEclipse cannot start the Tomcat instance without reaching an OutOfMemoryError exception that results from a "GC overhead limit exceeded" when Tomcat begins it's multi-threaded deployment process. MyEclipse is running with 1GB of maximum memory and still erro

Re: Solved - Connecting Tmcat and IIS

2012-07-16 Thread André Warnier
Vijaya wrote: Andre Warnier, thanks very much pointing the shortfall in my message. I myself have been using isapi_redirector for more than 3 years without any problem and suddenly for unexplainable reasons (I am sure it was not the isapi_redirector problem but some other problem in our server