Yes, it should follow the pattern for listMessages, i.e. be exposed as a management operation on org.jboss.mq.server.jmx.Queue and org.jboss.mq.server.jmx.Topic (with an optional extra parameter to identify the subscription).
What do you do about messages that have been received by the client but not acknowledged? e.g. removeAllMessages() also removes these, but this may not be behaviour you want? I've been thinking about adding an optional parameter: void removeAllMessages(boolean includingUnackedMessages); View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3835968#3835968 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3835968 ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
