IBM BPM, V8.0.1, All platforms > Troubleshooting and support > Troubleshooting administration tasks and tools

Troubleshooting store-and-forward processing

This topic discusses problems that you can encounter with store-and-forward processing.

Select the problem you are experiencing from the table below:
Problem Refer to the following
I am having problems setting the store-and-forward qualifier Store-and-forward qualifier processing only works on asynchronous interfaces
Qualifying runtime exceptions are occurring, but events are not getting stored Store is not activated by qualifying runtime exceptions
Messages are still being processed even though the Store and Forward widget shows the state is set to Store (Network deployment environment) In an ND environment, messages are being processed even though the store-and-forward state is set to Store
The Store and Forward widget shows the state is set to Forward, but messages are not being processed by all members of the cluster. (Network deployment environment) In an ND environment, messages are not getting processed by all members of the cluster even though the store-and-forward state is set to Forward


Store-and-forward qualifier processing only works on asynchronous interfaces

The store-and-forward qualifier must be specified on an asynchronous interface. The store cannot be activated if the interface is called synchronously.

Here are some guidelines (with respect to components) to help you determine if the interface is being called synchronously or asynchronously.

Also, consider these restrictions:


Store is not activated by qualifying runtime exceptions

If the store is not being activated by qualifying runtime exceptions, check the following.


In an ND environment, messages are being processed even though the store-and-forward state is set to Store

Messages might continue to be processed by some members of a cluster, despite the state being set to Store, if the state is not set to Store for each member of the cluster. To fix this problem, confirm that the state is set to Store for each member of the cluster in the Store and Forward widget. If any members of the cluster are set to Forward, change them to Store.

This might also happen if one of the members of the cluster is forced to restart. Since the Store state is not persistent, it reverts to the Forward state at restart. To fix this problem, change the state to Store for the module in the Store and Forward widget.

When the service becomes available again, you should not set the state to Store immediately if you want new events to be processed. If you set the state to Store before new events have the chance to be processed, they will be stored in the queue.


In an ND environment, messages are not getting processed by all members of the cluster even though the store-and-forward state is set to Forward

Messages might continue to be stored by some members of a cluster, despite the state being set to Forward, if the store-and-forward state is not set to Forward for each member of the cluster. To fix this problem, confirm that the state is set to Forward for the module in the Store and Forward widget. If any members of the cluster are set to Store, change them to Forward.

Troubleshooting IT administration

Troubleshooting administration tasks and tools