Rachit gUPTA created HTTPCORE-576:
-------------------------------------

             Summary: DefaultListeningIOReactor does not resumes listening to 
requests after stopped with linux OS
                 Key: HTTPCORE-576
                 URL: https://issues.apache.org/jira/browse/HTTPCORE-576
             Project: HttpComponents HttpCore
          Issue Type: Bug
          Components: HttpCore, HttpCore NIO
    Affects Versions: 4.4.9
            Reporter: Rachit gUPTA


We are using DefaultListeningIOReactor with nio http server 4.5.5, within our 
application we have a setting when the number a requests reaches a particular 
value, we call pause() method on DefaultListeningIOReactor object and when the 
request gets handled, software resumes listening to new request with the help 
of resume() method.

However with Linux machine, this behavior does not seems to be working, and 
when we try to resume the listener, it throws BindException. At the same time 
if we check we do not have any process running in the same port.

 

This application is working fine with Windows machine and also worked well with 
HTTPComponent 4.0.2 beta version.

 

We are using this code to pause and resume :

 

ListeningIOReactor serverHandle = 
(ListeningIOReactor)ServerHandles.get(portKey);
if (serverHandle!=null)
{
serverHandle.pause();
}

 

ListeningIOReactor serverHandle = 
(ListeningIOReactor)ServerHandles.get(portKey);
if (serverHandle!=null)
{
serverHandle.resume();
}

 

Here this ServerHandles is map whoch we populate ate the time of creating 
server like this :

 

final ListeningIOReactor ioReactor = new DefaultListeningIOReactor(
workerThread, params);
ServerHandles.put(new Integer(connector.getPort()),ioReactor);

try {
ioReactor.listen(socketaddress);
ioReactor.execute(ioEventDispatch);

 

Can anyone please help for this.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to