Databases
StackOverflow2013
Postsdbo
POSpeeding up Tomcat in debug mode with Eclipse IDE
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSpeeding up Tomcat in debug mode with Eclipse IDE
    primarykey
    data
    text
    <p>Running Tomcat through eclipse works fine in non-debug mode, but not in debug mode. When I try to start the Tomcat server in debug mode, the console output looks fine for a while, but then starts slowing down and eventually just stops, pegging the cpu at 100%. I don't think it's relevant, but just in case - here's the console output right about when it starts slowing down and eventually stopping (by stopping I mean no more console output, but still 100% cpu).</p> <pre><code>2009-09-02 14:35:30,859 INFO NONE org.springframework.context.weaving.DefaultContextLoadTimeWeaver:72 - Found Spring's JVM agent for instrumentation 2009-09-02 14:35:49,562 INFO NONE org.springframework.beans.factory.support.DefaultListableBeanFactory:414 - Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@ed889d: defining beans [... 2009-09-02 14:37:31,031 INFO NONE org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean:221 - Building JPA container EntityManagerFactory for persistence unit ... </code></pre> <p>I tried everything I could think of to fix it:</p> <ul> <li>cleanesd tomcat working directory</li> <li>restarted eclipse</li> <li>restarted Windows</li> <li>refreshed/cleaned all projects</li> </ul> <p>I first had this problem last week using eclipse ganymede. I had been running fine in debug-mode for several months prior to this issue. I didn't make any significant changes to our project that would cause this. Eventually, I upgraded to eclipse galileo which solved my problem. Now 2 days later, I'm having the same problem in galileo. Like I said it works fine in non-debug mode. Any help is much appreciated.</p> <p>I should add that other things work in debug mode - for instance junit tests, so it is something specific to tomcat.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USthejartender
    1. USandersonbd1
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSpeeding up Tomcat in debug mode with Eclipse IDE
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSpeeding up Tomcat in debug mode with Eclipse IDE
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POSpeeding up Tomcat in debug mode with Eclipse IDE
      1. USaldrinleal
      1. VTFavorite
    1. CODid you try to cleanup your workspace. Sometimes it happens to me, then I'll just clean my workspace. Once the workspace is cleaned it works fine
      singulars
      1. POSpeeding up Tomcat in debug mode with Eclipse IDE
      1. USArun P Johny
    2. COFYI - this same applies to Intellij IDEA. Just tried this with IntelliJ 10 and i went from 7 minutes startup time for tomcat 5.5.31 to 20 seconds for my app....
      singulars
      1. POSpeeding up Tomcat in debug mode with Eclipse IDE
      1. USShaun F
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload