[jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1661) NullPointerException when calling printDetails on cache containing nested clustered SFSB

Carlo de Wolf (JIRA) jira-events at lists.jboss.org
Tue Sep 7 07:18:54 EDT 2010


     [ https://jira.jboss.org/browse/EJBTHREE-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carlo de Wolf resolved EJBTHREE-1661.
-------------------------------------

    Resolution: Out of Date


This issue is reported against a version which is no longer maintained,
which means that it will not receive a fix. As a result we are closing
this bug.

If you can reproduce this bug against a currently maintained version of 
JBoss EJB 3 please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

> NullPointerException when calling printDetails on cache containing nested clustered SFSB
> ----------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1661
>                 URL: https://jira.jboss.org/browse/EJBTHREE-1661
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: cache, Clustering
>    Affects Versions: AS 4.2.3.GA
>            Reporter: Galder Zamarreño
>            Assignee: Galder Zamarreño
>            Priority: Minor
>             Fix For: Branch_4_2
>
>
> After invoking an operation spanning a clustered EJB3 SFSB that has a reference to a another 
> clustered EJB3 SFSB, if you try to call printDetails() on the EJB3 SFSB cache, you'll get an exception 
> like this:
> java.lang.NullPointerException
> 	org.jboss.ejb3.stateful.StatefulBeanContext.hashCode(StatefulBeanContext.java:927)
> 	java.lang.Object.toString(Object.java:236)
> 	java.lang.String.valueOf(String.java:2838)
> 	java.lang.StringBuffer.append(StringBuffer.java:236)
> 	org.jboss.cache.AbstractNode.printDetailsInMap(AbstractNode.java:176)
> 	org.jboss.cache.Node.printDetails(Node.java:411)
> 	org.jboss.cache.AbstractNode.printDetailsInMap(AbstractNode.java:185)
> 	org.jboss.cache.Node.printDetails(Node.java:411)
> 	org.jboss.cache.AbstractNode.printDetailsInMap(AbstractNode.java:185)
> 	org.jboss.cache.Node.printDetails(Node.java:411)
> 	org.jboss.cache.TreeCache.printDetails(TreeCache.java:4181)
> 	sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	java.lang.reflect.Method.invoke(Method.java:616)
> 	org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
> 	org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
> 	org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
> 	org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> 	org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
> 	org.jboss.jmx.adaptor.control.Server.invokeOpByName(Server.java:258)
> 	org.jboss.jmx.adaptor.control.Server.invokeOp(Server.java:223)
> 	org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOp(HtmlAdaptorServlet.java:276)
> 	org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:100)
> 	org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:82)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> 	javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> 	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> This is due to trying to call to hashCode() on a ProxiedStatefulBeanContext which doesn't
> contain any containerClusterUid as such. Instead, ProxiedStatefulBeanContext should 
> somehow pass the request for containerClusterUid to its delegate.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       



More information about the jboss-jira mailing list