[JBoss JIRA] (WFLY-11672) @ApplicationScoped does not work when used with @ServerEndpoint
by Marek Marusic (Jira)
[ https://issues.jboss.org/browse/WFLY-11672?page=com.atlassian.jira.plugin... ]
Marek Marusic updated WFLY-11672:
---------------------------------
Attachment: applicationScopedServerEndpoint.zip
> @ApplicationScoped does not work when used with @ServerEndpoint
> ---------------------------------------------------------------
>
> Key: WFLY-11672
> URL: https://issues.jboss.org/browse/WFLY-11672
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, Web Sockets
> Affects Versions: 15.0.1.Final
> Reporter: Marek Marusic
> Assignee: Matej Novotny
> Priority: Major
> Attachments: applicationScopedServerEndpoint.zip
>
>
> When the @ApplicationScoped annotation is used in combination with @ServerEndpoint the class is instantiated on every new connection instead of being instantiated once for the whole application.
> The expected behaviour:
> There should be only one instance of the class which is annotated with @ApplicationScoped and @ServerEndpoint annotations.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (WFLY-11672) @ApplicationScoped does not work when used with @ServerEndpoint
by Marek Marusic (Jira)
Marek Marusic created WFLY-11672:
------------------------------------
Summary: @ApplicationScoped does not work when used with @ServerEndpoint
Key: WFLY-11672
URL: https://issues.jboss.org/browse/WFLY-11672
Project: WildFly
Issue Type: Bug
Components: CDI / Weld, Web Sockets
Affects Versions: 15.0.1.Final
Reporter: Marek Marusic
Assignee: Matej Novotny
When the @ApplicationScoped annotation is used in combination with @ServerEndpoint the class is instantiated on every new connection instead of being instantiated once for the whole application.
The expected behaviour:
There should be only one instance of the class which is annotated with @ApplicationScoped and @ServerEndpoint annotations.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (WFLY-10268) TimerService sometimes doesn't invoke timers
by Bartosz Baranowski (Jira)
[ https://issues.jboss.org/browse/WFLY-10268?page=com.atlassian.jira.plugin... ]
Bartosz Baranowski resolved WFLY-10268.
---------------------------------------
Resolution: Cannot Reproduce
> TimerService sometimes doesn't invoke timers
> --------------------------------------------
>
> Key: WFLY-10268
> URL: https://issues.jboss.org/browse/WFLY-10268
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 12.0.0.Final
> Reporter: Rich DiCroce
> Assignee: Bartosz Baranowski
> Priority: Major
> Attachments: WFLY-10268-reproducer.patch
>
>
> The EJB TimerService seems to have a nasty race condition where a scheduled task never gets invoked.
> Because it's racy, it's hard to reproduce, but I've seen it happen fairly often by scheduling a single-action timer with a duration of zero (i.e. should be executed immediately).
> Based on another problem I've been debugging in our application, I suspect that this issue affects all timers, including ones created using the Schedule annotation.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (WFLY-10268) TimerService sometimes doesn't invoke timers
by Bartosz Baranowski (Jira)
[ https://issues.jboss.org/browse/WFLY-10268?page=com.atlassian.jira.plugin... ]
Bartosz Baranowski commented on WFLY-10268:
-------------------------------------------
Unfortunately Im unable to reproduce - though, given latency I thought I could. Given spam it takes timers to invoker EJB, still all of them come through. If you can isolate reproducer please reopen.
> TimerService sometimes doesn't invoke timers
> --------------------------------------------
>
> Key: WFLY-10268
> URL: https://issues.jboss.org/browse/WFLY-10268
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 12.0.0.Final
> Reporter: Rich DiCroce
> Assignee: Bartosz Baranowski
> Priority: Major
> Attachments: WFLY-10268-reproducer.patch
>
>
> The EJB TimerService seems to have a nasty race condition where a scheduled task never gets invoked.
> Because it's racy, it's hard to reproduce, but I've seen it happen fairly often by scheduling a single-action timer with a duration of zero (i.e. should be executed immediately).
> Based on another problem I've been debugging in our application, I suspect that this issue affects all timers, including ones created using the Schedule annotation.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (WFLY-10268) TimerService sometimes doesn't invoke timers
by Bartosz Baranowski (Jira)
[ https://issues.jboss.org/browse/WFLY-10268?page=com.atlassian.jira.plugin... ]
Bartosz Baranowski updated WFLY-10268:
--------------------------------------
Attachment: WFLY-10268-reproducer.patch
> TimerService sometimes doesn't invoke timers
> --------------------------------------------
>
> Key: WFLY-10268
> URL: https://issues.jboss.org/browse/WFLY-10268
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 12.0.0.Final
> Reporter: Rich DiCroce
> Assignee: Bartosz Baranowski
> Priority: Major
> Attachments: WFLY-10268-reproducer.patch
>
>
> The EJB TimerService seems to have a nasty race condition where a scheduled task never gets invoked.
> Because it's racy, it's hard to reproduce, but I've seen it happen fairly often by scheduling a single-action timer with a duration of zero (i.e. should be executed immediately).
> Based on another problem I've been debugging in our application, I suspect that this issue affects all timers, including ones created using the Schedule annotation.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-2262) [DMN Designer] DRD Grid Column width is not preserved
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-2262?page=com.atlassian.jira.plugi... ]
Daniele Zonca commented on DROOLS-2262:
---------------------------------------
[~jomarko] [~manstis]
That ticket is intended to improve full page width for canvas grid component so it is not directly related to this one.
Btw we need to add persistence of column size for sure also in Test Scenario so let me know if the way are you using to implement this can be reused
> [DMN Designer] DRD Grid Column width is not preserved
> -----------------------------------------------------
>
> Key: DROOLS-2262
> URL: https://issues.jboss.org/browse/DROOLS-2262
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.6.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
>
> DND Grid Column don't preserve the width.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (WFLY-10268) TimerService sometimes doesn't invoke timers
by Bartosz Baranowski (Jira)
[ https://issues.jboss.org/browse/WFLY-10268?page=com.atlassian.jira.plugin... ]
Bartosz Baranowski updated WFLY-10268:
--------------------------------------
Attachment: (was: WFLY-10268-reproducer.patch)
> TimerService sometimes doesn't invoke timers
> --------------------------------------------
>
> Key: WFLY-10268
> URL: https://issues.jboss.org/browse/WFLY-10268
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 12.0.0.Final
> Reporter: Rich DiCroce
> Assignee: Bartosz Baranowski
> Priority: Major
>
> The EJB TimerService seems to have a nasty race condition where a scheduled task never gets invoked.
> Because it's racy, it's hard to reproduce, but I've seen it happen fairly often by scheduling a single-action timer with a duration of zero (i.e. should be executed immediately).
> Based on another problem I've been debugging in our application, I suspect that this issue affects all timers, including ones created using the Schedule annotation.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months