Grizzly ignores the selector handlers added to Controller if the controller is already running

[glassfishrobot]

Grizzly v1.6.1/0 onwards:
Grizzly ignores the TCP selection handlers added if the controller is
already started. In the old versions this is not a problem.

Here is a TENTATIVE fix: In Controller.java:

public void addSelectorHandler(SelectorHandler selectorHandler){
if (selectorHandlers == null)

{ selectorHandlers = new ConcurrentLinkedQueue(); }

selectorHandlers.add(selectorHandler);

if (isStarted())

{ Runnable selectorRunner = new SelectorHandlerRunner(this, selectorHandler); new Thread(selectorRunner).start(); }

}

Environment

Operating System: All
Platform: Sun

[glassfishrobot]

@glassfishrobot Commented
Reported by raih@java.net

[glassfishrobot]

@glassfishrobot Commented
Was assigned to oleksiys@java.net

[glassfishrobot]

@glassfishrobot Commented
jfarcand@java.net said:
...

[glassfishrobot]

@glassfishrobot Commented
oleksiys@java.net said:
fixed

[glassfishrobot]

@glassfishrobot Commented
jfarcand@java.net said:
Fix milestones

[glassfishrobot]

@glassfishrobot Commented
Marked as fixed on Wednesday, December 16th 2009, 6:14:11 pm

[glassfishrobot]

@glassfishrobot Commented
This issue was imported from java.net JIRA GRIZZLY-37

[glassfishrobot]

• Issue Imported From: Grizzly ignores the selector handlers added to Controller if the controller is already running javaee/grizzly#37
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @glassfishrobot
• Original Issue Closed By:@glassfishrobot