[weld-issues] [JBoss JIRA] (WELD-2557) Not all events are fired
Title: Message Title Matěj Novotný updated WELD-2557 Weld / WELD-2557 Not all events are fired Change By: Matěj Novotný Status: Pull Request Sent Resolved Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.12.1#712002-sha1:609a505) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2557) Not all events are fired
Title: Message Title Matěj Novotný assigned an issue to Matěj Novotný Weld / WELD-2557 Not all events are fired Change By: Matěj Novotný Assignee: Matěj Novotný Add Comment This message was sent by Atlassian Jira (v7.12.1#712002-sha1:609a505) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2557) Not all events are fired
Title: Message Title Craig McIlwee commented on WELD-2557 Re: Not all events are fired Stefan Gr, I found the linked issue just after I added my comment. Glad to hear that you have a handle on it. Add Comment This message was sent by Atlassian Jira (v7.12.1#712002-sha1:609a505) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2557) Not all events are fired
Title: Message Title Stefan Gr commented on WELD-2557 Re: Not all events are fired Craig McIlwee Please have a look at WFLY-11601. The root cause is already known, but the fix is still pending. As soon as I find some time, I will try to fix it myself based on the comment from Matěj Novotný Add Comment This message was sent by Atlassian Jira (v7.12.1#712002-sha1:609a505) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2557) Not all events are fired
Title: Message Title Craig McIlwee commented on WELD-2557 Re: Not all events are fired I've been having a similar issue for a while as well. I have war files that contain application initialization listeners (@Observes @Initialized(ApplicationScoped.class)) that occasionally are not invoked. No errors in the logs, and as Ste Gr points out, the debug or trace logging from Weld shows that it does find them. I haven't be able to reproduce with a minimal test case. As I slim down my deployments the problem stops occurring, but the intermittent nature of the problem makes it hard to tell if a change I made solves the problem or if it just didn't occur that time. On the other hand, perhaps it's the "larger" deployments (and several of them in the same container) that trigger the possible race condition described above. I don't know if this helps at all, but I never saw this behavior on WildFly 10.1.0.Final but did start seeing it with 14.0.0.Final. I never tried an versions between them to pin it down. Add Comment This message was sent by Atlassian Jira (v7.12.1#712002-sha1:609a505) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2557) Not all events are fired
Title: Message Title Matej Novotny commented on WELD-2557 Re: Not all events are fired I could try to create a minimal example but I don't know if it will trigger the same behavior. Please let me know if I should do that. Yes, that would be great. We have tests for those events fired but obviously those are working. ... "Weld Thread Pool – x" Yea, those are actual Weld threads. ... "MSC service thread x-x" ... And that's JBoss MSC threads bootstrapping WildFly (and Weld inside it). As as site note: It never failed with WildFly 10.0.1.Final Have you tried anything in between 10.0.1.Final and 15.0.1.Final? I am aware of some changes done in Weld's services inside WildFly, but those were quite numerous. Add Comment This message was sent by Atlassian Jira (v7.12.1#712002-sha1:609a505) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2557) Not all events are fired
Title: Message Title Ste Gr commented on WELD-2557 Re: Not all events are fired Thanks for your reply. The app and jar contains a lot of company internal code which I'm not allowed to share I could try to create a minimal example but I don't know if it will trigger the same behavior. Please let me know if I should do that. After some more debugging (with custom log messages) it must be some race condition. The whole CDI bootstrap happens in threads named "Weld Thread Pool – x" & "MSC service thread x-x". The step "START bootstrap > endInitialization" is then in a thread named "ServerService Thread Pool – xxx" which also fires the initialized event. It seems to work every time when enough log output is produced (which again makes it harder to debug) As as site note: It never failed with WildFly 10.0.1.Final Add Comment This message was sent by Atlassian Jira (v7.12.1#712002-sha1:609a505) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2557) Not all events are fired
Title: Message Title Matej Novotny commented on WELD-2557 Re: Not all events are fired Hello Ste Gr thanks for reporting the issue. Would you be able to share the example app you were using? I know it's not a reproducer but it may still be a good starting point. Add Comment This message was sent by Atlassian Jira (v7.12.1#712002-sha1:609a505) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2557) Not all events are fired
Title: Message Title Matej Novotny updated an issue Weld / WELD-2557 Not all events are fired Change By: Matej Novotny Component/s: Servlet Container Support Add Comment This message was sent by Atlassian Jira (v7.12.1#712002-sha1:609a505) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2557) Not all events are fired
Title: Message Title Ste Gr created an issue Weld / WELD-2557 Not all events are fired Issue Type: Bug Affects Versions: 3.0.5.Final Assignee: Unassigned Components: Servlet Container Support Created: 15/Jan/19 5:10 AM Environment: WildFly 15.0.1.Final, JDK 8 / JDK 11 Priority: Major Reporter: Ste Gr I have a war application that contains a jar with commonly used code. Both contain a beans.xml set to version 2.0 and both have a application-scoped bean with an observer method for the initialized event of the application scope. Additionally both have an observer method for the destroyed event of the application scope. My observation is that only the observer inside the war is fire 100% of the time. The initialized-observer in the jar is sometimes ignored. I can't find any pattern when it fires and when not. The destroyed-observer is always fired in both cases (even if the initialized-observer didn't fire). I'm not able to debug the whole thing because it always works as soon as I start the server in debug mode.
