• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

Gross Ups abnormal end

jeremey_garcia

VIP Member
We are trying to process gross ups in a large quantity (6k+ employee) and it abnormal ends at about 1500 employees. When running locally, I notice cache leaks for each employee:
Entering jdeCacheDestroyAllUserCaches
Nov 05 18:30:51.151005 - 4884/5916 UNKNOWN hCache:[2B68BB00] Nm:[2PWHDR3] Recs:1 Curs:0 Hnds:1 Cchs:10 DESTROY
Nov 05 18:30:51.151006 - 4884/5916 UNKNOWN CAC0001111 - (jdeCacheDestroyAllUserCaches) Unterminated cache 2PWHDR3 with 1 record(s), created from File=B0702395.c, Function=InitializePrevailingWageCaches, Line=181.
Nov 05 18:30:51.151007 - 4884/5916 UNKNOWN hCache:[2B68BE78] Nm:[2PWPT3] Recs:0 Curs:0 Hnds:1 Cchs:9 DESTROY
Nov 05 18:30:51.151008 - 4884/5916 UNKNOWN CAC0001111 - (jdeCacheDestroyAllUserCaches) Unterminated cache 2PWPT3 with 0 record(s), created from File=B0702395.c, Function=InitializePrevailingWageCaches, Line=293.
Nov 05 18:30:51.151009 - 4884/5916 UNKNOWN hCache:[2B68BD50] Nm:[2PWTRAN3] Recs:0 Curs:0 Hnds:1 Cchs:8 DESTROY
Nov 05 18:30:51.151010 - 4884/5916 UNKNOWN CAC0001111 - (jdeCacheDestroyAllUserCaches) Unterminated cache 2PWTRAN3 with 0 record(s), created from File=B0702395.c, Function=InitializePrevailingWageCaches, Line=276.
Nov 05 18:30:51.151011 - 4884/5916 UNKNOWN hCache:[2B68B410] Nm:[2PT1] Recs:0 Curs:0 Hnds:1 Cchs:7 DESTROY
Nov 05 18:30:51.151012 - 4884/5916 UNKNOWN CAC0001111 - (jdeCacheDestroyAllUserCaches) Unterminated cache 2PT1 with 0 record(s), created from File=B0700003.c, Function=IB0700003_InitializePrePayrollCaches_OpenCacheTemplate, Line=3222.
Nov 05 18:30:51.151013 - 4884/5916 UNKNOWN hCache:[2B68BC28] Nm:[2PWDBA3] Recs:0 Curs:0 Hnds:1 Cchs:6 DESTROY
Nov 05 18:30:51.151014 - 4884/5916 UNKNOWN CAC0001111 - (jdeCacheDestroyAllUserCaches) Unterminated cache 2PWDBA3 with 0 record(s), created from File=B0702395.c, Function=InitializePrevailingWageCaches, Line=259.
Nov 05 18:30:51.151015 - 4884/5916 UNKNOWN hCache:[2B68B788] Nm:[2PayrollInit] Recs:0 Curs:0 Hnds:1 Cchs:5 DESTROY
Nov 05 18:30:51.151016 - 4884/5916 UNKNOWN CAC0001111 - (jdeCacheDestroyAllUserCaches) Unterminated cache 2PayrollInit with 0 record(s), created from File=B0700059.c, Function=I_B0700059_TerminatePayrollCache, Line=164.
Nov 05 18:30:51.151017 - 4884/5916 UNKNOWN hCache:[2B68B098] Nm:[2MPC1] Recs:0 Curs:0 Hnds:1 Cchs:4 DESTROY
Nov 05 18:30:51.151018 - 4884/5916 UNKNOWN CAC0001111 - (jdeCacheDestroyAllUserCaches) Unterminated cache 2MPC1 with 0 record(s), created from File=B0700003.c, Function=IB0700003_InitializePrePayrollCaches_OpenCacheTemplate, Line=3222.
Nov 05 18:30:51.151019 - 4884/5916 UNKNOWN hCache:[2B68B1C0] Nm:[2PPWW1] Recs:0 Curs:0 Hnds:1 Cchs:3 DESTROY
Nov 05 18:30:51.151020 - 4884/5916 UNKNOWN CAC0001111 - (jdeCacheDestroyAllUserCaches) Unterminated cache 2PPWW1 with 0 record(s), created from File=B0700003.c, Function=IB0700003_InitializePrePayrollCaches_OpenCacheTemplate, Line=3222.
Nov 05 18:30:51.151021 - 4884/5916 UNKNOWN hCache:[2B68BFA0] Nm:[2PWFD3] Recs:0 Curs:0 Hnds:1 Cchs:2 DESTROY
Nov 05 18:30:51.151022 - 4884/5916 UNKNOWN CAC0001111 - (jdeCacheDestroyAllUserCaches) Unterminated cache 2PWFD3 with 0 record(s), created from File=B0702395.c, Function=InitializePrevailingWageCaches, Line=314.
Nov 05 18:30:51.151023 - 4884/5916 UNKNOWN hCache:[2B68B9D8] Nm:[2PWADJ3] Recs:0 Curs:0 Hnds:1 Cchs:1 DESTROY
Nov 05 18:30:51.151024 - 4884/5916 UNKNOWN CAC0001111 - (jdeCacheDestroyAllUserCaches) Unterminated cache 2PWADJ3 with 0 record(s), created from File=B0702395.c, Function=InitializePrevailingWageCaches, Line=238.
Nov 05 18:30:51.151025 - 4884/5916 UNKNOWN CAC0001025 - Application code leaked 10 caches which were detected when freeing environment DV910 (EnvHandle 2B1B2510) for user JEREMEYG. Please refer to the debug log for details. If there are not enough details in the debug log to determine the cause, set Output=FILE in the [DEBUG] section of the JDE.INI and watch for this error message again. Or, set logCacheLeaksAtSignoff=TRUE in the [DEBUG] section of the JDE.INI and look for CAC0001036 error messages. This message (CAC0001025) will only appear with debug tools code or when debug logging is turned on.
Nov 05 18:30:51.152000 - 4884/5916 UNKNOWN The JDEMAIL library is disabled, function <JDE_CleanupMail> is not available. Please see SAR 6546021 for details, and contact support.
Nov 05 18:30:51.152001 - 4884/5916 UNKNOWN JDB4100006 - DP - While freeing the JDB environment, leaked data pointer (359B6B60), pointer handle (3), stored from File=B0702395.c, Function=InitializePrevailingWageCaches, Line=577.
Nov 05 18:30:51.152002 - 4884/5916 UNKNOWN JDB4100005 - Application code leaked 1 data pointers which were detected when freeing environment DV910 (EnvHandle 2B1B2510) for user JEREMEYG. Please refer to the debug log for details. If there are not enough details in the debug log to determine the cause, set DataPointerTracing=1 and Output=FILE in the [DEBUG] section of the JDE.INI and watch for this error message again. Or, set logDPLeaksAtSignoff=TRUE in the [DEBUG] section of the JDE.INI and look for JDB4100006 error messages. This message (JDB4100005) will only appear with debug tools code or when debug logging is turned on.
Nov 05 18:30:51.152004 - 4884/5916 UNKNOWN Enter JDB_FreeCriticalSections. count=6

