Thanks for your help.
Davor Hrg wrote:
there's some insight in the rpoblem since it happened for the snippet shown...
... and a workarround..
http://wiki.apache.org/tapestry/Tapestry5HowToRunTaskInThread
Davor Hrg
On 2/29/08, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
There's a workarou
there's some insight in the rpoblem since it happened for the snippet shown...
... and a workarround..
http://wiki.apache.org/tapestry/Tapestry5HowToRunTaskInThread
Davor Hrg
On 2/29/08, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
> There's a workaround for the JDK bug in Tapestry 5.0.10.
>
> O
There's a workaround for the JDK bug in Tapestry 5.0.10.
On Fri, Feb 29, 2008 at 8:40 AM, Baofeng Yu <[EMAIL PROTECTED]> wrote:
> Looks like the NPE problem is due to a JDK 5 bug. After I upgrade JDK to
> 1.6, the problem is fixed.
>
> Baofeng
>
>
>
>
> Baofeng Yu wrote:
> > Yes, it happens co
Looks like the NPE problem is due to a JDK 5 bug. After I upgrade JDK to
1.6, the problem is fixed.
Baofeng
Baofeng Yu wrote:
Yes, it happens consistently when I restart jboss and access the page
the first time after the restart. Afterwards, it's all OK. I am using
5.0.9.
Baofeng
Robert
Yes, it happens consistently when I restart jboss and access the page
the first time after the restart. Afterwards, it's all OK. I am using 5.0.9.
Baofeng
Robert Zeigler wrote:
Does this happen consistently?
I see the same stack trace on occasion. Also using mod_jk, tomcat
4.x, but no jboss
Does this happen consistently?
I see the same stack trace on occasion. Also using mod_jk, tomcat
4.x, but no jboss, and I can't reliably reproduce this issue. It just
pops up on occasion.
So I'd be interested in knowing if you can consistently reproduce this
problem. Btw, what version of
