- This topic has 3 replies, 2 voices, and was last updated 9 years, 11 months ago by
.
-
Posts
-
Today all of a sudden when I want to start tomcat 5 in the eclipse IDE using my eclipse I’m getting this error. I’ve used this feature for years without any issues. So I reinstalled eclipse and my eclipse and also re-installed tomcat 5 and still getting the same error. HEre is my installation summary and error log.
*** System properties:
OS=Windows7
OS version=6.1.0
OS arch=amd64
Profile arch=x86_64
Window system=win32
Java version=1.7.0_51
Workspace=file:/C:/Users/a/workspace/
VM Args=-Dosgi.requiredJavaVersion=1.6
-Xms40m
-Xmx512m
-XX:MaxPermSize=256m
-jar
C:\eclipse\plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar!STACK 1
org.eclipse.core.runtime.CoreException: FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)at org.eclipse.jdt.launching.AbstractVMRunner.abort(AbstractVMRunner.java:53)
at org.eclipse.jdt.internal.launching.StandardVMDebugger.checkErrorMessage(StandardVMDebugger.java:519)
at org.eclipse.jdt.internal.launching.StandardVMDebugger.run(StandardVMDebugger.java:324)
at com.genuitec.eclipse.core.JavaVMUtility.execute(JavaVMUtility.java:277)
at com.genuitec.eclipse.easie.core.EASIEServerManager.start(EASIEServerManager.java:41)
at com.genuitec.eclipse.easie.core.EASIEServer.start(EASIEServer.java:55)
at com.genuitec.eclipse.easie.core.EASIEServer.start(EASIEServer.java:33)
at com.genuitec.eclipse.easie.core.ui.action.ServerStartAction.startServer(ServerStartAction.java:98)
at com.genuitec.eclipse.easie.core.ui.action.ServerStartAction.basicRun(ServerStartAction.java:77)
at com.genuitec.eclipse.core.ui.action.LicenseValidatingAction.run(Unknown Source)
at com.genuitec.eclipse.core.ui.action.LicenseValidatingAction.runWithEvent(Unknown Source)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1081)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1066)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:778)
at org.eclipse.jface.action.ActionContributionItem$9.handleEvent(ActionContributionItem.java:1284)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:140)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
!SUBENTRY 1 org.eclipse.jdt.launching 4 116 2014-05-28 20:10:04.738
!MESSAGE FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR logaliaghili,
We couldn’t replicate the issue at our end.
This error typically comes up when the necessary port is taken by another program. Can you please reboot your machine and check whether you can replicate the issue after rebooting ?
Can you please clarify whether you can run Tomcat 5.x outside of MyEclipse ?
Also, can you please uninstall or disable your anti virus(if installed) in your machine and check whether you can run tomcat, as it might block some ports ?
Let us know how it works for you.
Hi Predeep,
Thank you for your response. I have rebooted a couple of times and yes I can start tomcat on it’s own. But you were right when I turned off webroot it started working. Something must have changed with my security policies. I’m still confused as why the anti virus allows me to start tomcat on its own but not through myeclipse.aliaghili,
Glad that you got it running in MyEclipse after disabling your antivirus program.
I’m still confused as why the anti virus allows me to start tomcat on its own but not through myeclipse.
Can you please clarify whether you have started Tomcat in Debug mode or Run mode in MyEclipse (Window > Preferences > MyEclipse > Servers > Tomcat > Tomcat 5.x > Launch) and outside of MyEclipse ?
In MyEclipse, if the launch mode is in Debug mode, can you please change it to Run mode and check whether tomcat starts even when the antivirus is enabled.
Let us know how it works for you.
