You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The null in this message can be traced to logging in omero-blitz omero.client on line 803.
The null is meant to be a reason that is set in the catch block handling the exception. However the reason variable is declared inside the retry loop while loop. Thus is always null when the retry reason is logged.
Note that if the Glacier2.SessionPrx prx ends up being null after the failed connection attempts, the last recorded reason can then also be thrown in the line:
if (null == prx) {
// TODO: Add 'reason' to this error if not nullthrownewClientError("Obtained null object proxy");
}
The text was updated successfully, but these errors were encountered:
I have a connection issue with OMERO Insight but the logging outputs a non-helpful message.
The message logged to the console during the Insight's retry attempts is:
The
null
in this message can be traced to logging in omero-blitzomero.client
on line 803.The
null
is meant to be areason
that is set in the catch block handling the exception. However thereason
variable is declared inside the retry loop while loop. Thus is always null when the retry reason is logged.See omero.client Line 801
If you move this declaration outside the while loop:
Then the logged message will be useful.
Note that if the
Glacier2.SessionPrx prx
ends up being null after the failed connection attempts, the last recordedreason
can then also be thrown in the line:The text was updated successfully, but these errors were encountered: