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 101584 - Not all installed IDE able to start.
Summary: Not all installed IDE able to start.
Status: RESOLVED WORKSFORME
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Nitya Doraisamy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-18 14:37 UTC by Michael Nazarov
Modified: 2007-10-12 21:45 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
screenshot (5.92 KB, image/png)
2007-04-18 14:37 UTC, Michael Nazarov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Nazarov 2007-04-18 14:37:19 UTC
I've installed six different daily bundles from basic to full (apr 17 and apr 18
ones). Possible same situation will come with installing only full bundles.

There are two items in start menu and so I tried to start two IDEs. IDE from Apr
18 started well. IDE from Apr 17 reported invalid file from GF installation.
After exiting running IDE other one starts without any troubles.

See attach for error message.
Comment 1 Michael Nazarov 2007-04-18 14:37:51 UTC
Created attachment 41164 [details]
screenshot
Comment 2 Kirill Sorokin 2007-04-18 15:13:31 UTC
So you had one IDE running and started another one? And once started in parallel
it complained about GF? At the same time if it was started alone it could start
successfully? 

Looks like a userdir conflict.
Comment 3 Michael Nazarov 2007-04-18 15:17:56 UTC
Yes. Second IDE report about GF files corruption and failed to start.
Comment 4 Kirill Sorokin 2007-04-18 15:21:40 UTC
Reassigning to the IDE or evaluation. The root cause of this behavior is the
same as in issue 101336.
Comment 5 Peter Pis 2007-04-22 16:48:23 UTC
Reassigning to "core" for evaluation...
Comment 6 Marian Mirilovic 2007-04-22 21:54:00 UTC
I am not sure about the glassfish, but we have a check on startup of the IDE -
so it mustn't start if you are running with the same userdir. (if it was running
with same userdir, please reassign back to core and rise priority - hence this
is regression) 
If you are running second IDE with different userdir - from IDE's point of view
it's ok, this is a glassfish bug.

BTW: for future, it would be much better to attach log file from the IDE instead
of screenshot http://qa.netbeans.org/bugzilla/reportbug.html
+ please use priority based on our guidelines
http://qa.netbeans.org/bugzilla/bug_priority_guidelines.html
Comment 7 Kirill Sorokin 2007-04-23 05:36:15 UTC
Marian, I don't know why, but your comment led me to the idea that issue 89655
might be related. In fact the two IDEs would be "sharing" ~/.netbeans-derby and
that could be causing problems. Just my 2 cents.
Comment 8 Peter Pis 2007-06-08 13:45:55 UTC
Can this issue be closed as a DUP of #89655?
Comment 9 Michael Nazarov 2007-06-08 13:50:03 UTC
I don't think so...
Tricky issue about configuration file(s) and really unusable IDE are slightly
different things.
Comment 10 Peter Pis 2007-06-11 09:28:57 UTC
But "ide" is not the right place for it then. Reassigning back to core for
evaluation.
Comment 11 Antonin Nebuzelsky 2007-09-14 13:10:58 UTC
Not a "core" issue. Reassigning to j2ee.
Comment 12 Nitya Doraisamy 2007-10-12 21:45:12 UTC
I installed two full builds 200710120000 & 200710100000. Second installer recognizes presence of previosly installed
GlassFish and points to it.
Started IDE 200710120000 via Desktop shortcut. Came up successfully.
- Started IDE 200710100000 via Desktop shortcut. Just brings into focus the running IDE from before. I guess this is
because the userdir's are the same.
- Started IDE 200710100000 by providing a new userdir. IDE started successfully.

GlassFish server present under both IDE's Services node and was able to successfully administer the server from both IDE's.

Closing as WorksForMe. Please reopen if you see this issue again.