🎄 Happy Holidays! 🥳
Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.
Happy Holidays!
Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.
Fail back to broker configuration for IPC clients
If you need to set up IPC connections, you introduce dependencies in application start-up order and availability: if your IPC listener isn't up when your connection initiator starts, you get a failure.
To mitigate this, you might like the option of your IPC connection failing back to a broker connection. This ensures the connections are always made, but how to control this, so that you don't accidentally end up with broker connections?
The answer is to create a client-username for use with IPC clients. In normal operation, leave this shutdown, so that IPC clients don't accidentally connect to the broker. Then, specify the broker as the second connection in the host list. Examples using sdkperf:
sdkperf -cip=listen:localhost:port ... (IPC listener)
sdkperf -cip=shm:localhost:port,broker-ip:port -cu=ipc@message-vpn ... (IPC connection initiator)
The connection initiator will connect via IPC or fail. If you decide you want to enable broker connections, simply "no shutdown" the "ipc" client-username (you'll need to reconfigure the IPC listener to connect to the broker if that's what you'd like to do) Once you have the IPC listener running, you can shutdown the ipc client-username and the IPC connections will be made automatically!
Comments
