JBossDeveloper

without some sort of test or example its difficult me to really help here.

no its not a normal situation, your not pointing both your servers at the same journal by any chance?

you said you are running 2 servers on the same machine, are they using the same journal directory?

I believe I see what is happening.  As a sanity check I started a fresh copy of EAP 6.1 using standalone-ha-full.xml and hooked up JConsole to it.  What you're looking at are the MBeans for the "messaging" subsystem and while there appear to be duplicates each of those objects is actually different even though it has the same name.  For example, if you actually inspect the two entries with the name "#" you will see that one is for security-settings and the other is for address-settings.  Likewise with the entries named "netty" - one is for the connector named "netty" the other is for the acceptor named "netty".

So from everything I can see this is normal.

I was curious so I added this to my configuration:

   <jms-destinations>

       <jms-queue name="testQueue">

           <entry name="jms/queue/test"/>

           <entry name="java:jboss/exported/jms/queue/test"/>

       </jms-queue>

   </jms-destinations>

And I also noticed 2 entries for "jms.queue.testQueue" in JConsole.  As before, both of these entries point to different resources - one for the underlying HornetQ queue and one for the underlying HornetQ address (both of which are required to implement a JMS queue in HornetQ).  If you actually inspect the MBeanInfo for the entry you'd see this.  The ObjectNames are different as well as the Descriptions.  The Description for the address even says, 'A runtime-only resource representing a HornetQ "address". Zero or more queues can be bound to a single address. When a message is routed, it is routed to the set of queues bound to the message's address.'

I already answered that question.  See above.