E1: 32: Data Pointer Leak Triggers “No Sufficient Memory” Error for BSSV Service Sales Order Manager - JP420000 (Doc ID 2872142.1)

Last updated on MARCH 14, 2024

Applies to:

Symptoms

When using an integration platform thru BSSV into E1, there will be the error "insufficient error messages" presented back from E1, in some cases. If this happens it is necessary to reboot BSSV server to get everything to work again.

In the standard jde.log this is printed:
21929/7 WRK:XXX_0270AA50_DConnector Tue Jan 18
11:47:44.579150 jdb_utl1.c1100
JDB9900600 - Failed to store value, maximum exceeded. Probable cause is forgetting to call jdeRemoveDataPtr(). Dumping data pointer data in debug log.

and in the jdedebug log can we see this:
Jan 18 11:44:28.380447 jdb_utl1.c1184 - 21929/5
WRK:XXX_0270AA50_DConnector SESSION,Ptr=000000010270aa50,User=SYSINTE1,Env=JPD920,Role=*ALL,Machine=idcjdeais02,SignOnTime= 1/18/2022 6:41:50,LastActiveTime= 1/18/2022 11:44:26,ThreadedBSFN=0,InlinedBSFN=0

DATAPOINTER,Ptr=00000001024b1910,Index=1004,File=b3202670.c,Function=Component
CacheFetch,Line=878

DATAPOINTER,Ptr=ffffffff600e33a0,Index=1005,File=x4801.c,Function=IX4801_Store
OutSourcePointers,Line=1716

Steps:

1. Use BSSV JP420000 Sales Order Manager.
2. Check errors.
   
   

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.