Hi,
We can't start our application anymore, errormessage is
"Could not initialize application. The application has not been initialized, for more information execute javaws from the command line."
Message in the logfile is:
Caused by: net.sourceforge.jnlp.LaunchException: Fatal: Application ...
Search found 7 matches
- 08 Jun 2023, 16:07
- Forum: Public Forums
- Topic: Application Error: The signed JNLP file did not match the launching JNLP file.
- Replies: 2
- Views: 23512
- 18 Aug 2022, 10:34
- Forum: Installation & Configuration
- Topic: Default Open JDK
- Replies: 5
- Views: 56986
Re: Default Open JDK
Thanks for this post, I save the same question :)
I now did this: I added an OpenJDK 18.0.1.1 to the JVM:
ows1.png
Set update strategy to "Never":
ows2.png
Version in JNLP is 18.0.1.1:
<j2se initial-heap-size="256m" max-heap-size="768m" version="18.0.1.1"/>
Result: Warning in logfile ...
I now did this: I added an OpenJDK 18.0.1.1 to the JVM:
ows1.png
Set update strategy to "Never":
ows2.png
Version in JNLP is 18.0.1.1:
<j2se initial-heap-size="256m" max-heap-size="768m" version="18.0.1.1"/>
Result: Warning in logfile ...
- 27 Jul 2022, 15:23
- Forum: Public Forums
- Topic: problem with log4j2
- Replies: 14
- Views: 52551
Re: problem with log4j2
log4j 2.18 is released and the problem is solved.
Thanks to hilalkale who found that this problem didn't appear in a 2.17.3 snapshot, finally we just waited for the 2.18 release
Thanks to hilalkale who found that this problem didn't appear in a 2.17.3 snapshot, finally we just waited for the 2.18 release
- 14 Feb 2022, 15:33
- Forum: Public Forums
- Topic: problem with log4j2
- Replies: 14
- Views: 52551
Re: problem with log4j2
Hi and sorry for the delayed answer
.....
Could it be that you have old and new versions of Log4J classes in the jars that you are specifying in your Jnlp file?
Don't think so - I had a look in all the cached jar files and I found only the new log4j version in the jars
...
Can you please ...
.....
Could it be that you have old and new versions of Log4J classes in the jars that you are specifying in your Jnlp file?
Don't think so - I had a look in all the cached jar files and I found only the new log4j version in the jars
...
Can you please ...
- 27 Jan 2022, 11:14
- Forum: Public Forums
- Topic: problem with log4j2
- Replies: 14
- Views: 52551
problem with log4j2
Hi,
We upgraded the logging in our application from log4j 1.x to the newest 2.17.1 version and now we get errors with OpenWebstart.
Exception is below - log4j-core-2.17.1.jar and log4j-api-2.17.1.jar are in the jnlp and they are loaded. PluginAliases is part of the core-jar. Is this a known ...
We upgraded the logging in our application from log4j 1.x to the newest 2.17.1 version and now we get errors with OpenWebstart.
Exception is below - log4j-core-2.17.1.jar and log4j-api-2.17.1.jar are in the jnlp and they are loaded. PluginAliases is part of the core-jar. Is this a known ...
- 22 Jul 2021, 15:44
- Forum: Public Forums
- Topic: Wrong menu entry on Mac OS
- Replies: 2
- Views: 7325
Re: Wrong menu entry on Mac OS
Thanks for your reply. I forwarded this to our customers who are interested in OpenWebstart
- 20 Jul 2021, 16:37
- Forum: Public Forums
- Topic: Wrong menu entry on Mac OS
- Replies: 2
- Views: 7325
Wrong menu entry on Mac OS
Hello,
We're currently testing OWS with our Java application and we have a few issues on Mac OS X. One is: The first menue entry (usually the Application name) is not correct. Instead of "JournalDesigner" I see "BOOT" and we didn't find a way to solve this.
This problem is on different Macs ...
We're currently testing OWS with our Java application and we have a few issues on Mac OS X. One is: The first menue entry (usually the Application name) is not correct. Instead of "JournalDesigner" I see "BOOT" and we didn't find a way to solve this.
This problem is on different Macs ...