JBoss 4.3.0 fails to start

[kapilanand]

I have tried this with Eclipse3.3.1/JBossTools2.0 and JBossDeveloperStudio1.0

I am able to launch JBoss 4.3.0 from command line using run.sh/run.bat, but it fails to start from within eclipse. Java process just intermittently dies abruptly. Logs do not show any error or exception, neither anything shows up on stderr eclipse is capturing and I could not establish any pattern in this since I tried this multiple times and the process died at different points.

Is there a fix for this? Thanks for the help.

[maxandersen]

I guess you mean JBoss EAP 4.3, right ?

JBoss AS is only at 4.2.

In any case I haven't heard about that before.

Please report in jira with details for us to reproduce.

[kapilanand]

Yes I meant JBoss AS bundled with JBoss EAP 4.3.0

I have opened a jira issue: http://jira.jboss.org/jira/browse/JBIDE-1646

thanks
kapil

[rob.stryker]

kapilanand:

Can you please open the JBoss Server's View and check the "Event Log" portion of view and tell me what is going on in the startup / shutdown section.

Thanks.

[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

[rob.stryker]

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.

[kapilanand]

This worked.

The entry in jmx-console-users.properties was commented.
I uncommented it and specified the same user/pass in the JBoss Server configuration.

JBoss server started correctly, but now stop server does not work. Will figure it out myself.

[maxandersen]

i'm curious, when you installed jboss as 4.3 did it ask for specifying username and password or not ?

and what entry in jmx-console-users.proeprties was commented ? It should just work out of the box so i'm just trying to identify if 4.3 have a bad change or this is just normal since a 4.3 installed by the AS installer is secured by default.

[kapilanand]

I had downloaded the zipped version jboss-eap-4.3.0.GA-1.ep1.8.zip and did not run the installer.

This were the contents of jmx-console-users.properties:
# A sample users.properties file for use with the UsersRolesLoginModule
#admin=admin



I removed the # comment and specified the user(admin) and password (admin) in the eclipse plugin to make it work.

[maxandersen]

ah got it - yes, we need to be able to communicate with the server to verify it is running or not.