On 8/5/2013 8:15 PM, Scott Battaglia wrote:
This isn't really a long term solution but you should be able to set
your default logging level to WARN and then set
net.sf.ehcache.distribution.ManualRMICacheManagerPeerProvider explicitly
to DEBUG. This will at least show them in the production logs.
This isn't really a long term solution but you should be able to set your
default logging level to WARN and then set net.sf.ehcache.distribution.
ManualRMICacheManagerPeerProvider explicitly to DEBUG. This will at least
show them in the production logs.
On Mon, Aug 5, 2013 at 11:12 PM, Paul B. H
I'm testing out ehcache based ticket replication, and it seems the
ehcache code logs connection failures at DEBUG level:
2013-08-05 17:44:39,624 DEBUG
[net.sf.ehcache.distribution.ManualRMICacheManagerPeerProvider] -
Looking up rmiUrl //ned:41001/org.jasig.cas.ticket.ServiceTicket through
exceptio
