mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Trustin Lee (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRMINA-245) MINA does not fire read events
Date Thu, 07 Sep 2006 04:54:23 GMT
    [ http://issues.apache.org/jira/browse/DIRMINA-245?page=comments#action_12433019 ] 
Trustin Lee commented on DIRMINA-245:

I want to introduce backport-concurrent-util here.  Would this be fine for everyone?

> 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
>         Assigned To: Trustin Lee
>            Priority: Blocker
>             Fix For: 1.0
> 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


View raw message