[jboss-jira] [JBoss JIRA] (AS7-2268) Domain member does startup instances

[Andreas Tauber (JIRA)]

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

Andreas Tauber commented on AS7-2268:
-------------------------------------

Hi Tomaz, first the good news: Passed the Certified Expert EJB Developer Exam with 95% today. Quiet happy about that.

Im not sure here. I guess you talk about the message:
21:25:19,477 DEBUG [org.jboss.as.protocol] (Remoting "server-1:MANAGEMENT" task-1) active-op (405838434) failed null: java.io.IOException: Channel closed
This is a message of server-1? It is logged in server-1 logs when I shutdown my domain-controller. I have actually no problems with server-1 which runs on domain-controller.

Like mentioned, I would expect to see slave-server to registered with domain-controller.
I dont understand. Why should I get a messages:
21:21:45,179 INFO  [org.jboss.as.domain] (management-handler-threads - 4) JBAS010918: Registered remote slave host slave
21:25:19,468 INFO  [org.jboss.as.domain] (MSC service thread 1-7) JBAS010925: Unregistered remote slave host slave
The communication between HC and DC seem to work. And my instance slave-server is not registered.

I adjusted the logging.properties, but i didnt get any additional useful information.
Sorry, I have no other enviroment at hand. I cannot test at work, because it is public institution working with Weblogic servers. Sorry, for the Weblogic thing. JBoss team is doing great work with the new AS7.
But wait, I have an old Windows 2000 host here. Does it make sense to use it? Which of the the other two would you replace? The Linux or XP? Where should I place domain controller?
                
> Domain member does startup instances
> ------------------------------------
>
>                 Key: AS7-2268
>                 URL: https://issues.jboss.org/browse/AS7-2268
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 7.0.2.Final
>         Environment: SuSE Linux Domain Admin; Windows XP Domain Member; JBoss Web 7.0.2 on both sides
>            Reporter: Andreas Tauber
>            Assignee: Tomaz Cerar
>             Fix For: 7.1.0.Final
>
>         Attachments: logging.properties, logs.zip, windows-linux-config.zip
>
>
> After creating domain setup, resolved with ticket AS7-1431 individual instances defined with attribute autostart in host.xml of the domain member to not startup automatically when starting the domain.sh of this cluster member.
> Ok, at the moment the Admin Console is able to see my Windows XP Domain Member with three defined instances (they dont honor autostart). So I try to use Console to start those instances. Nothing really happens. AdminConsole shows green light, pressing another button goes back to red. ok, green, then red, the instances on xp domain member are not started.
> Starting server-four(xp) from my AdminConsole on domain controller(linux) brings one message on console:
> [Host Controller] 21:56:04,984 WARN  [org.jboss.as.host.controller] (pool-4-thread-4) Existing server [Server:server-four] with state: STARTING 
> But simply nothing happens.
> Looking forward to do full cluster deployment on "my" JBoss AS7.

--
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