Dears, 
It seems the Shark activity persistence has timeout 60 seconds. How can I implement process with complicated background processing with longer duration than 60 seconds? Where can be this timeout set? I need to change it to 300 seconds. 
The processing ends with error: 
A org.cmdbuild.workflow.CMWorkflowException occurred calling method class org.cmdbuild.servlets.json.Workflow.saveActivity: org.enhydra.shark.api.internal.instancepersistence.PersistenceException: Persisting of ActivityVariable failed
exactly after 60 seconds after save on manual activity during automated activity processing in the background. 
Than you very much for any ideas, I have tried all i can thing of.
Jiří
 
 
 
 
 
         
        
          
        
           
           
           
         
         
            
            
          
       
      
        
        
          Hello Jiří,
 
Some user in this forum facing same issue, but as far as I read in this forum, still no solution nor response from CMDBuild Team.
 
One solution you might want to try is by modify CMDBuild source code, you can find detail from Konstantin post in below thread.
 
 
Regards,
Herru Windiarto
 
 
Previously Jiří wrote:
Dears, 
It seems the Shark activity persistence has timeout 60 seconds. How can I implement process with complicated background processing with longer duration than 60 seconds? Where can be this timeout set? I need to change it to 300 seconds. 
The processing ends with error: 
A org.cmdbuild.workflow.CMWorkflowException occurred calling method class org.cmdbuild.servlets.json.Workflow.saveActivity: org.enhydra.shark.api.internal.instancepersistence.PersistenceException: Persisting of ActivityVariable failed
exactly after 60 seconds after save on manual activity during automated activity processing in the background. 
Than you very much for any ideas, I have tried all i can thing of.
Jiří
 
 
 
 
 
 
         
        
        
           
           
           
         
         
            
            
          
       
      
        
        
          Dear Jiří,
 
we had the same problem during one of our internal activities. We've looked for a solution and we must do some checks about it. If the solution will work then we'll include some kind of configuration for the timeout as soon as possible.
 
Best regards.
 
-- CMDBuild Team
 
Previously Jiří wrote:
Dears, 
It seems the Shark activity persistence has timeout 60 seconds. How can I implement process with complicated background processing with longer duration than 60 seconds? Where can be this timeout set? I need to change it to 300 seconds. 
The processing ends with error: 
A org.cmdbuild.workflow.CMWorkflowException occurred calling method class org.cmdbuild.servlets.json.Workflow.saveActivity: org.enhydra.shark.api.internal.instancepersistence.PersistenceException: Persisting of ActivityVariable failed
exactly after 60 seconds after save on manual activity during automated activity processing in the background. 
Than you very much for any ideas, I have tried all i can thing of.
Jiří