Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

plugin causing "Remote System Explorer Operation" that lock up Eclipse #2

Open
GoogleCodeExporter opened this issue Jul 15, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
Unsure, happens after having Eclipse open for a while and doing normal
edits.  Doesn't seem to matter what is being edited.  Doesn't have to be a JPA 
entity.

What is the expected output? What do you see instead?
The lower left status area will flash every few seconds, basically unreadable 
because it's very brief.  Open the Progress view and there will be several 
"Remote System Explorer Operation" 
entries, almost always followed by 
"JPA Java Change Event Handler (Waiting)"
or
"JPA Project Change Event Handler (Waiting)"
and Eclipse is essentially useless (can't do anything that has to wait for 
those to complete, like saving a change) until all of the items in progress 
complete.  This can take a minute or two and is quite frustrating when all you 
want to do is save a change.

What version of the product are you using? On what operating system?
most recent version of this plugin
on
Version: Kepler Release
Build id: 20130614-0229
on 
Windows 7 x64 with all the latest updates.

Please provide any additional information below.
I had first entered this under Eclipse bugs here (see the bottom few entries)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=386171

Original issue reported on code.google.com by [email protected] on 9 Aug 2013 at 2:07

@GoogleCodeExporter
Copy link
Author

My apologies.  I had uninstalled this plugin yesterday and had not had the 
described problem all day.  It had been happening so frequently prior to the 
uninstall that I was certain it must be the cause.  But it has just happened 
again today, so it must not be this plugin.

Original comment by [email protected] on 9 Aug 2013 at 3:22

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant