[ http://jira.jboss.com/jira/browse/JBIDE-1891?page=comments#action_12404678 ] Rob Stryker commented on JBIDE-1891: ------------------------------------ I must have missed this issue. Can you elaborate on if this is still occurring in the 2.0.1 release? Once the process is terminated, the server state should automatically switch to "stopped". If this is not happening, please respond. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1891?page=comments#action_12404761 ] Gene Gretter commented on JBIDE-1891: ------------------------------------- This is still a problem in the 2.0.1 release. The issue is not with the server state. The problem is that the JBoss process is ungracefully blown away before shutdown is called. When shutdown is called, then the error "Could not obtain connection to any of these urls: localhost:1099" is returned because there is no longer a JBoss process to connect to. With the suggest fix mentioned above, the JBoss process shuts down in a orderly fashion after shutdown has been called and the server state correctly switches to 'Stopped'. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1891?page=comments#action_12404891 ] Gene Gretter commented on JBIDE-1891: ------------------------------------- For me, this problem happens everytime I stop the JBoss server by right-clicking the server in the Server View and selecting Stop, which is not at all helpful for you. I have stepped through the code to get a better understanding of what may be causing this problem, so maybe I can describe what I am seeing and it will help you to understand the cause. Above I had mentioned that commenting out pollServer(IServerStatePoller.SERVER_DOWN); in the JBossServerBehavior.serverStopping() seemed to fix the problem. I added back in this line of code so that I could locate the statement that causes the JBoss process to be blown away. The problem seems to start in the pollServer() method on the last statement, which is a call to pollThread.start(). This causes the PollThread.run() method to be executed. The last statement in the run() method is a call to alertBehavior(). The code drops through to the last 'else' statement in alertBehavior(), which is a call to behavior.forceStop(false). Executing this statement causes the JBoss process to be blown away. I appears that another process is started to execute the shutdown code. What I am seeing is that the JBoss process is already gone by the time the shutdown attempts to stop JBoss. This results in the error I mentioned above. I am wondering why another PollThread is started in pollServer when the JBoss server is being shut down? I made the following code change at the end of the pollServer() method that also seems to solve the problem I see: if ( expectedState != IServerStatePoller.SERVER_DOWN ) { this.pollThread = new PollThread("Server Poller", expectedState, this); pollThread.start(); } Hope that helps. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1891?page=comments#action_12405119 ] Gene Gretter commented on JBIDE-1891: ------------------------------------- The problem is related to 2. The Stop Timeout value is set to zero. I did remember setting this value to zero, so I started over with a fresh copy of Eclipse and new JBoss Tools plugin install. I found that the Start Timeout and Stop Timeout values both where set to 450. I then tried to start JBoss and received the error "Server JBoss 4.2 Server Failed to Start". I have seen this error before and found that setting Preferences -> Server: Server Timeout Delay to Unlimited solves the problem. After making this change I was able to start JBoss. I then tried to stop JBoss and received the error "Could not obtain connection to any of these urls: localhost:1099". I checked the Stop Timeout value and found it was now set to zero. Apparently, switch Server Timeout Delay has the side-effect of setting Start Timeout and Stop Timeout to zero. I changed Stop Timeout to 100 and then I was able to stop JBoss without receiving an error. Some observations: I am only able to start JBoss if Server Timeout Delay is set to Unlimited. The values Normal, Long, and Longer do not solve the start problem. The odd thing is that the start failure happens immediately so it does not really appear to be a timeout issue. It appears that the value of Server Timeout Delay determines the maximum value for Start Timeout and Stop Timeout. This relationship is not obvious. When Server Timeout Delay is set to Unlimited, the values displayed for Start Timeout and Stop Timeout is always zero. As I mentioned above, I set Stop Timeout to 100, but it is displayed as zero. If you switch Server Timeout Delay to another value, such as Longer, then the value 100 is displayed for Stop Timeout. There seems to be a few problems here: Unable to start JBoss using the default values for Server Timeout Delay, Start Timeout, and Stop Timeout. Changing Server Timeout Delay to Unlimited also changes Start Timeout and Stop Timeout to zero. When Server Timeout Delay is set to Unlimited, Start Timeout and Stop Timeout are always displayed as zero even though the effective value is greater than zero. Thanks for your help in diagnosing this problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1891?page=comments#action_12406044 ] Rob Stryker commented on JBIDE-1891: ------------------------------------ Gene: Thanks for all the help. It's obvious that when you first discovered the bug, you had your workspace using the "unlimited" timeout, which my poller was not prepared for. It saw a value near zero and gave up very quickly polling, claiming failure. The only part that really confuses me so far is that, even after starting a new workspace, your server still failed to start properly. Obviously that is why you switched to "unlimited", but the ultimate question is why did it fail at all? 450 seconds should be plenty of time for any server to start up really. The only thing I can think of is that your server does not have the JMX console enabled. In JBoss Tools and JBDS, the suggested method of starting a server that does not have JMX is *not* to switch to unlimited timeout. This will, unfortunately, leave a background thread continually trying to connect via JMX to the server, which does not have JMX enabled. The suggested method to remedy this is in window -> preferences -> JBoss Tools -> JBoss Servers, select your server, and switch your startup poller to "Timeout Poller". This will do *no* polling at all (save your machine trouble) and will only set the server state to "Started" after your startup timeout is reached. To be fair, there *is* still a bug with my pollers not recognizing a timeout less than zero means unlimited, and I thank you for discovering that. But if the poller is failing to recognize your server's startup, the approved course of action is to switch your startup poller to a timeout poller with an approximate timeout as to how long you think it normally takes to start up. Get back to me and let me know if that's helped you at all. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1891?page=comments#action_12406943 ] Rob Stryker commented on JBIDE-1891: ------------------------------------ Can you open the jboss server's view and select your server, then expand the "event log" to see what's going on there? That might provide some info. (Sadly, there's no easy way to copy the event log. I'll need to add that as a feature soon.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1891?page=all ] Rob Stryker updated JBIDE-1891: ------------------------------- Fix Version/s: 2.2.x (was: 2.1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1891?page=comments#action_12407199 ] Rob Stryker commented on JBIDE-1891: ------------------------------------ You should double-click on your server object to open the server editor. There, you'll have an opportunity to set a username and password to ones accepted by your server. Basically, it seems your username and passwords are incorrect ;) It's receiving your username "admin" and is most likely receiving the password as well, however it's refusing to authenticate. As an exercise, from outside eclipse, start up your eclipse, and then from another terminal, navigate to your bin folder and type: ./twiddle.sh -s localhost:1099 -a jmx/rmi/RMIAdaptor -u admin -p admin get jboss.system:type=Server Started Then make sure that is the same username / password combination stored in the server editor inside eclipse. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1891?page=all ] Snjezana Peco updated JBIDE-1891: --------------------------------- Attachment: jbide-1891.txt -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1891?page=comments#action_12407441 ] Gene Gretter commented on JBIDE-1891: ------------------------------------- The cause for the JBoss startup problem seems to be related to adding -b <IP-address> to the launch configuration for the JBoss server. Maybe a bad habit on my part, but I have a need to specify a specific IP address when starting the 'all' configuration so I tend to do the same for other configurations as well. I was able to reproduce the problem using twiddle. If I start JBoss using a b-option, then I receive a SecurityException unless I specify -s <IP-address>:8080 when calling twiddle. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1891?page=comments#action_12409915 ] Rob Stryker commented on JBIDE-1891: ------------------------------------ Gene: I've made some patches to the getHost() portion of startup and shutdown. Hopefully this will fix your most recent problem. I was wondering if you'd be good enough to test in the next day or two to see if this solves your whole problem or not. I realize this jira got a little convoluted and explored many issues. Thanks again. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1891?page=comments#action_12410118 ] Rob Stryker commented on JBIDE-1891: ------------------------------------ sure does. thanks. leaving issue opened until modifying the "host" also modifies the launch configuration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira