I have the same problem. (A workaround is to wait long enough, then the Jboss tools in Eclipse will time out and set the server to started. It does about 220 checks before timing out :-) ) To check what would work with Twiddle I used the "Twiddle Server" in the Jboss Servier View (right click on the server in the lower half of the window, as opposed to same server in the upper half of the windows. Why the difference?). The command I executed in the Twiddle Server window, when the server is started is: -s MyHost:1099 -a jmx/rmi/RMIAdaptor -u MyUser -p MyPassword get jboss.system:type=Server Started The returned answer is: Started=true This is what we want, right? (If I leave out the -u and -p I get a SecurityException which I guess tells me that my server is password protected.) If I then add -S -s MyHost:1099 -a jmx/rmi/RMIAdaptor -u MyUser -p MyPassword to the Twiddle Args in the Edit Launch Configuration then nothing new happens. It seems that it is not picked up by the tool checking the server? The twiddle.log file shows that the arguments I put in are not used. From the top of the twiddle.log file; 13:08:36,406 DEBUG [Twiddle] args[0]=-s | 13:08:36,406 DEBUG [Twiddle] args[1]=MyHost:1099 | 13:08:36,406 DEBUG [Twiddle] args[2]=-a | 13:08:36,406 DEBUG [Twiddle] args[3]=jmx/rmi/RMIAdaptor | 13:08:36,406 DEBUG [Twiddle] args[4]=get | 13:08:36,406 DEBUG [Twiddle] args[5]=jboss.system:type=Server | 13:08:36,406 DEBUG [Twiddle] args[6]=Started | 13:08:36,406 DEBUG [Twiddle] Command name: get | 13:08:36,421 DEBUG [Twiddle] Command arguments: jboss.system:type=Server,Started | ... What am I doing wrong? Thanks! Best Regards, Claus View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990425#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...