April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22142) Watchers should not try to reconnect when a project has been deleted

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22142?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22142: ---------------------------------- Summary: Watchers should not try to reconnect when a project has been deleted (was: Watches should not try to reconnect when a project has been deleted) > Watchers should not try to reconnect when a project has been deleted > -------------------------------------------------------------------- > > Key: JBIDE-22142 > URL: https://issues.jboss.org/browse/JBIDE-22142 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Labels: respin-b > Fix For: 4.4.0.Alpha1 > > > When a project has been deleted from the webconsole, the watchmanager in eclipse is not notified. Each watch that times out tries to reconnect to some of the dead project's urls. Each access is rejected with 403 errors (the project could exist but not be visible to the user). > After each attempt, the watches will wait a little longer before trying to reconnect, until it eventually stops trying. > Since the watch manager has access to the projects, it can try to check the project exists before connecting the watch -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22142) Watches should not try to reconnect when a project has been deleted

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22142?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22142: ------------------------------------------ cherry-picked into master > Watches should not try to reconnect when a project has been deleted > ------------------------------------------------------------------- > > Key: JBIDE-22142 > URL: https://issues.jboss.org/browse/JBIDE-22142 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Labels: respin-b > Fix For: 4.4.0.Alpha1 > > > When a project has been deleted from the webconsole, the watchmanager in eclipse is not notified. Each watch that times out tries to reconnect to some of the dead project's urls. Each access is rejected with 403 errors (the project could exist but not be visible to the user). > After each attempt, the watches will wait a little longer before trying to reconnect, until it eventually stops trying. > Since the watch manager has access to the projects, it can try to check the project exists before connecting the watch -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22129) Watches should not try to reconnect when a project has been deleted

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22129?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22129: ------------------------------------------ merged into jbosstools-4.3.x > Watches should not try to reconnect when a project has been deleted > ------------------------------------------------------------------- > > Key: JBIDE-22129 > URL: https://issues.jboss.org/browse/JBIDE-22129 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Labels: respin-b > Fix For: 4.3.1.CR1 > > > When a project has been deleted from the webconsole, the watchmanager in eclipse is not notified. Each watch that times out tries to reconnect to some of the dead project's urls. Each access is rejected with 403 errors (the project could exist but not be visible to the user). > After each attempt, the watches will wait a little longer before trying to reconnect, until it eventually stops trying. > Since the watch manager has access to the projects, it can try to check the project exists before connecting the watch -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22142) Watches should not try to reconnect when a project has been deleted

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-22142: ---------------------------------------- Summary: Watches should not try to reconnect when a project has been deleted Key: JBIDE-22142 URL: https://issues.jboss.org/browse/JBIDE-22142 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Fred Bricon Assignee: Jeff Cantrill Fix For: 4.3.1.CR1 When a project has been deleted from the webconsole, the watchmanager in eclipse is not notified. Each watch that times out tries to reconnect to some of the dead project's urls. Each access is rejected with 403 errors (the project could exist but not be visible to the user). After each attempt, the watches will wait a little longer before trying to reconnect, until it eventually stops trying. Since the watch manager has access to the projects, it can try to check the project exists before connecting the watch -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22142) Watches should not try to reconnect when a project has been deleted

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22142?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22142: ------------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.CR1) > Watches should not try to reconnect when a project has been deleted > ------------------------------------------------------------------- > > Key: JBIDE-22142 > URL: https://issues.jboss.org/browse/JBIDE-22142 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Labels: respin-b > Fix For: 4.4.0.Alpha1 > > > When a project has been deleted from the webconsole, the watchmanager in eclipse is not notified. Each watch that times out tries to reconnect to some of the dead project's urls. Each access is rejected with 403 errors (the project could exist but not be visible to the user). > After each attempt, the watches will wait a little longer before trying to reconnect, until it eventually stops trying. > Since the watch manager has access to the projects, it can try to check the project exists before connecting the watch -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22078) Error publishing war file to wildfy 8 or above on windows

