On 04/11/2017 12:42 PM, Robbie Gemmell wrote:
For the most part topic subscriptions only ever had a single
subscriber asociated with them, until at some point someone thought it
would be useful to support more. Some systems can do that, others
cant, others still have specific mechanisms to
For the most part topic subscriptions only ever had a single
subscriber asociated with them, until at some point someone thought it
would be useful to support more. Some systems can do that, others
cant, others still have specific mechanisms to achieve the same
effect.
This is all completely
If I understand this correctly, the limitation with regard to only a single
consumer on one topic is in order to maintain compliance with the JMS
specification. ActiveMQ's Virtual Destinations give a workaround for this
where a producer will publish to a topic as normal whilst allowing a
This vote thread is cancelled pending a new release candidate.
-Ted
On 04/11/2017 09:51 AM, Ted Ross wrote:
-1
I hate to do this to my own vote, but Chuck Rolke has found an issue
that is a blocker:
https://issues.apache.org/jira/browse/DISPATCH-742
Please stand by for RC3 with a fix
Can you send a "[CANCELLED] [VOTE] Release Qpid Dispatch Router 0.8.0
(RC2) " mail, just for the record.
Robbie
On 11 April 2017 at 14:51, Ted Ross wrote:
> -1
>
> I hate to do this to my own vote, but Chuck Rolke has found an issue that is
> a blocker:
>
>
I'm afraid I don't even know really know what NiFi is, but essentially
it should be pretty obvious from your classpath what is happening, and
it may or may not involve NiFi directly. In the past, SLF4J would
complain if there was more than one logging binding available, so its
possible there is
-1
I hate to do this to my own vote, but Chuck Rolke has found an issue
that is a blocker:
https://issues.apache.org/jira/browse/DISPATCH-742
Please stand by for RC3 with a fix for this issue.
-Ted
On 04/07/2017 10:34 AM, Ted Ross wrote:
Please cast your vote on this thread for
OK thanks, will ask the NiFi guys
--
View this message in context:
http://qpid.2158936.n2.nabble.com/qpid-jms-client-writing-passwords-to-the-log-tp7662189p7662193.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
With ActiveMQ 5 I think your only option would be Virtual Topics,
http://activemq.apache.org/virtual-destinations.html
On 11 April 2017 at 13:17, Jeremy Gooch wrote:
> It's...
> - ActiveMQ 5.14- Python 3 (running in Docker)- Latest version of Qpid Proton
>
As described at
http://qpid.apache.org/releases/qpid-jms-0.21.0/docs/index.html#logging,
the client uses SLF4J and requires the application provide a binding
for it and matching logging implementation then configure it according
to its needs. It logs nothing by default unless loaded alongside
When connecting to ActiveMQ via JMS I am using failover and also specifingy
the SSL parameters in the connection URI - as specified @
https://qpid.apache.org/releases/qpid-jms-0.21.0/docs/index.html
Questions:
* Is it possible to disable the logging of the JMS connection URI?
* If not, is it
It's...
- ActiveMQ 5.14- Python 3 (running in Docker)- Latest version of Qpid Proton
(installed via pip3)
J.
Jeremy Gooch http://goochgooch.co.uk
From: Robbie Gemmell
To: "users@qpid.apache.org"
Sent: Monday, 10 April 2017, 15:55
12 matches
Mail list logo