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.
[ BUILD # : RC3 ] [ JDK VERSION : 1.6.* ] See attachment. I'm afraid I have to delete cache. Is there any other way by partially deleting the cache to avoid Issue 166800 (> 2 hours to wait for new project scan) today?
Created attachment 83794 [details] No debug anymore
Can not comment in issue #166800. This does not seem to be about caches. If translate.google.com is correct, the error says: "A file can not be created if it already exists". It seems like the previous debug session was to fully terminated and the shared memory is still somehow in use. Not sure we can do anything about this. Please try to close NetBeans, kill all Java processes and try again...
Did that solve the problem? I've found issue #148490, which already describes this problem. This is a duplicate. *** This issue has been marked as a duplicate of 148490 ***
Very much thanks for quick help. Indeed restarting NetBeans helped. For the offhand user it seems, *NetBeans fails* because of wrong data in cache. In assumption of this, it's a P1, because there is no hint, no help, what to do. Offhand user maybe doesn't know about existence of cache, he just can't debug anymore. It's a P2 as long, as there is no hint, where the problem is located (e.g. previous debug session was to fully terminated and the shared memory is still somehow in use), so user doesn't guess by himself, that simple restart could help. - the message seems like wrong data in cache (here: ..\cache\executor-snippets\...). - experienced user knows, that cache will not be cleared by restart, so why should it help? - *missing name* of already-existing-file maybe would give better hint to the user.
In the error output in the attached screenshot I do not see anything that would suggest that caches are involved. I understand that the error message "A file can not be created if it already exists" does not say much, but that's out of scope for NetBeans. This message is provided by JVM. If it should be improved, it should be improved there. Restart of NetBeans probably interrupted the shared memory connection with the staled debugger session and therefore released the shared memory. - That's my guess.
> .. I do not see anything that would suggest that caches are involved. From error output user can guess about 2 possible problems: - erroneously already existing file, but nobody knows which and where (Couldn't NB detail this?) - erroneous xml script "...junit-debug.xml", which is undoubtedly located in *cache*. Couldn't you say: " ... possibly caused by JDK bug (not released shared memory). Closing NetBeans and killing all JVM instances should help)
verified duplicate