[jira] [Created] (TAP5-2152) NPE in Form on Websphere 8 after applying load
Christian Köberl created TAP5-2152: -- Summary: 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 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: https://github.com/porscheinformatik/tapestry-was8 The behavior *cannot* be reproduced with JIT turned off. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-2152) NPE in Form on Websphere 8 after applying load
[ https://issues.apache.org/jira/browse/TAP5-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725177#comment-13725177 ] Christian Köberl commented on TAP5-2152: The problem cannot be reproduced with JIT disabled - we're just investigating this with IBM. 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: https://github.com/porscheinformatik/tapestry-was8 The behavior *cannot* be reproduced with JIT turned off. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-2152) NPE in Form on Websphere 8 after applying load
[ https://issues.apache.org/jira/browse/TAP5-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725176#comment-13725176 ] Christian Köberl commented on TAP5-2152: The problem can only be reproduced with Tapestry 5.2.6, Tapestry 5.3.7 seems not to trigger the NPE (this could be due to the remove of javassist). 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: https://github.com/porscheinformatik/tapestry-was8 The behavior *cannot* be reproduced with JIT turned off. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (TAP5-2153) Adapt quickstart archetype generated sources to be bootstrap and 5.4 compatibile
Massimo Lusetti created TAP5-2153: - Summary: Adapt quickstart archetype generated sources to be bootstrap and 5.4 compatibile Key: TAP5-2153 URL: https://issues.apache.org/jira/browse/TAP5-2153 Project: Tapestry 5 Issue Type: Improvement Components: quickstart Affects Versions: 5.4 Reporter: Massimo Lusetti Current quickstart is based on an old HTML/CSS template which doesn't use bootstrap nor jquery. It would be nice to have the source code generated by the latest quickstart archetype to follow the choice from core -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-2070) Respond with a HTTP 404 if the page is activated with an activation context not explicitly supported by the page itself
[
https://issues.apache.org/jira/browse/TAP5-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725320#comment-13725320
]
Massimo Lusetti commented on TAP5-2070:
---
Any comment on this?!
Does we want to ship with the current behavior?
Respond with a HTTP 404 if the page is activated with an activation context
not explicitly supported by the page itself
---
Key: TAP5-2070
URL: https://issues.apache.org/jira/browse/TAP5-2070
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Reporter: Massimo Lusetti
Assignee: Massimo Lusetti
Attachments:
0001-TAP5-2070-Implement-logic-for-recognize-requests-to-.patch
The behavior from day one for pages within Tapestry is to being able to serve
requests that come with an activation context with more parameters that the
ones declared by the page itself.
This feature lead the framework to serve requests that comes to URL which are
not explicitly declared by the pages, for example a page named: Super with an
activation event handler method like this one:
onActivate(String character) { ... }
will finely serve requests for:
/super/mario
/super/luigi
/super/wario
/super/waluigi
but it will also serve requests for:
/super/mario/luigi/wario/waluigi
This issue is to change that behavior.
If the page does declare a specific activation event handler method the
corresponding serving URLs should adhere strictly, otherwise a HTTP 404 is
raised.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-2070) Respond with a HTTP 404 if the page is activated with an activation context not explicitly supported by the page itself
[
https://issues.apache.org/jira/browse/TAP5-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Massimo Lusetti updated TAP5-2070:
--
Affects Version/s: 5.4
Respond with a HTTP 404 if the page is activated with an activation context
not explicitly supported by the page itself
---
Key: TAP5-2070
URL: https://issues.apache.org/jira/browse/TAP5-2070
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.4
Reporter: Massimo Lusetti
Assignee: Massimo Lusetti
Attachments:
0001-TAP5-2070-Implement-logic-for-recognize-requests-to-.patch
The behavior from day one for pages within Tapestry is to being able to serve
requests that come with an activation context with more parameters that the
ones declared by the page itself.
This feature lead the framework to serve requests that comes to URL which are
not explicitly declared by the pages, for example a page named: Super with an
activation event handler method like this one:
onActivate(String character) { ... }
will finely serve requests for:
/super/mario
/super/luigi
/super/wario
/super/waluigi
but it will also serve requests for:
/super/mario/luigi/wario/waluigi
This issue is to change that behavior.
If the page does declare a specific activation event handler method the
corresponding serving URLs should adhere strictly, otherwise a HTTP 404 is
raised.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-2070) Respond with a HTTP 404 if the page is activated with an activation context not explicitly supported by the page itself
[
https://issues.apache.org/jira/browse/TAP5-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13725340#comment-13725340
]
Lenny Primak commented on TAP5-2070:
I would love to get this fix incorporated. I currently use this code in the
index page to work around this issue:
8 /**
9* Restore 404 Not Found errors
10 * @param context
11 * @return
12 */
13 HttpError onActivate(EventContext context)
14 {
15 if (context.getCount() == 0)
16 {
17 return null;
18 }
19
20 return new HttpError(404, Resource not found.);
21 }
Respond with a HTTP 404 if the page is activated with an activation context
not explicitly supported by the page itself
---
Key: TAP5-2070
URL: https://issues.apache.org/jira/browse/TAP5-2070
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.4
Reporter: Massimo Lusetti
Assignee: Massimo Lusetti
Attachments:
0001-TAP5-2070-Implement-logic-for-recognize-requests-to-.patch
The behavior from day one for pages within Tapestry is to being able to serve
requests that come with an activation context with more parameters that the
ones declared by the page itself.
This feature lead the framework to serve requests that comes to URL which are
not explicitly declared by the pages, for example a page named: Super with an
activation event handler method like this one:
onActivate(String character) { ... }
will finely serve requests for:
/super/mario
/super/luigi
/super/wario
/super/waluigi
but it will also serve requests for:
/super/mario/luigi/wario/waluigi
This issue is to change that behavior.
If the page does declare a specific activation event handler method the
corresponding serving URLs should adhere strictly, otherwise a HTTP 404 is
raised.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
