Hi Gordon,
>> 4) There is no feature to detect slow/hung consumers
>You can get an alert when the backlog of messages for a subscriber
>reaches a configured level. That would be indicative of a slow
consumer.
How can I do that? Setting something like
"default-event-threshold-ratio" or "alert_size"? Can we be sure that it
is one single consumer that is too slow on reading and not just the
ensemble of all consumers?
>> 8) SQL92-compliant message selectors as defined in the JMS standard
are not
>> supported
>They are not yet supported by the c++ broker, but the JMS client can
>evaluate them on the client side. So logically the feature is there,
>though less efficiently implemented than if they were evaluated server
side.
I tried using a message selector in the client using an SQL92 compatible
string from the Oracle JMS API ("NewsType = 'Sports' OR NewsType =
'Opinion'"). However I get the following exception:
"javax.jms.InvalidSelectorException: cannot create consumer because of
selector issue"
Do you have any idea why this is? NewsType is a String property which I
am creating manually in the producer, but that shouldn't be a problem at
the time the client creates the consumer.
>> 13) There is no way to do message tracing in the broker.
>No, but if you can describe what you would like here in a bit more
>detail, that would be useful for possible future development.
I'll try to get back on that.
Regards,
Holger
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
