JDK-7130054 : Second instance of the jnlp application is not working
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 7
  • Priority: P2
  • Status: Closed
  • Resolution: Incomplete
  • OS: generic
  • CPU: generic
  • Submitted: 2012-01-14
  • Updated: 2012-02-29
  • Resolved: 2012-01-25
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7
7u4Resolved
Related Reports
Relates :  
JDK-6563938 - CouldNotLoadArgumentException when starting an updated JWS application
Description
When a user tried to  launch an application by "single click" from a JNLP link, the application launches properly. But when a user did double (or multiple) clicks on the link and if time interval between first and second click is very small(say less than one sec) the exception happens.

The problem is not reproducible locally, i.e. the customer was unable to create a test case. This is reproducible on the customer side (access can be provided by a special request).

The customer provided all screenshots, steps and logs how the problem was reproduced.

#1:Single Click (successful)
 
See each step description in the file Single_click_steps.gif
Please, find the corresponding screen shots in Screen Shots.zip.

#2:Double Click (unsuccessful) 

See each step description in the file Double_cleck_steps.gif
Please, find the corresponding screen shots in Screen Shots.zip.
 
Also attaching trace logs and console logs for the test performed (Logs.zip).
Comments
EVALUATION Tried reproduce with a batch file launching 2 instance of a similar webstart app that always relaunch. Could not reproduce. Noticed that the relaunch command line use the original URL, not the cache file as argument. Requested customer to try latest build of 7u4 to see if the problem fixed. If confirmed, will identify the CR or change list responsible for the fix so it could be backport if needed.
25-01-2012
EVALUATION Exception on the screenshots is not present in the logs. Possible explanation: 1) Application uses lots of custom properties => jvm need to relaunch 2) When we relaunch JVM we pass link to the JNLP file in cache 3) Launching second copy of app will update JNLP file in cache and possibly remove previous file 4) Removal at the same time as other copy of the app tries to relaunch leads to failure I am not sure same problem is applicable to 7 train but seem likely. Perhaps we should rely on "relookup" of file in cache for relaunch based on URL? This will not work for cache disabled scenario though. Or may be for relaunch we better create private copy of JNLP file (drawback - updates of app info will not be saved to correct place)?
16-01-2012