Workflow Agent issue

Hi ,
Recently we did clone, every thing looks fine in TEST server except workflow agent pointing to PROD servers,
[Sep 15, 2010 6:30:47 PM EDT]:1284589847305:Thread[outboundThreadGroup1,5,outboundThreadGroup]:0:-1:
XCEPTION:[fnd.wf.bes.PLSQLQueueHandler]:dequeue() :Dequeued the following BusinessEvent -> BusinessEvent{name=oracle.apps.wf.notification.send, key=8080299, priority=50, correlationId=null, sendDate=Fri Jul 09 18:16:16 EDT 2010, receiveDate=Wed Sep 15 18:30:47 EDT 2010, From Agent:Agent{agent=WF_NOTIFICATION_OUT, system=prod}, To Agent: , Last

Hi,
Recently we did clone, every thing looks fine in TEST server except workflow agent pointing to PROD servers, Please post the application release along with the database version and OS.
Have you completed all the Workflow setup changes on the cloned instance as per the Rapid Clone doc?
Also, please run the test as per (11i : Oracle Workflow Cartridge Workflow Java Mailer Setup Test [ID 274764.1]) and (Oracle Workflow ATG Support: R12 Java Mailer Setup Diagnostic Test [ID 748421.1]) and see if it returns any errors.
Thanks,
Hussein

Similar Messages

Workflow agent listener stopped with errors

Dear Gurus
We are having following errors in workflow mailer log files, all the workflow agent listeners are down.
:1:ERROR:[SVC-GSM-WFALSNRSVC-68525 : oracle.apps.fnd.cp.gsc.SvcComponentMonitor.process()]:Monitoring failed this iteration -> oracle.apps.fnd.cp.gsc.ProcessorException: Could no
t start automatic component -> oracle.apps.fnd.cp.gsc.server.GenericSvcComponentEOException: The Service Component Container is not running.
ANONYMOUS(0):-1:Thread[ComponentMonitor,5,main]:192.168.29.34:27454:1283539093063:1:ERROR:[SVC-GSM-WFWSSVC-68529 : oracle.apps.fnd.cp.gsc.SvcComponentMonitor.process()]:Monitoring failed this iteration -> oracle.apps.fnd.cp.gsc.ProcessorException: Could not retrieve list of Automatic components for this container -> oracle.apps.fnd.cp.gsc.server.GenericSvcComponentEOException: Failure to executeQuery() or read ResultSet. Query was: SELECT application_id, component_class_name, component_id, component_name, component_status, component_status_display_name, component_status_info, component_type, component_type_display_name, concurrent_queue_display_name, concurrent_queue_id, concurrent_queue_name, container_type, container_type_display_name, correlation_id, created_by, customization_level, inbound_agent_display_name, inbound_agent_name, max_idle_time, object_version_number, outbound_agent_display_name, outbound_agent_name, standalone_container_name, startup_mode, startup_mode_display_name FROM fnd_svc_components_v WHERE startup_mode = :1 AND (component_status = :2 OR component_status = :3 ) AND ( (container_type = :4 AND concurrent_queue_name = :5) ) -> java.sql.SQLRecoverableException: Io exception: Connection timed out
thanks for the help.
cheers

Pl post details of OS, EBS and database versions. Does bouncing all of the services help ? Any errors in the database alert log ? Is all other functionality available as normal ? Any changes made to the system recently ?
>
java.sql.SQLRecoverableException: Io exception: Connection timed out
>
This error points to either a connection issue or a code performance issue.
HTH
Srini

Workflow Agent Listener and Workflow Background program run after each minute

Hello,
We have scheduled Workflow agent listener program to be run after 5 minutes but it runs every minute more than once and fills concurrent request queue.
Please help.
EBS 12.1.1, DB 11.1.0.7, Linux 5.
Thanks & Regards
Aneel Ahmed

We have scheduled Workflow agent listener program to be run after 5 minutes but it runs every minute more than once and fills concurrent request queue.
Looks like this concurrent program was scheduled to run more than once? Maybe under a different application user?
What if you cancel the recent schedule you made, would you be able to reproduce the issue then?
Thanks,
Hussein

How to find through back end workflow Agent Listener is runnning or not

Hi all,
How to find through backend workflow Agent Listener is runnning or not.
Thanks

Reddy,
Simple way to find if it is running or not can be done by below
SQL> select COMPONENT_NAME,COMPONENT_STATUS from fnd_svc_components;
COMPONENT_NAME COMPONENT_STATUS
ECX Inbound Agent Listener STOPPED
ECX Transaction Agent Listener STOPPED
Workflow Deferred Agent Listener DEACTIVATED_SYSTEM
Workflow Deferred Notification Agent Listener DEACTIVATED_SYSTEM
Workflow Error Agent Listener RUNNING
Workflow Inbound Notifications Agent Listener RUNNING
Workflow Notification Mailer DEACTIVATED_SYSTEM
Thanks,
baskar.l

How to activate Workflow Agent listener Service - Oracle E-BIZ R12

Environment
DB : 11.1.0.7
Appl Rel. : R12.1.1
OS : RHEL 5.1 (x86_64)
Following is the work around done to bring up WF Agent listener
After Completion of Clone navigating to WORKFLOW system ,
Status of     Notication Mailers : Down
          Agent Listeners : Down
          Service Components : Down
-- Workflow Notification Mailer is not reqd for this Instance
I have done following NAVIGATION
Login as sysadmin
Go to System Administartor > OAM > Wrkflow > Service Components
Here this window theres a drop down with defined actions , i have selected Stop ALL and hit Go
a Conq Req got submitted , when i have checked System Administartor > OAM > Wrkflow > Service Components
state of the components are deactivating ...
After a while i have selected WF Agent listener and started from OAM and in another windows checked the concurrent request , it got completed normal and there was no output and logfile and priority was 0
Please guide me what has to be done to enable particular service ..
- Chetan

Please see these MOS Docs.
How to start the Workflow Deferred Agent Listener andWorkflow Java Deferred Agent Listener? [ID 548918.1]
'Service Component Container is not Running' when Trying to Start Workflow Components [ID 733335.1]
Troubleshooting Workflow Agent Listener's Failure To Start [ID 469009.1]
Thanks,
Hussein

Workflow Agent Listener and Service Components showing Down status

Hi
We are using oracle11i(11.5.10.2) on windows 2000 server
unable to satrt Workflow agent and service component but mail server showing running status
what could be the problem?
with Regards
AUH

Hi Auh;
Please check below and see its helpful:
'Service Component Container is not Running' when Trying to Start Workflow Components [ID 733335.1]
Oracle Workflow Release 12 Diagnostics [ID 469822.1]
11i/R12 - A guide for troubleshoting Workflow Notification Emails - Inbound and Outbound [ID 831982.1]
Cannot start WF Agent Listener - Error "Service Component Container Not Running" [ID 559388.1]
How to Start Workflow Service Component Containers? [ID 436183.1]
Troubleshooting Workflow Agent Listener's failure to start [ID 469009.1]
Regard
Helios

Workflow Agent Listener Service - Performance tuning for high volume

We have AR and Collection which initiate thousands of workflows. We also have various other workflows that run parallell activities. We have workflow backgrond engine schedule as Y,N,N for each of the item types.
It takes many hours for the workflows to progress. In some cases the background engine stays running on the current manager for hours when it reaches flow steps that take longer. It looks like the Workflow Agent Listener Service processes a single flow at one time which is killing us when longer running processes are running. We run 1 Workflow Agent Listener Service with 30 threads assuming it would pick up and process 30 items. It is very hard to tell if we have improvement.
Does anyone have any information on the following-
1) is it better to have more than 1 Workflow Agent Listener Service or is 1 sufficient?
2) is there a benefit to having multiple threads?

