[JBoss JIRA] (WFLY-13177) ManagedExecutorService: Wrong activeRequestCount at RequestController on RejectedExecutionException
by Guido Jäkel (Jira)
[ https://issues.redhat.com/browse/WFLY-13177?page=com.atlassian.jira.plugi... ]
Guido Jäkel updated WFLY-13177:
-------------------------------
Steps to Reproduce:
* Configure a ManagedExecutorService with a limited pool and queuesize
* Let an application fill out the pool and queue with threads -> see the number of active requests stated by the RequestController is as expected
* Submit/Execute one more thread to get a RejectedExecutionException as expected -> see the number of active request is erronous incremented by each of such event.
was:
* Configure a ManagedExecutorService with a limited pool and queuesize
* Let an application fill out the pool and queue with threads -> see the number of active requests stated by the RequestController is as expected
* Submit/Execute one more thread to get a RejectedExecutionException as expected -> see the number of active request is erronously incremented by each of such event.
> ManagedExecutorService: Wrong activeRequestCount at RequestController on RejectedExecutionException
> ---------------------------------------------------------------------------------------------------
>
> Key: WFLY-13177
> URL: https://issues.redhat.com/browse/WFLY-13177
> Project: WildFly
> Issue Type: Bug
> Components: EE, Server
> Affects Versions: 10.1.0.Final, 16.0.0.Final
> Reporter: Guido Jäkel
> Assignee: Brian Stansberry
> Priority: Major
>
> On WF-10 and WF-16 we observe a serious bug of the RequestCount of the RequestController while using ManagedExecutorService.submit() or ...execute() in the edge case of a full queue. In this case, the caller gets a RejectedExecutionException, but in the RequestController, the number of active requests is erroneously incremented.
> This will lead to a false and monotonously increasing number of active requests. And in case of a limitation configured by the maxRequestCount feature, which is best practice for production environments, over the time this will lead to deadlock of the RequestController and herewith the complete activity of the Wildfly at all.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (WFLY-13177) ManagedExecutorService: Wrong activeRequestCount at RequestController on RejectedExecutionException
by Guido Jäkel (Jira)
[ https://issues.redhat.com/browse/WFLY-13177?page=com.atlassian.jira.plugi... ]
Guido Jäkel updated WFLY-13177:
-------------------------------
Steps to Reproduce:
* Configure a ManagedExecutorService with a limited pool and queuesize
* Let an application fill out the pool and queue with threads -> see the number of active requests stated by the RequestController is as expected
* Submit/Execute one more thread to get a RejectedExecutionException as expected -> see the number of active request is erroneously incremented by each of such event.
was:
* Configure a ManagedExecutorService with a limited pool and queuesize
* Let an application fill out the pool and queue with threads -> see the number of active requests stated by the RequestController is as expected
* Submit/Execute one more thread to get a RejectedExecutionException as expected -> see the number of active request is erronous incremented by each of such event.
> ManagedExecutorService: Wrong activeRequestCount at RequestController on RejectedExecutionException
> ---------------------------------------------------------------------------------------------------
>
> Key: WFLY-13177
> URL: https://issues.redhat.com/browse/WFLY-13177
> Project: WildFly
> Issue Type: Bug
> Components: EE, Server
> Affects Versions: 10.1.0.Final, 16.0.0.Final
> Reporter: Guido Jäkel
> Assignee: Brian Stansberry
> Priority: Major
>
> On WF-10 and WF-16 we observe a serious bug of the RequestCount of the RequestController while using ManagedExecutorService.submit() or ...execute() in the edge case of a full queue. In this case, the caller gets a RejectedExecutionException, but in the RequestController, the number of active requests is erroneously incremented.
> This will lead to a false and monotonously increasing number of active requests. And in case of a limitation configured by the maxRequestCount feature, which is best practice for production environments, over the time this will lead to deadlock of the RequestController and herewith the complete activity of the Wildfly at all.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (WFLY-13177) ManagedExecutorService: Wrong activeRequestCount at RequestController on RejectedExecutionException
by Guido Jäkel (Jira)
[ https://issues.redhat.com/browse/WFLY-13177?page=com.atlassian.jira.plugi... ]
Guido Jäkel updated WFLY-13177:
-------------------------------
Steps to Reproduce:
* Configure a ManagedExecutorService with a limited pool and queuesize
* Let an application fill out the pool and queue with threads -> see the number of active requests stated by the RequestController is as expected
* Submit/Execute one more thread to get a RejectedExecutionException as expected -> see the number of active request is erronously incremented by each of such event.
was:
* Configure a ManagedExecutorService with a limited pool and queuesize
* Let an application fill out the pool and queue with threads -> see the number of active requests stated by the RequestController is as expeted
* Submit/Execute one more thread to get a RejectedExecutionException as expected -> see the number of active request is errounously incremended by each of such event.
> ManagedExecutorService: Wrong activeRequestCount at RequestController on RejectedExecutionException
> ---------------------------------------------------------------------------------------------------
>
> Key: WFLY-13177
> URL: https://issues.redhat.com/browse/WFLY-13177
> Project: WildFly
> Issue Type: Bug
> Components: EE, Server
> Affects Versions: 10.1.0.Final, 16.0.0.Final
> Reporter: Guido Jäkel
> Assignee: Brian Stansberry
> Priority: Major
>
> On WF-10 and WF-16 we observe a serious bug of the RequestCount of the RequestController while using ManagedExecutorService.submit() or ...execute() in the edge case of a full queue. In this case, the caller gets a RejectedExecutionException, but in the RequestController, the number of active requests is erroneously incremented.
> This will lead to a false and monotonously increasing number of active requests. And in case of a limitation configured by the maxRequestCount feature, which is best practice for production environments, over the time this will lead to deadlock of the RequestController and herewith the complete activity of the Wildfly at all.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (WFLY-13177) ManagedExecutorService: Wrong activeRequestCount at RequestController on RejectedExecutionException
by Guido Jäkel (Jira)
[ https://issues.redhat.com/browse/WFLY-13177?page=com.atlassian.jira.plugi... ]
Guido Jäkel updated WFLY-13177:
-------------------------------
Summary: ManagedExecutorService: Wrong activeRequestCount at RequestController on RejectedExecutionException (was: ManagedExecutorService: Wrong RequestCount on RejectedExecutionException)
> ManagedExecutorService: Wrong activeRequestCount at RequestController on RejectedExecutionException
> ---------------------------------------------------------------------------------------------------
>
> Key: WFLY-13177
> URL: https://issues.redhat.com/browse/WFLY-13177
> Project: WildFly
> Issue Type: Bug
> Components: EE, Server
> Affects Versions: 10.1.0.Final, 16.0.0.Final
> Reporter: Guido Jäkel
> Assignee: Brian Stansberry
> Priority: Major
>
> On WF-10 and WF-16 we observe a serious bug of the RequestCount of the RequestController while using ManagedExecutorService.submit() or ...execute() in the edge case of a full queue. In this case, the caller gets a RejectedExecutionException, but in the RequestController, the number of active requests is erroneously incremented.
> This will lead to a false and monotonously increasing number of active requests. And in case of a limitation configured by the maxRequestCount feature, which is best practice for production environments, over the time this will lead to deadlock of the RequestController and herewith the complete activity of the Wildfly at all.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (WFLY-13177) ManagedExecutorService: Wrong RequestCount on RejectedExecutionException
by Guido Jäkel (Jira)
[ https://issues.redhat.com/browse/WFLY-13177?page=com.atlassian.jira.plugi... ]
Guido Jäkel updated WFLY-13177:
-------------------------------
Summary: ManagedExecutorService: Wrong RequestCount on RejectedExecutionException (was: ManagedExecutorService: Wrong RequestCount on Exception )
> ManagedExecutorService: Wrong RequestCount on RejectedExecutionException
> ------------------------------------------------------------------------
>
> Key: WFLY-13177
> URL: https://issues.redhat.com/browse/WFLY-13177
> Project: WildFly
> Issue Type: Bug
> Components: EE, Server
> Affects Versions: 10.1.0.Final, 16.0.0.Final
> Reporter: Guido Jäkel
> Assignee: Brian Stansberry
> Priority: Major
>
> On WF-10 and WF-16 we observe a serious bug of the RequestCount of the RequestController while using ManagedExecutorService.submit() or ...execute() in the edge case of a full queue. In this case, the caller gets a RejectedExecutionException, but in the RequestController, the number of active requests is erroneously incremented.
> This will lead to a false and monotonously increasing number of active requests. And in case of a limitation configured by the maxRequestCount feature, which is best practice for production environments, over the time this will lead to deadlock of the RequestController and herewith the complete activity of the Wildfly at all.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (WFLY-13177) ManagedExecutorService: Wrong RequestCount on Exception
by Guido Jäkel (Jira)
Guido Jäkel created WFLY-13177:
----------------------------------
Summary: ManagedExecutorService: Wrong RequestCount on Exception
Key: WFLY-13177
URL: https://issues.redhat.com/browse/WFLY-13177
Project: WildFly
Issue Type: Bug
Components: EE, Server
Affects Versions: 16.0.0.Final, 10.1.0.Final
Reporter: Guido Jäkel
Assignee: Brian Stansberry
On WF-10 and WF-16 we observe a serious bug of the RequestCount of the RequestController while using ManagedExecutorService.submit() or ...execute() in the edge case of a full queue. In this case, the caller gets a RejectedExecutionException, but in the RequestController, the number of active requests is erroneously incremented.
This will lead to a false and monotonously increasing number of active requests. And in case of a limitation configured by the maxRequestCount feature, which is best practice for production environments, over the time this will lead to deadlock of the RequestController and herewith the complete activity of the Wildfly at all.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (WFLY-13175) Expressions in jboss-ejb-client.xml don't work for client-context invocation-timeout
by Cheng Fang (Jira)
[ https://issues.redhat.com/browse/WFLY-13175?page=com.atlassian.jira.plugi... ]
Cheng Fang commented on WFLY-13175:
-----------------------------------
Looks like another {{client-context}} attribute, {{deployment-node-selector}} does not honor expression either.
> Expressions in jboss-ejb-client.xml don't work for client-context invocation-timeout
> ------------------------------------------------------------------------------------
>
> Key: WFLY-13175
> URL: https://issues.redhat.com/browse/WFLY-13175
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Cheng Fang
> Assignee: Cheng Fang
> Priority: Minor
>
> [WFLY-4303] made it possible to use expressions in jboss-ejb-client.xml
> However that doesn't seem to work everywhere. We tried to make several especially timeout related properties configurable and while expressions work at most places, in the case of {{client-context invocation-timeout}} they don't and we get a java.lang.NumberFormatException for the string specified as the value of the invocation-timeout.
> Would it be possible to make the {{client-context invocation-timeout}} work with expressions as well?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (WFLY-13176) Add jboss-ejb-client_1_3.xsd schema
by Cheng Fang (Jira)
Cheng Fang created WFLY-13176:
---------------------------------
Summary: Add jboss-ejb-client_1_3.xsd schema
Key: WFLY-13176
URL: https://issues.redhat.com/browse/WFLY-13176
Project: WildFly
Issue Type: Bug
Components: EJB
Reporter: Cheng Fang
Assignee: Cheng Fang
WildFly currently (2020-02-28) includes schemas 1.0, 1.1, 1.2, but not 1.3:
{code}
./src/main/resources/schema/jboss-ejb-client_1_1.xsd
./src/main/resources/schema/jboss-ejb-client_1_0.xsd
./src/main/resources/schema/jboss-ejb-client_1_2.xsd
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (WFLY-13175) Expressions in jboss-ejb-client.xml don't work for client-context invocation-timeout
by Cheng Fang (Jira)
[ https://issues.redhat.com/browse/WFLY-13175?page=com.atlassian.jira.plugi... ]
Cheng Fang moved JBEAP-18837 to WFLY-13175:
-------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-13175 (was: JBEAP-18837)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: EJB
(was: EJB)
Affects Version/s: (was: 7.2.4.GA)
> Expressions in jboss-ejb-client.xml don't work for client-context invocation-timeout
> ------------------------------------------------------------------------------------
>
> Key: WFLY-13175
> URL: https://issues.redhat.com/browse/WFLY-13175
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Cheng Fang
> Assignee: Cheng Fang
> Priority: Minor
>
> [WFLY-4303] made it possible to use expressions in jboss-ejb-client.xml
> However that doesn't seem to work everywhere. We tried to make several especially timeout related properties configurable and while expressions work at most places, in the case of {{client-context invocation-timeout}} they don't and we get a java.lang.NumberFormatException for the string specified as the value of the invocation-timeout.
> Would it be possible to make the {{client-context invocation-timeout}} work with expressions as well?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months
[JBoss JIRA] (WFLY-13174) Improve the WFLYSRV0002 error message
by Carlo de Wolf (Jira)
Carlo de Wolf created WFLY-13174:
------------------------------------
Summary: Improve the WFLYSRV0002 error message
Key: WFLY-13174
URL: https://issues.redhat.com/browse/WFLY-13174
Project: WildFly
Issue Type: Enhancement
Reporter: Carlo de Wolf
Assignee: Brian Stansberry
Currently WFLYSRV0002 is reported as an error and the associated exception is swallowed.
{noformat}
WFLYSRV0002: Could not read provided index
{noformat}
It should really be a warning with details of the exception.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 7 months