[infinispan-issues] [JBoss JIRA] Commented: (ISPN-1119) HotRod client should only log ERROR when it cannot failover

Galder Zamarreño (JIRA) jira-events at lists.jboss.org
Tue May 17 11:22:00 EDT 2011


    [ https://issues.jboss.org/browse/ISPN-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602628#comment-12602628 ] 

Galder Zamarreño commented on ISPN-1119:
----------------------------------------

Also, seems like errors are being logged twice by the AbstractProtocolDecoder and InvocationContextInterceptor

{code}[JBoss] 07:46:01,502 ERROR [InvocationContextInterceptor] (MemcachedServerWorker-1-47) Execution error: 
[JBoss] java.util.concurrent.ExecutionException: org.infinispan.remoting.transport.jgroups.SuspectException: Suspected member: perf19-47000
[JBoss] 	at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
--
[JBoss] 07:46:01,511 ERROR [AbstractProtocolDecoder$] (MemcachedServerWorker-1-47) Exception reported
[JBoss] org.infinispan.server.hotrod.HotRodException: org.infinispan.CacheException: java.util.concurrent.ExecutionException: org.infinispan.remoting.transport.jgroups.SuspectException: Suspected member: perf19-47000
[JBoss] 	at org.infinispan.server.hotrod.HotRodDecoder.createServerException(HotRodDecoder.scala:185){code}

Remove the log call from APD and let the most higher up call log the error.

> HotRod client should only log ERROR when it cannot failover
> -----------------------------------------------------------
>
>                 Key: ISPN-1119
>                 URL: https://issues.jboss.org/browse/ISPN-1119
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Cache Server
>            Reporter: Galder Zamarreño
>            Assignee: Galder Zamarreño
>              Labels: hotrod, java_hotrod_client
>             Fix For: 4.2.2.BETA1, 5.0.0.CR3
>
>
> In the Hot Rod client, if an error occurs connecting to a server, an ERROR is logged
> 2011-05-17 07:48:42,000 312441 ERROR [org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport] (Runner - 0:) Could not connect to server: perf19/10.16.90.56:11222
> However, this is not necessarily an ERROR unless you've run out of nodes and you cannot failover. So this should be a WARN and only log ERROR if you can't
> failover any more

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       



More information about the infinispan-issues mailing list