Description of problem:

This worked fine until CP06 release. If a WAR or EAR file path is an UNC windows share file path then the deployment fails with file not found error. In this scenario, CLI adds an extra "s" character in the deployment path. However, the same WAR/EAR deploys fine if the path is changed to a local path.

Example:

This deployment is successful:

1. jboss-cli.bat -c --controller=$mytestserver.dot.com:9999  --command="deploy "d:\Test\Drop732863\TEST.war" --server-groups=MyHA"

However, this one fails to find the WAR file even though it exists in the same folder as above but the path is an UNC one instead of the local one:

2. jboss-cli.bat -c --controller=$mytestserver.dot.com:9999  --command="deploy "\\stlmjbad001\Test\Drop732863\TEST.war" --server-groups=MyHA"

Version-Release number of selected component (if applicable):

JBoss EAP 6.4 CP06


How reproducible:

Using a UNC path for the WAR file location on a Windows server consistently shows the same error.

Steps to Reproduce:
1. Deploy a WAR or an EAR file with a UNC path using the following CLI:

jboss-cli.bat -c --controller=$mytestserver.dot.com:9999  --command="deploy "\\stlmjbad001\Test\Drop732863\TEST.war" --server-groups=MyHA"


Actual results:

Path \\stlmjbad001\Test\Drop732863\TEST.war doesn't exist. 

Expected results:

It should deploy successfully since TEST.war exists. This worked fine until CP06 release. Same deployment when attempted on a EAP 6.4.0 CP05 instance it is successful.


Additional info:

This is preventing the customer from patching JBoss EAP 6.4.z. They have to use the Windows share paths for deployment from Jenkins.