If you have started JBoss AS 7.1.0.CR1 “standalone-full.xml” profile you must have noticed that you would be getting the below WARNING message. However as this just a warning message and would not hamper your set-up but warning is a warning, hence I had to look why this was coming up when I was starting the default “standalone-full.xml” profile thus started my investigation, if you guys remember that in earlier versions of JBoss had a similar warning which was sucker password which can be fixed by going through this article How to set JBoss Message Sucker Password in JBoss AS 6, similarly we can even fix this warning message by following the below steps.

Warning Message:

22:34:54,728 INFO  [org.apache.coyote.http11.Http11AprProtocol] (MSC service thread 1-4) Starting Coyote HTTP/1.1 on http-localhost.localdomain-
22:34:54,876 WARNING [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-5) Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default. Please see the HornetQ user guide, cluster chapter, for instructions on how to do this.
22:34:55,045 INFO  [org.jboss.as.jacorb] (MSC service thread 1-8) CORBA ORB Service Started
22:34:55,276 INFO  [org.jboss.as.jacorb] (MSC service thread 1-6) CORBA Naming Service Started

Steps to fix this warning message:

By just following the warning message say’s and add the cluster user and password for the Hornetq to overcome this issue

  1. Stop your running server
  2. Open “/jboss-as-7.1.0.CR1/standalone/configuration/standalone-full.xml” file
  3. Now just add “cluster-user” and “cluster-password” tags with its value under “hornetq-server” as shown below
  4. <hornetq-server>
      <cluster-user>admin</cluster-user>		<!-- Added this line -->
      <cluster-password>admin1</cluster-password>	<!-- Added this line -->
      <!-- disable messaging persistence -->
      <!-- Default journal file size is 10Mb, reduced here to 100k for faster first boot -->
  5. Restart your server using the below command
  6. ./standalone.sh -c standalone-full.xml

You would notice now the warning message which was coming earlier has been fixed.

Middleware Magic

If you enjoyed this post, please consider leaving a comment or subscribing to the RSS feed to have future articles delivered to your feed reader.