More details: By the way: our memory on one of the servers is 24 GB (physical) + 10 GB (swap).
It should be enough for 60 jBASE processes, should not it? We are exporting ldr_cntrl=maxdata=0x80000...@userregs in our .profiles. ulimit on test environment processes is: jsh t24fe ~ -->ulimit -a time(seconds) unlimited file(blocks) unlimited data(kbytes) 2097152 stack(kbytes) 4194304 memory(kbytes) unlimited coredump(blocks) 2097151 nofiles(descriptors) 4096 Kind regards Pawel Dnia 4-02-2009 o godz. 10:26 Pawel (privately) napisał(a): > Hi, > > I know that it sounds unbeliveable for most of you, but I would like to > share with problems that we started to face on our test servers about > 2-3 days ago. > > We started to run out of memory errors on our test servers, eg.: > jsh t24fe ~ -->jdiag > ** Warning [ PERFORM_ERROR ] ** > Unix error number 0 while attempting PERFORM , Line 111 , Source jsh.b > Trap from an error message, error message name = PERFORM_ERROR > Line 111 , Source jsh.b > jBASE debugger->q > Are you sure ?y > . > > We have several instances of some banking product on each test server. > We run batch processing (COB) on these test servers - usually 2-3 envs > in the same time on one, single AIX "test" server. > Our specificity is that we run these COBs using multiple agents - say 20 > processes, giving 60 agents in total (60 jBASE processes running in the > same time on one test machine). > > Today I was first time informed about problem and we have checked memory > allocation. It showed that we simply run out of it (physical and swap > runs out). > > We have also found out that some of jBASE (COB) processes are consuming > large amounts of memory, for example: > 16 eoyrx08 61482 633 (521) 1025 26K 9.38M 395K 6541 1212M 35m > 2 SLEEP tSA 8 (BATCH.JOB.CONTROL,593) > 26 t24ferx 503830 786 (776) 228 266K 12.2M 1.33M 1814 1321M 34m > 2 SLEEP tSA 7 (BATCH.JOB.CONTROL,323) > 28 t24ferx 430118 808 (799) 200 240K 17.6M 1.28M 1813 1200M 45m > 2 tSA 6 (BATCH.JOB.CONTROL,322) > > I know that somebody can start to suggest me that our local C/C++ code > is causing memory leaks. Please belive me that we do not run any C/C++ > code during batch processing. We have only 1 (MQ) library written in C > and interfaced (DEFC) to jBASE. It was done by external vendor and is > LIVE since 5 years. It was thoroughly tested few years ago against > memory leaks. You have to belive me, but this library does not run > during COB. It is used only by some online processes. > > Therefore I claim that something must be wrong with jBASE. My guess is > that jBASE does not free "transaction buffer" (does not downsize it once > transaction is finished). > > There are some (single threaded) jobs during our COB that create huge > transactions (eg. 900K changes in one transaction). It seems to me that > "changes" buffer is never downsized or this memory simply "leaks" > somehow. > > Does anyone face(d) similar problems? > > jBASE version 4.1.5.17 (Major 4.1 , Minor 5.17 , Patch 5690 (Change > 52756)), AIX 5.3.0.0-06. > > Kind regards > Pawel ---------------------------------------------------- Twoja rodzina na bliscy.pl Zobacz: http://klik.wp.pl/?adr=http%3A%2F%2Fcorto.www.wp.pl%2Fas%2Fbliscy.html&sid=628 --~--~---------~--~----~------------~-------~--~----~ Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24 To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en -~----------~----~----~----~------~----~------~--~---
