Bug 1074640 - Random ShutdownChannelGroupException on a peaceful, clean shutdown with no load
Summary: Random ShutdownChannelGroupException on a peaceful, clean shutdown with no load
Keywords:
Status: CLOSED DUPLICATE of bug 1075695
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web
Version: 6.3.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: DR3
: EAP 6.3.0
Assignee: Rémy Maucherat
QA Contact: Radim Hatlapatka
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-10 17:50 UTC by Michal Karm Babacek
Modified: 2014-10-25 12:17 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-03-13 16:47:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Michal Karm Babacek 2014-03-10 17:50:54 UTC
With EAP 6.3.0.DR2, a single web application deployed (both with distributable and non-distributable versions), several requests made to it, one can get ShutdownChannelGroupException on a clean shutdown, for a no apparent reason.

I believe this is a random race condition, yet it is noteworthy that it occurred with mod_cluster and JGroups subsystems in place, standalone-ha profile.

{noformat}
(Thread-105) Exception in thread "Thread-105" java.nio.channels.ShutdownChannelGroupException
(Thread-105)        at sun.nio.ch.Invoker.invokeIndirectly(Invoker.java:210)
(Thread-105)        at sun.nio.ch.UnixAsynchronousSocketChannelImpl.finishRead(UnixAsynchronousSocketChannelImpl.java:432)
(Thread-105)        at sun.nio.ch.UnixAsynchronousSocketChannelImpl.finish(UnixAsynchronousSocketChannelImpl.java:191)
(Thread-105)        at sun.nio.ch.UnixAsynchronousSocketChannelImpl.onEvent(UnixAsynchronousSocketChannelImpl.java:213)
(Thread-105)        at sun.nio.ch.EPollPort$EventHandlerTask.run(EPollPort.java:293)
(Thread-105)        at java.lang.Thread.run(Thread.java:744)
{noformat}

Environment is:
java version "1.7.0_51"
OpenJDK Runtime Environment (rhel-2.4.4.1.el6_5-x86_64 u51-b02)
&
OpenJDK Runtime Environment (rhel-2.4.4.1.el7-x86_64 u51-b02)


Any ideas?

Comment 1 Michal Karm Babacek 2014-03-10 17:55:36 UTC
It might actually not be limited to JBossWeb, I guess JGroup use NIO as well, so mabye lThon might have seen it somewhere as well... WDYT lThon? :-)

Comment 2 Ladislav Thon 2014-03-11 07:18:34 UTC
I don't remember seeing this. It's not clear if this happens in clustering (I guess you get this in a clustered setting) or in the web subsystem. Can you [try to] reproduce this in the standalone profile (i.e., no "ha")?

Comment 3 Michal Karm Babacek 2014-03-13 11:40:50 UTC
AFAIK, this is specific to standalone-ha (ha) profile, inherently to full-ha (not tested). On the other hand, the fact that I didn't see it proves nothing, provided it's some kind of a race condition.

I will bring this email from the internal jboss-support-eap6 list to your attention:
    [01035878] Http11NioProtocol not being able to handle concurrent requests

Aaron? WDYT? Is it related?

Comment 4 Michal Karm Babacek 2014-03-13 16:47:49 UTC

*** This bug has been marked as a duplicate of bug 1075695 ***


Note You need to log in before you can comment on or make changes to this bug.