Please mention the details of the application release, database version and OS.
Can you find any errors in the workflow/database log files?
Any locks in the database?
Please see these doc.
Troubleshooting WF_DEFERRED Agent Listeners Performance [ID 468650.1]
Autoadjustment Business Events Blocking Wf_deferred Queue [ID 1120818.1]
Performance Caused By Lock On WF_EVENT.LISTEN [ID 579471.1]
Thanks,
Hussein

Workflow Agent Listener and Workflow Background Engine

Hi all,
I try to update roles via User Management responsibility but when applying them it throws the following warning: "Updates to Role data will not be visible in the application until the following processes are started : Workflow Agent Listener and Workflow Background Engine". So, my question is via which responsibility i can submit those requests and is there anything else i should know before creating, update roles and assigning permissions to them?
Thanks in advance,
Alexander.

I checked the requests and i found that Workflow Background Engine completed successful. Only Open Period Balance finished with error but is it possible this to be the reason of the given warning? I believe not.
And pls kindly explain what exactly means "you may need to log a SR."? Create a Service Request (SR) in My Oracle Support website so you get a help from Oracle Support Engineer (assuming you have a valid CSI number and MOS account) -- https://support.oracle.com
Thanks,
Hussein

Workflow Agent Listener Service is Down

Hi,
EBS version 12.0.4
While starting Workflow notification mailer , Workflow Agent Listener Service state is activated but status is Down.Also same status for Workflow Document Web Services Service.
Acual process showing 0 and Target as 1.
whereas Workflow Mailer Service is Activated with status UP
We tried steps from 559388.1 note bouncing apache,starting container but same error.
Please advice.
Thanks & Regards--Dhanashree

