Bug 1011831

Summary:	JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException at server shutdown
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Jitka Kozana <jkudrnac>
Component:	Remoting	Assignee:	David M. Lloyd <david.lloyd>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jitka Kozana <jkudrnac>
Severity:	medium	Docs Contact:	Russell Dickenson <rdickens>
Priority:	unspecified
Version:	6.2.0	CC:	jkudrnac, kkhan, lcosti, pkremens, rsvoboda
Target Milestone:	ER2
Target Release:	EAP 6.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	A `DEBUG` message from the remoting sugbsystem was incorrectly logged as a `WARN` message during server shutdown. The message logged was similar to the following: ---- 02:46:15,512 WARN [org.jboss.remoting.remote] (Remoting "node1:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException ---- As part of an upgrade to the remoting subsystem in this release of JBoss EAP 6, this message has been correctly reclassified as a `DEBUG` level message.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-28 15:37:00 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1080576
Bug Blocks:	1051640

Description Jitka Kozana 2013-09-25 08:25:34 UTC

This exception is sometimes logged on server shutdown:

02:46:15,512 WARN  [org.jboss.remoting.remote] (Remoting "node1:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException

See the server log here:

https://jenkins.mw.lab.eng.bos.redhat.com/job/eap-6x-manu-multinode-startup-different-IPs-solaris/jdk=java16_default,label_exp=sol10_sparc64/30/artifact/target/manu-reports/units/manu.testsuite.eap6.acceptance.multinodeStartup.MultinodeStartupDifferentIPs/server.log-standalone-full.xml-server2.log

Comment 1 Jitka Kozana 2013-10-07 12:19:52 UTC

Seen again during EAP 6.2.0.ER4 testing.

Comment 2 Jitka Kozana 2014-01-23 13:38:00 UTC

Seen again during EAP 6.2.1.CP.CR1 testing.

Comment 3 David M. Lloyd 2014-01-23 14:22:29 UTC

I have an upstream patch to move this message to DEBUG.  It is relevant, perhaps, but an unimportant condition, and not indicative of any real problem.

Comment 4 Rostislav Svoboda 2014-03-04 12:30:27 UTC

*** Bug 1009766 has been marked as a duplicate of this bug. ***

Comment 5 Rostislav Svoboda 2014-03-05 12:51:10 UTC

Proposing as blocker as discussed on EAP 6 PM meeting March 4.

This is blocking acceptance tests where we have requirement for issue-less startup & shutdown.

Comment 7 Rostislav Svoboda 2014-03-21 10:55:16 UTC

DEBUG level is fine, it's blocker from clean start and shutdown perspective, based on comments no functional issue.

David, please go ahead and grant dev_ack.

Comment 8 Kabir Khan 2014-04-08 17:39:03 UTC

Fixed by component upgrade https://bugzilla.redhat.com/show_bug.cgi?id=1080576 and https://github.com/jbossas/jboss-eap/pull/1205

Comment 9 Jitka Kozana 2014-04-30 12:33:58 UTC

EAP 6.3.0.ER2, Verified.