Multiple versions og Java Web start conflicts

I have a situation where the same Windows 2000 station will run 2 Java-web-started applications from different Java version (one being 1.3_x with an early 1.0.1_02 version of Java Web Start and the second the most recent 1.4 packages).
It seems that the installation of the any Java Web Start would overwrite the previous installation, the result is that only one application can work at a time.
Though, I have one developement machine where both applications can run simultenously, yet I do not know how that was achieved (maybe just fluke).
I tried to point the Java Web start to different path without success.
Any idea ?

Yep...JNLP is a file you configure a WebStart app in and one of the fields (j2se version) you specify what JRE(s) are acceptable. So, one can use 1.3 and another can use 1.4.
See http://java.sun.com/j2se/1.4.2/docs/guide/jws/developersguide/syntax.html if you want to see details on the JNLP syntax.

Similar Messages

  • How can I check what version of Java Web Start is installed on the client ?

    hi,
    Can anyone tell me how can I check what version of java web start is installed on the client and display a message if the client has not the good version ?
    I mean:
    I'd like all people running my application use java 5 and if someone using java 1.4 try to run the application get a nice screen telling him to download the latest version of Java Web Start.
    Is this possible ?
    Thanks in advance.

    Of course, I put this on my jnlp file,
    <resources>
        <j2se version="1.5+"/>
        <jar href="..... "/>
    </resources> But even with that, it doesn't display a nice message but a kind of exception instead.
    Thanks in advance.

  • Problem with CORBA application deployed using Java Web Start 1_6_0.

    Java Web Start fans and experts:
    We have been using Java Web Start to deploy the client side of a CORBA-based application since the inception of Java Web Start ... including Java Web Start 1.0 right up through the present.
    With Java Web Start 1_6_0, we see evidence that Web Start is "tinkering with" the IOR that CORBA uses to communicate. In all previous versions of Java Web Start, independent of the JRE which the application uses, the stringified IOR have been the same size regardless of whether the application is deployed locally or via Java Web Start. With Java Web Start 1_6_0, the stringified IOR is much longer than the "real" IOR (again, regardless of the JRE used by the application itself). To me this smells like a bug in Java Web Start 1_6_0. Has anyone else observed this behavior?
    Here are some specifics .... I've run the same client application with various JREs both with and without Java Web Start as the deployment mechanism. The application was compiled and runs against servers that are running JDK 1_5_0_09.
    Here is the summary of my results from a Linux box running various JREs, various versions of Java Web Start, and also running as a non-JWS deployed application. I've listed the length of the stringified IOR in each case.
    JRE 1.5.0 non-JWS client: stringified IOR length = 344
    JRE 1.6.0 non-JWS client: stringified IOR length = 344 ... this, I think, excludes the JRE as the cause of these problems.
    Java WS 1.5.0, JRE 1.5.0 JWS client: stringified IOR length = 344
    Java WS 1.5.0, JRE 1.6.0 JWS client: stringified IOR length = 344
    Java WS 1.6.0, JRE 1.6.0 JWS client: stringified IOR length = 1568
    Java WS 1.6.0, JRE 1.5.0 JWS cleint: stringified IOR length = 1568
    In all cases, the stringified IOR length is determined by the service receiving the message and is always running JRE 1_5_9_09 and is
    always the same 344 characters in length UNLESS it was deployed
    using Java Web Start 1_6_0, in which case it in nearly 5 times as big!
    To me, it sure looks as if there is a problem with Java Web Start 1_6_0 to be adding so much to the stringified IOR. Note: it's hard to tell how different the underlying IOR is in the JWS 1_6_0 case because, unlike most other ORBs, the Sun ORB doesn't have a tool to extract the IOR into a human readable structure. However, I can think of no good reason why the identical application deployed using Java Web Start 1_6_0 should have a stringified IOR length that is different than that of the same application deployed in non-JWS form or should differ from the behavior seen in all previous releases of Java Web Start.
    Any clues or suggestions? Has anyone else observed this behavior?
    Thanks,
    John

    Hi.
    I got a different problem. My Corba application works in JRE 1.6, but doesn't works in JRE 1.5.X. I got an unexpected error and my console shows:
    getSubjectX500Principal NoSuchMethodError: java.lang NoSuchMethodError
    #### Java Web Start Error:
    #### null
    Can you help me?

  • Mac OS 10.4.8 , Java Web Start and JRE version of 1.4.2 and 1.5.0 problem

    Hello,
    I've been searching internet and reading the problems related to Java Web Start and JNLP.
    But no solution I read can solve what I faced.
    I'm running Mac OS x 10.4.8 and Macintosh updates the Java in my machine so that it has Java version 1.4.2 and Java 1.5.0
    The application I'm running needs to be running in JRE 1.4.2.
    So I changed the Java Preferences so that the default Java setting is JRE 1.4.2. However, the JNLP application still running in Java 1.5.0
    So I changed the MIME and make sure the JNLP is opened with Java Web start instead. The Java Web start is for version 1.4.2. I also change its preference so that the console is opened.
    I tried to run the JNLP application once again. Java web start 1.4.2_09 starts and console open, but the Java Runtime is still showing Java 1.5.0
    I adjust the JNLP file so that the version is only showing 1.4.2_09 (ignoring all other variables of version 1.4.1, 1.4.2, etc found in the original JNLP file). That didn't work either.
    I search on methods on how to uninstall Java 1.5.0 in Mac - apple page told me that I can't do that unless I reinstall the whole OS.
    I am henceforth declare that I am stuck now !!!! Heellllpp....

    Are you up to date with the updates?
    Update for Snow Leopard users:
    Apple issued update 12 for Java for OS 10.6:
    http://support.apple.com/kb/DL1573
    Note:  On systems that have not already installed Java for Mac OS X 10.6 update 9 or later, this update will configure web browsers to not automatically run Java applets. Java applets may be re-enabled by clicking the region labeled "Inactive plug-in" on a web page. If no applets have been run for an extended period of time, the Java web plug-in will deactivate.
    If, after installing Java for OS X 2013-002 and the latest version of Java 7 from Oracle, you want to disable Java 7 and re-enable the Apple-provided Java SE 6 web plug-in and Web Start functionality, follow these steps:
    http://support.apple.com/kb/HT5559?viewlocale=en_US
    Further update:
    Apple issued this Java related security update No. 13 on February 19:
    http://support.apple.com/kb/HT5666
    and Update No. 14 on March 4:  http://support.apple.com/kb/DL1573
    http://support.apple.com/kb/HT5677
    The standard recommendation is for users to turn off Java except when they have to use it on known and trusted websites (like their bank). Javascript, which is unrelated despite the name, can be left on.

  • Java Web Start Version 1.0 doesn't found installed JRE

    I would like to try some demos from http://java.sun.com/products/javawebstart/demos.html
    After I clicked on image receive next page with message "In order to launch the requested application, you will need to download Java Web Start Version 1.0 - This installation is a one-time process."
    And after click "Download now" me propose download JSE and install.
    But I already have installed JRE!
    This is from command line java -version:
    java version "1.6.0_03"
    Java(TM) SE Runtime Environment (build 1.6.0_03-b05)
    Java HotSpot(TM) Client VM (build 1.6.0_03-b05, mixed mode)
    I have try from opera and firefox.

    set JAVA_HOME to jdk and not jre.JAVA_HOME is for other applications to find the java libraries inside jdk
    Example:
    JAVA_HOME=C:\Program Files\Java\jdk1.5.0_05

  • Java web start error running Asset Editor or any jnlp page

    When I try to launch Asset Editor or Import/Export or any of the jnlp pages that runs using Java Web Start, I get an error. Java 7 Web start starts but It throws “Could not connect to Server. Please check your Java Web Start and Browser proxy settings”.
    I read conflicting opinions on the internet as to what version of JRE/JDK is needed and potentially some issues running Java Web start with Java 7. I have 64-bit java 1.7.0_45 JDK/JRE installed and no other version. I tried installing 32-bit 1.7.0_45 as well. I have tried to run it from 32-bit as well as 64-bit browser also. All situations provide the same error.
    However, when I install JRockit, it seems to work fine. But we cannot use jrockit. We have to use IBM JDK/JRE 7 eventually. Currently, the java web start does not work on Oracle Java as well as IBM JRE.
    Any help is much appreciated.

    I found a solution for this problem. We have to apply patch 17634436.
    https://support.oracle.com/epmos/faces/ui/patch/PatchDetail.jspx?_afrLoop=149081897091441&patchId=17634436&_afrWindowMode=0&_adf.ctrl-state=xfsajjmff_74
    Just thought it will be useful for anyone encountering this problem.

  • Multiple version of Java on one machine

    Is it possible to have multiple versions of Java co-exist on the same XP Pro machine?
    Here is our scenario: we have apps that use Java 1.5, but we have one critical app that doesn't support that version yet. It has to use the 1.4 version. Is there a way to allow both versions to exist and be usable for their respective apps? If so, how?
    Thank you.

    I can't, however it's never a good idea to have
    multiple versions of Java on one machine. Try and
    standardise if possible. If OP used JAVA_HOME as you
    often suggest, then he would be knackered wouldn't
    he? JAVA_HOME can only point to one JDK. Your
    advice is conflicting kaj.Nope. JAVA_HOME should always be defined in the start script/file for a java application, so it's not set per system. It's very common that companies have applications that requires different JDK/JRE versions, and it's usually very expensive to upgrade all applications (if it's possible at all). You can of course also alter the PATH variable if you want to in the script.
    /Kaj

  • JVM - Microsoft JScript.dll Memory Leak when using Java Web Start

    I have posted before a topic related to this matter, although now I have a lot more information about what is going on (although still no fix for it). This is the link to the earlier post, containing JVM HOTSPOT EXCEPTION_ACCESS_VIOLATION
    http://forum.java.sun.com/thread.jspa?threadID=5116970&messageID=9402346#9402346
    The issue is that after deploying on Windows XP a multi threaded, memory consuming (40 Mb) Java Swing application using Java Web Start, and the standard web page (IE6) reference to the jnlp file to launch the installation from Tomcat, each time this application gets executed by double clicking on the desktop icon (with no IE6 interaction at all), calls start being made between jvm.dll (sun) and jscript.dll (Microsoft IE), these interactions never release the memory they consume, so after a period of using the application it crashes unavoidably. If I execute exactly the same application launching it from command line (no Web Start nor IE6 browser involved), the application works nicely all the time, no problem at all.
    My question is: does anyone know why these calls to jscript.dll are even being made during web start application execution? As said, it's a desktop Swing app, it does not need the browser at all, and jscript.dll is a IE dll. Anyone can advice on how these interactions can be eliminated?
    I've worked with Microsoft support for two weeks on this issue and all they have said is that it is a Sun problem and they can not help further.
    Thanks
    Jes�s

    Microsoft suggested (among others) two test.
    1- Install IE7 and run the application
    2-Install Firefox and run the application
    Results were:
    For 1: The application does not crash, apparently IE7 has a newer version of Jscript.dll that, in Microsoft words, handles better 'bad software', refering to 'bad software' to the java virtual machine I guess. Looking at the performance manager you can see memory goes down as with IE6, but at some point memory is released and the app. does not crash. Anyway is still is uncertain to me why Jscript.dll is getting involved at all. Although this solves the problem is not a viable solution for us, because I work in a corporation where changes such as upgrading the IE version on a large number of desktop can not be justified just because one app. is crashing, and it would take a long validation time anyway before the upgrade can proceed.
    For 2: I did install Firefox in a machine and the application still crashed, but it is true I did not uninstall IE6, so the conflictive Jscript.dll was still sitting at system32. Quite possibly the crash would not happen if that dll wasn't there at all.
    Thanks
    Jes�s

  • What is Java Web Start?

    Hi
    After installing Java 2 Platform Standard Edition v 1.4.2, Java Web Start link on the
    Windows 98 desktop.
    What do I use Java Web Start for?
    Please reply soon.
    Thanks,
    Sincerely,
    Egan

    Java Web Start software provides a flexible and robust deployment solution for Java technology-based applications based on the Java Community Process program (JCP). The technology is being developed through the JCP program as JSR-56: The Java Network Launching Protocol & API (JNLP), which provides a browser-independent architecture for deploying Java 2 technology-based applications to the client desktop.
    Java Web Start technology works with any browser and any Web server. Each application developed for use with the Java Web Start software specifies which version of the Java 2 platform it requires, e.g., version 1.2 or 1.3, and each application runs on a dedicated Java Virtual Machine (JVM).
    A main feature of the Java Network Launching Protocol and API technology is the ability to automatically download and install Java Runtime Environments onto the users machine.
    For example, an application might depend APIs in Sun's Java Runtime Environment 1.3.0 (or later). When a user first accesses this application, the Java Web Start software will download all the needed files for the application, as well as download the Java Runtime Environment (JRE) if the requested version is not available locally. The ability to automatically download a JRE is one of the key features to ensure robust deployments. It ensures that the JRE that your application is tested on will be available on the user's machine, as well as make it possible to seamlessly upgrade to improved versions of the Java 2 platform over time.
    The java.sun.com auto-download feature simplifies Java Web Start deployments because it makes commonly used software readily available for use with Java Web Start. Typically, only an extra line has to be added to a JNLP file to take advantage of this feature. In contrast, without the auto-download feature, developers would be forced to repackage and host the software themselves - adding a significant overhead to the deployment burden. As an added benefit to both developers and end-users, this minimizes the download time for an application since each JRE will be shared between multiple applications.

  • Java Web Start running JasperReports

    The following is the exception that is thrown when trying to compile an .xml report template to a JasperReport object, from an app that has been deployed via the Java Web Start:
    dori.jasper.engine.JRException: Errors were encountered when compiling report expressions class file:
    C:\Program Files\mozilla.org\Mozilla\DailyReport.java:4: package dori.jasper.engine does not exist
    import dori.jasper.engine.*;
    * I have deployed the application properly via Java Web Start; however, when running the application it is not able to compile the xml file to a JasperReport object.
    * The .java file is created properly; but the app does not seem to be able to find the dori.jasper.engine.*; library.
    * I have signed and included the jasperreports-0.5.0.jar (and it's dependencies) with the app, and have put the path to all of it in the Class-Path of the manifest file.
    * NOTE: Just FYI, I am able to run this without any problems under netbeans.

    Dear Patrick,
    Recently I have used iReports for generating report through java & deploy it through java web start.
    I had taken all the measures you had mentioned in your previous replies. But I am not able to view the report. ( might be it is not compiliing)
    I am using new version of jasperreports-0.5.3.jar
    also through console it is running well.
    Also it is not giving any errors. can u have any idea about this.
    Might be it is silly mistake I have done.
    My code for report generation is :
    public class SReportA
         public SReportA()
         try
         JasperDesign jasperDesign = JasperManager.loadXmlDesign("/home/ora/iReport/RSENIORITYLIST-A.xml");
         dori.jasper.engine.design.JRBshCompiler theCompiler = new dori.jasper.engine.design.JRBshCompiler();
         JasperReport jasperReport = theCompiler.compileReport(jasperDesign);     
         Map parameters = new HashMap();
         parameters.put("uname","admin");               
         Connection con=null;
         try
              Class.forName("oracle.jdbc.driver.OracleDriver");
              con=DriverManager.getConnection("jdbc:oracle:thin:@158.144.71.219:1521:dbadp","acom","admin123");
         catch(Exception e)
              System.out.println("Exception in test.jsp "+ e);
         JasperPrint jasperPrint = JasperFillManager.fillReport(jasperReport,parameters,con);
         JasperManager.printReportToPdfFile(jasperPrint,"ReportA.pdf");
         JasperViewer.viewReport(jasperPrint,false);
         catch(Exception e){ System.out.println("There is exception here"+ e); }

  • Unable to launch Integeration Builder - Java Web Start - Unexpected Error

    Hi there,
    I am not able to launch the Integeration builder. The ESR has no problem and is working fine though.
    Here is the exception :- com.sap.aii.ibdir.gui.appl.ApplicationImpl
    I have tried below options already :
    1. Cleared the java cache under - javaws -logviewer
    2. Go into administration and inside Directory --> Java Web Start Administration clicked "Restore archives and generate new sign."
    Strange part is some of my colleagues here doesnt have any issue while opening the Integeration Builder. In fact I dont have any such issue in QA and PROD environment. The issue is only in DEV environment. Please advice.
    Anshul

    Hello,
    Usually restoring the archives will help resolve the issue.
    If the issue is occurring for just yourself maybe you could check that you are using the correct java version. e.g. for for 7. 1 java version 5
    Also please refresh the Java Web Start:
    If it's a Windows terminal, select Start - Run - javaws to launch Java Web Start and then clear the cache. File -> preferences ->
    advanced -> clear folder button
    If you have later versions of Java and doing the
    Start -> Run doesn't give you anything, then select Start - Run and type Control and hit Enter. Double-click Java in the list
    that displays to view the more up-to-date Java Control Panel. In the General tab, select Settings from the Temporary Internet Files section. Click Delete Files to clear the cache and then log into the Integration Builder again (download will be longer as jars will be cached locally again).
    If the problem still remains I would advise to check that the latest patches have been applied for XI_TOOL, and also the other components MESSAGING  SAP-XIAFC SAP_XIAF SAP_XIESR SAP_XIGUI
    Regards,
    Sarah

  • Java Web Start Application surprisedly does not start anymore based on new JRE1.7.0_45

    Hi everyone,
    we have to maintain a self-developed Java Application which is running based on JRE1.5.0_51 (x64). Our recent client machines have JRE1.7.0_40 (x64 too) installed in addition to the mentioned (and needed) JRE1.5.0_51 (x64).
    Everything was fine up to the point where we tried to install the newest JRE1.7.0_45 (x64) as the new version for doing the web start magic. The result is that our application (which is/was unchanged!) does not launch anymore. The strange thing is that we do not get any StackTrace, Exception or something else like this.
    The startup process simply hangs :-(
    Nothing has changed (application itself, firewall, network settings, hardware) apart from the new JRE version. It's reproducible at will. If I install JRE1.7.0_40 (x64) the application starts, if I install JRE1.7.0_45 (x64) the application hangs.
    I can say for sure, that in both cases (*_40 AND *_45) Web Start is able to do the synchronizing job and to launch the application base on the correct JRE1.5.0_51 (x64).
    My guess is that in case of an installed JRE1.7.0_45 (x64), the application hangs when it tries to connect to the database (Oracle 11g) via JDBC.
    I found a little hint in the Web Start Console. Therefore I had to switch the trace level of the console to 3 (which includes security, network and basic)
    In case of an installed JRE1.7.0_40 (x64) - which leads to a running application - I will receive the following output:
    Java Web Start 10.40.2.43
    JRE-Version verwenden 1.5.0_51-b10 Java HotSpot(TM) 64-Bit Server VM
    security: Istrusted: http://PKS-Server/jnlp2/advise_office.jnlp true
    avawsApplicationMain     3798 DEBUG root                : get Service: com.sun.jnlp.BasicServiceImpl@3b8e609b  fileName: connection.properties
    network: Cacheeintrag nicht gefunden [URL: http://PKS-Server/jnlp2//connection.properties, Version: null]
    network: Verbindung von http://PKS-Server/jnlp2//connection.properties mit Proxy=DIRECT wird hergestellt
    avawsApplicationMain     3803 INFO  root                : 'Alex2 connection.properties' wurde vom WebServer gelesen
    network: Verbindung von socket://PKS-Server:1521 mit Proxy=DIRECT wird hergestellt
    avawsApplicationMain     4488 DEBUG root                : get Service: com.sun.jnlp.BasicServiceImpl@3b8e609b  fileName: connection.properties
    network: Cacheeintrag nicht gefunden [URL: http://PKS-Server/jnlp2//connection.properties, Version: null]
    network: Verbindung von http://PKS-Server/jnlp2//connection.properties mit Proxy=DIRECT wird hergestellt
    avawsApplicationMain     4492 INFO  root                : 'Alex2 connection.properties' wurde vom WebServer gelesen
    Connect OK => application starts.
    In case of an installed JRE1.7.0_45 (x64) - which leads to a hanging application - I will receive the following output:
    Java Web Start 10.45.2.18
    JRE-Version verwenden 1.5.0_51-b10 Java HotSpot(TM) 64-Bit Server VM
    security: Istrusted: http://PKS-Server/jnlp2/advise_office.jnlp true
    avawsApplicationMain     3805 DEBUG root                : get Service: com.sun.jnlp.BasicServiceImpl@25a41cc7  fileName: connection.properties
    network: Cacheeintrag nicht gefunden [URL: http://PKS-Server/jnlp2//connection.properties, Version: null]
    network: Verbindung von http://PKS-Server/jnlp2//connection.properties mit Proxy=DIRECT wird hergestellt
    avawsApplicationMain     3810 INFO  root                : 'Alex2 connection.properties' wurde vom WebServer gelesen
    network: Verbindung von socket://PKS-Server:1521 mit Proxy=DIRECT wird hergestellt
    network: Verbindung von socket://PKS-Server:1521 mit Proxy=DIRECT wird hergestellt
    network: Verbindung von socket://PKS-Server:1521 mit Proxy=DIRECT wird hergestellt
    network: Verbindung von socket://PKS-Server:1521 mit Proxy=DIRECT wird hergestellt
    network: Verbindung von socket://PKS-Server:1521 mit Proxy=DIRECT wird hergestellt
    network: Verbindung von socket://PKS-Server:1521 mit Proxy=DIRECT wird hergestellt
    network: Verbindung von socket://PKS-Server:1521 mit Proxy=DIRECT wird hergestellt
    network: Verbindung von socket://PKS-Server:1521 mit Proxy=DIRECT wird hergestellt
    network: Verbindung von socket://PKS-Server:1521 mit Proxy=DIRECT wird hergestellt
    network: Verbindung von socket://PKS-Server:1521 mit Proxy=DIRECT wird hergestellt
    network: Verbindung von socket://PKS-Server:1521 mit Proxy=DIRECT wird hergestellt
    These last "network:" log entries will never stop. This will lead to an infinite loop which results in a great memory leak. I have to kill the process via windows task manager in order to get rid of it.
    Does someone out there has the same problem? Are there any new additional security issues which prevent my client to establish the database connection on port 1521?
    Any other ideas?
    Thanks in advance for any hint on this issue!
    Regards,
    Alex

    Resolution: We still were not able to solve this issue! The only way to get out of this is to install the JRE1.5 as the x64 variant. In this case no switching from 64-bit to 32-bit is needed and everything is on track again.
    But this is still strange and unexplainable :-(

  • Java web start application runs too slow...

    Hello,
    I am new to Java Web Start. I have created a java web start application and when i enable web start from local Execution, then it works perfectly well. But when i upload it on server and then download the application, then it is too too slow...i mean it takes minutes to get the output on clicking some button....my jnlp file is as under:
    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <jnlp codebase="http://(web server code base)" href="launch.jnlp" spec="1.0+">
    <information>
    <title>ERD</title>
    <vendor>Deepika Gohil</vendor>
    <homepage href="http://appframework.dev.java.net"/>
    <description>A simple java desktop application based on Swing Application Framework</description>
    <description kind="short">ER Deign Tools</description>
    </information>
    <update check="always"/>
    <security>
    <all-permissions/>
    </security>
    <resources>
    <j2se version="1.5+"/>
    <jar href="ERD_1_2.jar" main="true"/>
    <jar href="lib/appframework-1.0.3.jar"/>
    <jar href="lib/swing-worker-1.1.jar"/>
    <jar href="lib/jaxb-impl.jar"/>
    <jar href="lib/jaxb-xjc.jar"/>
    <jar href="lib/jaxb1-impl.jar"/>
    <jar href="lib/activation.jar"/>
    <jar href="lib/jaxb-api.jar"/>
    <jar href="lib/jsr173_api.jar"/>
    <jar href="lib/ant-contrib-1.0b3.jar"/>
    <jar href="lib/jaxb-impl.jar"/>
    <jar href="lib/jaxb-xjc.jar"/>
    <jar href="lib/FastInfoset.jar"/>
    <jar href="lib/gmbal-api-only.jar"/>
    <jar href="lib/http.jar"/>
    <jar href="lib/jaxws-rt.jar"/>
    <jar href="lib/jaxws-tools.jar"/>
    <jar href="lib/management-api.jar"/>
    <jar href="lib/mimepull.jar"/>
    <jar href="lib/policy.jar"/>
    <jar href="lib/saaj-impl.jar"/>
    <jar href="lib/stax-ex.jar"/>
    <jar href="lib/streambuffer.jar"/>
    <jar href="lib/woodstox.jar"/>
    <jar href="lib/jaxws-api.jar"/>
    <jar href="lib/jsr181-api.jar"/>
    <jar href="lib/jsr250-api.jar"/>
    <jar href="lib/saaj-api.jar"/>
    <jar href="lib/activation.jar"/>
    <jar href="lib/jaxb-api.jar"/>
    <jar href="lib/jsr173_api.jar"/>
    </resources>
    <application-desc main-class="erd.screen1">
    </application-desc>
    </jnlp>
    I dont understand the reason. Could you please help me out.
    Thank you,
    Deepika Gohil.

    Check your web server's access logs to see how many requests web start is sending for each jar. After you've loaded the application the first time, for each subsequent launch, if you've got everything configured right, you should only see requests for the JNLP file and maybe some gifs because web start should load everything else out of the cache (if you're using the version-based download protocol). Or if you're using the basic download protocol, then you might see requests for each jar file, but even in this case, if your web server is prepared to evaluate the last-updated attribute for each jar request and for jars that have not changed, respond with no actual payload and a header value of Not-Modified, then that should run almost as fast.
    You might also want to consider changing the "check" attribute of the "update" element from "always" to "background" for a couple of reasons. It should allow your app to start sooner (but this means that you might have to launch once or twice after an update is applied to the web server before the update shows up on the workstation). Also, my impression is that "always" is broken and prevents web start from ever checking to see if your jnlp file has been updated if you launch your app from a web start shortcut - launching from a browser is less likely to have this problem, depending on how often your browser is configured to check for updated resources.

  • Java Web Start application doesn't run in Tomcat

    I successfully did a Java Web Start example for me to learn then I tried another one where I encountered an error:
    This is what Tomcat 6.0.18 says. The deploy is successful but when I try to run the web start application
    with this htmlcode
    <A href="http://localhost:8080/ConvertorValutar/app/launch.jnlp">I get this error witch leads me to think that it can't find the jar correct ?
    type Status report
    message /convertorvalutar/
    description The requested resource (/convertorvalutar/) is not available.Appendix:
    This is how I am doing the JAR
    jar cfvm convertorvalutar.jar myManifest2.mf Java*.class IRata*.class The myManifest2.mf is
    Main-class: JavaWebStart_Convertor witch is the main class
    This way I am doing the WAR:
    del *.war /F /Q
    jar cfv convertorvalutar.war app/* WEb-INF/*This is the correct directory structure
    &#9474;   faWar.bat
    &#9474;   convertorvalutar.war
    &#9474;
    &#9500;&#9472;&#9472;&#9472;app
    &#9474;       ConvertorValutar.jar
    &#9474;       launch.jnlp
    &#9474;
    &#9492;&#9472;&#9472;&#9472;WEB-INF
        &#9474;   web.xml
        &#9474;
        &#9492;&#9472;&#9472;&#9472;lib
                jnlp-servlet.jarThis is the web.xml
    <?xml version="1.0" encoding="iso-8859-1"?>
    <!DOCTYPE web-app
    PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
    "http://java.sun.com/dtd/web-app_2_3.dtd">
    <web-app>
    <!-- Standard Action Servlet Configuration (with debugging) -->
    <web-app>
         <servlet>
              <servlet-name>JnlpDownloadServlet</servlet-name>
              <servlet-class>jnlp.sample.servlet.JnlpDownloadServlet</servlet-class>
         </servlet>
         <servlet-mapping>
              <servlet-name>JnlpDownloadServlet</servlet-name>
              <url-pattern>*.jnlp</url-pattern>
         </servlet-mapping>
    </web-app>
    </web-app>This is the jnlp:
    <?xml version="1.0" encoding="UTF-8"?>
    <jnlp codebase="http://localhost:8080/convertorvalutar/app">
    <information>
         <title>Convertor Valutar</title>
         <vendor>remus.dragos</vendor>
         <description>Simple Java Web Start Example</description>
    </information>
    <resources>
         <j2se version="1.5+"/>
         <jar href="ConvertorValutar.jar"/>
    </resources>
    <application-desc main-class="JavaWebStart_Convertor"/>
    </jnlp>Where is the problem?
    Edited by: remus.dragos on Dec 9, 2008 7:14 PM

    I did checked the names again and I found that the makeJar.bat had an "issue".
    It missed the del *.jar and I had 2 uppercase letters like ConvertorValutar, instead of convertorvalutar.jar.
    After that I rebuild the war and deployed and it works :)
    Thanks.

  • Java Web Start Error in Tiger

    I just received a new MacBookPro and when I attempt to download/run a Java application I get the following error (worked with my older system):
    An error occurred while launching/running the application.
    Title: Extensity 6
    Vendor: Geac Computer Corporation Limited
    Category: System Configuration
    The application has requested a version of the JRE (version 1.3.1* 1.3.1_02 1.3.1_01 1.3.1 1.3.0* 1.4.1* 1.4.2_08 1.4.2_10) that currently is not locally installed. Java Web Start is unable to automatically download and install the requested version. This JRE must be installed manually.

    Have you tried using Rosetta?

Maybe you are looking for