Hi everyone, my evaluation of QPID v0.14 features is slowly approaching the end. Unfortunately I haven't really found reliable information on each of my requirements. I would like to ask you to verify whether the following statements are true (in C++ broker and JMS client) or not:
1) Destination bridging (as in Tibco EMS) is not supported. 2) There is no monitoring event to detect exceedance of broker memory limits. 3) No monitoring event is created upon purging messages in qpid-tool 4) There is no feature to detect slow/hung consumers 5) The installation of the C++ broker requires root privileges 6) There is no message rollback limit (such as 10 times) 7) There is no message processing time threshold to identify messages staying in a queue longer than a specified threshold 8) SQL92-compliant message selectors as defined in the JMS standard are not supported 9) Message selectors cannot be applied to messages that are routed between brokers. 10) There is no option to specify a maximum log file size, before rotation to another log file takes place 11) How does the fanout functionality work? Can I use it to do reliable multicast as in PGM or is it more like a general broadcast without any guarantees? 12) Message compression is not supported (only by the application itself) 13) There is no way to do message tracing in the broker. I know that this is a very long list, but I thought that creating 13 posts on the mailing list would lead to even more chaos. Thank you for your support. Regards, Holger -- View this message in context: http://qpid.2158936.n2.nabble.com/Evaluation-of-requirements-tp7581225.html Sent from the Apache Qpid users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
