This problem will be fixed in the next release. It was indeed an issue
with AccessController.doPrivileged as Marc had hypothesized below.
Thanks, Marc!
On Thu, Jan 7, 2010 at 4:43 AM, Ftaylor wrote:
> This problem still exists.
>
> On Dec 16 2009, 9:42 pm, polyurethan wrote:
> > Hey there,
> >
This problem still exists.
On Dec 16 2009, 9:42 pm, polyurethan wrote:
> Hey there,
>
> I still get this ClassCastException. When will the JVM be fixed?
> It's Dec and the issue was raised in Jul. Is there any progress?
>
> Thanks,
> Alexander
>
> On Oct 22, 10:13 am, Marc Guillemot wrote:
>
>
>
Hey there,
I still get this ClassCastException. When will the JVM be fixed?
It's Dec and the issue was raised in Jul. Is there any progress?
Thanks,
Alexander
On Oct 22, 10:13 am, Marc Guillemot wrote:
> Don,
>
> I've tried to produce a unit test to open an issue for Jasper... and failed.
>
> I
Don,
I've tried to produce a unit test to open an issue for Jasper... and failed.
I'm now quite sure that this is a bug in the JVM used for GAE.
The JavaDoc of AccessController.doPrivileged (which is a native method)
says that it propagates unchecked exceptions and throws a
PrivilegedActionEx
Ah, you're right actually. I hadn't looked closely enough at that bug.
We'll have to get the Jasper guys to fix that and then upgrade.
Thanks,
Don
On Mon, Oct 19, 2009 at 10:39 AM, Marc Guillemot wrote:
>
> This seems to be a really old issue that relates to something
> different... or do you m
This seems to be a really old issue that relates to something
different... or do you mean that GAE uses a 5 years old version of Jasper?
I've just look at the current sources of PageContextImpl
http://svn.apache.org/repos/asf/tomcat/trunk/java/org/apache/jasper/runtime/PageContextImpl.java
and i
Yes, this is:
https://issues.apache.org/bugzilla/show_bug.cgi?id=31171
We need to bundle a later version of Jasper with the App Engine SDK to fix
this.
On Mon, Oct 19, 2009 at 10:24 AM, Marc Guillemot wrote:
>
> Hi,
>
> any progress on this issue?
>
> Is it possible that it comes from a bug in J
Hi,
any progress on this issue?
Is it possible that it comes from a bug in Jasper, not able to recognize
RuntimeException occurring in a PrivilegedExceptionAction?
// org.apache.jasper.runtime.PageContextImpl
public void handlePageException(final Throwable t) throws IOException,
ServletE
