You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mina.apache.org by "peter royal (JIRA)" <ji...@apache.org> on 2006/08/20 20:53:14 UTC

[jira] Commented: (DIRMINA-245) MINA does not fire read events

    [ http://issues.apache.org/jira/browse/DIRMINA-245?page=comments#action_12429284 ] 
            
peter royal commented on DIRMINA-245:
-------------------------------------

If the Executor-based thread pool is a workaround, sounds like a bug is in our LeaderFollowerThreadPool then.

fwiw, I highly recommend using Java5 concurrency bits where possible. I'm happy to hear that's a workaround for now :)

> MINA does not fire read events
> ------------------------------
>
>                 Key: DIRMINA-245
>                 URL: http://issues.apache.org/jira/browse/DIRMINA-245
>             Project: Directory MINA
>          Issue Type: Bug
>    Affects Versions: 0.9.4, 0.9.5
>         Environment: Java 5, Java 6. Not reproducible on Windows
>            Reporter: Vinod Panicker
>            Priority: Blocker
>
> We've been stumped with a serious issue with MINA where it stops firing read events after a particular scenario occurs. The scenario is such - 
> 1. A MINA server is listening for connections
> 2. Clients connect to it and send requests - server responds
> 3. Number of clients concurrently connected doing the same activity is around 60-100
> 4. Clients are terminated abruptly
> 5. Server processes disconnects and is idle
> 6. New client connects and sends requests
> 7. Server accepts connection, but a read event is not fired. This happens with each subsequent client connection.
> On debugging, we found that the JVM is notifying MINA about the read event, but after the event is put into the queue for processing, MINA does not process it and a read event is not fired.  sessionCreated, however is fired.
> On using the Executor based thread pool implementation, this problem does not occur.
> This problem is not reproducible on Windows based systems.  Reproduced on Linux systems with java 5 and 6.
> Unfortunately, we can't provide a test case at the moment since we were able to reproduce this only with our application server and custom client.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira