Download [#OPENAM-8294] No value specified for parameter of audit access

[OPENAM-8294] No value specified for parameter of audit access insert
statement Created: 05/Feb/16 Updated: 20/Nov/16 Resolved: 19/May/16
Status:
Project:
Component/s:
Affects
Version/s:
Fix Version/s:
Resolved
OpenAM
audit logging
13.0.0
Type:
Reporter:
Resolution:
Labels:
Remaining
Estimate:
Time Spent:
Original
Estimate:
Environment:
Bug
Priority:
kohei
Assignee:
Fixed
Votes:
13.5.0-Must-Fix, EDISON
Not Specified
Issue Links:
Depends
depends on
CAUD-311
Mismatch between prepared
statements ...
Duplicate
is duplicated
by
OPENAM8295
Parameter index out of range error Closed
wh...
13.5.0
Major
kohei
0
Not Specified
Not Specified
OpenAM 13.0.0 Build 5d4589530d (2016-January-14 21:15)
MySQL 5.1.17
Resolved
Target Version/s: 13.5.0, 14.0.0
Support Ticket
IDs:
Filip Kubáň
QA Assignee:
13.5.0
Verified
Version/s:
Description
When configuring the JDBC Audit Event Handler and logging out to the console, the following log is recorded.
org.forgerock.audit.handlers.jdbc.BufferedJdbcAuditEventExecutor:02/05/2016 05:09:49:209 P
1,5,main]: TransactionId[4099b763-9c93-4a31-8a01-6883289e056b-177]
ERROR: Unable to create event in the queue
java.sql.SQLException: No value specified for parameter 13
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1073)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:987)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:982)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:927)
at com.mysql.jdbc.PreparedStatement.checkAllParametersSet(PreparedStatement.java:2
at com.mysql.jdbc.PreparedStatement.addBatch(PreparedStatement.java:1013)
at com.zaxxer.hikari.proxy.HikariPreparedStatementProxy.addBatch(HikariPreparedSta
at
org.forgerock.audit.handlers.jdbc.BufferedJdbcAuditEventExecutor$DatabaseWriterTask.run(Bu
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
org.forgerock.audit.handlers.jdbc.BufferedJdbcAuditEventExecutor:02/05/2016 05:09:49:214 P
1,5,main]: TransactionId[4099b763-9c93-4a31-8a01-6883289e056b-177]
ERROR: Unable to create event in the queue
java.sql.SQLException: No value specified for parameter 16
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1073)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:987)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:982)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:927)
at com.mysql.jdbc.PreparedStatement.checkAllParametersSet(PreparedStatement.java:2
at com.mysql.jdbc.PreparedStatement.addBatch(PreparedStatement.java:1013)
at com.zaxxer.hikari.proxy.HikariPreparedStatementProxy.addBatch(HikariPreparedSta
at
org.forgerock.audit.handlers.jdbc.BufferedJdbcAuditEventExecutor$DatabaseWriterTask.run(Bu
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Comments
Comment by kohei [ 09/Feb/16 ]
The cause may be the same as .
Comment by kohei [ 26/Feb/16 ]
This is a bug of BufferedJdbcAuditEventExecutor in forgerock-audit-handler-jdbc-4.1.1.jar
Comment by kohei [ 27/Feb/16 ]
This issue is caused by and fixed by using forgerock-audit-handler-jdbc-4.4.0.jar.
Comment by Peter Major [ 14/Mar/16 ]
Considering that forgerock-audit master is on 4.3.1-SNAPSHOT and the fact that there was no
CAUD release yet AFAIK with the fix included, nor was OpenAM updated to use a fixed
version of the library: this is not yet fixed (and certainly not fixed for 13.5.0).
Craig McDonnell are there any release plans for CAUD?
Comment by Craig McDonnell [ 14/Mar/16 ]
There aren't any immediate plans to perform another Commons release. Unfortunately, we just
missed the last commons release that happened last week. At the moment they're happening as
needed. I think it's safe to assume that another commons release will happen before OpenAM
13.5 though so I can't see that the fix won't be brought in. Is there any urgency for commons to
be re-released so that this fix is available? Do you need to produce a patch fix or is the plan for
this to go into OpenAM 13.5?
Releasing commons is not without effort so if there's no urgency then I'd prefer to let this wait.
Is that ok for you?
Comment by Andy Cory [ 14/Mar/16 ]
Hi Craig
We're implementing a project for Standard Life building on top of existing FR components. The
new project has just started and is in design at the moment, but it will be moving to dev/test
within the next couple of weeks. We are building with OpenAM 13, and the customer has a
requirement for audit logging to an Oracle DB. We are pushing them to go down the route of
CAUD rather than the legacy logging they are using at present (OAM12), and would like to be
able to make use of a patch if at all possible. This is all related to
https://support.forgerock.com/requests/11214.
Andy
Comment by Peter Major [ 14/Mar/16 ]
Craig McDonnell no need for a CAUD release just yet. I suppose this could mean that we need
to keep this issue open a bit longer until we can depend on a version with the fix included
(assuming we can't depend on SNAPSHOT versions).
Andy Cory if you need a patch, raise a support case, and you should get one. No need to have a
release for that.
Comment by Andy Cory [ 14/Mar/16 ]
Thanks Peter, I'll do that, a patch is fine.
Comment by Jonathan Scudder [ 11/May/16 ]
Commons release has been updated in the master pom today. Should address this issue.
Comment by Peter Major [ 19/May/16 ]
Part of 13.5.0 (and consequently 14.0.0) builds now.
Comment by Filip Kubáň [ 15/Jun/16 ]
verified fix on OpenAM 13.5.0-RC4 Build 3ab00bf836 (2016-June-10 13:50)
Generated at Thu May 11 02:43:34 BST 2017 using JIRA 7.2.2#72004sha1:9d5132893cc8c728a3601a9034a1f8547ef5c7be.