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.

Bug 73136 - Provide Terminate action for Start Server process
Summary: Provide Terminate action for Start Server process
Status: RESOLVED DUPLICATE of bug 80490
Alias: None
Product: serverplugins
Classification: Unclassified
Component: WebLogic (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Libor Kotouc
URL:
Keywords:
Depends on: 80490
Blocks:
  Show dependency tree
 
Reported: 2006-03-01 15:38 UTC by Alexander Kouznetsov
Modified: 2011-03-23 10:30 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kouznetsov 2006-03-01 15:38:03 UTC
Reproduced with JSE 8.1, 2006.02.25

Once I've tried to start WebLogic using plugin, but some problems cause WebLogic
to cancel the startup. But the plugin didn't recognize the situation and was
waiting for the server to Start Up. Unfortunately, all the plugin menu items are
disabled, so there is no possibility to cancel the process unless you shut down
the IDE. So the Starting Process was hovering for more than 10 minutes and I had
to shut down the IDE.
Comment 1 Libor Kotouc 2006-03-01 16:13:16 UTC
Please try with NetBeans 5.0 or later and reopen if you can reproduce. In that
case please provide the steps which lead to the problem.
Comment 2 Alexander Kouznetsov 2006-07-12 16:50:18 UTC
Use evaluation copy of WebLogic when its period is expired.
Comment 3 Petr Jiricka 2006-07-12 17:52:49 UTC
JSE 8.1 issue, not reproducible with NetBeans 5.5 -> adding the NO55 keyword.
Comment 4 Alexander Kouznetsov 2006-07-13 08:30:53 UTC
Could please give me additional details on which build have you used to try to reproduce this issue.
Comment 5 Libor Kotouc 2006-07-13 09:25:41 UTC
This issue is duplicate of the issue 67170.

The important thing is that the problem seems to be caused in the WL server, see
the thread dump attached to the original issue. The NB call ends up waiting on
some lock in the WL code.

I have not seen the problem quite a long time. I would appreciate if you
reproduce it in NB5.5 build with WL9.1 and attach the thread dump of the IDE and
of the WL server. Thanks.

*** This issue has been marked as a duplicate of 67170 ***
Comment 6 Alexander Kouznetsov 2006-07-13 09:38:31 UTC
I disagree. This issue describes the situation when WebLogic is not started due to its problems. In issue 67170 - it is started and there is a problem for the plugin to recognize it. Therefore this issue can't be a duplicate of issue 67170. Moreover when WebLogic is failed to start there is no exception from NetBeans at all - it seems to be waiting forewer.
Comment 7 Libor Kotouc 2006-07-13 09:59:23 UTC
I don't understand the issue then. Please describe better what's going on,
especially what is started or not and what is recognized or what is not.

We don't have any piece of code which would lead to "some problems cause WebLogic
to cancel the startup". What does it mean? I thought that it means that WL is
started but IDE does not recognize it.
If it means that WL is really cancelled (from whatever reason, e.g. by a user)
then IDE is waiting some time (I am not sure about the exact numbers) and then
expects that the server is not running. IDE cannot recognize that the server was
cancelled and then automatically cancel the running startup process.
Then behavior is correct and intentional.

If you are missing 'Terminate' action, please file another (enhancement) issue.
Comment 8 Petr Jiricka 2006-07-13 20:12:25 UTC
Looks like I was wrong when I wrote that this does not apply to NB 5.5, removing
NO55 keyword.
Comment 9 Alexander Kouznetsov 2006-07-18 09:37:06 UTC
Sorry for ambiguity. The problem is, in fact, that timeout is too big and you can't force plugin to stop waiting.

So the scenario is:
1. Plugin tries to start server
2. Server fails to start due to its reasons (expired licence, for example)
3. Plugin doesn't recognize that it is not starting any more and waits for it indefinitely (timeout probably is too big to feel it not to be indefinitely). It is usually clear from logs is server still starting or not.
4. Plugin doesn't allow user to stop waiting.

IMO, Terminate action would be reasonable. And there is no need to enter a new issue. Since this is the one.
Comment 10 Libor Kotouc 2006-07-18 15:47:41 UTC
I filed new enhancement for the general Cancel action, see the issue 80490. Then
the server plugins will be able to implement the cancelling on their side.
Comment 11 Jiri Prox 2007-09-17 21:37:45 UTC
Obsolete milestone, please reevaluate
Comment 12 Petr Hejl 2011-03-23 10:30:43 UTC

*** This bug has been marked as a duplicate of bug 80490 ***