Here I am again with durable topic subscribers ;) Is it a bug or a feature that Pending Queue sizes in admin interface are zero, even if there are messages pending?
To test this, first I have subscribed to a topic and left using stomp: > telnet adminbroker 61613 Trying 213.198.74.83... Connected to adminbroker. Escape character is '^]'. CONNECT client-id:test2 login:system passcode:manager ^@ CONNECTED session:test2 SUBSCRIBE activemq.prefetchSize:1 activemq.subscriptionName:masterbcast ack:client-individual destination:/topic/COMMAND.test id:masterbcast ^@ ^] telnet> q Connection closed. now i see an offline durable subscriber in the admin interface, so I send a few messages like this > telnet adminbroker 61613 Trying 213.198.74.83... Connected to adminbroker. Escape character is '^]'. CONNECT client-id:test2 login:system passcode:manager ^@ CONNECTED session:test2 SEND destination:/topic/COMMAND.test persistent:true asdf ^@ SEND destination:/topic/COMMAND.test persistent:true asdf ^@ ^] telnet> q Connection closed. In the admin interface Pending Queue Count is still zero although the messages are there and can be fetched > telnet adminbroker 61613 Trying 213.198.74.83... Connected to adminbroker. Escape character is '^]'. CONNECT client-id:test2 login:system passcode:manager ^@ CONNECTED session:test2 SUBSCRIBE activemq.prefetchSize:1 activemq.subscriptionName:masterbcast ack:client-individual destination:/topic/COMMAND.test id:masterbcast ^@ MESSAGE message-id:ID:STATS2-38410-1314344446931-6:490:-1:1:1 destination:/topic/COMMAND.test timestamp:1314345053259 expires:0 subscription:masterbcast priority:4 asdf ACK message-id:ID:STATS2-38410-1314344446931-6:490:-1:1:1 ^@ MESSAGE message-id:ID:STATS2-38410-1314344446931-6:490:-1:1:2 destination:/topic/COMMAND.test timestamp:1314345067627 expires:0 subscription:masterbcast priority:4 asdf ACK message-id:ID:STATS2-38410-1314344446931-6:490:-1:1:2 ^@
