When connecting to Solace via JMS JNDI LookUp with compression the lookup occurs over 55555 but the connection then connects of 55003. I have a network configuration where we port translate to multiple solace instances and trying to figure out how to map different servers to different ports but I ca…

I think I figured it out. you have to overide the host value of the connection factory by calling setHost when the SolConnectionFactory is returned. This is the connection host and port that is used to establish the JMS connection. The URL you listed in the JNDI is only for the JNDI lookup.

Can you set compression port on JMS client?

PubSub+ Event Broker

amackenzie December 15, 2021, 4:07pm 6

The port can be in the JNDI Properties file as per the “tip” on the right. Does that help?

Topic		Replies	Views
Solace Message Compression PubSub+ Event Broker	3	6330	January 25, 2022
JMS API connection factory route to different VPN PubSub+ Event Broker	3	14073	September 9, 2021
Solace PubSub+ APIs (JMS/JCSMP, C, .NET) are released PubSub+ Event Broker	17	36296	September 16, 2022
JCSMP, JMS, and New Java APIs now support WebSockets! PubSub+ Event Broker	0	173	September 13, 2024
Solace now supports Payload Compression! Training, Tips and Tricks	9	402	October 16, 2024

Can you set compression port on JMS client?

Related topics