Hibernate WARN messages flooding logs in RSA Identity Governance & Lifecycle
4 years ago
Originally Published: 2020-09-16
Article Number
000042557
Applies To
RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.1.1, 7.2.0
 
Issue
The aveksaServer.log logs WARN level log messages similar to the following.
08/18/2020 16:57:07.230 WARN (Worker_actionq#Normal#jdbc/avdb_258) [org.hibernate.hql.internal.ast.HqlSqlWalker] [DEPRECATION] Encountered positional parameter near line 1, column 343 
in HQL: [select count(cri.id) from com.aveksa.server.core.cr.ChangeRequestItem cri, com.aveksa.server.core.Application app where ((cri.operandAppId=app.id and cri.operandTypeStr not in ('US')) or cri.valueAppId=app.id) and (app.name = 'UID' OR app.name = 'Office 365 MFA program' OR app.name = 'MYAPP' OR app.name = 'MYAPP-ITG') and (cri.itemID IN (?,?))]. 
Positional parameter are considered deprecated; use named parameters or JPA-style positional parameters instead.
08/18/2020 16:57:09.551 WARN (Worker_jobq#Normal#jdbc/avdb_24) [org.hibernate.hql.internal.ast.HqlSqlWalker] [DEPRECATION] Encountered positional parameter near line 1, column 250 
in HQL: [select count(cri.id) from com.aveksa.server.core.cr.ChangeRequestItem cri, com.aveksa.server.core.Application app where ((cri.operandAppId=app.id and cri.operandTypeStr not in ('US')) or cri.valueAppId=app.id) and (app.cai1 = 1) and (cri.itemID IN (?,?))]. 
Positional parameter are considered deprecated; use named parameters or JPA-style positional parameters instead.
Cause
This is an Oracle database deprecation warning.
Resolution

This is resolved in the following versions where these WARN level messages are suppressed.

  • RSA Identity Governance & Lifecycle 7.1.1 P08
  • RSA Identity Governance & Lifecycle 7.2.0 P02
  • RSA Identity Governance & Lifecycle 7.2.1
Workaround
This is benign except that in some environments can flood the aveksaServer.log with a lot of messages.