Re: Active Durable Subscriber status automatically changing to offline Durable Subscriber [5.14.1 Most Stable Version]

[Tim Bain]

When this happens with your real-world server (in the morning or the middle
of the night), are you experiencing network partitions that result in the
subscriber really truly being offline for some period of time? If so, you
completely left that out of your initial description, and it means that
your question is actually, "Why doesn't my consumer reconnect automatically
after a network partition?" If not, why are you doing that during the test
you described here?

With 5.12.3, is SUB1 seen as offline in step 8? That is, is the only
difference in behavior between 5.12.3 and 5.14.5 what you see in Step 11,
but you see identical behavior for all other steps?

Is your consumer using a URI that uses the failover transport, to ensure it
automatically reconnects after the network connection is lost? More
generally, what URI is your client using to connect to the broker?

At what Log4J level is your webapp logging for ActiveMQ-related loggers?
What did you see when you switched them to DEBUG? I find it very surprising
that you would not see any logging by the client when you pull its network
cable; I'd expect that there'd be some logging that would occur after your
TCP session timeout elapses (did you wait that long?) and the client
figures out that it's not connected to the broker, so if you're not seeing
anything (Step 6) then I'd wonder whether you have Log4J configured
correctly.

Is there any difference between what's in the logs (either broker or
webapp) when you use the 5.14.5 client vs. when you use the 5.12.3 client?
Also, when you said you use 5.12.3 or 5.14.5 for a given test run, are you
switching both the broker and the client JARs?

Tim

On Fri, Jul 14, 2017 at 10:08 PM, tejas13  wrote:

>
> Hi,
>
> Thank you for your response. I did all setup and tested.
>
> 1] First I tested with 5.14.5 . I started active mq server on laptop L1.
> 2] I started application on laptop L2 . Both laptops are in same network
> 3] So connection established, and I found my 2 [ SUB1 and SUB2 ]
> subscribers active.
> 4] After 5 minutes I removed LAN Cable of Laptop L1 on which Active MQ
> Server is running
> 5] Still I found both subscribers are listed in Active Durable
> Subscription list
> 6] Checked in application also no error observed.
> 7] Using active mq web console I sent one message in SUB1 subscribed topic
> 8] Then SUB1 went to offline durable subscriber list.
> 9] SUB2 was in Active Subscriber list only
> 10] Then I connected LAN cable to Laptop L1.
> 11] SUB1 was offline he wont come online.
> 12] SUB2 was in active mode only and able to receive message also.
>
> After that same repeated with version 5.12.3 . In this testing I found my
> both subscribers active after network connection.
>
> Please give your inputs.
>
> Answers for your queries
>
> How long till it goes offline?
> Every morning, sometimes in mid night. Not fixed time
>
> Does it get messages up until that point?
> No message lost
>
> (Are messages even being published? You haven't described any producers in
> your test scenario; do you have any?) Are messages received continuously,
> or are there long gaps between the messages and/or bursts followed by quiet
> periods?
>
> Yes messages are produced with time interval but interval may be 5 minutes
> also or 3 hours also.
>
>
>
> Once the subscriber is offline, does it keep getting messages, or
> do they stop when it goes offline?
>
> No Subscriber doesn't receive any message. After application restart all
> message get received.
>
>
> How do you know it's offline; what
> indicator are you looking at? Does it come back to active and then go
> offline again later (maybe many times over), or does it stay offline from
> that point onward?
>
> End user stop receiving data. Then issue get reported and we come to know
> about offline case.
>
> Does your operating system show the socket (the same
> socket) as still being open after the subscriber goes offline? (You could
> use netstat to determine this, if you're on Linux.)
>
> We are using windows server
>
> Is this behavior easily and quickly reproducible with a minimum of code? Is
> it possible to package up your test scenario (broker configs, producer
> code, consumer code - anything beyond what you've shown here) so someone
> else could quickly reproduce the behavior on their own machine, or does
> this require so much infrastructure and/or time that it's not possible for
> someone else to reproduce?
>
> Yes anyone can do it. Just need 2 machines. One for active mq server and
> one for application. Application is web application deployed in tomcat
> server.
>
>
> Currently team is restarting tomcat so application get restarted and
> activemq connection get reestablished. Please help me as we recently
> upgraded active mq version and application is running in production
> environment.
>
>
> Thanks & Regards,
> Tejas Ramchandra Sawant
> Tata Consultancy Services Ltd.
> QBPL, Phase-2, Hinjewadi
> Pune, Maharashtra.
> cell : 

Re: Transport failed, attempting to automatically reconnect due to: java.io.EOFException

[Tim Bain]

Details of the inactivity monitor are at
http://activemq.apache.org/activemq-inactivitymonitor.html. It's on by
default, so if you haven't modified any settings related to it, it should
be working correctly.

An EOFException typically means that something closed the TCP connection.
Often it's the program on the other end (if you're seeing this in the
client, then the broker may have closed it, or vice versa), so check that
program's logs to see if they tell you anything. It can also happen because
the other process was hard-killed (kill -9), or because a firewall between
the broker and the client killed the connection, or probably other things
as well.

If it happens infrequently and your clients reconnect to the broker and
resume processing without incident, then you can safely ignore it if you
want. If you don't want to ignore it and you want to dig into what's going
on, I'd start with both logs (client and broker), and if you can't see
anything in them then I'd probably try using WireShark to figure out what's
going on at the TCP layer and then go from there.

Tim

On Fri, Jul 14, 2017 at 7:13 PM, akpuvvada  wrote:

> I have not configured any inactivity monitoring. How can I check if any
> exists by default?
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/Transport-failed-attempting-to-automatically-
> reconnect-due-to-java-io-EOFException-tp2351687p4728568.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Re: Active Durable Subscriber status automatically changing to offline Durable Subscriber [5.14.1 Most Stable Version]

[tejas13]

Hi,

Thank you for your response. I did all setup and tested.

1] First I tested with 5.14.5 . I started active mq server on laptop L1.
2] I started application on laptop L2 . Both laptops are in same network
3] So connection established, and I found my 2 [ SUB1 and SUB2 ] subscribers 
active.
4] After 5 minutes I removed LAN Cable of Laptop L1 on which Active MQ Server 
is running
5] Still I found both subscribers are listed in Active Durable Subscription list
6] Checked in application also no error observed.
7] Using active mq web console I sent one message in SUB1 subscribed topic
8] Then SUB1 went to offline durable subscriber list.
9] SUB2 was in Active Subscriber list only
10] Then I connected LAN cable to Laptop L1.
11] SUB1 was offline he wont come online.
12] SUB2 was in active mode only and able to receive message also.

After that same repeated with version 5.12.3 . In this testing I found my both 
subscribers active after network connection.

Please give your inputs.

Answers for your queries

How long till it goes offline? 
Every morning, sometimes in mid night. Not fixed time

Does it get messages up until that point? 
No message lost

(Are messages even being published? You haven't described any producers in 
your test scenario; do you have any?) Are messages received continuously, 
or are there long gaps between the messages and/or bursts followed by quiet 
periods? 

Yes messages are produced with time interval but interval may be 5 minutes also 
or 3 hours also.



Once the subscriber is offline, does it keep getting messages, or 
do they stop when it goes offline? 

No Subscriber doesn't receive any message. After application restart all 
message get received.


How do you know it's offline; what 
indicator are you looking at? Does it come back to active and then go 
offline again later (maybe many times over), or does it stay offline from 
that point onward? 

End user stop receiving data. Then issue get reported and we come to know about 
offline case.

Does your operating system show the socket (the same 
socket) as still being open after the subscriber goes offline? (You could 
use netstat to determine this, if you're on Linux.) 

We are using windows server

Is this behavior easily and quickly reproducible with a minimum of code? Is 
it possible to package up your test scenario (broker configs, producer 
code, consumer code - anything beyond what you've shown here) so someone 
else could quickly reproduce the behavior on their own machine, or does 
this require so much infrastructure and/or time that it's not possible for 
someone else to reproduce? 

Yes anyone can do it. Just need 2 machines. One for active mq server and one 
for application. Application is web application deployed in tomcat server. 
 

Currently team is restarting tomcat so application get restarted and activemq 
connection get reestablished. Please help me as we recently upgraded active mq 
version and application is running in production environment.


Thanks & Regards,
Tejas Ramchandra Sawant
Tata Consultancy Services Ltd.
QBPL, Phase-2, Hinjewadi
Pune, Maharashtra.
cell : +91-8055946458
Mailto: tejas.sawa...@tcs.com
Website:http://www.tcs.com


Experience certainty.IT Services
  Business Solutions
  Consulting
 


-"Tim Bain [via ActiveMQ]"  wrote: 
-
To: tejas13 
From: "Tim Bain [via ActiveMQ]" 
Date: 07/13/2017 09:31AM
Subject: Re: Active Durable Subscriber status automatically changing to offline 
Durable Subscriber [5.14.1 Most Stable Version]

If you haven't already, I'd turn logging up to DEBUG on both the broker and 
your client and see if there is any useful information in either log at the 
time that the state changes. 

Also, can you characterize in more detail what happens to the consumer 
during the test? Presumably it starts in an active state, but then what? 
How long till it goes offline? Does it get messages up until that point? 
(Are messages even being published? You haven't described any producers in 
your test scenario; do you have any?) Are messages received continuously, 
or are there long gaps between the messages and/or bursts followed by quiet 
periods? Once the subscriber is offline, does it keep getting messages, or 
do they stop when it goes offline? How do you know it's offline; what 
indicator are you looking at? Does it come back to active and then go 
offline again later (maybe many times over), or does it stay offline from 
that point onward? Does your operating system show the socket (the same 
socket) as still being open after the subscriber goes offline? (You could 
use netstat to determine this, if you're on Linux.) 

Is this behavior easily and quickly reproducible with a minimum of code? Is 
it possible to package up your test 

Re: Active MQ - Performance with CLIENT Ack

[Tim Bain]

Is your workflow process-ack-process-ack-process-ack (one message at a time
immediately followed by acking that one message, in a single thread)? If
so, I'd expect your processing to be slower than if you only acknowledge
every Nth message, though I'm not sure how significant of a performance
impact I'd expect that to be.

Can you describe in more detail what you're actually observing? Are you
slowly but correctly consuming messages (i.e. this is a performance problem
but not a correctness problem)? Or is the problem that messages are not
being acknowledged at all (none, zip, zero), which makes this a correctness
problem? You've described both types of problem in your description, but
any problem is by definition only one or the other, and knowing what the
actual problem is will help us focus on what's actually wrong.

Tim

On Fri, Jul 14, 2017 at 6:54 PM, akpuvvada  wrote:

> We are testing it from Tibco Business Works. We configured the JMS
> Connection
> using JNDI.
>
> With auto acknowledged we did not see any issues. Everything worked fine.
>
> We are testing queues. Topics are also in scope for the testing, have not
> started yet.
>
> I did not configure prefetch, using the default which as per documentation
> is 1000.
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/Active-MQ-Performance-with-CLIENT-Ack-tp4728551p4728566.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Re: Active MQ - Master/Slave Config Not working

[Tim Bain]

Is the shared drive using a filesystem where distributed exclusive locks
work correctly and reliably? NFSv4 is safe, NFSv3 isn't, and some others
work while others don't.
http://activemq.apache.org/shared-file-system-master-slave.html has some
details, though it's hardly an exhaustive list of all the shared filesystem
that exist.

If your exclusive locks are working, the slave broker will fail to start
(well, it'll start, but you'll see logs saying it's waiting to acquire the
lock, and it won't accept any connections). If both brokers come up and
accept connections at the same time, you don't have a master/slave pair,
and you need to figure out why not before you can go any further with
master/slave.

Tim

On Fri, Jul 14, 2017 at 7:10 PM, akpuvvada  wrote:

> Hi Tim,
>
> The paths configured for Kaha DB and data in broker attributes are same for
> both instances - pointing to the same folder on the shared drive.
> Anything else needs to be changed/added?
>
> Thanks
> Anil
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/Active-MQ-Master-Slave-Config-Not-working-
> tp4728550p4728567.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Re: Active MQ - runtimeConfigurationPlugin - Set Message Priority - Not working

[Tim Bain]

I finally got some time to dig into the code, and discovered that the
PolicyEntry.update() and PolicyEntry.baseUpdate() methods (
https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=blob;f=activemq-broker/src/main/java/org/apache/activemq/broker/region/policy/PolicyEntry.java;h=5b7ff0e184b9e6b4be6cf61ebcacc0a845bb1a6c;hb=HEAD)
don't attempt to set any of the three properties you're passing in.

I don't have any insight into why they wouldn't; maybe there's some reason
I'm not aware of why those specific attributes can't be updated (in which
case, we should document that on the wiki so users like you don't have to
find this out the hard way), but more likely they were just an oversight.
Can you please submit a bug in JIRA requesting that those attributes be set
when the policy entry is reloaded?

Thanks,
Tim

On Fri, Jul 14, 2017 at 6:48 PM, akpuvvada  wrote:

> Sorry, Tim. I miss understood your previous question.
> If I restart with the policy configured, the property is getting applied
> and
> it is working as expected. It is only not happening if I try to have it
> updated at runtime.
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/Active-MQ-runtimeConfigurationPlugin-Set-Message-Priority-Not-
> working-tp4728264p4728565.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Re: Transport failed, attempting to automatically reconnect due to: java.io.EOFException

[akpuvvada]

I have not configured any inactivity monitoring. How can I check if any
exists by default?



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Transport-failed-attempting-to-automatically-reconnect-due-to-java-io-EOFException-tp2351687p4728568.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Active MQ - Master/Slave Config Not working

[akpuvvada]

Hi Tim,

The paths configured for Kaha DB and data in broker attributes are same for
both instances - pointing to the same folder on the shared drive.
Anything else needs to be changed/added?

Thanks 
Anil



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Active-MQ-Master-Slave-Config-Not-working-tp4728550p4728567.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Active MQ - Performance with CLIENT Ack

[akpuvvada]

We are testing it from Tibco Business Works. We configured the JMS Connection
using JNDI.

With auto acknowledged we did not see any issues. Everything worked fine.

We are testing queues. Topics are also in scope for the testing, have not
started yet.

I did not configure prefetch, using the default which as per documentation
is 1000.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Active-MQ-Performance-with-CLIENT-Ack-tp4728551p4728566.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Active MQ - runtimeConfigurationPlugin - Set Message Priority - Not working

[akpuvvada]

Sorry, Tim. I miss understood your previous question. 
If I restart with the policy configured, the property is getting applied and
it is working as expected. It is only not happening if I try to have it
updated at runtime.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Active-MQ-runtimeConfigurationPlugin-Set-Message-Priority-Not-working-tp4728264p4728565.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: [ActiveMQ 6.0] Will ActiveMQ 6.0 will be released on Artemis codebase?

[Christopher Shannon]

Yes Artemis is being actively developed  and is the primary focus while the
old ActiveMQ 5.x line is mostly just maintenance mode at this point.  The
intention is that Artemis is the successor regardless of whether it keeps
the name Artemis or is renamed at some point.  In my opinion if you are
starting a new project I would use Artemis as that is where all current
development focus is and what will be actively maintained and improved in
the future.

On Fri, Jul 14, 2017 at 10:59 AM, Clebert Suconic  wrote:

> ...there's a lot of activity on Artemis with new code and features
> added each day.
>
>
> On Fri, Jul 14, 2017 at 3:20 AM, kkott00  wrote:
> > As it have been reported before  here
> >    Artemis become
> > successor of ActiveMQ line. Is it still actual? Is there  migration plan
> > expected? Should I prefer Artemis for new projects than ActiveMQ?
> >
> >
> >
> > --
> > View this message in context: http://activemq.2283324.n4.
> nabble.com/ActiveMQ-6-0-Will-ActiveMQ-6-0-will-be-released-
> on-Artemis-codebase-tp4728543.html
> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
>
> --
> Clebert Suconic
>

Re: [ActiveMQ 6.0] Will ActiveMQ 6.0 will be released on Artemis codebase?

[Clebert Suconic]

...there's a lot of activity on Artemis with new code and features
added each day.


On Fri, Jul 14, 2017 at 3:20 AM, kkott00  wrote:
> As it have been reported before  here
>    Artemis become
> successor of ActiveMQ line. Is it still actual? Is there  migration plan
> expected? Should I prefer Artemis for new projects than ActiveMQ?
>
>
>
> --
> View this message in context: 
> http://activemq.2283324.n4.nabble.com/ActiveMQ-6-0-Will-ActiveMQ-6-0-will-be-released-on-Artemis-codebase-tp4728543.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.



-- 
Clebert Suconic

[ActiveMQ 6.0] Will ActiveMQ 6.0 will be released on Artemis codebase?

[kkott00]

As it have been reported before  here
   Artemis become
successor of ActiveMQ line. Is it still actual? Is there  migration plan
expected? Should I prefer Artemis for new projects than ActiveMQ?



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/ActiveMQ-6-0-Will-ActiveMQ-6-0-will-be-released-on-Artemis-codebase-tp4728543.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Transport failed, attempting to automatically reconnect due to: java.io.EOFException

[Tim Bain]

Are you using the inactivity monitor on the connection?

On Jul 14, 2017 2:54 AM, "akpuvvada"  wrote:

> We are also facing the same issue.
> I have two Active MQ Brokers on different machine configured as configured
> as Master/Slave using shared store.
> We are suing the current release version.
> Transport (tcp://localhost:61616) failed , attempting to
> automatically
> reconnect: java.io.EOFException
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/Transport-failed-attempting-to-automatically-
> reconnect-due-to-java-io-EOFException-tp2351687p4728544.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Re: Active MQ - Master/Slave Config Not working

[Tim Bain]

By default, the failover transport attempts to connect to the child URIs in
order. That doesn't mean it considers the first one to be the master, just
that it tries the first one first.

When the client doesn't attempt to connect to the secondary broker, that
means it's successfully connecting to the first broker. That means that
either the first broker failed to shut down (the logs may tell you why), or
it shut down fine but you brought it back up and it failed to detect that
the second broker was the master (which would mean you haven't set up the
shared filesystem KahaDB correctly).

Tim

On Jul 14, 2017 5:12 AM, "akpuvvada"  wrote:

> I observed an issue with the Fault Tolerance configuration:
> When the primary/master is down, clients are not able to reconnect to the
> secondary on retry; it is throwing a warning and trying to reconnect. Also,
> it is considering the first URL as Master and first trying to connect to
> and
> fall back is not working even if we stop the Master and restart the client.
> The fail-over URL has to be changed to make the connection work such that
> the Machine 2 (current master) tcp URL is the first one.
>
> I configured the Fault Tolerance as per
> http://activemq.apache.org/shared-file-system-master-slave.html
> Shared File System -
> 
>   
> 
>
> Please help me identify where I am ding wrong.
> I am using URL : failover:(tcp://host1:61616,tcp:/host2:61616)
>
> Appreciate any help.
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/Active-MQ-Master-Slave-Config-Not-working-tp4728550.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Re: Active MQ - Performance with CLIENT Ack

[Tim Bain]

1MB payloads are pretty big. I'm not sure that is affecting the behavior
you're seeing, but it stands out as unusual.

Since you say the messages are not being acked, can you show us the code
that attempts to send those acks? And are we talking about queues or
topics?

Are the performance characteristics normal/expected if you use auto-ack?

What prefetch buffer size are you using for your clients?

Tim

On Jul 14, 2017 5:18 AM, "akpuvvada"  wrote:

> I am trying to test Active MQ for Performance
> I have installed it in Unix in 'Shared File System' Fault Tolerant pair.
> Max Heap Size is 3 GB
> 4GB Persistence Store Size
> 2Gb Temporary Store Size
>
> I am trying to publish messages with 'Non_Persistent' Delivery mode with
> Payload of size 1 MB without any delay in a loop - 10K messages.
> I am trying to consume the messages with Clinet ACK and acknowledging after
> logging the receipt of message.
>
> Prouder has published 3k+ messages and slowed down as Temp Store size is
> only 2GB.
>
> However, Subscriber is consuming the messages at a very slow rate and not
> acknowledging or Active MQ is not processing the acknowledgements.
>
> Please advise what I am doing wrong or what should be changed to improve
> the
> performance?
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/Active-MQ-Performance-with-CLIENT-Ack-tp4728551.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Re: Active MQ - runtimeConfigurationPlugin - Set Message Priority - Not working

[Tim Bain]

To make sure I'm understanding your answer: when you *restart* the broker,
you see a log line saying that the broker applied your configuration, but
it doesn't have the desired effect. Is that what you're saying?

On Jul 14, 2017 5:07 AM, "akpuvvada"  wrote:

> No, Tim.
> I can see an update in the log that the configuration is updated, however
> the policy is not getting applied. When seen in JConsole, the detestation
> property is not showing as set.
>
> Thanks
> Anil
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/Active-MQ-runtimeConfigurationPlugin-Set-Message-Priority-Not-
> working-tp4728264p4728549.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Active MQ - Performance with CLIENT Ack

[akpuvvada]

I am trying to test Active MQ for Performance
I have installed it in Unix in 'Shared File System' Fault Tolerant pair.
Max Heap Size is 3 GB
4GB Persistence Store Size
2Gb Temporary Store Size

I am trying to publish messages with 'Non_Persistent' Delivery mode with
Payload of size 1 MB without any delay in a loop - 10K messages.
I am trying to consume the messages with Clinet ACK and acknowledging after
logging the receipt of message.

Prouder has published 3k+ messages and slowed down as Temp Store size is
only 2GB.

However, Subscriber is consuming the messages at a very slow rate and not
acknowledging or Active MQ is not processing the acknowledgements.

Please advise what I am doing wrong or what should be changed to improve the
performance?



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Active-MQ-Performance-with-CLIENT-Ack-tp4728551.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Active MQ - Master/Slave Config Not working

[akpuvvada]

I observed an issue with the Fault Tolerance configuration:
When the primary/master is down, clients are not able to reconnect to the
secondary on retry; it is throwing a warning and trying to reconnect. Also,
it is considering the first URL as Master and first trying to connect to and
fall back is not working even if we stop the Master and restart the client.
The fail-over URL has to be changed to make the connection work such that
the Machine 2 (current master) tcp URL is the first one.

I configured the Fault Tolerance as per
http://activemq.apache.org/shared-file-system-master-slave.html
Shared File System - 

  


Please help me identify where I am ding wrong.
I am using URL : failover:(tcp://host1:61616,tcp:/host2:61616)

Appreciate any help.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Active-MQ-Master-Slave-Config-Not-working-tp4728550.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Active MQ - runtimeConfigurationPlugin - Set Message Priority - Not working

[akpuvvada]

No, Tim.
I can see an update in the log that the configuration is updated, however
the policy is not getting applied. When seen in JConsole, the detestation
property is not showing as set.

Thanks
Anil



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Active-MQ-runtimeConfigurationPlugin-Set-Message-Priority-Not-working-tp4728264p4728549.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Transport failed, attempting to automatically reconnect due to: java.io.EOFException

[akpuvvada]

We are also facing the same issue.
I have two Active MQ Brokers on different machine configured as configured
as Master/Slave using shared store.
We are suing the current release version.
Transport (tcp://localhost:61616) failed , attempting to automatically
reconnect: java.io.EOFException 



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Transport-failed-attempting-to-automatically-reconnect-due-to-java-io-EOFException-tp2351687p4728544.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.