Switch to DuckDuckGo Search
   January 17, 2019
< | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31

Toggle Join/Part | bottom
[00:08:33] *** [diablo] <[diablo]!~diablo]@unaffiliated/miles/x-000000001> has quit IRC (Quit: Ping timeout (120 seconds))
[00:09:59] *** [diablo] <[diablo]!~diablo]@unaffiliated/miles/x-000000001> has joined #qpid
[01:29:53] *** lithium <lithium!~lithium@unaffiliated/lithium> has joined #qpid
[02:00:05] *** stitchedup <stitchedup!~stitchedu@146.115.146.152> has quit IRC (Read error: Connection reset by peer)
[02:00:30] *** stitchedup <stitchedup!~stitchedu@146.115.146.152> has joined #qpid
[02:03:15] *** lithium <lithium!~lithium@unaffiliated/lithium> has quit IRC (Ping timeout: 268 seconds)
[02:29:06] *** lithium <lithium!~lithium@unaffiliated/lithium> has joined #qpid
[03:02:33] *** lithium <lithium!~lithium@unaffiliated/lithium> has quit IRC (Ping timeout: 268 seconds)
[03:18:27] *** gemmellr1 <gemmellr1!~rgemmell@apache/committer/robbie> has joined #qpid
[03:18:27] *** ChanServ sets mode: +o gemmellr1
[03:19:49] *** gemmellr <gemmellr!~rgemmell@apache/committer/robbie> has quit IRC (Ping timeout: 268 seconds)
[05:00:49] *** lithium <lithium!~lithium@unaffiliated/lithium> has joined #qpid
[05:09:06] *** stitchedup <stitchedup!~stitchedu@146.115.146.152> has quit IRC (Read error: Connection reset by peer)
[05:09:26] *** stitchedup <stitchedup!~stitchedu@146.115.146.152> has joined #qpid
[05:16:05] *** tbish <tbish!~timothy@c-69-243-80-114.hsd1.va.comcast.net> has quit IRC (Quit: Leaving.)
[05:33:12] *** lithium <lithium!~lithium@unaffiliated/lithium> has quit IRC (Ping timeout: 250 seconds)
[05:38:16] *** stitchedup <stitchedup!~stitchedu@146.115.146.152> has quit IRC (Read error: Connection reset by peer)
[05:39:02] *** stitchedup <stitchedup!~stitchedu@146.115.146.152> has joined #qpid
[06:08:23] *** lithium <lithium!~lithium@unaffiliated/lithium> has joined #qpid
[06:41:18] *** lithium <lithium!~lithium@unaffiliated/lithium> has quit IRC (Ping timeout: 245 seconds)
[09:06:39] *** lithium <lithium!~lithium@unaffiliated/lithium> has joined #qpid
[09:51:43] *** dejanb <dejanb!~dejanb@dynamic-109-121-74-4.adsl.eunet.rs> has joined #qpid
[10:18:53] *** kara_ <kara_!55ffec31@gateway/web/freenode/ip.85.255.236.49> has joined #qpid
[10:23:09] *** kara_ <kara_!55ffec31@gateway/web/freenode/ip.85.255.236.49> has quit IRC (Ping timeout: 256 seconds)
[10:30:48] *** kara_ <kara_!d4338cf0@gateway/web/freenode/ip.212.51.140.240> has joined #qpid
[10:33:12] *** kara_ <kara_!d4338cf0@gateway/web/freenode/ip.212.51.140.240> has quit IRC (Client Quit)
[10:33:44] *** kara_ <kara_!55ffec31@gateway/web/freenode/ip.85.255.236.49> has joined #qpid
[10:35:46] <kara_> Hi. I have a problem sending message to qpid server. When I set the expiration to 10000 in rabbitmq BasicProperties the message is not delivered
[10:37:00] <kara_> This is because in QueueEntryImpl it checks System.currentTime > expiration
[10:38:37] <kara_> Current time in millis is much greater than 10000 and it always thinks it is expired
[10:39:12] <kara_> Is my understanding wrong? It looks like a bug to me
[10:42:19] *** lithium <lithium!~lithium@unaffiliated/lithium> has quit IRC (Quit: Sleep)
[10:46:05] <gemmellr1> kara_: presumably it is expecting the absolute expiry time and not a relative period
[10:46:10] *** gemmellr1 is now known as gemmellr
[10:50:13] <kara_> It works fine with RabbitMQ. The documentation says that Expiration: Expiration time after which the message will be deleted. The value of the expiration field describes the TTL period in milliseconds.
[10:50:27] *** lithium <lithium!~lithium@unaffiliated/lithium> has joined #qpid
[10:51:11] <gemmellr> kara_: I believe this is an area the AMQP 0-9-1 spec does not define what the field does, and Qpid went with absolute 'expiration' (e.g like JMS messages report) and RabbitMQ went with relative 'ttl'
[10:52:24] <gemmellr> AMQP 1.0 for example defines an absolute-expiry-time field, and a ttl field
[10:53:19] <kara_> Thanks gemmellr. Do you suggest to upgrade amqp 1.0?
[10:57:45] <gemmellr> kara_: generally yes (it is the current and only ISO Standard version of AMQP), but that would really depend on your needs, i.e are you using RabbitMQ for specific reeasons, and if so is their 1.0 support suitable for your needs
[10:58:55] <kara_> Thank you very much!
[11:05:39] *** kara_ <kara_!55ffec31@gateway/web/freenode/ip.85.255.236.49> has quit IRC (Ping timeout: 256 seconds)
[11:18:26] *** gemmellr is now known as gemmellr_afk
top

   January 17, 2019
< | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31