[JBoss JIRA] (HRJS-83) Client listener failover
by Galder Zamarreño (Jira)
[ https://issues.jboss.org/browse/HRJS-83?page=com.atlassian.jira.plugin.sy... ]
Galder Zamarreño commented on HRJS-83:
--------------------------------------
Workaround:
The problem with errors like the one you saw in the log about socket error, for normal RPCs those are failed over, so they don't bubble up. So, the only workaround I can think of is for you to periodically check of the contents of client.getTopologyInfo.getMembers and if there's any change, delete any client listeners (ignoring errors) and re-register them.
> Client listener failover
> ------------------------
>
> Key: HRJS-83
> URL: https://issues.jboss.org/browse/HRJS-83
> Project: Infinispan Javascript client
> Issue Type: Enhancement
> Reporter: Galder Zamarreño
> Priority: Major
>
> If the node on which a client listener is registered goes down, the listener must fail over to a different node.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 7 months
[JBoss JIRA] (HRJS-83) Client listener failover
by Galder Zamarreño (Jira)
Galder Zamarreño created HRJS-83:
------------------------------------
Summary: Client listener failover
Key: HRJS-83
URL: https://issues.jboss.org/browse/HRJS-83
Project: Infinispan Javascript client
Issue Type: Enhancement
Reporter: Galder Zamarreño
If the node on which a client listener is registered goes down, the listener must fail over to a different node.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 7 months
[JBoss JIRA] (ISPN-10162) Improve Retrievability for Sping Boot Starter Docs
by Donald Naro (Jira)
Donald Naro created ISPN-10162:
----------------------------------
Summary: Improve Retrievability for Sping Boot Starter Docs
Key: ISPN-10162
URL: https://issues.jboss.org/browse/ISPN-10162
Project: Infinispan
Issue Type: Enhancement
Components: Documentation-Core
Affects Versions: 10.0.0.Beta4, 9.4.13.Final
Reporter: Donald Naro
Assignee: Donald Naro
Make Data Grid Spring Boot Starter docs standalone to improve retrievability.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 7 months
[JBoss JIRA] (ISPN-10106) Fix thread leaks in JUnit modules
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-10106?page=com.atlassian.jira.plugin... ]
Dan Berindei updated ISPN-10106:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/6857, https://github.com/infinispan/infinispan/pull/6858, https://github.com/infinispan/infinispan/pull/6875, https://github.com/infinispan/infinispan/pull/6877 (was: https://github.com/infinispan/infinispan/pull/6857, https://github.com/infinispan/infinispan/pull/6858)
> Fix thread leaks in JUnit modules
> ---------------------------------
>
> Key: ISPN-10106
> URL: https://issues.jboss.org/browse/ISPN-10106
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Server
> Affects Versions: 9.4.11.Final, 10.0.0.Beta3
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Labels: testsuite_stability
> Fix For: 10.0.0.Beta4
>
>
> ISPN-9863 added a thread leak checker, but even with all the recent improvements, leaks in JUnit modules are not reported as test failures.
> Because Surefire ignores failures in JUnit configuration methods and listeners, the only sign of a leak is an error message in the console output:
> {noformat}
> [2019-03-28T17:33:54.119Z] org.apache.maven.surefire.booter.SurefireBooterForkException: ExecutionException There was an error in the forked process
> [2019-03-28T17:33:54.119Z] Test mechanism :: Leaked threads:
> [2019-03-28T17:33:54.119Z] {pool-7-thread-1: possible sources [UNKNOWN]},
> [2019-03-28T17:33:54.119Z] {management-client-thread 1-1: possible sources [UNKNOWN]}
> {noformat}
> And in a dump file:
> {noformat}
> [2019-03-28T18:23:39.501Z] ./integrationtests/security-it/target/failsafe-reports/2019-03-28T17-28-10_213-jvmRun1.dump
> [2019-03-28T18:23:39.501Z] # Created at 2019-03-28T17:29:25.623
> [2019-03-28T18:23:39.501Z] org.apache.maven.surefire.testset.TestSetFailedException: Test mechanism :: Leaked threads:
> [2019-03-28T18:23:39.501Z] {pool-7-thread-1: possible sources [UNKNOWN]},
> [2019-03-28T18:23:39.501Z] {management-client-thread 1-1: possible sources [UNKNOWN]}
> [2019-03-28T18:23:39.501Z] at org.apache.maven.surefire.common.junit4.JUnit4RunListener.rethrowAnyTestMechanismFailures(JUnit4RunListener.java:223)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 7 months
[JBoss JIRA] (ISPN-10161) ThreadLeakChecker is blocking PolarionJUnitXMLReporter to generate the reports
by Diego Lovison (Jira)
[ https://issues.jboss.org/browse/ISPN-10161?page=com.atlassian.jira.plugin... ]
Diego Lovison updated ISPN-10161:
---------------------------------
Description:
When we have Leaked threads we are throwing a new RuntimeException that is preventing the next listener to be running.
>From `master` execute `rm -rf hibernate/cache-v51/target/surefire-reports/ && rm -rf hibernate/cache-v53/target/surefire-reports/ && mvn verify -pl hibernate/cache-v51,hibernate/cache-v53 -Dtest=MultiTenancyTest -fae`
After that, check the hibernate/cache-v53/target/surefire-reports/ folder, you will see no reports there.
was:
When we have Leaked threads we are throwing a new RuntimeException that is preventing the next listener to be running.
>From `master` execute `rm -rf hibernate/cache-v51/target/surefire-reports/ && rm -rf hibernate/cache-v53/target/surefire-reports/ && mvn verify -pl hibernate/cache-v51,hibernate/cache-v53 -Dtest=MultiTenancyTest -fae`
After that, check the hibernate/cache-v53/target/surefire-reports/ folder, you see no reports there.
> ThreadLeakChecker is blocking PolarionJUnitXMLReporter to generate the reports
> ------------------------------------------------------------------------------
>
> Key: ISPN-10161
> URL: https://issues.jboss.org/browse/ISPN-10161
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 9.4.12.Final, 10.0.0.Final
> Reporter: Diego Lovison
> Assignee: Diego Lovison
> Priority: Critical
>
> When we have Leaked threads we are throwing a new RuntimeException that is preventing the next listener to be running.
> From `master` execute `rm -rf hibernate/cache-v51/target/surefire-reports/ && rm -rf hibernate/cache-v53/target/surefire-reports/ && mvn verify -pl hibernate/cache-v51,hibernate/cache-v53 -Dtest=MultiTenancyTest -fae`
> After that, check the hibernate/cache-v53/target/surefire-reports/ folder, you will see no reports there.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 7 months
[JBoss JIRA] (ISPN-10161) ThreadLeakChecker is blocking PolarionJUnitXMLReporter to generate the reports
by Diego Lovison (Jira)
[ https://issues.jboss.org/browse/ISPN-10161?page=com.atlassian.jira.plugin... ]
Diego Lovison updated ISPN-10161:
---------------------------------
Status: Open (was: New)
> ThreadLeakChecker is blocking PolarionJUnitXMLReporter to generate the reports
> ------------------------------------------------------------------------------
>
> Key: ISPN-10161
> URL: https://issues.jboss.org/browse/ISPN-10161
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 9.4.12.Final, 10.0.0.Final
> Reporter: Diego Lovison
> Assignee: Diego Lovison
> Priority: Critical
>
> When we have Leaked threads we are throwing a new RuntimeException that is preventing the next listener to be running.
> From `master` execute `rm -rf hibernate/cache-v51/target/surefire-reports/ && rm -rf hibernate/cache-v53/target/surefire-reports/ && mvn verify -pl hibernate/cache-v51,hibernate/cache-v53 -Dtest=MultiTenancyTest -fae`
> After that, check the hibernate/cache-v53/target/surefire-reports/ folder, you see no reports there.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 7 months
[JBoss JIRA] (ISPN-10161) ThreadLeakChecker is blocking PolarionJUnitXMLReporter to generate the reports
by Diego Lovison (Jira)
[ https://issues.jboss.org/browse/ISPN-10161?page=com.atlassian.jira.plugin... ]
Diego Lovison reassigned ISPN-10161:
------------------------------------
Assignee: Diego Lovison
> ThreadLeakChecker is blocking PolarionJUnitXMLReporter to generate the reports
> ------------------------------------------------------------------------------
>
> Key: ISPN-10161
> URL: https://issues.jboss.org/browse/ISPN-10161
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 9.4.12.Final, 10.0.0.Final
> Reporter: Diego Lovison
> Assignee: Diego Lovison
> Priority: Critical
>
> When we have Leaked threads we are throwing a new RuntimeException that is preventing the next listener to be running.
> From `master` execute `rm -rf hibernate/cache-v51/target/surefire-reports/ && rm -rf hibernate/cache-v53/target/surefire-reports/ && mvn verify -pl hibernate/cache-v51,hibernate/cache-v53 -Dtest=MultiTenancyTest -fae`
> After that, check the hibernate/cache-v53/target/surefire-reports/ folder, you see no reports there.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 7 months