Remote server over ssh does not work with cygwin ------------------------------------------------ Key: JBIDE-23431 URL: https://issues.jboss.org/browse/JBIDE-23431 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.4.2.AM2 Reporter: Martin Malina Assignee: Rob Stryker Fix For: 4.5.x Today [~rawagner] reported to me that he cannot run a remote server over ssh on Windows. So I tried it and I get the same error as him: {code} cd / cd / echo $PWD'>' echo $PWD'>' java "-Dprogram.name=JBossTools: WildFly 10.x" -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone/log/boot.log" "-Dlogging.configuration=file:/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone/configuration/logging.properties" "-Djboss.home.dir=/cygdrive/c/mmalina/wildfly-10.0.0.Final" -Dorg.jboss.logmanager.nocolor=true -jar /cygdrive/c/mmalina/wildfly-10.0.0.Final/jboss-modules.jar -mp "/cygdrive/c/mmalina/wildfly-10.0.0.Final/modules" org.jboss.as.standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base.dir=/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone& echo "JBTOOLS_SERVER_START_CMD:WildFly 10.x1478166494076:"$! Last login: Thu Nov 3 10:47:34 2016 from 10.40.4.40 0;~ jbossqa@DESKTOP-QOUU1SV ~ $ cd / 0;/ jbossqa@DESKTOP-QOUU1SV / $ 0;/ jbossqa@DESKTOP-QOUU1SV / $ cd / 0;/ jbossqa@DESKTOP-QOUU1SV / $ 0;/ jbossqa@DESKTOP-QOUU1SV / $ echo $PWD'>' /> 0;/ jbossqa@DESKTOP-QOUU1SV / $ echo $PWD'>' /> 0;/ jbossqa@DESKTOP-QOUU1SV / $ java "-Dprogram.name=JBossTools: WildFly 10.x" -Xms64m -Xmx512m -Dorg.jboss.re solver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInter val=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs= org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=/cygdrive/ c/mmalina/wildfly-10.0.0.Final/standalone/log/boot.log" "-Dlogging.configuration =file:/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone/configuration/logging. properties" "-Djboss.home.dir=/cygdrive/c/mmalina/wildfly-10.0.0.Final" -Dorg.jb oss.logmanager.nocolor=true -jar /cygdrive/c/mmalina/wildfly-10.0.0.Final/jboss -modules.jar -mp "/cygdrive/c/mmalina/wildfly-10.0.0.Final/modules" org.jboss.as .standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base.dir=/c ygdrive/c/mmalina/wildfly-10.0.0.Final/standalone& [1] 7888 0;/ jbossqa@DESKTOP-QOUU1SV / $ echo "JBTOOLS_SERVER_START_CMD:WildFly 10.x1478166494076:"$! JBTOOLS_SERVER_START_CMD:WildFly 10.x1478166494076:7888 0;/ jbossqa@DESKTOP-QOUU1SV / $ Error: Unable to access jarfile /cygdrive/c/mmalina/wildfly-10.0.0.Final/jboss-modules.jar wait 7888; echo "JBTOOLS_SERVER_LAUNCH_TERMINATED_CMD:WildFly 10.x147816649407 6:" $? [1]+ Exit 1 java "-Dprogram.name=JBossTools: WildFly 10.x" -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone/log/boot.log" "-Dlogging.configuration=file:/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone/configuration/logging.properties" "-Djboss.home.dir=/cygdrive/c/mmalina/wildfly-10.0.0.Final" -Dorg.jboss.logmanager.nocolor=true -jar /cygdrive/c/mmalina/wildfly-10.0.0.Final/jboss-modules.jar -mp "/cygdrive/c/mmalina/wildfly-10.0.0.Final/modules" org.jboss.as.standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base.dir=/cygdrive/c/mmalina/wildfly-10.0.0.Final/standalone JBTOOLS_SERVER_LAUNCH_TERMINATED_CMD:WildFly 10.x1478166494076: 1 {code} I'm not sure what's going on, /cygdrive/c/mmalina/wildfly-10.0.0.Final/jboss-modules.jar is accessible for me just fine over ssh. One may think that perhaps the java process has to use windows paths. But when I try to run ./standalone.sh in cygwin there, it works just fine. So I guess there is no reason why it shouldn't work over ssh then. We just need to figure out what's wrong.