What happened?

When we upgraded the Beam version to 2.46.0 to use the Retryconfiguration we faced this issue:

JmsIO.Write sink = JmsIO.write()
.withConnectionFactory(ConnectionsFactoryObject)
.withValueMapper(new TextMessageMapper())
.withRetryConfiguration(RetryConfiguration.create(5))
.withQueue("testQueqe");

Here we used the TIBCO for jms

Issue Priority

Priority: 0 (outage / urgent vulnerability)

Issue Components

• Component: Python SDK
• Component: Java SDK
• Component: Go SDK
• Component: Typescript SDK
• Component: IO connector
• Component: Beam examples
• Component: Beam playground
• Component: Beam katas
• Component: Website
• Component: Spark Runner
• Component: Flink Runner
• Component: Samza Runner
• Component: Twister2 Runner
• Component: Hazelcast Jet Runner
• Component: Google Cloud Dataflow Runner