[jbertram]

Are you joking?

[soranki]

No Justin. what i meant was in which configuration or xml  file I can locate that. That was my intention.

[soranki]

As per the previous conversation above I understand   that cluster-password>  will be set in some of the xml files which is located in glog.ear

[jbertram]

No Justin. what i meant was in which configuration or xml  file I can locate that. That was my intention.

The <hornetq-server> is located in the main server configuration file (e.g. standalone-full.xml).  That is where the <cluster-password> is set.

As per the previous conversation above I understand   that cluster-password>  will be set in some of the xml files which is located in glog.ear

I don't understand what was said previously which would indicate to you that the <cluster-password> would be set in any configuration file in your application ear.

The issue here is the clustering of the HornetQ servers themselves.  It has nothing to do with your application, at least not directly.  Since the HornetQ servers are configured in the main server configuration file then that is where you need to make the configuration change.  I assumed you were familiar with the main server configuration file and that it contained the HornetQ server configuration.

[soranki]

But Justin I am not calling or not using standalone-full.xml anywhere. All I am doing to bring my application up is with the below command.

standalone.bat -c standalone-ha.xml -Djboss.node.name=NodeA -b 192.168.0.118  -Djboss.socket.binding.port-offset=100

So still do  I need to change in standalone-full.xml. I will give a try.

[jbertram]

But Justin I am not calling or not using standalone-full.xml anywhere. All I am doing to bring my application up is with the below command.

I didn't say you had to change the specific file standalone-full.xml.  I simply used that as an example of "the main server configuration file." 

Here is exactly what I said, "The <hornetq-server> is located in the main server configuration file (e.g. standalone-full.xml)."  The "e.g." there is Latin for exempli gratia which essentially means "for example."  If you are using a file named "standalone-ha.xml" as your main configuration file then you should edit "standalone-ha.xml."

However, even if you didn't understand the abbreviation "e.g." I think you would understand that the HornetQ server is configured in the main server configuration file and simply edit it.  This isn't rocket science.  It's simple server configuration.

[soranki]

I dont find any term as hornet or hornetQ in any of my standalone or standalone-ha.xml files. So Justin, Kindly bear me and walk me through this error.

[jbertram]

Are you familiar with IRC?  If so, could you log on to a freenode server and join #hornetq?  This conversation would got much more quickly there.

If you can't join IRC then please explain your entire application and server topology.

[jaysensharma]

/subsystem=messaging/hornetq-server=default:write-attribute(name=cluster-user,value=admin)
/subsystem=messaging/hornetq-server=default:write-attribute(name=cluster-password,value=adminPassword)

You can run the above CLI comands which will add the following info in the hornetQ server:

<subsystem xmlns="urn:jboss:domain:messaging:1.1">
        <hornetq-server>
            <cluster-user>admin</cluster-user>
            <cluster-password>adminPassword</cluster-password>
            ...
</subsystem>

EDIT:  Abhishek,  I did not check that the discussion went upto 2 pages.   , I replied to your comment:   Re: Getting WARN message in logs with hornetq in Jboss

Justin is right for detailed conversation like this , it is best to join the  IRC channel.

[soranki]

I really donot have much exposure towards IRC channel. And moreover justin has asked me to give explain entire application topology. So what are all that I have to put infront of him.

[soranki]

I have added below lines in my standalone-ha.xml with which the boot was not happened while starting my JBoss and hence commented. As per my understanding the hornetQ term is available in standalone-full.xml. I am nowhere calling that to start my JBoss so does it make sense if I add the below lines there (in standalone-full.xml) and call standalone-ha.xml. Please suggest what changes do I have to make in order to overcome this issue.

<subsystem xmlns="urn:jboss:domain:webservices:1.1">

            <modify-wsdl-address>true</modify-wsdl-address>

            <wsdl-host>${jboss.bind.address:127.0.0.1}</wsdl-host>

            <endpoint-config name="Standard-Endpoint-Config"/>

            <endpoint-config name="Recording-Endpoint-Config">

                <pre-handler-chain name="recording-handlers" protocol-bindings="##SOAP11_HTTP ##SOAP11_HTTP_MTOM ##SOAP12_HTTP ##SOAP12_HTTP_MTOM">

                    <handler name="RecordingHandler" class="org.jboss.ws.common.invocation.RecordingServerHandler"/>

                </pre-handler-chain>

            </endpoint-config>

        </subsystem>

<!--<subsystem xmlns="urn:jboss:domain:messaging:1.1"> 

            <hornetq-server> 

            <cluster-user>admin</cluster-user> 

            <cluster-password>bajrangbali</cluster-password> 

        </subsystem> -->

        <subsystem xmlns="urn:jboss:domain:weld:1.0"/>

    </profile>

[soranki]

I see the below in my standalone-ha.xml. So please let me know where can I make the changes inorder to fix that hornetq WARN logs.

<hornetq-server>

                <clustered>true</clustered>

                <persistence-enabled>true</persistence-enabled>

                <journal-file-size>102400</journal-file-size>

                <journal-min-files>2</journal-min-files>

                <connectors>

                    <netty-connector name="netty" socket-binding="messaging"/>

                    <netty-connector name="netty-throughput" socket-binding="messaging-throughput">

                        <param key="batch-delay" value="50"/>

                    </netty-connector>

                    <in-vm-connector name="in-vm" server-id="0"/>

                </connectors>

                <acceptors>

                    <netty-acceptor name="netty" socket-binding="messaging"/>

                    <netty-acceptor name="netty-throughput" socket-binding="messaging-throughput">

                        <param key="batch-delay" value="50"/>

                        <param key="direct-deliver" value="false"/>

                    </netty-acceptor>

                    <in-vm-acceptor name="in-vm" server-id="0"/>

                </acceptors>

                <broadcast-groups>

                    <broadcast-group name="bg-group1">

                        <group-address>231.7.7.7</group-address>

                        <group-port>9876</group-port>

                        <broadcast-period>5000</broadcast-period>

                        <connector-ref>

                            netty

                        </connector-ref>

                    </broadcast-group>

                </broadcast-groups>

                <discovery-groups>

                    <discovery-group name="dg-group1">

                        <group-address>231.7.7.7</group-address>

                        <group-port>9876</group-port>

                        <refresh-timeout>10000</refresh-timeout>

                    </discovery-group>

                </discovery-groups>

                <cluster-connections>

                    <cluster-connection name="my-cluster">

                        <address>jms</address>

                        <connector-ref>netty</connector-ref>

                        <discovery-group-ref discovery-group-name="dg-group1"/>

                    </cluster-connection>

                </cluster-connections>

                <security-settings>

                    <security-setting match="#">

                        <permission type="send" roles="guest"/>

                        <permission type="consume" roles="guest"/>

                        <permission type="createNonDurableQueue" roles="guest"/>

                        <permission type="deleteNonDurableQueue" roles="guest"/>

                    </security-setting>

                </security-settings>

                <address-settings>

                    <address-setting match="#">

                        <dead-letter-address>jms.queue.DLQ</dead-letter-address>

                        <expiry-address>jms.queue.ExpiryQueue</expiry-address>

                        <redelivery-delay>0</redelivery-delay>

                        <max-size-bytes>10485760</max-size-bytes>

                        <address-full-policy>BLOCK</address-full-policy>

                        <message-counter-history-day-limit>10</message-counter-history-day-limit>

                        <redistribution-delay>1000</redistribution-delay>

                    </address-setting>

                </address-settings>

                <jms-connection-factories>

                    <connection-factory name="InVmConnectionFactory">

                        <connectors>

                            <connector-ref connector-name="in-vm"/>

                        </connectors>

                        <entries>

                            <entry name="java:/ConnectionFactory"/>

                        </entries>

                    </connection-factory>

                    <connection-factory name="RemoteConnectionFactory">

                        <connectors>

                            <connector-ref connector-name="netty"/>

                        </connectors>

                        <entries>

                            <entry name="RemoteConnectionFactory"/>

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

                        </entries>

                    </connection-factory>

                    <pooled-connection-factory name="hornetq-ra">

                        <transaction mode="xa"/>

                        <connectors>

                            <connector-ref connector-name="in-vm"/>

                        </connectors>

                        <entries>

                            <entry name="java:/JmsXA"/>

                        </entries>

                    </pooled-connection-factory>

                </jms-connection-factories>

                <jms-destinations>

                    <jms-queue name="testQueue">

                        <entry name="queue/test"/>

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

                    </jms-queue>

                    <jms-topic name="testTopic">

                        <entry name="topic/test"/>

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

                    </jms-topic>

                </jms-destinations>

            </hornetq-server>

[jbertram]

The problem you're facing is regarding the servers in your environment that are actually running HornetQ.  You can't solve this by reconfiguring a server to run HornetQ when that server wasn't running HornetQ previously and wasn't part of the original problem.

You need to identify which servers are running HornetQ and are having trouble clustering (i.e. throwing the "Unable to validate user: HORNETQ.CLUSTER.ADMIN.USER" error).  Then you need to find the main server configuration file for those servers and modify them as both Jay and I have already very clearly described.

[soranki]

Thanks Justin for your response. As per my understanding I see standalone.xml is my main server configuration file. But I donot see any as such as HornetQ in that and hence I have moved to standalone-ha.xml in which I have found the hornetQ term and hence posted.