[johnryanbuss]

Tomcat (built in and external) starts fine the first time after MyEclipse is opened, but every subsequent attempt gives me this message:

“A configuration error occurred during startup. Please verify the preference field with the promp: Cannot connect to VM”

log:

!ENTRY com.genuitec.eclipse.easie.core 1 0 2011-07-01 14:14:16.166
!MESSAGE Error starting MyEclipse Tomcat  server
!STACK 0
com.genuitec.eclipse.core.GenuitecCoreException: Cannot connect to VM
    at com.genuitec.eclipse.easie.tomcat.Tomcat.start(Tomcat.java:55)
    at com.genuitec.eclipse.easie.tomcat.myeclipse.MyEclipseTomcat.start(MyEclipseTomcat.java:39)
    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: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:1053)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1062)
    at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:774)
    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:1053)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
    at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
    at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
    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:369)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
Caused by: org.eclipse.core.runtime.CoreException: Cannot connect to VM
    at org.eclipse.jdt.launching.AbstractVMRunner.abort(AbstractVMRunner.java:50)
    at org.eclipse.jdt.internal.launching.StandardVMDebugger.run(StandardVMDebugger.java:340)
    at com.genuitec.eclipse.core.JavaVMUtility.execute(JavaVMUtility.java:277)
    at com.genuitec.eclipse.easie.tomcat.TomcatManager.startTomcat(TomcatManager.java:59)
    at com.genuitec.eclipse.easie.tomcat.TomcatManager.start(TomcatManager.java:37)
    at com.genuitec.eclipse.easie.tomcat.Tomcat.start(Tomcat.java:52)
    ... 39 more
Caused by: java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind
    at java.net.PlainSocketImpl.socketBind(Native Method)
    at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
    at java.net.ServerSocket.bind(ServerSocket.java:319)
    at java.net.ServerSocket.<init>(ServerSocket.java:185)
    at java.net.ServerSocket.<init>(ServerSocket.java:97)
    at org.eclipse.jdi.internal.connect.SocketTransportService.startListening(SocketTransportService.java:277)
    at org.eclipse.jdi.internal.connect.SocketTransportImpl.startListening(SocketTransportImpl.java:47)
    at org.eclipse.jdi.internal.connect.SocketListeningConnectorImpl.startListening(SocketListeningConnectorImpl.java:115)
    at org.eclipse.jdt.internal.launching.StandardVMDebugger.run(StandardVMDebugger.java:246)
    ... 43 more

[support-joy]

johnryanbuss,

Sorry to hear you are running into this issue. You have not mentioned details regarding your OS, version and the version of MyEclipse you are using. Also what are the steps to replicate this and since how long you are experiencing this issue. Could you answer below queries –
1. Copy and paste your installation details. Open MyEclipse IDE, from menu options click on MyEclipse > Installation Summary > Installation Details
2. Your .log file points to java.net.SocketException. This indicates that either you are behind proxy / firewall and the proxy is not allowing you to connect to update sites. Could you clarify if you have setup proxy here – window > preferences > general > network connections? If yes, please attach a screenshot to help me get a visual. Refer – https://www.genuitec.com/forums/topic/troubleshooting-how-to-upload-attachments-on-forum/ on how to upload attachments.
Could you try the following for me –

1. Open Window > preferences > Myeclipse > servers > Integrated Sandbox > Tomcat 6. From the right hand pane click on [Restore MyEclipse Tomcat Server Installation], [Apply] and [OK] and restart the IDE.
2. If it is still an issue, could you try out the solution posted by the user – “grr” solution here – https://www.genuitec.com/forums/topic/socket-closed-cannot-connect-to-vm-when-debugging/

Let me know how this works for you.

[johnryanbuss]

This is a new computer, so it has been happening the whole time I’ve been using it, there aren’t really any steps, I just start tomcat, stop it, then try to start it again.

*** Date:
Tuesday, July 5, 2011 8:56:26 AM EDT

** System properties:
OS=WindowsVista
OS version=6.1.0
Java version=1.6.0_13

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 9.1
Build id: 9.1-20110701

