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 134382

Summary:	Netbeans hangs if you try to update the wsit config which was deleted outside
Product:	webservices	Reporter:	daniel_manzke <daniel_manzke>
Component:	WSIT	Assignee:	Martin Grebac <mgrebac>
Status:	RESOLVED FIXED
Severity:	blocker
Priority:	P3
Version:	6.x
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:
Attachments:	Threaddump of the hanging IDE

Description daniel_manzke 2008-05-02 10:09:13 UTC

If you have a web service project where you configured your wsit with the help of the gui, you can bring your IDE to 
hang in a never ending loop. For example set the field for MTOM. A wsit config file is created. Now you delete this 
file. (because you want a fresh one or something else) If you now try to remove the selection of MTOM, your IDE tries 
to update your configuration file. Due the fact that this file didn't exists anymore, the update information hangs in a 
loop. Your only chance now is, to kill your IDE process.

I hope the description helps.

Comment 1 Lukas Jungmann 2008-05-02 10:17:52 UTC

you want this to be P2 I guess... (http://qa.netbeans.org/bugzilla/bug_priority_guidelines.html)

Comment 2 Lukas Jungmann 2008-05-02 10:19:59 UTC

btw: any chance you could add a thread dump[1] to this issue, please?

Thanks for the report :)

[1]: http://wiki.netbeans.org/GenerateThreadDump

Comment 3 daniel_manzke 2008-05-03 16:54:03 UTC

Created attachment 61008 [details]
Threaddump of the hanging IDE

Comment 4 daniel_manzke 2008-05-03 16:56:07 UTC

Hi jungi,

no problem for the report. It's my second one for this tool (wuhuuu) and I have to say, that this is a nice tool. I 
will try to support you where I can, if you need more informations or man power.

Best Regards,
Daniel

Comment 5 Martin Grebac 2008-05-30 13:08:59 UTC

You can delete the file from within netbeans. I'd like to fix this, but I'm not aware of any notification mechanism in
xml model that would tell the client (throw specific exception, ...) that something went wrong. Currently it throws
nullpointerexception, which doesn't help.

Comment 6 Martin Grebac 2008-05-30 13:19:24 UTC

I filed http://www.netbeans.org/issues/show_bug.cgi?id=136160 for the xml model. Without that I'm afraid I can't do much
here.

Comment 7 Martin Grebac 2008-05-30 14:09:15 UTC

I actually was able to find a workaround, so fixed in 6.5.