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.
|Summary:||startup cannot be cancelled, IDE's attempts to start server cannot be cancelled either|
|Product:||serverplugins||Reporter:||Petr Dvorak <joshis>|
|Component:||Code||Assignee:||Petr Hejl <phejl>|
|Issue Type:||ENHANCEMENT||Exception Reporter:|
Description Petr Dvorak 2008-08-04 12:49:14 UTC
NB: 200808040201 OS: Ubuntu 8.04 JDK: 1.6.0_10 JBoss: 5.0.0.CR1 I have tried to start a JBoss 5. However, a lot of OutOfMemory exceptions popped out during the startup. So I wanted to stop the JBoss server, but there is no gui for this in IDE. "Stop" button is disabled during the startup. For the second time, I tried to set -Xmx=512m parameter (I admit I had no idea what I was doing...) and I started the server again. I got an error message about incompatible minimum and maximum heap size (ok, no problem with this..), but the process was not stopped, a progress bar in the lower right corner was still there saying "Starting Jboss Application Server", icon in the Servers view was indicating that something was happening (though it was not), I was unable to cancel this in IDE... This issue is very annoying. If I cannot start the Jboss in NB, I should be able to kill it from the IDE at least.
Comment 1 Petr Dvorak 2008-08-04 13:01:02 UTC
> You must run NetBeans on JDK 1.5 when testing JBoss 5 Sorry for that. I will try again with JDK 5 and will let you know...
Comment 2 Petr Dvorak 2008-08-04 13:02:08 UTC
No, still the same problems with JDK 1.5.0_15...
Comment 3 Petr Hejl 2008-08-11 19:25:04 UTC
Startup should be already fixed - issue 139628.
Comment 4 Petr Dvorak 2008-08-12 09:49:42 UTC
Yes, I see... However this issue is also more general - it is about the fact that you cannot stop server's startup (and therefore you are sometimes doomed to waiting for ages till the server starts).
Comment 5 Petr Hejl 2008-08-12 09:58:47 UTC
Then its probably not jboss specific. It's hard to anything during the startup because the IDE does not have any control over the startup script - it usually start some daemon processes etc. As no real user reported this, I'm thinking about enhancement issue type.
Comment 6 Petr Dvorak 2008-08-12 10:02:13 UTC
I agree - changing to ENHANCEMENT. You are right that this holds for other servers too (I tested with Glassfish)...