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. Henson <[email protected]>wrote: > 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 > exception Connection refused to host: ned; nested exception is: > > If I end up going into production, I'd really prefer to see at least > warnings, if not errors, if for some reason the cache peers are failing > to communicate (say, for example, a firewall rule was misconfigured). > There's a *lot* of debugging logs that don't really need to be seen on a > production system, so I'd rather not leave it at such a high log level. > > I'm guessing there's no way to fix this short of recompiling that code? > And it appears that's in upstream ehcache code, not cas specific code? > > For those using ehcache, how do you keep track of communications > failures or other ehcache issues? > > Thanks... > > > -- > Paul B. Henson | (909) 979-6361 | http://www.csupomona.edu/~henson/ > Operating Systems and Network Analyst | [email protected] > California State Polytechnic University | Pomona CA 91768 > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
