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 ;)
if I start the server in the command line without the help of eclipse it starts and stops normally. If I start jboss outof eclipse the progressbar displays "Starting ..." but never changes to "Started". So it seems that the verification of the server state is the problem.
But maybe it is a problem with the permission. I work on a linux-system and had a lot of trouble with the permissions in the jboss directory "server". Could you tell me which directories should be accessable.
I have found some more detailed informations to my problem. The described behaviour rises if I choose an JBoss AS 3.2 Server as server type. If I choose JBoss v3.2.3 everything works fine. Does anybody has an explanation for this?