I know JDE has this fixed in 9.2, but not in 9.1. We are not under support as we are slowly migrating to Cloud. Function B0702395 is called from B0700059 and 59 is the function fixed in 9.2/9.0 with 9.1 fix possibly coming out this week. Can someone help me out with what was fixed in 9.2 on the 59 function? We have third party support looking at this for us, but so far they haven't found the error. I believe I have everything fixed in R07932 with only the 59 piece left to fix. TIA.
 

BOster

Legendary Poster
An un-terminated jdeCache instance is not necessarily a leak. It depends on the design pattern. With some designs, like the sales order MBF main cache (UI01, UI02, UI11, UI12, etc.), the jdeCache instances are only terminated when the user logs out... which is perfectly acceptable - not my preferred design, but perfectly fine none the less. You can still leak resources however if records are not cleaned up after a transaction but from the log above it looks like all of the cache instances had zero records when the cache instance were destroyed. The one that did have a record may be by design and not indicative of an error - again depends on the design pattern. Even if you were leaking resources in jdeCache, unless you run out of memory that, in and of itself, should not cause a problem.

The one jdeCache resource that IS a problem if leaked is jdeCache cursors (nothing in the log above indicates this situation btw). There are a fixed number of cursor per cache instance and if these are leaked you can get failures. When I see errors that happen after xxxxx number of transactions, I usually look for some type of jdeCache cursor leak. The other leak (which is not necessarily related to jdeCache) which can cause issues is leaking pointer handles via the api jdeStoreDataPtr/jdeRemoveDataPtr. This is an even worse leak because a leak in one application can break a completely different application. There is some indication of this type of leak in the log you posted.

Nov 05 18:30:51.152002 - 4884/5916 UNKNOWN JDB4100005 - Application code leaked 1 data pointers which were detected when freeing environment DV910 (EnvHandle 2B1B2510) for user JEREMEYG. Please refer to the debug log for details. If there are not enough details in the debug log to determine the cause, set DataPointerTracing=1 and Output=FILE in the [DEBUG] section of the JDE.INI and watch for this error message again. Or, set logDPLeaksAtSignoff=TRUE in the [DEBUG] section of the JDE.INI and look for JDB4100006 error messages. This message (JDB4100005) will only appear with debug tools code or when debug logging is turned on.
Nov 05 18:30:51.152004 - 4884/5916 UNKNOWN Enter JDB_FreeCriticalSections. count=6
This may be a symptom or a cause or completely unrelated. May be something to look into though.
 
Top