stankiewicz opened a new issue, #35165: URL: https://github.com/apache/beam/issues/35165
### What happened? Currently JMS.Write catches all JMSException and routes the input records to failedMessagesTags. Issues: - there is no way to understand why record has failed, input record doesn't have exception attached to it - in case of transient issues, if underlying jms.connection doesn't have connection recovery built-in (see [activeMQ)](https://activemq.apache.org/components/artemis/documentation/2.17.0/client-reconnection.html), connection won't recover, as connection is established on setup() method and is never recycled (e.g. after 100+ jms exceptions) some comment: Vendors (IBM, activeMQ) has various exceptions and it's difficult to decide based on exception instance if this is network, transient issue or some other case. ### Issue Priority Priority: 2 (default / most bugs should be filed as P2) ### Issue Components - [ ] Component: Python SDK - [x] Component: Java SDK - [ ] Component: Go SDK - [ ] Component: Typescript SDK - [x] Component: IO connector - [ ] Component: Beam YAML - [ ] Component: Beam examples - [ ] Component: Beam playground - [ ] Component: Beam katas - [ ] Component: Website - [ ] Component: Infrastructure - [ ] Component: Spark Runner - [ ] Component: Flink Runner - [ ] Component: Samza Runner - [ ] Component: Twister2 Runner - [ ] Component: Hazelcast Jet Runner - [ ] Component: Google Cloud Dataflow Runner -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
