RASunOne is the connector for Sun Java System Message Queue.
The connector for SJSMQ is shipped as rasunone.rar. It includes the client runtime (imqjmsra.jar).
- Enabled CC mode
- Now shipping with 3.7UR1 client runtime
- Extensive support for message management through Enterprise Manager
- This version supports 3.6 UR4 and up.
- The URL syntax must be mq://host:port/serviceName?option1=value1&option2=value2. Notes:
- SJSMQ jms and ssljms services are supported.
- If serviceName is omitted, jms service will be used as default.
- To support one or more SJSMQ message server addresses, add a comma and another URL, e.g. mq://host:port/serviceName?option1=value1&option2=value2, mq://host:port/serviceName?option1=value1&option2=value2
- Options can include options for JMSJCA and options for the client runtime. The latter options are propagated to the SJSMQ connection factories.
- the connector has been certified with client runtime version 3.6 SP4 (Build 1) and 3.7 UR1. When deploying into Sun Java System Application Server 8.1, make sure that the version of the imqjmsra.jar that is in the classpath of the server is of this version or higher.
- To make management messages persistent, add this option in the configuration file of the SJSMQ broker: imq.metrics.topic.persist=true. Refer to the documentation of SJSMQ for a description of this option, as well as other options such as imq.metrics.interval, imq.metrics.topic.interval and imq.metrics.topic.timetolive.
Under the following conditions:
- the system is processing messages
- CC mode is used
- the inflow of messages is closed by undeploying the application or other means
... one or more messages may appear to get lost. These messages re-appear when the SJSMQ broker is restarted.
Workaround #1:use sync mode instead of CC mode. This implies that there is no concurrent processing for topics. This mode can be specified in the deployment descriptor or in the URL. See the JMSJCA release notes.
Workaround #2: restart the SJSMQ broker if this situation occurs
The management MBean for management of messages in queues and topics is limited to queues only because the client runtime does not provide functionality for the management of topics.
Workaround: upgrade to 3.7UR1 or higher.
To enable concurrent processing on queues when using sync mode, make sure to provide this option in the configuration of the SJSMQ broker: imq.autocreate.queue.maxNumActiveConsumers=-1. The default number of messages sent to one queue-receiver; this is likely too many to have a reasonable concurrency. Therefore it is recommended to set this additional parameter in the broker configuration: imq.autocreate.queue.consumerFlowLimit=10