[
https://issues.jboss.org/browse/ISPN-3454?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on ISPN-3454:
----------------------------------------
This is a side effect of ISPN-2737, where we introduced RemoteException in order to report
application-level exceptions (i.e. lock timeout). What's happening here is that it
seems that on occasion, [SuspectException is treated as a
RemoteException|https://gist.github.com/galderz/bd1a71a06fa24efa7792], and others it just
bubbles up as [
SuspectException|https://gist.github.com/galderz/a121b1727a7f4ac1b78c]. The
bug here is that SuspectExceptions should not be treated as RemoteException.
RemoteException instances on the client should be reported by to the client, as it happens
here, since they are application-level errors.
Hot Rod client doesn't retry operation on RemoteException
---------------------------------------------------------
Key: ISPN-3454
URL:
https://issues.jboss.org/browse/ISPN-3454
Project: Infinispan
Issue Type: Bug
Affects Versions: 6.0.0.Alpha3
Reporter: Michal Linhard
Assignee: Galder Zamarreño
Priority: Critical
Labels: 620
Fix For: 6.0.0.CR2, 6.0.0.Final
This is a client-side problem.
In a resilience test with 4 nodes where 1 is killed, I'm getting a lot of these:
{code}
08:30:55,198 ERROR [org.jboss.smartfrog.jdg.loaddriver.DriverThread] (DriverThread-369)
Error doing: PUT key399869 to node node04, took 493 ms
org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for message
id[821188] returned server error (status=0x85): org.infinispan.remoting.RemoteException:
ISPN000217: Received exception from node01/default, see cause for remote stack trace
at
org.infinispan.client.hotrod.impl.protocol.Codec10.checkForErrorsInResponseStatus(Codec10.java:143)
at org.infinispan.client.hotrod.impl.protocol.Codec10.readHeader(Codec10.java:99)
at
org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:56)
at
org.infinispan.client.hotrod.impl.operations.AbstractKeyValueOperation.sendPutOperation(AbstractKeyValueOperation.java:50)
at
org.infinispan.client.hotrod.impl.operations.PutOperation.executeOperation(PutOperation.java:30)
at
org.infinispan.client.hotrod.impl.operations.PutOperation.executeOperation(PutOperation.java:19)
at
org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:46)
at org.infinispan.client.hotrod.impl.RemoteCacheImpl.put(RemoteCacheImpl.java:209)
at org.infinispan.client.hotrod.impl.RemoteCacheSupport.put(RemoteCacheSupport.java:79)
at
org.jboss.qa.jdg.adapter.Infinispan60Adapter$HotRodRemoteCacheAdapter.put(Infinispan60Adapter.java:269)
at
org.jboss.smartfrog.jdg.loaddriver.DriverThreadImpl.makeRequest(DriverThreadImpl.java:265)
at org.jboss.smartfrog.jdg.loaddriver.DriverThreadImpl.run(DriverThreadImpl.java:378)
{code}
Isn't this a recoverable problem that shouldn't be left to user to handle ?
source:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/RESILIENCE...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira