Grouper Users - Open Discussion List

[Dominique Petitpierre <>]

Hello,

thanks for your answer:


On 9/13/19 4:03 PM, Hyzer, Chris wrote:
> Its seeing if database configuration is changed.  Just ignore these.  or if 
> you don’t want them, make sure you are on the most recent patches of 
> grouper (might already be fixed), and see if you still have the problem.

The new patches (70, 71, 72) were applied and these warning messages did no 
appear anymore.

There were other new problems related to database configuration, but I'll 
wait for new patches;
In the mean time the configuration in the database was disabled by removing 
", database:grouper" in all the *.config.hierarchy properties.

This made me realize that each time the full upgrade process was performed, 
which happened over a few weeks, there were more patches being applied.
I had not paid attention to the patch numbers, thinking that I was upgrading 
to a fixed "released" tagged 2.4.0 stable version.
I really was wondering why I was seeing new problems every time: I was aiming 
at a moving target!


> -----Original Message-----
> From:  
> <> On Behalf Of Dominique Petitpierre
> Sent: Thursday, September 12, 2019 7:27 PM
> To: 
> Subject: [grouper-users] GrouperJdbcConnectionProvider: "shouldnt set ..." 
> warning messages
> 
> Hello,
> in the process of upgrading Grouper to version 2.4.0 I encounter some 
> problems. Here is another one:
> 
> When the Grouper UI webapp is running there are periodic warning messages 
> every 4 minutes in the log grouper_error.log:
> 
> 2019-09-12 23:41:36,034: [Thread-11] WARN  
> GrouperJdbcConnectionProvider.init(104) -  - shouldnt set driver for 
> GrouperJdbcConnectionProvider: null, oracle.jdbc.driver.OracleDriver
> 2019-09-12 23:41:36,034: [Thread-11] WARN  
> GrouperJdbcConnectionProvider.init(120) -  - shouldnt set dbUrl for 
> GrouperJdbcConnectionProvider: null, 
> jdbc:oracle:thin:@dbtst.unige.ch:1521:dbtst
> 2019-09-12 23:41:36,034: [Thread-11] WARN  
> GrouperJdbcConnectionProvider.init(124) -  - shouldnt set dbUser for 
> GrouperJdbcConnectionProvider: null, grouper
> 2019-09-12 23:41:36,035: [Thread-11] WARN  
> GrouperJdbcConnectionProvider.init(128) -  - shouldnt set dbPassword for 
> GrouperJdbcConnectionProvider: null
> 2019-09-12 23:45:36,193: [Thread-11] WARN  
> GrouperJdbcConnectionProvider.init(104) -  - shouldnt set driver for 
> GrouperJdbcConnectionProvider: null, oracle.jdbc.driver.OracleDriver
> 2019-09-12 23:45:36,194: [Thread-11] WARN  
> GrouperJdbcConnectionProvider.init(120) -  - shouldnt set dbUrl for 
> GrouperJdbcConnectionProvider: null, 
> jdbc:oracle:thin:@dbtst.unige.ch:1521:dbtst
> 2019-09-12 23:45:36,194: [Thread-11] WARN  
> GrouperJdbcConnectionProvider.init(124) -  - shouldnt set dbUser for 
> GrouperJdbcConnectionProvider: null, grouper
> 2019-09-12 23:45:36,194: [Thread-11] WARN  
> GrouperJdbcConnectionProvider.init(128) -  - shouldnt set dbPassword for 
> GrouperJdbcConnectionProvider: null
> 
> This is written by the "init" method of GrouperJdbcConnectionProvider.
> The "null" value corresponds to the parameter sourceId.
> 
> - How can one "not set" those values?
>   They are configured only once in grouper.hibernate.properties.
> 
> Presumably it is linked to the c3p0 pool of JDBC connections which empties 
> (after hibernate.c3p0.timeout = 100 seconds)
> and it occurs when a new connection needs to be established.
> 
> 
> For my understanding:
> - Why does Grouper UI  connect to the database every 4 minutes while 
> otherwise idle?
> From a tcpdump, it looks like there is only one query
> "select config_file_name, config_key, config_value from grouper_config 
> where config_file_hierarchy = :1"
> and eventually an error is returned:
> "ORA-01403: no data found".
> 
> 
> Thanks in advance for your help!
> 
> Regards.
> 


-- 
Mr Dominique Petitpierre, user=Dominique.Petitpierre domain=unige.ch
IT Division, University of Geneva, Switzerland