[midPoint] DB error starting midPoint 3.4

[Gustavo J Gallardo]

Hi Viliam,
it happened (twice) in our production environment, but eventually
dissapeared after a reboot.
We could not replicate the issue in our testing environment.

We are in the process to import the accounts (~450000) and provisioning to
3 resources (eDirectory LDAP, Google Apps and Office 365).
We are also checking if we need to do some additional tuning on the
PostgreSQL database.

I'll let you know if we can isolate anything.


Regards,

GJG

On Mon, Jul 18, 2016 at 8:18 AM, Viliam Repan <vilo.repan at evolveum.com>
wrote:

> Hi Gustavo,
>
> I've tried to run clean installation of midpoint 3.4 against postgresql
> 9.2 on ubuntu 14.04 and I can't replicate this behavior - does it happen
> after restart?.
> Do you have clean installation any other environment specific stuff?
> I've tested it on ubuntu 14.04 (64bit) with postgres 9.2.17, tomcat 8,
> oracle java 8
>
> *00000000-0000-0000-0000-000000000006* is validity task so I'm not sure
> what happened
>
> v
>
>
> On 17.07.2016 18:19, Gustavo J Gallardo wrote:
>
> Hi,
> we are running midPoint 3.4 with database PostgreSQL 9.2, and getting this
> error:
> *2016-07-17 13:00:49,887 [] [midPointScheduler_Worker-2] ERROR
> (org.hibernate.engine.jdbc.spi.SqlExceptionHelper): Batch entry 0 update
> m_object set booleansCount=0,
> createChannel='http://midpoint.evolveum.com/xml/ns/public/gui/channels-3#init
> <http://midpoint.evolveum.com/xml/ns/public/gui/channels-3#init>',
> createTimestamp='2016-06-02 17:23:48.969000 -03:00:00',
> creatorRef_relation=NULL, creatorRef_targetOid=NULL, creatorRef_type=NULL,
> datesCount=1, fullObject=?, longsCount=0, modifierRef_relation=NULL,
> modifierRef_targetOid=NULL, modifierRef_type=NULL, modifyChannel=NULL,
> modifyTimestamp=NULL, name_norm='validity scanner', name_orig='Validity
> Scanner', objectTypeClass='9', polysCount=0, referencesCount=0,
> stringsCount=0, tenantRef_relation=NULL, tenantRef_targetOid=NULL,
> tenantRef_type=NULL, version=13637 where
> oid='00000000-0000-0000-0000-000000000006' was aborted.  Call
> getNextException to see the cause.*
> *2016-07-17 13:00:49,887 [] [midPointScheduler_Worker-2] ERROR
> (org.hibernate.engine.jdbc.spi.SqlExceptionHelper): ERROR: could not
> serialize access due to read/write dependencies among transactions*
> *  Detail: Reason code: Canceled on identification as a pivot, during
> write.*
> *  Hint: The transaction might succeed if retried.*
> *2016-07-17 13:00:49,892 [] [midPointScheduler_Worker-2] ERROR
> (org.hibernate.engine.jdbc.batch.internal.BatchingBatch): HHH000315:
> Exception executing batch [could not execute batch]*
>
>
> Any ideas?
>
> Attached is complete idm.log trying to start the server.
>
> Thanks,
>
> GJG
>
>
> _______________________________________________
> midPoint mailing listmidPoint at lists.evolveum.comhttp://lists.evolveum.com/mailman/listinfo/midpoint
>
>
> --
> Ing. Viliam Repáň
> Evolveum, s.r.o.
>
> tel: +421 910 797978
> mail: vilo.repan at evolveum.com
>
>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> http://lists.evolveum.com/mailman/listinfo/midpoint
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20160720/dd58ccba/attachment.htm>