Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
1 reply Latest Post - ‏2011-07-08T19:49:52Z by SystemAdmin
SystemAdmin
SystemAdmin
9224 Posts
ACCEPTED ANSWER

Pinned topic Update record failed when nanos value of 'updated' is 999

‏2011-07-01T11:03:40Z |
NOTE: this thread was migrated from projectzero.org. Some content and formatting may have been lost in the move.


Originally posted by projectzero userid: bcliao - f=4&t=2325#p9419
HI,

We have encountered a problem when updating a db record whose nanos value of 'updated' is 999. The exception stacktrace is listed below for reference.
Please help, thanks!!

java.lang.IllegalArgumentException:nanos > 999999999 or < 0<br />
java.sql.Timestamp.setNanos (null:-1)
zero.resource.fields.DateTimeField.preSave (DateTimeField.java:126)
zero.resource.Collection.update (Collection.java:1183)
zero.resource.Type.update (Type.java:532)
sun.reflect.NativeMethodAccessorImpl.invoke0 (null:-2)
sun.reflect.NativeMethodAccessorImpl.invoke (null:-1)
sun.reflect.DelegatingMethodAccessorImpl.invoke (null:-1)
java.lang.reflect.Method.invoke (null:-1)
org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoCachedMethodSiteNoUnwrapNoCoerce.invoke (PojoMetaMethodSite.java:229)
org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call (PojoMetaMethodSite.java:52)
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall (CallSiteArray.java:40)
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call (AbstractCallSite.java:117)
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call (AbstractCallSite.java:125)
Updated on 2011-07-08T19:49:52Z at 2011-07-08T19:49:52Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    9224 Posts
    ACCEPTED ANSWER

    Re: Update record failed when nanos value of 'updated' is 999

    ‏2011-07-08T19:49:52Z  in response to SystemAdmin

    Originally posted by projectzero userid: jeffo - f=4&t=2325#p9427
    Which version/distro of sMash are you using? It looks like a problem that is fixed in our current Indy development stream. You could verify by using the Indy cli from http://www.projectzero.org/zero/indy/latest/download/