[jbosstools-issues] [JBoss JIRA] (JBIDE-20476) "File may be locked" warning if EAR is deployed to multiple Servers
Rob Stryker (JIRA)
issues at jboss.org
Thu Aug 20 17:53:26 EDT 2015
[ https://issues.jboss.org/browse/JBIDE-20476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100434#comment-13100434 ]
Rob Stryker commented on JBIDE-20476:
-------------------------------------
This shouldn't really be causing an issue, because typically when we deploy, we create new packages of the given zip / ear / war / etc. If your server is configured for exploded filesystem deployment, we simply copy each file over into your wf deployments folder, and add a deployment marker at the end. If your server is using filesystem zipped deployment, we create a zip and then place it in deployments folder, and add a deployment marker.
If your server is configured for management deployment, we tell the appserver to deploy a given URL. IT usually does this by reading the file into memory. I've never seen this cause issues before, though, since hte original file usually remains unchanged.
Can you attach a stacktrace please? Maybe something you find in the error log.
> "File may be locked" warning if EAR is deployed to multiple Servers
> -------------------------------------------------------------------
>
> Key: JBIDE-20476
> URL: https://issues.jboss.org/browse/JBIDE-20476
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Beta2
> Environment: Eclipse Mars
> Reporter: The Alchemist
> Assignee: Rob Stryker
> Priority: Minor
>
> I have multiple Server's in my Eclipse:
> * Wildfly 8.2
> * Wildfly 9.0.1
> I have my application (two EARs) deployed to both of them, but when I try to Publish my changes, it complains in the Eclipse error log that some files might be locked so the publish was not completely successful.
> Perhaps I shouldn't have the same EARs in two apps?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the jbosstools-issues
mailing list