*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 9.1
Build id: 9.1-20110701

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Users\bussr\AppData\Local\MyEclipse\MyEclipse 9\myeclipse.exe
-name
Myeclipse
–launcher.library
C:\Users\bussr\AppData\Local\MyEclipse\MyEclipse 9\../Common/plugins/org.eclipse.equinox.launcher.i18n.win32.win32.x86_3.2.0.v201103301700\eclipse_3215.dll
-startup
C:\Users\bussr\AppData\Local\MyEclipse\MyEclipse 9\../Common/plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
-install
C:\Users\bussr\AppData\Local\MyEclipse\MyEclipse 9
-configuration
C:\Users\bussr\AppData\Local\MyEclipse\MyEclipse 9\configuration
-vm
C:\Users\bussr\AppData\Local\MyEclipse\Common\binary\com.sun.java.jdk.win32.x86_1.6.0.013\jre\bin\client\jvm.dll

[johnryanbuss]

I have not set up a proxy, I didn’t need one previously.

[johnryanbuss]

I restored tomcat and have the same problem still.

[johnryanbuss]

I found and tried grr’s solution on Friday.

[johnryanbuss]

I’m not sure why it says my OS is Vista, I am actually on Windows 7

[Patrick Kates]

Hi Joy – I work with Ryan (original poster) and have an essentially identical install (i.e. brand new laptop with new MyEclipse 9 32 bit install) and I am also having the same issue.

Some info that that the Installation Details leave out.

We are using:

Windows 7 Pro 64 bit
Tomcat 6.0.32 32 bit
Java 1.6.0.26 32 bit

[support-tony]

Ryan and Kate,

Unfortunately, I wasn’t able to replicate your problem, using WIn 7, 64 bit and the same versions of Tomcat and JDK.

Is this just a problem when you start the server in debug mode? Can you start the server externally (i.e. not in MyEclipse), reliably?

Did you install the Tomcat service? I’ve seen some mention of this problem with the Tomcat service. Also, there are quite a few google hits on “java.net.SocketException: Unrecognized Windows Sockets error: 0: JVM_Bind ” and tomcat. For example, near the bottom of this page a couple of suggestions are posted. The last one mentions Skype, which I’ve seen mentioned in other hits, though I couldn’t replicate the problem even with Skype running.

I’m wondering if some part of tomcat is left running, after the first instance is started. Would it be possible to check that? Perhaps one of the ports is left open. You can check ports with ‘netstat -a -o -n” in a command window.

Please try the suggestions in the linked page or on other pages that come up with the search, and come back with anything you find and with more info.

[Patrick Kates]

Tomcat is not installed as a service – you can stop and restart it externally to myeclipse even after getting the error in myeclipse. We do not have Skype installed.

We start in debug mode normally. I tried Run mode and it stopped and started normally. After switching back to debug mode it started receiving the same error again.

We’ll check on the suggestions in the other thread.

[Patrick Kates]

Port 8080 is not in use by any other process. The tcnative1.dll suggestion from the javaranch thread did not help.

Creating an alternate launch configuration seemed to work initially. But when you attempt to start that configuration in debug mode then you get the same error. This would seem to indicate that the port being used to connect to tomcat for debugging is not being released.

[support-tony]

The only problem with that is that the port used seems to be generated dynamically and so won’t use the same port each time. Check out the Debug Perspective after starting Tomcat successfully for the first time, in debug mode. It will show the port used to connect.

From what you say, it certainly does appear to be related to debugging but I can’t replicate it here. Could you delete the error log (you can do this from the Error Log view) then try starting Tomcat in debug mode again and see if there are any relevant errors in the Error Log? If so, please post them here.

I did find another reference to a similar (but not identical) problem whereby if the user waits a few minutes after getting a start problem, Tomcat start up fine. Perhaps you could try this just to rule it out.

If we get no further, I’ll try to find someone who might know a bit more about this to take a look.

[Patrick Kates]

Waiting does not help.

I cleared the log and then attempted a server restart and received:

null
Info
Thu Jul 07 10:06:04 EDT 2011
Error starting Tomcat  6.x server

