Conflicts: hornetq-server/src/main/java/org/hornetq/core/server/HornetQMessageBundle.java hornetq-server/src/main/java/org/hornetq/core/server/HornetQServerLogger.java hornetq-server/src/main/java/org/hornetq/core/server/Queue.java hornetq-server/src/main/java/org/hornetq/core/server/impl/QueueImpl.java hornetq-server/src/main/resources/schema/hornetq-configuration.xsd hornetq-server/src/test/java/org/hornetq/core/config/impl/FileConfigurationTest.java hornetq-server/src/test/java/org/hornetq/core/server/impl/ScheduledDeliveryHandlerTest.java tests/unit-tests/src/test/java/org/hornetq/tests/unit/core/postoffice/impl/FakeQueue.java
When a live and backup server are both started at or near the same moment there is a small window where the live server's acceptors have been started but the server's state != STARTED. During this window if the backup sends its announcement the announcement will fail and the backup will shutdown. This fix closes this small window by only starting the acceptors until the server is fully started. Conflicts: hornetq-server/src/main/java/org/hornetq/core/remoting/server/impl/RemotingServiceImpl.java hornetq-server/src/main/java/org/hornetq/core/server/impl/HornetQServerImpl.java
… persistent https://issues.jboss.org/browse/HORNETQ-1467 https://bugzilla.redhat.com/show_bug.cgi?id=1207707 NullStorageLargeServerMessage's method copy is not implemented. For that reason a LargeMessage would fail if copied (operation that would happen through the Bridge or Expiration)
…e topic consumer with null subscription name and non-durable topic consumer with not-null subscription name.
…Control missing methods
…n through totalIteration and Paging this goes beyond the last fix I implemented on BZ-1169781. We recently changed found https://issues.jboss.org/browse/HORNETQ-1457 which would affect the implementation on this BZ I don't take this as a back port of HQ-1457, it's really fixing my previous commit on this BZ
on the replication channel The connection-ttl and client-failure-check-period are not passed to the server locator used to create replication connection. So the fix sets the two parameters in SharedNothingBackupActivation.
…en after Paging fix Changing the order of depaging introduced an extra check that needs to be checked now. This will probably take care of the issue by checking if the page is complete before depage.
…g process Browser is not working over paged messages, and the depage process may be lazier than expected.
https://bugzilla.redhat.com/show_bug.cgi?id=1158920 https://issues.jboss.org/browse/HORNETQ-1446 The DiscoveryGroup should be resilient to failures on the communication. We shouldn't kill the Loop if an exception happened during the read of the UDP messages.