JBossDeveloper

I have run the scenario you specified and did not get the OOM, however i used visualvm and did notice that the memory levels did start to rise and also GC happened on a smaller and smaller frequency, however on my machine it would probably take a long time before I had an issue. It happens on your machine probably because of your env, however saying that this is probably an issue we need to look at.

What we think is happening is this, when a node goes down the clustered bridge will keep trying to reconnect, at this point it depages messages, if it fails then these are repaged, so you get into an cycle where depending on processor speed and disc speed the garbage collector can't keep up, look at the following piece of code:

while(true)

{

String s = "a big string";

s = null;

}

If the objects are created faster than the GC can collect them you may have issues.

We will keep investigating but for now a few points:

There are 2 things you can do, firstly bring the other node backup or configure a backup server, this will stop the bridge trying to reconnect. Alternatively, set reconnectAttempts on the cluster connection to something other than -1, this will also stop the bridge from trying to reconnect by closing it )detaching it from the cluster).

One last thing, although its great that you gave us an easy reproducable (we wish all people would do this) I see it uses spring. From experience this usually muddies the water, for instance i'm assuming from the senderContect xml that there are 100 connection shared between the 2 nodes? What Is uncertain is how Spring handles things when 50 of these are disconnected, are they recreated to the other node, closed etc etc, any chance if you still have issues you could give us a pure JMS client?

Hi, I am also seeing the same Illegal State Exception messages in my log. I have already posted this in disucssion https://community.jboss.org/message/755529. We are using hornetq(JMS) using JBOSS AS 7.1.1. We are not using MDB. When we try to start our jboss servers in multiple physical systems, we get this. The last system that starts gets this message. I even tried this in the configuration, still facing the same issue,...we dont need to deploy any application, jsut starting the server itself I am getting this.

                    <connection-factory name="InVmConnectionFactory">

                        <connectors>

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

                        </connectors>

                        <entries>

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

                        </entries>

                        <connection-ttl>-1</connection-ttl>

                        <retry-interval>1000</retry-interval>

                        <retry-interval-multiplier>1.5</retry-interval-multiplier>

                        <max-retry-interval>60</max-retry-interval>

                        <reconnect-attempts>100</reconnect-attempts>

                    </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-ttl>-1</connection-ttl>

                        <retry-interval>1000</retry-interval>

                        <retry-interval-multiplier>1.5</retry-interval-multiplier>

                        <max-retry-interval>60000</max-retry-interval>

                        <reconnect-attempts>1000</reconnect-attempts>

                    </connection-factory>

Can you please help me on this. It says the Remote queue is already bound. For all the queue and topic we are using it is saying the same message,

[server=HornetQServerImpl::serverUUID=a2faeb49-edcc-11e1-a95d-45205e0dc74b]]@16a4847b, isClosed=false, firstReset=true]::Remote queue binding jms.queue.expiryQueuea2faeb49-edcc-11e1-a95d-45205e0dc74b has already been bound in the post office. Most likely cause for this is you have a loop in your cluster due to cluster max-hops being too large or you have multiple cluster connections to the same nodes using overlapping addresses

Aftet this whatever ERROR message you have put up here is coming up.

org.hornetq.core.server.cluster.impl.ClusterConnectionImpl - Failed to handle message

java.lang.IllegalStateException: Cannot find binding for jms.queue

Will you please help me fixing this. If it is something environment, what it can be ?