ODBC (qzdasoinit) memory GUSH!

[Steven.Gray@xxxxxxxxxxxxxx]

Larry,

I know this does not answer your question as to why the leaks under 5.2 but
you could limit the leak.
The QZDASOINIT connection to the AS400 runs under a user profile , on my
system QUSER. Now you can limit the amount of storage QUSER can use ,
MAXSTG within the user profile.

Also instead of IPL'ing the system you could just recycle QSERVER subsystem
, which would terminate any remaining QZDASOINIT jobs.




> Upgraded a client to V5R2. Existing Java application running on a Linux
> server 
> opens (and keeps open) 40-50 connections to iSeries for DB access, about
> 99 to 
> 1 reads to updates. This was running for months on V5R1 just ducky. Now it
> 
> leaks like an old boat. 40+GB per day! Many of the QZDASOINIT jobs have
> over a 
> Gig of temporary storage after 12-14 hours!  Shutting down and restarting 
> tomcat on the Linux side frees about 75% of the memory each time as the 
> attached qzdasoinit jobs get cycled. Of course the 25%s add up and are
> causing 
> us to IPL daily at this point.
> 
> We have every PTF that even seems remotely applicable. IBM Has connected
> to 
> the box and are declaring "you need consultline, must be a coding problem
> on 
> your end." Needless to say this is NOT the right answer and will not be 
> accepted. Has anyone out there seen leaks in these jobs at V5R2 or found a
> way 
> to fix them??
> 
>   Thanks
> 
>     - Larry
> 
> 
Regards

Steven Gray
Development/Support Analyst
Business Solutions IT

Tel:    +44 (0) 870 4194639
Fax:    +44 (0) 870 4194948


________________________________________________________________________
Messaggio controllato da MessageLabs SkyScan ed esente da virus.
________________________________________________________________________