On 20 June 2011 17:02, Christopher Schultz ch...@christopherschultz.net wrote:
That depends on what Service.logHit does. If it only uses the
HttpServletRequest object during the method's lifetime, then everything
is fine. If it retains a reference to the request object, you will
probably end
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Calum,
On 6/21/2011 4:26 AM, Calum wrote:
On 20 June 2011 17:02, Christopher Schultz ch...@christopherschultz.net
wrote:
That depends on what Service.logHit does. If it only uses the
HttpServletRequest object during the method's lifetime, then
On 15 June 2011 18:54, Konstantin Kolinko knst.koli...@gmail.com wrote:
The request and response objects must never be accessed outside the
request processing cycle. The objects are recycled and cleared or
reused for subsequent request and responses, and are not guaranteed to
be thread-safe.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Calum,
On 6/20/2011 6:12 AM, Calum wrote:
On 15 June 2011 18:54, Konstantin Kolinko knst.koli...@gmail.com wrote:
The request and response objects must never be accessed outside the
request processing cycle. The objects are recycled and cleared
On Wed, 15 Jun 2011, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jocelyn,
On 6/15/2011 1:43 PM, Jocelyn Ireson-Paine wrote:
ResponseHolder rh = (ResponseHolder)this_session.getAttribute(
response_holder );
Here is the beginning of your errors.
By saving
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jocelyn,
On 6/20/2011 4:11 PM, Jocelyn Ireson-Paine wrote:
I do put a reference to
the response into an instance, in order that I can give my main
processing method all the data it needs (including the response) as one
single parameter. But I'd
About a week ago, I reported what seemed like a sporadic null-pointer
exception from response.encodeUrl. I've managed to simplify the code that
provokes it, and will show it below. My original report, with details of
the Tomcat version and so on, is after this mail.
The error occurred in a
2011/6/15 Jocelyn Ireson-Paine p...@j-paine.org:
ResponseHolder rh = (ResponseHolder)this_session.getAttribute(
response_holder );
out.println( rh = + rh + .BR );
if ( rh == null ) {
out.println( rh is null.BR );
rh = new ResponseHolder( response );
donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
Date: Wed, 15 Jun 2011 18:43:21 +0100
From: p...@j-paine.org
To: users@tomcat.apache.org
Subject: Re: Null-pointer exception from response.encodeUrl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jocelyn,
On 6/15/2011 1:43 PM, Jocelyn Ireson-Paine wrote:
ResponseHolder rh = (ResponseHolder)this_session.getAttribute(
response_holder );
Here is the beginning of your errors.
By saving a reference to the response that was used for your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Chuck,
On 06/09/2011 07:52 AM, Caldarale, Charles R wrote:
Can you display the original request URL, or perhaps enable the
AccessLogValve? (I'm not sure if that captures forwards, however.)
It does. The redirect URL set to the client can be
Thomas Freitag wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Chuck,
On 06/09/2011 07:52 AM, Caldarale, Charles R wrote:
Can you display the original request URL, or perhaps enable the AccessLogValve?
(I'm not sure if that captures forwards, however.)
It does. The redirect URL
Am Donnerstag, den 09.06.2011, 04:53 +0100 schrieb Jocelyn Ireson-Paine:
Hi,
I'm getting sporadic null-pointer exceptions from 'response.encodeUrl'.
This is with Tomcat 7.0.14, the latest stable version to which I upgraded
an hour ago, and Java 1.6.0_26, which again I upgraded to at the
On Thu, 9 Jun 2011, André Warnier wrote:
...
By the way :
(Interface HttpServletResponse, Javaee 5)
encodeUrl
String encodeUrl(String url)
Deprecated. As of version 2.1, use encodeURL(String url) instead
Maybe it's worth replacing encodeUrl by encodeURL, and see if the problem
still
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi André,
On 09.06.11 um 09:07, André Warnier wrote:
It does. The redirect URL set to the client can be logged with %{Location}o.
I don't think we are talking about a redirect response sent to the client
here.
That would definitely /not/ work
On Thu, 9 Jun 2011, Felix Schumacher wrote:
Am Donnerstag, den 09.06.2011, 04:53 +0100 schrieb Jocelyn Ireson-Paine:
Hi,
I'm getting sporadic null-pointer exceptions from 'response.encodeUrl'.
This is with Tomcat 7.0.14, the latest stable version to which I upgraded
an hour ago, and Java
On Thu, 9 Jun 2011, Caldarale, Charles R wrote:
From: Jocelyn Ireson-Paine [mailto:p...@j-paine.org] Subject:
Null-pointer exception from response.encodeUrl under Windows Tomcat 7
I'm getting sporadic null-pointer exceptions from
'response.encodeUrl'.
First off, let me say that it's
On 09/06/2011 06:52, Caldarale, Charles R wrote:
From: Jocelyn Ireson-Paine [mailto:p...@j-paine.org]
Subject: Null-pointer exception from response.encodeUrl under Windows Tomcat
7
I'm getting sporadic null-pointer exceptions from
'response.encodeUrl'.
First off, let me say that it's
Am Donnerstag, den 09.06.2011, 09:40 +0100 schrieb Jocelyn Ireson-Paine:
On Thu, 9 Jun 2011, Felix Schumacher wrote:
Am Donnerstag, den 09.06.2011, 04:53 +0100 schrieb Jocelyn Ireson-Paine:
Hi,
I'm getting sporadic null-pointer exceptions from 'response.encodeUrl'.
This is with Tomcat
, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
Date: Thu, 9 Jun 2011 09:06:52 +0100
From: p...@j-paine.org
To: users@tomcat.apache.org; users@tomcat.apache.org
Subject: Re: Null-pointer exception from response.encodeUrl under Windows
Tomcat 7
On Thu, 9 Jun 2011, André
From: Martin Gainty [mailto:mgai...@hotmail.com]
Subject: RE: Null-pointer exception from response.encodeUrl under Windows
Tomcat 7
place servletapi-2.3.jar in $CATALINA_HOME/bin
Absolute rubbish. Never, never do that.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL
To: users@tomcat.apache.org; users@tomcat.apache.org
Subject: Re: Null-pointer exception from response.encodeUrl under Windows
Tomcat 7
On Thu, 9 Jun 2011, André Warnier wrote:
...
By the way :
(Interface HttpServletResponse, Javaee 5)
encodeUrl
String encodeUrl(String url
Hi,
I'm getting sporadic null-pointer exceptions from 'response.encodeUrl'.
This is with Tomcat 7.0.14, the latest stable version to which I upgraded
an hour ago, and Java 1.6.0_26, which again I upgraded to at the same
time, under Windows XP. I also got the error under Tomcat 5.5.33, which
From: Jocelyn Ireson-Paine [mailto:p...@j-paine.org]
Subject: Null-pointer exception from response.encodeUrl under Windows Tomcat 7
I'm getting sporadic null-pointer exceptions from
'response.encodeUrl'.
First off, let me say that it's an unexpected pleasure to read such a complete
24 matches
Mail list logo
