When using the JDBC Driver Wrapper, passing a null to a setX method of PreparedStatement throws NullPointerException.
FusionReactor's JDBC driver expects passed binding values to be non-null. The expected method of setting null for a given parameter is the setNull(...) method, however the JDBC API does not specifically prohibit null as a binding value being passed directly to the setX methods of PreparedStatement. Internally, the wrapper does some marshaling of this value in order to log it and display it in FusionReactor, and this operation was not null-guarded.
We confirm this to be a bug in the JDBC Driver Wrapper shipped up to FusionReactor 3.5.5.
Customers with FusionReactor 3.5.5
Customers with FusionReactor 3.5.5 only installed should apply the attached Hotfix 2069, which resolves this issue.
Instructions for applying the hotfix are supplied in instructions.txt within the hotfix zip file.
Hotfixes are cumulative: any future hotfixes on the FusionReactor 3.5.5 stream, up to but not including the next point release, will contain this hotfix (and all earlier hotfixes since the last point release).
Customers with prior versions (< 3.5.5)
Customers with versions earlier than FusionReactor 3.5.5 should update to that version using the published installer/updater prior to applying this hotfix.
After installation, FusionReactor's "About" page should identify itself as *"
Revision: 3.5.5, Build: FusionReactor 3.5.x Maintenance Branch.17.19877"*
|Last Updated:||02/Mar/11 2:27 PM|
|Server:||ColdFusion 6, ColdFusion 7, ColdFusion 8, ColdFusion 9, Flex Data Services, JBoss, Jetty, JRun 4, LiveCycle Data Services, Railo, Resin, ServletExec, Tomcat, WebSphere, WebLogic|
|Platform:||Windows XP, Windows 2000, Windows 2003, Linux, MacOS, Solaris, Windows Vista, Windows x64, AIX, Windows 7, Windows 2008|
Comments are closed.