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 196109 - Can not get rid of "IDE needs to reconnect..." notification
Summary: Can not get rid of "IDE needs to reconnect..." notification
Status: NEW
Alias: None
Product: cnd
Classification: Unclassified
Component: Remote (show other bugs)
Version: 7.0
Hardware: PC All
: P3 normal (vote)
Assignee: Vladimir Kvashin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-28 15:43 UTC by Alexander Pepin
Modified: 2016-12-07 13:30 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Pepin 2011-02-28 15:43:28 UTC
Steps to reproduce:
- create a project
- add a remote host
- set that host for the project
- restart IDE, notification "IDE needs to reconnect..." 
- add another host and set it for the project
- remove "old" remote host
Result: Notification "IDE needs to reconnect..." does not disappear.
Comment 1 Vladimir Kvashin 2011-03-01 15:00:06 UTC
As I understand, you wait until parsing is finished before restarting IDE, right?

Then I guess (although I'm not quite sure) this is because of tool chain validation
Comment 2 Vladimir Kvashin 2011-03-02 05:51:23 UTC
To remove a notification, press "close" (a cross sign at upper right corner of the notification balloon)

After a discussion we agreed with submitter to consider this issue is about not removing notifications for host that has just been removed.
Comment 3 Alexander Pepin 2011-09-16 13:51:15 UTC
Another scenario:
- add a remote build host
- create a full remote project on that host
- open some files from that project
- close the project
- remove the host
Result: "IDE needs to reconnect to the host" notification appears.

IMO the notification seems to be misleading and very annoying.
Comment 4 Leonid Lenyashin 2012-10-30 21:09:36 UTC
There was no activity on this issue for quite a long time. We apologize that the issue was not addressed so far due to lack of development resources. We might not have time in near future to fix this problem, so it is closed as WONTFIX.
If the issue is still critical for you please do not hesitate to REOPEN it.
Thank you for using our product and reporting bugs. We are really sorry that we were not able to fix this issue timely.

Regards,
CND team.
Comment 5 necktwi 2016-06-12 05:47:43 UTC
Please give me some leads to fix this issue. Its very annoying.
Comment 6 Vladimir Kvashin 2016-07-20 20:48:59 UTC
That's funny. It seems thatthe stack that leads to this is as follows:

"Connection and R/W change :: ATTR_CHANGED /home/vkvashin/NetBeansProjects/atoi/atoi.c"
	at org.netbeans.modules.remote.impl.fs.ui.ConnectionNotifierDelegate.showIfNeed(ConnectionNotifierDelegate.java:164)
	at org.netbeans.modules.remote.impl.fs.ui.ConnectionNotifierDelegate.addTask(ConnectionNotifierDelegate.java:115)
	at org.netbeans.modules.remote.impl.fs.ui.ConnectionNotifierImpl.addTask(ConnectionNotifierImpl.java:59)
	at org.netbeans.modules.remote.api.ConnectionNotifier.addTask(ConnectionNotifier.java:104)
	at org.netbeans.modules.remote.impl.fs.RemoteFileSystem$RemoteFileSupport.addPendingFile(RemoteFileSystem.java:1253)
	at org.netbeans.modules.remote.impl.fs.RemoteFileSystem.addReadOnlyConnectNotification(RemoteFileSystem.java:816)
	at org.netbeans.modules.remote.impl.fs.RemoteFileObjectBase.canWriteImpl(RemoteFileObjectBase.java:508)
	at org.netbeans.modules.remote.impl.fs.RemoteFileObjectBase.canWrite(RemoteFileObjectBase.java:486)
	at org.netbeans.modules.remote.impl.fs.RemoteFileObject.canWrite(RemoteFileObject.java:470)
	at org.netbeans.modules.editor.lib2.highlighting.ReadOnlyFilesHighlighting.fileAttributeChanged(ReadOnlyFilesHighlighting.java:185)
	at sun.reflect.GeneratedMethodAccessor14.invoke
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.openide.util.WeakListenerImpl$ProxyListener.invoke(WeakListenerImpl.java:487)
	at com.sun.proxy.$Proxy1.fileAttributeChanged
	at org.openide.filesystems.FCLSupport$DispatchEventWrapper.dispatchEventImpl(FCLSupport.java:187)
	at org.openide.filesystems.FCLSupport$DispatchEventWrapperSingle.dispatchAllEventsSync(FCLSupport.java:224)
	at org.openide.filesystems.FCLSupport$DispatchEventWrapper.dispatchEvent(FCLSupport.java:137)
	at org.openide.filesystems.FCLSupport.dispatchEvent(FCLSupport.java:105)
	at org.openide.filesystems.FileObject$ED.dispatch(FileObject.java:1398)
	at org.openide.filesystems.FileSystem$EventDispatcher.run(FileSystem.java:795)
	at org.openide.filesystems.EventControl.dispatchEvent(EventControl.java:84)
	at org.openide.filesystems.FileSystem.dispatchEvent(FileSystem.java:554)
	at org.openide.filesystems.FileObject.dispatchEvent(FileObject.java:644)
	at org.openide.filesystems.FileObject.fireFileAttributeChangedEvent(FileObject.java:628)
	at org.netbeans.modules.remote.impl.fs.RemoteFileObject.fireFileAttributeChangedEvent(RemoteFileObject.java:185)
	at org.netbeans.modules.remote.impl.fs.RemoteFileObjectBase.fireFileAttributeChangedEvent(RemoteFileObjectBase.java:144)
	at org.netbeans.modules.remote.impl.fs.RemoteFileObjectBase.fireFileAttributeChangedEvent(RemoteFileObjectBase.java:478)
	at org.netbeans.modules.remote.impl.fs.RemoteFileObjectBase.fireReadOnlyChangedEvent(RemoteFileObjectBase.java:472)
	at org.netbeans.modules.remote.impl.fs.RemoteFileObjectBase.connectionChanged(RemoteFileObjectBase.java:467)
	at org.netbeans.modules.remote.impl.fs.RemoteFileSystem$ConnectionChangeRunnable.run(RemoteFileSystem.java:306)
	at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1443)
	at org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:68)
	at org.openide.util.lookup.Lookups.executeWith(Lookups.java:303)
	at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2058)