[troycampano]

Hello,
Sometimes when I start Tomcat I get the error message:

“A configuration error occured during startup. Please verify the preference field with the prompt: err:: No such file or directory
Error [2] in connect() call!
Socket transport failed to init.
Transport dt_socket failed to initialize, rc = -1.”

I’m running:
Eclipse 3.0.1
Tomcat 5.0.28

Any ideas? I’m really stumped.

thank you,

Troyston Campano

[Riyad Kalla]

Troyston,
Please let us know what all of your Tomcat connector settings are for each field and the JDK you have configured. Also the MyEclipse version you are using.

[troycampano]

– Java 1.4.2_05
– Jakarta-tomcat-5.0.28

I’ve accepted the defaults for everything so no parameters to the JVM and I haven’t appended the classpath or anything else like that. Everything is the default which is blank I believe.

thank you!

[Riyad Kalla]

troy,
What did you set Home/Temp/Base dirs to? These are the fields I am curious about.

Also Did you specify a JDK in the JDK settings or a JRE?

[troycampano]

Tomcat Home: c:\mydir\jakarta-tomcat-5.0.28
Tomcat Base: c:\mydir\jakarta-tomcat-5.0.28
Tomcat Temp: c:\mydir\jakarta-tomcat-5.0.28\Temp
…which were the defaults after I told eclipse where I had tomcat.

I’m running the JDK.

thank you!

[Riyad Kalla]

Shut down MyEclipse, go into your <workspace dir>\.metadata directory and erase the .log file. Then fire up MyEclipse and try and reproduce the problem, as soon as it happens check the log file for exceptions and paste them here.

Additionally I would suggest restarting Eclipse with the -clean command line argument to let it rebuild your plugin cache, this might be what is causing the problems.

[gcstang]

I have the same problem. It seems as though it’s using my JDK 1.5.0_07 even though I’ve assigned 1.4.2_12 as the JDK to use with Tomcat 5.0.28

@support-rkalla wrote:

Shut down MyEclipse, go into your <workspace dir>\.metadata directory and erase the .log file. Then fire up MyEclipse and try and reproduce the problem, as soon as it happens check the log file for exceptions and paste them here.

Additionally I would suggest restarting Eclipse with the -clean command line argument to let it rebuild your plugin cache, this might be what is causing the problems.

!SESSION 2006-08-07 10:05:06.826 ———————————————–
eclipse.buildId=M20060629-1905
java.version=1.5.0_07
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -product com.genuitec.myeclipse.product.ide
Command-line arguments: -os win32 -ws win32 -arch x86 -product com.genuitec.myeclipse.product.ide

!ENTRY org.eclipse.wst.internet.cache 1 0 2006-08-07 10:05:16.901
!MESSAGE wtp.autotest.noninteractive is set. Licenses dialogs will not be displayed.

!ENTRY com.genuitec.eclipse.easie.core 1 0 2006-08-07 10:05:29.198
!MESSAGE Error starting Tomcat 5 server
!STACK 0
com.genuitec.eclipse.core.GenuitecCoreException: Transport dt_socket failed to initialize, rc = 509.

at com.genuitec.eclipse.easie.tomcat.Tomcat.start(Tomcat.java:56)
at com.genuitec.eclipse.easie.tomcat.Tomcat.start(Tomcat.java:44)
at com.genuitec.eclipse.easie.core.ui.action.ServerStartAction.ă(Unknown Source)
at com.genuitec.eclipse.easie.core.ui.action.ServerStartAction.basicRun(Unknown Source)
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:539)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
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.core.launcher.Main.invokeFramework(Main.java:336)
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at org.eclipse.core.launcher.Main.main(Main.java:952)
Caused by: org.eclipse.core.runtime.CoreException: Transport dt_socket failed to initialize, rc = 509.

at org.eclipse.jdt.launching.AbstractVMRunner.abort(AbstractVMRunner.java:47)
at org.eclipse.jdt.internal.launching.StandardVMDebugger.checkErrorMessage(StandardVMDebugger.java:328)
at org.eclipse.jdt.internal.launching.StandardVMDebugger.run(StandardVMDebugger.java:242)
at com.genuitec.eclipse.core.JavaVMUtility.execute(JavaVMUtility.java:204)
at com.genuitec.eclipse.easie.tomcat.TomcatManager.startTomcat(TomcatManager.java:56)
at com.genuitec.eclipse.easie.tomcat.TomcatManager.start(TomcatManager.java:36)
at com.genuitec.eclipse.easie.tomcat.Tomcat.start(Tomcat.java:53)
… 30 more

[geodok]

Same for me with MyEclipse starting with JDK 1.5.0_09, and Tomcat 5.0.30 configured for use with JDK 1.4.2_10 and debug mode. In run mode, everything is fine.

Will there be a fix for this soon!?

[geodok]

Forgot to mention that “eclipse -clean” didn’t help.

[Riyad Kalla]

There are a handful of solutions to this problem here:
http://forum.java.sun.com/thread.jspa?threadID=160025&start=15

1) Try adding your JDK\bin dir to your System PATH.
2) Try disabling your local firewall (Eclipse debugger uses IP)

[sri.vaddi]

Try disabling your local firewall (Eclipse debugger uses IP)>>>

After disabling local firewall eclipse debugger started working.

Will there be any work around for this?

[Riyad Kalla]

It effects some folks and not others, we are looking into it.

[Author]

Posts