Introduce OpenWire v11 which adds noLocal to the SubscriptionInfo, if
configured KahaDB can store that version and the noLocal value is
recovered from the store.
Add workarounds to allow for TX work to take place in multiple sessions
on the same connection. Future work needed to properly support TXN
Capabilities defined in the spec and support checking of violations of
expected behavior.
Adding a new property on PolicyEntry called includeBodyForAdvisory which will
include the original message body when sending advisory messages that include
the original message, instead of clearing it out. This is turned off by
default.
Have the test store its data in the target folder to let the clean step
remove it and attempt to remove the data folder between runs to avoid
state derby instances.
Adding a property called schedulePeriodForDiskUsageCheck which can be set
to a time period to periodically check disk usage limits and adjust if
the amount of disk space has been reduced.
pauses the delivery of messages to the activemq session when a rollback is happening until the message has been redelivered.
patch applied with thanks to Tamas Cserveny
- added more reliable quoting
- improved reliability of stopping
- improved management of concurrent stop processes
- added a "kill" option which terminates the daemon in a rude way
Reduce the default memory minimal overhead of activemq from 1G to 64M to
ensure that activemq does not revoke to work in small environments.
If a larger process heap than 64M is needed the jvm grows up to 1GB.
Conflicts:
assembly/src/release/bin/env
This commit adds:
- some quoting of variables to prevent problems with unusual paths
- sets some default variables to prevent problems
- adds some function and helptext documentation
this adds a pidfile which contains the pid of the running shellscript if
activemq is run by "console". This prevents problems if someone tries to
to use i.e. the start/stop options while some is debugging activemq in
foreground mode.
This adds a better output for some tasks if the broker is not running.
The user gets the information that the broker is currently not running.
Users are confused if they see a java stacktrace on invoking commands -
often they do not read error output in detail.
This change respects that the script can also be used to contact remote
brokers - if ACTIVEMQ_QUEUEMANAGERURL is defined you get the regular
stacktrace, because the script cannot know about the state if a remote
broker.
In >98% of all cases this script controls local instances - we should
help the common user!