Bug 1009766 - Warning messages during server startup on Solaris
Summary: Warning messages during server startup on Solaris
Keywords:
Status: CLOSED DUPLICATE of bug 1011831
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Remoting
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: David M. Lloyd
QA Contact: Jitka Kozana
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-19 05:54 UTC by Petr Kremensky
Modified: 2014-03-04 12:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-04 12:30:27 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
Server logs (23.47 KB, application/x-zip)
2013-09-19 05:54 UTC, Petr Kremensky 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 997930 0 unspecified CLOSED HPUX: WARN: The currently defined selector provider class (sun.nio.ch.PollSelectorProvider) is not supported for use wit... 2021-02-22 00:41:40 UTC

Internal Links: 997930

Description Petr Kremensky 2013-09-19 05:54:56 UTC 
Created attachment 799743 [details]
Server logs

We've run into some warning messages during Clean EAP server start tests on Solaris:
[org.jboss.remoting.remote] (Remoting "dsp05" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
[org.jboss.remoting.remote] (Remoting "dsp05:MANAGEMENT" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException
[org.jboss.remoting.remote] (Remoting "master:server-two" read-1) JBREM000205: Failed to accept a connection: java.nio.channels.ClosedChannelException

See server-two.log which is extremely polluted by WARN messages. 

We believe that clean out-of-box EAP instance shouldn't give any serious logs (WARN, ERROR, FATAL).

Please change target component if needed.
Comment 1 Rostislav Svoboda 2014-03-04 12:30:27 UTC 

*** This bug has been marked as a duplicate of bug 1011831 ***
Note You need to log in before you can comment on or make changes to this bug.