0 Replies Latest reply on Jul 7, 2017 8:56 PM by mdtaylor

    WF_NOTIFICATION_OUT keeps increasing and WF notifications take weeks to be sent

    mdtaylor

      In our high volume Production 12.1.3 environment, we have between 4000 and 9000 rows in WF_NOTIFICATION_OUT at all times, and it can take weeks for email notifications to be sent.  We tried increasing the outbound thread count from 1 to 10 but no messages were sent and the following errors were present in the Mailer log:

       

      YSADMIN(0):-1:Thread[outboundThreadGroup1,5,outboundThreadGroup]:1630983388:74220:1498896021498:11:ERROR:[fnd.wf.bes.PLSQLQueueHandler] repareDequeueStatement() : Could not prepare dequeue CallableStatement or set IN parameters 1, 3, or 4 or register OUT parameter -> java.sql.SQLRecoverableException: Closed Connection

      [Jul 7, 2017 11:06:08 AM PDT]:1499450768611:-1:-1:host.domain10.10.9.201:-1:-1:1:20420 (worry) YSADMIN(0):-1:Thread[outboundThreadGroup1,5,outboundThreadGroup]:1630983388:74220:1498896021498:11:ERROR:[SVC-GSM-WFMLRSVC-247500-10006 : 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.SQLRecoverableException: Closed Connection

       

      These errors do not appear when the outbound thread count is 1.

       

      We are using on premise Exchange Server for our IMAP/SMTP server.  Has anyone had issues with WF_NOTIFICATION_OUT clearing very slowly.  We are on 12.1.3+ RPC5.

       

      Thanks,

      Michael