You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by Denis Signoretto <de...@intesys.it> on 2014/06/19 16:53:18 UTC
It's possible add info about user/role/membership creation failure
in Execution messages?
Hi,
I'm doing some test with Syncope 1.1.7.
I'm trying to sync users from AD Connector. During sync there are some entries that generate an exception,
due to a correct unique attribute violation. (e.g. two users that has the same Full Name mapped on a schema attribute defined as unique)
In Syncope Execution messages I get a message like this one:
Users failed to create: CREATE FAILURE (id/name): null/null with message: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred.; nested exception is <openjpa-2.2.2-r422266:1468616 fatal store error> org.apache.openjpa.persistence.EntityExistsException: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred.
FailedObject: org.apache.syncope.core.persistence.beans.user.UAttrUniqueValue@52ded8f8
The only way I have found to understand which entries are generating this error it's to open the core.log file
where I can find the useful info about which user generated this exception (a00001in my case)
16:45:40.209 ERROR org.apache.syncope.core.sync.impl.SyncopeSyncResultHandler - Could not create USER a00001
org.springframework.dao.DataIntegrityViolationException: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred.; nested exception is <openjpa-2.2.2-r
422266:1468616 fatal store error> org.apache.openjpa.persistence.EntityExistsException: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred.
FailedObject: org.apache.syncope.core.persistence.beans.user.UAttrUniqueValue@52ded8f8
at org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:313)...
Is there another way (for a Syncope administrator) to know such info?
Do you think it's possible/useful add such information in Execution messages ?
Thanks.
Best regards,
Denis.
R: It's possible add info about user/role/membership creation
failure in Execution messages?
Posted by Denis Signoretto <de...@intesys.it>.
Hi Fabio,
Yes, I've just opened related improvement issue [1].
Regards,
Denis.
[1] https://issues.apache.org/jira/browse/ SYNCOPE-511
-----Messaggio originale-----
Da: Fabio Martelli [mailto:fabio.martelli@gmail.com]
Inviato: giovedì 19 giugno 2014 17:02
A: dev@syncope.apache.org
Oggetto: Re: It's possible add info about user/role/membership creation failure in Execution messages?
Il 19/06/2014 16:53, Denis Signoretto ha scritto:
> Hi,
>
> I'm doing some test with Syncope 1.1.7.
> I'm trying to sync users from AD Connector. During sync there are some
> entries that generate an exception, due to a correct unique attribute
> violation. (e.g. two users that has the same Full Name mapped on a
> schema attribute defined as unique)
>
> In Syncope Execution messages I get a message like this one:
>
> Users failed to create: CREATE FAILURE (id/name): null/null with message: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred.; nested exception is <openjpa-2.2.2-r422266:1468616 fatal store error> org.apache.openjpa.persistence.EntityExistsException: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred.
> FailedObject:
> org.apache.syncope.core.persistence.beans.user.UAttrUniqueValue@52ded8
> f8
>
> The only way I have found to understand which entries are generating
> this error it's to open the core.log file where I can find the useful
> info about which user generated this exception (a00001in my case)
>
> 16:45:40.209 ERROR
> org.apache.syncope.core.sync.impl.SyncopeSyncResultHandler - Could not
> create USER a00001
> org.springframework.dao.DataIntegrityViolationException: The
> transaction has been rolled back. See the nested exceptions for
> details on the errors that occurred.; nested exception is
> <openjpa-2.2.2-r
> 422266:1468616 fatal store error> org.apache.openjpa.persistence.EntityExistsException: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred.
> FailedObject: org.apache.syncope.core.persistence.beans.user.UAttrUniqueValue@52ded8f8
> at org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:313)...
>
> Is there another way (for a Syncope administrator) to know such info?
> Do you think it's possible/useful add such information in Execution messages ?
Ciao Denis,
you are right. It should be improved: can you open a new issue please?
Best regards,
F.
>
> Thanks.
>
> Best regards,
> Denis.
>
--
Fabio Martelli
Tirasa - Open Source Excellence
http://www.tirasa.net/
Apache Syncope PMC
http://people.apache.org/~fmartelli/
Re: It's possible add info about user/role/membership creation failure
in Execution messages?
Posted by Fabio Martelli <fa...@gmail.com>.
Il 19/06/2014 16:53, Denis Signoretto ha scritto:
> Hi,
>
> I'm doing some test with Syncope 1.1.7.
> I'm trying to sync users from AD Connector. During sync there are some entries that generate an exception,
> due to a correct unique attribute violation. (e.g. two users that has the same Full Name mapped on a schema attribute defined as unique)
>
> In Syncope Execution messages I get a message like this one:
>
> Users failed to create: CREATE FAILURE (id/name): null/null with message: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred.; nested exception is <openjpa-2.2.2-r422266:1468616 fatal store error> org.apache.openjpa.persistence.EntityExistsException: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred.
> FailedObject: org.apache.syncope.core.persistence.beans.user.UAttrUniqueValue@52ded8f8
>
> The only way I have found to understand which entries are generating this error it's to open the core.log file
> where I can find the useful info about which user generated this exception (a00001in my case)
>
> 16:45:40.209 ERROR org.apache.syncope.core.sync.impl.SyncopeSyncResultHandler - Could not create USER a00001
> org.springframework.dao.DataIntegrityViolationException: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred.; nested exception is <openjpa-2.2.2-r
> 422266:1468616 fatal store error> org.apache.openjpa.persistence.EntityExistsException: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred.
> FailedObject: org.apache.syncope.core.persistence.beans.user.UAttrUniqueValue@52ded8f8
> at org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:313)...
>
> Is there another way (for a Syncope administrator) to know such info?
> Do you think it's possible/useful add such information in Execution messages ?
Ciao Denis,
you are right. It should be improved: can you open a new issue please?
Best regards,
F.
>
> Thanks.
>
> Best regards,
> Denis.
>
--
Fabio Martelli
Tirasa - Open Source Excellence
http://www.tirasa.net/
Apache Syncope PMC
http://people.apache.org/~fmartelli/