×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Ken
A crazy thought from the chosen frozen here in Minnesota!
There is another graphical debugger that works much like the one in RDi
- it's part of the IBM Toolbox for Java, also known as JTOpen. There is
documentation in KnowledgeCenter for IBM Toolbox for Java, and it has a
section on the IBM Graphical Debugger.
There is no connection to source in RDi, so that could be a drawback -
in other words, if you set a breakpoint in RDi, I don't expect that this
debugger would know about it.
But since debugging is maybe one of the main reasons you have these
lockups, this could be an interim solution. And you'd get another Java
app to have heap problems, eh? Heh! Could not resist that one!
The other Ken mentioned turning on a heap indicator - maybe that'd be
worth a try if you stay with the RDi debugger - and make it easier to
say how to duplicate the problem when you report it to IBM - one can
submit issues with RDi, I believe. If you have RDi through Passport
Advantage, you can maybe do it directly. If as the licensed product, as
we have it, then however you submit PMRs for other stuff would be the
pathway - I don't have direct ability to do that here, it has to go
through our systems guy.
HTH
Vern
On 9/4/2015 7:38 AM, Ken Killian wrote:
That could be it...
RDI works great, as long as I do not use debug. About 95% of the time it flawless! But, that 5% can painful, especially when you are in the "zone", and then it happens. It locks ups, unexpected results.
-snip-
midrange.com
