When the server is first starting, typically there is no connection at all from JNDI
because the server hasn't even started JNDI yet. This is why you get the
javax.naming.CommunicationException:
A few seconds later, JNDI is bound, but JMX is not. JNDI responds to the request, and the
request responds that, javax.naming.NameNotFoundException: jmx not bound
To be clear, these are not failures. This is the expected flow as the server starts up.
After a while, JMX is bound, and I get the Server mbean and ask if the server is started
yet. At first, the response is no.... the server has not completed starting. When the
server is completely started, however, the poller responds that the server is started, and
the server's state switches to "Started" instead of "Starting".
To be clear, is your complain that these status errors are logged? You havent' said
whether or not there's a problem in the view. This is not a bug unless the
server's view is not updating the server's status when the server is completely
started.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226852#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...