× 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.



Hi Ken,

When the Heap becomes too high RDi will slow down or become un-responsive. I'd suggest turning on the heap status monitor by going into the menu Window > Preferences > General and select the Show Heap Status. Your heap memory will display on the status bar.

I'd suggest closing the editor tabs before you reach max heap size. Closing the editor(s) will free memory that the java garbage collector isn't able to. To close all open editors you can right click on a tab and select Close All. There are other handy options like close others if you want to keep one in place.

The Thread Death is how the Live Parse is cancelled and is not the cause of your slowdown. If you notice any anomalies in the outline view (duplicate labels or unexpected branches), it may help diagnosis the root cause. Also, if you notice each time you do "X" the heap climbs and doesn't clean up, please provide that information to IBM support so they can add it to your PMR.

Steve Ferrell

-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxx> On Behalf Of Ken Killian
Sent: Thursday, August 9, 2018 4:28 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: [WDSCI-L] RDI 9.6.0.4 LOCK-UP. Java Death-Thread!

Hi,


Using Junk-ware called RDI 9.6.0.4 with blasted parsers errors and LOCKING up! <Sad>

CANNOT CLOSE member, nor resize members? <Sad>

Luckily, SEU does NOT LOCK UP! EVER! That is ENTERPRISE Stable Software!<Joy Joy>


How in the world do I show that I cannot close "views" or "resize"? This on my Desktop with 8-cores 3.7 GHZ. So it is not a lack of HORSE-POWER. nor lack of memory, no hard-disk speed. SSD 500Gig!

What in the heck is a Java Death Thread?

org.eclipse.rse.ui
Error
Thu Aug 09 14:29:22 EDT 2018
Exception when parsing MCDTOIRI.SQLRPGLE

java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:1008)
at com.ibm.etools.iseries.edit.language.model.LiveModelSupport.dispose(LiveModelSupport.java:331)
-----------------------------------------
org.eclipse.rse.ui
Error
Thu Aug 09 15:49:04 EDT 2018
Exception when parsing MCMC23RL.SQLRPGLE

java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:1008)
Etc... Much too long for a post here...

------------------------------

com.ibm.lpex
Error
Thu Aug 09 16:18:42 EDT 2018
Uncaught exception in class "com.ibm.etools.iseries.parsers.ISeriesEditorRPGILESQLParser". Document parser was disabled.
!VIEW ...

java.lang.NullPointerException


If IBM cannot fix the parser, they NEED TO REMOVE IT! yet, I was told it was okay to turn it back on. Off it goes. I much rather have an editor that does NOT LOCK, than have fancy "Code-Assist". That is WORTHLESS if it locks up the editor! Junk ware!

When does the next "so called" fix-pack come out?

PS. I need a WHOLE bag of SNICKERS! <Sad> I was forced to kill RDI-Junkware TWICE. <Sad> Fell-back to RELIABLE SEU. That NEVER FAILS! <sad>



--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/wdsci-l.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.