The minimal config is not accessible over JMX to be able to shutdown remotely. In the testsuite it's shutdown by copying to deploy a 'shutdown.sar', then removing it. At undeployment it does a shutdown (or exit?) and the server stops. It's tested just so to know it can boot properly. We usually have issues with it when things change in VFS, like file locking problems. That's why it's run with special flags to the VM. Andrew Lee Rubinger wrote: > My Hudson runs on the AS TestSuite trunk are failing because the > "minimal" config cannot be shut down via JMX. > > Reproducible locally: > > * ./run.sh -c minimal > * ./shutdown.sh -S > > The odd thing is that this isn't present (often?) in the JBossQA > environment. So I'm hesitant to comment out the "jboss-minimal-tests" > target. > > Does anyone know the history here? Is remote JMX shutdown of the > minimal config supported or expected to work? If so, why is this part > of the TestSuite? > > S, > ALR > > References (via Shelly): > * https://jira.jboss.org/jira/browse/JBAS-1109 > * https://jira.jboss.org/jira/browse/JBAS-6965 > _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development