Created Jira https://issues.apache.org/jira/browse/AMQ-9569
On 04.09.2024 20:32, Martin Lichtin wrote:
We often encounter this call stack, with the suspicion that the thread
forever hangs in the socket read:
"ActiveMQ Task-5" #195869202 daemon prio=5 os_prio=0
tid=0x7f8b68
ue debugging, but wanted to reach out in case I'm on the wrong
path, or on to something
- Martin
-
To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org
For additional commands, e-mail: users-h...@activemq.apache
Hi
After upgrading from 5.16.7 to 5.18.4, we're seeing sometimes wrong
'inflight' count (gathered from DestinationStatistics). It's returning
negative numbers..
Has anyone else experienced this?
- Martin
CRYPT).
I look forward to your feedback.
Best regards
Martin
Hi JB
Thank you so much. Very appreciated.
Best regards
Martin
-Ursprüngliche Nachricht-
Von: Jean-Baptiste Onofré
Gesendet: Donnerstag, 11. April 2024 07:25
An: users@activemq.apache.org
Betreff: Re: Disabled authentication ActiveMQ Classic Webapps since V6.x
H Martin
For the
ility). Because all those
updated from 5x to 6x could have a security issue now.
I wanted to report the issue as friendly hint only.
Best regards
Martin
-Ursprüngliche Nachricht-
Von: Vilius Šumskas
Gesendet: Mittwoch, 10. April 2024 13:47
An: users@activemq.apache.org
Betreff: RE: Dis
should protect everything.
--
Vilius
-Original Message-
From: Zeissig, Martin
Sent: Wednesday, April 10, 2024 12:33 PM
To: users@activemq.apache.org
Subject: Disabled authentication ActiveMQ Classic Webapps since V6.x
Dear Community
I have updated from ActiveMQ Classic 5.x to 6.1.1
nge
>intentional or is this a bug?
I recommend restricting access to root (/) to fully protect all endpoints.
Lower security can be setup by users manually if needed.
Best regards
Martin
the store (store
useless when non persistent).
As persistent is a message property, you can keep the store just for the lease.
Can you please create a Jira about that ? I can add something around that.
Regards
JB
On Wed, Nov 29, 2023 at 9:19 AM Martin Lichtin
wrote:
I'd like to con
I'd like to configure ActiveMQ classic for non-persistent messaging,
with a database lease locker.
How can this be done?
Configuring then at startup it says:
persistent="false", ignoring configured persistenceAdapter
but the "lease-database-locker" must be configured inside:
When configuring an ActiveMQ client connection, does this look reasonable:
failover:(nio+ssl://1.2.8.2:61616,nio+ssl://1.2.8.3:61616)?randomize=false&nested.verifyHostName=false&socket.enabledProtocols=TLSv1.2&socket.enabledCipherSuites=TLS_RSA_WITH_AES_256_CBC_SHA256
Or do the socket options al
, the browser no longer overwrites the cookies and the sessions
> are not lost.
>
> e.
>
> -Oorspronkelijk bericht-
> Van: David Martin
> Verzonden: dinsdag 26 april 2022 11:01
> Aan: users@activemq.apache.org
> Onderwerp: Re: Artemis Cluster Management UI
>
>
>
One thing that could help a bit would be to bookmark a set of tabs in the
browser but unfortunately when logging into a broker any existing session
for another broker is invalidated. Perhaps there is a broker-side setting
in hawtio to allow multiple concurrent sessions for different brokers in
one
[13:40:50 WRN] Connection Failed: activemq://localhost:61616/
Apache.NMS.NMSConnectionException: Could not create the IConnectionFactory
implementation: Value cannot be null. (Parameter 'path1')
---> System.ArgumentNullException: Value cannot be null. (Parameter
'path1')
at System.IO.Path.Combi
Thanks Clebert - I guess this is related to ARTEMIS-3587 so will go to 2.20
asap.
On Mon, 20 Dec 2021 at 20:05, Clebert Suconic
wrote:
> You should try 2.20.0 that's being released now
>
> On Mon, Dec 20, 2021 at 10:11 AM David Martin wrote:
> >
> > FYI found a simi
FYI found a similar issue as the OPs after upgrading from 2.16 to 2.18 -
perhaps 2.18 is better at detecting slow paths, can see some related
tickets in 2.17 and 2.18 release notes.
Turned out to be MiB/s throttling on cloud storage - increasing the
allocation increased the threshold at which thro
2:41, Tim Bain wrote:
> Great, I'm glad you were able to figure it out, and thanks for sharing the
> root cause once you found it.
>
> Tim
>
> On Mon, Dec 6, 2021, 5:24 AM David Martin wrote:
>
> > Domenico, Tim,
> >
> > I've figured it out.
>
tered Hawtio's behaviour -
-Dcom.sun.management.jmxremote.authenticate=false perhaps?
Thanks for all of your help,
Dave
On Mon, 6 Dec 2021 at 10:33, David Martin wrote:
> Hi Domenico,
>
> root@artemis-0:/var/lib/artemis/etc# ls -l
> total 44
> -rw-r--r-- 1 artemis a
icrok8s locally but I could try a different k8s next.
Thanks,
Dave
On Sun, 5 Dec 2021 at 13:40, Tim Bain wrote:
> To take the K8s networking out of the equation, maybe kubectl exec a shell
> session into the container and invoke the curl command against localhost?
>
> And while yo
> could you get the artemis etc folder from your kubernetes container
> and share it?
>
> Thanks,
> Domenico
>
>
> On Fri, 3 Dec 2021 at 17:17, David Martin wrote:
>
> > Hi Domenico,
> >
> > Thanks - after further experimentation It appears to be rel
t;0.0.0.0\"","attribute":"AddressMemoryUsage","type":"read"},"error_type":"java.lang.Exception","error":"java.lang.Exception
> : User not authorized to access attribute:
> AddressMemoryUsage","status":403}
mq,monitor"\/>/' ./broker/etc/management.xml
>
> 5) run the broker
> ./broker/bin/artemis run
>
> 6) read the Active attribute
> curl -H "Origin:http://localhost:8161"; -u test:test
>
> http://localhost:8161/console/jolokia/read/org.apache.activemq.ar
;
> 5) run the broker
> ./broker/bin/artemis run
>
> 6) read the Active attribute
> curl -H "Origin:http://localhost:8161"; -u test:test
>
> http://localhost:8161/console/jolokia/read/org.apache.activemq.artemis:broker=\
> "0.0.0.0\"/Active
>
> {"request":{"mbean&qu
Hi all,
I'm trying to configure role access via the Jolokia REST API for the single
attribute "Active" on the "org.apache.activemq.artemis" domain.
I have a user with a role "monitor" and want them to be able to access
nothing but the above attribute via e.g.
/console/jolokia/read/org.apache.acti
ested/supported configuration. Has anyone
else gotten TLS 1.3 working with ActiveMQ?
Thank you,
Martin
Unfortunately I believe it's not one of these timeouts.
What you mention below affects TcpTransport, but here we're talking about a
setter for ActiveMQConnection
On 2021/09/23 16:41:24, Matt Pavlovich wrote:
> Hi Martin->
>
> Check out the docs here: https://activemq.ap
e sense to configure a relatively short timeout value.
- Martin
> clientID to the same broker.
>
> Regards,
> Domenico
>
>
> On Fri, 23 Jul 2021 at 14:02, David Martin wrote:
>
> > Hi Domenico,
> >
> > OK thanks I'll have a look at that.
> >
> > Was considering writing a plugin to block authorisati
fix this issue by redirecting each client with the same
> > clientID to the same broker.
> >
> > Regards,
> > Domenico
> >
> >
> > On Fri, 23 Jul 2021 at 14:02, David Martin wrote:
> >
> > > Hi Domenico,
> > >
> > > OK thanks I'll
balance incoming client connections according to their ClientID (or other
> connection parameters), see the draft documentation[2] for further details.
>
> [2]
>
> https://github.com/brusdev/activemq-artemis/blob/broker_balancers/docs/user-manual/en/broker-balancers.md
>
> Rega
Hi all,
Puzzled by some behaviour we're seeing on a broker cluster of 3 live
Artemis v2.16.0 brokers hosted on k8s which has an F5 in front of it
terminating TLS and routing to a k8s node port forwarding to an AMQP
acceptor for each broker. The cluster is healthy and has been up for about
2 months
Looks like I ran into changes https://issues.apache.org/jira/browse/AMQ-2659
and will need to adapt to it.
On 01.05.2021 16:15, Martin Lichtin wrote:
Hi
Has anyone also noticed an issue with queue browsing with 5.16.2?
It happens when using an XA connection and starting a session without a
javax.jms.JMSException: Session's XAResource has not been enlisted in a
distributed transaction.
at
org.apache.activemq.ActiveMQXASession.doStartTransaction(ActiveMQXASession.java:101)
~[?:?]
I'll investigate further, just wanted to see if this is already a known issue.
- Martin
s possible
> > to architect a system to limit the producer when the consumer is behind,
> > I'd be very hesitant to do so, and would strongly consider other
> approaches
> > such as speeding up the consumer or configuring the message broker to
> drop
> > messag
ld be very cautious
> about any architecture that proposed the intentional linking of producer
> processes and consumer processes via a flow control window, since it can
> broaden the impact of problems beyond the process that is experiencing
> them.
>
> Tim
>
> On Sat, Mar 2
Hello,
You could possibly try producer window-based flow control to stop messages
backing up on the queue when consumers are offline (e.g. using an
intermediate queue to store the backlog) -
https://activemq.apache.org/components/artemis/documentation/1.0.0/flow-control.html
Dave
On Fri, Mar
gt; >
> >
> > So I think it would be considerable safe to do reconnect the POD.
> >
> > So a damage in the file system or journal after a failure is IMO a
> disaster situation. And for that I can only think of the mirror to mitigate
> any of that.
> >
> >
Sorry, just to add. I could create a kubernetes service for publishers with
affinity to 2 of 4 brokers and another service for consumers with affinity
to the other 2 but looking for something more dynamic if possible, to be
able to scale out seamlessly.
On Thu, 11 Mar 2021 at 13:52, David Martin
ther 2, somehow?
Thanks for any advice you can offer.
Dave Martin.
Added a comment toAMQ-7298 on how to reproduce the issue:
https://issues.apache.org/jira/browse/AMQ-7298?focusedCommentId=17292431&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17292431
On 01.02.2021 16:41, Martin Lichtin wrote:
It could be related to AMQ-
these tasks to be created in
the first place? JMX doesn't seem to have anything relevant.
Thanks,
Martin
, Martin Lichtin a écrit :
There's no exception, but the re-delivery no longer works.
It's a server-side redelivery case, configuring the broker with the
redeliveryPlugin, such as:
, but JMSRedelivered will be set to true, and
another header tells the consumer the redelivery count.
Any version before 5.16.0, this works fine and the "suppressing duplicate" does
not occur.
- Martin
On 27.01.2021 19:24, Jean-Baptiste Onofre wrote:
Hi Martin,
Do you have some
Hi, has anything changed regarding server-side redelivery using the
?
Going from 5.15.14 to 5.16.1, it seems to no longer work as expected.
I see AMQ-7298 which may contribute to a change in this area.
- Martin
There's something seemingly weird going on when connecting with a browser to
the ssl-secured Openwire port of an ActiveMQ (classic) server.
Using this Url: https://AMQ-HOST:OPENWIRE-PORT
The browser sends off a GET request and after 30 seconds actually receives a
response from ActiveMQ.
The pa
In theory, yes, an iptables or firewalld approach would work.
But certain customers doing pen-testing require the solution to be
self-sufficient, so I'll need
this kind of access control as part of the listen-accept logic of the ActiveMQ
broker.
- Martin
On 02.09.2020 18:14, Justin Be
Yes. 5.15.13. It may be an issue with the SSL connector only.
https://issues.apache.org/jira/browse/AMQ-8030
https://issues.apache.org/jira/browse/AMQ-8031
- Martin
On 31.08.2020 06:08, Jean-Baptiste Onofre wrote:
Hi,
I guess you are talking about TCP/OpenWire transport connector.
Which
o
reject rogue connections as early as possible.
Note the current behaviour is quite bad, ActiveMQ accepts connections and
doesn't drop them (client doesn't send any data), thus eventually exceeding the
maximum number of allowed client connections and resulting in DoS.
- Martin
Hi Alex,
I'm not one of the maintainers and maybe they will respond.
To clarify, are you asking whether routing high volumes of messages though
a large number of addresses is likely to lead to poor performance versus
using a small number of addresses?
I can't answer that but Artemis was designed
to it
Just an idea. I'm hoping there are other, already available, solutions.
- Martin
mq-artemis/blob/master/tests/activemq5-unit-tests/src/test/java/org/apache/activemq/blob/FTPBlobTest.java
>
>
>
> -Ursprüngliche Nachricht-
> Von: David Martin
> Gesendet: Donnerstag, 12. März 2020 10:47
> An: users@activemq.apache.org
> Betreff: Re: Support for BLOB typ
Hi Tobias,
Is there a specific reason for needing BlobMessage support?
If you just want to send binary messages, including very large ones, both
BytesMessage and StreamMessage are supported.
https://activemq.apache.org/components/artemis/documentation/latest/large-messages.html
Dave
VAT Regis
Hi
I've written a plugin for ActiveMQ that monitors disk space usage and that will
close the connectors on low disk space (and re-open once disk space is again
sufficient). Let me know know in case you are interested.
- Martin
On 02.03.2020 12:24, COURTAULT Francois wrote:
Hello,
I su
I was just suggesting to check your cluster configuration against the
reference examples, to make sure the nodes are actually working as a group.
Could it be something as simple as the "ha" URI parameter being
case-sensitive? In all the examples it's in lower case, not uppercase as
you have it.
Hi
Have you checked out the various examples for discovery here -
https://github.com/apache/activemq-artemis/tree/master/examples/features/clustered
?
Dave
On Thu, Feb 27, 2020 at 8:18 AM Jarek Przygódzki
wrote:
> Hi,
> I've been experimenting with Artemis cluster. Apparently remote clien
t step is to raise a feature ticket for this?
Thanks again
Dave
On Thu, Feb 20, 2020 at 5:15 PM David Martin wrote:
> Hi Justin,
>
> Having done some analysis I think I need to do the following however it
> appears that QueueConfig is intended to be immutable so maybe point (3)
t; change the code to allow it in certain places like this.
>
> Would you be willing to send a PR with the changes you need?
>
>
> Justin
>
> On Sat, Feb 15, 2020 at 11:14 AM David Martin wrote:
>
> > Hi Justin,
> >
> > AMQP or Core - can be either
> >
>
> Would you be willing to send a PR with the changes you need?
>
>
> Justin
>
> On Sat, Feb 15, 2020 at 11:14 AM David Martin wrote:
>
> > Hi Justin,
> >
> > AMQP or Core - can be either
> >
> >
> > Thanks,
> >
> &
Hi Justin,
AMQP or Core - can be either
Thanks,
Dave
On Fri, Feb 14, 2020, 11:02 PM Justin Bertram wrote:
> What protocol are your clients going to be using?
>
>
> Justin
>
> On Fri, Feb 14, 2020 at 3:28 PM David Martin wrote:
>
> > Thanks Chris -
> >
; https://github.com/apache/activemq-artemis/blob/master/artemis-server/src/main/java/org/apache/activemq/artemis/core/server/plugin/ActiveMQServerConsumerPlugin.java
>
> On Thu, Feb 13, 2020 at 9:59 AM David Martin wrote:
>
> > Hi everyone,
> >
> > Decided to switch to Ar
Hi everyone,
Decided to switch to Artemis which is not going to be difficult in the main
but not sure of my best option to migrate an AMQv5 broker plugin which
overrides *addConsumer()* to set a new destination and a message selector
using broker-side business logic based on the user credentials.
Hi everyone,
Decided to switch to Artemis which is not going to be difficult in the main
but not sure of my best option to migrate a broker plugin which overrides
*addConsumer()* to set a new destination and a message selector using
broker-side business logic based on the user credentials. It look
make this behaviour configurable.
Thanks much
- Martin
On 04.02.2020 05:33, Jean-Baptiste Onofré wrote:
Hi Martin,
Just to be sure: did you enable DLQ for non persistent message ?
I'm splitted about that: as a message in DLQ never expired, I would
expect that it would stay forever (as
tence requirements.
If the current behaviour makes sense for anyone, then please at least can we
make it configurable? I'm happy to help.
- Martin
On 30.01.2020 17:41, Jean-Baptiste Onofré wrote:
Hi,
If you enable DLQ to non-persistent message (it's disabled by default),
then, IMHO
stent(true);
message.setProperty("originalDeliveryMode", "NON_PERSISTENT");
}
I'm puzzled as to why this would make sense.
A non-persistent message, even if configured to use DLQ, should stay
non-persistent, i.e. not survive broker restarts.
- Martin
d of expertise. I find that most
of the documentation for Hawtio is either dead links or lacking. I don't
seem to be finding any recent solutions to the problem so any help is very
much welcome!
Regards,
Martin
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hi, is this property still set by the broker server?
I'm not seeing it when consuming a message.. at least not when using Camel JMS
consumer.
- Martin
No problem - nb it's port 8161 not 8162
From: jb6622
Sent: 03 June 2019 21:56:30
To: users@activemq.apache.org
Subject: RE: Simple high availability setup
Hi Dave,
Many thanks, that's an interesting approach - we are indeed using v5. I'll
look into our load balan
Hi
What version of ActiveMQ are you referring to? For v5, it is possible to have a
load balancer health check http://hostname:8162/jolokia/api on both broker
instances of a master/slave setup - if it receives a response then this is the
master and it should direct all traffic to this node.
Da
I have used QPID JMS as an ActiveMQ client with no issues so would recommend
you persevere with it.
-Original Message-
From: cooshal
Sent: 17 April 2019 13:51
To: users@activemq.apache.org
Subject: RE: Invoking JMS API with JMS 2.0, ActiveMQ and osgi (karaf)
I just had a quick look at Q
A possible option is to use the QPID JMS driver - this is a v2.0 driver - with
Active MQ v5. It uses AMQP to communicate with Active MQ instead of Openwire.
-Original Message-
From: cooshal
Sent: 17 April 2019 08:32
To: users@activemq.apache.org
Subject: Invoking JMS API with JMS 2.0, Ac
Hi everyone,
How does AMQ 5.4+ serve websockets clients as per
https://activemq.apache.org/websockets.html, and, how can it be configured?
There is no Jetty webapp for it so there is no web.xml that I can update to
relax the same origin policy.
Thanks,
Dave
ct is that the broker gets restarted and will try to
acquire the lease lock again.
- Martin
On 09.03.2019 03:05, Tim Bain wrote:
It's my understanding that restarts are handled by the Tanuki service
wrapper, when ActiveMQ is installed as a service, using the instructions at
http://activemq.
ger
issue is that after stopping, it does not restart to retry acquiring the lock.
Is there a configuration I'm missing? The code in LockableServiceSupport
actually requests a restart, but where is that re-start done?
Thanks for any insight
- Martin
It turned out there's a configuration setting on the broker that causes it to
timeout remote durable subscribers:
I'm not creating any durable subscribers in my application code, but it
appears that when you use a broker as a network bridge it creates durable
subscriptions on behalf of the topic s
I have a problem with my Network of Brokers setup. I posted the question on
stackoverflow.com. If you have any experience with that setup and think you
might be able to help, please take a look:
https://stackoverflow.com/questions/49052541/why-does-this-activemq-broker-configuration-fail-after-many
the
above?
Thanks,
Martin
the code that would recognize
> that something's not right. I'd like to see what if anything Martin can
> tell us about how he figured out what was wrong in his code, in the hopes
> that that might lead you to something that would be useful for you as well,
> so hopefully he&#x
Thanks Morgan,
In the end I figured out that the threads were killed and started by the
code on my side hence the constant retries.
Sorry for all the noise about this.
M
On Thu, May 18, 2017 at 4:51 PM, Morgan wrote:
> MartinEden do you have the Inactivity Monitor running on both client and
>
Hi Clebert,
Would be great if you could repost here once you have a link to the
recording.
Much appreciated,
M
On Wed, May 17, 2017 at 7:42 PM, Clebert Suconic
wrote:
> There was a camera recording the event.
>
> However I don't know how to recover the recording yet:
>
> http://sched.co/9zwW
>
Hi,
Related to what Ragoubi is experiencing, I posted a message a few days ago
with this title: *Experiencing constant reconnects with paho Java client
v1.1.1 and broker Active MQ 5.14.3.*
I am basically seeing constant reconnects for both MqttClient instances
(one subscriber and one publisher) u
Hi all,
I am using Active MQ 5.14.3 as an MQTT broker. I am talking to it using the
paho java client v1.1.1.
My application uses a paho MQTT client to subscribe to a certain topic. I
am also setting manual acks so when it gets a callback (each time a msg
arrives) it does not ack immediately the m
Hi everyone,
I am experiencing constant reconnects from my paho MQTT subscriber and
publisher clients running inside a JVM on my Mac talking to a Active MQ
instance running in Virtual BOX also on my Mac.
The protocol is MQTT.
It is an integration test where I am trying to test a simple app that
JIRA: https://issues.apache.org/jira/browse/AMQ-
I'm running now with a patched version without the "command.isMessage()"
condition and fail-over behaviour has substantially improved.
Can't really judge whether it is the correct fix, however.
- Martin
On 30.04.2017 1
rt.get();
}
The timeout is set to 5000ms and should have hit a long time ago, but I guess
"command.isMessage()" returns false in this situation?
Any reason this condition is needed? It seems to me anything that can't be sent
within the timeout should cause the throw.
- Martin
act a specific group,
can I tell the broker about this in advance?
Thanks - Martin
have a workaround?
- Martin
r,
Ubuntu has been using their own upstart (https://en.wikipedia.org/wiki/Upstart)
in between Upstart.
Regards,
Martin
Van: maneeshmp
Verzonden: vrijdag 14 oktober 2016 18:38:22
Aan: users@activemq.apache.org
Onderwerp: Re: sudo update-rc.d activemq multiu
Hi,
I believe this is not an activemq issue, but an update-rc.d problem. On which
distro+version are you running activemq?
I would have been using 'sudo update-rc.d activemq defaults'.
HTH,
Martin
Van: maneeshmp
Verzonden: vrijdag 14 oktober
The solution/workaround for us was to move away the 3 db.* files and let Kahadb
start with only the journal files.
It recreated the 'index' files and since then we're ok.
On 05.10.2016 14:48, Tim Bain wrote:
Martin Lichtin, did you ever resolve what was causing your problem,
Hi
After upgrading from a 5.12.x version to 5.14.0, it looks like
ActiveMQServiceFactory,
instantiating the Spring application context, has a problem accessing the Spring
schema and resorts to trying to access the Internet.
Any ideas what could have changed that's causing this unwanted remote acc
Hi Martin,
When updating from 5.11 to 5.14 I encountered a different issue (which might
have existed during earlier upgrades as well). I am in the situation that I can
remove the kahadb contents before starting 5.14. Maybe that can be a solution
for you as well.
Also see the thread
When trying to upgrade from 5.12.2 to 5.14.0 we encounter this exception at
startup:
Caused by: java.io.IOException: Detected missing journal files. [3]
at
org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:978)[102:org.apache.activemq.activemq-osgi:5.14.0]
at
your error log: check if the indexes have the
latest version. For more info see the archives for 'Updating KahaDB' at
http://mail-archives.apache.org/mod_mbox/activemq-users/201608.mbox/browser
HTH,
Martin
Van: xabhi
Verzonden: woensdag 10 augustus 2016 8:45
Aan: users@acti
,
Martin
Van: pdudits
Verzonden: donderdag 4 augustus 2016 16:33
Aan: users@activemq.apache.org
Onderwerp: Messages piling up in FailoverTranport
Hello,
I'm facing a situation where client go OutOfMemory due to ever growing
transaction log in
FailoverTransport.stateTracker.connectionState
again!
Martin
Met vriendelijke groet/Kind regards,
Martin Herrman
Manager DevOps
[YMOR]<http://www.ymor.com>
Ptolemaeuslaan 70
3528 BP Utrecht
Mobiel: +31 6 10761936
Kantoor:+31(0)30 6021149
Email: mherr...@ymor.nl
[ITOA]
Van reactief naar preventief IT-beheer?
Download de whit
the kahadb files, not the activemq.xml.
Any hints, tips or advise?
Thanks in advance!
Met vriendelijke groet/Kind regards,
Martin Herrman
Manager DevOps
[YMOR]<http://www.ymor.com>
Ptolemaeuslaan 70
3528 BP Utrecht
Mobiel: +31 6 10761936
Kantoor:+31(0)30 6021149
Email: mherr...@ym
I see a large amount of PageOverflowIOExceptions being thrown (~ 60/sec) when
producing messages.
Is this to be expected or does this perhaps indicate an issue in the broker
configuration?
(note the exception doesn't bubble up, it is caught internally to handle a
"split" situation.)
Hi,
It's been quite some time now and I just wanted to follow up for
archiving purposes. Since we updated everything to 5.13, we don't see
the issue any more. I am convinced it had been caused by the 5.7
client library.
Best regards,
Martin
On Sat, Jan 9, 2016 at 6:24 AM, Tim B
request!
On Apr 9, 2016 11:51 AM, "Martin Lichtin" wrote:
With a test sending 5000 messages to a queue, I see heavy CPU use on the
broker side (v 5.12.2).
Using Yourkit it shows that the hot spot methods are
FilePendingMessageCursor.isEmpty() iterates over in-memory messages and
therefore
1 - 100 of 232 matches
Mail list logo
