Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8313239
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 8, 20262026-06-08T20:25:28+00:00 2026-06-08T20:25:28+00:00

I have a EJB2/EJB3 Java project in Eclipse. I recently enabled JPA Facet and

  • 0

I have a EJB2/EJB3 Java project in Eclipse. I recently enabled JPA Facet and now installed Dali and configured access to the MySQL DB containing the actual tables and data.

The problem is, editing entity beans in IDE Java editor became 100-1000 times slower. Write one word, see “Update JPA Project” appear on status bar, wait 30 seconds CPU under high load, Eclipse totally unresponsive, then continue and write next word..

The project that makes JPA slow is medium-sized, not just a simple webstore, but not enterprise-class either. I count 42 Stateless Session Beans and 49 Entity Beans. We actually have more entity beans, but many of them have not yet been converted to EJB 3, but are mapped only with EJB 2.1 instead.

The longest of the session beans spans 20616 lines, longest methods being a hair below 2k lines.

The slowness of JPA is so severe, it makes also typing code slow. After every 5-10 characters the Eclipse goes into complete halt for several seconds and content-assist is almost unusable, because it keeps triggering Eclipse’s internal time-outs.

So, the question is: How do I keep the JPA Facet enabled for the project and still make it not lag all the real work? Some simple toggle switch that would just disable the JPA part and then later re-enable would be lovely.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-08T20:25:30+00:00Added an answer on June 8, 2026 at 8:25 pm

    In Juno the Dali project has made several performance improvements that should help with your situation. We also made changes to push some of our work to background threads and use the Eclipse Jobs framework.

    • https://bugs.eclipse.org/bugs/show_bug.cgi?id=370407
    • https://bugs.eclipse.org/bugs/show_bug.cgi?id=377039
    • https://bugs.eclipse.org/bugs/show_bug.cgi?id=376787
    • https://bugs.eclipse.org/bugs/show_bug.cgi?id=336403

    If you still see performance lags in Juno I would greatly appreciate you sending us some performance profiling information.
    I could attempt to use your results in my work to improve performance (In Juno SR1 if possible). I’ve had success using the Java VisualVM included in jdk1.6.0_31. I set the profiler CPU settings to ‘Start profiling from classes:’ org.eclipse.jpt.**, uncheck ‘Profile new Runnables’, and ‘Profile only classes:’ org.eclipse.jpt.*. Then you could run one of your use cases that causes issues and attach the resulting snapshot to an eclipse bug (WebTools-Dali Jpa Tools).

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Now we have a project with java 1.4 and ejb 2.1 running on jboss
We have an old project written with EJB 2.1. Now we need to extend
I have created a ejb2 application in eclipse 3.7, with jboss 5.0 application server.
I have migration project which i have to start to migrate EJB2.1 enterprise web
i have to migrate a project written in java 1.4 with ejb 2.0 to
I have created a EJB2.0 using Eclipse 3.7 IDE, and deployed it in JBoss
I have an old EJB (2.1) project that uses xdoclet (1.2.3) to generate the
I have an EJB 2.1 project, works on WebShere 7. I must migrate it
I have legacy application using struts & ejb2.0 , hibernate v3.0 running on JBoss
We have a project with a pretty considerable number of EJB 2 stateless session

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.