Bug 1097591 - Multiple instance of the same ServletContainerInitializer can execute on single deployment
Summary: Multiple instance of the same ServletContainerInitializer can execute on sing...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web
Version: 6.2.3,6.3.0,6.2.4
Hardware: Unspecified
OS: Unspecified
low
high
Target Milestone: ---
: EAP 6.4.0
Assignee: Rémy Maucherat
QA Contact: Radim Hatlapatka
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-14 07:01 UTC by baranowb
Modified: 2014-10-07 21:06 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-09-08 12:18:53 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-3353 0 Minor Resolved Multiple instance of the same ServletContainerInitializer can execute on single deployment 2014-09-09 13:22:59 UTC

Description baranowb 2014-05-14 07:01:49 UTC 
This is spawn of: https://issues.jboss.org/browse/WFLY-3353
Related: https://issues.jboss.org/browse/WFLY-3353
Since: https://bugzilla.redhat.com/show_bug.cgi?id=1060740
Comment 1 baranowb 2014-05-14 07:08:27 UTC 
Related should be: https://issues.jboss.org/browse/JBWEB-298
Comment 2 baranowb 2014-05-14 12:35:59 UTC 
Simple test case: https://github.com/baranowb/jboss-eap/tree/BZ-1097591
Comment 3 JBoss JIRA Server 2014-05-16 14:32:04 UTC 
Stuart Douglas <stuart.w.douglas> updated the status of jira WFLY-3353 to Resolved
Comment 4 Radim Hatlapatka 2014-08-01 13:37:58 UTC 
Issue is still valid in latest build EAP 6.3.0.ER10
Comment 5 Rémy Maucherat 2014-09-02 16:09:26 UTC 
WFLY-3353 was rejected by Stuart.
Comment 6 baranowb 2014-09-02 16:58:02 UTC 
IMHO a bad choice. NPE from jboss-web looks bad, indication of something not being handled properly.
Comment 7 Rémy Maucherat 2014-09-03 07:56:58 UTC 
Ok, so you refer specifically to the websockets SCI. However, on this issue, if it's not going to be addressed in WF, it's not going to happen in EAP either.
Comment 8 baranowb 2014-09-03 08:17:11 UTC 
Yes, I understand. This could happen not only with WebSockets SCI. Bad deployment could cause NPE which is confusing.
Comment 9 Rémy Maucherat 2014-09-08 12:18:53 UTC 
Not actually fixed [rejected upstream], but the Websockets SCI should no longer cause a NPE after r2499 in web.
Note You need to log in before you can comment on or make changes to this bug.