Hi,
Pls find the log.
GC 12413K->7696K(16984K), 0.0069343 secs]
[Sep 4, 2010 12:27:18 AM BST]:1283556438150:-1:-1:STFPROJAPP001.fna.pbpo.com:10.32.97.435:-1:-1:1:20420:ANONYMOUS(0):-1:Thread[inboundThreadGroup1,5,inboundThreadGroup]:10.32.97.435:23133:1283556438150:14:ERROR:[fnd.wf.bes.PLSQLQueueHandler]:dequeue() :Could not execute() the CallableStatement or retrieve OUT parameter -> java.sql.SQLException: Io exception: Connection timed out
[Sep 4, 2010 12:27:18 AM BST]:1283556438150:-1:-1:STFPROJAPP001.fna.pbpo.com:10.32.97.435:-1:-1:1:20420:SYSADMIN(0):-1:Thread[inboundThreadGroup1,5,inboundThreadGroup]:10.32.97.435:23133:1283556438150:15:ERROR:[fnd.wf.bes.PLSQLQueueHandler]:dequeue() :Could not execute() the CallableStatement or retrieve OUT parameter -> java.sql.SQLException: Io exception: Connection timed out
[Sep 4, 2010 12:36:01 AM BST]:1283556961887:-1:-1:STFPROJAPP001.fna.pbpo.com:10.32.97.435:-1:-1:1:20420:SYSADMIN(0):-1:Thread[inboundThreadGroup1,5,inboundThreadGroup]:10.32.97.435:23133:1283556438150:15:ERROR:[SVC-GSM-WFALSNRSVC-177852-10022 : oracle.apps.fnd.cp.gsc.SvcComponentProcessor.read()]:Error occurred while dequeueing -> oracle.apps.fnd.wf.bes.QueueHandlerException: Could not execute() the CallableStatement or retrieve OUT parameter -> java.sql.SQLException: Io exception: Connection timed out
[Sep 4, 2010 12:28:34 AM BST]:1283556514169:-1:-1:STFPROJAPP001.fna.pbpo.com:10.32.97.435:-1:-1:1:20420:SYSADMIN(0):-1:Thread[inboundThreadGroup1,5,inboundThreadGroup]:10.32.97.435:23133:1283556514169:19:ERROR:[SVC-GSM-WFALSNRSVC-177852-10003 : oracle.apps.fnd.wf.bes.AgentListenerProcessor.read()]:Could not executeUpdate() on { CALL   WF_EVENT.LISTEN ( p_agent_name => :1, p_wait => :2, p_correlation => :3, p_deq_condition => null, p_message_count => :4, p_max_error_count => :5 )} -> java.sql.SQLException: Io exception: Connection timed out
[Sep 4, 2010 12:27:27 AM BST]:1283556447537:-1:-1:STFPROJAPP001.fna.pbpo.com:10.32.97.435:-1:-1:1:20420:SYSADMIN(0):-1:Thread[inboundThreadGroup1,5,inboundThreadGroup]:10.32.97.435:23133:1283556447537:17:ERROR:[SVC-GSM-WFALSNRSVC-177852-10004 : oracle.apps.fnd.wf.bes.AgentListenerProcessor.read()]:Could not executeUpdate() on { CALL   WF_EVENT.LISTEN ( p_agent_name => :1, p_wait => :2, p_correlation => :3, p_deq_condition => null, p_message_count => :4, p_max_error_count => :5 )} -> java.sql.SQLException: Io exception: Connection timed out
[Sep 4, 2010 12:28:59 AM BST]:1283556539358:-1:-1:STFPROJAPP001.fna.pbpo.com:10.32.97.435:-1:-1:1:20420:SYSADMIN(0):-1:Thread[inboundThreadGroup1,5,inboundThreadGroup]:10.32.97.435:23133:1283556539358:20:ERROR:[SVC-GSM-WFALSNRSVC-177852-10002 : oracle.apps.fnd.wf.bes.AgentListenerProcessor.read()]:Could not executeUpdate() on { CALL   WF_EVENT.LISTEN ( p_agent_name => :1, p_wait => :2, p_correlation => :3, p_deq_condition => null, p_message_count => :4, p_max_error_count => :5 )} -> java.sql.SQLException: Io exception: Connection timed out
[Sep 4, 2010 12:35:53 AM BST]:1283556953006:-1:-1:STFPROJAPP001.fna.pbpo.com:10.32.97.435:-1:-1:1:20420:SYSADMIN(0):-1:Thread[inboundThreadGroup1,5,inboundThreadGroup]:10.32.97.435:23133:1283556438150:14:ERROR:[SVC-GSM-WFALSNRSVC-177852-10021 : oracle.apps.fnd.cp.gsc.SvcComponentProcessor.read()]:Error occurred while dequeueing -> oracle.apps.fnd.wf.bes.QueueHandlerException: Could not execute() the CallableStatement or retrieve OUT parameter -> java.sql.SQLException: Io exception: Connection timed out
[GC 12432K->8231K(16984K), 0.0214131 secs]
[Sep 4, 2010 12:27:47 AM BST]:1283556467428:-1:-1:STFPROJAPP001.fna.pbpo.com:10.32.97.435:-1:-1:1:20420:SYSADMIN(0):-1:Thread[inboundThreadGroup1,5,inboundThreadGroup]:10.32.97.435:23133:1283556467428:18:ERROR:[SVC-GSM-WFALSNRSVC-177852-10005 : oracle.apps.fnd.wf.bes.AgentListenerProcessor.read()]:Could not executeUpdate() on { CALL   WF_EVENT.LISTEN ( p_agent_name => :1, p_wait => :2, p_correlation => :3, p_deq_condition => null, p_message_count => :4, p_max_error_count => :5 )} -> java.sql.SQLException: Io exception: Connection timed out
[Sep 4, 2010 12:27:18 AM BST]:1283556438150:-1:-1:STFPROJAPP001.fna.pbpo.com:10.32.97.435:-1:-1:1:20420:SYSADMIN(0):-1:Thread[inboundThreadGroup1,5,inboundThreadGroup]:10.32.97.435:23133:1283556438150:16:ERROR:[fnd.wf.bes.PLSQLQueueHandler]:dequeue() :Could not execute() the CallableStatement or retrieve OUT parameter -> java.sql.SQLException: Io exception: Connection timed out
[Sep 4, 2010 12:36:01 AM BST]:1283556961937:-1:-1:STFPROJAPP001.fna.pbpo.com:10.32.97.435:-1:-1:1:20420:SYSADMIN(0):-1:Thread[inboundThreadGroup1,5,inboundThreadGroup]:10.32.97.435:23133:1283556438150:16:ERROR:[SVC-GSM-WFALSNRSVC-177852-10040 : oracle.apps.fnd.cp.gsc.SvcComponentProcessor.read()]:Error occurred while dequeueing -> oracle.apps.fnd.wf.bes.QueueHandlerException: Could not execute() the CallableStatement or retrieve OUT parameter -> java.sql.SQLException: Io exception: Connection timed out
[Sep 4, 2010 12:36:01 AM BST]:1283556961959:-1:-1:STFPROJAPP001.fna.pbpo.com:10.32.97.435:-1:-1:1:20420:SYSADMIN(0):-1:Thread[inboundThreadGroup1,5,inboundThreadGroup]:10.32.97.435:23133:1283556467428:18:ERROR:[SVC-GSM-WFALSNRSVC-177852-10005 : oracle.apps.fnd.cp.gsc.Processor.performError(ProcessorException)]:Maximum number of errors have occurred for this processing thread.
[Sep 4, 2010 12:36:02 AM BST]:1283556962038:-1:-1:STFPROJAPP001.fna.pbpo.com:10.32.97.435:-1:-1:1:20420:SYSADMIN(0):-1:Thread[inboundThreadGroup1,5,inboundThreadGroup]:10.32.97.435:23133:1283556514169:19:ERROR:[SVC-GSM-WFALSNRSVC-177852-10003 : oracle.apps.fnd.cp.gsc.Processor.performError(ProcessorException)]:Maximum number of errors have occurred for this processing thread.
[Sep 4, 2010 12:36:02 AM BST]:1283556962041:-1:-1:STFPROJAPP001.fna.pbpo.com:10.32.97.435:-1:-1:1:20420:SYSADMIN(0):-1:Thread[inboundThreadGroup1,5,inboundThreadGroup]:10.32.97.435:23133:1283556539358:20:ERROR:[SVC-GSM-WFALSNRSVC-177852-10002 : oracle.apps.fnd.cp.gsc.Processor.performError(ProcessorException)]:Maximum number of errors have occurred for this processing thread.
[Sep 4, 2010 12:36:18 AM BST]:1283556978393:-1:-1:STFPROJAPP001.fna.pbpo.com:10.32.97.435:-1:-1:1:20420:SYSADMIN(0):-1:Thread[ComponentMonitor,5,main]:10.32.97.435:23133:1282813541517:1:EXCEPTION:[SVC-GSM-WFALSNRSVC-177852 : oracle.apps.fnd.cp.gsc.SvcComponentMonitor.startAutomaticComponents()]:Starting automatic component 10002
[Sep 4, 2010 12:36:18 AM BST]:1283556978632:-1:-1:STFPROJAPP001.fna.pbpo.com:10.32.97.435:-1:-1:1:20420:SYSADMIN(0):-1:Thread[ComponentMonitor,5,main]:10.32.97.435:23133:1282813541517:1:ERROR:[SVC-GSM-WFALSNRSVC-177852 : oracle.apps.fnd.cp.gsc.SvcComponentMonitor.process()]:Monitoring failed this iteration -> oracle.apps.fnd.cp.gsc.ProcessorException: Could not start automatic component -> oracle.apps.fnd.cp.gsc.server.GenericSvcComponentEOException: The Service Component Container is not running.
[Sep 4, 2010 12:37:01 AM BST]:1283557021942:-1:-1:STFPROJAPP001.fna.pbpo.com:10.32.97.435:-1:-1:1:20420:SYSADMIN(0):-1:Thread[inboundThreadGroup1,5,inboundThreadGroup]:10.32.97.435:23133:1283556438150:15:ERROR:[fnd.wf.bes.PLSQLQueueHandler]:prepareDequeueStatement() : Could not prepare dequeue CallableStatement or set IN parameters 1, 3, or 4 or register OUT parameter -> java.sql.SQLException: Closed Connection
[Sep 4, 2010 12:37:01 AM BST]:1283557021943:-1:-1:STFPROJAPP001.fna.pbpo.com:10.32.97.435:-1:-1:1:20420:SYSADMIN(0):-1:Thread[inboundThreadGroup1,5,inboundThreadGroup]:10.32.97.435:23133:1283556438150:15:ERROR:[SVC-GSM-WFALSNRSVC-177852-10022 : oracle.apps.fnd.cp.gsc.SvcComponentProcessor.read()]:Error occurred while dequeueing -> oracle.apps.fnd.wf.bes.QueueHandlerException: Could not prepare dequeue CallableStatement or set IN parameters 1, 3, or 4 or register OUT parameter -> java.sql.SQLException: Closed Connection
[Sep 4, 2010 12:37:02 AM BST]:1283557022071:-1:-1:STFPROJAPP001.fna.pbpo.com:10.32.97.435:-1:-1:1:20420:SYSADMIN(0):-1:Thread[inboundThreadGroup1,5,inboundThreadGroup]:10.32.97.435:23133:1283556438150:14:ERROR:[fnd.wf.bes.PLSQLQueueHandler]:prepareDequeueStatement() : Could not prepare dequeue CallableStatement or set IN parameters 1, 3, or 4 or register OUT parameter -> java.sql.SQLException: Closed Connection
Regds,

WORKFLOW AGENT LISTENER SERVICE 기동되지 않을때

제품 : AOL
작성날짜 : 2005-11-28
WORKFLOW AGENT LISTENER SERVICE 기동되지 않을때
========================================
PURPOSE
신규설치 및 Clonning후 WORKFLOW AGENT LISTENER SERVICE 기동되지 않을때가 있습니다. 이에 대한 조치사항을 기술하고 있습니다.
Problem Description
증상
1. Workflow Agent Listener Service 와 Workflow Mailer Service 기동되지 않습니다.
2. 기동될때 "Activating" status 로 남아 있습니다.
3. 위와 같은 증상은 아래와 같은 원인에 발생할수 있습니다.
(a) The WF_JMS_IN 와 WF_JMS_OUT queues 가 invalid 일때
(b) 아래 workflow listeners 와 mailer 들이 'STOPPED_ERROR' status일때
Workflow Deferred Agent Listener
Workflow Deferred Notification Agent Listener
Workflow Error Agent Listener
Workflow Inbound Notifications Agent Listener
Workflow Notification Mailer
(c) Af_CLASSPATH 가 JDK 1.3.1을 가리키지 않을때
Solution Description
이런 증상이 발견될경우 아래와 같은 조치를 취해주세요.
1. missing/corrupt queues 가 있는지 확인하고 이를 재성성 해주세요.
sqlplus apps/apps @$FND_TOP/patch/115/sql/wfjmsqc.sql applsys apps
위 sql이 먹지 않을때
다음 command들을 copy/paste해서 작업해주세요(APPLSYS user로 하셔야 합니다.)
Exec dbms_aqadm.stop_queue( queue_name => ' WF_JMS_IN', wait => FALSE);
Exec dbms_aqadm.drop_queue(queue_name=> ' WF_JMS_IN');
exec dbms_aqadm.drop_queue_table( queue_table => ' WF_JMS_IN', force => TRUE);
Exec dbms_aqadm.stop_queue( queue_name => ' WF_JMS_OUT', wait => FALSE);
Exec dbms_aqadm.drop_queue(queue_name=> ' WF_JMS_OUT');
exec dbms_aqadm.drop_queue_table( queue_table => ' WF_JMS_OUT', force => TRUE);
위 queue들이 drop되면 아래 sql을 다시 실행해 주세요.
sqlplus apps/apps @$FND_TOP/patch/115/sql/wfjmsqc.sql applsys apps
그리고 확인차 wfver.sql를 돌려주세요.
(Note: The file wfjmsqc.sql has been replaced in 9.2.0.4 with wfjmsqc2.sql.)
2. 11.5. 7 이전 버전은 JDK 1.3을 CM node에 설치해야 하고 patch 2356331 를 적용해야 합니다.
Please reference:
Note:242941.1 (How To Troubleshoot Java-based Workflow Notification Mailer In 11.5.9 and OWF.G)
Note:130091.1 (Upgrading Oracle Applications 11i to use JDK 1.3)
3. 환경변수 AF_JRE_TOP, AF_CLASSPATH, and AFJVAPRG 가 $APPL_TOP/admin/adovars.env에 제대로 설정되었는지 확인해 주세요. 그리고 이들이 JDK 1.3.1을 가리키고 있는지 확인해 주세요.
Reference Documents
Note 278428.1

제품 : AOL
작성날짜 : 2005-11-28
WORKFLOW AGENT LISTENER SERVICE 기동되지 않을때
========================================
PURPOSE
신규설치 및 Clonning후 WORKFLOW AGENT LISTENER SERVICE 기동되지 않을때가 있습니다. 이에 대한 조치사항을 기술하고 있습니다.
Problem Description
증상
1. Workflow Agent Listener Service 와 Workflow Mailer Service 기동되지 않습니다.
2. 기동될때 "Activating" status 로 남아 있습니다.
3. 위와 같은 증상은 아래와 같은 원인에 발생할수 있습니다.
(a) The WF_JMS_IN 와 WF_JMS_OUT queues 가 invalid 일때
(b) 아래 workflow listeners 와 mailer 들이 'STOPPED_ERROR' status일때
Workflow Deferred Agent Listener
Workflow Deferred Notification Agent Listener
Workflow Error Agent Listener
Workflow Inbound Notifications Agent Listener
Workflow Notification Mailer
(c) Af_CLASSPATH 가 JDK 1.3.1을 가리키지 않을때
Solution Description
이런 증상이 발견될경우 아래와 같은 조치를 취해주세요.
1. missing/corrupt queues 가 있는지 확인하고 이를 재성성 해주세요.
sqlplus apps/apps @$FND_TOP/patch/115/sql/wfjmsqc.sql applsys apps
위 sql이 먹지 않을때
다음 command들을 copy/paste해서 작업해주세요(APPLSYS user로 하셔야 합니다.)
Exec dbms_aqadm.stop_queue( queue_name => ' WF_JMS_IN', wait => FALSE);
Exec dbms_aqadm.drop_queue(queue_name=> ' WF_JMS_IN');
exec dbms_aqadm.drop_queue_table( queue_table => ' WF_JMS_IN', force => TRUE);
Exec dbms_aqadm.stop_queue( queue_name => ' WF_JMS_OUT', wait => FALSE);
Exec dbms_aqadm.drop_queue(queue_name=> ' WF_JMS_OUT');
exec dbms_aqadm.drop_queue_table( queue_table => ' WF_JMS_OUT', force => TRUE);
위 queue들이 drop되면 아래 sql을 다시 실행해 주세요.
sqlplus apps/apps @$FND_TOP/patch/115/sql/wfjmsqc.sql applsys apps
그리고 확인차 wfver.sql를 돌려주세요.
(Note: The file wfjmsqc.sql has been replaced in 9.2.0.4 with wfjmsqc2.sql.)
2. 11.5. 7 이전 버전은 JDK 1.3을 CM node에 설치해야 하고 patch 2356331 를 적용해야 합니다.
Please reference:
Note:242941.1 (How To Troubleshoot Java-based Workflow Notification Mailer In 11.5.9 and OWF.G)
Note:130091.1 (Upgrading Oracle Applications 11i to use JDK 1.3)
3. 환경변수 AF_JRE_TOP, AF_CLASSPATH, and AFJVAPRG 가 $APPL_TOP/admin/adovars.env에 제대로 설정되었는지 확인해 주세요. 그리고 이들이 JDK 1.3.1을 가리키고 있는지 확인해 주세요.
Reference Documents
Note 278428.1

Workflow Agent login failure

Hi Everybody,
I m following KFI process for Invoice Processing.The document image is successfully loaded into UCM and display in IPM search criteria.But the thing is that when ever i m watching Documentrouting in EM ,there is no instance created .
IPM logs:Workflow Agent login failure
Please guide me how to solve this one.
With Regards
Jyoti

Hi Everybody,
Actually imaging.ear was missing.It has solved with the patch installation for soa suite 11.1.1.3 in linux machine.
Thnx for co-operation.
With Regards
Jyoti

Agent Issue in Workflow

Hi Team ,
I have created one rule which is returing two agents . But when i am using this rule in decsion step , then workitem is going only to one agent , not to both .
Please help .
Regards
Jagjit Singh

Hi Jagjit
"If iam executing workflow using A/B agent login in sap system"
How are you executing the workflow? Where are you starting the workflow from?
By "Executing the workflow" do you mean starting the workflow or executing the work item?
If a work item goes to two users, each one will see it in their inbox. If you open it, it gets reserved by the name of the user who opened it and disappear's from other's inbox (standard behaviour). If you execute the work item, it completes, is no more available in any inbox , and moves to the next step in workflow.
Looking at your recent description, it seems that the workitem is going to both users and you are executing from one inbox .... so what do we want here and what is not happening here?
It would be good to see the activeX version log of the workflow (the work item should not be completed or processes), click on the button in AGENTS column and see what is listed.
Regards,
Modak

