Tuesday, January 19, 2016

Solace JMS issue

Solace JMS provider implementation has an obvious bug, in SolMessageProducer.java, method
protected void sendMessage(Destination destination, Message message, int deliveryMode, int priority, long timeToLive)

the parameter priority is never used, it sets the priority to 0 directly:
solMsg.setJMSPriority(0);

It causes that the JMSPriority cannot be set to other value. It exists until the current version: sol-jms-7.1.2.226

QBrowser is an excellent Java Swing GUI client. It can browse the queue/topic with minor modification.
https://java.net/nonav/projects/mq/sources/mq5/content/mq/src/share/java/examples/applications/qbrowser/QBrowser.java?rev=38

Hermes should be more powerful, but it's too complex and you can only treat it as a black box. I cannot configure it to connect Solace based on the below document. Already set SECURITY_PRINCIPAL to username@vpn Got the error
jndi lookup failed - 401 incomplete authentication configuration

http://dev.solacesystems.com/integration-guides/hermes-jms/

The JMS API provides no mechanism for browsing a topic. Messages usually disappear from a topic as soon as they appear: if there are no message consumers to consume them, the JMS provider removes them. Although durable subscriptions allow messages to remain on a topic while the message consumer is not active, no facility exists for examining them.

No comments:

Post a Comment