Bug 745855 (EDG-122) - HotRod: Unclear error message on node failure
Summary: HotRod: Unclear error message on node failure
Keywords:
Status: CLOSED WONTFIX
Alias: EDG-122
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/EDG...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-08 14:33 UTC by Radoslav Husar
Modified: 2012-03-16 18:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 745856 (view as bug list)
Environment:
Last Closed: 2011-03-15 15:21:42 UTC
Type: Feature Request


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker EDG-122 0 None Closed HotRod: Unclear error message on node failure 2011-10-13 15:31:31 UTC
Red Hat Issue Tracker ISPN-944 0 None Resolved Server error messages not being returned to clients 2011-10-13 15:31:31 UTC

Description Radoslav Husar 2011-03-08 14:33:35 UTC
project_key: EDG

This happens 2 seconds after the server a client is connected to crashes.

Its not very clear what is actually happening. A more descriptive message would be helpful.

{code}
        org.infinispan.client.hotrod.exceptions.HotRodClientException: id [155810] code [133] 
	at org.infinispan.client.hotrod.impl.operations.HotRodOperation.checkForErrorsInResponseStatus(HotRodOperation.java:129)
	at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:98)
	at org.infinispan.client.hotrod.impl.operations.AbstractKeyValueOperation.sendPutOperation(AbstractKeyValueOperation.java:48)
	at org.infinispan.client.hotrod.impl.operations.PutOperation.executeOperation(PutOperation.java:27)
	at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:38)
	at org.infinispan.client.hotrod.impl.RemoteCacheImpl.put(RemoteCacheImpl.java:166)
	at org.infinispan.CacheSupport.put(CacheSupport.java:28)
	at org.jboss.smartfrog.edg.adapter.HotRodAdapter$HotRodRemoteCacheAdapter.put(HotRodAdapter.java:150)
	at org.jboss.smartfrog.edg.loaddriver.CacheRequestProcessorFactory$InfinispanRequestProcessor.processRequest(CacheRequestProcessorFactory.java:163)
	at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:51)
	at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87)
	at java.lang.Thread.run(Thread.java:619)
{code}

Comment 1 Radoslav Husar 2011-03-08 14:35:16 UTC
Link: Added: This issue is related to ISPN-944


Comment 2 Radoslav Husar 2011-03-08 14:49:03 UTC
Link: Added: This issue is incorporated by JBPAPP-6054


Comment 3 Galder Zamarreño 2011-03-08 15:18:45 UTC
Rado, as you said this was executed with CR3 and precisely for CR4 I fixed messages and providing clearer exceptions. Closing now. Please reopen if no satisfied with CR4.

Comment 4 Radoslav Husar 2011-03-15 15:21:42 UTC
So the new messages are in this format: "Request for message id[139205] returned server error (status=0x85)" also with a server exception rethrown. This gives the app enough information to work with. Closing.


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