SAP workflow strange issue Rule agent

Dear all,
This happens once in 40 document.I have debugged the rule and agent coming into actor_tab for the error wf.I have kept the screen shot before the user decision they kept the wait step and also the start event binding.Please let me know your views.
Thanks in advance.

Hi Sridar,
Yes, that is probably your problem. If it's a similar data type it wouldn't matter. But WFSYST-INITIATOR is an HR structured type and has the object type prefixed (e.g. US=User), thus "USBOND007", whereas BNAME is just a username "BOND007".
This would still technically work if your code strips the "US" object type component, but BNAME will be too short and cut off long IDs as in "USBOND00". This would explain why it only occasionally fails.
Regards,
Mike

FI Payment Release Workflow Agent assignment and SPRO settings.

Hi Experts,
I am working on Payment release workflow for 2 stages. So for this i have activated the main workflow WS00400012 and for First level release WS00400011 and for second level release WS00400021.
Now where should i assign the agent for First level release and second level release ? and what setting should i do in SPRO as FI settings.
Any of you suggestions will be of great help me to resolve this issue.
Regards,
Hari

Hi,
Thank you for your reply.Should i mention the main workflow number in SPRO or
just the subworkflows alone ?.
Assign main workflow number
Can i assign users directly in workflow itself insteas of assigning position in SPRO.
Don't assign users inside the workflow, if the user id you want to change then again you have to change the workflow.
Regards,
Surjith

TRIP Workflow approval issue

Dear All
We have developed custom workflow for TRIP workflow, with single level approval of line manager.
We are raising Trip request using Transaction PR05.Workitem goes to line manager for approval in SAP inbox and
NWBC (SAP netweaver ) for approval.On approval by manager workflow is completed instead of further processing.
Reason for completion of workflow is Event BUS2089 CHANGE is created with event APPROVED.
Due to this CHANGE event current workflow instance is completed,as parallely condition for CHANGE is checked for workflow completion.
Kindly let us now this unexpected behavior of CHANGE event creation of BUS2089 on approval of trip by manager and any
steps to control this.
Thanks and Regards,
Aditya

Hi Aditya
You may want to retain CHANGED event wait step so that if the trip is changed outside the WF, the current instance, being redundant, gets completed.
For your case there can be two different approaches, depending how you have implemented the workflow.
1) Check who is the user triggering the event CHANGED in this case. Is the system catching the manager user name or the user name WF-BATCH. If it is WF-BATCH, it becomes fairly simple. You do not complete the workflow after WAIT for EVENt step, instead loop back to wait step for any possible changes later on (outside the WF)....you will get the user name in the event (_EVT_CREATOR)
2) If the username is that of the Approver, see if this works for you (Iam assuming that your approval is in one branch of the fork and the wait for event is in another branch of the fork (1 of 2 fork)).
a) Trap the Actual Agent of the decision in the approval branch
b) Trap the user triggering the COMPLETED event in the other branch
c) Compare the two - if they are same, do not execute the process control step to complete the WF instead loop back to wait step for any possible changes later on (outside the WF).
Not sure if this will work because there can be timing issues.....the Actual Agent of approval may not be written in one branch and the comparison happens in the other..... it's worth a try
Regards,
Modak

Workflow Agent issue

Similar Messages

Maybe you are looking for