(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 configure ActiveMQ
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=false=TLSv1.2=TLS_RSA_WITH_AES_256_CBC_SHA256
Or do the socket options also need an additional "nested." prefix?
I can unfortunately never
cp-transport-reference
<https://activemq.apache.org/tcp-transport-reference>>
>
> Sounds like you want ‘client-side'>
>
> connectionTimeout>
> soTimeout>
> soWriteTimeout>
>
> Let us know how it goes!>
>
> -Matt>
>
> > On Sep 23,
I can't seem to find any documentation on the configurable "connect response
timeout" of an ActiveMQConnection.
Believe it's used only in method ensureConnectionInfoSent() but still would
like to understand it and also is the default value 0 reasonable or would it
not make sense to configure
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
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
transaction context.
This always worked fine but no longer does, instead one can see a exception,
but only when debug log is turned on
Added a comment toAMQ-7298 on how to reproduce the issue:
https://issues.apache.org/jira/browse/AMQ-7298?focusedCommentId=17292431=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-7298 which
, 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
Let me try it on 5.16.1 (I didn’t see any issue but I might have missed it).
Regards
JB
Le 27 janv. 2021 à 18:41, Martin Lichtin a écrit :
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
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
wrote:
Would a firewall rule be an option here? It seems like that would be the
best tool to control access to the broker based on IP address. Or is your
use-case more complex than that?
Justin
On Sun, Aug 30, 2020 at 2:19 PM Martin Lichtin
wrote:
Hi
Looking at how to best implement IP-address
ActiveMQ version are you talking ?
I remember to have fixed closing of connection in 5.15.13 AFAIR.
Can you please create two Jira (one for the connect hook, one for connection
leaking) ? I will take a look.
Regards
JB
Le 30 août 2020 à 21:19, Martin Lichtin a écrit :
Hi
Looking at how to best
Hi
Looking at how to best implement IP-address based access control via a Plugin.
I've an implementation based on "addConnection", but this method is called way
too late in the connection setup.
Ideally there should be a hook available in TcpConnection.connect() method to
reject rogue
Hi All
Configuring the broker SSL context with
seems quite rigid and the password a security issue.
Is there a better way to do this? I couldn't really find a solution looking at
the XSD.
For example, using a bean to offer the SSLContext
and then referring to it
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 suppose
mprovement.
Regards
JB
On 03/02/2020 20:50, Martin Lichtin wrote:
Hi JB, I have to disagree with this view.
The JMS delivery mode should be honoured by ActiveMQ, it should not
'improve' or change the delivery mode in any way. There's no reason such
a message should survive a broker re-start, i
2020 17:35, Martin Lichtin wrote:
Can somone help me understand why a non-persistent message is
"converted" into a persistent message on entering DLQ?
It happens in RegionBroker, around line 733:
if (!message.isPersistent()) {
m
Can somone help me understand why a non-persistent message is "converted" into
a persistent message on entering DLQ?
It happens in RegionBroker, around line 733:
if (!message.isPersistent()) {
message.setPersistent(true);
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
/java-service-wrapper.html. Is that how you're
using ActiveMQ? Or are you running the broker directly from the executable
in the bin directory, which wouldn't use the wrapper (and so wouldn't
restart the process)?
Tim
On Thu, Feb 28, 2019, 1:57 PM Martin Lichtin
wrote:
Hi
Can you help me
Hi
Can you help me understand this situation?
I've ActiveMQ configured with a lease lock on a DB. Spontaneously it decided it
can no longer keep the lock, and starts shutting down:
2019-02-27T16:47:45,491 | INFO | Starting Thread | BrokerService |
he.activemq.broker.BrokerService
blem.
Tim
On Apr 29, 2017 4:24 AM, "Martin Lichtin" <lich...@yahoo.com.invalid> wrote:
I'm running into a situation with the Failover Transport not respecting
the timeout that's been set.
The symptom is endless messages of this kind:
2017-04-29 09:48:26,128 | TRACE | .engine.cfgengine.
I'm running into a situation with the Failover Transport not respecting the
timeout that's been set.
The symptom is endless messages of this kind:
2017-04-29 09:48:26,128 | TRACE | .engine.cfgengine.in]-11 | FailoverTransport
| sport.failover.FailoverTransport 615 | 81 -
Wanted to ask some specifics about the "Message Groups" feature.
* is the feature incurring an overhead to the broker processing?
* would a large queue depth cause any issues?
* there is a note about 'grouping in memory', does this mean messsages are
somehow re-ordered?
* would an ever
When running multiple brokers in master-slave(s) mode (KahaDB file), they
behave as described:
- The first broker grabs the exclusive lock on the file and becomes the master
broker.
- If that broker dies and releases the lock then another broker takes over.
- The slave brokers sit in a loop
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, or how
to work
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
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
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.)
request!
On Apr 9, 2016 11:51 AM, "Martin Lichtin" <lich...@yahoo.com.invalid> 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() iterate
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 (as it is a prioritized queue) uses
I see
org.osgi.framework.BundleException: Unresolved constraint in bundle activemq-karaf [124]:
Unable to resolve 124.0: missing requirement [124.0] osgi.wiring.package;
(&(osgi.wiring.package=org.apache.felix.gogo.commands)(version>=0.16.0)(!(version>=1.0.0)))
when trying to upgrade ActiveMQ
an the sum of the two limits, and
allow nothing else to write to it.) Prevention is usually better than
treatment.
On Oct 14, 2015 4:36 AM, "Martin Lichtin" <lich...@yahoo.com.invalid> wrote:
Wanted to ask if it is advisable to configure an IOExceptionHandler, such as
this.
>
> Tim
> On Nov 12, 2015 11:51 AM, "Martin Lichtin" <lich...@yahoo.com.invalid>
> wrote:
>
>> I believe that branch is for transacted sessions (which I'm also using).
>> If the test would use a transacted session, I'd say it no longer sees the
(md, false);
}
}
should also set md.setRollbackCause(e) in the else clause?
- Martin
From: Martin Lichtin <lich...@yahoo.com>
To: Gary Tully <gary.tu...@gmail.com>; ActiveMQ Users
<users@activemq.apache.org>
// next message.
afterMessageIsConsumed(md, false);
}
}
should also set md.setRollbackCause(e) in the else clause?
- Martin
------
*From:* Martin Lichtin <lich...@yahoo.com>
*To:* Gary Tully <gary.t
ion threw.
- Martin
>
> From: Gary Tully <gary.tu...@gmail.com>
> To: Martin Lichtin <lich...@yahoo.com>; ActiveMQ Users
> <users@activemq.apache.org>
> Sent: Wednesday, November 4, 2015 11:52 AM
> Subject: Re: What happ
I see the JMSRedelivered flag goes back to 'false' when # of redeliveries is
exceeded
and ActiveMQ server moving the message into the DLQ.
Is this done on purpose? I'd rather expect the flag stay 'true', as this state
should be preserved.
- Martin
Can you help me understand what is stored in the "scheduler" directory?
I see about 14G of db-xxx.log files sitting there.
All queues are empty and also the kahadb directory contains just one db-nnn.log
file.
schedulerSupport is enabled only due to use of the redelivery plugin.
I'm pretty
Your problem sounds a bit more complex, but just wanted to mentioned that one
can set usePrefetchExtension=”false”.
From the docs:
The default behavior of a broker is to use delivery acknowledgements to
determine the state of a consumer's prefetch buffer. For example, if a
consumer's prefetch
About JMSActiveMQBrokerOutTime, as redelivery is typically done locally by the
client/consumer, it will not change.
I imagine it should get updated in case of a server-side redelivery though.
On 19.10.2015 06:18, Tim Bain wrote:
I'm pretty sure the JMS spec describes how JMSTimestamp is
ery plugin very very rarely comes into action, so I still don't
understand why there's all this data being stored.
On 22.10.2015 15:47, Timothy Bish wrote:
On 10/22/2015 04:46 AM, Martin Lichtin wrote:
Can you help me understand what is stored in the "scheduler" directory?
I see abo
Wanted to ask if it is advisable to configure an IOExceptionHandler, such as
false
true
I could not find much information about this feature, besides
http://activemq.apache.org/configurable-ioexception-handling.html
Is this a tried and trusted approach to
I've seen this behaviour as well and did not find a way around it besides
limiting the number of _startup_ reconnect attempts.
Append something like "?startupMaxReconnectAttempts=5" to the Url.
On 29.09.2015 15:31, Anna Maier wrote:
Hi,
I am using Camel to connect to ActiveMQ and it fails
Can someone explain (or understand) why KahaDb implements only three levels of
priority?I wish it'd implement a few more, ideally the 10 levels JMS
specifies.Also, is there an alternative backing store that implements all
levels?
Has anyone tried upgrading to 5.12.0 under OSGi (e.g. Karaf) already?
It fails for me with
org.osgi.service.blueprint.container.ComponentDefinitionException: Error setting
property: PropertyDescriptor name: maxConnections, getter: class
Hi
What tool(s) can I use todeal with prepared XA transactions?
Given an XID
a) show or provide a reference to the associated JMS message
b) manually commit/rollback the transaction for maintenance purposes
I actually just found https://github.com/chirino/activemq-xa-cli which seems to
do
segments, so
the entire last segment would need to be out, but I would imagine
you could adjust your naming conventions to match that, right?
On Thu, Apr 9, 2015 at 4:21 AM, Martin Lichtin
lich...@yahoo.com.invalid wrote:
I read http://activemq.apache.org/wildcards.html but am still puzzled about
how
I read http://activemq.apache.org/wildcards.html but am still puzzled about
how to write a pattern that matches queue names with a particular suffix.
For example, for queue names such as A.B.Cout and D.E.Fout will
redeliveryPolicy queue=*out
be enough to match the queues? Or do I need
Wanted to ask if there's a way to disable MBeans creation for
sessions/producers/consumers in ActiveMQ?
In certain setups (such as when using JTA/XA), not everything can be pooled,
and new producers/sessions are frequently created. This causes a constant
stream of new MBeans as well.
James
Ok, makes sense, thanks.
https://issues.apache.org/jira/browse/AMQ-5656
- Original Message -
From: Gary Tully gary.tu...@gmail.com
To: users@activemq.apache.org users@activemq.apache.org; Martin Lichtin
lich...@yahoo.com
Cc:
Sent: Tuesday, March 10, 2015 2:42 PM
Subject: Re
The situation I have is a Camel route with a timer: endpoint sending a JMS
message every few seconds.
After stopping/starting the broker, the client does not seem to be able to
recover and forever spits out
2014-08-14 15:53:55,429 | WARN | #39 - timer://brokerInfo | TimerConsumer
Hi all, while debugging an (unexpected) redelivered message, I come across the
following log
2014-06-25 13:37:53,608 | DEBUG | ActiveMQ NIO Worker 16 | ActiveMQConnection
| he.activemq.ActiveMQConnection$3 1887 | 93 -
org.apache.activemq.activemq-osgi - 5.10.0 |
55 matches
Mail list logo
