[jboss-dev-forums] [Design of JBoss internal QA (Test Suite)] - Re: Testsuite runs failing due to server failed startups/tim

"rachmatowicz(a)jboss.com" wrote : A similar issue was raised (JBQA-405) and the code was changed by Anil to add the class library commons-logging.jar to the stopServerClasspath(), as when exec'ing org.jboss.Shutdown, it may fail to execute due to classes it needs not being present on ths classpath. I believe this was in response to 'minimal' not shutting down, and this was a repeatble error. However, these changes made in the JIRA issue are not present in the current distribution versions. | If we were seeing the server fail to shutdown cleanly across platforms, I agree investigation of JBQA-405 would be pertinent. But since it is intermittent, I think it is more likely that the "all" server is experiencing an OOME, which prevents it from responding to the shutdown request. Have you verified that the "all" server is not experiencing an OOME by looking at the logs? "rachmatowicz(a)jboss.com" wrote : | 1. reworking the targets above to use server:start and server:stop, so that at least we have consistent behaviours being applied to stopping and starting servers. | 2. re-investigate the probelm with 'all' not shutting down, which may be sue to OOME. One approach would be to introduce TRACE statements which trace the execution of steps between a client exec'ing Shutdown, and the shutdown() request being processed on the server side. | I am in total agreement with #1. As for #2, you should be able to see the presence of an OOME just by greping the logs. If you don't see it, an OOME on the server is unlikely, IIUC. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029440#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...