I think I've found the code that results in this behavior.
DurableTopicSubscription.unmatched() is called when a message fails to
match a selector for a given consumer, and it calls
Destination.acknowledge() which eventually calls
DefaultJDBCAdapter.doSetLastAck(). My suspicion is that this method
https://github.com/apache/activemq/commit/7d30b5cedafe8abb0daaec295dcf850f0c63b8ae#diff-55ede8f17775e966f880f650905ce820
is the commit where it was removed, which apparently happened in 5.12.0.
I can't find any JIRA issue or pull request specifically related to
removing the script and the commit
Networks of brokers with only dynamically included destinations will only
forward messages when a consumer is present; otherwise, the messages will
stay on the broker to which they were published (BrokerA, in your example)
until a consumer connects to another broker in the network. But if you do
Francois,
I think you're misunderstanding a few things, so let me try to explain more
fully and then respond to your questions.
In ActiveMQ, there are three places messages are stored.
1. The persistence store. All persistent messages are stored here. May
be backed by a SQL database, a
I've submitted https://issues.apache.org/jira/browse/AMQ-6864 to capture
this.
However, the fix on our end that I advocated in that JIRA issue will be to
specify a JVM argument such as --add-exports in our start scripts, so if
your security team is going to have a problem with that approach,
Hi Tim,
Thank you for your respone.
Can you please raise a Jira as I dont have access to it.
And also please let me know when will the support be available, as we have a
release of our software planned with JRE 9 support and using --add-exports
option may not be permissible.
Please let me know
Thanks, gtully!
Is our implementation for #1 correct? The assumption is by disabling removal
of inactive virtual destination queues, we effectively make them static
queues the moment they are created. So, assuming a producer publishes to
"topic://virtualTopics.mytopic" on BrokerA, if BrokerB has
Do those errors occur on the client or the broker? Are there any relevant
lines in the other one's log?
This has been previously seen at least once (
https://stackoverflow.com/questions/27768919/in-my-activemq-config-i-have-problems-with-the-udp-and-http-protocols),
but there was apparently no
That's great, thank you.
Although we welcome all bug reports, we especially appreciate when the
submitter provides a detailed analysis and/or a test to reproduce the
problem, so thank you for that.
Tim
On Nov 15, 2017 8:54 AM, "tpavelka" wrote:
> Thanks for the
Thank you Eric,
That was the issue indded. Changing GC algorithm helped dramatically reduce
memory consumption.
Abhinav SUryawanshi
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
On Wed, Nov 15, 2017 at 2:22 PM, Christopher Shannon
wrote:
> Also, I should add that if a bunch of people think it's better to rename
> Artemis to ActiveMQ 6 then that is fine too. My opinion about keeping it
> as Artemis is it would be easier but if people feel
My personal two cents is
I think of 5.x as ActiveMQ Classic.
And the next gen is ActiveMQ Artemis which has its own versioning.
really it’s the Message outwards to user that just needs updating and being
clear IMO.
Cheers
Mike
Sent from my iPhone
> On 15 Nov 2017, at 22:22, Christopher
Also, I should add that if a bunch of people think it's better to rename
Artemis to ActiveMQ 6 then that is fine too. My opinion about keeping it
as Artemis is it would be easier but if people feel strongly about making
it ActiveMQ 6 and want to do the work to rename everything that is fine
with
Not trying to push any directions here. But just wanted to point out that
Artemis could just be a codename. That would still allow a next version to
be whatever we want and change docs only.
On Wed, Nov 15, 2017 at 10:42 AM Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:
> I think
Thanks for the confirmation, I have opened
https://issues.apache.org/jira/browse/AMQ-6863 and added a Java class that
reproduces the issue.
Tomas
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
I think it's pretty clear at this point that Artemis is the future.
However, I don't know that renaming it to ActiveMQ 6 makes any sense as it
would be a lot of work and more confusion.
My opinion would be to just have the roadmap say Artemis is the future and
recommended broker and drop plans to
any progress?
On Tue, Nov 14, 2017 at 11:15 AM, ipolevoy wrote:
> Clebert, thank you for your help. Enjoy your vacation, we will be looking
> closer, and if cannot resolve I will ping you in a few days.
>
> Thank you,
>
>
>
>
> --
> Sent from:
On 11/15/2017 10:04 AM, Jiri Danek wrote:
On Wed, Nov 15, 2017 at 3:59 PM, Justin Bertram wrote:
Ultimately I believe the decision is in the hands of the ActiveMQ PMC [1].
Where can I find a list of PMC members for ActiveMQ? The closest I got to
it is
> Where can I find a list of PMC members for ActiveMQ?
http://people.apache.org/committers-by-project.html#activemq-pmc
Justin
On Wed, Nov 15, 2017 at 9:04 AM, Jiri Danek wrote:
> On Wed, Nov 15, 2017 at 3:59 PM, Justin Bertram
> wrote:
>
> >
On Wed, Nov 15, 2017 at 3:59 PM, Justin Bertram wrote:
> Ultimately I believe the decision is in the hands of the ActiveMQ PMC [1].
>
Where can I find a list of PMC members for ActiveMQ? The closest I got to
it is http://activemq.apache.org/team.html
--
Jiri Daněk
Ultimately I believe the decision is in the hands of the ActiveMQ PMC [1].
Justin
[1] http://www.apache.org/dev/pmc.html#what-is-a-pmc
On Wed, Nov 15, 2017 at 7:59 AM, Tim Bain wrote:
> I'm also curious about who gets to make the decision about what the future
>
Hi Guys,
I am trying to use ActiveMQ with HTTP transport. After setting up the
broker, when I tried to send msgs and I got the following exceptions: After
debugging, the exception occured during "connection.start()".
Thanks a lot in advance
The apache-activemq-5.9.0 is used. I have HTTPclient
I'm also curious about who gets to make the decision about what the future
direction is for the project. Nominally it's probably "the community", but
that's rather abstract, so I'd like to know what the process is by which
the decision will be made and who gets to provide what inputs into the
#2 is a problem - when the name of the subscription queue will be unknown.
If you know the names in advance then statically creating the destinations
will work.
You could go down the plugin route and implement/manage a shared
retroactive queue SRQ
Intercept send to the virtual topic to forward a
A few recent interactions with confused users has caused me some concern
about the clarity, or lack thereof, regarding the future of ActiveMQ. In
short, I think users don't really understand where ActiveMQ is going in the
future so they don't know which broker to use for new projects or if they
Checking in just to confirm that same issue was encountered while building on
Ubuntu 16.04 and openssl 1.0.2
Fixed by replacing as suggested above.
PS: What is the datatype of extension->value->length ?
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
26 matches
Mail list logo