metrics vs plugged-in persistent store
Hello. I'm running IMQ3.5sp1 on Linux with java 1.4.2_04.
I'm using the plugged-in persistent store.
I get this error in the broker log when I try to run the default metrics (ttl) on a Topic: I'm concerned it may point to a bug:ERROR [B3100]: Unexpected Broker Internal Error : [unable to disk usagefor destinationFlowEvent [Topic]] :
com.sun.messaging.jmq.jmsserver.util.BrokerException: The operation does not apply to plugged-in persistent store.
I guess, it is a known bug in 3.5 SP1
The bug given below is in the 3.5SP1 release notes.
=====================
4950601
imqcmd metrics dst triggers broker internal error to be printed when using the JDBC persistent store.
Disk usage metrics information applies to file store only. However, when metrics information is retrieved, the broker will try to get the disk usage information regardless of the store type. If a database is used instead of the file store, the following error message will be printed by the broker:
06/Nov/2003:22:57:36 PST] ERROR [B3100]: Unexpected Broker Internal
Error : [unable to disk usage for destinationT:topic1] :
com.sun.messaging.jmq.jmsserver.util.BrokerException:
The operation does not apply to plugged-in persistent store.
Workaround: None
============
--
Sagar
