Re: Virtual topics, custom prefix limitations

[Tim Bain]

I could have sworn I had read something on the wiki that indicated this
used to work (and that failing to exclude the queues would result in
duplicate messages), but I can't find it so maybe I'm thinking of something
else.  Thanks for humoring my faulty memory.

So what happened when you included the topics in the
staticallyIncludedDestinations element?

On Oct 15, 2016 11:18 PM, "Devlin"  wrote:

We may need to support standard subscribers to the virtual topic, but it's
not a drop-dead requirement.
Having said that, we verified the broker network is working for standard
queues/topics using the above configuration, but not virtual topics, even
after removing . VT's are only working when producers
AND consumers are all connected to the same broker.



--
View this message in context: http://activemq.2283324.n4.
nabble.com/Virtual-topics-custom-prefix-limitations-tp4717481p4717975.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: sudo update-rc.d activemq multiuser throws error

[Martin Herrman]

Hi Maneesh,


In that case 'sudo update-rc.d activemq defaults' should work.


Linux systems used to be shipped with the sysvinit system 
(https://wiki.archlinux.org/index.php/SysVinit), which is currently being 
replaced by systemd (https://wiki.archlinux.org/index.php/Systemd). However, 
Ubuntu has been using their own upstart (https://en.wikipedia.org/wiki/Upstart) 
in between Upstart.


Regards,


Martin




Van: maneeshmp 
Verzonden: vrijdag 14 oktober 2016 18:38:22
Aan: users@activemq.apache.org
Onderwerp: Re: sudo update-rc.d activemq multiuser throws error

I am using ubuntu

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.1 LTS"

Thanks,
Maneesh



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/sudo-update-rc-d-activemq-multiuser-throws-error-tp4717903p4717930.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Met vriendelijke groet/Kind regards,

Martin Herrman
Manager DevOps

[YMOR]

Ptolemaeuslaan 70
3528 BP Utrecht
Mobiel: +31 6 10761936
Kantoor:+31(0)30 6021149

Email:  mherr...@ymor.nl

[ITOA]
Van reactief naar preventief IT-beheer?
Download de whitepaper:
'Van achteruitkijkspiegel naar glazen bol met IT Operations 
Analytics'


This e-mail message and its attachments are subject to the disclaimer published 
on our 
website

Re: KAHADB clean up old log files

[Shobhana]

Sorry about adding to somebody else's thread I am adding here since I see
same issue in our production server.

We use 5.14.0 version and I have already enabled DLQ to discard all expired
messages and also set expiry of 1 day to all messages (MQTT) and offline
durable consumers using the following configurations :

a) I enabled following plug-in to set expiry of 1 day for every message (we
use only MQTT messages) : 

  



b) I enabled DLQ to drop all expired messages for all topics and queues : 

  




c) I enabled offline durable subscribers to timeout after 1 day : 
offlineDurableSubscriberTimeout="8640"
offlineDurableSubscriberTaskSchedule="360" 

After these changes, I could see a few log files got deleted, but majority
of the log files remain in the Kahadb folder which consume lot of disk
space. 

I observed this in our production server where I cannot enable trace or JMX.
Is there any other way to identify what is causing this issue?

TIA,
Shobhana



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/KAHADB-clean-up-old-log-files-tp4716661p4717977.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: AMQ 5.13.2 : Kaha DB logs cleanup issue

[Shobhana]

Hi Tim,

I tried 5.13.3 and all further versions till 5.14.0, but this problem is
still not gone. I still see a lot of Kaha DB log files which consume huge
amounts of disk space and eventually the broker stops functioning!

I made some more changes to check if I could get rid of this problem :
a) I enabled following plug-in to set expiry of 1 day for every message (we
use only MQTT messages) :

  



b) I enabled DLQ to drop all expired messages for all topics and queues :

  




c) I enabled offline durable subscribers to timeout after 1 day :
offlineDurableSubscriberTimeout="8640"
offlineDurableSubscriberTaskSchedule="360"

After these changes, I could see a few log files got deleted, but majority
of the log files remain in the Kahadb folder which consume lot of disk
space.

I observed this in our production server where I cannot enable trace or JMX.
Is there any other way to identify what is causing this issue?

TIA,
Shobhana






--
View this message in context: 
http://activemq.2283324.n4.nabble.com/AMQ-5-13-2-Kaha-DB-logs-cleanup-issue-tp4712046p4717976.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.