[sma202]

Tomcat startup is extremely slow with 5.5.16. With 5.0.28 it was alot better (but here it wouldn’t stop properly). This happens only in DEBUG mode. I understand that the plugin should call tomcat exactly like from the command prompt but this is not happening correctly for some reason. How do I find out what command myeclipse is sending to tomcat? Is there a log file somewhere?

With a fresh/clean download of 5.5.16:

Eclipse:

In RUN mode tomcat starts up in 2718ms.
In DEBUG mode tomcat starts up in 40,000ms. with 100%cpu!!

Command prompt:
In RUN mode tomcat starts up in 2000-3000ms.
In DEBUG mode tomcat starts in 7000-9000ms.

Sysdeo Plugin
In RUN mode tomcat starts up in 2000-3000ms.
In DEBUG mode tomcat starts in 7000-9000ms.

This is definitely a problem with myeclipse as i’ve tried launching tomcat using the Sysdeo plugin with no issues. I’ll also note that my AFS service is going to 100% when launching tomcat in DEBUG mode using myeclipse which doesn’t make sense.

*** Date: Wed Apr 19 16:56:14 EDT 2006

*** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.5.0_04

*** MyEclipse details:
MyEclipse Enterprise Workbench

Version: 4.0.3 GA
Build id: 20051025-4.0.3-GA

*** Eclipse details:
Eclipse SDK

Version: 3.1.1
Build id: M20050929-0840

Eclipse Project SDK

Version: 3.1.1
Build id: M20050929-0840

Eclipse Platform

Version: 3.1.1
Build id: M20050929-0840

Eclipse Java Development Tools

Version: 3.1.1
Build id: I20050627-1435

Eclipse RCP

Version: 3.1.1
Build id: I20050627-1435

Eclipse Plug-in Development Environment

Version: 3.1.1
Build id: I20050627-1435

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-launcher
C:\Program Files\AFSMirror\EclipseIDE\3.1\eclipse\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
1738_734
-configuration
C:\Documents and Settings\saadah\Application Data\EclipseIDE3.1\configuration\default
-data
C:\Documents and Settings\saadah\Application Data\EclipseIDE3.1\workspace\default
-vm
C:\Program Files\AFSMirror\sunjdk\1.5.0_04\jre\bin\javaw.exe

[Riyad Kalla]

I think you replied in another thread with this same info and I followed up there with you. Let’s keep tracking the issue in the other thread and get you fixed up.

[Author]

Posts