Skip to Main Content
Forums

Java SE (Java Platform, Standard Edition)

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

JRE 8u121 and 8u131 App-V Virtualization and JNLP issue

3480315Jun 8 2017 — edited Apr 17 2018

Hello,

We use App-V to distribute JRE to our XenDesktop users in Citrix enviroment.

Everything was working fine until we updated our app-v package from JRE 8u91 to 121. Applications that are using JNLP stopped working. They are not launching at all, Java splash screen appears for few seconds and after that... nothing. I have monitored processes. Under 8u91, 2 instances of javaws and one instance of jp2launcher is started. For 8u121 there is only one instance of javaws that gets closed after around 10 seconds without any output, no errors, nothing. I have tried to start few apps using javaws.exe -verbose app.jnlp and to enable tracing but no .trace files are created under u121 or u131.

  • It is working as expected when 8u121 is installed locally, only under app-v it's causing problems

  • It doesn't matter if i use x86 or x64 bit version of JRE
  • Interesting thing is, that with 8u131 and 8u121 I'm not even able to start
    javaws.exe -viewer (but i can do it using Java Control Panel GUI)
  • I prepared few app-v packages of different x86 an x64 JRE versions, all sequenced on the same machine following exactly same procedure. For 8u11 u45 and u91 that i have tested JNLP is working fine. For 8u121 and 131 we have that described behavior.
  • I have tried this also on different machines (win 7 and win 10)
  • I'm not specifying any particular applications that are affected because this can be reproduced using ANY application that is using JNLP to start 
  • As I mentioned, it was working fine with app-v sequences with JRE 8u91 and below, so something got changed in recent updates and it looks like app-v doesn't like it

Comments

9d41c51d-4873-45b5-88ab-af0f333ab216

Hi,

I have nearly the same issue, but from another perspective.
Since Update from 8.121 to 8.131 neither the Java verify nor JPNL Applets are working anymore.
JavaScript and Java as local interpreter is working as expected.

Symptoms are like this:

1. start internet explorer 11

2. browse to website (e.g.: https://www.in-manager.arcor.de/INManager/pwd )
3. IE freezes.
4. open Task Manager
5. You can see a single instance of jp2launcher.exe running idle.

6. killing the process unfreezes internet explorer but w/o loading the applet of course.

I tried to build a new virtual machine using opera and firefox under Linux, but with the same behavior.
Is this related to the discontinued NPAPI support?

br

Carsten

Radek Rehorek

Hi. Exactly the same problem with our Java application in our company's environment. Latest working JavaWS was from Java 8 update 92.

I tried many times sequence App-V package, tried to monitor processes, but no luck.

Today I found there is new Java 8 update 141 out, so I'll try it.

Radek Rehorek

No progress in Java 8 update 141. The same behavior.

Radek Rehorek

Java 8 update 144 is out, no change

2ecd0036-1b34-4c1e-8f65-3c05293fc66a

I am having exactly the same issue. Is this problem being looked into by Oracle? This is causing serious issues here now.

3480315

No update from my side so far. I'm working with a person from MS support trying to solve that. So far we had to include java in our base Citrix/XenDesktop image.

Joe_

Exact same problem here... java pops up for a couple seconds, tries to load then closes down. Works fine when running java apps within Internet Explorer itself.

3480315

Ok, I just tested this with latest JRE 9 Early Access build. Works like a charm.

Tested on win 7 machine with all updates, App-V client HF09. But I'm pretty sure it will work on app-v 5.0. Sequenced to VFS. No additional settings like COM integration.

jre9eaappv.png

Joe_

I had the same issue, when i packaged this i packaged it using a PVAD pointing to the Local App Data folder (excluded local app data folder in the ui before sequencing) and then also installed java to the same local app data folder. Need to do some tidying up and test the exception site list but that got it working for me.

8981c429-54f4-4152-9ed0-fb2e02cceaf4

Has anyone found a fix for this issue, other than using JRE9?  We have the same problem and really need this to work with the latest java 8 client. 

5a4b79d5-6e1a-4fcc-a0e4-07d1525b7925

If you have not come across this site / documentation - you may find it useful.

This documentation addresses many of the general java issues w/ AppV.  The site has good insight on IE11 freezes and PVAD.

http://packageology.com/2014/02/sequencing-java-the-definitive-guide-part-1/

3480315
  • https://bugs.openjdk.java.net/browse/JDK-8194690
    Pardeep Sharma added a comment - <time class="livestamp" datetime="2018-02-22T02:06:29-0800">2018-02-22 02:06</time> - edited"Confirming that the adding deployment property - "deployment.security.use.insecure.launcher=true" resolves the issue. Verified with the versions where it has failed prior (JDK 8u102 b14, JDK 8u111 b14 and JDK 162). "
Confirmed, workaround is working fine !Adding deployment.security.use.insecure.launcher=true to deplyment.properties solved the issue. You can :
Remove localAppData from Exclusions prior to sequencing and edit the deplyment.properties in AppData\LocalLow\Sun\Java\Deployment during sequencing OR somehow edit the deplyment.properties in AppData\LocalLow\Sun\Java\Deployment for the existing package in local, not virtualized location (if localLow was in excludes) OR edit the global per machine in %windir%\Sun\Java\DeploymentMore on deployment.properties
https://docs.oracle.com/javase/7/docs/technotes/guides/jweb/jcp/properties.html

1 - 12
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on May 15 2018
Added on Jun 8 2017
#java-web-start-jnlp
12 comments
7,520 views