Can you please clarify the exact steps you use to deploy and I will try reproducing here.
Most importantly are you using the command line interface for deployment or the admin console?
I start the domain controller with following configuration
No wars deployed
I start the host controller with following configuration
No wars deployed
All the severs belong to the main server group.
Now I upload a content(war) and try to deploy to the main server group. Then I get the above mentioned error.
I have tried other steps also. But get the same error.
PS - Is this issue related to this bug https://issues.jboss.org/browse/AS7-1608 ?
Ok, I will set something up here and see what happens.
Which AS version are you currently using?
I have just tried the scenario you described using the latest code in git and my deployment is being correctly deployed to all three servers.
From your description I did also wonder if this is related to the issue in AS7-1608 but that is specifically regarding a host controller added after the deployment has occured - from your description you are able to trigger this failure when all servers are running.
Is there any possibility of you attaching your host.xml definitions and the server logs from the failures?
I was using one windows machine as master and one mac machine as slave. I am using jboss-as-web-7.0.1.Final.
When I used two windows machines there were no problems. The applications got deployed in all servers without any issue. Does it mean that we cannot have mixed OS environment?
I am not aware of any reasons why a mixed OS environment should fail in this way, the communication between the slave and master hosts is using the same protocol that admin clients may use and those may come from a mixed environment.
I don't have access to a mac at the moment but I can try my test with a Windows machine and a Linux machine to see if that is sufficient to trigger.