Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
None
-
None
Description
Currently, when creating a SiteSpecificTrustStore and the protocol is not specified in the URL the object will be created but put into ERRORED state. No indication as to what is wrong is given. Furthermore the URL is not editable rendering the newly created object utterly useless.
On the Broker side a MalformedURLException is logged at INFO level giving the helpful information "no protocol".
On the broker side we do not need a full stack trace.
On the client side a error message would be preferable to creating an ERRORED object.
Attachments
Issue Links
- is related to
-
QPID-7623 "SEVERE: RuntimeException while executing runnable" reported by Guava to stderr if a state transition method throws exception
- Closed