A managed transaction is causing the site import can fail (at around 94%) due to a bad user, even though the error may be recoverable.

As the site import is completing, the post import stack begins to run. The UserPostImportTask is attempting to set properties on users to be added to the system. If a erroneous user exists in the import, this process can throw a NullPointerException (which will cause the transaction to be set to rollback only), and the import in process to fail.

It appears the code in UserPostImportTask.createUserPersonalInformation does not expect the transaction to roll back, as the exception is swallowed and waned to the logs.

In this case we should modify DefaultPersonalInformationManager to not cause the NPE, rather than configure the transactionInterceptor to not abort on this exception.