jmeierhofer opened a new pull request, #16160: URL: https://github.com/apache/camel/pull/16160
# Description When Camel can not establish the connection to the S7 PLC, the component is throwing follow-up exceptions which are causing the application start up to fail and which hide the real connection issue. - Added isConnected() to endpoint which checks if connection is null. This method is public to allow external logic to check if endpoint is really connected. - Moved canWrite() call to be checked only when connected or re-connected. - Added additional canWrite() check after reconnectIfNeeded() Steps to reproduce: - Add Camel route with S7 driver - PLC is not available - Connection failure - Additional NullPointerExceptions are thrown # Target - [X] I checked that the commit is targeting the correct branch (note that Camel 3 uses `camel-3.x`, whereas Camel 4 uses the `main` branch) # Tracking - [X] If this is a large change, bug fix, or code improvement, I checked there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for the change (usually before you start working on it). # Apache Camel coding standards and style - [X] I checked that each commit in the pull request has a meaningful subject line and body. - [X] I have run `mvn clean install -DskipTests` locally from root folder and I have committed all auto-generated changes. <!-- You can run the aforementioned command in your module so that the build auto-formats your code. This will also be verified as part of the checks and your PR may be rejected if if there are uncommited changes after running `mvn clean install -DskipTests`. You can learn more about the contribution guidelines at https://github.com/apache/camel/blob/main/CONTRIBUTING.md --> -- 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]
