[
https://issues.jboss.org/browse/JBIDE-10224?page=com.atlassian.jira.plugi...
]
jaikiran pai commented on JBIDE-10224:
--------------------------------------
My guess is that whatever mechanism JBoss Tools is using right now, is ending up using a
older version of JBoss Remoting3 and JBoss SASL libraries. The server side in 7.1.0 Beta1
is using remoting3 3.2.0.CR3 and sasl 1.0.0.Beta6. I've seen users running into this
issue if the client had a different (lower) versions of this library.
Ofcourse it's a different matter whether the backward compatibility was intentionally
changed or if it's an oversight/bug.
JBossAS 7.1 cannot be launched
------------------------------
Key: JBIDE-10224
URL:
https://issues.jboss.org/browse/JBIDE-10224
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS/Servers
Affects Versions: 3.3.0.M4
Reporter: Juergen Zimmermann
Assignee: Rob Stryker
Labels: jbossas_7.1
Fix For: 3.3.0.M5
I just installed JBossAS 7.1.Beta1. However, the server start is hanging in an endless
loop (see below). Maybe it's due to the new security mechanism in
standalone/configuration/mgmt-users.properties.
Console output:
13:55:42,836 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.1.0.Beta1
"Tesla" started in 2862ms - Started 143 of 206 services (60 services are passive
or on-demand)
13:55:45,116 ERROR [org.jboss.remoting.remote] (Remoting
"iwi-w-ziju01-c:MANAGEMENT" read-1) JBREM000200: Remote connection failed:
java.io.IOException: JBREM000201: Received invalid message on Remoting connection 001bd732
to /127.0.0.1:53864
// from now on: endless loop of the preceeding line
--
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