[JBoss JIRA] (ISPN-11044) Client timeout Exception should log the connection additional to the key
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-11044?page=com.atlassian.jira.plugi... ]
Will Burns updated ISPN-11044:
------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 10.1.0.CR1
Resolution: Done
> Client timeout Exception should log the connection additional to the key
> ------------------------------------------------------------------------
>
> Key: ISPN-11044
> URL: https://issues.redhat.com/browse/ISPN-11044
> Project: Infinispan
> Issue Type: Enhancement
> Components: Hot Rod
> Affects Versions: 10.1.0.Beta1
> Environment: HotRod client
> Reporter: Wolf-Dieter Fink
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.1.0.CR1
>
>
> In case of communication timeout with the server the client should log the connection details as the key will not give enough to analyse the issue.
> It will be hard to know which connection/server is affected as the distribution will be based on the key's consistent hash algorithm and a user can not determine which server connection is used.
> If that case the ERROR message should include the connection information as host-name or IP address AND port (to be unique for multiple servers with the same IP) to track that.
> The access log can't be used in this case as there is no message because the server is not reached or already affected/blocked.
> ~~~
> ERROR [stderr] (pool-12-thread-3) org.infinispan.client.hotrod.exceptions.TransportException:: java.net.SocketTimeoutException: GetOperation{TestCache, key=[B0x800127656A6B2F6C..[103], flags=0} timed out after 60000 ms
> ERROR [stderr] (pool-12-thread-3) at org.infinispan.client.hotrod.impl.Util.rewrap(Util.java:54)
> ERROR [stderr] (pool-12-thread-3) at org.infinispan.client.hotrod.impl.Util.await(Util.java:27)
> ERROR [stderr] (pool-12-thread-3) at org.infinispan.client.hotrod.impl.RemoteCacheImpl.get(RemoteCacheImpl.java:418)
> ...
> ERROR [stderr] (pool-12-thread-3) Caused by: java.net.SocketTimeoutException: GetOperation{TestCache, key=[B0x800127656A6B2F6C..[103], flags=0} timed out after 60000 ms
> ERROR [stderr] (pool-12-thread-3) at org.infinispan.client.hotrod.impl.operations.HotRodOperation.run(HotRodOperation.java:172)
> ERROR [stderr] (pool-12-thread-3) at io.netty.util.concurrent.PromiseTask$RunnableAdapter.call(PromiseTask.java:38)
> ERROR [stderr] (pool-12-thread-3) at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:127)
> ERROR [stderr] (pool-12-thread-3) at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)
> ERROR [stderr] (pool-12-thread-3) at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:404)
> ERROR [stderr] (pool-12-thread-3) at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:322)
> ERROR [stderr] (pool-12-thread-3) at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:884)
> ERROR [stderr] (pool-12-thread-3) ... 3 more
> ~~~
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-11044) Client timeout Exception should log the connection additional to the key
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-11044?page=com.atlassian.jira.plugi... ]
Will Burns updated ISPN-11044:
------------------------------
Fix Version/s: 9.4.17.Final
> Client timeout Exception should log the connection additional to the key
> ------------------------------------------------------------------------
>
> Key: ISPN-11044
> URL: https://issues.redhat.com/browse/ISPN-11044
> Project: Infinispan
> Issue Type: Enhancement
> Components: Hot Rod
> Affects Versions: 10.1.0.Beta1
> Environment: HotRod client
> Reporter: Wolf-Dieter Fink
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 9.4.17.Final, 10.1.0.CR1
>
>
> In case of communication timeout with the server the client should log the connection details as the key will not give enough to analyse the issue.
> It will be hard to know which connection/server is affected as the distribution will be based on the key's consistent hash algorithm and a user can not determine which server connection is used.
> If that case the ERROR message should include the connection information as host-name or IP address AND port (to be unique for multiple servers with the same IP) to track that.
> The access log can't be used in this case as there is no message because the server is not reached or already affected/blocked.
> ~~~
> ERROR [stderr] (pool-12-thread-3) org.infinispan.client.hotrod.exceptions.TransportException:: java.net.SocketTimeoutException: GetOperation{TestCache, key=[B0x800127656A6B2F6C..[103], flags=0} timed out after 60000 ms
> ERROR [stderr] (pool-12-thread-3) at org.infinispan.client.hotrod.impl.Util.rewrap(Util.java:54)
> ERROR [stderr] (pool-12-thread-3) at org.infinispan.client.hotrod.impl.Util.await(Util.java:27)
> ERROR [stderr] (pool-12-thread-3) at org.infinispan.client.hotrod.impl.RemoteCacheImpl.get(RemoteCacheImpl.java:418)
> ...
> ERROR [stderr] (pool-12-thread-3) Caused by: java.net.SocketTimeoutException: GetOperation{TestCache, key=[B0x800127656A6B2F6C..[103], flags=0} timed out after 60000 ms
> ERROR [stderr] (pool-12-thread-3) at org.infinispan.client.hotrod.impl.operations.HotRodOperation.run(HotRodOperation.java:172)
> ERROR [stderr] (pool-12-thread-3) at io.netty.util.concurrent.PromiseTask$RunnableAdapter.call(PromiseTask.java:38)
> ERROR [stderr] (pool-12-thread-3) at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:127)
> ERROR [stderr] (pool-12-thread-3) at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)
> ERROR [stderr] (pool-12-thread-3) at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:404)
> ERROR [stderr] (pool-12-thread-3) at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:322)
> ERROR [stderr] (pool-12-thread-3) at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:884)
> ERROR [stderr] (pool-12-thread-3) ... 3 more
> ~~~
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-11044) Client timeout Exception should log the connection additional to the key
by Wolf-Dieter Fink (Jira)
[ https://issues.redhat.com/browse/ISPN-11044?page=com.atlassian.jira.plugi... ]
Wolf-Dieter Fink updated ISPN-11044:
------------------------------------
Security: (was: Red Hat Internal)
> Client timeout Exception should log the connection additional to the key
> ------------------------------------------------------------------------
>
> Key: ISPN-11044
> URL: https://issues.redhat.com/browse/ISPN-11044
> Project: Infinispan
> Issue Type: Enhancement
> Components: Hot Rod
> Affects Versions: 10.1.0.Beta1
> Environment: HotRod client
> Reporter: Wolf-Dieter Fink
> Assignee: Tristan Tarrant
> Priority: Major
>
> In case of communication timeout with the server the client should log the connection details as the key will not give enough to analyse the issue.
> It will be hard to know which connection/server is affected as the distribution will be based on the key's consistent hash algorithm and a user can not determine which server connection is used.
> If that case the ERROR message should include the connection information as host-name or IP address AND port (to be unique for multiple servers with the same IP) to track that.
> The access log can't be used in this case as there is no message because the server is not reached or already affected/blocked.
> ~~~
> ERROR [stderr] (pool-12-thread-3) org.infinispan.client.hotrod.exceptions.TransportException:: java.net.SocketTimeoutException: GetOperation{TestCache, key=[B0x800127656A6B2F6C..[103], flags=0} timed out after 60000 ms
> ERROR [stderr] (pool-12-thread-3) at org.infinispan.client.hotrod.impl.Util.rewrap(Util.java:54)
> ERROR [stderr] (pool-12-thread-3) at org.infinispan.client.hotrod.impl.Util.await(Util.java:27)
> ERROR [stderr] (pool-12-thread-3) at org.infinispan.client.hotrod.impl.RemoteCacheImpl.get(RemoteCacheImpl.java:418)
> ...
> ERROR [stderr] (pool-12-thread-3) Caused by: java.net.SocketTimeoutException: GetOperation{TestCache, key=[B0x800127656A6B2F6C..[103], flags=0} timed out after 60000 ms
> ERROR [stderr] (pool-12-thread-3) at org.infinispan.client.hotrod.impl.operations.HotRodOperation.run(HotRodOperation.java:172)
> ERROR [stderr] (pool-12-thread-3) at io.netty.util.concurrent.PromiseTask$RunnableAdapter.call(PromiseTask.java:38)
> ERROR [stderr] (pool-12-thread-3) at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:127)
> ERROR [stderr] (pool-12-thread-3) at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)
> ERROR [stderr] (pool-12-thread-3) at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:404)
> ERROR [stderr] (pool-12-thread-3) at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:322)
> ERROR [stderr] (pool-12-thread-3) at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:884)
> ERROR [stderr] (pool-12-thread-3) ... 3 more
> ~~~
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10908) Client timeout Exception should log the connection additional to the key
by Wolf-Dieter Fink (Jira)
[ https://issues.redhat.com/browse/ISPN-10908?page=com.atlassian.jira.plugi... ]
Wolf-Dieter Fink closed ISPN-10908.
-----------------------------------
Resolution: Duplicate Issue
> Client timeout Exception should log the connection additional to the key
> ------------------------------------------------------------------------
>
> Key: ISPN-10908
> URL: https://issues.redhat.com/browse/ISPN-10908
> Project: Infinispan
> Issue Type: Enhancement
> Components: Hot Rod
> Affects Versions: 10.0.0.Final
> Environment: HotRod client
> Reporter: Wolf-Dieter Fink
> Assignee: Tristan Tarrant
> Priority: Major
>
> In case of communication timeout with the server the client should log the connection details as the key will not give enough to analyse the issue.
> ~~~
> ERROR [stderr] (pool-12-thread-3) org.infinispan.client.hotrod.exceptions.TransportException:: java.net.SocketTimeoutException: GetOperation{TestCache, key=[B0x800127656A6B2F6C..[103], flags=0} timed out after 60000 ms
> ERROR [stderr] (pool-12-thread-3) at org.infinispan.client.hotrod.impl.Util.rewrap(Util.java:54)
> ERROR [stderr] (pool-12-thread-3) at org.infinispan.client.hotrod.impl.Util.await(Util.java:27)
> ERROR [stderr] (pool-12-thread-3) at org.infinispan.client.hotrod.impl.RemoteCacheImpl.get(RemoteCacheImpl.java:418)
> ...
> ERROR [stderr] (pool-12-thread-3) Caused by: java.net.SocketTimeoutException: GetOperation{TestCache, key=[B0x800127656A6B2F6C..[103], flags=0} timed out after 60000 ms
> ERROR [stderr] (pool-12-thread-3) at org.infinispan.client.hotrod.impl.operations.HotRodOperation.run(HotRodOperation.java:172)
> ERROR [stderr] (pool-12-thread-3) at io.netty.util.concurrent.PromiseTask$RunnableAdapter.call(PromiseTask.java:38)
> ERROR [stderr] (pool-12-thread-3) at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:127)
> ERROR [stderr] (pool-12-thread-3) at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)
> ERROR [stderr] (pool-12-thread-3) at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:404)
> ERROR [stderr] (pool-12-thread-3) at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:322)
> ERROR [stderr] (pool-12-thread-3) at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:884)
> ERROR [stderr] (pool-12-thread-3) ... 3 more
> ~~~
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10836) Docs Productization: Marshalling and Protostream
by Donald Naro (Jira)
[ https://issues.redhat.com/browse/ISPN-10836?page=com.atlassian.jira.plugi... ]
Donald Naro edited comment on ISPN-10836 at 12/6/19 7:21 AM:
-------------------------------------------------------------
[~dnaro27] need to clarify if the white list is per cache managers thing or per marshaller
https://github.com/infinispan/infinispan/blob/master/documentation/src/ma...
and
https://github.com/infinispan/infinispan/blob/master/documentation/src/ma...
was (Author: dnaro27):
[~dnaro27] need to clarify if the white list is per cache managers thing or per marshaller
> Docs Productization: Marshalling and Protostream
> ------------------------------------------------
>
> Key: ISPN-10836
> URL: https://issues.redhat.com/browse/ISPN-10836
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation
> Reporter: Donald Naro
> Assignee: Donald Naro
> Priority: Major
>
> Productize content for marshalling and protostream.
> Modularize existing content.
> Show consistent examples for usage (i.e. should match CLI example).
> Identify additional changes and work to develop customer content.
> Review Server Guide marshalling section (8. Adding Custom Marshaller Bridges) and make sure this is relevant and up to date for DG 8
> From Ryan:
> - protostream and marshalling:
> The important things to document are:
> Jboss marshalling no longer present by default, infinispan-jboss-marshalling jar must be added to the classpath of the client/server if required.
> - Externalizers ignored unless this is present
> Protostream is the default marshaller for user types. Need to document the process of generating marshallers using pojos, and configuring the serialization context.
> - Best practices on how to evolve schemas to ensure backwards-compatibility
> Possible to configure a custom user marshaller in embedded mode, for example if the user wants to use Java Serialization but not jboss marshalling.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months
[JBoss JIRA] (ISPN-10836) Docs Productization: Marshalling and Protostream
by Donald Naro (Jira)
[ https://issues.redhat.com/browse/ISPN-10836?page=com.atlassian.jira.plugi... ]
Donald Naro commented on ISPN-10836:
------------------------------------
[~dnaro27] need to clarify if the white list is per cache managers thing or per marshaller
> Docs Productization: Marshalling and Protostream
> ------------------------------------------------
>
> Key: ISPN-10836
> URL: https://issues.redhat.com/browse/ISPN-10836
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation
> Reporter: Donald Naro
> Assignee: Donald Naro
> Priority: Major
>
> Productize content for marshalling and protostream.
> Modularize existing content.
> Show consistent examples for usage (i.e. should match CLI example).
> Identify additional changes and work to develop customer content.
> Review Server Guide marshalling section (8. Adding Custom Marshaller Bridges) and make sure this is relevant and up to date for DG 8
> From Ryan:
> - protostream and marshalling:
> The important things to document are:
> Jboss marshalling no longer present by default, infinispan-jboss-marshalling jar must be added to the classpath of the client/server if required.
> - Externalizers ignored unless this is present
> Protostream is the default marshaller for user types. Need to document the process of generating marshallers using pojos, and configuring the serialization context.
> - Best practices on how to evolve schemas to ensure backwards-compatibility
> Possible to configure a custom user marshaller in embedded mode, for example if the user wants to use Java Serialization but not jboss marshalling.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 4 months