OK, thanks for letting us know.
Tim
On Wed, May 29, 2019, 4:03 AM emw wrote:
> Hello,
> I tried and tried and tried and I could not replicate the issues.
> I modified and I could not rescue the configuration that exploited the
> issue.
> So let's say it is not an issue.
> I will tell here and
Currently in the motion of moving our servers to EC2 and using all of Amazons
services.
I configured a AmazonMQ broker just fine. But I'm a tad confused on why the
Javascript AWS-SDK is very limited for MQ. You can't subscribe/publish,
although you can only view details about brokers and users.
T
Awesome, thank you
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
The issue is related to a dependency upgrade that changes what libraries
are required when the broker starts. The main difference here for upgrading
users like yourself is a change in the bin/artemis start script.
Before 2.8.1 there was this "if" statement:
if [ -z "$LOG_MANAGER" ] ; then
#
I've recently tried upgrading a broker created on 2.6.4 to 2.8.1 and I'm
getting the following trace upon starting it
java.lang.NoClassDefFoundError: org/wildfly/common/net/HostName
at org.jboss.logmanager.ExtLogRecord.(ExtLogRecord.java:87)
at org.jboss.logmanager.Logger.log(Logge
/One issue to be aware of is: in case of a successful fail-over, the backup's
data will be newer than the one at the live's storage. If you configure your
live server to perform a failback to live server when restarted, it will
synchronize its data with the backup's. If both servers are shutdown, t
