HTTP 401 Errors for REST API Calls
Article ID: 216031
Updated On:
Products
Issue/Introduction
AWI generates a lot of Errors on REST API call for objects that do not have a ERT because they have not reached the END status yet.
In the JCP log files many messages of this kind can be found
======================================================================
20201201/010051.410 - 228021 U00045099 The server replied with following status: '401'
20201201/010051.411 - 228044 U00045098 Method 'GET', URL: 'http://<JCP Server name>:8088/ae/api/v1/0010/executions'
20201201/010051.415 - 228044 U00045105 Log on of 'USER/DEPT' successful.
20201201/010051.995 - 228043 U00045098 Method 'GET', URL: 'http://<JCP Server name>:8088/ae/api/v1/0010/executions'
20201201/010051.996 - 228043 U00045099 The server replied with following status: '401'
20201201/010051.997 - 228022 U00045098 Method 'GET', URL: 'http://<JCP Server name>:8088/ae/api/v1/0010/executions'
20201201/010051.999 - 228022 U00045105 Log on of 'USER/DEPT' successful.
======================================================================
HTTP 422 errors can be present in a huge number as well.
Environment
Release : 12.3
Component : AUTOMATION ENGINE
Cause
This is a bug in AWI until to the AE versions:
12.3.6 available end of June 2021
21.0.0 available end of September 2021
Resolution
Update AE and AWI to versions listed in the solution or higher.
Feedback
