Bug 745852 (EDG-51) - hot rod server exceptions don't display detailed messages
Summary: hot rod server exceptions don't display detailed messages
Keywords:
Status: CLOSED NEXTRELEASE
Alias: EDG-51
Product: JBoss Data Grid 5
Classification: JBoss
Component: Infinispan
Version: EAP 5.1.0 EDG TP
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: EAP 5.1.0 EDG TP
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/EDG-51
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-02 12:19 UTC by Michal Linhard
Modified: 2014-03-17 04:02 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-02 15:43:59 UTC
Type: Bug


Attachments (Terms of Use)
wireshark.txt (1.63 KB, text/plain)
2011-03-02 12:24 UTC, Michal Linhard
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker EDG-51 0 None None None Never

Description Michal Linhard 2011-03-02 12:19:14 UTC
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.

Comment 1 Michal Linhard 2011-03-02 12:24:26 UTC
wireshark.txt - attached TCP stream dump of one PUT with error response

Comment 2 Michal Linhard 2011-03-02 12:24:26 UTC
Attachment: Added: wireshark.txt


Comment 3 Galder Zamarreño 2011-03-02 15:42:19 UTC
Hmmmmm, this is exactly what I ended up fixing in ISPN-944

Comment 4 Galder Zamarreño 2011-03-02 15:42:58 UTC
Link: Added: This issue depends ISPN-944


Comment 5 Galder Zamarreño 2011-03-02 15:43:59 UTC
This issue has been solved for 4.2.1.Final already. Feel free to reopen.

Comment 6 Michal Linhard 2011-03-02 16:06:57 UTC
ok. it seems to be it. i'll verify this once 4.2.1.Final is out


Note You need to log in before you can comment on or make changes to this bug.