Hi,
Yes I was trying the same. There is some problem.
You figured out problem ?
Thanks,
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Retained-Flag-in-MQTT-tp4668333p4671630.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hello.
We are running activemq 5.8, on centos 6.X with OpenJDK 64-Bit Server VM
(build 20.0-b12, mixed mode).
I have a situation where I think I have turned off flow control but I am
seeing seeing behavior that makes me think flow control is still on.
The activemq broker configurations are here
h
Some additional info.
I turned on some additional logging and it looks like in the case where it
is broken i get the output:
restore consumer: ID:client1-3075-13795...:1:47
But in the working scenario I see:
restore consumer: ID:client1-3075-13795...:1:47 in pull mode pending
recovery, overriding
Hi,
Of all the defined TCP transport options:
minimumWireFormatVersion
trace
daemon
useLocalHost
socketBufferSize
keepAlive
soTimeout
connectionTimeout
wireFormat
closeAsync
soLinger
maximumConnections
diffServ
typeOfService
tcpNoDelay
- which can be used ONLY on a transport connector definition
Hi,
is it possible to secure all queues start with a "t" with the Simple
Authentication Plug-In?
Only one special defined user (authenticationUser) needs to get access to
all queues with a name like "test1", "test2", "testX".
I tried something like
" ...
http://activemq.2283324.n4.nabble.com/Sec
Currently the two brokers are not connected. They are completely separate.
The destinations are all created on demand when the clients subscribe.
Here is what my client URI looks like.
failover:(ssl://server1:61610?wireFormat.maxInactivityDuration=3000&keepAlive=true,ssl://server1:61610?wireForm
Here are my policies:
