I've only ever seen that error before if you try to start the server twice in a row, or try to terminate it while it's starting.
Looking at the code, the only way for there to be a null pointer there is if the directory being added to the classpath either does not exist (unlikely) or the permsisions dont allow us to access it. File libs[] = libDir.listFiles(someFilter); If there were no acceptable children, it would be of size zero, instead of null. It also seems that the error is occurring only where the server is trying to verify whether the server is up or down, as opposed to when actually starting or stopping the server. So does the server start or stop normally? Either way, this is entirely rewritten in HEAD and the errors should not exist, but that's no consolation to you who then needs to wait for beta 3 ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986331#3986331 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986331 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
