[jboss-jira] [JBoss JIRA] (AS7-1431) JBREM00205 when starting domain controller

[David Lloyd (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/AS7-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637182#comment-12637182 ] 

David Lloyd commented on AS7-1431:
----------------------------------

This may be fixed in the latest upstream.  Can you verify?
                
> JBREM00205 when starting domain controller
> ------------------------------------------
>
>                 Key: AS7-1431
>                 URL: https://issues.jboss.org/browse/AS7-1431
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 7.0.0.Final
>         Environment: 1 Windows XP + 1 Linux Host with jdk 1.6.0_26 each. I guess that a different enviroment won't change things. Why do you deliver Beta versions for xnio + remoting?
>            Reporter: Andreas Tauber
>            Assignee: Brian Stansberry
>
> I try to setup cluster on two hosts using provided manual "Domain Setup". Host Controller on Windows XP can establish connection to Domain Controller on Linux because i see message:
> Registered remote slave host staging.
> But I can't see server instances on admin console. So, it seems like the Domain Controller is not able to connect back to native interface on Host Controller. Not really sure here.
> Shutting down my host controller, I get warnings in boot.log. Here my complete boot.log:
> 17:05:58,484 INFO  [org.jboss.modules] (main) JBoss Modules version 1.0.1.GA
> 17:05:58,796 INFO  [org.jboss.msc] (main) JBoss MSC version 1.0.0.GA
> 17:05:59,156 INFO  [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 3.2.0.Beta2
> 17:05:59,171 INFO  [org.xnio] (MSC service thread 1-2) XNIO Version 3.0.0.Beta3
> 17:05:59,187 INFO  [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.0.Beta3
> 17:06:00,250 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) Listening on /192.168.2.10:9999
> 17:06:04,468 WARN  [org.jboss.remoting.remote] (XNIO NIO Write 1) JBREM00205: Failed to accept a connection: java.nio.channels.ClosedChannelException
> 17:06:04,484 WARN  [org.jboss.remoting.remote] (XNIO NIO Write 1) JBREM00205: Failed to accept a connection: java.nio.channels.ClosedChannelException
> 17:06:04,484 WARN  [org.jboss.remoting.remote] (XNIO NIO Write 1) JBREM00205: Failed to accept a connection: java.nio.channels.ClosedChannelException
> 17:06:04,484 WARN  [org.jboss.remoting.remote] (XNIO NIO Write 1) JBREM00205: Failed to accept a connection: java.nio.channels.ClosedChannelException
> 17:06:04,484 WARN  [org.jboss.remoting.remote] (XNIO NIO Write 1) JBREM00205: Failed to accept a connection: java.nio.channels.ClosedChannelException
> 17:06:04,484 WARN  [org.jboss.remoting.remote] (XNIO NIO Write 1) JBREM00205: Failed to accept a connection: java.nio.channels.ClosedChannelException
> Note: I renamed the servers to not create name clash (server-four, server-five, server-six) and disabled auto start because I wanted to start instances from admin console on domain controller. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira