//issues.apache.org/jira/browse/ARTEMIS-2173
> >
> > Slava.
> >
> >
> >
> > --
> > Sent from:
> > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
> >
>
--
Clebert Suconic
nts/artemis/documentation/latest/address-model.html.
>
> Regards,
> Domenico
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
--
Clebert Suconic
or at least.. there's a back-off period.. I forgot the name now...
where you can set a timeout to remove the queue.. lets say if no
clients reconnecting in 5 minutes.
@Domenico: remember what I'm talking about?
On Fri, Mar 20, 2020 at 11:48 AM Clebert Suconic
wrote:
>
>
/activemq.apache.org/components/artemis/documentation/latest/address-model.html
>
> Regards,
> Domenico
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
--
Clebert Suconic
hanks for all the contributors to this release.
--
Clebert Suconic
I'm pleased to announce the release of ActiveMQ Artemis 2.13.0
Downloads are now available at:
http://activemq.apache.org/artemis/download.html
This version has some major improvements on AMQP Performance. We
performed extensive tests with AMQP and found a few minor changes that
made a huge impa
.com/file/t378961/artemis_stacktrace.txt>
>
> A thread dump on the clients report that basically all JMS related threads
> are stuck at the same place, see attached file client_threads.txt
> <http://activemq.2283324.n4.nabble.com/file/t378961/client_threads.txt>
>
> Br,
> Anton
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
--
Clebert Suconic
te independently of the
> broker over time.
>
> Br,
> Anton
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
--
Clebert Suconic
expected usage of queues, is it? Because I will need that queues would be
> very cheap and have something like a multitopic subscription for consumers.
Why don't you make a message for the invoice as I said?
>
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
--
Clebert Suconic
ents that hold the messages in Delivering) connected to them, but
> their corresponding sessions point to a non-existent connectionID.
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
--
Clebert Suconic
ng the documentation
> (https://activemq.apache.org/components/artemis/documentation/1.0.0/resource-limits.html),
> I would expect that the number of connections is not limited.
>
> So I have two issues where I would appreciate any help:
> 1. Why is the number of connections limited in my scenario?
> 2. How can my broker get rid of the „dead" bindings of the „crashed“ clients?
>
> Thanks a lot
> Tobias
--
Clebert Suconic
if you're facing some bug more specifically, i would ask you to
produce a testcase and try it with a later version.
Perhaps what you need is a non durable queue, that would be removed
when the connection is gone?
On Tue, Jun 23, 2020 at 4:40 PM Clebert Suconic
wrote:
>
> Artemis doe
temis/download/release-notes-2.14.0
--
Clebert Suconic
bal-Max-Size: 104857600
> Xms/XmX: 512M/2G
> Platform: Windows
> Message size: < 1K/message
> Scheduled messages: 10k - 100k / night
> Total messages: approx 500k/day
> Consumers: MDBs on 12 Wildfly servers, about 500 instances
>
> Thanks for any insights anyone can offer,
> -a
>
--
Clebert Suconic
es of America. WHG (International)
> Limited is registered in Gibraltar and has its registered office at 6/1
> Waterport Place, Gibraltar. Mr Green Limited is registered in Malta and has
> its registered office at Tagliaferro Business Centre, Level 7, 14 High
> Street, Sliema SLM 1549, Malta. Unless specifically indicated otherwise,
> the contents of this e-mail are subject to contract; and are not an
> official statement, and do not necessarily represent the views, of William
> Hill PLC, its subsidiaries or affiliated companies. Please note that
> neither William Hill PLC, nor its subsidiaries and affiliated companies can
> accept any responsibility for any viruses contained within this e-mail and
> it is your responsibility to scan any emails and their attachments. William
> Hill PLC, its subsidiaries and affiliated companies may monitor e-mail
> traffic data and also the content of e-mails for effective operation of the
> e-mail system, or for security, purposes.
>
--
Clebert Suconic
);
> > jmsTemplate.setSessionTransacted(true);
> > jmsTemplate.setSessionAcknowledgeMode(Session.AUTO_ACKNOWLEDGE);
> > jmsTemplate.setExplicitQosEnabled(true);
> > jmsTemplate.setPriority(Jms.DEFAULT_PRIORITY);
> > jmsTemplate.setReceiveTimeout(1000);
> > ---
> >
> > Message receiving is implemented with multiple ListenerContainers.
> > One group of containers configured like that:
> > ---
> > DefaultMessageListenerContainer container = new
> BackGroundClusterNodeListenerContainer(args);
> > container.setConnectionFactory(connectionFactory);
> > container.setCacheLevel(2);
> > container.setReceiveTimeout(1500);
> > container.setDestinationName(destinationName);
> > container.setConcurrency("8-8");
> > container.setBeanName(containerID);
> > container.setAutoStartup(true);
> > container.setMessageListener(messageListener);
> > container.setSessionTransacted(false);
> > container.setSessionAcknowledgeMode(AUTO_ACKNOWLEDGE);
> > ---
> >
> > Another one is like that:
> > ---
> > DefaultMessageListenerContainer container = new
> DefaultMessageListenerContainer();
> > container.setDestinationName(destinationName);
> > container.setConnectionFactory(connectionFactory);
> > container.setConcurrentConsumers(3)
> > container.setSessionAcknowledgeMode(101)
> >
> container.setCacheLevel(modules.reportBuilderHelper.MESSAGE_LISTENER_CACHE_LEVEL)
> > container.setExceptionListener(t ->
> > {
> > Throwable rootCause = ExceptionUtils.getRootCause(t);
> > LOG.error("An error occured in listener for " + destination,
> rootCause);
> > });
> > container.afterPropertiesSet();
> > container.start();
> > ---
> >
> > Connection factory for the first two cases is created like that:
> > ---
> > final Map nettyParams = new HashMap<>(2);
> > nettyParams.put("host", host);
> > nettyParams.put("port", port);
> > nettyParams.put(TransportConstants.NETTY_CONNECT_TIMEOUT, 6);
> > nettyParams.put(TransportConstants.REMOTING_THREADS_PROPNAME, 4);
> > ActiveMQConnectionFactory connectionFactory =
> ActiveMQJMSClient.createConnectionFactoryWithoutHA(JMSFactoryType.CF,
> > new TransportConfiguration(NettyConnectorFactory.class.getName(),
> nettyParams))
> >
> > ---
> >
> > Connection factory for the last case is created like that (Groovy code):
> > ---
> > def nettyParams = ["host" : host, "port" : port];
> > def connectionFactory =
> ActiveMQJMSClient.createConnectionFactoryWithoutHA(JMSFactoryType.CF, new
> TransportConfiguration(NettyConnectorFactory.class.getName(), nettyParams));
> > def serverLocator = connectionFactory.getServerLocator()
> > serverLocator.setConnectionTTL(-1)
> > serverLocator.setReconnectAttempts(-1)
> > serverLocator.setRetryInterval(1000)
> > serverLocator.setRetryIntervalMultiplier(1)
> > ---
> >
> > BackGroundClusterNodeListenerContainer - is an extension of a
> DefaultMessageListenerContainer with overridden doReceiveAndExecute. The
> overridden method does some quick checks and returns false if they don't
> hold, otherwise delegates to the super.
> >
> > Both a client and a broker are on the same laptop.
> >
> > Any chance there is something I can do to overcome it?
> >
> > --
> > Oleg Kleshchev
--
Clebert Suconic
at 1:05 AM Domenico Francesco Bruscino
wrote:
>
> FYI, the issue related to this discussion is ARTEMIS-2850 Client deadlocks
> on failover https://issues.apache.org/jira/browse/ARTEMIS-2850
>
> Il giorno gio 23 lug 2020 alle ore 00:34 Clebert Suconic <
> clebert.suco...@gmail
similar. Currently
> I am thinking on doing message tracking (infligh messages) in our producer
> side and having notifications when the brokers go up to re-populate
> messages and avoid relying on disk or external state.
>
>
>
> Thanks & Best Regards,
>
> Luis
>
> --
Clebert Suconic
em to be stucked in a destination used for clustering when the paging
> occured on it too
> (internal.sf.my-cluster.335036cc-edc0-11ea-bae1-005056a7672b for example)
>
> I can't find what have caused this since the 2.12 so if someone with more
> knowledge of the paging and clustering can help me it would be great.
>
> Regards,
> Gaetan
>
>
--
Clebert Suconic
essage should be interpreted
> > as a digital signature that can be used to authenticate a document. No
> > warranty is given by the sender that any attachments to this email are free
> > from viruses or other defects.
> >
> The information transmitted is intended only for the person or entity to
> which it is addressed and may contain confidential and / or privileged
> material that may be governed by confidential information provisions
> contained in the agreement between GBST and your company. Any disclosure,
> copying, distribution, or other use without the express consent of the sender
> is prohibited. If you received this in error, please contact the sender and
> delete the material from any computer. All rights in the information
> transmitted, including copyright, are reserved. Nothing in this message
> should be interpreted as a digital signature that can be used to authenticate
> a document. No warranty is given by the sender that any attachments to this
> email are free from viruses or other defects.
--
Clebert Suconic
reviews and
Votes on the CR release.
--
Clebert Suconic
nt way we are
> using AMQP acceptor in broker We would like to know:
> 1. What would be maximum concurrent connection could be handled by Artemis
> broker (includes both publisher and subscriber)
> 2. Does broker connection has any dependency with acceptor (STOMP, AMQP, HTTP
> etc...)
>
> Thanks,
> Mohan
>
--
Clebert Suconic
Broker level?
> Ex : If we connect 1 persistent connection, does Artemis broker handle
> without any problem?
>
> Thanks,
> Mohan
>
> -Original Message-
> From: Clebert Suconic
> Sent: Wednesday, December 16, 2020 7:41 AM
> To: users@activemq.apache.org
>
If you expect somehting to be halting your system due to slow CPU,
antivirus, I suggest you change the policy to LOG instead of HALT:
Change
HALT
Into:
LOG
We could add a new policy that would be IGNORE for cases like this.
On Mon, Feb 15, 2021 at 8:34 AM Kamil Serwin
wrote:
>
> Hi Francesc
I'm pleased to announce the release of ActiveMQ Artemis 2.17.0
Downloads are now available at:
http://activemq.apache.org/artemis/download.html
For a complete list of updates:
https://activemq.apache.org/components/artemis/download/release-notes-2.17.0
I would like to highlight these improveme
A small correction:
This is the correct link for the download page:
https://activemq.apache.org/components/artemis/download/
On Wed, Feb 17, 2021 at 3:54 PM Clebert Suconic
wrote:
>
> I'm pleased to announce the release of ActiveMQ Artemis 2.17.0
>
> Downloads are now ava
tion:
> http://www.springframework.org/schema/beans";
>xmlns:camel="http://camel.apache.org/schema/spring";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xsi:schemaLocation="http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
>http://camel.apache.org/schema/spring
> http://camel.apache.org/schema/spring/camel-spring.xsd";>
>
>class="org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory">
>
>
>
>
>
>class="com.ibm.mq.jms.MQQueueConnectionFactory">
>
>
>
>
>
>
>
>
>class="org.springframework.jms.connection.UserCredentialsConnectionFactoryAdapter">
>
>
>
>
>
>xmlns="http://camel.apache.org/schema/spring";>
>
>uri="jms:queue://SOURCE.Q?connectionFactory=#wmqConnectionFactoryWrapper&disableReplyTo=true&concurrentConsumers=8&asyncConsumer=true&maxConcurrentConsumers=16&mapJmsMessage=false"/>
>uri="jms:queue://TARGET.Q?connectionFactory=#amqConnectionFactory&exchangePattern=InOnly&forceSendOriginalMessage=true"/>
>
>
>
>
>
> Thanks,
> Thomas
>
--
Clebert Suconic
gt; suspension, all messages consumed in other queues will be deleted.
>
> Thank
--
Clebert Suconic
destination will use memory. Artemis
is optimized as a message system... meaning message going through.. as
long as you configure paging accordingly you should be fine.
Hope that helps!
On Sat, Feb 27, 2021 at 7:10 PM Clebert Suconic
wrote:
>
> There are two things that could happen..
>
>
distributed to Consumer 1 (via Broker 2) or *particularly* Consumer 2
> (directly) would be lost (unless the journal could be recovered).
>
> Is there some straightforward configuration to avoid or reduce this
> possibility? Perhaps a 4 broker cluster could have affinity for publishers
> on 2 brokers and affinity for consumers on the other 2, somehow?
>
>
> Thanks for any advice you can offer.
>
>
> Dave Martin.
>
--
Clebert Suconic
been thinking to embed CoreMessage as AMQP. It would have still
some inefficiency crossing the protocol, but it would avoid conversion
issues.
On Thu, Mar 11, 2021 at 1:31 PM Clebert Suconic
wrote:
>
> The journal getting corrupted could happen in 2 situations:
>
> - the file system i
> It does seem like an edge case for Artemis and with mirroring now available
> I'll prioritise the DR solution. AMQP is already the protocol used
> throughout.
>
>
> Dave
>
>
> On Thu, Mar 11, 2021, 9:48 PM Clebert Suconic,
> wrote:
>
> > If yo
n google)
> > The Messagehandler may work for several minutes on each message.
> >
> > regards,
> >Arno
> >
> >
--
Clebert Suconic
t; > > session.start();
> > > ClientConsumer consumer =
> > > session.createConsumer(ACTIVE_MQ_SMTP_QUEUE);
> > > ClientMessage message = consumer.receive();
> > > result =
> > > ActiveMQBuffers.fixedBuffer(message.getBodyBufferSize());
> > > message.getBodyBuffer().readBytes(result);
> > > } finally {
> > > session.close();
> > > }
> > >
> > > return result;
> > >}
> > >
> > >
> > >public void startServer() throws Exception {
> > > this.configuration = new ConfigurationImpl();
> > > this.configuration.addAcceptorConfiguration("in-vm",
> > > ACTIVE_MQ_EMBEDDED_SERVER_URL);
> > > this.configuration.setPersistenceEnabled(true);
> > > this.configuration.setSecurityEnabled(false);
> > > this.configuration.addQueueConfiguration(new
> > > QueueConfiguration(ACTIVE_MQ_SMTP_QUEUE));
> > >
> > > this.server = new ActiveMQServerImpl(this.configuration);
> > > this.server.start();
> > >}
> > >
> >
--
Clebert Suconic
les and
> hides this detail. But if you go for direct access, you need to be
> aware of the encoding.
>
>
> On Tue, 23 Mar 2021 at 07:37, wrote:
> >
> > getDataBuffer gives same result! Already tried!
> >
> > -Ursprüngliche Nachricht-
> > Von: Clebert
t
> >>
> >> When I try to subscribe to an address, I get this error in Artemis Console:
> >> AMQ332069: Sent ERROR frame to STOMP client /0:0:0:0:0:0:0:1:49225:
> >> AMQ339016 Error creating subscription subscription/Orders But I have 0
> >> queue created so far...
> >>
> >> A few more remarks:
> >>
> >> 1. When I change the value of to "-1", I have no problem to
> >> connect with a Stomp over websocket client.
> >> 2. When I set a high value to like "500", I still have
> >> the problem 3. I have the same problem with a JMS client.
> >>
> >> Thanks for your help!
> >>
> >> Nicolas
> >>
> >
>
--
Clebert Suconic
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunne
etail would be hidden away from the
internal API.
On Tue, Mar 23, 2021 at 9:57 AM Clebert Suconic
wrote:
>
> I'm adding a test doing exactly what you did, and it's working...
>
> give me 10 minutes and I will post a link here...
>
> On Tue, Mar 23, 2021 at 9
ar 23, 2021 at 9:59 AM Clebert Suconic
wrote:
>
> You were supposed to call reset right before sending though... but I
> did not need it on my test.. I will post a link...
>
> Anyway, if you use the JMS API, the JMS layer is very thin, and I
> don't think it would affect your
already there
> when you create a new instance.
>
> -Message d'origine-
> De : Clebert Suconic
> Envoyé : mardi 23 mars 2021 14:38
> À : users@activemq.apache.org
> Objet : Re: ActiveMQ Artemis - resource limits - max-queues issue
>
> The problem I see is tha
ssage d'origine-
> De : Clebert Suconic
> Envoyé : mardi 23 mars 2021 15:11
> À : users@activemq.apache.org
> Objet : Re: ActiveMQ Artemis - resource limits - max-queues issue
>
> I did not realize you set the limit at 500.
> >> When I set a high value to like &qu
I think it makes no sense to convert it back from a native buffer into a byte
> array or stream and tunnel this throught the jvm!
>
> Is there a way to use a ByteBuf with jms?
>
> -Ursprüngliche Nachricht-
> Von: Clebert Suconic
> Gesendet: Dienstag, 23. März 2021
It is a bug, there's a NullPointerException causing the issue...
I'm sending a fix and I will provide you a snapshot to try it out.
On Tue, Mar 23, 2021 at 10:14 AM Clebert Suconic
wrote:
>
> Ok, let me run a test then.. let me work on it for 1 or 2 hours... brb
>
> O
https://issues.apache.org/jira/browse/ARTEMIS-3204
On Tue, Mar 23, 2021 at 3:07 PM Clebert Suconic
wrote:
>
> It is a bug, there's a NullPointerException causing the issue...
>
> I'm sending a fix and I will provide you a snapshot to try it out.
>
> On Tue, Mar
est your snapshot version.
>
> ________
> De : Clebert Suconic
> Envoyé : mardi 23 mars 2021 20:14
> À : users@activemq.apache.org
> Objet : Re: ActiveMQ Artemis - resource limits - max-queues issue
>
>
> https://eur01.safelinks.protection.outlook.com/?url=https
I'm finalizing the change.. it should be committed soon today or tomorrow.
On Tue, Mar 23, 2021 at 5:28 PM Clebert Suconic
wrote:
> you ok to build one from master, or should I prepare one to be downloaded?
>
> On Tue, Mar 23, 2021 at 4:42 PM CASAUX Nicolas <
> nicolas.ca
PR sent: https://github.com/apache/activemq-artemis/pull/3516
On Tue, Mar 23, 2021 at 5:29 PM Clebert Suconic
wrote:
> I'm finalizing the change.. it should be committed soon today or tomorrow.
>
> On Tue, Mar 23, 2021 at 5:28 PM Clebert Suconic
> wrote:
>
>> you o
n in the
> context of your use case to justify the disadvantages of what you're trying
> to do.
>
> Tim
>
> On Tue, Mar 23, 2021, 9:20 AM Clebert Suconic
> wrote:
>
> > Not on the API itself.
> >
> > Try the core api example I sent you... and
7;origine-
> De : Jean-Baptiste Onofre
> Envoyé : mercredi 24 mars 2021 05:50
> À : users@activemq.apache.org
> Objet : Re: ActiveMQ Artemis - resource limits - max-queues issue
>
> Hi Clebert,
>
> Oh, you were faster than me ;)
>
> Thanks !
>
> Regards
> JB
>
ed, Mar 24, 2021 at 8:11 AM Clebert Suconic
wrote:
>
> +1, and he does not need a String. He could use a BytesMessage.
>
> On Wed, Mar 24, 2021 at 8:04 AM Tim Bain wrote:
> >
> > One thing to keep in mind is that although the code may be slightly slower,
> > if it le
that.
On Wed, Mar 24, 2021 at 12:53 PM Clebert Suconic
wrote:
>
> I have two suggestions for you:
>
> - Why you don't cast BytesMessage, access the internal message on the
> BytesMessage, and add the NettyBuffer directly
>
>
> - Or Even better, why you don't you
actually outweigh the types of advantages I
> > referenced in the first paragraph. But remember that premature
> > optimization is the root of all evil, so make sure that your
> > micro-optimization of avoiding the creation of a String is really a
> > significant enough optimiz
ss the name of the file via
> a message property, right?
> How would the receiver side looks like?
>
>
> -Ursprüngliche Nachricht-
> Von: Clebert Suconic
> Gesendet: Donnerstag, 25. März 2021 16:04
> An: users@activemq.apache.org
> Betreff: Re: send message
>
&
ready and don't want bring the
> huge messages back into the jvm.
>
> -Ursprüngliche Nachricht-
> Von: Clebert Suconic
> Gesendet: Donnerstag, 25. März 2021 20:31
> An: users@activemq.apache.org
> Betreff: Re: send message
>
> I assumed the data was already o
result = message.getDataBuffer().readString();
> message.acknowledge();
> session.commit();
> } finally {
> session.close();
> }
--
Clebert Suconic
from your ByteBuffer and
pass it in.
On Fri, Mar 26, 2021 at 8:48 AM wrote:
>
> A example would be great!
>
> -Ursprüngliche Nachricht-----
> Von: Clebert Suconic
> Gesendet: Freitag, 26. März 2021 13:26
> An: users@activemq.apache.org
> Betreff: Re: send message
&
library.
On Fri, Mar 26, 2021 at 10:43 AM Clebert Suconic
wrote:
>
> look at message.setInputStream as you are using the Core API.
>
> if you were using the JMS API there's a property that kind of wraps it
> into the CoreMessage through the JMS Message.
>
> Since you are u
leString(ACTIVE_MQ_SMTP_QUEUE));
> if (!queueQuery.isExists())
> session.createQueue(new
> QueueConfiguration(ACTIVE_MQ_SMTP_QUEUE).setDurable(true));
> } finally {
> session.close();
> }
>
>
>
ould be particularly careful on allowing clients to
create stuff).. .I would keep the broker under control for the OPs
guy.
On Tue, Mar 30, 2021 at 3:19 PM Clebert Suconic
wrote:
>
> if you create se JMS Session with true, then you should pass in
> Session.SESSION_TRANSACTED. (I guess you
iry
> to keep a clean system.
> This specific case seems to avoid that...
>
> My question:
> Is there any trick (setting) to get the paged-out messages physically
> expired (i.e. removed) without needing client requests?
>
> Thx!
> Erwin
>
--
Clebert Suconic
Perhaps we could optimize such use case.. issue a dapage an an
immediate scan if all references in memory are expired.
Do you want to create a JIRA for that?
On Tue, Mar 30, 2021 at 6:18 PM Clebert Suconic
wrote:
>
> All the messages had expiry ?
>
> My expectation was that the
Just a heads up.
We will still need to expire messages that are in memory. But what I plan
to do is to optimize things a bit to it keeps depagjng and scanning as it’s
empty.
On Tue, Mar 30, 2021 at 6:30 PM Clebert Suconic
wrote:
> Perhaps we could optimize such use case.. issue a dapage
=17312236&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17312236
>
> On Wed, 31 Mar 2021 at 00:52, Clebert Suconic
> wrote:
> >
> > Just a heads up.
> >
> >
> > We will still need to expire messages that are in memory. But what
umer receive the message
>
>
>
>
>
>
>
> thanks
--
Clebert Suconic
ding en/of
> verstrekking van (de inhoud van) deze e-mail (en eventuele bijlagen) aan
> derden is uitdrukkelijk niet toegestaan. Indien u niet de bedoelde
> geadresseerde bent, wordt u vriendelijk verzocht degene die de e-mail verzond
> hiervan direct op de hoogte te brengen en de e-mail (en eventuele bijlagen)
> te vernietigen.
>
> Informatie vennootschap<http://www.ns.nl/emaildisclaimer>
--
Clebert Suconic
on the Artemis broker.
>
> Also, the ALL command is created exactly the same and is persistent over
> reconnects and does relay all pending messages.
>
>
> Regards,
>
> Sebastiaan la Fleur
>
> -Original Message-
> From: Clebert Suconic
> Sent: zater
its usage.
This is a significant release, with tons of bug fixes, enhancements
and other features.
Thank you to all the contributions to this release
--
Clebert Suconic
communication together with any attachments
> is intended only for the person or entity to which it is addressed and may
> contain confidential and/or privileged material. If you are not the
> intended recipient of this e-mail communication, please notify us
> immediately. Any views expressed in this e-mail communication are those of
> the individual sender, unless otherwise specifically stated. Charles River
> Development does not represent, warrant or guarantee that the integrity of
> this communication has been maintained or that the communication is free of
> errors, virus or interference.
>
--
Clebert Suconic
Do you have any other process opening the journal file such as backups.
Etc.?
Be careful with that especially on windows.
On Wed, Sep 8, 2021 at 8:36 PM Clebert Suconic
wrote:
>
> Although the exit was for a critical IO error. Some IO error.
>
>
> On Thu, Sep 2, 2021 at 7:5
It seems an IO issue to me. the load you're generating is taking more
time than the configured time on CriticalAnalyzer would allow you to
do.
you should either get a faster device (If I'm right on this), or allow
more time, or diminish your load. (getting more nodes perhaps):
The thread I see
The critical analyzer is used to protected against dead locks.
if you have a box that's not acting as fast for any other reason, I
suggest you turn it off. (Use Log instead of HALT on the Critical
Analyzer options).
On Wed, Oct 27, 2021 at 11:09 AM Eric Kaplan wrote:
>
> I am seeing this as well
around exists. Maybe we do not use Artemis in the
> good way and we could change something in our configuration or way to use
> it to avoid this issue.
> 3. Currently, I don't know where to look to go ahead so any help
> would be useful.
> 4.
> Thanks !
> Elodie
>
--
Clebert Suconic
to JDK 11 here ...
Here is a space for your complaints if you can't move, and I space
for us to convince you to move out of JDK 8 :)
I had a few conversations with many other teams and I don't foresee a
reason to.. so, let me know if I'm wrong here.
--
Clebert Suconic
deployment?
>
>
> Regards,
>
> Dave
>
>
> On Fri, 29 Oct 2021 at 23:27, Clebert Suconic
> wrote:
>
> > The critical analyzer is used to protected against dead locks.
> >
> > if you have a box that's not acting as fast for any other reason, I
&g
I'm pleased to announce the release of ActiveMQ Artemis .
Downloads are now available at:
https://activemq.apache.org/components/artemis/download/
For a complete list of updates:
https://activemq.apache.org/components/artemis/download/release-notes-2.20.0
There are a few bug fixes as usual as
I'm pleased to announce the release of ActiveMQ Artemis 2.20.0
My apologies for the copy & paste error... it's been a long year and
I'm ready for the holidays break... thanks for understanding it :)
On Tue, Dec 21, 2021 at 5:31 PM Clebert Suconic
wrote:
>
> I'm p
rt - 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:
> &g
gt; Viktor Kolomeyko
>
> On 2021/12/15 17:27:26 Clebert Suconic wrote:
> > I just sent ActiveMQ Artemis 2.20.0 to be reviewed under Vote. and I
> > would like to clarify that JDK 1.8 will not be supported any more from
> > Artemis 2.20.0
> >
> >
> > At this
> Indeed, own Artemis releases will always be an option, but there are few
> drawbacks I can see with this approach:
> - It will be an unofficial release and clients who receive software with this
> unofficial library will be naturally cautious about it;
> - Since it will be a private release it
s remain in several Eclipse projects.
> Not a big problem as the command-line use of "mvn clean install" still works.
>
> So I was wondering whether using an IDE is common practice for the Artemis
> development. And if so, is there any preference between
> Eclipse/IntelliJ/NetBeans/etc.?
>
> thx,
> e.
--
Clebert Suconic
gt;
> > > > > > > > > name="artemis">tcp://internal-cluster-dns-1:61616?tcpSendBufferSiz
> > > > > e=
> > > > > 10
> > > > > 48576;tcpReceiveBufferSize=1048576;amqpMinLargeMessageSize=102400;
> > > > > pr
> > > > > ot
> > > > > ocols=CORE,AMQP,STOMP,HORNETQ,MQTT,OPENWIRE;useEpoll=true;amqpCred
> > > > > it
> > > > > s=
> > > > > 10
> > > > >
> > > > > 00;amqpLowCredits=300;amqpDuplicateDetection=true;supportAdvisory=
> > > > > fa ls e;suppressInternalManagementObjects=false
> > > > >
> > > > > We don’t have issues with internal consumers/producers, however
> > > > > when we try to connect external consumers (via external IP), they
> > > > > are trying to connect via internal DNS which is probably set in
> > > > > the cluster topology packet.
> > > > >
> > > > > This is probably expected and by design, but my question is how do
> > > > > we correctly handle such case? We obviously do not want internal
> > > > > clients to be served via external IP because external traffic is
> > > > > expensive in the cloud and the performance would decrease
> > > > > dramatically. Even with static discovery we would like to have a
> > > > > possibility to expand our cluster in the future, i.e. use the
> > > > > topology so that clients are configured automatically.
> > > > >
> > > > > Do we need to have a split-DNS server so that external and
> > > > > internal clients will see different IP addresses? Or maybe it is
> > > > > possible to have the same node serving different acceptors on
> > > > > different ports and different DNS names?
> > > > >
> > > > > Any pointers are much appreciated.
> > > > >
> > > > > --
> > > > >Best Regards,
> > > > >
> > > > > Vilius Šumskas
> > > > > Advantes technologies
> > > > > IT manager
> > > > > +370 614 75713
> > > > >
> > > > >
--
Clebert Suconic
ease with
> some fixes would be great:
> - https://issues.apache.org/jira/browse/ARTEMIS-3620
> - https://issues.apache.org/jira/browse/ARTEMIS-3607
> - https://issues.apache.org/jira/browse/ARTEMIS-3541
> Maybe I could help with this maintenance release.
> Cheers,
--
Clebert Suconic
please do not print, copy, retransmit, disseminate or
> otherwise use the information. Please indicate to the sender that you have
> received this communication in error, and delete the copy you received.
>
> Maxar reserves the right to monitor any electronic communication sent or
> received by its employees, agents or representatives.
--
Clebert Suconic
mmend upgrading your
environment and JDK so you can have the benefit of future releases and
enhancements.
Many thanks for all the contributions to this release, including the
evaluation of the Candidate release during the voting process.
--
Clebert Suconic
0740, widx: 271572, cap: 271572)
> > > at
> > >
> > >
> >
> io.netty.buffer.AbstractByteBuf.checkReadableBytes0(AbstractByteBuf.java:1442)
> > > at
> > >
> > >
> >
> io.netty.buffer.AbstractByteBuf.checkReadableBytes(AbstractByteBuf.java:1428)
> > > at io.netty.buffer.AbstractByteBuf.readBytes(AbstractByteBuf.java:937)
> > > at
> > >
> > >
> >
> org.apache.activemq.artemis.core.client.impl.ClientMessageImpl$DecodingContext.readInto(ClientMessageImpl.java:407)
> > > at
> > >
> > >
> >
> org.apache.activemq.artemis.core.message.impl.CoreMessage.getLargeMessageBuffer(CoreMessage.java:264)
> > > at
> > >
> > >
> >
> org.apache.activemq.artemis.core.message.impl.CoreMessage.getDataBuffer(CoreMessage.java:241)
> > >
> >
>
--
Clebert Suconic
e to make it
> faster. I thought I still had that code laying around somewhere, but I
> can't find it at the moment.
>
>
> Justin
>
> On Sun, Feb 20, 2022 at 9:03 AM Clebert Suconic >
> wrote:
>
> > I have seen (and fixed) cases where the large message file is
am wrote:
>
> No. The test was super-simple. Just send one large message and then consume
> it.
>
>
> Justin
>
> On Mon, Feb 21, 2022 at 12:57 PM Clebert Suconic
> wrote:
>
> > It did not involved paging ?
> >
> > On Mon, Feb 21, 2022 at 11:07 AM Justin Bertram
Found the reason:
You should use getBoddyBuffer instead.
getbodybuffer() will perform a call to checkBuffer() before returning
you the large message.
This should fix your test / problem.
On Tue, Feb 22, 2022 at 1:03 PM Clebert Suconic
wrote:
>
> this is something done on the co
or use the JMS API instead.. that's another possibility. but if you
want to use the core API, use getbodyBuffer instead.
On Tue, Feb 22, 2022 at 1:17 PM Clebert Suconic
wrote:
>
> Found the reason:
>
>
> You should use getBoddyBuffer instead.
>
>
> getbodybu
; at java.lang.ref.Reference.tryHandlePending(Reference.java:191)
> at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:153)
>
>
>
> ===
> End Thread dump
>
> Is this bugs in Artemis share file configuration?
>
> Regards,
> Rahman
>
--
Clebert Suconic
l the contributors to this release.
--
Clebert Suconic
[artemis-commons-2.20.0.jar:]
> >
> > Just wondering if these errors cause any lasting damage, and if it means
> > that something is not tuned correctly, or is a normal part of recovering
> > from such a severe leak (we had hundreds of thousands of stale consumers on
> > that queue.)
> >
> > Stephen E Baker
> >
> >
> >
--
Clebert Suconic
l]
> at
> io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
> [netty-common-4.1.72.Final.jar:4.1.72.Final]
> at
> org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
> [artemis-commons-2.20.0.jar:]
>
> Stephen E. Baker
>
>
--
Clebert Suconic
I think it was ignorable, but I'm dealing with it:
https://github.com/apache/activemq-artemis/pull/4049/commits/952bfde37d79701a02f6626c6345447d5fcd3e20
It should be part of the release this week
On Mon, Apr 25, 2022 at 11:17 AM Clebert Suconic
wrote:
>
> it means the message wa
'm pleased to announce the release of ActiveMQ Artemis .
Downloads are now available at:
https://activemq.apache.org/components/artemis/download/
For a complete list of updates:
https://activemq.apache.org/components/artemis/download/release-notes-2.22.0
This release contains many fixes and i
> stephen.ba...@rmssoftwareinc.com> wrote:
> >
> > > Understood thank you. We (the company I work for) are definitely getting
> > > more value out of the product than we are contributing, so that point is
> > > taken. The JDBC replication route was recommended by a consultant from
> > > Savoir as more established/reliable than mirroring when delivery
> > guarantees
> > > are important, which is why we are pursuing it.
> > >
> > >
> > [EXTERNAL]: This email originated from outside of Rave Mobile Safety. Do
> > not click links or open attachments unless you recognize the sender and
> > know the content is safe.
> >
--
Clebert Suconic
nnection for each message it publishes. I don't
> > have
> > > >> access to the client system implementation, but is there anything I
> > can
> > > do
> > > >> on the Artemis end to make it more efficient? Latency with this system
> > > is
> > > >> becoming an issue. Also every 30 minutes or so there is a spike in CPU
> > > >> usage (~50%) which I assume is garbage collection. During that spike
> > > >> message publishing slows down a lot.
> > > >>
> > > >> Thanks,
> > > >>
> > > >> Ben
> > > >>
> > > >
> > >
> >
--
Clebert Suconic
Can you use jdk 11?
On Mon, Jun 6, 2022 at 8:32 PM Clebert Suconic
wrote:
> You are likely hitting the bug I fixed at:
>
> https://github.com/apache/activemq-artemis/pull/4098
>
> I introduced a Thread Local Leakage. I thought by setting
> threadLocal.set(null) I would be cle
e whatever I want after I prove it out in lower environments.
>
> Thanks,
>
> Ben
>
> On Mon, Jun 6, 2022 at 10:06 PM Clebert Suconic
> wrote:
>
> > Can you use jdk 11?
> >
> > On Mon, Jun 6, 2022 at 8:32 PM Clebert Suconic
> > wrote:
> >
> >
ache.org/content/repositories/snapshots/org/apache/activemq/apache-artemis/2.23.0-SNAPSHOT/
>
> On Tue, Jun 7, 2022 at 11:34 AM Clebert Suconic
> wrote:
>
> > I am preparing artemis 2.23.0 at the moment...
> >
> > The way a release works in apache, you send it for vote
1 - 100 of 697 matches
Mail list logo
