How to Modify the Frequency of the Notification Sender Retries Which May Hang The BPEL Server

(Doc ID 1303322.1)

Last updated on MARCH 24, 2011

Applies to:

Oracle(R) BPEL Process Manager - Version: 10.1.3.3.1 and later   [Release: AS10gR3 and later ]
Information in this document applies to any platform.

Goal

This document provides a method to avoid server hangs which result from failed notification retry attempts.

Background
You may observe that notification sender retries hang the BPEL server. The retry is done every 15 minutes, and you will see the following in the OC4J container log file at :

<2011-01-30 22:22:12,088> <DEBUG> <collaxa.cube.services> <oracle.bpel.services.notification.queue.sender.QuartzPublisher::execute> Start of execute
<2011-01-30 22:22:12,089> <DEBUG> <collaxa.cube.services> <Publisher::retryFailedNotification> Start of retry failed notification
<2011-01-30 22:22:12,093> <DEBUG> <collaxa.cube.services> <oracle.bpel.services.notification.queue.QueueConnectionPool::QueueConnectionPool> Fetched a queue connection from pool java:comp/env/jms/Queue/NotificationSenderQueueConnectionFactory, available connections=6
<2011-01-30 22:22:12,094> <DEBUG> <collaxa.cube.services> <Publisher::retryFailedNotification> End of failed retry notification
<2011-01-30 22:22:12,094> <DEBUG> <collaxa.cube.services> <oracle.bpel.services.notification.queue.sender.QuartzPublisher::execute> End of execute
<2011-01-30 22:37:12,087> <DEBUG> <collaxa.cube.services> <oracle.bpel.services.notification.queue.sender.QuartzPublisher::execute> Start of execute
<2011-01-30 22:37:12,087> <DEBUG> <collaxa.cube.services> <Publisher::retryFailedNotification> Start of retry failed notification
<2011-01-30 22:37:12,097> <DEBUG> <collaxa.cube.services> <oracle.bpel.services.notification.queue.QueueConnectionPool::QueueConnectionPool> Fetched a queue connection from pool java:comp/env/jms/Queue/NotificationSenderQueueConnectionFactory, available connections=5
<2011-01-30 22:37:12,097> <DEBUG> <collaxa.cube.services> <Publisher::retryFailedNotification> End of failed retry notification
<2011-01-30 22:37:12,098> <DEBUG> <collaxa.cube.services> <oracle.bpel.services.notification.queue.sender.QuartzPublisher::execute> End of execute

As you can see, with every retry attempt, it removes a connection from the connection pool used by the BPEL engine.  Once all available connections are used, the BPEL Server may hang. 

Although it's not possible to turn off the retry, you can modify the frequency of the retry attempts.


Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms