APAR status
Closed as program error.
Error description
If you Process Center uses a different EXTERNAL_CLIENT and INTERNAL_CLIENT URLs, then after upgrading to BPM 8.5.7 CF2016.12 you may encounter an error in the logs occurring with every heartbeat: [3/23/17 11:32:23:428 CDT] 0000010c EJBProxyRestH I com.ibm.bpm. ejbproxy.rest.EJBProxyRestHelper callEJB EJBProxy REST API with basicAuth, Server Url: https://10.77.210.22: 4443/bpm/dev/ProcessCenterInternal, path: https://TestProcessServer/bpm/dev/bpm/repo/v1/ejbproxy, returned code: 302 [3/23/17 11:32:23:428 CDT] 0000010c EJBProxyRestH E com.ibm.bpm. ejbproxy.rest.EJBProxyRestHelper callEJB EJBProxy REST API return 302 [3/23/17 11:32:23:428 CDT] 0000010c EJBProxyRestH E com.ibm.bpm. ejbproxy.rest.EJBProxyRestHelper callEJB EJBProxy REST API return 302 com.lombardisoftware.core. TeamWorksException: EJBProxy REST API return 302 at com.ibm.bpm.ejbproxy.rest.EJBProxyRestHelper.callEJBWithFullUrl (EJBProxyRestHelper.java:171) at com.ibm.bpm.ejbproxy.rest.EJBProxyRestHelper. getConfigurationOnRemoteServer(EJBProxyRestHelper.java:317) at com.lombardisoftware.core.RollingUpdateHelper.getPCConfiguration (RollingUpdateHelper.java:279) While this error is being displayed in the logs constantly, the Process Server will still be shown as online and there is not functionality impact. In particular, this problem would be seen for all IBM BPM on Cloud Process Servers that are upgraded to BPM 8.5.7 CF2016.12
Local fix
This issue is due to an incorrect endpoint calculation on the Process Center side. A REST call from the Process Server on the Process Center is hitting the PROCESS_CENTER scenario resutling in return of an EXTERNAL_CLIENT URL as opposed to an expected INTERNAL_CLIENT url. Thus, as a workaround, you can configure the PROCESS_CENTER endpoint to be using the internal url in for this case. That will prevent the error from showing up in the logs. Otherwise, this issue is fixed in BPM 8.5.7 CF2017.03
Problem summary
No additional information is available.
Problem conclusion
A fix is included in IBM BPM V8.5.7 cumulative fix 2017.03 that ensures that the INTERNAL_CLIENT endpoint of Process Center is invoked even in the exception handling case.
Temporary fix
Comments
APAR Information
APAR number
JR57697
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
857
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-04-04
Closed date
2017-06-07
Last modified date
2017-06-07
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
BPM ADVANCED
Fixed component ID
5725C9400
Applicable component levels
R857 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"857","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
07 June 2017