[Red Hat JIRA] (WFLY-14199) OnOffOpenTracingTestCase leaves the server in a bad state
by Ronald Sigal (Jira)
[ https://issues.redhat.com/browse/WFLY-14199?page=com.atlassian.jira.plugi... ]
Ronald Sigal updated WFLY-14199:
--------------------------------
Comment: was deleted
(was: [~ehugonnet], are you sure it's 13774? I'm seeing "There isn’t anything to compare." Actually, I don't see a pull request with from you ...)
> OnOffOpenTracingTestCase leaves the server in a bad state
> ---------------------------------------------------------
>
> Key: WFLY-14199
> URL: https://issues.redhat.com/browse/WFLY-14199
> Project: WildFly
> Issue Type: Bug
> Components: MP OpenTracing, Test Suite
> Affects Versions: 22.0.0.Alpha1
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Priority: Major
>
> {color:#333333}OnOffOpenTracingTestCase{color} will leave the server in such a state that SimpleRestClientTestCase will fail. Removing and adding the opentracing subsystem to check that it doesn't work once removed shoudl be reevaluated.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[Red Hat JIRA] (WFLY-14199) OnOffOpenTracingTestCase leaves the server in a bad state
by Ronald Sigal (Jira)
[ https://issues.redhat.com/browse/WFLY-14199?page=com.atlassian.jira.plugi... ]
Ronald Sigal commented on WFLY-14199:
-------------------------------------
[~ehugonnet], are you sure it's 13774? I'm seeing "There isn’t anything to compare." Actually, I don't see a pull request with from you ...
> OnOffOpenTracingTestCase leaves the server in a bad state
> ---------------------------------------------------------
>
> Key: WFLY-14199
> URL: https://issues.redhat.com/browse/WFLY-14199
> Project: WildFly
> Issue Type: Bug
> Components: MP OpenTracing, Test Suite
> Affects Versions: 22.0.0.Alpha1
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Priority: Major
>
> {color:#333333}OnOffOpenTracingTestCase{color} will leave the server in such a state that SimpleRestClientTestCase will fail. Removing and adding the opentracing subsystem to check that it doesn't work once removed shoudl be reevaluated.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[Red Hat JIRA] (WFLY-14208) Review and make easier the removal of non base code
by Yeray Borges Santana (Jira)
Yeray Borges Santana created WFLY-14208:
-------------------------------------------
Summary: Review and make easier the removal of non base code
Key: WFLY-14208
URL: https://issues.redhat.com/browse/WFLY-14208
Project: WildFly
Issue Type: Task
Components: Build System
Reporter: Yeray Borges Santana
Assignee: Yeray Borges Santana
Microprofile functionality (microprofile modules and related test cases) and EE9 modules are not part of the base code.
At least for the Galleon layers implemented on testsuite/layers, we have identified that we are not handling this separation of concerns properly, which could make more difficult the conversion to product.
The task for this Jira is to make this separation more clear, identify any other place where this can occur, and facilitate the easy removal of what is not expected to be part of the base code.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[Red Hat JIRA] (AG-153) Application blocked getting Connection from shared handler cache.
by Jeremy Whiting (Jira)
[ https://issues.redhat.com/browse/AG-153?page=com.atlassian.jira.plugin.sy... ]
Jeremy Whiting commented on AG-153:
-----------------------------------
I am happy for this issue to be closed.
> Application blocked getting Connection from shared handler cache.
> -----------------------------------------------------------------
>
> Key: AG-153
> URL: https://issues.redhat.com/browse/AG-153
> Project: Agroal
> Issue Type: Bug
> Components: pool
> Affects Versions: 1.8
> Reporter: Jeremy Whiting
> Assignee: Luis Barreiro
> Priority: Major
> Attachments: jstack-tree.txt, summary-of-getConnection-method-calls.txt
>
>
> I am inspecting an application that stopped nearly all processing.
> A jstack dump reveals one of the thread pools (40 threads) has all threads blocked waiting for a database Connection. See the "summary-of-getConnection-method-calls.txt" file.
> -There are no other threads that already have a connection leased out.-
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[Red Hat JIRA] (AG-153) Application blocked getting Connection from shared handler cache.
by Jeremy Whiting (Jira)
[ https://issues.redhat.com/browse/AG-153?page=com.atlassian.jira.plugin.sy... ]
Jeremy Whiting commented on AG-153:
-----------------------------------
Thanks for the recommendations [~lbarreiro].
I've investigated further the configuration of the pool. The pool was exhausted. In this situation I've recommended reducing the number of JVM threads that use connections.
> Application blocked getting Connection from shared handler cache.
> -----------------------------------------------------------------
>
> Key: AG-153
> URL: https://issues.redhat.com/browse/AG-153
> Project: Agroal
> Issue Type: Bug
> Components: pool
> Affects Versions: 1.8
> Reporter: Jeremy Whiting
> Assignee: Luis Barreiro
> Priority: Major
> Attachments: jstack-tree.txt, summary-of-getConnection-method-calls.txt
>
>
> I am inspecting an application that stopped nearly all processing.
> A jstack dump reveals one of the thread pools (40 threads) has all threads blocked waiting for a database Connection. See the "summary-of-getConnection-method-calls.txt" file.
> -There are no other threads that already have a connection leased out.-
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months