Bug 745863 (EDG-42) - HotRodServer throwing NPE when removing itself from view
Summary: HotRodServer throwing NPE when removing itself from view
Keywords:
Status: CLOSED NEXTRELEASE
Alias: EDG-42
Product: JBoss Data Grid 5
Classification: JBoss
Component: Infinispan
Version: unspecified
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-42
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-08 15:25 UTC by Galder Zamarreño
Modified: 2011-10-11 17:05 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-09 07:37:40 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker EDG-42 0 None Closed HotRodServer throwing NPE when removing itself from view 2012-07-11 01:00:00 UTC

Description Galder Zamarreño 2011-03-08 15:25:43 UTC 
project_key: EDG

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

{code}[JBoss] 08:50:03,562 WARN  [StartStopLifecycleAction] Error during stop for HotRodServer
[JBoss] java.lang.NullPointerException
[JBoss] 	at org.infinispan.server.hotrod.HotRodServer.removeSelfFromTopologyView(HotRodServer.scala:124)
[JBoss] 	at org.infinispan.server.hotrod.HotRodServer.stop(HotRodServer.scala:119)
[JBoss] 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[JBoss] 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[JBoss] 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[JBoss] 	at java.lang.reflect.Method.invoke(Method.java:597){code}
Comment 1 Galder Zamarreño 2011-03-08 15:26:01 UTC 
Link: Added: This issue is incorporated by JBPAPP-6054
Comment 2 Galder Zamarreño 2011-03-08 16:53:34 UTC 
Link: Added: This issue depends ISPN-967
Note You need to log in before you can comment on or make changes to this bug.