Version 5

    How Do I remove JBossMQ(JMS) from JBoss 4.2 and below.


    version 4.0.4, 4.0.5, 4.2.x, EAP4.2





    1. Remove the jms directory in deploy


    Assuming the default configuration in $JBOSS_HOME/server/default, remove the server/default/deploy/jms directory. However, if you attempt to start JBoss and EJB or EJB3s are enabled, you'll get an exception.  If you are using clustered jms, you will still delete the jms directory and proceed to step 2.


    2.  (if you are not clustering skip this step)Remove the jms directory in the deploy_hasingleton directory if you are using clustering.

    If you are using the all configuration or the production configuration in EAP, JMS is enabled via clustering.

    You must delete the directory $JBOSS_HOME/server/$/deploy-hasingleton/jms

    3. Remove the jars(optional)

    Remove the $JBOSS_HOME/server/$/lib/jbossmq.jar




    Now JBoss should start normally provided you don't attempt to use any JMS in your application.



    Removes All JBossMQ components from the container. This means that the container will not have access to jms services, unless you install other jms components.