| Summary: | hot rod server exceptions don't display detailed messages | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Data Grid 5 | Reporter: | Michal Linhard <mlinhard> | ||||
| Component: | Infinispan | Assignee: | Default User <jbpapp-maint> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | EAP 5.1.0 EDG TP | CC: | galder.zamarreno, mlinhard, nobody | ||||
| Target Milestone: | --- | ||||||
| Target Release: | EAP 5.1.0 EDG TP | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://jira.jboss.org/jira/browse/EDG-51 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-03-02 15:43:59 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
wireshark.txt - attached TCP stream dump of one PUT with error response Attachment: Added: wireshark.txt Hmmmmm, this is exactly what I ended up fixing in ISPN-944 Link: Added: This issue depends ISPN-944 This issue has been solved for 4.2.1.Final already. Feel free to reopen. ok. it seems to be it. i'll verify this once 4.2.1.Final is out |
project_key: EDG infinispan version: 4.2.1.CR3 When a server side exception occurs in hotrod server, detailed message is not reported back to the client. I was trying this with replication timeout exceptions. - I ran 2 edg instances (host1, host2). - Placed a breakpoint to DefaultDataContainer.put() on host2 - did one PUT to host1 - This lead to repl. timeout on host1 This is reported as {code} org.infinispan.client.hotrod.exceptions.HotRodTimeoutException: id [2] code [134] {code} on the client side. What is missing is the message from the server: {code} org.infinispan.util.concurrent.TimeoutException: Replication timeout for localhost-37533 {code} this seems to be problem on the client side to me, I couldn't find problems in server code, when debugging. The message is sent correctly to the network. It even appears in wireshark, when I follow the TCP stream of one erroneous put. the code in the method HotRodOperation.checkForErrorsInResponseStatus() seems to try to retrieve the error message by means of transport.readString(), but only "" (zero length string) is returned.