Community Tip - You can change your system assigned username to something more personal in your community settings. X
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: wt.util.WTRuntimeException: "wt.doc.WTDocument>9205053" 物件不是持續的。; 巢狀例外:
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: (wt.fc.fcResource/7) wt.fc.ObjectNoLongerExistsException: "wt.doc.WTDocument>9205053" 物件不是持續的。
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at wt.vc.StandardVersionControlService.refresh(StandardVersionControlService.java:3015)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at sun.reflect.GeneratedMethodAccessor55.invoke(Unknown Source)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at java.lang.reflect.Method.invoke(Method.java:597)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at wt.services.ServiceFactory$ServerInvocationHandler.invoke(ServiceFactory.java:314)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at $Proxy29.refresh(Unknown Source)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at wt.fc.DefaultInflator$VfkCache.inflate(DefaultInflator.java:444)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at wt.fc.DefaultInflator$VfkCache.inflate(DefaultInflator.java:436)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at wt.fc.DefaultInflator$AbstractCache.get(DefaultInflator.java:291)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at wt.fc.DefaultInflator$AbstractCache.get(DefaultInflator.java:259)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at wt.fc.DefaultInflator.get(DefaultInflator.java:171)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at wt.vc.VersionReference.getObject(VersionReference.java:123)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at wt.workflow.engine.WfProcess.getName(WfProcess.java:1444)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at wt.workflow.engine.WfContainerReference.initialize(WfContainerReference.java:102)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at wt.workflow.engine.WfProcessReference.initialize(WfProcessReference.java:114)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at wt.workflow.engine.WfProcessReference.newWfProcessReference(WfProcessReference.java:99)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at sun.reflect.GeneratedMethodAccessor59.invoke(Unknown Source)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at java.lang.reflect.Method.invoke(Method.java:597)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at wt.fc.ReferenceResolver.getReference(ReferenceResolver.java:174)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at wt.fc.collections.ReferenceUtility.createReference(ReferenceUtility.java:123)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at wt.fc.collections.AbstractWTList.add(AbstractWTList.java:125)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at wt.fc.collections.AbstractWTList.add(AbstractWTList.java:62)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at wt.fc.collections.AbstractWTCollection.add(AbstractWTCollection.java:100)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at wt.events.summary.SummaryEventFactory.finishTransaction(SummaryEventFactory.java:274)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at wt.pom.TransactionManager.summaryEventFinishTransaction(TransactionManager.java:427)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at wt.pom.TransactionManager.commitTransaction(TransactionManager.java:386)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at wt.pom.BasicTransactionMonitor.commitTransaction(BasicTransactionMonitor.java:64)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at wt.pom.PersistentObjectManager.commitTransaction(PersistentObjectManager.java:424)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at wt.pom.Transaction.commit(Transaction.java:545)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at wt.queue.QueueRunnable.run(QueueRunnable.java:212)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
3/9/14 23:01:46: WfPropagationQueue.PoolQueueThread-3185: at java.lang.Thread.run(Thread.java:662)
Resently, these messages show in MethodServer over and over again, it produce many and large logs file, I couldn't find any solution.
Could anyone tell how to solve it?
Please check the queue entries inside WfPropagationQueue under Site-->Utilities-->Queue Administration. It may throw some more details.
Sometimes, after clearing tomcat instances & infoengine compiled task caches and then restarting method server may resolve the issue.
With Regards,
Suresh
I doubt clearing Tomcat instances or I*E compiled tasks will help at all here (most especially the former as there's no JSP involved here).
The underlying issue is clearly: wt.fc.ObjectNoLongerExistsException: "wt.doc.WTDocument>9205053...
So you're trying to operate on a document that no longer exists at this point. If so, then, yes, you'll tend to get a good deal of exceptions about that.
Dear Sureshbabu AD:
I have tried your suggestion, but it does not work...
I also clear all queue entries inside WfPropagationQueue which status is Failed or Servere, the problem still exist.
Dear Jess M Holle :
The problem is I have no idea what is operating the document...
I couldn't find and any useful information from MethodServer or Queue Manager