The process receives an XML document with 7000 Records or child elemts in it. It iterates through this document using
- Grabs one record at a time and formats the record into a SQL string.
- Opens a connection to Database (Microsft SQL Server).
- Start Transaction.
- Commit/Roll Back
- Close Connection
Repeat till there no more records in the file. I had used Microsoft JDBC Driver as well as the Data Direct JDBC Driver
The connection paramerters for database
Minimum Connections — 1
Maximum Connections — 20
Expiration Time (ms) — 120000
The Flow throws a NullPointerException the very first time after 26 min and then on every 20 min. I had switched on ‘watt.server.jdbcLogFile=jdbc.log’ to see jdbc logs and the Error occurs at execSQL, The SQL itself is valid, It mentions about database cursors being maxed out that in turn gets transalted as NullPointerException.
The way the process handles this situation is when ever there is a NullPointerException it backs off and retries the same record and that fixes the problem.
Is this a known problem ? I don’t see any traffic on this or
I am doing something fundamentally wrong or is there a back ground process that garbase collects a database object even though it is in use.
any thoughts/ resolutions ?