How to handle Error ClientAbortException in TIBCO BusinessWorks(TM) ProcessMonitor Server logs.

How to handle Error ClientAbortException in TIBCO BusinessWorks(TM) ProcessMonitor Server logs.

book

Article ID: KB0076368

calendar_today

Updated On:

Products Versions
TIBCO BusinessWorks ProcessMonitor 2.2.x,3.0.x
Not Applicable -

Description

 Description:
 
   In TIBCO BusinessWorks (TM)
ProcessMonitor (BWPM) server.logs, the following error is seen.

   "ERROR [http-8141-4] com.faizsiegeln.njams.util.JSONUtilities: ClientAbortException:  java.net.SocketException: Connection reset      by peer: socket write error"


Symptoms:
       
      The following error is logged in the BWPM server.logs.

     " ERROR [http-8141-4] com.faizsiegeln.njams.util.JSONUtilities: ClientAbortException:  java.net.SocketException: Connection reset by peer: socket write error"

Cause:
     
      Above error is usually a consequence of some action on the end users side, i.e., in the web browser where you the BWPM GUI is being accessed.

   For example, if a user clicks on the domain object in the technical view and moves to the admin view, or navigates to a process Diagram tab or selects other domain objects in the technical view.

Issue/Introduction

The error "ClientAbortException" is logged in TIBCO BusinessWorks (TM) ProcessMonitor server logs is usually found when the user clicks on the domain object in the technical view and moves to the admin view, or navigates to a process Diagram tab or selects other domain objects in the technical view.

Environment

Product: TIBCO BusinessWorks™ ProcessMonitor Version: 2.2.x,3.0.x OS: All Supported Operating Systems --------------------

Resolution

 This issue occurs if  BWPM server is trying to fetch data from a Tomcat server/database and before the request gets completed and  if the user navigates to another view/domain object in the BWPM GUI further the previous request gets closed/aborted.

   However, if previous requests are executed and successfully completed before navigating to other VIEW/Domain objects in the BWPM GUI, the above mentioned issue will not be logged. 

 Also such error could be ignored as this is a warning for a cancelled request / Connection RESET by a peer while the request is still in-process at the BWPM server.