[
https://issues.jboss.org/browse/ISPN-1126?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-1126:
-----------------------------------
Description:
RetryOnFailureOperation is not logging exceptions that lead to a retry correctlty and this
is hiding a crucial exception to clarify JBPAPP-6113. So, here's the log:
{code}211988 TRACE [org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation]
(Runner - 0:) Exception encountered. Retry 4 out of 40{code}
So, what exception was encountered? No idea. Why? Log code is:
{code}log.trace(message, i, transportFactory.getTransportCount(), te);{code}
Which translates to talking to "void trace(Object message, Object... params);"
which won't print the stacktrace as cause.
Instead, the log code should be:
{code}log.trace(message, te, i, transportFactory.getTransportCount());{code}
So that it uses "void trace(Object message, Throwable t, Object... params);"
Verify master as well.
was:
RetryOnFailureOperation is not logging exceptions that lead to a retry correctlty and this
is hiding a crucial exception to clarify JBPAPP-6113. So, here's the log:
{code}tcpTransport.log:33670:2011-05-17 11:23:31,119 211988 TRACE
[org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation] (Runner - 0:)
Exception encountered. Retry 4 out of 40{code}
So, what exception was encountered? No idea. Why? Log code is:
{code}log.trace(message, i, transportFactory.getTransportCount(), te);{code}
Which translates to talking to "void trace(Object message, Object... params);"
which won't print the stacktrace as cause.
Instead, the log code should be:
{code}log.trace(message, te, i, transportFactory.getTransportCount());{code}
So that it uses "void trace(Object message, Throwable t, Object... params);"
Verify master as well.
Exception hidden on Hot Rod client
----------------------------------
Key: ISPN-1126
URL:
https://issues.jboss.org/browse/ISPN-1126
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Affects Versions: 4.2.1.FINAL
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 4.2.2.BETA1
RetryOnFailureOperation is not logging exceptions that lead to a retry correctlty and
this is hiding a crucial exception to clarify JBPAPP-6113. So, here's the log:
{code}211988 TRACE [org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation]
(Runner - 0:) Exception encountered. Retry 4 out of 40{code}
So, what exception was encountered? No idea. Why? Log code is:
{code}log.trace(message, i, transportFactory.getTransportCount(), te);{code}
Which translates to talking to "void trace(Object message, Object... params);"
which won't print the stacktrace as cause.
Instead, the log code should be:
{code}log.trace(message, te, i, transportFactory.getTransportCount());{code}
So that it uses "void trace(Object message, Throwable t, Object... params);"
Verify master as well.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira