Memory leak on EEP when using JMS/SAP event resources not resolved

Document ID : KB000086533
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
On the universe.log, these kind of errors appear all the time with a JMS resource:
#########################
|ERROR|X|EEP|pid=15004.6116| owls_connect_auth | error getting port number for [JEE]/[X]
|ERROR|X|EEP|pid=15004.6116| o_callsrv_connect_r | Connection error 0 []
|ERROR|X|EEP|pid=15004.6116| owls_api_resjms_check | unable to connect to Mgr Java [COMPANY/NODE/X] [200]
|ERROR|X|EEP|pid=15004.6116| o_eep_exec_jms_resource | Error requesting Mgr Java, error code is: [200]
#########################

Patch level detected:Dollar Universe 6.1.00
Product Version: Dollar.Universe 6.1.0

Description :In case the manager for JEE / SAP is not configured, and a resource of type JMS / SAP is defined and added to an uproc, the EEP server will use a lot of memory and will eventually crash.
The file u_frrv60.dta of the concerned area will always contain the line concerning the resource, even if the job finish on time overrun or is cancelled.
 
Environment:
OS: All
 
Cause:
Cause type:
Defect
Root Cause: N/A
 
Resolution:
A new error code 200 has been implemented in case the manager of the concerned resource is not defined, and the memory leak of the EEP server has been fixed.
The line of the u_frrv60.dta will also be properly purged.

Fix Status: Released

Fix Version(s):
Component: Application.Server
Version: Dollar.Universe 6.7.41
 
Additional Information:
Workaround :
N/A