RE: Tomcat 5.5.28 on 64 bit windows server 2008.

2011-08-23 Thread eurotrans-Verlag
Hi, -Original Message- From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com] Sent: Monday, August 22, 2011 5:35 PM To: 'Tomcat Users List' Subject: RE: Tomcat 5.5.28 on 64 bit windows server 2008. Allow me to clear that up: 1) If no address= parameter is given in the

RE: Tomcat 5.5.28 on 64 bit windows server 2008.

2011-08-21 Thread eurotrans-Verlag
Hi, -Original Message- From: Venkata Surapaneni [mailto:vsurapan...@imedx.com] Sent: Sunday, August 21, 2011 12:26 PM To: Tomcat Users List Subject: RE: Tomcat 5.5.28 on 64 bit windows server 2008. And on top of this all the log look clean. Nothing looks suspicious.

RE: AJP-APR failures on Tomcat 7.0.16 with ISAPI Redirector 1.2.32

2011-08-03 Thread eurotrans-Verlag
-Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Tuesday, July 26, 2011 6:15 PM To: Tomcat Users List Subject: Re: AJP-APR failures on Tomcat 7.0.16 with ISAPI Redirector 1.2.32 You should also null-out the reference to Tomcat's output

RE: AJP-APR failures on Tomcat 7.0.16 with ISAPI Redirector 1.2.32

2011-07-25 Thread eurotrans-Verlag
Hi all, An alternative that I could imagine, would be to create a class (that has a boolean flag) which extends OutputStream, and decorates another OutputStream that is given to the class in the constructor (that would be the OutputStream from the servlet's response). This class would pass

RE: How to send binary data in a form field via Java

2011-07-15 Thread eurotrans-Verlag
Hi, -Original Message- From: Paritosh Patel [mailto:xygnu...@gmail.com] Sent: Friday, July 15, 2011 5:24 PM To: users@tomcat.apache.org Subject: How to send binary data in a form field via Java I apologize in advance if this is not the correct mail list for such a question, but

RE: AJP-APR failures on Tomcat 7.0.16 with ISAPI Redirector 1.2.32

2011-07-14 Thread eurotrans-Verlag
Hi André, -Original Message- From: André Warnier [mailto:a...@ice-sa.com] Sent: Thursday, July 14, 2011 1:00 PM To: Tomcat Users List Subject: Re: AJP-APR failures on Tomcat 7.0.16 with ISAPI Redirector 1.2.32 As a comment purely from a general programming point of view, not a

RE: AJP-APR failures on Tomcat 7.0.16 with ISAPI Redirector 1.2.32

2011-07-13 Thread eurotrans-Verlag
Hi Rainer, -Original Message- From: Rainer Jung [mailto:rainer.j...@kippdata.de] Sent: Thursday, July 14, 2011 12:17 AM At least there was trouble about Java2D for several users in the past. One such issue: https://issues.apache.org/bugzilla/show_bug.cgi?id=41772

RE: AJP-APR failures on Tomcat 7.0.16 with ISAPI Redirector 1.2.32

2011-07-12 Thread eurotrans-Verlag
However, when I switch to AJP BIO, it seems that the errors go away. Although I now switched to AJP-BIO (by deleting/renaming tcnative-1.dll), today morning I got an error again in the ISAPI log: [Tue Jul 12 06:04:49.812 2011] [4124:2444] [error]

RE: AJP-APR failures on Tomcat 7.0.16 with ISAPI Redirector 1.2.32

2011-07-12 Thread eurotrans-Verlag
Hi André, -Original Message- From: André Warnier [mailto:a...@ice-sa.com] Sent: Tuesday, July 12, 2011 9:25 PM Can you take a part of this setup out of the equation ? For example, at the moment you have browser - IIS - isapi_redir. - AJP Connector:8019 - Tomcat+webapp

AJP-APR failures on Tomcat 7.0.16 with ISAPI Redirector 1.2.32

2011-07-10 Thread eurotrans-Verlag
Hi all, I have a system with Windows Server 2008 (32 bit), Sun/Oracle JDK 1.6.0_26 and I’m using Tomcat 7.0.16 with Tomcat Native 1.1.20, and IIS 7.0 with ISAPI Redirector 1.2.32. For AJP, I use the AJP-APR connector. Sometimes, when many requests are sent to a webapp in short time, some

RE: NPE at StandardWrapperValve.invoke() in Tomcat 7.0.16

2011-07-08 Thread eurotrans-Verlag
Hi Christopher, My experience with the Sun/Oracle compiler is that lines 288 and 289 will never be indicated in a stack trace: the line number of the start of the statement is considered the line number for the entire statement. Well, I made a small test program with this code: String

RE: NPE at StandardWrapperValve.invoke() in Tomcat 7.0.16

2011-07-08 Thread eurotrans-Verlag
Hi Christopher, The compiler must have gotten smarter than the last time I checked. I'm sorry: I compiled that code with the Eclipse compiler. When compiling it with the Oracle Java compiler (javac), it prints out the line number of the System.out.println. Maybe if Tomcat was compiled

RE: NPE at StandardWrapperValve.invoke() in Tomcat 7.0.16

2011-07-07 Thread eurotrans-Verlag
Hi Pid, -Original Message- From: Pid [mailto:p...@pidster.com] Sent: Thursday, July 07, 2011 6:19 PM What is the request for and is the config of your Tomcat instance modified from the original download - if so, what has changed (config etc)? p I don't know which request

RE: NPE at StandardWrapperValve.invoke() in Tomcat 7.0.16

2011-07-07 Thread eurotrans-Verlag
Hi Christopher, -Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Thursday, July 07, 2011 9:13 PM Looks like it. I would be very interested to know which of those objects is null: the container, the logger, the wrapper, or the context. -

RE: NPE at StandardWrapperValve.invoke() in Tomcat 7.0.16

2011-07-07 Thread eurotrans-Verlag
Hi Pid, -Original Message- From: Pid [mailto:p...@pidster.com] Sent: Thursday, July 07, 2011 10:24 PM Are you using parallel deployment or are you replacing the existing application when it's redeployed. Maybe the old context is the one throwing the error. p I don't use

RE: NPE at StandardWrapperValve.invoke() in Tomcat 7.0.16

2011-07-07 Thread eurotrans-Verlag
Maybe I can reproduce the NPE if I make a servlet that takes a long time to finish the request, to see what was the original exception that has been suppressed by the NPE. OK, I was able to reproduce a NPE in TC 7.0.16 with a Servlet that calls Thread.sleep(2), then make a request to

NPE at StandardWrapperValve.invoke() in Tomcat 7.0.16

2011-07-06 Thread eurotrans-Verlag
Hi all, I’m using Tomcat 7.0.16 on a system with Java 1.6.0_26 on Windows Serer 2008 and wondered about a strange NPE I got shortly after deploying a webapp to Tomcat: SCHWERWIEGEND: An exception or error occurred in the container during the request processing java.lang.NullPointerException

Multiple errors (regressions) on Tomcat 7.0.17

2011-07-03 Thread eurotrans-Verlag
Hi all, today I downloaded the not yet released Tomcat 7.0.17 (downloaded it from http://people.apache.org/~markt/dev/tomcat-7/v7.0.17/bin/ ) to test it on a Windows Server 2008 R2 (64 bit) system with Sun Java 1.6.0_26 (64 bit), using IIS 7.5 and the ISAPI Redirector 1.2.32 (from

RE: Multiple errors (regressions) on Tomcat 7.0.17

2011-07-03 Thread eurotrans-Verlag
Hi Mark, If you explicitly set crawlerUserAgents, that will be resolved. Thanks. 2) When using the ISAPI Redirector 1.2.32 and Tomcat Native 1.1.20 which is included in the windows distribution, I get these errors when a client makes a request to IIS which is redirected to Tomcat,

Canceling Download on IIS7 with ISAPI Redirector 1.2.31 causes 100% CPU usage

2011-05-14 Thread eurotrans-Verlag
Hello everybody, I stumbled upon a strange problem with the ISAPI Redirector 1.2.31 on Windows Server 2008 SP2 (32 bit) with IIS 7.0. The problem is, that when a Servlet is generating lots of data (e.g. 200 MB) and a user downloads it over the Isapi Redirector/IIS7, and cancels the download, the

RE: Canceling Download on IIS7 with ISAPI Redirector 1.2.31 causes 100% CPU usage

2011-05-14 Thread eurotrans-Verlag
Hi André, thanks for your reply. To figure out if this is what's happening, you could do some logging at the servlet end, to see if it keeps sending data even when the client has canceled, or if it itself gets some stop indication from the isapi_redirector (also a closed socket e.g.). Or

NPE instead of '400 Bad Request' response when sending invalid request on Tomcat 7.0.7

2011-02-03 Thread eurotrans-Verlag
Hi all, I noticed that when sending an invalid request to Tomcat 7.0.7 (e.g. without a HTTP method), Tomcat throws a NullPointerException, instead of responding with a 400 Bad Request. If you do a request like this for example: /invalidRequest HTTP/1.1 Host: localhost Then Tomcat prints:

RE: No response buffering in Tomcat 7.0.6?

2011-01-14 Thread eurotrans-Verlag
Hi everybody, thanks for your replies. -Original Message- From: Mark Thomas [mailto:ma...@apache.org] Chunked encoding does not mean that the output is unbuffered. If a client declares support for HTTP/1.1 then web servers are free to use chunked encoding for the response if they