hi, Thanks for the right pointers.
We found that one of the attribute was incorrectly mapped to Date in the resource mapping. Synchronization is working fine now. Regards, Suresh On Wed, Oct 1, 2014 at 12:17 PM, Francesco Chicchiriccò <[email protected] > wrote: > Hi, > the relevant extract of the provided stacktrace is > > java.lang.NullPointerException > at java.util.Calendar.setTime(Calendar.java:1106) > at java.text.SimpleDateFormat.format(SimpleDateFormat.java:955) > at java.text.SimpleDateFormat.format(SimpleDateFormat.java:948) > at java.text.DateFormat.format(DateFormat.java:336) > at org.apache.syncope.core.util.DataFormat.format(DataFormat.java:65) > at org.apache.syncope.core.util.DataFormat.format(DataFormat.java:56) > at org.apache.syncope.core.util.DataFormat.format(DataFormat.java:52) > at > org.apache.syncope.core.persistence.beans.AbstractAttrValue.getValueAsString(AbstractAttrValue.java:243) > at > org.apache.syncope.core.connid.ConnObjectUtil.getSubjectTOFromConnObject(ConnObjectUtil.java:336) > > This seems to happen because one of elements in the resource mapping is > set as Date, but the provided conversion pattern is not adequate. > There should be, in fact, another error message saying something like as > ""While parsing provided value ..." > > The code in ConnObjectUtil around line 336 needs anyway to be made more > robust, but I would need some feedback from you about: > > 1. the actual value provided by the connector for this date attribute - > look in core-connid.log > 2. how the connector attribute is mapped in the related resource > 3. how the internal attribute date schema is defined (including > conversion pattern > > Thanks. > Regards. > > > On 01/10/2014 07:50, Suresh Ajja wrote: > > Attachment herewith. > On Oct 1, 2014 11:15 AM, "Suresh Ajja" <[email protected]> wrote: > >> I ticked the 'full reconciliation' and provided change column number with >> timestamp value in connector configuration. Getting null pointer exception >> now. >> >> PFA the error. >> >> - Suresh >> On Sep 30, 2014 11:47 AM, "Francesco Chicchiriccò" <[email protected]> >> wrote: >> >>> On 30/09/2014 07:20, Suresh Ajja wrote: >>> >>>> Hi, >>>> >>>> Created a synchronization task for an end application resource. >>>> While executing this task, it throws an error. Attached herewith is the >>>> error. >>>> >>> >>> The error says "Changelog column name configuration property is empty": >>> you are using the database table connector, whose configuration reference >>> [1] says >>> >>> The adapter also supports Active Sync to poll for account changes. To >>>> allow Active Sync capabilities, specify the changeLogColumn. >>>> >>> >>> What is happening then? You haven't configured the active >>> synchronization for this connector, but since the "Full reconciliation" >>> option of the synchronization task was not set, Syncope is querying the >>> connector for active synchronization. Then the error. >>> >>> This was working in Syncope 1.1.8 >>>> >>> >>> I don't think so, given what said above. >>> >>> Regards. >>> >>> Kindly provide us some fix. >>>> >>>> Thanks and Regards, >>>> Suresh >>>> >>> >>> [1] >>> https://connid.atlassian.net/wiki/display/BASE/Database+Table#DatabaseTable-Configuration >>> >> -- > Francesco Chicchiriccò > > Tirasa - Open Source Excellencehttp://www.tirasa.net/ > > Involved at The Apache Software Foundation: > member, Syncope PMC chair, Cocoon PMC, Olingo > PMChttp://people.apache.org/~ilgrosso/ > >
