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
ues.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
> >unmarshalling an exception from
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
+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.
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.
> >
> > Maven
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
e 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 ActiveMQ to make sure t
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
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
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 figure out the
> 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
> w
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
> > openwi
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 it to
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,
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
+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]
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
+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
> :-)
>
>
> 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 list
> > that requires filter
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
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,
>
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
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 t
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
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 th
t; > > > > >javax.jms;version="[1.1,3)",
> > > > > > >
> > > > > > > Else it won't work.
> > > > > > >
> > > > > > > And by the way, before the change, I sent a couple of messages
> on
> > >
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):
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
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.
> >
> > Any thoughts on miti
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
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
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 <
site/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)
21 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 number 5, but we have lived with th
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
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
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,
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.
> >
>
ld 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.15.14
>
20 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 ClassCastExc
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 as follows:
&g
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
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'll look at t
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]
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
ate 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
>
> > Le 30 juin 2020
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 ---
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
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,
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
d, the same is done on 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 slower 10k and 50k r
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.
>
>
>
>
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...
>>
>> LGPL
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
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:
>
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
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&,
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 Nas
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 jo
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
It's been a while since I've worked with C++, mangled symbol names and
linking, but I used to be good at it, so I'll help...
When linking the dynamic wrapper library, is the static library being
pulled into the link via "-L... -lactivemq-cpp"? If you can share the
commands used to build, that
Chatting with Justin about NMS this afternoon, there are some specific
questions that come up. Note the goal here is clarity and updating the
website (thank you Justin for working on the website).
Before jumping into these questions, I want to make clear that I feel
strongly NMS is an important
looking to attack anyone, if thats what you felt.
>
> Robbie
>
> On Tue, 19 Mar 2019 at 16:49, Arthur Naseef wrote:
> >
> > What are we doing with this thread? Trying to get individual commitments
> > to putting time into some vague possibility of needed effort in the
>
What are we doing with this thread? Trying to get individual commitments
to putting time into some vague possibility of needed effort in the future?
Just reading this thread is discouraging. I long to be part of a community
that works together to constructively solve problems - real problems.
e users needed to rebuild it from scratch, and
> bumped into this native issue, which I'm trying to improve here.
> >
> > The native layer build wouldn't have any .so, and the .so would be part
> of the release.
> >
> >
> >
> > On Thu, Jan 31, 2019 at 12:36
resee being used for other cases where we may need JNI.
>
> On Wed, Jan 30, 2019 at 5:53 PM Arthur Naseef wrote:
>
> > What is in the library?
> >
> > Art
> >
> >
> > On Wed, Jan 30, 2019 at 11:08 AM Clebert Suconic <
> > clebert.suco...@gmail.com&g
Looking at the following file to understand the functionality of the
library, I have a question around the allocation and freeing of iocb's:
activemq-artemis/artemis-native/src/main/c/org_apache_activemq_artemis_jlibaio_LibaioContext.c
Function
What is in the library?
Art
On Wed, Jan 30, 2019 at 11:08 AM Clebert Suconic
wrote:
> I thought Since the native project had open scope like I'm proposing,
> it would eventually be useful anywhere that needs a JNI library.
>
> But we can go with activemq-artemis-native. That's fine.
>
> On
I agree. Messaging and Database patterns are very different, with
different optimizations and considerations.
That's why folks often hear me repeat a part of a Jeff Genender's
presentation - "don't use ActiveMQ as a message store".
Messaging is about moving messages as quickly as possible
Jamie
> > >>> On Thu, Nov 29, 2018 at 8:56 AM Gary Tully
> wrote:
> > >>>>
> > >>>> Hey Arthur,
> > >>>> I am not asserting that they need to be small.
> > >>>> I am pointing out that they currently are small changes; th
ug than a random web console bug or
> transport
> > > > error that just causes an error with a single client or with a single
> > > > message. Granted the risk of a critical bug being introduced with a
> > > > refactor like this is not very high but if the
Improving the existing code is a great goal.
While cleaning up code is nice KahaDB has gotten pretty stable over the
> years and doing a bunch of refactoring just opens it up to new bugs that
> have to be fixed. Fixing bugs is not a problem however I tend to be more
> sensitive to store related
Are you looking to get queue semantics (competing consumption across
multiple consumers) out of this subscription, or topic semantics (every
consumer gets every message)?
If the later, then you may be able to directly subscribe to the virtual
topic itself, as a regular topic - because it still
I assume that "filter" here means selectors. If so, my first reaction is
to warn that selectors impose a heavy load on the broker, which can be seen
by monitoring CPU utilization. More subscriptions with more selectors only
adds to the problem. Without selectors or message groups, I have rarely
+1
Thank you.
On Wed, Oct 24, 2018 at 9:45 AM Daniel Kulp wrote:
> +1
>
> Dan
>
>
> > On Oct 24, 2018, at 10:41 AM, Christopher Shannon <
> christopher.l.shan...@gmail.com> wrote:
> >
> > Hi Everyone,
> >
> > I have created the 5.15.7 release and it is ready for a vote.
> >
> > The list of
ogle doc):
https://docs.google.com/document/d/1qRcpqVjfSvPOEZ4vDbTWSOu0PUAnABtvqrOYJSNaaNg/edit?usp=sharing
On Tue, Sep 4, 2018 at 1:41 PM, Arthur Naseef wrote:
> Looking over the release. I see the fix for AMQ-6954 is working.
>
> The build works when run without any tests. After a few retries, I have
> t
Looking over the release. I see the fix for AMQ-6954 is working.
The build works when run without any tests. After a few retries, I have
the following tests continually failing:
Tests run: 19, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 173.792
sec <<< FAILURE! - in
Probably the best approach is the Jolokia endpoint which provides HTTP
(REST-like) access to those values.
If there's a C# compatible means to access those settings via JMX, that
would be good - maybe even preferable.
Art
On Thu, Aug 30, 2018 at 7:00 PM, sridhar.infot...@gmail.com <
That appears to be the "Apache Portable Runtime" library required by the
ActiveMQ CPP build.
Does the build system have the APR package installed? I believe that's
"yum install apr" for CentOS.
Art
On Wed, Aug 15, 2018 at 10:31 AM, stevent.klingberg <
stevent.klingb...@ge.com> wrote:
>
I don't expect username and password to affect inactivity timeouts.
Inactivity timeouts should only occur when the TCP connection between the
client and broker is somehow excessively slow or stuck (e.g. if packets are
not crossing the network properly).
Versions of the client and server should
The openwire generator is executed by the activemq-client project when the "
openwire-generate" build profile is enabled and the "antrun:run" goal is
executed (according to the comments in the pom):
mvn -P openwire-generate antrun:run
This runs a complex script that appears to ultimately boil
r.l.shan...@gmail.com> wrote:
> > >
> > >> I can cancel the vote if you want but I won't be able to re-run a new
> > vote
> > >> for 10 days to 2 weeks. I'm out of the office next week so if I
> start a
> > >> new vote today then 72
Can we get this commit added to the release? It's currently on the master
branch.
d8c80a98212ee5d73a281483a2f8b3f517465f62
Please let me know what else needs to be done to get it into the release.
Art
On Tue, Aug 7, 2018 at 2:39 PM, Arthur Naseef wrote:
> I found that one is
Try this:
Notice the keyStoreType and trustStoreType attributes.
Art
On Tue, Aug 7, 2018 at 8:09 AM, Justin Bertram wrote:
> I would expect PKCS stores to work fine. Have you tried them and found
> they didn't work?
>
>
> Justin
>
> On Tue, Aug 7, 2018 at 9:59 AM, zollen
UT:-/dev/null}" 2>&1 &
It seems the new "ACTIVEMQ_OUT" variable must be defined based on the
commit as-is, making that change non-backward-compatible for anyone with
their own env setup.
Art
On Mon, Aug 6, 2018 at 11:10 AM, Arthur Naseef wrote:
>
Thank you Chris. That seems most prudent.
I just looked at the change to the script and found the commit; there may
be a very simple way to fix this:
commit 0036084af6ec930e91927170bdc6cfc1c81b37ff
Author: Alvin Lin
Date: Mon Apr 9 16:53:44 2018 -0700
AMQ-6930 provide options to allow
+1
On Fri, Aug 3, 2018 at 4:42 AM, Jamie G. wrote:
> +1 (non-binding)
>
> Cheers,
> Jamie
> On Fri, Aug 3, 2018 at 7:19 AM Jean-Baptiste Onofré
> wrote:
> >
> > +1
> >
> > Regards
> > JB
> >
> > On 03/08/2018 06:18, Francois Papon wrote:
> > > +1 (non-binding)
> > >
> > > Thanks for the
+1
On Wed, Aug 1, 2018 at 6:59 AM, Johan Edstrom wrote:
> +1 non binding
>
> Sent from my pressure cooker.
>
> > On Aug 1, 2018, at 05:32, Jamie G. wrote:
> >
> > +1 (non-binding)
> >
> > Cheers,
> > Jamie
> > On Tue, Jul 31, 2018 at 1:57 PM Francois Papon
> > wrote:
> >>
> >> +1
1 - 100 of 405 matches
Mail list logo
