Description of problem:
 org.jboss.as.test.integration.domain.suites.ManagementClientContentTestCase#testRolloutPlans test is failing in domain testsuite with different JDK for master and slave.

Version-Release number of selected component (if applicable):
 EAP 6.3.0.DR4

How reproducible:
 40%

Steps to Reproduce:
1. Prepare jdks
 JDK_MASTER=/path/to/jdk1.7.0_45
 JDK_SLAVE=/path/to/jdk1.8.0_b128
2. Go to EAP testsuite directorye and run
 mvn clean test -Dts.domain -Djboss.test.host.master.controller.jvmhome=$JDK_MASTER -Djboss.test.host.slave.controller.jvmhome=$JDK_SLAVE -Dtest=DomainTestSuite -Djboss.test.host.master.jvmhome=$JDK_MASTER -Djboss.test.host.slave.jvmhome=$JDK_SLAVE -Dtest=org.jboss.as.test.integration.domain.suites.ManagementClientContentTestCase

Actual results:
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 27.271 sec <<< FAILURE!
testRolloutPlans(org.jboss.as.test.integration.domain.suites.ManagementClientContentTestCase)  Time elapsed: 0.733 sec  <<< FAILURE!
java.lang.AssertionError: expected:<bytes {
    0x27, 0x88, 0xcf, 0x01, 0x0f, 0xfa, 0xe5, 0xd8,
    0xd4, 0xb9, 0x29, 0x07, 0x59, 0x32, 0xef, 0x4c,
    0x72, 0x88, 0x8d, 0xd0
}> but was:<bytes {
    0x60, 0x6e, 0xcf, 0x23, 0x0d, 0xf6, 0x88, 0x0f,
    0xc7, 0x72, 0xcb, 0xcc, 0xe5, 0x33, 0xd6, 0xe7,
    0xf9, 0x27, 0xe8, 0xe9
}>
        at org.junit.Assert.fail(Assert.java:88)
        at org.junit.Assert.failNotEquals(Assert.java:743)
        at org.junit.Assert.assertEquals(Assert.java:118)
        at org.junit.Assert.assertEquals(Assert.java:144)
        at org.jboss.as.test.integration.domain.suites.ManagementClientContentTestCase.validateHashes(ManagementClientContentTestCase.java:244)
        at org.jboss.as.test.integration.domain.suites.ManagementClientContentTestCase.testRolloutPlans(ManagementClientContentTestCase.java:158)

Expected results:
 Test passed

Additional info:
 https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Domain-mode/job/eap6x-domain-different-JDK-DC-HC/80/ failures are random not combination specific (see run#81 has failures on different combinations)