Community
Participate
Working Groups
Build Identifier: 20100617-1415 Republishing changes in a dynamic web project to a local Tomcat 6 server takes around a minute, even for small changes. Changing a single file then pressing save while the server runs takes a minute also. The exact same project, when used on Galileo, pushes small changes in 1 to two seconds. While the server is publishing a single CPU goes to 100% during the publish. Since a Galileo WTP workspace is not compatible with a Helios workspace (the info is there, but starting the server fails because the application cannot see it's dependencies) I have already removed the server and re-added it. I am using the default configuration for a Tomcat local server with the following changes: - startup timeout is 400 seconds - auto reload is disabled in the single deployed context (because restarting the server for every change is not funny) The project deployed is quite big; the deployed webapp takes around 134MB. This bug means I cannot use Helios at all because the code/run cycle takes way too long. Reproducible: Always Steps to Reproduce: 1. Create a big project and deploy it to Tomcat local server 2. Do an initial publish then run the server 3. Change a file, get coffee....
Hi, Same problem for me, project is about 80MB, it's a 'java-flex' problem, output path for 'flex projects' is WebContent folder of webapp project. (should that be done using 'new' deployment paths?) Same with tomcat 6 or 7 I also think is a blocker for me to use Helios. Any help we can provide? no traces in .log (except cpnflicts for keybindings) Publishing takes so long compared to galileo, takes all cores all cpu, it seems to hang or not to respond for more than a couple of minutes, sometimes it starts after a while. Eclipse JEE Dev Tools Version: 3.2.0.v201005241530-7b7GHTYFSK2W9kPaFClvz0O_NQmN Build id: 20100615235519
*** This bug has been marked as a duplicate of bug 317852 ***
