[jboss-dev-forums] [Design of JBoss Admin Console] - Re: JBossMQ vs JBoss Messaging

[chilin]

The webtest reported a couple of failures running against the ?all? server configuration.  Some of the failures can be resolved by specifying the server name at run time, however the failures in the JmsPageTest are a little harder to resolve!  Basically the test was written expecting the changes made to the JBossMQ services (e.g. MessageCache, PersistenceManager, and StateManager) are hot deployable.  However with the ?all? server, the configuration files for JBossMQ are deployed under the deploy-hasingleton/jms directory.  When changes are made to the config files (e.g. hsqldb-jdbc2-service.xml, hsqldb-jdbc-state-service.xml), the new values are not reflected in the mbeans until the server is restarted.  This caused the JmsPageTest to fail while verifying the changes.

The Admin Console?s readme file does indicate the webtest must run against the ?default? server.  Looks like we?re telling the truth here!!!


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973326#3973326

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973326