Bug 745859 (EDG-102)

Summary: HotRodServer fails to start with "Expected just one response; got {} instead!"
Product: [JBoss] JBoss Data Grid 5 Reporter: Radoslav Husar <rhusar>
Component: InfinispanAssignee: Default User <jbpapp-maint>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: galder.zamarreno, rhusar
Target Milestone: ---   
Target Release: EAP 5.1.0 EDG TP   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/EDG-102
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-11 13:57:40 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:

Description Radoslav Husar 2011-03-08 14:46:31 UTC 
project_key: EDG

After issues with state transfer, hotrod server fails to start

http://hudson.qa.jboss.com/hudson/job/edg-51x-resilience-client-size4-hotrod/13/console-perf01/

{code}
[JBoss] 08:51:02,327 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
[JBoss] 
[JBoss] DEPLOYMENTS IN ERROR:
[JBoss]   Deployment "HotRodServer" is in error due to the following reason(s): org.infinispan.remoting.RpcException: Expected just one response; got {} instead!
[JBoss] 
[JBoss] 08:51:02,338 INFO  [Http11Protocol] Starting Coyote HTTP/1.1 on http-172.17.64.254-8080
[JBoss] 08:51:02,356 INFO  [AjpProtocol] Starting Coyote AJP/1.3 on ajp-172.17.64.254-8009
[JBoss] 08:51:02,359 INFO  [ServerImpl] JBoss (Microcontainer) [5.1.0.Branch (build: SVNTag=JBPAPP_5_1_0_Branch date=201103081348)] Started in 2m:5s:687ms
{code}
Comment 1 Radoslav Husar 2011-03-08 14:49:04 UTC 
Link: Added: This issue is incorporated by JBPAPP-6054
Comment 2 Galder Zamarreño 2011-03-08 15:11:04 UTC 
When a HotRod server starts, it maintains a view of the servers and their corresponding endpoint addresses. So, I'd assume this failure is due to being unable to replicate that view. No idea why.
Comment 3 Galder Zamarreño 2011-03-09 17:16:59 UTC 
Rado, I created ISPN-972 to track this. I'd suggest you explain the circumstances under which this happens in the ISPN jira itself. Thanks :)
Comment 4 Galder Zamarreño 2011-03-09 17:17:35 UTC 
Link: Added: This issue depends ISPN-972
Comment 5 Galder Zamarreño 2011-03-11 13:37:49 UTC 
I believe the issue here was due to a suspicion. Manik's made the error clearer now. Closing now.
Comment 6 Radoslav Husar 2011-03-11 13:54:24 UTC 
So did the hotrod server get started actually and fully functional? Not sure how can I check that solely from logs.
Comment 7 Galder Zamarreño 2011-03-11 14:00:18 UTC 
No, I don't think it did. Was the suspicion intended?