topic Please help ActionExecuter and catching ConstraintViolation in Alfresco Archive

Please help ActionExecuter and catching ConstraintViolation

alexr — Wed, 08 Oct 2008 05:38:55 GMT

On a Alfresco 2.2 Enterprise/MySQL installation, I have encountered two issues while developing a Alfresco Java application to import a large number of documents (several thousands).The import is started by an inbound content rule on an added csv-file (delimited data).One csv-file contains multiple

Re: Please help ActionExecuter and catching ConstraintViolation

alexr — Fri, 17 Oct 2008 07:40:12 GMT

Through Alfresco Support (ACT) I found out what transaction to use to make the commit work inside
the ActionExecuter type class:

I have implemented thetransactionService.getNonPropagatingUserTransaction(); for committing the transactions.
That works fine now.

The ConstraintViolation Exceptions still can not be caught (not even by Exception or Throwable), but we modified the ConsistencyChecker behaviour through:

custom-node-service-context.xml:

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE beans PUBLIC '-//SPRING//DTD BEAN//EN' 'http://www.springframework.org/dtd/spring-beans.dtd'>

<!– Beans pertinent to node persistence and services –>
<beans>

   <!– ensures model-compliance of node structures –>
   <bean id="integrityChecker" class="org.alfresco.repo.node.integrity. IntegrityChecker" init-method="init">
      <property name="policyComponent">
         <ref bean="policyComponent"/>
      </property>
      <property name="dictionaryService">
         <ref bean="dictionaryService" />
      </property>
      <property name="nodeService">
         <ref bean="nodeService" />
      </property>
      <property name="enabled">
         <value>true</value> <!– on/off switch –>
      </property>
      <property name="traceOn">
         <value>false</value> <!– use only to trace problems –>
      </property>
      <property name="failOnViolation" >
         <value>${integrity.failOnError}</value>
      </property>
      <property name="maxErrorsPerTransaction" >
         <value>100000</value> <!– limit output (exception and log) to the first N violation messages –>
      </property>
   </bean>

</beans>
—————————-
Changed the following setting in our application.properties:
integrity.failOnError=false
—————————-
Changed the loglevel in the log4j.properties to "WARN"

So now the ConstraintViolation exceptions still aren't caught. But the document with a constraint violation is still processed.
We have to check the alfresco.log after each "import" batch to see what noderef got a ConstraintViolation and these properties changed manually afterwards. Of course hopefully there aren't too many constraint violations during the process of these batches

Regards,

Alex

Re: Please help ActionExecuter and catching ConstraintViolation

lee — Mon, 22 Feb 2010 20:52:40 GMT

Has anyone found a solution to catching integrity violations in a transaction? I have a similar problem where a webscript performs some action on content (for example creating a node or updating the name of a node), however the script will NOT catch any integrity or constraint violations.

Simplest example is a script that creates a node with a name that has a "|" (a pipe char) in it. This will cause an integrity exception that appears in the logs, but the webscript is oblivious to it. I can't catch it either.

I've used this code similar to this:


try{
   props.put(ContentModel.PROP_NAME, "test|pipe");
   nodeService.createNode(parent, assocQName, nodeName, type, props);
}
catch (IntegrityException ie){
   log.error("FOUND INTEGRITY EXCEPTION " + ie);
}
catch(ConstraintException ce){
   log.error("FOUND CONSTRAINTEXCEPTION " + ce);
}
‍‍‍‍‍‍‍‍‍‍‍‍

Has anyone found a solution to this? I suspect it's because the integrity checker runs as a behaviour.. and therefore is outside of the code that can be caught by any try/catch statements.

However, there must be a solution to this, because the web client catches integrity violations during a save of a node. Any suggestions?

Thanks in advance for your help
Lee