Re: RDI 9.6.0.4 LOCK-UP. Java Death-Thread!

Plugin interference is not unimaginable. For example, the parser doesn't
just look at your source code. It pulls in external definitions. Lets say
some plugin overrides your connection's library list somehow outside of
RDi knowledge. It is conceivable that this would interfere, even
indirectly, with parser functions. I'm not saying this is the cause, or
that this is even happening. I'm giving an example of why you shouldn't
discount plugin interaction in the parser issues you're seeing. The parser
is also capable of annotating issues in your source. A number of plugins
also do annotations. Here is another source of possible conflict.



___________________________________
Darren Strong
Dekko





From: "Ken Killian" <kkillian@xxxxxxxxxxxx>
To: "Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>
Date: 08/10/2018 11:55 AM
Subject: Re: [WDSCI-L] RDI 9.6.0.4 LOCK-UP. Java Death-Thread!
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>



Darren,

Wow, I would not expect any plug-in to affect the parser.

I only know I turned off live parsing, and my errors go away.

Same thing in previous releases, turn off the parser, and lockup go away.

I actual really hate SEU with a passion! But it reliable. I have been
actively using RDI full time for over 12-years in my 28-year rpg career.

I am Big fan of using an professional IDE / RDI. But, it should not lock
up when typing in code. Not even ONCE!

My source code is defined with a length of 262, instead of the typical 112
length. I have to use RDI to edit my code. <Big Proud Smile>

It cracks me up, RDI is a plugin to eclipse.

I will miss outline view & code assist greatly. But, it is better than
lockups! So, for now, I will keep live parsing turned off.

PS. I really need to find a way to duplicate these problem scenarios. Just
like I fix my programs with "repeatable scenarios". We need the same thing
to fix minor RDI bugs. I still need a "Monitor Camera", not sure if that
would be allowed at work. <LOL>

-Ken Killian-


-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxx> On Behalf Of Darren Strong
Sent: Friday, August 10, 2018 10:56 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] RDI 9.6.0.4 LOCK-UP. Java Death-Thread!

I've been seeing an issue with a couple plug-ins, and the parser. I'd
opened a PMR and a support ticket with one of the plug-in vendors, but
neither team could conceive of the issue being on their end. Reinstalling
seemed to help for awhile, but the issue has returned. My point is, watch
your plugins. If you're considering SEU, then at least run RDi for awhile
without any plugins, and see how it performs that way as a test.

___________________________________
Darren Strong
Dekko





From: "Ken Killian" <kkillian@xxxxxxxxxxxx>
To: "Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>
Date: 08/09/2018 05:29 PM
Subject: [WDSCI-L] RDI 9.6.0.4 LOCK-UP. Java Death-Thread!
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>



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>