[jbosstools-issues] [JBoss JIRA] (JBIDE-22145) nio WatchService possibly causing errors / locking files on windows

Nick Boldt (JIRA) issues at jboss.org
Thu Apr 19 10:15:26 EDT 2018


     [ https://issues.jboss.org/browse/JBIDE-22145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt updated JBIDE-22145:
-------------------------------
    Fix Version/s: 4.6.x
                       (was: 4.5.x)


> nio WatchService possibly causing errors / locking files on windows
> -------------------------------------------------------------------
>
>                 Key: JBIDE-22145
>                 URL: https://issues.jboss.org/browse/JBIDE-22145
>             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: Thomas Mäder
>            Priority: Critical
>             Fix For: 4.6.x
>
>         Attachments: FSWatcherHang.txt, FailureWatchModify1.PML, FileWatchError.zip, 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
(v7.5.0#75005)



More information about the jbosstools-issues mailing list