[JBoss JIRA] (JBIDE-22075) Cannot debug OpenShift application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22075:
------------------------------------------
[~fbricon] is this something you could look at since you're the one that's most intimate with the debugging tooling?
> Cannot debug OpenShift application
> ----------------------------------
>
> Key: JBIDE-22075
> URL: https://issues.jboss.org/browse/JBIDE-22075
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Critical
> Labels: openshift_v3
>
> When I am trying to run remote debugging of an application on OpenShift I get following error
> {code}
> Failed to connect to remote VM
> com.sun.jdi.connect.spi.ClosedConnectionException
> at org.eclipse.jdi.internal.connect.SocketTransportService.readHandshake(SocketTransportService.java:222)
> at org.eclipse.jdi.internal.connect.SocketTransportService.access$7(SocketTransportService.java:214)
> at org.eclipse.jdi.internal.connect.SocketTransportService$3.run(SocketTransportService.java:185)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> I guess this is something related to port forwarding. Even the port for debugging is forwarded on a free port and it looks like started, it fails. When I stop port forwarding, start it again and use a port, which is used as a forwarded port for remote debug port, in debug configuration, it works.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22075) Cannot debug OpenShift application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-22075:
----------------------------------------
Assignee: Fred Bricon
> Cannot debug OpenShift application
> ----------------------------------
>
> Key: JBIDE-22075
> URL: https://issues.jboss.org/browse/JBIDE-22075
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Critical
> Labels: openshift_v3
>
> When I am trying to run remote debugging of an application on OpenShift I get following error
> {code}
> Failed to connect to remote VM
> com.sun.jdi.connect.spi.ClosedConnectionException
> at org.eclipse.jdi.internal.connect.SocketTransportService.readHandshake(SocketTransportService.java:222)
> at org.eclipse.jdi.internal.connect.SocketTransportService.access$7(SocketTransportService.java:214)
> at org.eclipse.jdi.internal.connect.SocketTransportService$3.run(SocketTransportService.java:185)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> I guess this is something related to port forwarding. Even the port for debugging is forwarded on a free port and it looks like started, it fails. When I stop port forwarding, start it again and use a port, which is used as a forwarded port for remote debug port, in debug configuration, it works.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22078) Error publishing war file to wildfy 10.0 on windows
by Tobias van den Berg (JIRA)
Tobias van den Berg created JBIDE-22078:
-------------------------------------------
Summary: Error publishing war file to wildfy 10.0 on windows
Key: JBIDE-22078
URL: https://issues.jboss.org/browse/JBIDE-22078
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 4.3.0.Final
Environment: - Windows 7 x64
- jdk1.8.0_77 (32-bit)
- Eclipse Mars.2 (32-bit)
- JBoss Tools 4.3.0.FINAL
- Wildfly 10.0.0.FINAL
Reporter: Tobias van den Berg
The following error is thrown after publishing a maven webapplication (.war) to Wildfly 10.0:
"Error renaming C:\wildfly-10.0.0.Final\standalone\tmp\tmp8945090880188299781.properties to C:\wildfly-10.0.0.Final\standalone\deployments\WebViewer-0.0.3-SNAPSHOT.war\META-INF\maven\nl.incad.webviewer\WebViewer\pom.properties.
This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination.
You may adjust these settings in the server editor."
The webapplication is no longer available/online after the error. The only solution is to restart the server and to re-add the webapplication to the server. This makes it very hard to develop/test a webapplication on wildfly 10. The same error is thrown on wildfly 8.0/8.1, but the difference is that the webapplication is still available/online after the error.
I've tried/tested the following:
- Checked/updated Windows file permisions for the wildfly directory
- Take ownership of the wildfly directory (recursively)
- Disabled Windows User Account Control (UAC)
- Run Eclipse as Admin
Relates to:
- JBIDE-18697
- JBIDE-17545
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22075) Cannot debug OpenShift application
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22075:
----------------------------------
Workaround Description: Stop port forwarding, start it again with different free port and use port from port forwarding for remote debugger. (was: Stop port forwarding, start it again and use port from port forwarding for debugging.)
> Cannot debug OpenShift application
> ----------------------------------
>
> Key: JBIDE-22075
> URL: https://issues.jboss.org/browse/JBIDE-22075
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Priority: Critical
> Labels: openshift_v3
>
> When I am trying to run remote debugging of an application on OpenShift I get following error
> {code}
> Failed to connect to remote VM
> com.sun.jdi.connect.spi.ClosedConnectionException
> at org.eclipse.jdi.internal.connect.SocketTransportService.readHandshake(SocketTransportService.java:222)
> at org.eclipse.jdi.internal.connect.SocketTransportService.access$7(SocketTransportService.java:214)
> at org.eclipse.jdi.internal.connect.SocketTransportService$3.run(SocketTransportService.java:185)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> I guess this is something related to port forwarding. Even the port for debugging is forwarded on a free port and it looks like started, it fails. When I stop port forwarding, start it again and use a port, which is used as a forwarded port for remote debug port, in debug configuration, it works.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21981) Error during rsync
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21981?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-21981 at 4/4/16 8:07 AM:
------------------------------------------------------------------
[~mlabuda] your new issue seems to happen in the 1st step where we sync pod -> local filesystem (in an upcoming step we then sync back local -> pod). Somehow something prevents rsync from creating a ROOT.war in the local filesystem. Do you have a folder ROOT.war already?
And yes, please open a new issue since this isnt the same issue any more.
was (Author: adietish):
[~mlabuda] your new issue seems to happen in the 1st step where we sync pod -> local filesystem (in an upcoming step we then sync back local -> pod). Somehow something prevents rsync from creating a ROOT.war in the local filesystem. Do you have a folder ROOT.war already?
> Error during rsync
> ------------------
>
> Key: JBIDE-21981
> URL: https://issues.jboss.org/browse/JBIDE-21981
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Xavier Coulon
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> While testing the debugging support on the server adapter, I got the following error:
> {code}
> Could not sync all pods to folder /Users/xcoulon/workspaces/runtime-Eclipse-mars.2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample@eap-app/deploy
> OpenShiftBinaryCapability process exited: rsync: delete_file: rmdir "/Users/xcoulon/workspaces/runtime-Eclipse-mars.2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample(a)eap-app/deploy/ROOT.war" failed: Directory not empty (66)
> rsync error: some files could not be transferred (code 23) at /SourceCache/rsync/rsync-45/rsync/main.c(1400) [generator=2.6.9]
> error: exit status 23
> {code}
> The content of the {{.../deploy}} directory was:
> {code}
> drwxr-xr-x 9 xcoulon staff 306 Mar 25 12:19 ./
> drwxr-xr-x 4 xcoulon staff 136 Mar 25 11:55 ../
> -rw-r--r-- 1 xcoulon staff 9041 Mar 27 2015 README.txt
> drwxr-xr-x 7 xcoulon staff 238 Mar 25 11:59 ROOT.war/
> -rw-r--r-- 1 xcoulon staff 8 Mar 23 17:59 ROOT.war.deployed
> -rw-r--r-- 1 xcoulon staff 8 Mar 25 12:18 ROOT.war.isdeploying
> -rw-r--r-- 1 xcoulon staff 8415373 Aug 11 2015 activemq-rar.rar
> -rw-r--r-- 1 xcoulon staff 16 Aug 11 2015 activemq-rar.rar.deployed
> -rw-r--r-- 1 xcoulon staff 16 Mar 25 12:18 activemq-rar.rar.isdeploying
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21981) Error during rsync
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21981?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21981:
------------------------------------------
[~mlabuda] your new issue seems to happen in the 1st step where we sync pod -> local filesystem (in an upcoming step we then sync back local -> pod). Somehow something prevents rsync from creating a ROOT.war in the local filesystem. Do you have a folder ROOT.war already?
> Error during rsync
> ------------------
>
> Key: JBIDE-21981
> URL: https://issues.jboss.org/browse/JBIDE-21981
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Xavier Coulon
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> While testing the debugging support on the server adapter, I got the following error:
> {code}
> Could not sync all pods to folder /Users/xcoulon/workspaces/runtime-Eclipse-mars.2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample@eap-app/deploy
> OpenShiftBinaryCapability process exited: rsync: delete_file: rmdir "/Users/xcoulon/workspaces/runtime-Eclipse-mars.2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample(a)eap-app/deploy/ROOT.war" failed: Directory not empty (66)
> rsync error: some files could not be transferred (code 23) at /SourceCache/rsync/rsync-45/rsync/main.c(1400) [generator=2.6.9]
> error: exit status 23
> {code}
> The content of the {{.../deploy}} directory was:
> {code}
> drwxr-xr-x 9 xcoulon staff 306 Mar 25 12:19 ./
> drwxr-xr-x 4 xcoulon staff 136 Mar 25 11:55 ../
> -rw-r--r-- 1 xcoulon staff 9041 Mar 27 2015 README.txt
> drwxr-xr-x 7 xcoulon staff 238 Mar 25 11:59 ROOT.war/
> -rw-r--r-- 1 xcoulon staff 8 Mar 23 17:59 ROOT.war.deployed
> -rw-r--r-- 1 xcoulon staff 8 Mar 25 12:18 ROOT.war.isdeploying
> -rw-r--r-- 1 xcoulon staff 8415373 Aug 11 2015 activemq-rar.rar
> -rw-r--r-- 1 xcoulon staff 16 Aug 11 2015 activemq-rar.rar.deployed
> -rw-r--r-- 1 xcoulon staff 16 Mar 25 12:18 activemq-rar.rar.isdeploying
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21981) Error during rsync
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21981?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21981:
----------------------------------------
Create a new one with the link to this one please.
> Error during rsync
> ------------------
>
> Key: JBIDE-21981
> URL: https://issues.jboss.org/browse/JBIDE-21981
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Xavier Coulon
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> While testing the debugging support on the server adapter, I got the following error:
> {code}
> Could not sync all pods to folder /Users/xcoulon/workspaces/runtime-Eclipse-mars.2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample@eap-app/deploy
> OpenShiftBinaryCapability process exited: rsync: delete_file: rmdir "/Users/xcoulon/workspaces/runtime-Eclipse-mars.2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample(a)eap-app/deploy/ROOT.war" failed: Directory not empty (66)
> rsync error: some files could not be transferred (code 23) at /SourceCache/rsync/rsync-45/rsync/main.c(1400) [generator=2.6.9]
> error: exit status 23
> {code}
> The content of the {{.../deploy}} directory was:
> {code}
> drwxr-xr-x 9 xcoulon staff 306 Mar 25 12:19 ./
> drwxr-xr-x 4 xcoulon staff 136 Mar 25 11:55 ../
> -rw-r--r-- 1 xcoulon staff 9041 Mar 27 2015 README.txt
> drwxr-xr-x 7 xcoulon staff 238 Mar 25 11:59 ROOT.war/
> -rw-r--r-- 1 xcoulon staff 8 Mar 23 17:59 ROOT.war.deployed
> -rw-r--r-- 1 xcoulon staff 8 Mar 25 12:18 ROOT.war.isdeploying
> -rw-r--r-- 1 xcoulon staff 8415373 Aug 11 2015 activemq-rar.rar
> -rw-r--r-- 1 xcoulon staff 16 Aug 11 2015 activemq-rar.rar.deployed
> -rw-r--r-- 1 xcoulon staff 16 Mar 25 12:18 activemq-rar.rar.isdeploying
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22075) Cannot debug OpenShift application
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22075:
---------------------------------------
This is difference in netstat output for "default free forwarded debug port" and for "new free port for forwarded debug port"
{code}[13:23:34] [mlabuda@dhcp-10-40-5-177 ~]$ netstat -vatn | grep 35734
tcp 0 0 127.0.0.1:35734 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:35734 127.0.0.1:50380 TIME_WAIT
tcp 0 0 127.0.0.1:35734 127.0.0.1:50376 TIME_WAIT
tcp 0 0 127.0.0.1:35734 127.0.0.1:50384 ESTABLISHED
tcp 0 0 127.0.0.1:35734 127.0.0.1:50382 TIME_WAIT
tcp 0 0 127.0.0.1:35734 127.0.0.1:50378 TIME_WAIT
tcp6 0 0 ::1:35734 :::* LISTEN
tcp6 0 0 127.0.0.1:50384 127.0.0.1:35734 ESTABLISHED
[13:23:39] [mlabuda@dhcp-10-40-5-177 ~]$ netstat -vatn | grep 42711
tcp 0 0 127.0.0.1:42711 0.0.0.0:* LISTEN
tcp6 0 0 ::1:42711 :::* LISTEN {code}
> Cannot debug OpenShift application
> ----------------------------------
>
> Key: JBIDE-22075
> URL: https://issues.jboss.org/browse/JBIDE-22075
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Priority: Critical
> Labels: openshift_v3
>
> When I am trying to run remote debugging of an application on OpenShift I get following error
> {code}
> Failed to connect to remote VM
> com.sun.jdi.connect.spi.ClosedConnectionException
> at org.eclipse.jdi.internal.connect.SocketTransportService.readHandshake(SocketTransportService.java:222)
> at org.eclipse.jdi.internal.connect.SocketTransportService.access$7(SocketTransportService.java:214)
> at org.eclipse.jdi.internal.connect.SocketTransportService$3.run(SocketTransportService.java:185)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> I guess this is something related to port forwarding. Even the port for debugging is forwarded on a free port and it looks like started, it fails. When I stop port forwarding, start it again and use a port, which is used as a forwarded port for remote debug port, in debug configuration, it works.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years