This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Sometimes, when starting/stopping server actions take a long time, its status is determined incorrectly. We need to implement a better way to determine when the starting/stopping process is actually finished -or- provide a message such as "IDE can't recognize whether server starting/stopping process is finished, so you could use Refresh to update its status"
I am CCing the UI experts to say whether there should be some UI support when the server plugin is not able to obtain the server status.
Still reproducible with Coco 20060320 on WinXP
Jano, can you please comment this problem? Please reassign it back if you think that the issue can be solved somehow.
What is the real problem? If the action takes too long, we should show the hourglass icon until the server status is determined.
The problem is that plugin can't properly determine whether server start/stop process failed. Hence, timeout is used to wait for server to became online.
HG icon is shown...it depends on the particular server plugin how long the timeout is. If the timeout has gone then the IDE expects to be stopped (or at least we do not solve the situation and simply show the 'not-running' icon). When there the server is started (and some according messages are written in to the server output window) then the IDE should show 'running' icon. Here is the problem - when the plugin is not able to recognize the state. The plugin is still waiting until it times out. If I understand correctly mrkam suggests to have some icon indicating the 'uknown' state when the plugin times out. I am defintelly not sure about the issue...let's discuss it. BTW, such a state should be handled as other states, i.e. there should be some API, icon...I am CCing j2eeserver owner. to express his thoughts :)
What are all the possible circumstances when the plugin cannot determine the server status? Please try to list all of them. We need to know the cause to recommend the user how to fix it and provide proper indication. Also, if we don't know the status, how are the actions like Run, Deploy affected? Do they work?
From the user's point of view, server status sometimes can't be determined properly during Start Server process which can occur any time use start, restart server, run or even deploy an application. In this case the whole deployment process can be broken. When the timeout expires plugin decides that server is stopped. Therefore View Admin Console, View Logs, Restart and Stop Server menu items are disabled. If I recall correcty, Run and Deploy actions will still work correctly as the plugin usually refreshs the server status during these operations.
On the other side, sometimes server fails to start quickly. For example, when some port conflict occur or license is expired or anything else. In this case it is not very smart for our IDE to wait for a long-long time. During this time most of operations with server are disabled. User needs to wait cause he/she can't stop server starting process until he/she forces IDE to close.
I meant server starting process quickly fails.
I agree with the original description (proposal) that the server should provide better message (more explanatory and concrete) when starting/stopping times out. There is definitely no need for having some "unknown" server state. This issue should be reassigned to the concrete plug-in. Mrkam, what server did you have trouble with?
ok, I think that I complicated it unnecessarily. The problems are related mostly to the WL plugin, thus I will take care of it.
Well, I agree that this problem exists for WebLogic, and I also experienced it with SJSAS, WebSphere as well. I can't remember anything about JBoss, but I think that the general principles are the same among all the plugins, that's why I was filing it into ui subcomponent.
*** Issue 73924 has been marked as a duplicate of this issue. ***
Fixed for the WL plugin... Checking in Bundle.properties; /cvs/serverplugins/weblogic9/src/org/netbeans/modules/j2ee/weblogic9/optional/Bundle.properties,v <-- Bundle.properties new revision: 1.2.14.1.2.4; previous revision: 1.2.14.1.2.3 done Checking in WLStartServer.java; /cvs/serverplugins/weblogic9/src/org/netbeans/modules/j2ee/weblogic9/optional/WLStartServer.java,v <-- WLStartServer.java new revision: 1.9.6.2.2.2; previous revision: 1.9.6.2.2.1 done ...and for the JBoss plugin Checking in Bundle.properties; /cvs/serverplugins/jboss4/src/org/netbeans/modules/j2ee/jboss4/ide/Bundle.properties,v <-- Bundle.properties new revision: 1.5.8.3.2.5; previous revision: 1.5.8.3.2.4 done Checking in JBLogWriter.java; /cvs/serverplugins/jboss4/src/org/netbeans/modules/j2ee/jboss4/ide/JBLogWriter.java,v <-- JBLogWriter.java new revision: 1.3.42.11; previous revision: 1.3.42.10 done Checking in JBStartRunnable.java; /cvs/serverplugins/jboss4/src/org/netbeans/modules/j2ee/jboss4/ide/Attic/JBStartRunnable.java,v <-- JBStartRunnable.java new revision: 1.1.2.10; previous revision: 1.1.2.9 done Checking in JBStartServer.java; /cvs/serverplugins/jboss4/src/org/netbeans/modules/j2ee/jboss4/ide/JBStartServer.java,v <-- JBStartServer.java new revision: 1.17.8.5.2.13; previous revision: 1.17.8.5.2.12 done Checking in JBStopRunnable.java; /cvs/serverplugins/jboss4/src/org/netbeans/modules/j2ee/jboss4/ide/Attic/JBStopRunnable.java,v <-- JBStopRunnable.java new revision: 1.1.2.6; previous revision: 1.1.2.5 done
Verified