server started but Server view still says starting...

[mazz]

Under what conditions is a server considered fully "started".

Using the 2.0.0.alpha1, I created and started a Jboss server.

It started up fine and the console shows me all the normal log messages.

However, the Server view (and JBoss Server View) still says "Starting...", like it doesn't realize the server has fully come up.

[rob.stryker]

This is a known issue, and I'm not entirely sure what's causing it, however the alpha1a release contained another bug which prevented me from getting the needed feedback from users.

Basically, in the JBoss Server View, I've added an "Event Log" to document what's going on during the server startup. This isn't shown in the alpha1a due to a simple boolean error on my part. ;)

The way the server tells whether or not it is up or down is through a utility that comes with JBoss, "twiddle", which querries JMX repeatedly until it says the server is started. It checks whether the jboss.system:type=Server has a Started attribute, and the value of that attribute.

If the server is nowhere near started yet, it'll reply with an exception. (IE JMX not even up yet). If it's getting there, it'll reply Started=false. When the server decides it is done, it'll reply Started=true.

Now I dont know what could be happening for the server to be up, but the twiddle execution failing.

[mazz]

OK, I think that probably answers the question. I don't think the JMX remote adapter service is deployed in my particular server instance.

How would this support such a deployment? I'm assuming if this needs the remote JMX adapter to be deployed, and its not, then it will never know that the server is started. Perhaps you should have a timeout such that after, say, 5 mins or whatever, you flip the state to "Started" and in your log you indicate "timeout before twiddle could determine the state; assuming server is up".

Also, what if the remote adapter is deployed, but its secured such that you need a username/password to connect?

[rob.stryker]

I will probably add a preference / checkbox that allows that server's state to be automatically set to 'started' after the timeout is reached. Thanks for your help.

[mculpepper]

Hey Mazz..

Also, what if the remote adapter is deployed, but its secured such that you need a username/password to connect?

Are you referring to the auto-protection the JBoss installer does? I'm curious if this does more than just password-protect the jmx-console web application. Does it also add an extra layer of security on the protocol itself? (Keep in mind the web-app is just an adapter onto the JMX protocol)

[atomz4peace]

I see the same problem but my server IS running jmx and the manual twiddle command shows the bean at "Started". I'm using Alpha1a.

The funny thing is that this used to work, but I don't know what I changed or added. Any other ideas of what to check?

It also does not compile jsp's right now even though I added tools.jar in the JRE definition (Using the JRE from the JDK)

[rob.stryker]

JSP compilation is not implemented, as far as I understand it.

As for the twiddle execution:

You're using alpha 1a, which came with a boolean bug which stopped the JBoss Server View from showing all of its pieces to the user. If the view WAS showing all of the pieces, it would be able to tell you whether the twiddle execution is failing or not.

In Beta1, there is now a preference page which allows you to say that if the server doesnt officially designate itself as 'started' within some timeout, to either a) cancel the startup (abort), or b) set the server as started anyway.

So in short, in order to actually see what the problem is in the view and its event log, you'll need beta 1, but if you had beta1, you could use the override preference to just set the server as started.

[atomz4peace]

So in short, in order to actually see what the problem is in the view and its event log, you'll need beta 1, but if you had beta1, you could use the override preference to just set the server as started.

Don't suppose you would be able to share a link to beta1, would you? :-)