I'm running Ignition (version 8.1.47) on a Windows machine where both the Vision Client and the Designer Client are used locally.
When connecting to the same machine via RDP (Remote Desktop), using the same Windows user account, and verifying that the session ID remains the same (via query session), both the Vision clients and Designer close immediately upon RDP login.
The local user is not logged off.
We are not using mstsc /admin as the connection is via an RDP server.
Other applications like SSMS, notepad etc. do not close on connection.
Has anyone experienced similar behavior? Is there a known workaround to prevent Ignition from closing when reconnecting via RDP?
You are right — it does sound like a similar problem to the one you're referring to. Just to be clear: when I log on to the RDP server, I open 'Remote Desktop' on the server itself. So, where should I look for the hs_err_pid file?
You mean you open the Remote Desktop app on your local PC but log in to the server?
Anyway, they might be hanging around in the user home directory on the server (whatever PC is actually running the Designer and Client), and you might need to use Windows' awful file search to see if you can find some lying around elsewhere.
Yes, to be more precise: when I work remotely, I first connect to an RDP server. From there, I open the Remote Desktop app on the RDP server itself to connect to the Ignition machine, which is on a closed network. So it's a two-step RDP chain.
I tried reproducing the issue and managed to generate four hs_err_pid log files, all with the same minute timestamp. They were located in the user home directory on the Ignition machine. Each file starts with the following header:
A fatal error has been detected by the Java Runtime Environment:
EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ff93c20bbc6, pid=15672, tid=23712
JRE version: OpenJDK Runtime Environment Zulu17.54+22-SA (17.0.13+11) (build 17.0.13+11-LTS)
Java VM: OpenJDK 64-Bit Server VM Zulu17.54+22-SA (17.0.13+11-LTS, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
Problematic frame:
C [awt.dll+0xdbbc6]
So it does look like the Java runtime is crashing under certain conditions. Interestingly, in one test, only the Designer I last interacted with stayed open — all other Ignition apps closed. In other cases, everything shuts down.
Let me know if you'd like me to share the full contents of one of the logs or if there's anything specific I should look for in them.
Odd...i use the exact process...I connect to a customers VPN, use RDP to their jump server, then RDP to their ignition server. Two step RDP hop, and no issues like youre experiencing. Dont have much to offer, other than to confirm its possible. I didnt do anything special with the RDP settings. In one instance im using my own local account on the ignition server, in another, im using a shared account. If that user has designer ipen when i connect, it doesnt shut down.
We do need the full hs_err_pid file if we're going to open a bug report with Azul, but I am hopeful this is basically the same bug or root cause as the one I linked and if so, it will be fixed with the Java update (JDK 17.0.15) included in Ignition 8.1.49.
I see 8.1.49 was released yesterday. I also had this RDP issue after upgrading from 8.1.43 to 8.1.47 and 8.1.48 on several gateways. The Clients and Designer Sessions would crash on RDP log in (or log out not sure which). I will attempt a few tests today to see how it goes.
I had one designer from a gateway running 8.1.47 open and one with 8.1.49 open on my Cloud PC. I disconnected from the CPC. After reconnecting the designer running 8.1.47 crashed and disappeared. The designer running 8.1.49 was still there! I will keep testing but I’d say this is, in fact, fixed now with the release of 8.1.49.
Now I need to perform more dev tests with 8.1.49 on all my other gateway types to make sure I don’t introduce any new bugs with this version. However, as stated in the release notes, this release was focused more on bug fixes than new features so we’ll see.
In case it matters for your planning… we’re planning a quick follow up 8.1.50 release that contains only JDK and JXBrowser (Chromium) version updates. These updates fix CVEs that don’t affect Ignition directly but drive everybody’s security software bonkers. Because they don’t directly affect Ignition we didn’t want to delay the release of 8.1.49.
Thanks for testing this. I don´t know how you connect to a Cloud PC, but I believe it’s similar to using RDP to a physical PC. I’m not currently able to verify that this checks out, but my best guess is that upgrading to 8.1.49 fixes the problem.
The connection/process is very similar to RDP. I have a Windows CPC and you have to use an app called Windows App now, (image 1). Microsoft used to have an app called Microsoft Remote Desktop that looked like image 2 below, but they sunset that already. That was the previous way I used to connect and it was exactly like the traditional RDP method but you could store/save connections with credentials. It’s a whole mess but you cannot use Windows Apps to RDP into traditional Servers, only CPC's but that limitation only exists when running on a Windows PC. If you have Android, iOS, or MacOS, you can use the Windows App to rdp to CPC's and traditional local/cloud servers. There are some fun reddit posts about this topic and how hilarious it is that MS would make a product that doesn't fully work on a Windows device but does on other platforms.
