Re: Possible 9.9.0.4 issue

Hi Steve,



We are using RPGLE here, no Cobol.  Turning off the (performed on server) SQL syntax checking has stopped the RSE daemon errors from popping, and I can live without that anyhow.  The slight delay of that particular syntax check always annoyed me anyhow.  Isolating it to a single option is good enough for me on this issue.  I will just keep it disabled.



FYI - I do not think the SQL Syntax checking is related to my random IDE exits.  I have had the SQL syntax checking turned off since Friday, and this morning I had a random exit while waiting for Events to be returned for a compile.  The compile finished fine, but the IDE dumped.  No error messages, but I do see core/javacore/jitdump/Snap files were generated at about the exact time.  From the javacore.txt it looks like a Stack Overflow error, but not sure exactly how to tell what actually caused it based on what I am seeing in the file.  This started happening around 9.8.


Thanks as always for the feedback,

David






From: Steve Ferrell via WDSCI-L <wdsci-l@xxxxxxxxxxxxxxxxxx>
To: "Rational Developer for IBM i"<wdsci-l@xxxxxxxxxxxxxxxxxx>
Cc: "Steve Ferrell"<steve.ferrell@xxxxxxxxxx>
Date: Mon, 13 Jul 2026 06:32:22 -0700
Subject: Re: [WDSCI-L] Possible 9.9.0.4 issue



Hi David,

Our company turned off the ability for the RSE call back years ago. There are 2 levels of Automatic syntax checking, we usually turn off the (performed on the server) one, but I turned it on this morning with the RSE daemon not starting and it seems to be working for me.

When the JVM dumps it generates a stack and usually an error.

When the PV or Syntax checker crashes, it can take the UI down without an error.

Is it RPG or COBOL?

We've turned off the COBOL Automatic Syntax checking for this reason. There are some Known Issues that can cause the PV or Syntax checker to crash RDi.

-----Original Message-----
From: WDSCI-L < mailto:wdsci-l-bounces@xxxxxxxxxxxxxxxxxx > On Behalf Of David Wright
Sent: Friday, July 10, 2026 9:54 PM
To: Wdsci L < mailto:wdsci-l@xxxxxxxxxxxxxxxxxx >
Subject: [WDSCI-L] Possible 9.9.0.4 issue

External: Pause and review the sender's email address, any URLs before clicking links, opening attachments, or following requests. When in doubt, contact the Service Desk.


Hi All,



I have just started seeing "The RSE communications daemon could not be started." whenever I edit SQL statements. Maybe a coincidence, but this seemed to start happening right about the same time I applied the new fix pack. I check the port it says it cannot access, and the only app using the port is RDi. It is always in the low 4300s... Usually a system restart will make it work for a while. Disabling SQL syntax checking also seems to bypass this error.



Anyone else seeing this?



Possibly related, I am still seeing unexpected hard closures of RDi, usually as compile results are coming back to the Event Viewer (but I do not think it is only at this time). No java error, just RDi disappears. I have done totally clean reinstalls of everything except Windows itself, but this still happens intermittently. Wondering if the crashing RDi might be keeping the daemon active somewhere, locking the port.



If there is anything I can do to help isolate this, please let me know.



Thanks!

David