Uploaded image for project: 'MINA'
  1. MINA
  2. DIRMINA-818

Loosing connects on NioSocketConnector

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments


    • Bug
    • Status: Resolved
    • Major
    • Resolution: Abandoned
    • 2.0.2
    • 2.0.8
    • Core
    • None
    • WinXP JDK 1.6.1_23


      I implemented a reconnection mode, which initiates a immediate NIOSocketConnector.connect after connection is broken. This works fine for a while, but NioSocketConnector thread stops performing connects on TCP/IP level after a while. Connects are then lost in MINA and the corresponding connect future listener is never called... Connector thread is no longer in thread list of target VM (listet by Netbeans Debugger or VisualVM) My Automatic doesn't work any longer... Connection requests are done by a scheduler thread in my API, or direct in the thread running the DisconnectFuture.operationComplete() callback, "NioProcessor-X" thread AFAIK. In MINA-Core 2.0.2 I found NioSocketConnector and AbstractPollingIoConnector which iterate with a MINA provided Iterator implementation over the keys() and selectedKeys() Set provided by the selector. Iterator remove is also used. Both Set provided by the Selector are NOT THREAD SAFE as the java API doc says. What happens if another thread adds a connection request to the selector and MINA AbstractPollingIoConnector.Connector is processing the Set with its Iterator and calls remove on the Iterator? Concurrent modification error or some other inconsistence? I think iteration should be done with a copy of the Set and remove should be done on the original keys() and selectedKeys() Set synchronized with a concurrency protecting lock. What do you think about?



          This comment will be Viewable by All Users Viewable by All Users


            Unassigned Unassigned
            j.michelberger Jörg Michelberger
            0 Vote for this issue
            2 Start watching this issue




                Issue deployment