Re: [Hypercontent-users] Is this a bug , workflow takes time to load
Brought to you by:
alexvigdor
From: Alex V. <al...@bi...> - 2007-02-28 01:52:26
|
On Feb 27, 2007, at 5:33 PM, tom tom wrote: > Alex, > I will try it out and let you know, > > Well...Eventually when this (HC) goes to production > this will be used by the Authors, Hence there is > always a possibility this can happen, I suggest you deny your authors permission to read or write any files under /config, e.g. <permission activity="read" denied="true" principal="group:authors" target="/config/**/*.*"/> <permission activity="read" denied="true" principal="group:authors" target="/config/**/"/> > > Due to these reasons cant we do the following > > 1) Have a timeout and release the resources so that > users will not get this error all the time. Or as part > of the restart clear the locks. There is currently a 4 hour lock timeout and a 15 second lock wait time hard coded. If you'd like to see those moved to a properties file, or a facility for scheduling workflow tasks for startup, please submit jira issues. https://clearinghouse.ja-sig.org/issues/browse/HYP > > > 2) Delete unnecessary workflow data triggered by a > schedular > > 3) Mechanism to delete the history data which we can > see in the workflow screen In order to delete work data from the repository (and therefore on screen), you must remove it from any queues it is in. You can do this on a schedule. For example, in approvals.xml <q id="archived"> <event name="scheduled-discard" when="in 2 hours"> <dq where="${path}"/> <dq who="${editor}"/> <dq/> </event> ... or in publish.xml <q id="published"> <event name="scheduled-discard" when="in 2 days"> <dq who="${publisher}"/> <dq/> </event> ... See this page for more scheduling info: http://hypercontent.sourceforge.net/help/project/workflow/ scheduling.html > > Question > > 1) When the system goes through many > Author->Preview->Approve/Reject ->Build>publish > > Cycles there may be many data collected as part of > each workflow, > > Will this data cause some performance issue specially > when loading the Workflow Screen,? If so what is the > mechanism to get rid of that. Yes, this can cause performance issues loading the workflow screen. The scheduled events above will address this. > > Basically I want to be prepared if such a thing > happens when this goes to production > > > Thanks > > > > > > > Let me know your thoughts on this. > > Thanks > > > > > > > > > > > --- Alex Vigdor <al...@bi...> wrote: > >> This is likely the cause of the delays you are >> seeing; the system >> must be able to acquire a lock on workflow scripts >> in order to >> initialize them, so you have to make sure that once >> you open a >> workflow script for edit, you save or discard your >> changes. If you >> leave the file open the system will time out trying >> to acquire the lock. >> >> After things have gotten weird with the workflow >> components, its also >> a good idea to restart the server. This won't clear >> the lock, >> however - you can manually remove that from the >> filesystem by looking >> for "/config/workflow/build.xml/file.lock". >> >> Cheers, >> Alex >> >> On Feb 27, 2007, at 12:33 AM, tom tom wrote: >> >>> I looked at the catalina.out and it gives an Error >> as >>> follows. >>> >>> What is the cause for this error. >>> >>> >>> Thanks >>> >>> <Unable to load workflow build> >>> 2007-02-27 16:29:14,781 ERROR >>> [org.hypercontent.util.Logger] - <> >>> org.hypercontent.HyperException: Store already >> engaged >>> in transaction @ >> /config/workflow/build.xml(exists? >>> true) >>> at >>> >> > org.hypercontent.data.impl.AbstractDataStore.beginTransaction >> >>> (AbstractDataStore.java:141) >>> at >>> >> > org.hypercontent.data.impl.AbstractDataStore.beginTransaction >> >>> (AbstractDataStore.java:84) >>> at >>> >> > org.hypercontent.data.impl.AbstractDataStore.beginTransaction >> >>> (AbstractDataStore.java:80) >>> at >>> >> > org.hypercontent.workflow.impl.WorkflowFactoryImpl.getWorkflow >> >>> (WorkflowFactoryImpl.java:137) >>> at >>> >> > org.hypercontent.workflow.impl.WorkflowFactoryImpl.getWorkList >> >>> (WorkflowFactoryImpl.java:284) >>> at >>> >> sun.reflect.NativeMethodAccessorImpl.invoke0(Native >>> Method) >>> at >>> sun.reflect.NativeMethodAccessorImpl.invoke >>> (NativeMethodAccessorImpl.java:39) >>> at >>> sun.reflect.DelegatingMethodAccessorImpl.invoke >>> (DelegatingMethodAccessorImpl.java:25) >>> at >>> java.lang.reflect.Method.invoke(Method.java:585) >>> at >>> >> org.apache.velocity.util.introspection.UberspectImpl >> >>> $VelMethodImpl.invoke(UberspectImpl.java:267) >>> at >>> >> > org.apache.velocity.runtime.parser.node.ASTMethod.execute >> >>> (ASTMethod.java:197) >>> at >>> >> > org.apache.velocity.runtime.parser.node.ASTReference.execute >> >>> (ASTReference.java:175) >>> at >>> >> > org.apache.velocity.runtime.parser.node.ASTReference.value >> >>> (ASTReference.java:327) >>> at >>> >> > org.apache.velocity.runtime.parser.node.ASTExpression.value >> >>> (ASTExpression.java:51) >>> at >>> >> > org.apache.velocity.runtime.parser.node.ASTSetDirective.render >> >>> (ASTSetDirective.java:95) >>> at >>> >> > org.apache.velocity.runtime.parser.node.ASTBlock.render >> >>> (ASTBlock.java:55) >>> >>> >>> >>> --- tom tom <j_l...@ya...> wrote: >>> >>>> We modifed the approvals.xml as follows >>>> >>>> 1) remove the event remain reminder as we do not >>>> require them >>>> >>>> 2) Increased the content of the Approval and >> Denied >>>> email messages >>>> >>>> Since the we observe that when we click the >> workflow >>>> link it takes ages to load the workflow interface >>>> and >>>> sometimes it comes with the following exception, >>>> >>>> Is this becase we increased the email body text. >>>> >>>> Should I remove the email body text? Is this >> causing >>>> the delay and the following exception. >>>> >>>> >>>> There was an error processing your request >>>> null >>>> >>>> >>>> >>> >> > org.hypercontent.workflow.impl.WorkflowImpl.getEventDescriptors >> >>> (WorkflowImpl.java:105) >>>> >>>> >>> >> > sun.reflect.GeneratedMethodAccessor143.invoke(Unknown >>>> Source) >>>> >>>> >>> sun.reflect.DelegatingMethodAccessorImpl.invoke >>> (DelegatingMethodAccessorImpl.java:25) >>>> >> java.lang.reflect.Method.invoke(Method.java:585) >>>> >>>> >>> >> org.apache.velocity.util.introspection.UberspectImpl >> >>> $VelMethodImpl.invoke(UberspectImpl.java:267) >>>> >>>> >>> >> > org.apache.velocity.runtime.parser.node.ASTMethod.execute >> >>> (ASTMethod.java:197) >>>> >>>> >>> >> > org.apache.velocity.runtime.parser.node.ASTReference.execute >> >>> (ASTReference.java:175) >>>> >>>> >>> >> > org.apache.velocity.runtime.parser.node.ASTReference.value >> >>> (ASTReference.java:327) >>>> >>>> >>> >> > org.apache.velocity.runtime.parser.node.ASTExpression.value >> >>> (ASTExpression.java:51) >>>> >>>> >>> >> > org.apache.velocity.runtime.parser.node.ASTSetDirective.render >> >>> (ASTSetDirective.java:95) >>>> >>>> >>> >> > org.apache.velocity.runtime.parser.node.ASTBlock.render >> >> > === message truncated === > > > > > ______________________________________________________________________ > ______________ > Expecting? Get great news right away with email Auto-Check. > Try the Yahoo! Mail Beta. > http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html > |