com.genuitec.eclipse.core.GenuitecCoreException: Cannot connect to VM
at com.genuitec.eclipse.easie.tomcat.Tomcat.start(Tomcat.java:55)
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: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:1053)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1062)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:774)
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:1053)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
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:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
Caused by: org.eclipse.core.runtime.CoreException: Cannot connect to VM
at org.eclipse.jdt.launching.AbstractVMRunner.abort(AbstractVMRunner.java:50)
at org.eclipse.jdt.internal.launching.StandardVMDebugger.run(StandardVMDebugger.java:340)
at com.genuitec.eclipse.core.JavaVMUtility.execute(JavaVMUtility.java:277)
at com.genuitec.eclipse.easie.tomcat.TomcatManager.startTomcat(TomcatManager.java:59)
at com.genuitec.eclipse.easie.tomcat.TomcatManager.start(TomcatManager.java:37)
at com.genuitec.eclipse.easie.tomcat.Tomcat.start(Tomcat.java:52)
... 38 more
Caused by: java.net.BindException: Address already in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383)
at java.net.ServerSocket.bind(ServerSocket.java:328)
at java.net.ServerSocket.<init>(ServerSocket.java:194)
at java.net.ServerSocket.<init>(ServerSocket.java:106)
at org.eclipse.jdi.internal.connect.SocketTransportService.startListening(SocketTransportService.java:277)
at org.eclipse.jdi.internal.connect.SocketTransportImpl.startListening(SocketTransportImpl.java:47)
at org.eclipse.jdi.internal.connect.SocketListeningConnectorImpl.startListening(SocketListeningConnectorImpl.java:115)
at org.eclipse.jdt.internal.launching.StandardVMDebugger.run(StandardVMDebugger.java:246)
... 42 more

I then restarted MyEclipse and received the following errors during restart:

eclipse.buildId=unknown
java.version=1.6.0_26
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86


Warning
Thu Jul 07 10:11:42 EDT 2011
A handler conflict occurred.  This may disable some commands.


Warning
Thu Jul 07 10:11:42 EDT 2011
Conflict for 'com.genuitec.eclipse.ast.deploy.core.runonservershortcut.debug':
HandlerActivation(commandId=com.genuitec.eclipse.ast.deploy.core.runonservershortcut.debug,
    handler=org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension$LaunchCommandHandler@98db1f,
    expression=,sourcePriority=0)
HandlerActivation(commandId=com.genuitec.eclipse.ast.deploy.core.runonservershortcut.debug,
    handler=org.eclipse.debug.internal.ui.launchConfigurations.LaunchShortcutExtension$LaunchCommandHandler@159fa96,
    expression=,sourcePriority=0)

And

eclipse.buildId=unknown
java.version=1.6.0_26
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86


Warning
Thu Jul 07 10:11:41 EDT 2011
Keybinding conflicts occurred.  They may interfere with normal accelerator operation.


eclipse.buildId=unknown
java.version=1.6.0_26
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86


Warning
Thu Jul 07 10:11:41 EDT 2011
A conflict occurred for SHIFT+DEL:Binding(SHIFT+DEL,
ParameterizedCommand(Command(org.eclipse.datatools.sqltools.result.removeAllInstances,Remove All Visible Results,
,
Category(org.eclipse.datatools.sqltools.result.category,SQL Results View,null,true),
,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.window,,,system)
Binding(SHIFT+DEL,
ParameterizedCommand(Command(org.eclipse.ui.edit.cut,Cut,
Cut the selection to the clipboard,
Category(org.eclipse.ui.category.edit,Edit,null,true),
org.eclipse.ui.internal.handlers.WidgetMethodHandler@1a62c37,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.dialogAndWindow,,,system)
Binding(SHIFT+DEL,
ParameterizedCommand(Command(org.topcased.modeler.deleteModelObject,Delete From Model,
Allows the user to delete the selected graph element and its associated model element in a Topcased editor.,
Category(org.eclipse.ui.category.edit,Edit,null,true),
,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.window,,,system)

I then started tomcat – there were no new errors reported in the log.

[support-tony]

Kate,

I’ve talked to a developer about this and the suggestion is that WIndows 7 firewall might be interfering and that it blocks the debug port. Although it’s not clear why Tomcat would start the first time in debug mode, in that case, could you try turning off your Windows 7 firewall just to see if there is a problem there?

Thanks.

[Patrick Kates]

Sorry to disappoint but the firewall is already off via group policy.

The name is Kates, not Kate.

[Author]

Posts