You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Vinod Panicker (JIRA)" <ji...@apache.org> on 2006/08/17 07:35:17 UTC
[jira] Created: (DIRMINA-245) MINA does not fire read events
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
[jira] Commented: (DIRMINA-245) MINA does not fire read events
Posted by "peter royal (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (DIRMINA-245) MINA does not fire read events
Posted by "Trustin Lee (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRMINA-245?page=comments#action_12432717 ]
Trustin Lee commented on DIRMINA-245:
-------------------------------------
Peter confirmed that the order of events are maintained for all kinds of thread pools. I will replace L-F pool with a simpler one.
> 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
>
> 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
[jira] Updated: (DIRMINA-245) MINA does not fire read events
Posted by "Trustin Lee (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRMINA-245?page=all ]
Trustin Lee updated DIRMINA-245:
--------------------------------
Fix Version/s: 1.0
We have to fix this before we release 1.0.
> 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
[jira] Commented: (DIRMINA-245) MINA does not fire read events
Posted by "Trustin Lee (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRMINA-245?page=comments#action_12432563 ]
Trustin Lee commented on DIRMINA-245:
-------------------------------------
It seems like Peter implemented ThreadPoolFilter to work with any thread pool implementation without compromising the order of events. I did it in L-F pool, so I think it's a duplicate work and that's why L-F performs bad. L-F is very complex to implement and I suspect a bug was introduced while we split it from ThreadPoolFilter. I am very fine with replacing L-F pool with regular thread pool if Peter confirms that the order of events is maintained for any kind of thread pool.
> 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
[jira] Assigned: (DIRMINA-245) MINA does not fire read events
Posted by "Trustin Lee (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRMINA-245?page=all ]
Trustin Lee reassigned DIRMINA-245:
-----------------------------------
Assignee: Trustin Lee
> 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
>
> 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
[jira] Resolved: (DIRMINA-245) MINA does not fire read events
Posted by "Trustin Lee (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRMINA-245?page=all ]
Trustin Lee resolved DIRMINA-245.
---------------------------------
Resolution: Fixed
Now we are using ThreadPoolExecutor from backport-util-concurrent. There were a few changes in the API. Please refer to DIRMINA-260.
> 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
[jira] Commented: (DIRMINA-245) MINA does not fire read events
Posted by "Trustin Lee (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRMINA-245?page=comments#action_12432557 ]
Trustin Lee commented on DIRMINA-245:
-------------------------------------
One possibility is the case that there's no leader but only followers. No threads will accept the events then.
> 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
[jira] Commented: (DIRMINA-245) MINA does not fire read events
Posted by "Trustin Lee (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRMINA-245?page=comments#action_12432556 ]
Trustin Lee commented on DIRMINA-245:
-------------------------------------
Is there any full thread dump? ... though I think there's no much clue there.
> 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
[jira] Commented: (DIRMINA-245) MINA does not fire read events
Posted by "Trustin Lee (JIRA)" <ji...@apache.org>.
[ 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