I - Removing note about deprecated properties. Our configs are using it
II - useNIO property is irrelevant since we always use NIO now with the new netty
In some cases the ID Generator will be called after the JournalStorage was stopped.
AS a result you could have cases where the ID generator is called and the journal storage is stopped.
Also I added some check to IDs and added some code to cleanup old IDS on the BatchIDManager
Specifies unique host and port variable names in each acceptor. In
addition this patch sets default runtime parameters and replaces bash
specific `source` command with posix compliant `.`
This is so we would catch compilation failures on the testsuite.
Devs are now using the release profile. Not having the tests on the
release profile would give devs and contributors the impression
that everything compiled ok
I have changed the OpenOffice files. Exported the pictures
As I exported the pictures I selected the group on the slide,
File->Export, JPG file, and selected selection only.
The size was the default size and that worked alright.
The TransactionFailoverExample IDs are not really unique if the journal is not cleaned up
This commit will make the IDs to use an UUID so the ID will always be unique even if you reuse the journal
Linux support only. Allows users to define java args and a number of other
runtime configuration parameters outside of the run scripts. This will
be followed up with support for cmd.
Some of the distribution configuration files were outdated, using the
old configuration format. This patch updates the config to allow the
server to parse and run accordingly.
Updates the out of the box configuration files as shipped with the
distribution. Changes the default connector to use port 61616 to aid
migration of ActiveMQ 5.x clients. Configures acceptors with port and
protocol as follows:
61616: Core protocol, OpenWire, STOMP, AMQP
5445: Core Protocol, STOMP (aimed at legacy HornetQ clients)
5672: AMQP
61613: Stomp
A bug was recently discovered on a legacy HornetQ branch. ActiveMQ 6
doesn't suffer from the same problem, but the test is still valuable.
The HornetQ issue is described on
https://bugzilla.redhat.com/show_bug.cgi?id=1193085.
jbertram
Martyn Taylor
Andy Taylor
Clebert Suconic
Andy Taylor