JMS(3.0)

Owned by Former user (Deleted)
Last updated: May 02, 2023 by Former user (Deleted)
1 min read

The JMS agents enable  to communicate with other JMS application components. Following the JMS 1.1 specification, the agents look up the configured ConnectionFactory and Destination objects using JNDI. Therefore, it is required that a JNDI server is configured and can be accessed by the agents. 

Prerequisites

The user of this information should be familiar with:

  • JNDI
  • JMS

Supported JMS  Vendors

The following JMS vendors are currently supported:

JMS VendorsVersion
Weblogic12.2.1.3
SonicMQN/A
ActiveMQ5.15.0
JBossMQN/A
HornetQ2.4.0.Final
Solace9.7.0.29


Note!

Solace has a known limitation when the JMS processing agent and Solace VMR server are temporarily disrupted. When the agent successfully reconnects, it freezes when forwarding the next JMS message via a Solace JMS API. The issue is observed when using Solace JMS APIs lib version 10.1.1.


This section contains the following subsections: