Hello,
at the moment we are testing our application on 12.2.1.3 running on Linux
Whenever there is an unhandled exception in a trigger we get

We would expect (as in our current version 11.1.2.2.0) that the exception is caught later in the process and a message is shown to the user.
The code in this trigger only calls a procedure (one line of code). Remote debug shows that in line 2 (?) some magic happens and the alert pops up at the client.
The Java console shows:
basic: JNLP2ClassLoader.findClass: oracle.forms.handler.DialogThread: try again ..
basic: JNLP2ClassLoader.findClass: oracle.ewt.alert.resource.AlertBundle: try again ..
basic: JNLP2ClassLoader.findClass: oracle.ewt.alert.resource.AlertBundle_de: try again ..
basic: JNLP2ClassLoader.findClass: oracle.ewt.alert.resource.AlertBundle_de_DE: try again ..
basic: JNLP2ClassLoader.findClass: oracle.ewt.alert.resource.AlertBundle_de_DE: try again ..
network: Cacheeintrag nicht gefunden [URL: http://orafe.example.com:9001/forms/java/oracle/ewt/alert/resource/AlertBundle_de_DE.properties, Version: null]
network: Verbindung von http://orafe.example.com:9001/forms/java/oracle/ewt/alert/resource/AlertBundle_de_DE.properties mit Proxy=DIRECT wird hergestellt
basic: JNLP2ClassLoader.findClass: oracle.ewt.alert.AlertRowLayout$Enum: try again ..
basic: JNLP2ClassLoader.findClass: oracle.ewt.lwAWT.lwWindow.LWWindow$MouseGrab: try again ..
Any idea what might be wrong?
Edit: Client Java Version 1.8.0_144-b01
Regards
Marcus