Great, thank you for doing that.
Tim
On Wed, Nov 27, 2019, 1:36 AM Viliam Durina wrote:
> Done: https://issues.apache.org/jira/browse/AMQ-7354
>
> On Wed, 27 Nov 2019 at 07:44, Tim Bain wrote:
>
> > This sounds like a valid bug. Could you please submit a bug report
In the short term, one option would be to simply not include the Jetty JAR
in the ActiveMQ classpath. I'd expect you might lose access to the web
console and possibly also to the HTTP transport (I'm not sure if that
relies on Jetty, but it wouldn't surprise me if it did), but if you could
live with
This isn't something I've personally tried (nor that I'm familiar with
enough to say for sure whether it would work), but it seems like it should
be possible as long as you ensure that messages that are not processable
are not moved to a DLQ no matter how many times they're retried. That seems
to b
What does "7/8 backend brokers with a lot of routes" mean? My description
of your setup specified either a broker or a master-slave pair of brokers
for the backend, and you agreed that my description was correct. How did we
get from there to "7/8" backend brokers? Also, can you re-confirm that the
So we're repackaging com.sun.xml classes in the ActiveMQ JARs? Are you
using activemq-all.jar by any chance? If so, please switch to using the
individual JARs and see if that solves the problem; activemq-all.jar is
intended as a quick-start for standalone use, but anytime that users find
that they
To add to Justin's points, that old JRE is forcing you to use an old
version of ActiveMQ, for which many bugs were later fixed. Upgrade to a
more modern JRE (probably Java 8, unless SAP PI 7.1 supports Java 9+, but
that certainly isn't guaranteed given that it was released in 2008), and
then upgrad
You should also describe a few things about the usage pattern. Is there an
increasing number of unconsumed messages over time? Do you use a
non-trivial number of scheduled messages?
And for the heap usage itself, do you see a low staeady state but a sudden
spike at the time that the OOM occurs, or
None of your quoted content actually came through, either via email or on
Nabble. Can you resend?
Tim
On Tue, Dec 31, 2019, 3:09 PM ERP wrote:
> Hello, I am trying to develop a custom login module using JAAS. Everything
> works when authenticating, but when I include the authorizationPlugin for
One thing to keep in mind when health checking ActiveMQ (whether via
Prometheus or a load balancer) is that anything that opens a TCP socket to
the OpenWire port without actually sending any content will result in the
broker logging some content for each such connection. So I second the idea
of a J
This is why I hate interacting with JMX via code, especially since I only
do it once every few years. It's very useful, but I always find that I have
to troubleshoot every step of the way because it's not very intuitive (to
me).
Glad you found the solution.
Tim
On Wed, Jan 15, 2020, 4:58 PM cmat
but you've said that you don't want to use
JMX.
Those are basically the options as I know them, unless you want to get into
the ActiveMQ code and build a health check endpoint that behaves exactly
how you want it to.
Tim
On Mon, Jan 20, 2020, 8:47 AM Daniel Trüssel wrote:
> On 18.01
ActiveMQ runs in a Java Runtime Environment (JRE). 5.9 requires Java 7 or
later for its JRE. If you can run a Java 7 JRE on Windows Server 2012, then
you can run ActiveMQ on it.
Tim
On Mon, Jan 20, 2020, 7:12 PM Roy Low Chee Mun wrote:
> hi all
>
>
> wondering can ActiveMQ 5.9 install in Window
Do messages get stuck in both queues, or only one of them?
Tim
On Thu, Jan 23, 2020, 5:42 AM Jean-Baptiste Onofré wrote:
> By the way, what's the broker URL in the connection factory ? failover ?
> Are you using rebalance client ?
>
> What's the prefetch on client side configuration ?
>
> Rega
Have you read the Stuck Messages section of
https://activemq.apache.org/networks-of-brokers and applied one of the
solutions it describes (I recommend the replayWhenNoConsumers=true solution
because it works no matter how many consumers you have). You'll also need
to ensure that your TTL setting fo
Your first step is to get JAXB onto the classpath so you can see what the
actual error with your XML is.
https://stackoverflow.com/questions/43574426/how-to-resolve-java-lang-noclassdeffounderror-javax-xml-bind-jaxbexception-in-j
looks like it explains why you're hitting this with Java 13, and giv
r, and it
> works very well. I haven't observed message stuck since this change. If
> it still the case Friday this week, I'll update the "message stuck" part
> in the documentation.
>
> We're staying in touch,
>
> Jérôme
>
> Le 25/01/2020 à 14:29,
Is this for ActiveMQ 5.x or for Artemis?
Tim
On Fri, Feb 21, 2020, 12:30 PM ssjuvestabia1907
wrote:
> Hi all,
> please could you help me to understand the issue indicated below.
> We need to write iDoc message (xml file) from a SAP system on a queue
> (section Queues) but the iDoc message (xml
This is expected behavior. When a message with a JMXGroupId is dispatched
to a consumer, that consumer is the sole one that will receive future
messages with the same JMXGroupId, until the connection from the consumer
to the broker is broken.
Here's your sequence of events, with additional comment
I'm not aware of any mechanism for controlling the assignment of message
groups to consumers. I expect it would be possible for you to customize the
broker's code to do this, but that's not code that I've looked at recently
so I'm not sure how complicated it would be to do. Alternatively, you could
Based on https://dzone.com/articles/temp-store-and-memory-percent, it
sounds like storeLimit considers only the messages (db*.data) but not the
redo log. So the amount of disk used in total could be a bit larger than
the limit that's set.
Tim
On Mon, Mar 2, 2020, 6:48 AM Jean-Baptiste Onofre wro
Unrelated, but you don't need to specify failover in this
URI: uri="static:(failover:(tcp://localhost:61626))
Static networkConnectors retry automatically (unlike normal client
connections), so you can use static by itself.
Tim
On Fri, Mar 20, 2020, 6:35 PM Matt Pavlovich wrote:
> Nicky-
>
> T
Can you please provide a listing (ls -l) of the KahaDB data directory?
Also, can you please configure mKahaDB to point to a different (empty)
directory rather than the same one that the normal KahaDB points to, and
try again? I've never used mKahaDB so I don't have direct experience, but I
wouldn'
This definitely sounds like a bug in the mKahaDB code, so can you please
submit a bug report for it in JIRA?
I'd be curious to know whether the problem occurs if you cycle the remote
broker between steps 5 and 6. If not, it's likely something in-memory that
represents an inconsistency between the
Can you tell, is the message getting redelivered at all? I'd have expected
it to be redelivered several times and then move to the DLQ, so if that's
not happening, that might be a thread to pull...
Tim
On Wed, Mar 25, 2020, 7:11 AM areddy wrote:
> *Redelivery policy *
>
> sendToDlqIfMaxRe
This definitely sounds like a bug. Can you please submit a bug report for
it in JIRA?
Thanks,
Tim
On Wed, Mar 25, 2020, 6:57 PM areddy wrote:
> The messages with a delay header are delivered once, after the delay
> period,
> as expected. But when they are rejected by the consumer, they just sit
What I meant was, if you cycle the remote broker while the local one is
down, do you get the same behavior? I'm trying to characterize whether the
problem is purely something in-memory on the remote broker, or whether the
problem is also in the content written to disk (and therefore the problem
per
Thanks for testing that; it will help make sure that whoever works on a fix
focuses quickly on the right part of the code. Would you be able to submit
a bug in JIRA to capture the problem as you observed it? If you're able to
attach any config files that would make it easier to quickly reproduce th
I had forgotten you'd already submitted one. Thank you for doing that.
Tim
On Sat, Mar 28, 2020, 12:13 AM nexus wrote:
> I have already opened an issue AMQ-7453 with detailed description, logs and
> examples, please, take a look:
> https://issues.apache.org/jira/browse/AMQ-7453
>
>
>
> --
> Sen
Many, many software systems use ActiveMQ 5.x without experiencing hanging
consumers, so the presumption is that a recent version of 5.x will not have
this problem. But of you download it and find that you're still having this
problem, post a question here (with a detailed description of the behavio
The simplest path forward is to increase your JVM's heap, say to 3GB or
4GB. As long as the broker's steady-state utilization (after triggering a
full GC) remains relatively constant over time (more precisely, the steady
state utilization doesn't rise consistently over time), then increasing the
he
Do you have a significant number of unconsumed persistent messages?
Especially on many queues/topics? That would produce an increase in the
amount of RAM relative to an empty broker, because the broker will pull a
certain number of the messages into memory to be ready to dispatch them to
consumers
then we're grateful for the help identifying it. But you also
need to understand that there is no expectation that a heavily-used broker
would never use more heap than an empty on straight out of the box, so
"increase the heap" may turn out to be the solution, not a hack.
Tim
Yes, it would be helpful to have your exact configuration, and to know the
version of ActiveMQ that you are using.
Unfortunately I won't have time to try to reproduce this until the weekend.
But in the meantime would you please try the following to see if we can
narrow in on what aspect of the bro
What command are you using to stop the broker?
It looks like you're using the default JMX port (1099) for all six brokers
even though they're all running on the same machine and therefore only one
of them will actually succeed in opening that server socket. Does the
problem disappear if you use a
Justin, are you saying that there is a command(s) that would make the
client automatically fail over to a different broker in the situation Anton
described, if that command(s) is executed before the scale-in occurs?
AWS has a feature called ASG lifecycle hooks that allow a host to be
notified (and
>From the logs, it looks like the URI used for your connection is using
tcp:// as the transport protocol, whereas an MQTT connection use mqtt://.
And is the port you're connecting to running the MQTT protocol, or is it an
OpenWire port?
Tim
On Mon, Apr 20, 2020, 10:02 AM JJ wrote:
> Simple MQTT
What URI (without the HAProxy IP, of course) are you using in your MQTT
client? It's OK/expected that the underlying protocol be TCP at the network
level, but the client needs to be specifying mqtt:// in the URI to tell the
client library to use MQTT over TCP instead of OpenWire over TCP. It also
n
JVisualVM, which ships with the Oracle JDK (not sure about OpenJDK) is
another option. Be sure to use the CPU sampler, not the CPU profiler, if
you can't afford to add a significant load to the process (e.g. if this is
an operational host).
Tim
On Wed, Apr 22, 2020, 4:21 PM Francesco Nigro wrote
I hadn't understood that the connection was initially successful and data
passes correctly at first, so thank you for clarifying that.
Do you see the same behavior if you connect directly to the broker without
going through the HAProxy? Might this be introduced by the loan balancer,
possibly due t
You're right, I re-read the log and you did provide the broker logs. Sorry
for the confusion.
I assume the client logs show something similar for the root cause (even
though it'll be a different stack trace)?
Unfortunately I don't have any experience configuring or troubleshooting
HAProxy. I reco
Is this on a standalone broker, or are you running a network of brokers?
Might these consumers be the ones for one broker in a network of brokers to
pull messages from another?
Tim
On Thu, Apr 30, 2020, 1:32 PM bstrange wrote:
> I'm running ActiveMQ 5.11.1 and have two consumers on a queue. If
If these are consumers on a queue, are they consuming the queue's messages
such that your real consumers don't get all of them? Or are all of the
messages still on the queue despite these consumers having received a
million messages (per your screenshot in your original message)?
How often do thes
I'm not an NFS expert, but is vers=300 really correct? I don't think
there's an NFSv300.
Also, note that ActiveMQ offers the best support for shared-filesystem
master-slave on NFSv4, whereas NFSv3 has undesirable behavior (described in
https://activemq.apache.org/shared-file-system-master-slave) t
That makes sense. Thanks for sharing the resolution to the problem.
Tim
On Thu, May 7, 2020, 8:23 AM bstrange wrote:
> I've finally figured out what was causing this. Viewing the contents of a
> queue by clicking the queue name in the browser interface will spawn a
> consumer to view all of tha
Has there been any discussion of annotating the Artemis documentation to
specify which version adds support for a particular feature/option? The
ActiveMQ 5.x documentation is far from perfect, but one thing I like about
it is that it attempts to provide this information in at least some cases,
whic
as using the
> "latest" documentation when, in fact, he wasn't actually using the "latest"
> release.
>
>
> Justin
>
> [1]
>
> http://activemq.apache.org/components/artemis/documentation/latest/versions.html
>
> On Sun, May 10, 2020 at 8:17 P
I haven't done this, but believe it should be possible.
But I was surprised to see that your diagram only shows the use of
websockets for the hop from local broker to reverse proxy, and uses TCP
elsewhere. From your description, it sounded like you were intending to use
websockets on all network l
Looks great, thanks for sharing.
Tim
On Thu, May 14, 2020, 7:24 AM eleipold
wrote:
> With the help of this articles and a couple of others, I think I solved the
> problem. Below is a blog that I wrote on it:
>
>
> https://www.workhorseintegrations.com/2020/05/14/securing-activemq-console-with-l
You could write a plugin that would log the content of each message as it's
received; just log it and then call the corresponding
super.messageDelivered() method. Relevant information is at
https://activemq.apache.org/interceptors and
https://activemq.apache.org/developing-plugins.
Tim
On Thu, Ma
On Thu, May 21, 2020, 5:59 AM Tim Bain wrote:
> You could write a plugin that would log the content of each message as
> it's received; just log it and then call the corresponding
> super.messageDelivered() method. Relevant information is at
> https://activemq.apache.org/interce
Two different methods of viewing the message content both indicate that
there's no message body? That sounds like maybe your messages don't have
bodies...
I'm not an expert in Camel, but I've done enough with it to believe that
the method you found will capture the full message (headers and body),
No, I haven't yet found the block of time needed to reproduce the problem
and identify the root cause. Sorry, I know it's frustrating to ask for help
and not get it, but I do this as a volunteer in my personal time, and just
haven't found a large enough block of time when there wasn't something els
JB,
https://www.oracle.com/webfolder/technetwork/tutorials/obe/java/JMS2SharedConsumer/JMS2SharedConsumer.html
describes the feature, and the OP is correct that ActiveMQ 5.x and Amazon
MQ do not support it directly since they do not support JMS 2.0.
However, 5.x supports equivalent functionality
Oh, I just saw that Michael Andre Pearce wrote the same information, but my
mail app didn't group his response into the conversation so I didn't see it
before responding. Sorry for the duplication.
Tim
On Sat, May 30, 2020, 6:33 AM Tim Bain wrote:
> JB,
>
>
> https://ww
Does disabling one but not both of those things also fix the problem? Or is
the problem only eliminated if both are disabled?
Tim
On Mon, Jun 1, 2020, 7:44 AM sainath
wrote:
> Hi All,
>
> We disabled JMX and advisories, this seems to fix the memory issue.
>
> In the ActiveMQ.xml file we
>
> Add
Would CLIENT_ACKNOWLEDGE (or INDIVIDUAL_ACKNOWLEDGE, though I don't think
it buys you anything over CLIENT_ACKNOWLEDGE) delivery modes address your
use case, by allowing your clients control over when messages are acked?
Tim
On Wed, Jul 8, 2020, 5:57 AM Domenico Francesco Bruscino <
bruscin...@gm
My understanding is that that's a client limitation, that a browser will
refuse to make a websocket connection to a server other than the one that
served up the original web page, as a protection against malicious scripts
that make it into page via whatever attack vector.
Tim
On Wed, Jul 29, 2020
LevelDB support was removed in large part due to the absence of developers
willing to maintain the code and volunteers willing to provide support for
it on this mailing list. In the 5+ years I've been involved in this mailing
list, I don't recall ever seeing a LevelDB question answered (and I've
de
One way to test if it's a firewall issue is to try to open a raw TCP socket
to the port and see if you can establish a TCP connection and pass data. It
doesn't need to be compliant with the higher-level protocols (HTTP, STOMP),
it just needs to confirm that bytes are successfully passed. If bytes p
erver] AMQ221020: Started EPOLL
> Acceptor at 0.0.0.0:61616 for protocols
> [CORE,MQTT,AMQP,STOMP,HORNETQ,OPENWIRE]
>
> Using netstat may be helpful to confirm beyond all doubt, though.
>
>
> Justin
>
> On Fri, Aug 7, 2020 at 8:51 PM Tim Bain wrote:
>
> > One way to
It might also be helpful if you use Edge's developer tools to determine
what request (URL, parameters) is resulting in the 401. That might help
determine what's going on.
Tim
On Wed, Sep 2, 2020, 11:23 AM Justin Bertram wrote:
> What version of ActiveMQ are you using?
>
>
> Justin
>
> On Wed, S
Boris,
I'm not sure what the consequences would be if your underlying data store
doesn't support transactions and you simply perform a non-transactional
batch operation. I'd expect that recovery from failures wouldn't work
right, leaving some data written to the store when the broker expects it to
Note that the username in the error message is alfresco1, not alfresco, so
make sure you authorize the right user when you test explicitly authorizing
the user.
Tim
On Wed, Sep 9, 2020, 5:31 AM Jean-Baptiste Onofre wrote:
> OK,
>
> That’s weird as the advisory should be created by the broker it
Also, is 'all' a group you defined, and is alfresco1 in that group?
Tim
On Wed, Sep 9, 2020, 5:35 AM Tim Bain wrote:
> Note that the username in the error message is alfresco1, not alfresco, so
> make sure you authorize the right user when you test explicitly authorizing
>
ber of the `alfresco` group. Should I
> specify only users `authorizationEntry`?
>
> Thanks!
>
>
> From: Tim Bain
> Sent: 09 September 2020 12:41
> To: ActiveMQ Users
> Subject: Re: Please help me with authorisation configuration
>
> CA
ly worth trying with
only valid/existing groups, so only alfresco in this case, just to try to
get things working.
Tim
On Thu, Sep 10, 2020, 5:44 AM Tim Bain wrote:
> For the all group, I'm not aware of any default group that's created, and
> all of the examples I've seen had
TimeOfDay: !Ref MaintenanceTimeOfDay
> TimeZone: UTC
> Logs:
> Audit: false
> General: true
> AutoMinorVersionUpgrade: true
>
> Is there a way to debug things further? Maybe by having a look at the
> ActiveMQ logs, or using some kind of
>From the error message, it appears that the command line tool is attempting
to connect as a user named system. You could define that user in your Jetty
configuration (adding it to one of the groups that are authorized to access
that destination). I'm not sure how to know what password goes with th
Here's a full example from the ActiveMQ docs (
> http://activemq.apache.org/security) under "Controlling Access To
> Temporary Destinations". In the customer's config, it seems they are
> entering the user directly into the AuthorizationEntry, while in
pport!
>
> Best regards,
>
> Fabrice
>
> ____
> From: Tim Bain
> Sent: 26 September 2020 15:26
> To: ActiveMQ Users
> Subject: Re: Please help me with authorisation configuration
>
> CAUTION: This email originated from outside of
Sorry for the delay in responding to your questions.
I'm not aware of a better way to do what you're looking for. The advisories
are only about clients rather than the brokers themselves, and each broker
is only aware of state for themselves rather than anything network-wide, so
unfortunately ther
Brent,
Redeliveries aren't something that I go very deep on, but
https://activemq.apache.org/message-redelivery-and-dlq-handling only lists
four ways that redelivery should occur, and only #2 seems like it should be
applicable to the situation where the client connection closes abruptly. #2
involv
https://issues.apache.org/jira/browse/AMQ-6951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17228718#comment-17228718
recently asked whether Artemis has the security flaw listed on the bug
report for ActiveMQ 5.x. Can one of the Artemis-focused people on th
Thanks Gary.
Tim
On Tue, Nov 10, 2020, 6:14 AM Gary Tully wrote:
> it does not: see: https://issues.apache.org/jira/browse/ARTEMIS-1826 added
> same to the jira
>
> On Tue, 10 Nov 2020 at 03:16, Tim Bain wrote:
>
> >
> >
> https://issues.apache
Justin, is the documentation wrong for the boolean values for the legacy
forward-when-no-consumers attribute that it associates with STRICT and
ON_DEMAND? It seems like STRICT should be false and ON_DEMAND should be
true.
The problem with message redistribution (just like 5.x's store-and-forward
b
I assume there aren't any failures earlier in broker1's logs that might be
relevant?
>From those logs, it looks like Kubernetes is shutting down ActiveMQ rather
than ActiveMQ shutting itself down, based largely on the fact that there is
nothing that indicates that ActiveMQ initiated the shutdown.
This sounds like a bug. Please submit a bug in JIRA, ideally attaching a
minimal reproducer.
Thanks,
Tim
On Fri, Dec 11, 2020, 5:58 AM Martijn Brinkers (list) <
martijn.l...@gmail.com> wrote:
> I have embedded ActiveMQ inside a spring application.
>
> The broker is configured in XML and I explic
(org.apache.activemq.broker.BrokerService) [ActiveMQ
> >> ShutdownHook]
> >>
> >> A simple test application does not show this issue.
> >>
> >> If I disable (i.e., comment out) the following
> >> DefaultMessageListenerContainer, then the shutdown w
Thank you, both for capturing the stack trace and for writing the bug.
Tim
On Wed, Dec 16, 2020, 8:30 AM Martijn Brinkers (list) <
martijn.l...@gmail.com> wrote:
> I have added a JIRA bug report for this
>
> https://issues.apache.org/jira/browse/AMQ-8102
>
> Kind regards,
>
> Martijn Brinkers
>
For the embedded 2.10.1 broker case, are you saying that connections failed
when made from other threads in the process in which the broker was
embedded? If so, that would seem to rule out the network, since traffic
would never leave the host.
You mentioned capturing a stack trace, but have you do
Early in my time as an ActiveMQ user, I ran into unexpectedly poor
performance between a network of ActiveMQ 5.x brokers across a high-latency
network link. The particular situation I had involved links that were idle
long enough for the TCP congestion window to contract back to its min value
betwe
Another option would be to have the publisher send MQTT messages to Q1, the
consumer consume text messages from Q2, and then use an embedded Camel
route to translate messages on Q1 to text messages and send them to Q2.
https://activemq.apache.org/broker-camel-component
I've not used embedded Came
ridges.
>
>
> Brian
>
> > On Jan 12, 2021, at 10:20 PM, Tim Bain wrote:
> >
> > Early in my time as an ActiveMQ user, I ran into unexpectedly poor
> > performance between a network of ActiveMQ 5.x brokers across a
> high-latency
> > network link. The partic
Can you please submit a bug in JIRA for this behavior? If you're interested
in digging in and doing the investigation and the fix, that's great, but
let's get the problem captured, along with enough information to reproduce
the problem and test a fix. If you're interested in doing that, you might
w
If the third party simply puts a sleep at the end of their message-handling
logic, will that meet the need? If not, hearing what doesn't work about
that approach will help us to better understand exactly what's needed.
Tim
On Fri, Mar 19, 2021, 5:01 PM Christopher Pisz
wrote:
> I am using Artem
As an aside, while we wait for the OP to tell us whether any of these
suggestions are relevant to his situation:
In most cases, you want producers and consumers to be decoupled, so that a
slow consumer doesn't block its producers. Flow control is typically used
to protect the broker and to prevent
MP Consumer
>
> ---
>
> So are you saying that, as the Relay component will be blocked from
> publishing if the buffer queue is backed up, this will cause problems
> upstream?
>
>
>
> Dave
>
>
>
> On Tue, 23 Mar 2021 at 11:47, Tim Bain wrote:
>
> >
ver (maybe that's as simple as setting the TTL).
Sorry for missing your point in my first response.
Tim
On Wed, Mar 24, 2021, 5:47 AM Tim Bain wrote:
> I'm saying that in the scenario where you're preventing the producer from
> sending messages because the consumer h
One thing to keep in mind is that although the code may be slightly slower,
if it lets you use an API that is more favorable (which might mean better
documented, more portable, more stable across future versions, easier for
others to maintain because they're already familiar with it, or a number of
By default, topic consumers will receive only messages sent after they
subscribe. However, it is possible to configure the consumer to use a
retroactive subscription[1] to receive any previously sent messages that
haven't been acked by all existing subscribers and deleted by the broker.
By default,
I'm not aware of other options from within the broker. But you've asked
several questions about dynamic changes to the set of authorized users, so
I wonder if you'd be best served using an LDAP user store rather than the
bare-bones file-based auth store. In that case, you'd have access to all
the t
This sounds like a bug, since the closure of the inactive connections
doesn't seem to remove the associated subscriptions nor reduce the JMX
count accordingly. Can you please submit a bug in JIRA for this behavior?
Are you able to reproduce the problem on demand, ideally on a single broker
with mi
Be sure you understand what advisory support actually gives you (i.e. what
you're giving up by turning it off) before you lock into this workaround as
a permanent solution. See https://activemq.apache.org/advisory-message for
more info.
Also, if you're able to reproduce the problem reliably, would
Sounds great, thank you.
Tim
On Sun, Apr 11, 2021, 7:16 AM Prameet Patil
wrote:
> Yes definitely.
> I don't have access to the source code of the JMS clients. so i am not sure
> if i will be able to reproduce it in a clean environment.
> but will definitely give it a try and create a JIRA if i
I think you're asking how to ensure that the broker will close a client
connection if that connection is idle for 60s or longer. If so, that
setting is the wireFormat.maxInactivityDuration element of the URIs you
provided, and you'll want to change the current value of 0 to 6
(milliseconds) for
Note that the comments on AMQ-7426 (Log4J 2) state the following:
ActiveMQ is not affected by CVE-2019-17571 directly as we don't use the
SocketServer.
The upgrade does not appear to be in 5.16.2, so expect that to remain in
your scan results, and you'll have to manually adjudicate the finding.
If instead of staying up and attempting to reconnect to the database (while
still servicing requests without a database connection, whatever that would
mean), would you be OK with having ActiveMQ restart repeatedly until the
database is available again?
Also, is this 5.x or Artemis?
Tim
On Thu,
; So what the script would do then is,
> when detecting that the broker has stopped, basically shutdown all
> dependent processes,
> then have the script loop and check for DB-availability,
> when it comes back first restart the broker, then all the listeners.
> This is outside the sc
Matt and JB seem to have answered different questions, where Matt seemed to
be talking about segmenting a single config across multiple files and JB
was talking about the ability to have multiple distinct configs and choose
one of them when launching. Which of those scenarios do you mean?
Tim
On
i set the timeout option as following, I can't ensure that the
> broker closed a client
> connection.
> Can you tell me how to confirm the disconnection when the timeout has
> expired?
>
> ----
1 - 100 of 2340 matches
Mail list logo
