- This topic has 19 replies, 4 voices, and was last updated 19 years ago by
.
-
Posts
-
I can start Tomcat but not stop it. The Stop button is greyed out.
(I’ve followed Eclipse 3.0 Kickstart by Carlos Valcarcel for how to install MyEclipse and Tomcat.)
I’m using Windows XP Media Center Edition, Eclipse 3.1.2, MyEclipse 4.1.1, Tomcat 5.5.16.
I installed Tomcat first as a service, then uninstalled it and installed it just by expanding the zip file.
I’ve unistalled MyEclipse and reinstalled it. I’ve configured Tomcat for use by MyEclipse as per Valcarcel p. 184.Sorry to trouble you
Thanks
Charlie HowardCharlie I followed up with you in the other thread, this is a bug when launching in Run mode. Change your connector to launch in Debug mode to work around it.
Interesting. When I was using Tomcat 5.5.7, I had no trouble starting and stopping the Application server from Eclipse. I installed Tomcat 5.5.16 and now I can start the server but not stop it.
Another interesting quirk of this bug is the console spews debug statements on startup regardless of the setting. When I navigate to Configure server -> Application Servers -> Tomcat 5 – > Launch to press the “Run Mode” (from debug mode), it makes no difference. Even after completely cold-booting my PC, my Tomcat console is perpetually in debug mode after start up.
Well here is mine, i’m using tomcat 5.0.28 and can’t stop it. I have to terminate the process.
Also, I am experiencing a problem in Debug mode where the 1st time I start tomcat, it launches an app under 1 min. On subsequent runs, the startup time is 5-8min. Only exiting eclipse completely and then starting tomcat corrects this problem. If I switch to Run mode then it takes 1min to load everytime.
*** Date: Wed Apr 19 14:42:43 EDT 2006
*** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.5.0_04*** MyEclipse details:
MyEclipse Enterprise WorkbenchVersion: 4.0.3 GA
Build id: 20051025-4.0.3-GA*** Eclipse details:
Eclipse SDKVersion: 3.1.1
Build id: M20050929-0840Eclipse Project SDK
Version: 3.1.1
Build id: M20050929-0840Eclipse Platform
Version: 3.1.1
Build id: M20050929-0840Eclipse Java Development Tools
Version: 3.1.1
Build id: I20050627-1435Eclipse RCP
Version: 3.1.1
Build id: I20050627-1435Eclipse Plug-in Development Environment
Version: 3.1.1
Build id: I20050627-1435Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-launcher
C:\Program Files\AFSMirror\EclipseIDE\3.1\eclipse\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
fb4_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.exesma, please try upgrading to MyEclipse 4.1.1. Also the launch startup time issue sure sounds suspicious, try restarting Eclipse using the -clean command line argument to clean out any stale plugin state (like debugger state possibly).
Also it could be a memory issue, please see our tip here: http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-10087.html
@support-rkalla wrote:
sma, please try upgrading to MyEclipse 4.1.1. Also the launch startup time issue sure sounds suspicious, try restarting Eclipse using the -clean command line argument to clean out any stale plugin state (like debugger state possibly).
Also it could be a memory issue, please see our tip here: http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-10087.html
I’ve tried the clean the permsize options already and it made no difference., my vm args are:
-Xms256m -Xmx512m -XX:PermSize=128M -XX:MaxPermSize=256M
I’ve upgraded to 4.1.1, same problem with tomcat taking to long to run on the 2nd run, 1st run is fast (DEBUG mode). Also, once the debugger is stopped at a breakpoint, it takes quite long for the debugged to focus on the current stack around (5-8seconds) vs other plugins its instantaneous. Again, it seems like the AFS network service is being triggered by myeclipse somehow and it goes to 50-100% cpu. I don’t see this issue with sysdeo or standalone eclipse debugging.
*** Date: Thu Apr 20 14:18:57 EDT 2006
*** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.5.0_04*** MyEclipse details:
MyEclipse Enterprise WorkbenchVersion: 4.1.1 GA
Build id: 20060309-4.1.1-GA*** Eclipse details:
Eclipse SDKVersion: 3.1.1
Build id: M20050929-0840Eclipse Project SDK
Version: 3.1.1
Build id: M20050929-0840Eclipse Platform
Version: 3.1.1
Build id: M20050929-0840Eclipse Java Development Tools
Version: 3.1.1
Build id: I20050627-1435Eclipse RCP
Version: 3.1.1
Build id: I20050627-1435Eclipse Plug-in Development Environment
Version: 3.1.1
Build id: I20050627-1435Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-launcher
C:\Program Files\AFSMirror\EclipseIDE\3.1\eclipse\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
3c4_734
-clean
-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.exeAlso, once I upgraded to the new version, tomcat IS stopping properly now which is good. But the time it takes to startup is awful.
Try this. Go download the newest Tomcat 5.5 release in ZIP format from the Tomcat site, unzip it to a dir. Go to MyEclipse and setup your connector to JUST point to the Tomcat home dir, then go under the JDK settings and set the JDK to launch it with (don’t adjust any Paths settings). Now launch it from the toolbar and stop it.
Is it faster?
Also it might be a memory issue, try the tip I referred to before, according to your configuration you aren’t modifying your args in any way.
I’ve tried installing a clean tomcat and the same issue occurs with tomcat 5.5 startup being slower then 5.0.28. Again, there is no performance issue with other plugins or through command line.
When I deploy my application, the first time it loads fast (under <1min), 2nd time it takes (5-8min). What is happening, is myeclipse reusing the same jvm? It might be leaving some objects behind in memory, like JNI for example?
Also, I have verified that i’m using the perm options for my vm args, why do you think otherwise? I don’t think the myeclipse configuration shows the vm args being passed to eclipse.exe.
@support-rkalla wrote:
Try this. Go download the newest Tomcat 5.5 release in ZIP format from the Tomcat site, unzip it to a dir. Go to MyEclipse and setup your connector to JUST point to the Tomcat home dir, then go under the JDK settings and set the JDK to launch it with (don’t adjust any Paths settings). Now launch it from the toolbar and stop it.
Is it faster?
Also it might be a memory issue, try the tip I referred to before, according to your configuration you aren’t modifying your args in any way.
Very strange, I can’t reproduce this locally. When you setup Tomcat 5.5, are you only setting the Home directory, or are you messing with the optional VM args or adding anything special on the PATHS?
@support-rkalla wrote:
Very strange, I can’t reproduce this locally. When you setup Tomcat 5.5, are you only setting the Home directory, or are you messing with the optional VM args or adding anything special on the PATHS?
I’m not adding anything special. It’s a clean install. As I mentioned before, i’m also using AFS (http://en.wikipedia.org/wiki/Andrew_file_system) which is similar to NFS. This process goes to 60% cpus with the eclipse process going to 40%, taking up 100%. This is with tomcat 5.5, with 5.0.28, it is alot better. Tomcat 5.5 has problems even when first starting it up.
All my eclipse projects, plugins, are installed locally so I have no idea why myeclipse is causing the AFS process to take cpu.
Do you mind explaining what myeclipse is doing to startup tomcat, this will help me track down this issue? Obviously, it is doing something different then the cmdline.
Actually it’s not. It just calls the Catalina classes directly connects the debugging to the running process and that’s it. As I mentioned, I see no difference between the two on my machine.
I would point out that a *clean* unzip of Tomcat 5.5 takes 2.8 seconds to start on my AMD 4800 X2 computer. The fact that even your *first* startup takes around a minute makes me think you aren’t using a clean install, have a virus scanner running with real-time checking enabled or something else funky going on.
@support-rkalla wrote:
Actually it’s not. It just calls the Catalina classes directly connects the debugging to the running process and that’s it. As I mentioned, I see no difference between the two on my machine.
I would point out that a *clean* unzip of Tomcat 5.5 takes 2.8 seconds to start on my AMD 4800 X2 computer. The fact that even your *first* startup takes around a minute makes me think you aren’t using a clean install, have a virus scanner running with real-time checking enabled or something else funky going on.
The first startup takes around 4-5min with a clean tomcat 5.5 with the cpu 100%, with tomcat 5.0.28, it takes about 2-3 seconds. This problem occurred on another developer’s computer as well.
The problem gets more mysterious when I deploy my app. On tomcat 5.0.28, 1st run is about 1-2min. 2nd startup is 8min+. Tomcat 5.5 takes too long.
If I switch to RUN instead of DEBUG flag, applications load up on both tomcat 5.5 and 5.0.28 with under 1-2min startup, no issues.
