Eclipse JPA project change event handler (pending)

Question

Why do I get the "JPA project change event handler (pending)" when I try to build my project.

I have several JPA projects in my workspace and it takes a long time to create my project. It also causes the GC limit to be exceeded with 6 GB of heap space allocated for the eclipse

I am currently using Kepler. This problem did not occur in Helios.

There are some BugZilla entries for the above error, but I see them fixed. But not available in 4.3.1?

Any solutions / workarounds for the above problem?

thank

Answer 1

I had the same problem, and I found out that it looks like a known bug in DALI (Eclipse Java Persistence Tools), since at least eclipse 3.8, which could lead to the fact that saving the action in the java editor will be extremely slow .

Since this is not yet fully resolved in Kepler (20130614-0229), and because I do not need JPT / DALI in my eclipse, I manually deleted the org.eclipse.jpt functions and plugins.

What I've done:

1.) exit eclipse

2.) go to my eclipse installation directory

 cd eclipse 

and follow these steps:

* Nicks:

 mkdir disabled mkdir disabled/features disabled/plugins mv plugins/org.eclipse.jpt.* disabled/plugins mv features/org.eclipse.jpt.* disabled/features 

window:

 mkdir disabled mkdir disabled\features mkdir disabled\plugins move plugins\org.eclipse.jpt.* disabled\plugins for /D /R %D in (features\org.eclipse.jpt.*) do move %D disabled\features 

3.) Restart eclipse.

After starting up and the first time you use it, eclipse may warn you about the need to reconfigure your content assistant . Do this in the settings dialog.

Done.

After removing DALI / JPT, my eclipse feels good again. The user interface is no longer blocked and waits a second while saving the file.

Answer 2

I don’t know why, my Neon Eclipse still has this problem, it does not seem to be fixed in the Mars version, as many have said.

I found that using the command is too troublesome; I uninstall the plugin through Eclipse Installation Manager.

Neon: [Help> Installation Information> Installed Software]

Oxygen: [Settings> Installation / Update> Installed software]

Just select the "Dali Java Persistence Tools -JPA Support" plugin and click "Uninstall." Please note that my screen below does not have this because I have already been deleted.

Answer 3

I disabled (did not check) the JPA validator.

Now, when I save the file, it shows only one job for the JPA Project Change event handler and only 2 or 3 for the Java JPA event handler.

And most importantly, the UI Hang issue is resolved.

Please review the following screenshot for the setting I made:

Answer 4

I still have the same problem in Neon. 2 My solution is to disable JPA Configurator.

Open the Eclipse preferences (not project prefs!). Go to Maven -> Integration with Java EE and disable JPA Configurator. I also disabled JAX-RS Configurator and JSF Configurator.

From now on, the JPA project change event handler is no longer displayed.

Restart Eclipse if the change does not take effect immediately.

Answer 5

There is another way to disable JPA tools for a project that does not require the removal of JPA / plugin functions. I tested the project https://github.com/Jasig/uPortal , which was mentioned in https://bugs.eclipse.org/bugs/show_bug.cgi?id=386171 , and claims to have similar problems:

• Switch to the Eclipse Project Explorer View to view projects with JPA Facet enabled (must be a "JPA Content" node);
• Select a project of interest that has a "JPA Content" node, and select "Properties" from the context menu or press "Alt + Enter" to display the "Properties" dialog box for the project;
• Select the "Project Boundaries" node in the tree with categories;
• Clear the JPA check box in the object facet list and click OK.

After you have disabled the JPA facet for the project form repository for the add-in, I do not see any JPA-related tasks in the Eclipse progress view.

Answer 6

minor correction for mwhs response for windows section ...

The move command does not work for the folder. \ functions, because ... well, frankly, because Windows is lagging behind (you can use wildcards with "moving" through files, but obviously wildcards + folders == ignore the command). In any case, this should work as an alternative to the window fragment provided for step # 2 in his answer.

as a batch file:

 @echo off set eclipse_dir=C:\eclipse_luna mkdir disabled mkdir disabled\features mkdir disabled\plugins move plugins\org.eclipse.jpt.* disabled\plugins for /f %%i in ('dir "%eclipse_dir%\features\org.eclipse.jpt.*" /ad /b') do ( move "%eclipse_dir%\features\%%i" "%eclipse_dir%\disabled\features\%%i" ) 

Answer 7

Also, if you cannot find your eclipse, dir. Since I had such a problem on a Mac, we can remember that Eclipse uses OSGi, so we can go to the Target Platform and disable the functions / plugins that were described above: org.eclipse.jpt. *

Answer 8

The solution for photon eclipse is as follows:

1. open. /eclipse/configuration/org.eclipse.equinox.simpleconfigurator/bundles.info
2. delete lines starting with org.eclipse.jpt (can only work for deleting org.eclipse.jpt.jpa)