Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.10.0
-
None
Description
Some recent isses reported on the users list have shown that the client doesn't handle Errors (as opposed to Exceptions) well during the connection creation process. A couple of examples were from using incompatible version of proton-j (due to an older version being embedded within another client library being earlier on the classpath), and from failing to make some required classes available within an OSGi environment.
Looking closer, this is because the relevant tasks are passed to an Executor, but only Exceptions are caught within the task and used to fail their related requests, with the Executor itself swallowing any Errors when they weren't handled. We should trip request failure upon seeing Errors as well.