This is a short term change just before a shoal release.
Longer term solution is documented in a separate shoal issue. (will link when it
Currently when there is an IOException from DAS to a server instance that was
either killed or server failed to start for some reason (like ORB bind address
still in use), it results in a WARNING that does not contain sufficient
information for an administrator to know what server instance there was a
difficulty sending a message to. Given that the WARNING was occurring for
non-error cases and there was not enough info in message for an administrator to
easily be able to figure out whether the WARNING is something that requires
attention or not. This log event is being reduced to FINE.
When such a message does occur with FINE, here is how one can correlate the
failure with a server instance name.
From a server.log, here is an event indicating a failure to send to another
server instance in the cluster. From the jxta://uuid-XXX, take the last 6
numbers and search the log for an entry that has a server instance name in it.
Unable to create a messenger to
Search for BF803, find following log entry that shows that the sendMessage was
to server instance
9: MemberId: n2c1m4, MemberType: CORE, Address:
For test in question, the server instance n2c1m4 was killed to test for
FAILURE notification. Thus, the log event does not capture an event that should
be viewed as a failure. The log message needs to be improved to specifically
state what server instance the send message was going to when it failed.
Future fix will make sure that sendmessage to a FAILING instance are only
reported once in server log and reported with actual server instance name.