|
rpg400-l-request@xxxxxxxxxxxx wrote: > 4. Re: RPG/Java memory leaks? Possible? (Brad Stone) > >While the issue isn't with my application (sockets work >just fine) I am willing to try anything so that the other >ISV will quit stalling and debug their application. Brad... There must be _some_ kind of issue with your app because you originally wrote: |>When they call the encryption app alone, it works fine. |> |>When they call GETURI, then call they encryption app it |>works fine the first time. Any subsequent calls to the |>encryption app returns bogus data only if they follow a |>call to GETURI. But GETURI still funtions fine. This is |>only if done in the same job. That is, after your app runs the second time, the other app has trouble and the other app has trouble only after your app runs. (Hmmm... and only after the second time?) Now, that in no way means your code is definitely incorrect. It could be a PTF issue; it could be a compiler options issue; it could be all the things we've all seen that happen outside of the coding realm. But in some way, the other app can tell that your app ran first. _Something_ is being affected and left behind _because_ your app has been run; your app is somehow touching something the other app relies on. Perhaps you're calling the regular expression functions and somehow hitting a bug in the way those things create their references. (Not your fault, but... maybe they're also calling them?) Perhaps you're calling iconv APIs and somehow triggering a previously undiscovered bug from those. Perhaps a whole bunch of possibilities. But your app is leaving a... ummm... "warp signature"... that's disturbing the hyperspace that certain later instructions execute within. I'd start looking closely at any less common APIs that I might be using and see if the other ISV has any ideas about them. >This is pretty much the last thing they've thrown at us >along with a PTF that looked like it was for /free RPG >programs and chaining to files with 2 or more keys. (????) > I may have looked at the wrong PTF.. but that's what it >looked like. :) Unfortunately, unless every superceded PTF is reviewed in such a way as to determine which compiler modules were affected, etc., it probably doesn't matter what a given PTF claims to fix. I've sure seen enough that _apparently_ had nothing to do with my problem but fixed it anyway. >Support these days... well, it just isn't what it used to >be. Sigh, ain't that the truth. Support especially for ISVs ought to be much better. In this case, I'd love to see IBM just take ownership of the problem and do all necessary mediation. I'm usually well satisfied with what I get, but it often isn't much. OTOH, I like the support _from_ an ISV such as you try to give. I've always tried to give free bug support for anything I've supplied. Enhancements may be costly, but bugs simply need to be eliminated. Tom Liotta -- Tom Liotta The PowerTech Group, Inc. 19426 68th Avenue South Kent, WA 98032 Phone 253-872-7788 x313 Fax 253-872-7904 http://www.powertech.com __________________________________________________________________ Switch to Netscape Internet Service. As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register Netscape. Just the Net You Need. New! Netscape Toolbar for Internet Explorer Search from anywhere on the Web and block those annoying pop-ups. Download now at http://channels.netscape.com/ns/search/install.jsp
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.