by Thomas Mäder (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22078?page=com.atlassian.jira.plugi... ] Thomas Mäder commented on JBIDE-22078: -------------------------------------- I think this is a problem in OpenJDK. I believe the scenario happening is described here: https://blogs.msdn.microsoft.com/oldnewthing/20110303-00/?p=11313 . When ReadDirectoryChangesW fails with "DELETE_PENDING", no IO is initiated. If we then wait for the IO to complete, the thread hangs. Windows IO is not my strong suit, so I might be talking out of my shiny metal .... > Error publishing war file to wildfy 8 or above on windows > --------------------------------------------------------- > > Key: JBIDE-22078 > URL: https://issues.jboss.org/browse/JBIDE-22078 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > 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 > Assignee: Rob Stryker > Priority: Critical > Labels: respin-b > Fix For: 4.3.1.CR1 > > Attachments: FailureWatchModify1.PML, FileWatchError.zip, FSWatcherHang.txt, Logfile.PML, OkWatchModify1.PML > > > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-22133) Get error "UnsupportedMediaType' when create project/applications from JBT on Mac

by Xia Zhao (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22133?page=com.atlassian.jira.plugi... ] Xia Zhao commented on JBIDE-22133: ---------------------------------- @fbricon I used this template when creating new app from local : https://raw.githubusercontent.com/openshift/origin/master/examples/sample... > Get error "UnsupportedMediaType' when create project/applications from JBT on Mac > --------------------------------------------------------------------------------- > > Key: JBIDE-22133 > URL: https://issues.jboss.org/browse/JBIDE-22133 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: JBDS 9.1.0 Beta2-v20160127-2213-B262 > Mac OS > Reporter: Xia Zhao > Assignee: Jeff Cantrill > Labels: openshift_v3 > > Get error "UnsupportedMediaType" when create project and applications from JBT on Mac -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22078) Error publishing war file to wildfy 8 or above on windows

by Thomas Mäder (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22078?page=com.atlassian.jira.plugi... ] Thomas Mäder updated JBIDE-22078: --------------------------------- Attachment: FSWatcherHang.txt Stacktrace showing the the fs watcher thread hanging when trying to release resources > Error publishing war file to wildfy 8 or above on windows > --------------------------------------------------------- > > Key: JBIDE-22078 > URL: https://issues.jboss.org/browse/JBIDE-22078 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > 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 > Assignee: Rob Stryker > Priority: Critical > Labels: respin-b > Fix For: 4.3.1.CR1 > > Attachments: FailureWatchModify1.PML, FileWatchError.zip, FSWatcherHang.txt, Logfile.PML, OkWatchModify1.PML > > > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-22140) jboss-web.xml validate problem in JBDS 8.0.0.GA.

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22140?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-22140: ----------------------------------- Assignee: Rob Stryker > jboss-web.xml validate problem in JBDS 8.0.0.GA. > ------------------------------------------------ > > Key: JBIDE-22140 > URL: https://issues.jboss.org/browse/JBIDE-22140 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Final > Reporter: xu zhang > Assignee: Rob Stryker > > Create "jboss-web.xml" from article "https://access.redhat.com/solutions/159753" in JBDS 8.0.0, error shows: > ~~~ > No grammar constraints (DTD or XML Schema) referenced in the document. > ~~~ > Customer wants JBDS to validate "jboss-web.xml" correctly. > Please let us know if it will be resolved in the next release/patch. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22140) jboss-web.xml validate problem in JBDS 8.0.0.GA.

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22140?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22140: ------------------------------------- The following works slightly better, but still not much better: {code} <?xml version="1.1" encoding="UTF-8"?> <jboss-web version="7.2" xmlns="http://www.jboss.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=" http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-web_7_2.xsd"> <context-root>/</context-root> </jboss-web> {code} The problem here is that it indicates the referenced file (jboss-web_7_2.xsd) contains validation errors, which is a very annoying issue that is very prevelant throughout the toolset and we're still working on a solution for. > jboss-web.xml validate problem in JBDS 8.0.0.GA. > ------------------------------------------------ > > Key: JBIDE-22140 > URL: https://issues.jboss.org/browse/JBIDE-22140 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.3.Final > Reporter: xu zhang > > Create "jboss-web.xml" from article "https://access.redhat.com/solutions/159753" in JBDS 8.0.0, error shows: > ~~~ > No grammar constraints (DTD or XML Schema) referenced in the document. > ~~~ > Customer wants JBDS to validate "jboss-web.xml" correctly. > Please let us know if it will be resolved in the next release/patch. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2016