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.
For some reason, when I run my test app under JNLP, and exit, the log file says Settings saving timeout! List of pending locks: Windows2Local/Modes/properties.wsmode Windows2Local/Modes/leftSlidingSide.wsmode loaders.ser Windows2Local/Components/PROPERTIES.settings Windows2Local/Modes/explorer.wsmode Windows2Local/Modes/editor.wsmode Windows2Local/Modes/bottomSlidingSide.wsmode Windows2Local/Modes/properties/properties.wstcref Windows2Local/WindowManager.wswmgr Windows2Local/Modes/rightSlidingSide.wsmode Windows2Local/Components/properties.settings which does not happen under normal running mode.
I have no idea what is wrong, either something in core/settings or in filesystems. E.g. CCing Radek, as this issue will anyway end up assigned to him.
Which JDK? According to Marek, there is a bug in FileEntityResolver. It does not close inputstream and this is causing problems on jdk 1.6.
I do not have enough info to be sure if it is the same problem as issue #63254. No exceptions from StreamPool in log? As #63254 was fixed on Sep 13 you can try now if it still happens or not.
Again there is not enough info to proceed further with this issue. Please either check if it still happens (is it dupl of issue #63254 which happens only on latest builds of JDK 1.6.0). If it still happens please provide me with test to reproduce. Otherwise I will close it.
Not fixed, still happening. E.g. I just made the FeedReader app from Samples template and ran in JNLP mode (under JDK 1.5). Will attach log file.
Created attachment 25012 [details] My ~/.feedreader/var/log/messages.log
It is not duplicate of #63254.
Radek, can you please shed a light to the reasons why these locks can be pending? Is there any option to enable better logging?
Can other people reproduce, or is it just me?
I ran into this problem once AFAIK but I'm not able to reproduce. Definitely I have no ide what could be the cause for it.
Still reproducible for me.
Lukas says this may be related to a NbURLStreamHandlerFactory problem, recently worked around in the trunk by jtulach. I have not yet tried to confirm this.
Well I am unable to reproduce in a recent dev build even before Yarda's patch.