tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Köberl (JIRA) <j...@apache.org>
Subject [jira] [Commented] (TAP5-2152) NPE in Form on Websphere 8 after applying load
Date Thu, 28 Aug 2014 06:05:58 GMT

    [ https://issues.apache.org/jira/browse/TAP5-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14113395#comment-14113395

Christian Köberl commented on TAP5-2152:

We analyzed this problem with IBM - they could not find the reason. So we deactivated JIT
for all Tapestry managed classes (pages, components, ...) in production. This worked.

In parallel we upgraded the next release to Tapestry 5.3.x where the problem does not occur.
The problem seems to with javassist and IBM VM and Tapestry. 5.4.x will not use javassist
so I think the problem will not occur on newer versions of Tapestry.

(sorry for not documenting our progress on this issue)

> NPE in Form on Websphere 8 after applying load
> ----------------------------------------------
>                 Key: TAP5-2152
>                 URL: https://issues.apache.org/jira/browse/TAP5-2152
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.2.6
>            Reporter: Christian Köberl
>              Labels: websphere
> A NullPointerException occurs Form.java:406 (Tapestry 5.2.6) when applying load - in
any application deployed to Websphere 8.
> Here's the corresponding line from Form.java:406:
> resources.triggerEvent(EventConstants.PREPARE_FOR_RENDER, context, null);
> The NPE first is raised after some parallel users are working with the application -
before that everything works fine. After the first occurrence, the NPE is raised on *any*
Form render on *any* page for *all* users. We have to restart the application to get it working
again. We can reproduce the error with some load but the first NPE happens on different pages
- so that's no clue.
> The behavior can be reproduced with a quite simple application with some pages with forms:
> The behavior *cannot* be reproduced with JIT turned off.

This message was sent by Atlassian JIRA

View raw message