[JBoss JIRA] (ISPN-10066) Server remote store is missing server-name attribute
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10066?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10066:
-----------------------------------
Status: Open (was: New)
> Server remote store is missing server-name attribute
> ----------------------------------------------------
>
> Key: ISPN-10066
> URL: https://issues.jboss.org/browse/ISPN-10066
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores, Server
> Affects Versions: 10.0.0.Beta2, 9.4.10.Final
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.Beta3, 9.4.11.Final
>
>
> When attempting to connect to a server with DIGEST authentication, the client needs to be able to specify the server name, otherwise the following error will happen "javax.security.sasl.SaslException: DIGEST-MD5: digest response format violation. Mismatched URI: hotrod/null; expecting one of: hotrod/myserver"
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (ISPN-10066) Server remote store is missing server-name attribute
by Tristan Tarrant (Jira)
Tristan Tarrant created ISPN-10066:
--------------------------------------
Summary: Server remote store is missing server-name attribute
Key: ISPN-10066
URL: https://issues.jboss.org/browse/ISPN-10066
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores, Server
Affects Versions: 9.4.10.Final, 10.0.0.Beta2
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 10.0.0.Beta3, 9.4.11.Final
When attempting to connect to a server with DIGEST authentication, the client needs to be able to specify the server name, otherwise the following error will happen "javax.security.sasl.SaslException: DIGEST-MD5: digest response format violation. Mismatched URI: hotrod/null; expecting one of: hotrod/myserver"
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (ISPN-10024) Long test killer doesn't work on Java 11
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10024?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10024:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 9.4.11.Final
Resolution: Done
> Long test killer doesn't work on Java 11
> ----------------------------------------
>
> Key: ISPN-10024
> URL: https://issues.jboss.org/browse/ISPN-10024
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 9.4.8.Final, 10.0.0.Beta2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Labels: testsuite_stability
> Fix For: 10.0.0.Beta3, 9.4.11.Final
>
>
> When a test takes > 5 minutes, {{RunningTestsRegistry}} takes a thread dump of the entire JVM and its child processes, then interrupts the test thread, and if the test still doesn't stop, it kills the test suite JVM.
> With OpenJDK 11, the path to {{jstack}} is wrong, the thread dump step fails, and the interrupt/kill steps are skipped.
> Note that on IBM JDK 8 {{jstack}} is missing completely, so we may want to write the thread stacktraces ourselves. The downside is that we would lose synchronization/lock/deadlock information.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (ISPN-10024) Long test killer doesn't work on Java 11
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-10024?page=com.atlassian.jira.plugin... ]
Dan Berindei updated ISPN-10024:
--------------------------------
Git Pull Request: https://github.com/infinispan/infinispan/pull/6765, https://github.com/infinispan/infinispan/pull/6783 (was: https://github.com/infinispan/infinispan/pull/6765)
> Long test killer doesn't work on Java 11
> ----------------------------------------
>
> Key: ISPN-10024
> URL: https://issues.jboss.org/browse/ISPN-10024
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 9.4.8.Final, 10.0.0.Beta2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Labels: testsuite_stability
> Fix For: 10.0.0.Beta3
>
>
> When a test takes > 5 minutes, {{RunningTestsRegistry}} takes a thread dump of the entire JVM and its child processes, then interrupts the test thread, and if the test still doesn't stop, it kills the test suite JVM.
> With OpenJDK 11, the path to {{jstack}} is wrong, the thread dump step fails, and the interrupt/kill steps are skipped.
> Note that on IBM JDK 8 {{jstack}} is missing completely, so we may want to write the thread stacktraces ourselves. The downside is that we would lose synchronization/lock/deadlock information.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months