Community
Participate
Working Groups
Build Identifier: Tested Vista, Windows 7 JDK 6_18, JDK 6_25 Tomcat 6_032, Tomcat 7_12, Tomcat 7_21 Eclipse (eclipse-jee-indigo-win32.zip) latest from Eclipse site downloads WST latest from update site. With out any configuration and installation. All in stock. Reproducible: Always Steps to Reproduce: 1. Add new Server (Tomcat6 or Tomcat7) 2. add web project (import existing one) 3. start server
I am moving this over to Server Tools due to the "Start server" step, but really, we need more information before we can properly diagnose what is going on. Is there anything in the .log file? Are you able to take a thread dump to see what is taking so long to initialize?
(In reply to comment #1) > I am moving this over to Server Tools due to the "Start server" step, but > really, we need more information before we can properly diagnose what is going > on. Is there anything in the .log file? Are you able to take a thread dump to > see what is taking so long to initialize? Log information: eclipse.buildId=I20110613-1736 java.version=1.6.0_18 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=ru_RU Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os win32 -ws win32 -arch x86 -debug -clean -product org.eclipse.epp.package.jee.product !ENTRY org.eclipse.wst.server.core 4 0 2011-09-13 19:29:39.807 !MESSAGE Server MOD-7 was unable to start within 45 seconds. If the server requires more time, try increasing the timeout in the server editor. debug info: Start VM: -Dosgi.requiredJavaVersion=1.5 -Xms40m -Xmx512m -XX:MaxPermSize=256m -Djava.class.path=C:\Java\eclipse\\plugins/org.eclipse.equinox.launcher_1.2.0.v2 0110502.jar -os win32 -ws win32 -arch x86 -showsplash C:\Java\eclipse\\plugins\org.eclipse.platform_3.7.0.v201106131736\sp lash.bmp -launcher C:\Java\eclipse\eclipse.exe -name Eclipse --launcher.library C:\Java\eclipse\\plugins/org.eclipse.equinox.launcher.win32.w in32.x86_1.1.100.v20110502\eclipse_1406.dll -startup C:\Java\eclipse\\plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.j ar --launcher.overrideVmargs -debug -clean -product org.eclipse.epp.package.jee.product -vm C:\Program Files\Java\jre6\bin\client\jvm.dll -vmargs -Dosgi.requiredJavaVersion=1.5 -Xms40m -Xmx512m -XX:MaxPermSize=256m -Djava.class.path=C:\Java\eclipse\\plugins/org.eclipse.equinox.launcher_1.2.0.v2 0110502.jar Install location: file:/c:/Java/eclipse/ Configuration file: file:/c:/Java/eclipse/configuration/config.ini loaded Configuration location: file:/c:/Java/eclipse/configuration/ Framework located: file:/c:/Java/eclipse/plugins/org.eclipse.osgi_3.7.0.v20110613.jar Loading extension: reference:file:javax.transaction_1.1.1.v201105210645.jar eclipse.properties not found Framework classpath: file:/c:/Java/eclipse/plugins/org.eclipse.osgi_3.7.0.v20110613.jar file:/c:/Java/eclipse/plugins/ file:/c:/Java/eclipse/plugins/javax.transaction_1.1.1.v201105210645.jar Splash location: C:\Java\eclipse\\plugins\org.eclipse.platform_3.7.0.v201106131736\splash.bmp Debug options: file:/C:/Java/eclipse/.options not found Time to load bundles: 38 Starting application: 4432 Application Started: 9707 PS: please if you need more information, provide me with steps to collect it.
Does the server still timeout with no project added? My guess is that the answer will be yes. Examine the Console view while Tomcat is starting to see if it completes it's startup. You would see something link "INFO: Server startup in 1305 ms". If this state is reached prior to the timeout and the server still times out, it implies that the "ping" test isn't reaching the server. On the rare occasions where this has occurred, it has been a OS issue that was the cause. You can try specifying the Host name as "127.0.0.1" and see if that results in better behavior. If not, we will have to dig further.
(In reply to comment #3) > Does the server still timeout with no project added? My guess is that the > answer will be yes. > > Examine the Console view while Tomcat is starting to see if it completes it's > startup. You would see something link "INFO: Server startup in 1305 ms". If > this state is reached prior to the timeout and the server still times out, it > implies that the "ping" test isn't reaching the server. On the rare occasions > where this has occurred, it has been a OS issue that was the cause. You can > try specifying the Host name as "127.0.0.1" and see if that results in better > behavior. If not, we will have to dig further. Actually, yes. I see log message "INFO: Server startup in ... ms, and can work in my web project 45 seconds or else (depended on server settings). Server start up as usual, just Eclipse doesn't see that server already started. Another case I found. If I install Tomcat 7 server for Helios, it doesn't startup too and after installation no one new server (6 or 7 tomcat) doesn't want to start. In Indigo no one server works. It looks like in some way depended on creating new server. because if I copy all settings from Helios to Indigo with workplace and already created servers, tomcat 6 works. but new servers doesn't want.
Are these Tomcats being installed by unzipping one of the Tomcat binary.zips or running the install exe? Did using "127.0.0.1" make any difference?
(In reply to comment #5) > Are these Tomcats being installed by unzipping one of the Tomcat binary.zips or > running the install exe? Did using "127.0.0.1" make any difference? where I can set "127.0.0.1" unziped and installed and downloaded via eclipse also ssettings -> server -> profiles (no profiles registered) and don't know how to register one :)
To set "127.0.0.1", enter "127.0.0.1" as the "Host name" in the General Information section of the server editor. No other changes are needed. This will eliminate any need for the "ping" code to resolve "localhost".
I tried to re-create, but was unable to run into the same issue. Tested: - Win XP SP3 - Sun JDK 6_27 - Tomcat 7_21 (I downloaded the win 32 zip and unzipped to a directory) - Eclipse 3.7.1 M20110909-1335 - WTP R331 09152011 - Default configuration for my workspace and tomcat server 1. Created new Tomcat 7 server 2. Imported project (dynamic web project, containing a servlet) 3. Started the server 4. Add the project to the server 5. Waited about 1 minute, no issues 6. Restarted the server 7. Waited about 1 minute, no issues 8. Ran the servlet and verified results I checked my .log and I didn't see the same error you saw Does your project fail for that particular project? Have you tried a simple dynamic web project like the one I had described? Thanks
Thanks for Help. And Sorry for invalid bug ticket. It was my workstation problems. After re-installing OS all works fine. Don't know what it actually was.
