Re: ODBC (qzdasoinit) memory GUSH!

Why does IBM pull that crap?  It worked fine on v5r1 and now it doesn't
on v5r2?  And all they can say is "it must a coding problem"?!?!?

One would think IBM would at least try to duplicate the problem on
their side - a v5r1 test, then upgrade the box to v5r2.

Oh, stupid me, I forget, IBM makes most of their money on SERVICES! 
D'oh!

Larry, maybe you should have your client make some noise over on
iSeries Nation.  Anne Lucas has been known to intervene on a customer's
behalf.  Can't hurt to try.

- Dan

--- Larry Bolhuis <lbolhuis@arbsol.com> wrote:
> 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


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com