Return-Path: Delivered-To: apmail-geronimo-activemq-users-archive@www.apache.org Received: (qmail 63280 invoked from network); 10 Jul 2006 20:20:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 Jul 2006 20:20:25 -0000 Received: (qmail 18607 invoked by uid 500); 10 Jul 2006 20:20:16 -0000 Delivered-To: apmail-geronimo-activemq-users-archive@geronimo.apache.org Received: (qmail 18570 invoked by uid 500); 10 Jul 2006 20:20:16 -0000 Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: activemq-users@geronimo.apache.org Delivered-To: mailing list activemq-users@geronimo.apache.org Received: (qmail 18539 invoked by uid 99); 10 Jul 2006 20:20:16 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Jul 2006 13:20:15 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of lists@nabble.com designates 72.21.53.35 as permitted sender) Received: from [72.21.53.35] (HELO talk.nabble.com) (72.21.53.35) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Jul 2006 13:20:13 -0700 Received: from [72.21.53.38] (helo=jubjub.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1G02ET-0004UY-Ku for activemq-users@geronimo.apache.org; Mon, 10 Jul 2006 13:19:53 -0700 Message-ID: <5258348.post@talk.nabble.com> Date: Mon, 10 Jul 2006 13:19:53 -0700 (PDT) From: colincrist To: activemq-users@geronimo.apache.org Subject: Re: ActiveMQ JMX Questions.. In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-Sender: colincrist@hermesjms.com X-Nabble-From: colincrist References: <5248649.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hey James, Firstly, to reply to you comments.. > I've just added to SVN trunk a browseMessages() method (or one that > takes a selector) to return a List of JMS Message objects. Excellent, I'll check it out tomorrow. TVM. >> I could >> also imagine a "browseChangesSince" that included a timestamp and >> returned >> me the messages added and removed from that subscription queue. > Could you use a selector I wonder to implement the timestamp range? I thought that too but you only get new messages and no notification of consumed messages before that point in time. If you want to use it to update a GUI then you need to be able to remove consumed messages from some table model or wahtever in Swing or JavaScript. I've not tried them but are JMX notifications a good or bad idea for this? I think I'd like to control when I get data. > Am just wondering about the 'headers' version of this option. Would it > include all possible headers (including user defined ones) - which > could be quite big too - and just miss off the actual bodies? So kinda > make empty JMS Message objects just excluding the body to represent > the 'headers'? Not really thought about the implications here, from my persective with Hermes, just having the JMS header properties is enough. I could then request to "fill in" the message later to get the rest of it. One question here is whether I'd be interested to know if the message has been consumed at this point in time. I'd probably either want to exclude consumed messages or get them with some additional boolean header property such as JMSX_AcitiveMQ_Consumed being set. Secondly, some other questions: 1. DurableSubscriptions When a broker is first started, the durable "Subscription" MBean looks like this: http://www.nabble.com/user-images/3179.png Note how the "SubcriptionName" is both null and incorrectly spelt. Once I've created a consumer for this durable subscription it looks like this: http://www.nabble.com/user-images/3180.png See how we now have the correctly and incorrectly spelt "SubscriptionName" filled in. I cannot correctly "discover" existing durable subcriptions the way things currently work. 2. DurableSubscriptions again I think the active=true/false should not be in the ObjectName. This also goes for the DurableTopicSubscribers and InactiveDurableTopicSubscribers attributes on the BrokerMBean - why the distinction at this level when the attribute is available on the MBean? I would consider whether there is an active consumer secondary to whether the subscription actually exists. 3. Lazy Queue MBean loading. I only see queue MBeans once a consumer first exists after a Broker startup even if there are messages pending. A management console needs to see all object with state once the broker has started. Happily, I've got an integration working quickly and if we can get the above working okay then ActiveMQ will have as functional integration with Hermes as its current plugin model allows. Next step is some cooler stuff like dynamically creating subscriptions, queues, topics and whatever else we can do via JMX. Regards, Colin. http://hermesjms.com -- View this message in context: http://www.nabble.com/ActiveMQ-JMX-Questions..-tf1917262.html#a5258348 Sent from the ActiveMQ - User forum at Nabble.com.