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 e
hreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at
java.lang.Thread.run(Unknown Source)
In this, the first session gave an error on the second use of the page,
i.e. the first reload. However, the second session didn&#x
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 s
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 hou
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 happe
ing 'synchronized'. I've not seen
anything in recent postings to this list.
I wondered whether the problem might be caused by the browser creating
malformed cookies, or some such. (I'm using session-handling.) However,
this seems unlikely, as the error occurs regardless of whether
