[
https://issues.jboss.org/browse/AS7-2268?page=com.atlassian.jira.plugin.s...
]
Andreas Tauber commented on AS7-2268:
-------------------------------------
Hi Tomaz, thx for your quick answer and sorry for my slow one (was out for a birthday
party).
i reinstalled jboss as on both sides again, configured domain controller and tested ping
and telnet communication which works without problem.
After disconnecting the telnet client by pressing return two times, the server prints:
[Host Controller] 01:16:24,497 ERROR [org.jboss.remoting.remote] (Remoting
"master:MANAGEMENT" read-1) JBREM000200: Remote connection failed:
java.io.IOException: Received an invalid message length of 218762506
Thats ok for me, because by using telnet I am not sending real remoting message over
socket.
Starting xp client without security-realm attribute on remote element I get:
[Host Controller] 02:00:45,546 ERROR [org.jboss.remoting.remote] (Remoting "endp
oint" read-1) JBREM000200: Remote connection failed: javax.security.sasl.SaslExc
eption: Authentication failed: all available authentication mechanisms failed
[Host Controller] 02:00:45,546 WARN [org.jboss.as.host.controller] (Controller
Boot Thread) JBAS010900: Could not connect to remote domain controller 192.168.2
.100:9999
[Host Controller] 02:00:45,562 ERROR [org.jboss.as.host.controller] (Controller
Boot Thread) JBAS010901: Could not connect to master. Aborting. Error was: java.
lang.IllegalStateException: JBAS010942: Unable to connect due to authentication
failure.
Authentication fails! But the communication problem in my last comment seems to be
solved.
After adding the security-realm attribute I get:
[Host Controller] JBAS014775: New missing/unsatisfied dependencies:
[Host Controller] service jboss.server.controller.management.security_real
m.ManagementRealm.secret (missing) dependents: [service jboss.domain.controller.
connection]
[Host Controller]
I am missing JBoss Modules dependency, but why?
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
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