[infinispan-issues] [JBoss JIRA] Commented: (ISPN-947) Java Hot Rod client exceptions should be more user friendly

[Galder Zamarreño (JIRA)]

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

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

Message id is not to be confused with opcode, so the opcode message will not be applied. The server error modification is indeed being improved to make it easier to map to the Hot Rod protocol.

> Java Hot Rod client exceptions should be more user friendly
> -----------------------------------------------------------
>
>                 Key: ISPN-947
>                 URL: https://issues.jboss.org/browse/ISPN-947
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Cache Server
>    Affects Versions: 4.2.0.Final, 4.2.1.CR3
>            Reporter: Galder Zamarreño
>            Assignee: Galder Zamarreño
>              Labels: hotrod, java_hotrod_client
>             Fix For: 4.2.1.FINAL
>
>
> Java Hot Rod client exceptions are not friendly:
> {code}WARNING: Error status received from the server: for message id 2
> Exception in thread "main" org.infinispan.client.hotrod.exceptions.HotRodClientException: id [2] code [133]{code}
> What is that suppose to mean to clients? The following is much more friendly:
> {code}WARNING: Error status received from the server: for message put response (opcode=0x02)
> Exception in thread "main" org.infinispan.client.hotrod.exceptions.HotRodClientException: Put response (opcode=0x02) returned server error (status=0x85): ...{code}
> This is related to ISPN-944 which should solve the fact that server error messages are not being read by the client properly.

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