topic Re: rule executed in abckground does not work in Alfresco Archive

rule executed in abckground does not work

gandrez — Mon, 07 May 2007 14:10:53 GMT

Hi all!There seems to be a problem with executing rules in background. In my use case I'm copying several documents in a transaction to a space and an inbound rule in that space which is adding custom aspects to all copies. But when the rule is executed, aspects are added to some documents, but not

Re: rule executed in abckground does not work

andy — Mon, 14 May 2007 08:17:17 GMT

Hi

This looks like a bug to me.
Do you always see this type of error?

Could you raise a JIRA issue.

Cheers

Andy

Re: rule executed in abckground does not work

gandrez — Mon, 14 May 2007 12:26:26 GMT

Hello Andy

I have raised an issue as you suggested at

http://issues.alfresco.com/browse/AR-1456

Yes, the exception is thrown every time I access a document which has this aspect applied. I've also noticed a pattern. It gets thrown on a 1 minute basis. If I access any number of documents with this aspect applied in a time frame before the next time this (I think) job scheduler checks, a single exception is thrown. If I don't access any document within the next 60 seconds, the exception is not thrown. Of course when I access a document again at any point after that, everything repeats.

Regards,

Dragan

Re: rule executed in abckground does not work

gandrez — Tue, 15 May 2007 08:18:25 GMT

Hello Andy!

A small update:

So far I've been using Alfresco 2.0 CE with Tomcat bundle and HSQL.

After I deployed the application to a stand-alone Tomcat server and switched to MySQL the exceptions do not appear anymore.

Best regards,

Dragan

Re: rule executed in abckground does not work

tpasturel — Wed, 04 Jul 2007 07:46:39 GMT

Hi,

I have the same problem. A custom aspect is applied to each document. When a document is read or updated the same error is thrown.

There is no correlation with a backgroung executing rule.

The problem is linked with custom apect behaviours.

Since the bug appeared, a new message is sometimes written in the output console :

### Excluding compile:  org.apache.lucene.index.IndexReader$1::doBody‍

Re: rule executed in abckground does not work

andy — Fri, 06 Jul 2007 16:34:53 GMT

Hi

The issue is the indexer is reading content while doing background indexing - if this index changes attributes - it will need to reindex. The fix will be to reindex without binding the onReadContent policy. The fix is not in yet.

However, whatever you are trying to do is probably flawed. I would guess you want to count access or audit access.

In the first case caching/or not makes the numbers pretty pointless. Also, the windows CIFS client opens files threee times for a read and access to properties will open the content many times.

If it is for audit - then getting the content means nothing with regard to proving someone has read it …or that someone else has not read it - for I have email, a printer, …..

So I have to ask, what are you trying to do?

Andy

Re: rule executed in abckground does not work

tpasturel — Mon, 09 Jul 2007 08:41:17 GMT

Hi,

   there are two aspects applied to each document. One for metadatas and the second is the ContentHitsAspect sample from the sdk.

   For us, the purpose of the contenhits aspect is to have an audit of the content access by users (onReadContent). Not to have the exact number of content readings but to compare the different spaces success.
   The onUpdateContent behaviour has been deleted because it was called on each reading.

   CIFS is deactivated.

   The bug disappeared once on a tomcat reboot without source changes (only a larger jvm memory), and the next reboot reappeared.

   The documents are well indexed, but the big problem with that bug is that the memory is not well deallocated and the jvm heap oversizes in one day of using (1.5 GB alllocated).

Regards,
                           Thomas

Re: rule executed in abckground does not work

tpasturel — Wed, 18 Jul 2007 14:00:42 GMT

The problem was on the contenthits aspect.

During the onReadContent, not only onUpdateContent behaviour from the contenthits class should be deactivated, but also AuditableAspect update behaviour ! Indeed, the update of a document property also calls auditableaspect update behaviour.

Re: rule executed in abckground does not work

tpasturel — Mon, 01 Oct 2007 09:26:37 GMT

I'm using custom aspect similar to ContentHits that is updating a document every time the document is viewed. After a certain time Alfresco keeps throwing the following exception…

Auditable Aspect onUpdateNode behaviour deactivation is not sufficient because setProperty implementation constraints the call of the behaviour call :

DBNodeServiceImpl v2.0

  public void setProperty(NodeRef nodeRef, QName qname, Serializable value) throws InvalidNodeRefException
    {
        Assert.notNull(qname);
        
        // Invoke policy behaviours
      invokeBeforeUpdateNode(nodeRef);
      
        […]

      // Invoke policy behaviours
      invokeOnUpdateNode(nodeRef);
        invokeOnUpdateProperties(nodeRef, propertiesBefore, propertiesAfter);
    }‍‍‍‍‍‍‍‍‍‍‍‍‍