Field Notice: FN - 72033 - With AP376117 Applied, XSI Requests Whose Response Body Is Empty or Null Will Lead to an Unexpected Error - Software Upgrade Recommended

Available Languages

Updated:February 15, 2021
Document ID:FN72033

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Notice

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.

Revision History

Revision Publish Date Comments
1.0
08-Feb-21
Initial Release

Products Affected

Affected OS Type Affected Software Product Affected Release Affected Release Number Comments
NON-IOS
Application Patches
22.0
22.0.2020.10
NON-IOS
Application Patches
23.0
23.0.2020.10

Defect Information

Defect ID Headline
CSCvf34445 There were no defects filed with this field notice at the time of publication.

Problem Description

eXtended Services Interface (XSI) requests whose response body is empty or null will lead to HTTP 409 error code and NullPointerException could be seen in the logs.

Background

Note: This field notice was originally posted in the BroadSoft Xchange portal and has been moved over to Cisco.com as-is for historical purposes.

Problem Symptom

XSI requests whose response body is empty or null will lead to HTTP 409 error code and a NullPointerException being reported in the logs. This exception has the potential to affect XSI event channels leading to the channels being torn down, which requires the application to restart the channels.

An example of the exception is:

java.lang.NullPointerException
at java.util.regex.Matcher.getTextLength(Matcher.java:1283)
at java.util.regex.Matcher.reset(Matcher.java:309)
at java.util.regex.Matcher.<init>(Matcher.java:229)
at java.util.regex.Pattern.matcher(Pattern.java:1093)
at com.broadsoft.protocols.oci.util.OCIDataUtility.removePasswords(OCIDataUtility.java:451)
at com.broadsoft.xsi.base.BwXsiUtilities.scrubber(BwXsiUtilities.java:79)

When the XSI event channels are affected by this issue, this exception might be reported:

Oct 28, 2020 12:20:15 AM org.apache.coyote.AbstractProtocol$ConnectionHandler process
SEVERE: Error reading request, ignored
java.lang.IllegalStateException: Calling [asyncPostProcess()] is not valid for a request with Async state [ERROR]
at org.apache.coyote.AsyncStateMachine.asyncPostProcess(AsyncStateMachine.java:290)
at org.apache.coyote.AbstractProcessor.asyncPostProcess(AbstractProcessor.java:192)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:81)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1590)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) at com.broadsoft.xsp.platform.InstrumentedExecutor$Tracker.run(InstrumentedExecutor.java:413)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

Workaround/Solution

BroadWorks patches can now be downloaded through the Cisco Software Download Center after logging in with your Cisco.com (CCO) account.

The version of BroadWorks that is currently deployed as well as the patches currently activated can be checked by executing the get versions all command from the CLI. More information on how to check the patch level can be found in the Cisco BroadWorks Maintenance Guide.

Workaround

Remove AP376117.

Patch

Corrective patches AP377042 are now available on the Cisco Software Download. Download the corrective patch and apply it with AP376117.

These patches are now available through the Cisco Software Download Center:

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

Receive Email Notification For New Field Notices

My Notifications—Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco