You might be hitting the ephemeral nature of Kubernetes on-disk files.
See Kubernetes documentation.
https://kubernetes.io/docs/concepts/storage/volumes/
Youyu
Information Classification *General
-Original Message-
From: Justin Bertram
Sent: Wednesday, September 13, 2023 1:29 PM
To: us
We have experienced the similar problems.
1. Some of consumers (listens the same JMS topic) would stop receiving messages
while others are working perfectly. We haven't identified the root cause but
figured a way to resolve it. We institute (JMS consumer) a time-bound read and
track the last ti
We have experienced the similar problems.
1. Some of consumers (listens the same JMS topic) would stop receiving messages
while others are working perfectly. We haven't identified the root cause but
figured a way to resolve it. We institute (JMS consumer) a time-bound read and
track the last ti
-Oorspronkelijk bericht-
Van: Youyu Shao
Verzonden: vrijdag 5 november 2021 17:21
Aan: users@activemq.apache.org
Onderwerp: Artemis JMS queue paging prevents JMS consumer to receive newly
added message
EXTERNAL SENDER: Do not click any links or open any attachments unless you
trust th
Hi,
While investigating performance related issues, we discovered that once Artemis
JMS queue starts paging, newly produced message are not visible (within 60
seconds receive timeout) until most of the messages in the front (of that
queue) are consumed.
We have Artemis (2.11.0) in productio
I hope this can be achieved via ActiveMQConnectionFactory.setCallTimeout(...)
before creating JMS connection.
Youyu
From: Martin Lichtin
Sent: Thursday, September 23, 2021 1:06 PM
To: users@activemq.apache.org
Subject: [EXTERNAL] Re: ActiveMQ classic - ActiveMQConnection - Connect
Response Time
error unless configured to do otherwise
On Mon, 30 Aug 2021 at 23:06, Youyu Shao mailto:ys...@crd.com>>
wrote:
>
> Hi,
>
> We have being using Artemis 2.11.0 for a while. Recently we had an issue of
> file access violation as captured in the following two consecutive Artem
Hi,
We have being using Artemis 2.11.0 for a while. Recently we had an issue of
file access violation as captured in the following two consecutive Artemis log
entries:
2021-08-26 00:40:46,308 WARN [org.apache.activemq.artemis.core.server]
AMQ222010: Critical IO Error, shutting down the server
Hi,
What is the reason that method: public void writeUTF(final String value) of
org.apache.activemq.artemis.jms.client.ActiveMQBytesMessage.java imposes
length limit on the input string parameter? It seems that the length is
limited to either 32767 (or 65535).
wrtieUTF(...) is a JMS interface met
Hi,
What is the reason that method: public void writeUTF(final String value) of
org.apache.activemq.artemis.jms.client.ActiveMQBytesMessage.java imposes
length limit on the input string parameter? It seems that the length is
limited to either 32767 (or 65535).
writeUTF(…) is a JMS interface metho
Thank you very much. This is very helpful. What is the timeframe for 2.7.0?
Thanks again,
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hello,
We are using Artemis 2.6.2 as JMS server/broker. We have one JMS connection
created from
org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.
We have two JMS queues, both are used as task distribution/load-balancing
mechanism.
One queue contains complex tasks taking long time
Hi Mike,
Thank you very much for your input. In my case we do have SSD. After some
reading and fumbling, I am able to get the about 2000 sending/receiving
operations per second, with one message per transaction.
The specific adjustments I have done to achieve the above were:
1. using MAPPED --
Hi,
Recently we start evaluating Artemis 2.4.0 JMS queue performance. Our
business logic requires
the use of transactional session, where publisher sends one message per
commit, and
consumer receives one message per commit.
Our test environment is Windows machine with 4 cores(3.70 GHz), 8 logica
14 matches
Mail list logo
