| Weird error while trying to start RCP Client using Webstart jnlp [message #1837974] |
Thu, 11 February 2021 15:05  |
 Michael Frank
Messages: 13
Registered: February 2021 |
Junior Member |
|
|
If this is better situated in the e4 Forum let me know.
I built a minimal RCP Client using https://github.com/ECF/JaxRSProviders to call server endpoints. The client is feature based and built using tycho. Targeted execution environment is Java 8.
The client starts from Eclipse without any issues.
When I tycho build the client and use the generated launcher.exe the client starts.
I then tried to write a jnlp that includes all plugins from the plugin directory and I test locally, the client doesn't start and the log gives me weird looking errors like this
!SESSION 2021-02-11 15:39:35.838 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.8.0_251
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE
!ENTRY org.eclipse.osgi 4 0 2021-02-11 15:39:36.924
!MESSAGE Bundle reference:file:C:\Users\mfrank\AppData\LocalLow\Sun\Java\Deployment\cache\6.0\26\c761f9a-7b002a49null not found.
I say weird because of the "null" that is attached to the filename. Anyone have a pointer on what might be causing this? I think that all other errors in the log are caused by this.
I checked the cache directory and the referenced file is there, of course without the "null" at the end.
Additional information:
In my jnlp I set osgi.bundles by using the same bundles that are also present in the config.ini. I added also all the bundles mentioned at https://wiki.eclipse.org/Eclipse4/RCP/FAQ#Why_won.27t_my_application_start.3F
I use the same startlevels as the config.ini. I checked, that the same startlevels and plugins, that are used in my eclipse runconfiguration are also present in the osgi.bundles.
Because of changes in Java 7 and because I can't use jnlp signing I use a wrapper jar that takes all properties of my jnlp that are prefixed with jnlp. strips them of the jnlp. and sets them again. This wrapper works fine with a much older e3 based client.
If necessary I can provide the jnlp and other logs. I'll attach a full log of an attempted run. You'll see that there are a lot of bundles, that can't be resolved. For me this looks like that none of the bundles mentioned in osgi.bundles are being picked up but I'm not sure. I can also provide other logs and even tracelogs if necessary, just let me know what you need 'cause I'm pretty stumped.
After any change to the jnlp and the plugins I make sure to clean the cache. All jars are signed. The jnlp is not signed. I also tried signing it but this gives me the same error.
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03470 seconds
] 
Search
Help
Register
Login
Home
