Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
2 replies Latest Post - ‏2012-10-23T10:18:37Z by SystemAdmin
rajnishydv
rajnishydv
1 Post
ACCEPTED ANSWER

Pinned topic ERROR Failed dispatching QueueItem row

‏2012-05-07T09:26:47Z |
Hi Experts,

I have designed a workflow that can launch from the process designer without any problem manually, i have also created workflow subscription(on creation event) for that but it can not launch workflow when i add a document related to class.
My CE and PE On same system and http://192.168.1.81:32776/IOR/FileNet.PE.vworbbroker also gives correct outout.

I am stuck in resolving this issue from from last few days but still not succeeded, please look into it and help me out to resolve this issue..SystemOut.log is below.

Thanks in advance.

P8 Content Engine Version: 5.1.0 Build: dap501.153 on WIN-AWQFAFP0MII
All times are GMT; local time zone is Pacific Standard Time
VirtualServer: WIN-AWQFAFP0MIINode01 ServerInstance: server1
Date (GMT) Thread Sub Category Sev Message
2012-05-04T12:28:24.862Z 1D221D22 CBR FNRCE0000I - INFO Found CSE.properties file:/C:/Program Files/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/WIN-AWQFAFP0MIINode01Cell/FileNetEngine.ear/APP-INF/lib/engine-cbr-spi-impl.jar!/CSE.properties
2012-05-04T12:28:25.162Z 1D221D22 ENG FNRCE0000I - INFO Server startup completed
2012-05-04T12:28:26.598Z 05C205C2 CSTG FNRCE0000I - INFO TTLStreamReaper task has started.
2012-05-04T12:28:26.860Z 0A0C0A0C CFSI FNRCE0000I - INFO CFSImportAgent:p8domain serial=3 is enabled
2012-05-04T12:28:27.286Z 0C550C55 CBR FNRCE0000I - INFO CBRDispatcher$FailOver:p8domain serial=5 is enabled
2012-05-04T12:28:27.287Z 0C550C55 CBR FNRCE0000I - INFO Starting CBRDispatcher.FailOver task
2012-05-04T12:28:27.539Z 05C205C2 SEC FNRCE0000I - INFO Start resolving LDAP URL list for host=http://192.168.1.81, port=389
2012-05-04T12:28:27.556Z 05C205C2 SEC FNRCE0000I - INFO Host value http://192.168.1.81 is interpreted as a single host, becasue it resolves to a singe IP address http://192.168.1.81.
2012-05-04T12:28:27.556Z 05C205C2 SEC FNRCE0000I - INFO Final LDAP URL used for connection: ldap://192.168.1.81:389
2012-05-04T12:28:27.574Z 0F170F17 CBR FNRCE0000I - INFO Using temp directory for CSS:C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\FileNet\server1\CSSTemp
2012-05-04T12:28:27.589Z 0F170F17 CBR FNRCE0000I - INFO Unable to initialize INSO filter because it is not configured correctly. This is only a problem if the IBM Text search component will be used
2012-05-04T12:28:27.651Z 05C205C2 SEC FNRCE0000I - INFO Start resolving LDAP URL list for host=http://192.168.1.81, port=3268
2012-05-04T12:28:27.652Z 05C205C2 SEC FNRCE0000I - INFO Host value http://192.168.1.81 is interpreted as a single host, becasue it resolves to a singe IP address http://192.168.1.81.
2012-05-04T12:28:27.652Z 05C205C2 SEC FNRCE0000I - INFO Final LDAP URL used for connection: ldap://192.168.1.81:3268
2012-05-04T12:28:27.684Z 05C205C2 SEC FNRCE0000I - INFO Connected to GC on current host: 192.168.1.81
2012-05-04T12:28:28.653Z 0F170F17 CBR FNRCE0000W - WARN binary path is null, maybe the deployment hasn't finished or something else is wrong
2012-05-04T12:28:28.675Z 0F170F17 CBR FNRCE0000I - INFO binary_recognizer_config.xml located in the default location
2012-05-04T12:28:29.131Z 0F170F17 CBR FNRCE0000W - WARN binary path is null, maybe the deployment hasn't finished or something else is wrong
2012-05-04T12:28:29.144Z 0F170F17 CBR FNRCE0000I - INFO css_mime_actions_config.xml located in the default location
2012-05-04T12:28:31.279Z 05C205C2 ENG FNRCE0000I - INFO Pre-load inuse memory = 75832K
2012-05-04T12:28:33.216Z 05C205C2 ENG FNRCE0000I - INFO After loading metadata for object store #1: 'FilenetObjectStore' inuse memory = 121150K without explicit GC
2012-05-04T12:28:33.227Z 05C205C2 CSTG FNRCE0000I - INFO ContentQueueDispatcher starting :
2012-05-04T12:28:33.234Z 0F170F17 ASYN FNRCE0000I - INFO QueueItemDispatcher:FilenetObjectStore serial=10 is enabled
2012-05-04T12:28:33.234Z 0F170F17 ASYN FNRCE0000I - INFO QueueItemDispatcher: FilenetObjectStore: Starting queue dispatching.
2012-05-04T12:28:33.236Z 0C550C55 PUBL FNRCE0000I - INFO PublishRequestDispatcher:FilenetObjectStore serial=11 is enabled
2012-05-04T12:28:33.236Z 0C550C55 PUBL FNRCE0000I - INFO PublishRequestDispatcher: FilenetObjectStore: Starting queue dispatching.
2012-05-04T12:28:33.245Z 05C205C2 REPL FNRCE0000I - INFO InboundReplicationDispatcher starting :
2012-05-04T12:28:33.245Z 0A0C0A0C REPL FNRCE0000I - INFO InboundReplicationDispatcher:FilenetObjectStore serial=13 is enabled
2012-05-04T12:28:33.248Z 05C205C2 REPL FNRCE0000I - INFO OutboundReplicationDispatcher starting :
2012-05-04T12:28:33.257Z 0DCA0DCA REPL FNRCE0000I - INFO OutboundReplicationDispatcher:FilenetObjectStore serial=14 is enabled
2012-05-04T12:28:33.259Z 71F871F8 CSTG FNRCE0000I - INFO ContentQueueDispatcher:FilenetObjectStore serial=9 is enabled
2012-05-04T12:28:33.323Z 71F871F8 CSTG FNRCE0000I - INFO ContentQueueDispatcher {28C132A6-1F93-4A63-9E82-8A420C5AEB0F} Session Id={225FB4D4-568D-4BA0-8475-F22036AEF2EA}
2012-05-04T12:31:38.856Z 706B706B ASYN FNRCV0006E - ERROR Failed dispatching QueueItem row {230D4E90-9EAF-4B95-91F8-FF7D963B271B}
com.filenet.api.exception.EngineRuntimeException: FNRCV0006E: EVENT_HANDLER_THREW: An exception occurred in the event handler.
at filenet.pe.ce.wfeventhandler.WorkflowEventActionHandler.onEvent(WorkflowEventActionHandler.java:240)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
at com.filenet.engine.queueitem.SubscriptionProcessor.executeHandler(SubscriptionProcessor.java:1110)
at com.filenet.engine.queueitem.SubscriptionProcessor.execute(SubscriptionProcessor.java:902)
at com.filenet.engine.queueitem.EventQueueItemHandler.execute(EventQueueItemHandler.java:94)
at com.filenet.engine.queueitem.EventQueueItemHandler$1.run(EventQueueItemHandler.java:60)
at com.filenet.engine.context.CallState.doAs(CallState.java:218)
at com.filenet.engine.context.CallState.doAs(CallState.java:135)
at com.filenet.engine.queueitem.EventQueueItemHandler.executeAs(EventQueueItemHandler.java:51)
at com.filenet.engine.queueitem.QueueItemExecutor.loadAndExecuteQueuedRow(QueueItemExecutor.java:162)
at com.filenet.engine.queueitem.QueueExecutor.dispatchQueuedRow(QueueExecutor.java:375)
at com.filenet.engine.queueitem.QueueExecutor.dispatchEvent(QueueExecutor.java:210)
at com.filenet.engine.queueitem.QueueExecutor.execute(QueueExecutor.java:136)
at com.filenet.engine.tasks.BackgroundTask.safeExecute(BackgroundTask.java:239)
at com.filenet.engine.tasks.BackgroundTask$BackgroundTaskPriviledgedExceptionAction.run(BackgroundTask.java:1017)
at com.filenet.engine.context.CallState.doAsSystem(CallState.java:416)
at com.filenet.engine.tasks.BackgroundTask.run(BackgroundTask.java:195)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:896)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:735)
Caused by: Failed to connect to vworbbroker on 192.168.1.81:32776[1]. Check server connection.
filenet.pe.peorb.client.ORBServiceHelper$VWORBBrokerNotStarted: Failed to retrieve an IOR for vworbbroker. URL=http://192.168.1.81:32776/IOR/FileNet.PE.vworbbroker. Check PE server to make sure that vworbbroker process is started.
at filenet.pe.peorb.client.ORBSession.getPERPCService(ORBSession.java:692)
at filenet.pe.peorb.client.ORBSession.establishORBSession(ORBSession.java:585)
at filenet.pe.peorb.client.ORBSession.<init>(ORBSession.java:818)
at filenet.vw.server.PECommandsFactory.getPECommandsFromURL(PECommandsFactory.java:158)
at filenet.vw.api.VWSession.logon(VWSession.java:751)
at filenet.vw.api.VWSession.<init>(VWSession.java:588)
at filenet.pe.ce.wfeventhandler.WorkflowEventActionHandler.getVWSession(WorkflowEventActionHandler.java:963)
at filenet.pe.ce.wfeventhandler.WorkflowEventActionHandler.launchWorkflow(WorkflowEventActionHandler.java:782)
at filenet.pe.ce.wfeventhandler.WorkflowEventActionHandler.onEvent(WorkflowEventActionHandler.java:228)
... 22 more
Caused by: filenet.pe.peorb.client.ORBServiceHelper$VWORBBrokerNotStarted: Failed to retrieve an IOR for vworbbroker. URL=http://192.168.1.81:32776/IOR/FileNet.PE.vworbbroker. Check PE server to make sure that vworbbroker process is started.
at filenet.pe.peorb.client.ORBServiceHelper.getPERPCIOR(ORBServiceHelper.java:855)
at filenet.pe.peorb.client.ORBServiceHelper.getPERPC(ORBServiceHelper.java:624)
at filenet.pe.peorb.client.ORBSession.getPERPCService(ORBSession.java:688)
... 30 more
2012-05-04T12:31:38.885Z 706B706B ASYN FNRCE0000W - WARN Transaction timed out while executing queue item: {230D4E90-9EAF-4B95-91F8-FF7D963B271B}. Execution time: 184 seconds.
2012-05-04T12:31:38.891Z 706B706B ASYN FNRCE0000I - INFO dispatchFailed: Ignoring queue item: {230D4E90-9EAF-4B95-91F8-FF7D963B271B} for 960 seconds.
2012-05-04T12:31:38.926Z 0F170F17 ASYN FNRCE0000I - INFO QueueItemDispatcher: FilenetObjectStore: next retry date is: 2012-05-04 05:47:38.903. current date is: 2012-05-04 05:31:38.923
2012-05-04T12:32:26.407Z 0F170F17 ASYN FNRCE0000I - INFO QueueItemDispatcher: FilenetObjectStore: next retry date is: 2012-05-04 05:47:38.903. current date is: 2012-05-04 05:32:26.403
Updated on 2012-10-23T10:18:37Z at 2012-10-23T10:18:37Z by SystemAdmin
  • drdamour
    drdamour
    40 Posts
    ACCEPTED ANSWER

    Re: ERROR Failed dispatching QueueItem row

    ‏2012-05-07T18:32:24Z  in response to rajnishydv
    Your CE server can't communicate with your PE Server. It's looking for it at 192.168.1.81:32776. Since it appears you are running a singlebox install, are you sure your CE has the correct version of the PE client?

    I am Just a new Boy,
    A Stranger in this Town,
    Where are All the Good Times,
    Who's Gonna Show this Stranger Around?
    Check out our Agile ACM Catalogue: Widgets, APIs, & Components for Building Solutions
    • SystemAdmin
      SystemAdmin
      693 Posts
      ACCEPTED ANSWER

      Re: ERROR Failed dispatching QueueItem row

      ‏2012-10-23T10:18:37Z  in response to drdamour
      Is the problem resolved?

      I had similar problem, but clearing caching resolved in my case.