[ https://issues.jboss.org/browse/JBIDE-22471?page=com.atlassian.jira.plugi... ] Dmitry Bocharov edited comment on JBIDE-22471 at 8/8/16 9:03 AM: ----------------------------------------------------------------- Shortly about the bug: All OS connections in OS Explorer view a stored in CustomHashtable elementMap (see org.eclipse.jface.viewers.StructuredViewer class). We add connection there when the view is being opened (for example on eclipse startup). At that moment connection to the remote server is not established yet. And, say, hash1 is generated when adding to map. After we provide the token and want to expand the connection UI element, the real connection to the remote server almost always has already bee established and ANOTHER hash2 was generated. That's why connection wasn't just found in the view. This bug is more about the way how java counts hashCode for URL objects. The thing is that it tries to resolve ip address and connect to the URL. You can find lots of posts complaining on that theme in the internet. Most relative are: 1) http://bugs.java.com/view_bug.do?bug_id=6810437 2) http://brian.pontarelli.com/2006/12/05/mr-gosling-why-did-you-make-url-eq... So counting hashCode of String representation of URL and not of the URL object really solves the problem. was (Author: dbocharov): Shortly about the bug: All OS connections in OS Explorer view a stored in CustomHashtable elementMap (see org.eclipse.jface.viewers.StructuredViewer class). We add connection there when the view is being opened (for example on eclipse startup). At that moment connection to the remote server is not established yet. And, say, hash1 is generated when adding to map. After we provide the token and want to expand the connection UI element, the real connection to the remote server almost always has already bee established and ANOTHER hash2 was generated. That's why connection wasn't just found in the view. This bug is more about the way how java counts hashCode for URL objects. The thing is that it tries to resolve ip address and connect to the URL. You can find lots of posts complaining on that theme in the internet. Most relative are: 1) http://bugs.java.com/view_bug.do?bug_id=6810437 2) http://brian.pontarelli.com/2006/12/05/mr-gosling-why-did-you-make-url-eq... So counting hashCode of String representation of URL and of the URL object really solves the problem. -- This message was sent by Atlassian JIRA (v6.4.11#64026)