Back to bug 1002957
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| mark yarborough | 2013-09-04 13:25:22 UTC | Target Release | --- | 6.2.0 |
| Tristan Tarrant | 2013-09-10 08:48:05 UTC | Status | NEW | ASSIGNED |
| mark yarborough | 2013-10-09 13:07:32 UTC | CC | myarboro | |
| Blocks | 1017190 | |||
| Mircea Markus | 2013-10-09 15:28:53 UTC | CC | mmarkus | |
| Red Hat Bugzilla | 2013-11-03 23:56:57 UTC | CC | gsheldon | |
| Doc Type | Bug Fix | Known Issue | ||
| Doc Type | Known Issue | Bug Fix | ||
| Michal Linhard | 2013-11-04 10:38:59 UTC | Doc Text | Cause: There are certain types of remote-side exceptions that the Java Hot Rod client won't recover from by retrying, even though it should be possible. This also happens when the org.infinispan.remoting.RemoteException is thrown in the server. Consequence: The HotRodClientException is thrown on the client side, the operation doesn't retry and the issue needs to be handled by the user code. Fix: This issue is still present. If the server side error is recoverable, the workaround is to retry the operation again from the user code. Result: |
|
| Tristan Tarrant | 2013-11-19 13:38:47 UTC | Doc Text | Cause: There are certain types of remote-side exceptions that the Java Hot Rod client won't recover from by retrying | There are certain types of remote-side exceptions that the Java Hot Rod client will not recover from by retrying |
| Doc Text | , even though it should be possible. This also happens when the org.infinispan.remoting.RemoteException is thrown in the server. Consequence: The HotRodClientException is thrown on the client side | , even though it should be possible. This also happens when the org.infinispan.remoting.RemoteException is thrown in the server. The HotRodClientException is thrown on the client side | ||
| Doc Text | , the operation doesn't retry and the issue needs to be handled by the user code. Fix: This issue is still present. If the server side error is recoverable, the workaround is to retry the operation again from the user code. Result: | , the operation does not retry and the issue needs to be handled by the user code. This issue persists. If the server-side error is recoverable, the workaround is to retry the operation again from the user code. | ||
| Doc Type | Bug Fix | Known Issue | ||
| Doc Text | There are certain types of remote-side exceptions that the Java Hot Rod client will not recover from by retrying | There are certain types of remote-side exceptions that the Java Hot Rod client will not recover from by retrying | ||
| Doc Text | , even though it should be possible. This also happens when the org.infinispan.remoting.RemoteException is thrown in the server. The HotRodClientException is thrown on the client side | , even though it should be possible. This also happens when the org.infinispan.remoting.RemoteException is thrown in the server. <para> </para> The HotRodClientException is thrown on the client side | ||
| Doc Text | , the operation does not retry and the issue needs to be handled by the user code. This issue persists. If the server-side error is recoverable, the workaround is to retry the operation again from the user code. | , the operation does not retry and the issue needs to be handled by the user code. <para> </para> This issue persists. If the server-side error is recoverable, the workaround is to retry the operation again from the user code. | ||
| Doc Text | There are certain types of remote-side exceptions that the Java Hot Rod client will not recover from by retrying | There are certain types of remote-side exceptions that the Java Hot Rod client will not recover from by retrying | ||
| Doc Text | , even though it should be possible. This also happens when the org.infinispan.remoting.RemoteException is thrown in the server. <para> </para> The HotRodClientException is thrown on the client side | , even though it should be possible. This also happens when the org.infinispan.remoting.RemoteException is thrown in the server. The HotRodClientException is thrown on the client side | ||
| Doc Text | , the operation does not retry and the issue needs to be handled by the user code. <para> </para> This issue persists. If the server-side error is recoverable, the workaround is to retry the operation again from the user code. | , the operation does not retry and the issue needs to be handled by the user code. </para> <para> This issue persists. If the server-side error is recoverable, the workaround is to retry the operation again from the user code. | ||
| Status | ASSIGNED | ON_QA | ||
| Target Milestone | --- | ER4 | ||
| Michal Linhard | 2013-11-20 12:35:21 UTC | Status | ON_QA | VERIFIED |
| John Skeoch | 2014-03-17 04:03:31 UTC | Doc Text | There are certain types of remote-side exceptions that the Java Hot Rod client will not recover from by retrying | There are certain types of remote-side exceptions that the Java Hot Rod client will not recover from by retrying |
| Doc Text | , even though it should be possible. This also happens when the org.infinispan.remoting.RemoteException is thrown in the server. The HotRodClientException is thrown on the client side | , even though it should be possible. This also happens when the org.infinispan.remoting.RemoteException is thrown in the server. The HotRodClientException is thrown on the client side | ||
| Doc Text | , the operation does not retry and the issue needs to be handled by the user code. </para> <para> This issue persists. If the server-side error is recoverable, the workaround is to retry the operation again from the user code. | , the operation does not retry and the issue needs to be handled by the user code. | ||
| CC | nobody | |||
| John Skeoch | 2014-03-17 04:04:21 UTC | QA Contact | mlinhard | nobody |
| John Skeoch | 2014-11-30 21:15:57 UTC | CC | mmarkus | sjacobs |
| PnT Account Manager | 2018-09-12 22:21:01 UTC | CC | gsheldon |
Back to bug 1002957