scholzj commented on issue #1341:
URL: 
https://github.com/apache/camel-kafka-connector/issues/1341#issuecomment-1054558964


   > Why didn't the connector die and restart the process?
   
   TBH, it is quite hard to say what exactly the problem is when the whole 
environment gets into some broken state. The error clearly suggests that there 
is an issue with OAuth due to expired signing certificate for the tokens. The 
Admin Client is most likely used by Connect itself and not by the connector (as 
will be in most cases the Kafka consumers and producers). So this error is not 
directly in the connector.
   
   Also - as a sidenote - Kafka Connect lifecycle is not bound to any 
particular connector. So whether one particular connector works or not does not 
impact the state of the Connect worker.
   
   > Is there a way we can propagate the Admin client exception in the 
application?
   
   Not sure what exactly you mean with the application here. But in general, 
the application is in this case Connect which based on the logs has the errors. 
So where exactly would you want to propagate them?
   
   > If not, How can I monitor my application health?
   
   Again, it is not completely clear what is the _application_ here. I guess 
the Connect metrics can give you a lot of information.


-- 
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]


Reply via email to