[JBoss JIRA] (ISPN-10154) RESTCertSecurityIT.testInvalidCertificateAccess fails with Java 11
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10154?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10154:
-----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/6870, https://github.com/infinispan/infinispan/pull/6869
> RESTCertSecurityIT.testInvalidCertificateAccess fails with Java 11
> ------------------------------------------------------------------
>
> Key: ISPN-10154
> URL: https://issues.jboss.org/browse/ISPN-10154
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Server
> Affects Versions: 9.4.12.Final, 10.0.0.Beta3
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.Beta4, 9.4.13.Final
>
>
> testInvalidCertificateAccess
> javax.net.ssl.SSLException: readHandshakeRecord at org.infinispan.server.test.security.rest.RESTCertSecurityIT.put(RESTCertSecurityIT.java:160) at org.infinispan.server.test.security.rest.RESTCertSecurityIT.testInvalidCertificateAccess(RESTCertSecurityIT.java:136) Caused by: java.net.SocketException: Broken pipe (Write failed) at org.infinispan.server.test.security.rest.RESTCertSecurityIT.put(RESTCertSecurityIT.java:160) at org.infinispan.server.test.security.rest.RESTCertSecurityIT.testInvalidCertificateAccess(RESTCertSecurityIT.java:136)
> Java 8 reports SSLHandshakeException for this so the test fails
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 11 months
[JBoss JIRA] (ISPN-10154) RESTCertSecurityIT.testInvalidCertificateAccess fails with Java 11
by Tristan Tarrant (Jira)
Tristan Tarrant created ISPN-10154:
--------------------------------------
Summary: RESTCertSecurityIT.testInvalidCertificateAccess fails with Java 11
Key: ISPN-10154
URL: https://issues.jboss.org/browse/ISPN-10154
Project: Infinispan
Issue Type: Bug
Components: Test Suite - Server
Affects Versions: 10.0.0.Beta3, 9.4.12.Final
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 10.0.0.Beta4, 9.4.13.Final
testInvalidCertificateAccess
javax.net.ssl.SSLException: readHandshakeRecord at org.infinispan.server.test.security.rest.RESTCertSecurityIT.put(RESTCertSecurityIT.java:160) at org.infinispan.server.test.security.rest.RESTCertSecurityIT.testInvalidCertificateAccess(RESTCertSecurityIT.java:136) Caused by: java.net.SocketException: Broken pipe (Write failed) at org.infinispan.server.test.security.rest.RESTCertSecurityIT.put(RESTCertSecurityIT.java:160) at org.infinispan.server.test.security.rest.RESTCertSecurityIT.testInvalidCertificateAccess(RESTCertSecurityIT.java:136)
Java 8 reports SSLHandshakeException for this so the test fails
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 11 months
[JBoss JIRA] (ISPN-10145) Lock timeout errors do not show which cache they affect
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10145?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10145:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Lock timeout errors do not show which cache they affect
> -------------------------------------------------------
>
> Key: ISPN-10145
> URL: https://issues.jboss.org/browse/ISPN-10145
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 9.4.12.Final, 10.0.0.Beta3
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Priority: Major
> Labels: rhdemo-2019
> Fix For: 10.0.0.Final, 9.4.13.Final
>
>
> e.g.
> {code}
> [0m[31m14:56:40,478 ERROR [org.infinispan.interceptors.impl.InvocationContextInterceptor] (async-thread--p6-t24) ISPN000136: Error executing command PutKeyValueCommand, writing keys [WrappedByteArray{bytes=[B0x6C6561646572626F..[11], hashCode=-1576989476}]: org.infinispan.util.concurrent.TimeoutException: ISPN000299: Unable to acquire lock after 10 seconds for key WrappedByteArray{bytes=[B0x6C6561646572626F..[11], hashCode=-1576989476} and requestor CommandInvocation:datagrid-service-0:4720. Lock is held by CommandInvocation:datagrid-service-0:4712
> at org.infinispan.util.concurrent.locks.impl.DefaultLockManager$KeyAwareExtendedLockPromise.get(DefaultLockManager.java:288) [infinispan-core-9.4.11-SNAPSHOT.jar:9.4.11-SNAPSHOT]
> at org.infinispan.util.concurrent.locks.impl.DefaultLockManager$KeyAwareExtendedLockPromise.get(DefaultLockManager.java:218) [infinispan-core-9.4.11-SNAPSHOT.jar:9.4.11-SNAPSHOT]
> at org.infinispan.util.concurrent.locks.impl.InfinispanLock$LockPlaceHolder.checkState(InfinispanLock.java:436) [infinispan-core-9.4.11-SNAPSHOT.jar:9.4.11-SNAPSHOT]
> at org.infinispan.util.concurrent.locks.impl.InfinispanLock$LockPlaceHolder.lambda$toInvocationStage$3(InfinispanLock.java:412) [infinispan-core-9.4.11-SNAPSHOT.jar:9.4.11-SNAPSHOT]
> at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:602) [rt.jar:1.8.0_201]
> at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577) [rt.jar:1.8.0_201]
> at java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:442) [rt.jar:1.8.0_201]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_201]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_201]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_201]
> {code}
> Cache name is only added to NDC when trace is enabled, so the alternative would be for the error message to show it.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 11 months
[JBoss JIRA] (ISPN-10153) Log messages should use data type to present key/value info
by Galder Zamarreño (Jira)
Galder Zamarreño created ISPN-10153:
---------------------------------------
Summary: Log messages should use data type to present key/value info
Key: ISPN-10153
URL: https://issues.jboss.org/browse/ISPN-10153
Project: Infinispan
Issue Type: Enhancement
Reporter: Galder Zamarreño
A Node.js client was putting load on a key and the server was showing the following in the log:
{code}
[0m[31m14:43:08,342 ERROR [org.infinispan.interceptors.impl.InvocationContextInterceptor] (async-thread--p6-t18) ISPN000136: Error executing command PutKeyValueCommand, writing keys [WrappedByteArray{bytes=[B0x6C6561646572626F..[11], hashCode=-1576989476}]: org.infinispan.util.concurrent.TimeoutException: ISPN000299: Unable to acquire lock after 10 seconds for key WrappedByteArray{bytes=[B0x6C6561646572626F..[11], hashCode=-1576989476} and requestor CommandInvocation:datagrid-service-2:26030. Lock is held by CommandInvocation:datagrid-service-2:26029
at org.infinispan.util.concurrent.locks.impl.DefaultLockManager$KeyAwareExtendedLockPromise.get(DefaultLockManager.java:288) [infinispan-core-9.4.11-SNAPSHOT.jar:9.4.11-SNAPSHOT]
at org.infinispan.util.concurrent.locks.impl.DefaultLockManager$KeyAwareExtendedLockPromise.get(DefaultLockManager.java:218) [infinispan-core-9.4.11-SNAPSHOT.jar:9.4.11-SNAPSHOT]
at org.infinispan.util.concurrent.locks.impl.InfinispanLock$LockPlaceHolder.checkState(InfinispanLock.java:436) [infinispan-core-9.4.11-SNAPSHOT.jar:9.4.11-SNAPSHOT]
at org.infinispan.util.concurrent.locks.impl.InfinispanLock$LockPlaceHolder.lambda$toInvocationStage$3(InfinispanLock.java:412) [infinispan-core-9.4.11-SNAPSHOT.jar:9.4.11-SNAPSHOT]
at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:602) [rt.jar:1.8.0_191]
at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577) [rt.jar:1.8.0_191]
at java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:442) [rt.jar:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_191]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_191]
at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_191]
{code}
The server now knows the data types, so it could figure out that this key of "text/plain" and could use the info to present the key in its text format as opposed to binary. This would help with diagnose/debugging.
By trying out different keys I figured the key here was "leaderboard"
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 11 months
[JBoss JIRA] (ISPN-10145) Lock timeout errors do not show which cache they affect
by Galder Zamarreño (Jira)
[ https://issues.jboss.org/browse/ISPN-10145?page=com.atlassian.jira.plugin... ]
Galder Zamarreño updated ISPN-10145:
------------------------------------
Labels: rhdemo-2019 (was: )
> Lock timeout errors do not show which cache they affect
> -------------------------------------------------------
>
> Key: ISPN-10145
> URL: https://issues.jboss.org/browse/ISPN-10145
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 9.4.12.Final, 10.0.0.Beta3
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Priority: Major
> Labels: rhdemo-2019
> Fix For: 10.0.0.Final, 9.4.13.Final
>
>
> e.g.
> {code}
> [0m[31m14:56:40,478 ERROR [org.infinispan.interceptors.impl.InvocationContextInterceptor] (async-thread--p6-t24) ISPN000136: Error executing command PutKeyValueCommand, writing keys [WrappedByteArray{bytes=[B0x6C6561646572626F..[11], hashCode=-1576989476}]: org.infinispan.util.concurrent.TimeoutException: ISPN000299: Unable to acquire lock after 10 seconds for key WrappedByteArray{bytes=[B0x6C6561646572626F..[11], hashCode=-1576989476} and requestor CommandInvocation:datagrid-service-0:4720. Lock is held by CommandInvocation:datagrid-service-0:4712
> at org.infinispan.util.concurrent.locks.impl.DefaultLockManager$KeyAwareExtendedLockPromise.get(DefaultLockManager.java:288) [infinispan-core-9.4.11-SNAPSHOT.jar:9.4.11-SNAPSHOT]
> at org.infinispan.util.concurrent.locks.impl.DefaultLockManager$KeyAwareExtendedLockPromise.get(DefaultLockManager.java:218) [infinispan-core-9.4.11-SNAPSHOT.jar:9.4.11-SNAPSHOT]
> at org.infinispan.util.concurrent.locks.impl.InfinispanLock$LockPlaceHolder.checkState(InfinispanLock.java:436) [infinispan-core-9.4.11-SNAPSHOT.jar:9.4.11-SNAPSHOT]
> at org.infinispan.util.concurrent.locks.impl.InfinispanLock$LockPlaceHolder.lambda$toInvocationStage$3(InfinispanLock.java:412) [infinispan-core-9.4.11-SNAPSHOT.jar:9.4.11-SNAPSHOT]
> at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:602) [rt.jar:1.8.0_201]
> at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577) [rt.jar:1.8.0_201]
> at java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:442) [rt.jar:1.8.0_201]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_201]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_201]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_201]
> {code}
> Cache name is only added to NDC when trace is enabled, so the alternative would be for the error message to show it.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 11 months
[JBoss JIRA] (ISPN-10151) REST counter ops
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10151?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10151:
-----------------------------------
Description:
* GET /v2/counters/{counterName} Get counter value
* POST /v2/counters/{counterName} Increment/apply delta to counter
* DELETE /v2/counters/{counterName} Reset counter to initial value
> REST counter ops
> ----------------
>
> Key: ISPN-10151
> URL: https://issues.jboss.org/browse/ISPN-10151
> Project: Infinispan
> Issue Type: Sub-task
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
>
> * GET /v2/counters/{counterName} Get counter value
> * POST /v2/counters/{counterName} Increment/apply delta to counter
> * DELETE /v2/counters/{counterName} Reset counter to initial value
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 11 months
[JBoss JIRA] (ISPN-10149) Enable checkstyle plugin during the verify maven phase
by Diego Lovison (Jira)
[ https://issues.jboss.org/browse/ISPN-10149?page=com.atlassian.jira.plugin... ]
Diego Lovison updated ISPN-10149:
---------------------------------
Summary: Enable checkstyle plugin during the verify maven phase (was: Keep only one checkstyle plugin configuration)
> Enable checkstyle plugin during the verify maven phase
> ------------------------------------------------------
>
> Key: ISPN-10149
> URL: https://issues.jboss.org/browse/ISPN-10149
> Project: Infinispan
> Issue Type: Bug
> Reporter: Diego Lovison
> Assignee: Diego Lovison
> Priority: Major
>
> Today the checkstyle configuration is duplicated across multiple projects
> The docs say
> {noformat}
> ===== Checking coding style
> If you have written any new code, it is highly recommended to validate formatting before submitting a Pull Request.
> This might be done by invoking:
> $ mvn checktyle:check
> {noformat}
> but it is failing
> {noformat}
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 7.296 s
> [INFO] Finished at: 2019-04-25T19:55:17-03:00
> [INFO] ------------------------------------------------------------------------
> [ERROR] No plugin found for prefix 'checktyle' in the current project and in the plugin groups [com.oracle.weblogic, org.jenkins-ci.tools, org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/Users/dlovison/.m2/repository), -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/NoPluginFoundForPrefixEx...
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
4 years, 11 months