4.0.1 Hotspot JVM bug?

[Barry Books <tr...@gmail.com>]

I've got a bug that only occurs with Firefox as the browser and
Tomcat/Solaris 10 on x86 with the -server option to the jvm. On some
pages it seems the state objects do not get set correctly often
resulting in null pointer exceptions. Reloading the page may or may
not fix the problem.

This does not happen with Safari or IE and does not happen with
Firefox combined with Tomcat running on OSX or Linux. Switching the
jvm to -client fixes the problem on Solaris. It's also any version of
Firefox running on either Mac or Windows.

Has anyone seen anything like this?

Thanks
Barry

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org

Re: 4.0.1 Hotspot JVM bug?

[Barry Books <tr...@gmail.com>]

I suspect that it's a threading issue that goes away when the jvm is
switched from server to client, but the dependency on Firefox has me a
bit puzzled. Stepping with a debugger might find it but my production
system is Solaris and my development environment is OSX. Also if it's
a threading issue stepping on my development system might not find it
anyway.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org

Re: 4.0.1 Hotspot JVM bug?

[Kalle Korhonen <ka...@gmail.com>]

My experience is that unless the JVM crashes, in 95% of the cases it's not a
bug in JVM even if you may suspect so. The fact that it's browser dependent,
makes it even less likely that it'd be a bug in the JVM. To me, this one
sounds like a concurrency/threading issue. Is this in Tap4.x? In that case
maybe a bug in Hivemind, or the way you are using it, such as how you
initialize the state object. I'd step through it in the debugger, checking
threadlocals and the point where your state object factory is called.

Kalle


On 7/5/07, Barry Books <tr...@gmail.com> wrote:
>
> I've got a bug that only occurs with Firefox as the browser and
> Tomcat/Solaris 10 on x86 with the -server option to the jvm. On some
> pages it seems the state objects do not get set correctly often
> resulting in null pointer exceptions. Reloading the page may or may
> not fix the problem.
>
> This does not happen with Safari or IE and does not happen with
> Firefox combined with Tomcat running on OSX or Linux. Switching the
> jvm to -client fixes the problem on Solaris. It's also any version of
> Firefox running on either Mac or Windows.
>
> Has anyone seen anything like this?
>
> Thanks
> Barry
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>