[JBoss JIRA] (ISPN-9863) Testsuite leaks threads
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-9863?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-9863:
-------------------------------
Status: Pull Request Sent (was: Reopened)
Needed an update because it wasn't always catching leaks in the spring5 modules, depending on whether the last test to run called TestResourceTracker or not. This made me change the strategy a bit in a new PR:
* Move leak detection to a @AfterSuite configuration method.
That way leak detection works even if the last test does not
extend AbstractInfinispanTest.
* Also move detection of wrong/missing groups or testName
to a @BeforeSuite method + fix LimitExpiryFactoryTest.
* TestNG modules run ThreadLeakCheckTest from commons-test.
* JUnit modules check for thread leaks in JUnitTestListener
and/or TestResourceTrackingListener.
* JUnitTestListener.testRunFinished failures still build, so tests that
may leak threads should use TestResourceTrackingListener.
> Testsuite leaks threads
> -----------------------
>
> Key: ISPN-9863
> URL: https://issues.jboss.org/browse/ISPN-9863
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Server
> Affects Versions: 10.0.0.Alpha2, 9.4.5.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Labels: testsuite_stability
> Fix For: 10.0.0.Beta3
>
>
> Some hotrod-client tests do not stop their {{RemoteCacheManager}} instances. This was fine before ISPN-8619, but the Netty-based client starts event loop threads and we need to stop them.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (ISPN-10013) Observability: Distributed tracing
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10013?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10013:
-----------------------------------
Summary: Observability: Distributed tracing (was: Observability: Dsitributed tracing)
> Observability: Distributed tracing
> ----------------------------------
>
> Key: ISPN-10013
> URL: https://issues.jboss.org/browse/ISPN-10013
> Project: Infinispan
> Issue Type: Sub-task
> Components: JMX, reporting and management
> Reporter: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> We need to add tracing capabalities so that they can be exported/consumed by Jaeger.
> We should use the following spans:
> * container (the default span)
> * persistence (cache stores and loaders)
> * cluster (for same-cluster remoting)
> * xsite (for xsite cluster remoting)
> * security (for authenticaton/authorization)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (ISPN-10013) Observability: Dsitributed tracing
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10013?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10013:
-----------------------------------
Description:
We need to add tracing capabalities so that they can be exported/consumed by Jaeger.
We should use the following spans:
* container (the default span)
* persistence (cache stores and loaders)
* cluster (for same-cluster remoting)
* xsite (for xsite cluster remoting)
* security (for authenticaton/authorization)
was:We need to add tracing capabalities so that they can be exported/consumed by Jaeger.
> Observability: Dsitributed tracing
> ----------------------------------
>
> Key: ISPN-10013
> URL: https://issues.jboss.org/browse/ISPN-10013
> Project: Infinispan
> Issue Type: Sub-task
> Components: JMX, reporting and management
> Reporter: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> We need to add tracing capabalities so that they can be exported/consumed by Jaeger.
> We should use the following spans:
> * container (the default span)
> * persistence (cache stores and loaders)
> * cluster (for same-cluster remoting)
> * xsite (for xsite cluster remoting)
> * security (for authenticaton/authorization)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (ISPN-10018) Observability: clean up logging categories
by Tristan Tarrant (Jira)
Tristan Tarrant created ISPN-10018:
--------------------------------------
Summary: Observability: clean up logging categories
Key: ISPN-10018
URL: https://issues.jboss.org/browse/ISPN-10018
Project: Infinispan
Issue Type: Sub-task
Components: JMX, reporting and management
Affects Versions: 10.0.0.Beta2
Reporter: Tristan Tarrant
Fix For: 10.0.0.Final
For logs with level INFO, WARN, ERROR, FATAL we want to use specific categories instead of the fully-qualified class name.
The following is a list of categories:
* org.infinispan.CLUSTER: messages related to clustering (state transfer, rebalancing, partitioning, etc)
* org.infinispan.CONFIG: messages related to configuration
* org.infinispan.PERSISTENCE: messages related to loaders/stores
* org.infinispan.SECURITY: messages related to security
* org.infinispan.CONTAINER: messages related to the data container (e.g. expiration, eviction, listeners, transactions, etc)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (ISPN-9863) Testsuite leaks threads
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-9863?page=com.atlassian.jira.plugin.... ]
Dan Berindei reopened ISPN-9863:
--------------------------------
> Testsuite leaks threads
> -----------------------
>
> Key: ISPN-9863
> URL: https://issues.jboss.org/browse/ISPN-9863
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Server
> Affects Versions: 10.0.0.Alpha2, 9.4.5.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Labels: testsuite_stability
> Fix For: 10.0.0.Beta3
>
>
> Some hotrod-client tests do not stop their {{RemoteCacheManager}} instances. This was fine before ISPN-8619, but the Netty-based client starts event loop threads and we need to stop them.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months