Good finding - I commented on the Jira ticket.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-SSL-implementation-tp4706285p4706423.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Note, by the way, that asyncSend=false only affects the send from the
producer to the broker - not from the broker to the consumer.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Reject-an-incoming-message-from-Camel-broker-component-tp4706168p4706422.html
Sent from the
There is no way to notify a message producer if consumption of the message
fails through JMS semantics. That defeats the major aspect of JMS -
asynchronous processing and loose coupling of producers and consumers.
In order to inform the producer of success or failure, one of the following
would d
It should already work. In Apache Karaf you can install artemis using
these commands:
feature:repo-add artemis 1.2.0
feature:install artemis-core artemis-amqp artemis-hornetq artemis-mqtt
artemis-stomp
This will install all the transports.
You can then configure artemis using etc/artemis.xml
The default Message Group Map implementation was recently changed to use an
LRU Cache of message groups.
Here's the issue with message groups - the broker does not know the set of
message group IDs ahead of time and must allow for any number of group IDs
to be used. If the total set of possible m
The default limit is indeed 1024 message groups per destination.
However you increase that by adding the following configuration to your
broker's activemq.xml:
In addition to cachedMessageGroupMessageFactory (default) there's also the
Hello,
We are investigating using message groups as a technique to insure "in
order" processing of various IDs. In the past (2010), I have found posts
mentioning that more than 1024 message groups will trigger an overflow for
the default implementations.
http://scott.cranton.com/2010/09/acti
also, notice this is version specific:
https://github.com/apache/activemq-artemis/blob/1.2.0/docs/user-manual/en/karaf.md
(We will actually need to verify how to parameterize current version
on gitbooks ).. (Or maybe we just make the text generic such as:
feature:repo-add mvn:org.apache.ac
this got written, but I believe it's missing a link on the main .md..
https://github.com/apache/activemq-artemis/blob/master/docs/user-manual/en/karaf.md
On Mon, Jan 25, 2016 at 4:27 PM, Justin Bertram wrote:
> I'm not familiar with all the details, but my understanding is that there's
> ba
I'm not familiar with all the details, but my understanding is that there's
basic OSGI support available. See
https://issues.apache.org/jira/browse/ARTEMIS-93 for more details on that.
Perhaps Christian could elaborate more on what specifically is supported.
Justin
- Original Message --
Hi,
Just wanted to know of any plans Artemis has to release support for OSGI? Is
anyone already using it within OSGI containers ?
Regards,
-Yogesh
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Artemis-Any-plans-for-Artemis-Support-for-OSGI-tp4706368.html
Sent from th
Managed to get around this issue, so now ActiveMQ starts ok when Java is
enabled for FIPS mode using NSS. See ActiveMQ JIRA case...
https://issues.apache.org/jira/browse/AMQ-5100
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-SSL-implementation-tp4706285p47064
The documentation is pretty clear (IMO) about the purpose of the "address"
property of the cluster connection. There's nothing "magic" about it. In
short, "Each cluster connection only applies to addresses that match the
specified address field. An address is matched on the cluster connection
Your help is appreciated, and effective.
I have misunderstood the configuration elements. I was not clear that the
acceptor and the connector describe the same end-point. After fixing that I
saw a few logging messages about bridges being built.
The configuration help that you pointed me to s
No problem, I'm hoping to release 5.13.1 pretty soon (maybe this week) so
keep an eye out for it.
On Thu, Jan 21, 2016 at 10:45 PM, yogu13 wrote:
> I see its done... Thanks Chris!
>
> Regards,
> -Yogesh
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-S
I imagine this is just a configuration issue somewhere. We ship lots of
examples which use clustering (although not embedded), and the test-suite is
full of embedded clustering tests. As far as I know all these are working
properly.
When you say the NettyAcceptor and NettyConnector use a "ran
So I had a go at trying to do this.
I have followed the online guides on how to get NSS working with Java SE
(running on windows), and have managed to get Java to work ok with NSS. I
have configured the sslContext to point to the NSS DB, and set the store
types as PKCS11.
However when starting u
Hello group members.
I'm having problems with clustering/federating an application's Artemis
embedded server.
The application is a .WAR with Springframework 4 and Embedded Artemis
1.1.0 (from Spring).
Multiple instances of the application are expected to be deployed in
multiple spots. The
18 matches
Mail list logo