We're updating the issue view to help you get more done. 

Log fills up with "unmarshalling failure" messages when a cluster partition member is unreachable

Description

It was the intention of the RegistrarProxy.handleException to rethrow the exception if it is an Error, unless it is a LinkageError, OutOfMemoryError, or StackOverflowError. Otherwise print the exception stack trace if debugging is enabled.

The following printout is done in INFO instead of debug -

INFO [com.sun.jini.reggie] - unmarshalling failure; Caused by: java.io.NotActiveException: Failed to retrieve proxy from service, cause Connect Failed to [NIO://192.168.33.10:49706/pid[860]/1212233883811_3_286485615364391954_details[class com.gigaspaces.internal.server.space.SpaceImpl(foo_container1_1:foo)]]; nested exception is:
java.io.IOException: java.net.SocketException: Host is down

Move this log to level FINEST, configurable by
com.sun.jini.reggie.level = FINEST

Workaround

None

Acceptance Test

monitor log output on disconnect

Status

Assignee

Meron Avigdor

Reporter

Meron Avigdor

Labels

None

Priority

Trivial

SalesForce Case ID

None

Fix versions

Commitment Version/s

None

Due date

None

Product

XAP

Edition

Open Source

Platform

All

Sprint

None