>
> > > Then, the testcontainer can use the same MySQL container across all
> > > tests using this URL.
> > >
> > > Just fyi :)
> > >
> > > Regards
> > > JB
> > >
> > > On Fri, Sep 26, 2025 at 12:09 AM Arthur Naseef
&g
The profile approach is doable. Just a couple of thoughts to add:
- Real unit tests are whitebox-only. If we are using any type of DB,
that's grey box or black box testing.
- The majority of our "unit tests" are actually grey box integration
tests.
- Using docker to spin up
I agree on TestContainers. There are ways to work around the lack of a
straight-forward lifecycle fit for TestContainers, but we can do well with
the docker-maven-plugin instead.
And personally, I think it is fine for the tests to require docker.
Art
On Thu, Sep 25, 2025 at 3:12 AM Clebert Suc
6, 2025 at 8:40 AM Arthur Naseef wrote:
> Look like this page describes the release process. It is light on
> details, but there are some key bits there:
> https://activemq.apache.org/components/cms/developers/creating-distributions
> .
>
> I also wonder if some of it is o
Look like this page describes the release process. It is light on details,
but there are some key bits there:
https://activemq.apache.org/components/cms/developers/creating-distributions
.
I also wonder if some of it is out-of-date. For example, it mentions
minotaur, which I think has been remov
I want to merge the following PR on github into the project, but I don't
see the merge button. Attached is a screenshot from github.
https://github.com/apache/activemq-cpp/pull/21
Is this a permission issue, do I need to manually merge, or is there
another process?
Art
---
he PR
> for a review last week and realized I couldn't so I assumed that meant
> your account was not linked. Glad it is working now
>
> Chris
>
> On Thu, Mar 6, 2025 at 1:39 PM Arthur Naseef wrote:
> >
> > Thanks Justin. Turns out Tim was right - I just need
ttps://github.com/apache/activemq-artemis/blob/main/.asf.yaml
> [2] https://github.com/apache/activemq/blob/main/.asf.yaml
> [3] https://github.com/apache/infrastructure-asfyaml
>
> On Thu, Mar 6, 2025 at 11:35 AM Arthur Naseef wrote:
>
> > I want to merge the following PR on
Thanks Tim. Looks like I didn't have them linked. I think they are linked
now - getting a message that I need to give it a few minutes to update my
repository access.
Art
On Thu, Mar 6, 2025 at 10:39 AM Timothy Bish wrote:
> On 3/6/25 12:27, Arthur Naseef wrote:
> > I wan
Agree on version 4.x - no need to go there now.
For the 3.10.x branch - how about we treat 3.10.0 as "dead" and skip to
3.11.0 - then, leave that branch and work on a fresh 3.11.0 branch.
Lingering, incomplete work from the past should not hold us up. I was
thinking to suggest renaming the branc
[4]
> >
> https://activemq.apache.org/components/classic/documentation/maven/apidocs/index.html
> > [5]
> >
> https://activemq.apache.org/components/nms/msdoc/1.6.0/vs2005/Output/html/N_Apache_NMS.htm
> > [6]
> >
> https://activemq.apache.org/components/cms/api_docs/activ
, the pages are documentation and direct linking them is
valuable, especially since finding specific content can take a little
digging.
Art
On Mon, Feb 24, 2025 at 8:40 PM Arjun Ray wrote:
> TOn Mon, 24 Feb 2025 14:44:42 -0700, Arthur Naseef
> wrote:
>
> | I recently used the Artem
pecific bit of documentation which is relevant
> to their needs. I've personally worked to ensure the docs are as linkable
> as possible.
>
> AsciiDoc is pretty powerful so we may be able to get the best of both
> worlds (e.g. seamless integration without frame nonsense). I'm
I recently used the Artemis documents here:
https://activemq.apache.org/components/artemis/documentation
And noticed that, upon navigating to a specific page, the broker still
shows this fixed URL. This is problematic for sharing specific content
from the site.
Can we update the site to show the
Revisiting this briefly... There is also a setting to turn off the
temporary destination tracking on the client.
The setting is watchTopicAdvisories - setting it to false will stop the
client from trying to track the temporary destinations, and could eliminate
the scenario reported here. It is l
For the Strict Aliasing Rule, IIUC, the compiler is complaining about the
(void*) cast from (Node *), right?
Is there any way two different pointer types have different sizes? If not,
I agree with the assessment that this is not harmful. The only way I can
see to fix it would be to simply inline
++ access to
ActiveMQ messaging.
Art
On Thu, Feb 13, 2025 at 11:27 PM Arjun Ray wrote:
> TOn Thu, 13 Feb 2025 20:29:12 -0700, Arthur Naseef
> wrote:
>
>
> Hello Art,
>
> I freely apologize for my sardonic and curmudgeonly style. I come
> from the rough and tumble of a bygon
> ASF rightly does not make it easy to join projects as well.
So being a contributor is actually really easy, and you have already done a
good amount of that - both with the code contribution and this discussion
here. However, becoming a committer is a higher bar.
I was invited to become a commi
*MAJOR TANGENT WARNING* (you have been warned)
I'm going to interrupt the constructive part of this discussion for a
moment. There's something important here that needs to be addressed - it
keeps knawing at me.
First, let me repeat one of my most favorite sayings of all time - "hate
never ends h
There's a lot here. I'll try to hit a couple of key points.
First off, while it would be awesome (in my opinion) to have active C++
developers on the project to maintain activemq-cpp (or a replacement),
there is a process to becoming a committer that is important to follow. I
wanted to mention t
Tue, Feb 11, 2025 at 10:45 AM Arjun Ray wrote:
> On Fri, 7 Feb 2025 09:28:10 -0700, Arthur Naseef
> wrote:
>
> | I'm trying to use CLion to work on the activemq-cpp sources, and finding
> it
> | is only partially working. The main thing that's missing is navigati
I'm trying to use CLion to work on the activemq-cpp sources, and finding it
is only partially working. The main thing that's missing is navigating
symbols - for example, "find usages" and navigating from a base class to
sub class methods just isn't working at all.
Looking for the Intellij equival
dependency either, we
> > absolutely need to be able to build a new version going forward. Just
> > because it hasn't changed doesn't mean it won't.
> >
> > On Fri, Jan 17, 2025 at 3:20 PM Arthur Naseef
> wrote:
> >
> > > I agree with Justin her
I agree with Justin here. What is the need to remove the dependency on
javacc - especially since it is build-time only?
Art
On Fri, Jan 17, 2025 at 1:11 PM Justin Bertram wrote:
> In what sense is JavaCC a "dependency of the activemq-client package"? It's
> not a Maven dependency, and it's no
Dragan - do the graphs show heap usage? If so, do you also have graphs
showing GC timings? Or, can you graph the heap usage while triggering a
major GC (which can be done easily via JMX)?
Art
On Wed, Nov 13, 2024 at 7:33 AM Justin Bertram wrote:
> Your image was stripped when it passed throu
+1
* built with `mvn clean install`
* created and started broker from the build output
On Wed, Jun 12, 2024 at 9:37 AM Clebert Suconic
wrote:
> I would like to propose an Apache ActiveMQ Artemis 2.35.0 release.
>
> I would like to highlight the following changes:
>
> - https://issues.apache.or
If I read it correctly, the transformer together with the divert provides a
means to duplicate messages from any number of inbound destinations to a
parallel set of destinations by adding a prefix.
For example:
test.events.a.1 -> TestQ.test.events.a.1
test.events.b.2 -> TestQ.test.events.b.2
L
+1
On Fri, May 17, 2024 at 9:22 AM Jean-Baptiste Onofré wrote:
>
> +1
>
> Regards
> JB
>
> On Thu, May 16, 2024 at 8:19 PM Clebert Suconic
> wrote:
> >
> > I want to propose having all of our user lists including an
> > Unsubscribe-me link at the end of the messages. Such unsubscribe-me
> > shou
I read through Justin's document up to the section "Why Use GitHub
Issues?" and have questions.
When users want Jira access, do they use an Apache account, or can it
be any account? Or are we just creating jira-specific accounts for
these users? Do they have / need-to-have an ICLA signed and on-
to the Jira:
> https://issues.apache.org/jira/browse/AMQ-9418
>
> Chris
>
> On Tue, Jan 16, 2024 at 5:40 PM Arthur Naseef wrote:
>
> > Looks like the key points here are:
> >
> >1. Existing clients will run into ClassNotFoundException when
> >unmarsh
Looks like the key points here are:
1. Existing clients will run into ClassNotFoundException when
unmarshalling an exception from a non-compatible broker. (Do broker's ever
create an instance of the class specified by the client?)
2. The proposed change will update clients to convert b
+1
Ran the full build on my Ubuntu 20.04 system.
Note that I ran into a test failure on BrokerXmlConfigStartTest due to the
test reusing port 61616 quickly, and getting "port already in use" errors.
I know others have run this test without problem, so I'm not going to worry
about it for now.
All
You're welcome.
On Thu, Oct 26, 2023 at 10:42 AM Jean-Baptiste Onofré
wrote:
> Thanks Art :)
>
> Le jeu. 26 oct. 2023 à 19:25, Arthur Naseef a
> écrit :
>
> > BTW, I just found this while doing something unrelated to our 6.0.0
> > release.
> >
> >
BTW, I just found this while doing something unrelated to our 6.0.0 release.
Maven central already has an apache-activemq artifact released with version
6.0.0:
https://mvnrepository.com/artifact/org.apache.activemq/apache-activemq
Perhaps we can get that one removed?
It looks like there are no
ot;Classic" name as a separate topic.
> >
> > On Thu, Sep 14, 2023 at 5:14 AM Jean-Louis Monteiro <
> > jlmonte...@tomitribe.com> wrote:
> >
> > > Same, when I have to mention both in the same discussion, I tend to add
> > > "classic" for Act
As a general practice, I try to avoid unqualified + qualified names
together - it gets confusing. However, in this case, we have a
long-established history.
I believe that a formal rename of ActiveMQ would be fairly disruptive for a
small amount of value.
For the record - I have heard, and start
I agree. We have had breaking changes in the 5.x series, and that's bad.
We may not be perfect in maintaining semantic versioning, but it is
important.
The Jakarta changes are definitely a major concern if we stick to 5.x.
Is there any reason to avoid using 6.x? I looked around to see if we eve
That is very helpful, thank you Tim. I heard that generator didn't work,
but haven't yet tried it myself.
Art
On Wed, Aug 23, 2023 at 11:59 AM Timothy Bish wrote:
> On 8/23/23 13:11, Arthur Naseef wrote:
> > That sounds right. My 2cents - it would be nice to figur
>
> https://github.com/apache/activemq/commit/3953b9aaefaee914bdd0702f27aef47c021ceb27
>
> On Tue, Aug 22, 2023 at 5:49 PM Arthur Naseef wrote:
>
> > Thank you Tim. That helps.
> >
> > Art
> >
> >
> > On Tue, Aug 22, 2023 at 2:23 PM Timothy Bish
&
Thank you Tim. That helps.
Art
On Tue, Aug 22, 2023 at 2:23 PM Timothy Bish wrote:
> On 8/22/23 15:28, Arthur Naseef wrote:
> > I'd like to ask first to get some clarification.
> >
> > Using the activemq-openwire project, I was able to get it to generate
> > o
Tim - can you help answer the questions from my email above? Are there
notes/documents anywhere that help?
Art
On Tue, Aug 22, 2023 at 12:28 PM Arthur Naseef wrote:
> I'd like to ask first to get some clarification.
>
> Using the activemq-openwire project, I was able to get
I'd like to ask first to get some clarification.
Using the activemq-openwire project, I was able to get it to generate
openwire Java code, but that code did not exactly match the code in the
activemq codebase. It appeared to be mostly non-functional differences,
such as packages being renamed, an
David:
Please re-post this message on the user mailing list.
The DEV mailing list is for development of ActiveMQ itself, and not
applications using ActiveMQ.
Art
On Thu, Jun 29, 2023 at 9:54 AM David Hoffer wrote:
> Hi,
>
> We have a Quarkus app where we embed an Artemis server, we were usin
+1
Art
On Sun, May 7, 2023 at 7:32 AM wrote:
> +1
>
> Jeff
>
>
> > On May 7, 2023, at 2:09 AM, Havret wrote:
> >
> > FYI
> >
> > -- Forwarded message -
> > From: Jean-Baptiste Onofré mailto:j...@nanthrax.net>>
> > Date: Sun, May 7, 2023 at 7:02 AM
> > Subject: Re: [VOTE] Relea
Please ask this question on the user mailing list. The dev mailing list is
for discussion of development/maintainenance of the ActiveMQ / Artemis code
bases themselves.
Art
On Fri, Mar 17, 2023 at 2:47 PM Walter Krix (Nokia)
wrote:
> Dear ActiveMQ Artemis Developers,
>
>
> I am writing to inq
+1 (binding)
Built and did a quick comparison of the file sizes in the published zip.
Art
On Wed, Mar 15, 2023 at 9:21 AM Clebert Suconic
wrote:
> (hmm.. I had already sent the previous +1, sorry, I thought this was
> another spin or something).
>
> please make sure you only consider one vote
ooked over the dev list in 4 years?
> :-)
>
>
> Justin
>
> On Tue, Mar 7, 2023 at 11:01 AM Arthur Naseef wrote:
>
> > Just saw this from a rare look over DEV list messages (hint hint) ;-).
> >
> > So glad to see this action. Easy-to-Use is top priority, and a dev
Just saw this from a rare look over DEV list messages (hint hint) ;-).
So glad to see this action. Easy-to-Use is top priority, and a dev list
that requires filtering to use - why? Just why?
Art
On Thu, Mar 14, 2019 at 11:40 AM jgenender wrote:
> +1 to github notifications on another list.
Please send this message to the user list. The dev list is reserved for
discussions related to the development (e.g. code changes) of the broker
itself.
Thank you.
Art
On Thu, Mar 2, 2023 at 8:26 AM Rhea MOUBARAK wrote:
> Hello,
>
>
>
> I am trying to look everywhere for the versions of Acti
Yeah, Sontatype OSSRH is a little involved to get going, but not too bad.
I use it (for example
https://mvnrepository.com/artifact/com.artnaseef/correlation-id-utils).
On Mon, Nov 7, 2022 at 4:20 AM Robbie Gemmell
wrote:
> You can release stuff to Maven Central via Sonatype OSSRH,
> https://cent
Making use simple for users is a good thing. On the other hand, there are
a lot of target environments that could use different tweaks. Our
dependency-management tool is maven.
If folks want to work outside of maven, that's their choice, but then
dependency management becomes a problem for that
+1 for eliminating shaded jars/bundles where possible
On Tue, Jul 26, 2022 at 10:16 AM Timothy Bish wrote:
> +1
>
> Removing them seems valid given the issues noted.
>
> On 7/26/22 12:18, Robbie Gemmell wrote:
> > I think removing them would be good for various reasons inc all you
> noted below.
Sounds good - thank you JB.
On Sun, Jul 24, 2022 at 12:07 AM Jean-Baptiste Onofré
wrote:
> Thanks for the test app. I will test with my PR.
>
> I will keep you posted.
>
> Regards
> JB
>
> Le sam. 23 juil. 2022 à 21:46, Arthur Naseef a écrit :
>
> > Got the te
backward compatibility for
JMS 1.1 applications while retaining JMS 2.0 compatibility (i.e. does not
further break backward compatibility).
Art
On Wed, Jun 22, 2022 at 9:15 AM Arthur Naseef wrote:
> Still working on a test project - almost got it working.
>
> Art
>
>
> On Tue,
That error can happen under normal (non-errant) conditions - are there
other symptoms that raise concerns related to it?
One cause of such an error is an unstable network that is dropping
connections. Another could be a simple race between the connection being
closed on the other end and the publ
Still working on a test project - almost got it working.
Art
On Tue, Jun 21, 2022 at 8:27 AM Arthur Naseef wrote:
> Agreed on fixing it going forward and not simply reverting - that would
> really just create another non-backward-compatible change and increase the
> size of the prob
the right range:
> > > > > > >
> > > > > > >javax.jms;version="[1.1,3)",
> > > > > > >
> > > > > > > Else it won't work.
> > > > > > >
> > > > > > > And by the way, befor
I created the following ticket to address applications failing to load into
Karaf with AMQ 5.16.3 - 5.17.1 due to an incompatible change in the
activemq-client feature.
https://issues.apache.org/jira/browse/AMQ-8971
Looks to me like the right fix here is to revert the change to the JMS 1.1
spec
My 2 cents...
For AMQ 5: Active / Passive or Active / Standby makes sense for H/A. NOB
it does not apply - each "node" (H/A pair in case every broker is running
in H/A) has active/passive pairs. So yes, a NOB could have a bunch of
brokers all in Active state if none of the nodes is running H/A.
In case the testing part is not entirely clear, after making the logger
injectable, then use a Mock in the test; like this:
Logger mockLogger = Mockito.mock(Logger.class);
target.setLog(mockLogger);
...
Mockito.verify(mockLogger).info("Started");
Art
On Wed, May 4, 2022 at 10:27
+1 on SLF4J - that's what it does: eliminate the tight coupling of code
generating log output from the logging implementation.
For testing, I would just make the logger injectable, but configure a
default. Here's a "Live Template" for intellij that does this (minus the
getter and setter):
privat
Clarifying on (4) units problem - that refers to the software industry in
whole, not just AMQ.
Art
On Wed, Dec 22, 2021 at 12:24 PM Arthur Naseef wrote:
> Thoughts that come to mind (not advocating anything, just putting down
> thoughts);
>
>1. Semver + breaking-changes = new
> What else would you suggest?
>
> -Matt Pavlovich
>
> > On Dec 22, 2021, at 11:25 AM, Arthur Naseef wrote:
> >
> > Hmm, what about the impact to all the consumers of that metric today?
> >
> > That's potentially a huge amount of change.
> >
> >
Hmm, what about the impact to all the consumers of that metric today?
That's potentially a huge amount of change.
Any thoughts on mitigating the problems for users?
Art
On Wed, Dec 22, 2021 at 7:32 AM Matt Pavlovich wrote:
> Using nanos would eliminate the math division. Might be worth it to
I didn't read the full thread, but I have a question based on the initial
description.
There is an XML payload with random bytes inline? If so, what keeps that
from being invalid XML? '<', '>', '&', and characters that are invalid for
the character set would all cause havok.
Art
On Wed, Jun 1
May I ask where this is going? The vm-transport's handling of
copying/not-copying messages isn't intended to be a feature. Changing a
message that's in-flow within the broker is a bad idea for a lot of reasons.
Art
On Thu, Apr 1, 2021 at 1:01 PM Christopher Shannon <
christopher.l.shan...@gmai
, website/documentation
> first and code base after).
> I’m ready to tackle this (even it’s a big effort ;)).
>
> Regards
> JB
>
> > Le 20 mars 2021 à 19:19, Arthur Naseef a écrit :
> >
> > When it comes to naming, and overloaded names, having two things with the
When it comes to naming, and overloaded names, having two things with the
same base name, then one with a distinguisher and one without, creates an
imbalance that always leads to confusion. In other words, having
"ActiveMQ" and "ActiveMQ Artemis" is confusing. If it had been (too late
now) "Activ
Art
On Fri, Mar 19, 2021 at 3:28 PM Arthur Naseef wrote:
> TLDR; my take here - we discussed making Artemis a TLP long ago, and we
> chose this path.
>
> I see the naming can be confusing. And of course, there's the fact that
> AMQ 5 is kinda stuck on major version numbe
TLDR; my take here - we discussed making Artemis a TLP long ago, and we
chose this path.
I see the naming can be confusing. And of course, there's the fact that
AMQ 5 is kinda stuck on major version number 5, but we have lived with that
up until now without significant problems.
Was there some o
I keep seeing mention of having multiple variations of docker images using
different base images and some thoughts come to mind.
Here are my thoughts:
- Docker staged builds make it easy to copy specific contents from one
base image into a new one, leaving behind unwanted content (e.g. O/S
Hey JB, I am interested here.
I know many approaches to replication have been tried - with AMQ 5 as well
as Artemis. For example, "LevelDB replicated storage" and "Pure Master
Slave" (where the active broker copied updates to the passive brokers) in
AMQ 5. So I'm curious how the problem is getti
I have started to run the build after updating the tag.
Thank you JB.
Art
On Fri, Dec 4, 2020 at 1:20 PM Jamie G. wrote:
> +1
>
> Cheers,
> Jamie
>
> On Fri, Dec 4, 2020 at 9:11 AM Jean-Baptiste Onofre
> wrote:
> >
> > +1 (binding)
> >
> > Regards
> > JB
> >
> > > Le 3 déc. 2020 à 06:03, Jea
t;
> > So, I started to improve the situation, but it takes sometime and I
> don’t think we should hold releases for non accurate/flaky tests.
> >
> > Thanks again for your feedback, I’m moving forward on release (5.15.14
> take #2) and improving the build/tests.
> >
>
- the build often fails on Jenkins due to flaky tests
> >
> > So, I started to improve the situation, but it takes sometime and I
> don’t think we should hold releases for non accurate/flaky tests.
> >
> > Thanks again for your feedback, I’m moving forward on release (5.1
Dec 1, 2020 at 1:48 PM Arthur Naseef wrote:
> Looks like I'm finding 2 problems with the InMemeoryJmsSchedulerTest:
>
>
>1. The ClassCastException in one test, and
>2. "Didn't receive the message" problem in the other.
>
>
> Digging into the C
Could this have been broken all this time?
Haven't dug into the second problem yet.
Art
On Tue, Dec 1, 2020 at 1:03 PM Arthur Naseef wrote:
> So it looks like my build only had 2 test failures. The first we
> discussed already. The second is
So it looks like my build only had 2 test failures. The first we discussed
already. The second is as follows:
[INFO] Running
org.apache.activemq.broker.scheduler.memory.InMemeoryJmsSchedulerTest
[ERROR] Tests run: 8, Failures: 1, Errors: 1, Skipped: 0, Time elapsed:
41.993 s <<< FAILURE! - in
or
gt;
> My bad, I will fix that.
>
> Thanks !
> Regards
> JB
>
> > Le 1 déc. 2020 à 05:00, Arthur Naseef a écrit :
> >
> > I'm running the build on an Ubuntu system and getting 4 test failures. I
> > retried 1 and it repeated.
> >
> > I&#x
I'm running the build on an Ubuntu system and getting 4 test failures. I
retried 1 and it repeated.
I'll look at the failures more tomorrow. Here are the errors from the test
I retried:
[ERROR]
testStartBrokerUsingXmlConfig1[activemq-leveldb-replicating.xml](org.apache.activemq.config.BrokerXml
To clarify, the subject says "move to" which sounds at first like "remove
and replace" - but that's not the intent, right? Just talking about adding
the JakartaEE API and keeping JMS 2.0, correct?
If it's just adding a new API, I have no strong feelings either way.
Art
On Tue, Sep 22, 2020 at
I'm just catching up on this thread and didn't read it all thoroughly, so
forgive me if I missed anything.
The idea of using Virtual Topics to meet the JMS 2.0 "named subscriptions"
feature sounds like a good approach.
One question that raises - removal of the queue so ensure it doesn't end up
ab
repared the
> update to maven-bundle-plugin 4.2.1 allowing us to build using JDK 11
> (targeted for ActiveMQ 5.17.0).
>
> This warning also exists on activemq-5.15.x branch for very very long time.
>
> So, no blocker, and I already fix that.
>
> Regards
> JB
>
> &
I'm building now. Don't know how quickly it'll get done, so I won't be
surprised if the vote is closed before then.
There is an error in making the activemq-client bundle - any thoughts on
this?
[INFO] --- maven-bundle-plugin:2.3.7:bundle (default-bundle) @
activemq-client ---
java.lang.ArrayIn
You should not see any problems with mixing versions. With that said,
please test before rolling out to production. In our history, we have had
a couple of unintentional version-mismatch issues arise, so they are very
rare, but not impossible.
Art
On Thu, Apr 30, 2020 at 4:04 AM goutamknit wr
I would be comfortable to use a maven profile that is disabled by default
together with the plugin to do the C# build.
Any concerns with that approach?
Art
P.S. Apologies if I missed something from your messages Michael - the
spacing on my screen is a mess (looks like lost newlines).
On Tue, A
Did you get any feedback on this?
Here are thoughts that come to mind...
The src/main/java/... structure is used by (and "encouraged" by) Maven.
Would the C# sources be built as part of the maven build process? If so,
how do we ensure folks can build the Java sources even when they don't have
th
the consumer side.
> > - the message volume your working with
> > When I set to the queue to persistent the throughput on the producer side
> > is 50k msg per second, non persistent its 250k msg per second. The
> consumer
> > side throughput is much slowe
While it is possible to improve throughput with batching acks in
transactions, I would recommend to check some other things first. Also
note that transactions can introduce other issues, as I have experienced.
Here are things I recommend to try (forgive me if these have already been
tried):
-
Try 'netstat -an'
It appears something else is already using that port.
On Sat, Jul 27, 2019 at 8:02 AM balan.karuppasamy <
balan.karuppas...@cognizant.com> wrote:
> Hello,
>
> In *conf/activemq.xml* , we have below configuration to connect with remote
> host and port.
>
>
>
> uri="tcp:
ils would be called out in the LICENCE file, not NOTICE)
>
> Robbie
>
>> On Fri, 7 Jun 2019 at 00:21, Arthur Naseef wrote:
>>
>> Looking for clarification here. Our projects can depend on LGPL'ed
>> dependencies, right? Here is my understanding...
>>
Looking for clarification here. Our projects can depend on LGPL'ed
dependencies, right? Here is my understanding...
LGPL is not GPL, so using it as a library in our project should not force
the license on our software - i.e. we can still release under the Apache
License. We do need to include a
The error, "bind failed" is often caused by something else listening on the
same port.
Double-check that the port is free. Also double-check the IP address being
bound is valid (0.0.0.0, 127.0.0.1, or a valid IP address on the host).
Art
On Mon, May 20, 2019 at 9:43 AM saddaypally
wrote:
> H
Unfortunately, you can't have it both ways with the failover transport as
it cannot know what the application wants.
That is -- either the failover transport tries forever (my preferred
approach), or it fails and stops trying to reconnect after some time.
If you are looking to have individual mes
Awesome! Glad I could help.
Art
On Sat, Mar 23, 2019 at 1:16 PM klaus.holst.jacobsen <
klaus.holst.jacob...@gmail.com> wrote:
> Art, thx for the response.
>
> Solved the problem.
> You led me on the way.
>
> I had compiled activemq-cpp on the target system whereas i compiled my
> wrapper libs
OK, using an online name demangler, I get the following:
-
_ZN8activemq4core25ActiveMQConnectionFactoryC1ERKN5decaf3net3URIERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESE_
-
activemq::core::ActiveMQConnectionFactory::ActiveMQConnectionFactory(decaf::net::URI
const&, std:
es.apache.org/jira/browse/INFRA-18068
>
> But it might be something we need to change (ie the SSL versions are
> mismatched or something) which is why in the other thread I mentioned maybe
> we should just vote and push the new site.
>
> On Thu, Mar 21, 2019 at 3:19 PM Arthur Naseef wr
move
the SVN repo to GIT, or if a GIT repo of that already exists somewhere else.
Art
On Thu, Mar 21, 2019 at 1:38 PM Arthur Naseef wrote:
> I was looking through that build and trying to find the project that is
> being built, without success.
>
> Can you point me at the build job
wrapper library:
... -Wl,-Bstatic -lactivemq-cpp -Wl,-Bdynamic ...
Note that I tested a generic dynamic-lib link locally on a mac and the
arguments are a little different; here is what I came up with:
... -Wl,-static -lb -Wl,-dynamic -Wl,-dylib
Art
On Thu, Mar 21, 2019 at 11:55 AM Arthur
Sorry Chris, not I. That has been a mystery to me.
I'll poke at the logs briefly and let you know if I have any ideas.
On Thu, Mar 21, 2019 at 3:25 AM Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:
> Does anyone know much about how the current website is deployed? There
> seems t
1 - 100 of 455 matches
Mail list logo
