[jboss-jira] [JBoss JIRA] Closed: (JBAS-4278) Timers: PreparedStatement.setNull() should be used for null arguments
Alexey Loubyansky (JIRA)
jira-events at lists.jboss.org
Sat Mar 31 16:01:19 EDT 2007
[ http://jira.jboss.com/jira/browse/JBAS-4278?page=all ]
Alexey Loubyansky closed JBAS-4278.
-----------------------------------
Fix Version/s: JBossAS-5.0.0.Beta2
JBossAS-4.2.0.GA
JBossAS-4.0.5.SP1
Resolution: Done
Fixed.
> Timers: PreparedStatement.setNull() should be used for null arguments
> ---------------------------------------------------------------------
>
> Key: JBAS-4278
> URL: http://jira.jboss.com/jira/browse/JBAS-4278
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: EJB2
> Affects Versions: JBossAS-4.2.0.CR1, JBossAS-5.0.0.Beta1, JBossAS-4.0.5.GA
> Reporter: Alexey Loubyansky
> Assigned To: Alexey Loubyansky
> Fix For: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.GA, JBossAS-4.0.5.SP1
>
>
> When a timer is inserted into the database PreparedStatement.setBytes(i, bytes) is called despite the bytes sometimes may be null. This doesn't work for all databases.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list