This content has been marked as final. Show 3 replies
910396 wrote:Red flag: it is not consistent, in other words it is system dependent. It is already hard for you to diagnose such an occurrence, I wouldn't expect anything more by asking in a forum. At least you have SOME way of doing some more diagnosing.
This happens only on particular customer systems (servers as well as desktop machines)
I'm sorry, but you'll have to dive in deep. Figure out what update versions of Java the failing machines are running. Which OS. Which processor architecture. Etc. See if there is a common factor involved. If not, hunt through release notes of newer JDKs to see if any of them mention something related to the splash screen and if you find something, let the client attempt an update of the JDK on such a failing machine to see if the problem is remedied. If it is windows, try running with the server VM (java -server) in stead of the default client VM, if you are not already doing that.
And yeah if all that fails and nobody else has something to add, I'm sorry to say that Oracle support will be your next logical step.
910396 wrote:What does that mean exactly?
This happens only on particular customer systems
Do you have many different customers?
And this failure is only occurring on one of those customers?
Yes, we have many different customers with individual installations of our Java-based system. In some of those installations the Java virtual machine cannot be loaded as I described above. That problem can only be fixed by either reducing the -Xmx parameter by a certain amount (which is also not consistent from installation to installation, in some installations reducing 100 MB is sufficient, in others 300 MB reducing is required) or by completely deactivating the splash screen.