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.
Found in FFJEE, apparently in db module. I had just clicked on the Pointbase server node in the Runtime tab and selected Connect. Probably no server was running, so it was OK for it to fail. I may have tried to expand the Pointbase connection node too. But the entire IDE hung. See thread dump. IMO Children.Array.initCollection may never block, e.g. waiting for a network connection. The connection should be made asynchronously, and subnodes added when they are available.
Created attachment 5561 [details] Thread dump of deadlock
Sorry: Orion EE build from today's sources. After a few minutes the IDE recovered with an error dialog: Unable to connect, cannot establish ..... (SQL-server rejected .....) and then all was well. But if I had not been busy filing a bug, I would have killed the IDE with kill -9 long before this.
This problem can occur in some special situations (e.g. overloaded network, db server is not running) when the JDBC driver is waiting for response for its connect request. Usually the response is quite quick and the connection or possible error message don't hang the IDE. I wasn't able to reproduce Jesse's a few minutes delay. On Win2000 I got the response till 1 second, on Linux I got the response at worst till 3 seconds. It is risky to fix it because the bugfix requires bigger changes in the code and it can probably affect the rest of the module. Requesting waiver for FFJ 4.0.
I tested this issue a little bit and have done these observation: If there is no running server on defined port, you get error message really quickly (as Radko wrote). The problem is, when on defined port is anything listening. It could be stupid socket server, which does nothing, only accept connections. Then there is a huge timeout interval.
Hmm, I definitely did not have some dummy server running. I simply started EE after building from source and tried to use it.
Set target milestone to TBD
Request for 3.4 waiver. For more info see the comments above.
Docs approves waiver. Leaving Patrick's name on cc for his records.
I agree with the waiver
Request for S1S41 waiver. For more info see the comments above.
Requires bigger and more complex changes in the module. Will be fixed as a part of the task #28199.
Please don't use RESOLVED LATER, keep the bug open so that it doesn't get out of focus.
*** Issue 32553 has been marked as a duplicate of this issue. ***
Dup of bug that is marked 'resolve later'? Apparent UI bug that *can* be fixed. It is meant as a way how live without third waiver in a row? Quite simple to reproduce: use wrong url for new connection to database and if it has long timeout you've got serious trouble in 'New Database Connection ...' dialog when you press OK. What is even worse you have the same problem when you try to switch to Advanced tab in the same dialog but there is no way how to find that IDE tries to connect to database imediately. Please remember that many users are not big wizards so they sometimes try to use wrong parameters.
I think it is not hard to find that this issue depends on task #28199 which is marked as STARTED and target milestone is 4.0. It is obvious from the comments in these issues why it was marked "resolve later".
If you don't plan to implement this to S1S5, why doesn't it have S1S5_WAV keyword ?
Priority decreased to P3, approved by QA. The bugfix is in progress but it is not planned for 3.5. Part of this fix is also redesign of the connect dialog which should better inform the user about the progress (task #32603).
Is this something that needs to be release noted (for either NetBeans or S1S)? If so, is this text appropriate?: "The IDE might freeze when using the Database Explorer to connect to a database under some circumstances, such as network overload, slow response from the database server, or retrieval of a large amount of data."
In my opinion it is not necessary to release noted it. This problem is caused by the module design so it was in the module from the beginning. It appears very rarely and that's why it wasn't reported for long time.
I think that it should be be release noted, taking it into account user can avoid it. Otherwise it is unpleasant surprise. Sorry Radko.
OK, I agree with the proposed text.
Hopefully fixed as part of #28199 changes.
VERIFIED
removing RELNOTE keyword