• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

WebStart

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am wondering if someone has any suggestions in how to work around this problem in webstart.
The problem happens if the user is running an application that was started using webstart. And the application is updated to a new version in the server. And then, the user starts another instance of the application while running the previous instance. Webstart fails to update the jars in the client, but it thinks that it has updated the jars for the new version.
Any ideas?
Thanks
 
Ranch Hand
Posts: 3244
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Alec
Welcome to the Java Ranch, we hope you’ll enjoy visiting as a regular however,
your name is not in keeping with our naming policy here at the ranch. Please change your display name to an appropriate name as shown in the policy.
Thanks again and we hope to see you around the ranch!!
 
Ranch Hand
Posts: 569
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Alec:
I am wondering if someone has any suggestions in how to work around this problem in webstart.
The problem happens if the user is running an application that was started using webstart. And the application is updated to a new version in the server. And then, the user starts another instance of the application while running the previous instance. Webstart fails to update the jars in the client, but it thinks that it has updated the jars for the new version.
Any ideas?
Thanks



Does the webstart throws any exception on launching when you start the second instance? If both the instances are running on the same box, chances are the first instance of the webstart might be using the jars, thus preventing the second instance from renaming the jars when it finds an update. I had come across a situation when my application did not exit gracefully(javaw process was still running even after closing webstart), and when I tried to launch the application again thru webstart, it thru a JNLP exception stating that it is unable to rename the jars. After removing the inital javaw process, the application was able to launch properly.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic