Hi Ovidio, On the JIRA link i can only seem to browse issues, the submit issue link below on the page is as far as i can see only for JIRA itself.
A feature that would help me a lot is an addition to the JMX function of JBoss Messaging. When you open a queue in JMX you can see the number of messages that are still in the queue. There is also a purge queue function. Nothing new sofar. What i would like is to get a list of active consumers in the queue. Each consumer would have a JMX interface where you can see some kind of reference set by the MDB and an indication how long this consumer is running. So, then i can see for what messages are taking a (too) long time for the consumer to finish. If i would be possible, this JMX interface would have a method to stop the consumer from processing and to pick up a new message from the queue. In short i would get two functions to manage the queue. One is to reset a consumer through JMX. The othere is to set a reference for the consumer programmatically within the MDB that will be visible in JMX at consumer level. ---------------- Antoher approach, that might slightly too advannced, is to make a dynamic optimisation of the maximum number of consumers. You might compare it with old school RBDMS that needed skilled DBA's to configure specific parameters for each table. 'Modern' systems can configure themselves on the fly. In a real life situation where you have say 20% slow messages ad 80% fast messages where for example the slow messages only use few system resources. You need an old school DBA to configure the optimal consumer settings. The consideraion is: too many consumers will kill the application server and too little consumers will lead to traffic jams. A solution would be to have a "maximum resource setting", instead of setting a fixed number of maximum consumers. JBoss Messages could add as many consumers as it would wish as long as the whole queue would not exceed XX% of the available resources. So, in terms of speed, JBoss Messaging would then become superior because it will always utilise all available computing power and it will not be restricted to some arbritrary, manual setting. If you add the above mentioned JMX with reference, then that would be similar to a 'log slow query' function that will give the system manager a clue how to improve on the slow or troublesome messages. Jaap View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979807#3979807 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979807 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
