[jboss-jira] [JBoss JIRA] (WFCORE-1548) Access denied when deploying to wildfly 10

[Joey Wang (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13362787#comment-13362787 ] 

Joey Wang commented on WFCORE-1548:
-----------------------------------

We have the same issue with Wildfly 10.1.0.Final in Windows Server 2016. We excluded the Wildfly folder from Windows Defender as workaround.
Will this issue be fixed in Wildfly, or it is not a problem of Wildfly?

> Access denied when deploying to wildfly 10
> ------------------------------------------
>
>                 Key: WFCORE-1548
>                 URL: https://issues.jboss.org/browse/WFCORE-1548
>             Project: WildFly Core
>          Issue Type: Bug
>         Environment: Wildfly 10, Windows 7, java 1.8_05, maven 3.0.5, maven 3.3.9
>            Reporter: Srecko Mandelj
>            Assignee: James Perkins
>            Priority: Minor
>         Attachments: TestMavenPlugin.zip, server.log
>
>
> I have a war application containing web services. I have no problems deploying war to wildfly 8.1. After upgrade to wildfly 10, the plugin doesn't work any more. I get this error when trying to deploy:
> {code}
> [Server:server-one] 09:36:51,162 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 132) Initializing Mojarra 2.2.12-jbossorg-2 20150729-1131 for context '/ActivatorFrontEnd'
> [Server:server-one] 09:36:51,220 SEVERE [javax.enterprise.resource.webcontainer.
> jsf.config] (ServerService Thread Pool -- 132) Critical error during deployment:
>  : com.sun.faces.config.ConfigurationException: java.util.concurrent.ExecutionException: javax.faces.FacesException: java.io.FileNotFoundException: C:\podatki\jboss_configurations\wildfly10\domainController\servers\server-one\tmp\vfs\temp\temp1e3a1daf9121b0e4\content-34b685741ee5aeb4\content-6322725066713898564.tmp (Access is denied)
> {code}
> It looks like a concurrency issue - one process is trying to use a file that other process is using. If I deploy through web console or via CLI, I don't have this issue. It is somehow related to jsf implementation. If I remove jsf from wildfly configuration file (the module and subsystem), deploy works ok (Mojara is then not triggered and deploy is successful).
> I tried to deploy with 1.1.9.Alpha8, but I get the same error.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)