[JBoss Tools (users)] - Re: JBoss 4.3.0 fails to start
by rob.stryker@jboss.com
The tools poll the server via JMX repeatedly in order to see if the server is up yet. The warning messages are not critical but if you go through them you'll see first no connection can be made (server hasn't even gotten jmx up yet), jmx isn't bound (jmx itself isnt listening on the port yet), and finally, either a success or failure.
It's failing ;) What's failing is that your authentication is not being accepted. The polling mechanism uses the RMIAdapter in JMX to ask if the server is up. The other possibility (which the tools does *not* use) is the http adapter (ie viewing on a web page for example).
Both of these adapters can be password protected. If they are, then you need to double-click the server (opening the server editor) and add in the username and password for authentication.
Give that a shot and let's see how this goes.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121110#4121110
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4121110
18 years, 5 months
[JBoss Tools (users)] - Re: JBoss 4.3.0 fails to start
by kapilanand
Oh I did not think of looking here before.
There are lot of events in the EventLog in JBoss server view, surprisingly they do not show in the log file.
They all are JMXExceptions:
Message in the first JMXException:
======================
"Could not obtain connection to any of these urls: localhost:1099 and discovery failed with error: javax.naming.CommunicationException: Receive times out [Root exception]"
Then there about 20 more JMXException with the message:
======================================
"jmx not bound"
All the above messages have yellow exclamation icon, but the last one has red-cross icon.
The last message reads:
================
"Failure: Security Exception: Failed to authenticate principal=,securityDomain=jms-console"
The behavior is same for default, all and production configurations, except that all gave another exception that showed up on the console and log file, but that's because deploy-hasingleton directory was missing.
regards
kapil
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121106#4121106
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4121106
18 years, 5 months