I think you've misunderstood something important here.
> I was not clear of the benefits of setting up a colocated backup servers
> with data replication approach.
The benefits of colocation are the same whether you use shared-store or
replication. The difference is simply how the messages get
Hi Justin,
I was not clear of the benefits of setting up a colocated backup servers
with data replication approach.
If I set up master activemq server and slave activemq server in the same
wildfly instance, then the messages will be copied from master to slave?
That does not seem to be a useful f
I tested that on windows
Le 11 août 2016 21:26, "Hassen Bennour" a écrit :
> The only things i done is to download your version, start it , connect to
> the web console with admin/admin , stopped the broker, changed the pwd,
> start the broker, retry with admin/admin and cannot log on, tried with
The only things i done is to download your version, start it , connect to
the web console with admin/admin , stopped the broker, changed the pwd,
start the broker, retry with admin/admin and cannot log on, tried with the
new password and i log on.
The only difference as i see is that you restart th
> What is the deal of setting up colocated backup servers for data replication
> approach?
I'm not clear on what you're asking here. Can you clarify your question?
> What are the use cases which we need to set up collocated backup? How to set
> it up?
Colocated backups are useful when you w
Hi,
I reverted credentials.properties to :
activemq.username=system
activemq.password=manager
guest.password=password
I reverted users.properties to :
admin=admin
The only changes that are present in jetty-realm.properties (btw
AwesomeNewPassword is not the real one, just example)
admin:Aweso
Hi,
The colocated backup servers for shared store approach is to set up a backup
server which basically read the messages that are written by another
instance of live server.
instance #1(master.1 + slave.1)
instance #2 (master.2 + slave.2)
Where the directory of slave.1 is the same as that of m
How many consumers do you have on the queue, and how many messages have
been dispatched (but not consumed) to each? And what prefetch size are
they using? The default prefetch size is 1000; any chance you have three
slow consumers that are each sitting on a full prefetch buffer?
Are you seeing t
Good to hear. Have fun.
On Thu, Aug 11, 2016 at 1:45 PM, Luca Capra wrote:
> Martyn,
> great work, I got connected and messages flows.. Thank you very much!
>
> Regards,
> Luca
>
> 2016-08-11 11:23 GMT+02:00 Martyn Taylor :
>
> > No problem. Thanks for your help in identifying the issue. The
Can you describe in more detail what the behavior you see is? How long
does the broker take to dispatch the first, second, third, etc. matching
message? Note that I'm not asking how long it takes for the message to be
consumed; if your consumer code is slow, there's nothing ActiveMQ can do
about
Martyn,
great work, I got connected and messages flows.. Thank you very much!
Regards,
Luca
2016-08-11 11:23 GMT+02:00 Martyn Taylor :
> No problem. Thanks for your help in identifying the issue. The fix is now
> merged on master you can check out the project and build it yourself.
>
> On linu
You should test the behavior both when you kill the broker (kill -9 or
equivalent) and when you stop the broker (via the shutdown script). You
may see different behavior between a hard kill and a clean shutdown...
On Aug 10, 2016 7:04 PM, "davidyce" wrote:
> hi Tim
> thank you for your response
No problem. Thanks for your help in identifying the issue. The fix is now
merged on master you can check out the project and build it yourself.
On linux:
git clone g...@github.com:apache/activemq-artemis.git
cd activemq-artemis
mvn clean install -Prelease // This will install apache-artemis in
Hello,
sorry you have reason I misspoke, I meant to add the credentials.properties as
mentioned or updated it if needed.
I done a test with a fresh download of ActiveMQ 5.11.1 and only changed the
password in the jetty-realm.properties file like you done
admin:AwesomeNewPassword, admin
, restart
Wow Martyn, thank you very much!
So it is my browser (Chrome) causing the issue. Looking forward to test you
fix.
Best
2016-08-10 14:37 GMT+02:00 Martyn Taylor :
> Hi Luca,
>
> The log message you were seeing is due to Artemis not supporting the
> websocket subprotocol ID that is getting passed
15 matches
Mail list logo
