SDX Application Library 6.4.0 Release Notes > Known Problems and Limitations

Known Problems and Limitations

This section identifies known problems and limitations in this release.

ACP

• When you configure the ACP application in edge mode or dual mode, you must configure both the service and the network interfaces between subscribers and the SDX network in the same directory. If the network interfaces appear in a different directory from the service, ACP cannot retrieve the congestion points.

Reference: TIC 9123

Deep Packet Inspection

• If the following exception is written into an error log, you can safely ignore it.

14:33:57.178 EST 13.01.2006 [SLEAccReader-default@ogre]
[DPISLEAcctMgr-default@ogre] [50] Failed to read accounting data
10.227.7.131/UF-10.227.7.131-011206@1615-15M.ufb/default@ogre from
SLE; stack trace: com.ellacoya.dataobject.ObjectDoesNotExistException: ffffffff

Workflow Manager

• Occasionally, Workflow Manager is unresponsive because of communication problems with the workflow engine.

Workaround: Stop and then restart Workflow Manager.

Reference: TIC 4316

• If you install the Workflow application on the same machine as the JBoss application server, Workflow Manager will not operate if the JBoss application server is running.

Workaround: If you use the Workflow application and the JBoss application server in your SDX configuration, install the Workflow application and the JBoss application server on different machines.

Reference: TIC 8133