grouper-users - Re: [grouper-users] Cache reconnection config
Subject: Grouper Users - Open Discussion List
List archive
- From: "Hyzer, Chris" <>
- To: "" <>, Francesco Malvezzi <>
- Cc: "" <>
- Subject: Re: [grouper-users] Cache reconnection config
- Date: Tue, 7 Feb 2023 22:18:04 +0000
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=isc.upenn.edu; dmarc=pass action=none header.from=isc.upenn.edu; dkim=pass header.d=isc.upenn.edu; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=Vsyy0MPhEHYqS73CELygqSPpWGIrIOLCnWbcvCQ5ZW0=; b=hddTA+WpYnm1y+c1dFnyxqBj2qs/P7nlme4ymffQ3o2pm+PRdWc3B4bJMOC88aJwr8nFMEPJmC/UeEl33PNVkqXXSNUuLjPsY4afvMimTHljnweVboVCo6bK+qznjPXN0+NbsT73cWImVLanbMzwv9QMxrKGtk7hd8ppNkmiO5HQKBHqXmAfOJLpO0NkkCyPtpXWXKa7+EjngjyTqPdC6tpD3bqi2ni1+k6NPCiZY4tDm77aYupERpCidSesXkQwsFiKS3eBKFNDwrVYkzH05tIl1rHml8rXpn0VeAGZCj2gzluLazvWzBizDNpvlwnI7W4cUQsIzGK/zABAvUrLAg==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=iJj6UeV7+SrRsy9BA8UFnahVZ/+i7sYMpMyRRkMr6CAtDw4FuWdOegae7AFDS+ep6UEB8hlQnUHjnNd1TrE1QfWT1WpeRqCtrP7yo2AzDFEqpvNyCTaiVBi+oL9QvJaSnTJwcU+33QSyX0eWM/6lRAopa+uedhsWummud1g57TZGARUxqNxrLES/per44bSmr/lw2DPAVuPJrk1RCZ/n6hpW9CB12yCxHV0MhaqQAMsv1bgdZsLZE652wAKCJwcJnQg0UQM2zcw1wZQUiErBIv1B5yYl6Zual0YfX8BdRJgizLc83fjZZCEqcbnnKdy5Nj1mVBfFZb/E75Xe2OJyvw==
- Msip_labels:
I think the database pool needs to reconnect, there could be a c3p0 setting to help adjust this...
From: <> on behalf of Francesco Malvezzi <>
Sent: Tuesday, February 7, 2023 12:15 PM
To: <>
Cc: <>
Subject: Re: [grouper-users] Cache reconnection config
Sent: Tuesday, February 7, 2023 12:15 PM
To: <>
Cc: <>
Subject: Re: [grouper-users] Cache reconnection config
On 07/02/23 17:19, Bruce Timberlake wrote:
> On Tue, Feb 7, 2023 at 5:13 AM Francesco Malvezzi <
> > wrote:
>
>> hi everybody,
>>
>> our grouper stores data on Oracle.
>>
>> It looks sometimes the DNS has a failure and it has to drop connection
>> to DB. When DNS is working again, grouper logs are full of these lines:
>>
>> grouper-daemon;grouper_error.log;2023-02-07T06:18:13,440: [Thread-27]
>> ERROR Grou
>> perLogger.error(77) - [] - Error in cache database thread
>> java.lang.RuntimeException: java.sql.SQLRecoverableException: Closed
>> Connection,
>> sql: select nanos_since_1970 from grouper_cache_overall where
>> overall_cache = 0,
>>
>
> We have had this issue ourselves since we deployed Grouper. The standard
> answer we have received has been "just restart the container" but it'd be
> nice to get a source of the problem identified TBH. We've poked at some
> settings, but nothing obvious has revealed itself to us so far. So for
> now, we have a Splunk alert for the error and the on-call person who gets
> the notification does a 'docker restart grouper-daemon' on the affected
> server(s) and moves on with life :)
>
a suboptimal solution is better than no solution! Thank you so much for
your pragmatic input that saves me so many pointless researches,
Francesco
> On Tue, Feb 7, 2023 at 5:13 AM Francesco Malvezzi <
> > wrote:
>
>> hi everybody,
>>
>> our grouper stores data on Oracle.
>>
>> It looks sometimes the DNS has a failure and it has to drop connection
>> to DB. When DNS is working again, grouper logs are full of these lines:
>>
>> grouper-daemon;grouper_error.log;2023-02-07T06:18:13,440: [Thread-27]
>> ERROR Grou
>> perLogger.error(77) - [] - Error in cache database thread
>> java.lang.RuntimeException: java.sql.SQLRecoverableException: Closed
>> Connection,
>> sql: select nanos_since_1970 from grouper_cache_overall where
>> overall_cache = 0,
>>
>
> We have had this issue ourselves since we deployed Grouper. The standard
> answer we have received has been "just restart the container" but it'd be
> nice to get a source of the problem identified TBH. We've poked at some
> settings, but nothing obvious has revealed itself to us so far. So for
> now, we have a Splunk alert for the error and the on-call person who gets
> the notification does a 'docker restart grouper-daemon' on the affected
> server(s) and moves on with life :)
>
a suboptimal solution is better than no solution! Thank you so much for
your pragmatic input that saves me so many pointless researches,
Francesco
- [grouper-users] Cache reconnection config, Francesco Malvezzi, 02/07/2023
- Re: [grouper-users] Cache reconnection config, Bruce Timberlake, 02/07/2023
- Re: [grouper-users] Cache reconnection config, Francesco Malvezzi, 02/07/2023
- Re: [grouper-users] Cache reconnection config, Hyzer, Chris, 02/07/2023
- Re: [grouper-users] Cache reconnection config, Francesco Malvezzi, 02/08/2023
- Re: [grouper-users] Cache reconnection config, Hyzer, Chris, 02/07/2023
- Re: [grouper-users] Cache reconnection config, Francesco Malvezzi, 02/07/2023
- Re: [grouper-users] Cache reconnection config, Bruce Timberlake, 02/07/2023
Archive powered by MHonArc 2.6.24.