GroupHandle.sendMessage with Null targetComponentName results in exception being thrown

[glassfishrobot]

Based on the javadoc, "Specifying a null component name would result in the message being delivered to all registered components in the target member instance."

When actually done via: gh.sendMessage(null, "testMsg3".getBytes());

The receiving side gets the following exception:

[#|2010-01-21T14:55:23.953-0500|SEVERE|Shoal|ShoalLogger|_ThreadID=14;_ThreadName=com.sun.enterprise.ee.cms.impl.common.Router Thread;ClassName=SignalHandler;MethodName=run;|exiting due unhandled exception in thread com.sun.enterprise.ee.cms.impl.common.Router Thread java.lang.NullPointerException at java.util.Hashtable.get(Hashtable.java:334) at com.sun.enterprise.ee.cms.impl.common.Router.notifyMessageAction(Router.java:356) at com.sun.enterprise.ee.cms.impl.common.SignalHandler.analyzeSignal(SignalHandler.java:128) at com.sun.enterprise.ee.cms.impl.common.SignalHandler.handleSignal(SignalHandler.java:106) at com.sun.enterprise.ee.cms.impl.common.SignalHandler.run(SignalHandler.java:91) at java.lang.Thread.run(Thread.java:637)

| #] |

Environment

Operating System: All Platform: All

Affected Versions

[current]

[glassfishrobot]

• Issue Imported From: https://github.com/javaee/shoal/issues/97
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @jfialli
• Original Issue Closed By:@glassfishrobot

[glassfishrobot]

@glassfishrobot Commented Reported by sdimilla

[glassfishrobot]

@glassfishrobot Commented @jfialli said: Fix checked into trunk and pluggable transport branch.

Sending to null targetComponent is no longer allowed. Updated javadoc to reflect this change.

[glassfishrobot]

@glassfishrobot Commented @jfialli said:

• • • Issue 85 has been marked as a duplicate of this issue. ***

[glassfishrobot]

@glassfishrobot Commented This issue was imported from java.net JIRA SHOAL-97

[glassfishrobot]

@glassfishrobot Commented Marked as fixed on Wednesday, June 23rd 2010, 4:11:06 am