[jboss-remoting-issues] [JBoss JIRA] Closed: (JBREM-915) NullPointerException in InvokerLocator
Ron Sigal (JIRA)
jira-events at lists.jboss.org
Fri Mar 28 20:52:41 EDT 2008
[ http://jira.jboss.com/jira/browse/JBREM-915?page=all ]
Ron Sigal closed JBREM-915.
---------------------------
Resolution: Done
> NullPointerException in InvokerLocator
> --------------------------------------
>
> Key: JBREM-915
> URL: http://jira.jboss.com/jira/browse/JBREM-915
> Project: JBoss Remoting
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jmx remoting
> Affects Versions: 2.2.2.SP4
> Environment: JBEAP 4.3 (JBoss Remoting 2.2.2 SP4)
> Windows 2000
> Reporter: Matthew Brasier
> Assigned To: Ron Sigal
> Priority: Minor
> Fix For: 2.2.2.SP7
>
>
> A NullPointerException is thrown by InvokerLocator.resolveHost if a null host is passed in. (Line 333 of InvokerLocator.java for the 2.2.2SP4 tag)
> This was observed when running JBEAP 4.3 on a laptop that has a VPN client installed. JBoss was configured to bind to all interfaces (-b0.0.0.0) and iIt appears that this configuration results in a null host being passed to resolveHost. resolveHost then does a host.indexOf("0.0.0.0") which throws the NPE.
> On the laptop in question, this can be worked around by explicitly binding the the required IP address, rather than binding to all, but the code should handle the case where a null host is passed in more gracefully.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-remoting-issues
mailing list