Java Web Start issue

Hi,
since we deploy JRE using Software distribution in Active Directory, the msi file provided with the Java installation is not well usable. Not sure, if it is still the case, that triggering the msi file a second time after successfull installation destroys the exisiting Java installation.
So I have built my own msi file for internal deployment using Advanced Installer. Finally all seemed to work (had some intermediate issues with outdated keys in HKCU), but now a new corporate application arrived, which creates a Java Web Start shortcut on the desktop. This shortcut fails to start with the error "Can not find message file".
Not very helpful. I found out, that the shortcut points to the javaws.exe in system32 folder (if I create the shortcut with the Cache Viewer, the same happens). And this javaws.exe file is also bringing up this message if double clicking. If I manually alter the shortcut to point to Program Files\Java\jre6\bin\javaws.exe, the application launches.
So there must be something wrong in my package with the javaws.exe in the Windows system folder. But what? I compared already several registry keys with a non corporate machine, on which I installed from download, and here it functions well, but could not find any visible differences.
Would be nice, if somebody could point me to either a way to fix the javaws.exe file in system32 (without using the downloaded Java installer, which cannot be deployed) or default created shortcuts to point to Program Files\Java instead of Windows\system32.
Thanks and best greetings from Germany
Olaf

907297 wrote:
Hi and thanks for the answer.
That is my guess as well. As mentioned I already tried to compare the registry keys related to javaws on two machines and found no visible differences, which would explain, why this functions on one and not on the other. But maybe I simply did not stumble over the needed key.I wonder if there is a way to sniff out which registry keys a native application is referencing. That could also provide some clues into which keys need to be cleaned up to fix a broken JDK installation, which too many people are suffering from.

Similar Messages

Issue Downloading Resources with Java Web Start

I'm having an issue with Java Web Start downloading resources. After executing the JNLP file, the download will start and the main Jar will download, then the download will just stop. The downloader is still running, but the progress bar just sits and nothing happens. This only will happen on some machines, even ones on the same network. Others download fine, and the application starts correctly. I thought maybe a setting with java web start needed to be changed, but the proxy settings are set to the browser, which are the same for all machines. The JNLP file is below (however, for security reasons the codebase/homepage are left out, but they are correct in the actual file). Does anyone have any idea of what the problem might be?
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
     <jnlp codebase="..." spec="1.0+">
     <information>
     <title>Java3D Test</title>
          <vendor>None</vendor>
          <homepage href="..." />
          <description>Test application for Java3D</description>
     </information>
     <update check="always" />
<security>
     <all-permissions/>
</security>
<resources>
          <j2se version="1.5+"/>
     <jar eager="true" href="TestJava3D.jar" main="true" />
          <jar href="lib/Library.jar" />
          <jar href="lib/Java3D.jar" />
          <jar href="lib/j3dnative.jar" />
     </resources>
<application-desc main-class="testjava3d.TestJava3DMain">
</application-desc>
</jnlp>

You could enable JavaConsole and turn on tracing to get more debugging info. See: http://docs.oracle.com/javase/7/docs/webnotes/tsg/TSG-Desktop/html/plugin.html#gcexdf

Deployment Issues using Java Web Start

I am attempting to deploy a Java application that works in JDeveloper. The app has a Database connection to a MSSQL 2000 Server which is loaded into the active Project Libraries as Other JBDC. When I deploy the app using Java Web Start I receive the following error: com.microsoft.jdbc.sqlserver.SqlServerDriver.
How to I need to configure my deployment so the JDBC works properly? Thanks in advance

I got it to work with the following settings:
1. edit ur ctbuild.xml file to have these settings:
<include name="BC4J/lib/msbase.jar"/>
<include name="BC4J/lib/mssqlserver.jar"/>
<include name="BC4J/lib/msutil.jar"/>
Then have the same jar files in localmt.jsp as
<jar href="adfjars/BC4J/lib/msbase.jar" />
<jar href="adfjars/BC4J/lib/mssqlserver.jar" />
<jar href="adfjars/BC4J/lib/msutil.jar" />
2. edit data-sources.xml file, if ur using external oc4j as
<data-source
class="com.evermind.sql.DriverManagerDataSource"
name="sqlserverDBDS"
location="jdbc/SQLServerCoreDS"
xa-location="jdbc/xa/SQLServerXADS"
ejb-location="jdbc/SQLServerDS"
connection-driver="com.microsoft.jdbc.sqlserver.SQLServerDriver"
username="scott"
password="PwdForScott"
url="xxxx"
inactivity-timeout="30"
/>
Thnks,
Sainath

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 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
│   faWar.bat
│   convertorvalutar.war
│
├───app
│       ConvertorValutar.jar
│       launch.jnlp
│
└───WEB-INF
    │   web.xml
    │
    └───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>

<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 - java.io.IOException: EOF reading band

I am using Java Web Start to download an application and I am getting the following error. How do I resolve this? The jar that is being downloaded is present in the directory.
java.io.IOException: EOF reading band
     at com.sun.java.util.jar.pack.NativeUnpack.start(Native Method)
     at com.sun.java.util.jar.pack.NativeUnpack.run(Unknown Source)
     at com.sun.java.util.jar.pack.NativeUnpack.run(Unknown Source)
     at com.sun.java.util.jar.pack.UnpackerImpl.unpack(Unknown Source)
     at com.sun.deploy.net.HttpDownloadHelper.download(Unknown Source)
     at com.sun.deploy.cache.Cache.downloadResourceToTempFile(Unknown Source)
     at com.sun.deploy.cache.Cache.downloadResourceToCache(Unknown Source)
     at com.sun.deploy.net.DownloadEngine.actionDownload(Unknown Source)
     at com.sun.deploy.net.DownloadEngine.getCacheEntry(Unknown Source)
     at com.sun.deploy.net.DownloadEngine.getCacheEntry(Unknown Source)
     at com.sun.deploy.net.DownloadEngine.getResourceCacheEntry(Unknown Source)
     at com.sun.deploy.net.DownloadEngine.getResourceCacheEntry(Unknown Source)
     at com.sun.deploy.net.DownloadEngine.getResource(Unknown Source)
     at com.sun.javaws.LaunchDownload.downloadJarFiles(Unknown Source)
     at com.sun.javaws.LaunchDownload.downloadEagerorAll(Unknown Source)
     at com.sun.javaws.Launcher.downloadResources(Unknown Source)
     at com.sun.javaws.Launcher.prepareLaunchFile(Unknown Source)
     at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
     at com.sun.javaws.Launcher.launch(Unknown Source)
     at com.sun.javaws.Main.launchApp(Unknown Source)
     at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
     at com.sun.javaws.Main$1.run(Unknown Source)
     at java.lang.Thread.run(Unknown Source)

jfdenise wrote:
Hi,
I am facing the exact same issue when getting a big jar of more than 7 megs. It seems to occur in some special network configuration that I am not yet able to figure out. It is obviously linked to the fact that the jar is unpacked on the client side.
Anybody ran into this one and understood the root cause?Please, don't resurrect old threads, and don't use signatures with addresses. I'm locking this thread.
Kaj

Java Web Start Error in through codebase url with SSL

I have created one Java web-start plugin application in swing which is launched from PHP site at browser plugin.
All things were working fine, but when we implemented SSL in our site it stopped working. And when we try to start the application from browser it thorws error like:
Unable to launch Application.
In Java console it puts following log:
JNLP Ref (...): NULL !
#### Java Web Start Error:
#### null
Following is my JNLP file:
<jnlp spec="1.0+" codebase="https://<<server_domain>>/MyPlugin/">
<information>
    <title>Test Plugin</title>
    <vendor>The Java(tm) Tutorial</vendor>
    <homepage href="null"/>
    <description>Test Plugin</description>
    <description kind="short">Test Plugin</description>
    <offline-allowed/>
</information>
<security>
    <all-permissions/>
</security>
<update check="timeout" policy="always"/>
<resources>
    <java version="1.7+"/>
    <jar href="http://<<server_domain>>/MyPluginJar.jar" download="eager" main="false"/>
</resources>
<application-desc>
    <argument>test</argument>
    <argument>test</argument>
    <argument>test</argument>
    <argument>test</argument>
    <argument>test</argument>
</application-desc>
</jnlp>
The issue started only after implementation of SSL in our site. Please provide any solution for this. Many thanks in advance.
P.S. My Jar file is signed by third party authorized certificate.

Have you tried using Rosetta?

Java Web Start 1.6 fails to start application without Java Consol on Vista

Hi All,
I've faced with problem related to starting my application in IE 7 on Vista SP1 using Java Web Start (JRE 1.6.0_12 and 1.6.0_13). I suppose that issue appears after 11th update of JRE 1.6 since it works fine before.
There were set settings to indicate initial and maximal size of the Java heap in the JNLP file.
Application consist of 2 JAR files and they are signed with the same certificate.
When user tried to start application there is no any activity after accepting certificate. After starting application javaw.exe just disappeared from processes list without any message or error.
When I changed default setting in Java Control Panel to show Java Console, I noticed that the application began to start. But it's not a solution of the issue, since all customers cannot be required to turn on Java console.
I believe this is a bug in JRE as the application starts with Java console and doesn't without it.
When I browsed the web looking for the solution or an advice I found Release notes for 1.6.0_014 where it was said that 6u14 Java Web Start failed to launch and notifies that JARs were not signed, if an insecure Java system property was specified in a sandbox JNLP file. In spite of that 14th updated wasn't used and there was no notification I tried to start application without settings for the Java heap and it worked.
Could someone help me with advice, since the application cannot be started with default heap size settings.
Thanks in advance.
Edited by: vovanst on Jul 28, 2009 8:06 AM

Hi,
as the 6u15 just arrived and the above mentioned bug should've been fixed (though I was unable to verify through the release notes), the error is still in there.
We have no timestamped jars, neither ours nor the bouncy castle ones, all certs are valid, ours is self signed.
6u13 runs, 6u14/6u15 won't.
I followed the instructions here: http://bouncycastle.org/devmailarchive/msg10415.html to no avail.
The bcprov.jar is wrapped in its own jnlp and referred as extension from the "main" jnlp.
The interesting parts of the stack trace are these:
Caused by (via getCause): java.lang.SecurityException: JCE cannot authenticate the provider BC
     at javax.crypto.Cipher.getInstance(DashoA13*..)
     at javax.crypto.Cipher.getInstance(DashoA13*..)
Caused by (via getCause): java.util.jar.JarException: Cannot parse https://localhost:8443/deploy/bcprov.jar
     at javax.crypto.SunJCE_c.a(DashoA13*..)
     at javax.crypto.SunJCE_b.b(DashoA13*..)
     at javax.crypto.SunJCE_b.a(DashoA13*..)
     at javax.crypto.Cipher.getInstance(DashoA13*..)
     at javax.crypto.Cipher.getInstance(DashoA13*..)
For me it seems there's a problem with resolving the url of the bcprov.jar, which would explain the lack of a delay which normally occurs when JCE verifies the signature of the bcprov provider classes. The error pops up almost instantly.
I'm clueless what to do now. Did Sun really achieve to completely destroy JCE provider functionality in Javaws, forcing us to use an alternative implementation?
Patric

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.

Unable to launch java web start

We have already devloped an application based on java web start. Most of the client machines, we try to install java web start and run the developed app, it works fine. For one of the clients machine, we have an issue with java web start itself, it does not startup and bring up the application manager. When you start java web start, it shows up the splash screen 'java web start 1.0.1' after some time, it vanishes and does not bring up the application manager. I have installed java web start 1.0.1_01 (build 04) installed on Windows 2000 Professional, by default that has installed JRE 1.3.1_04 also.
We verified the system, all the files being existing under c:\program files\java web start dir. And the JRE is also installed fine.
Couple of times we uninstalled, rebooted and installed.
Infact, we have even verified the file types for html, htm, which was set to msoffice, and we have changed to internet explorer. For jnlp file type it was already set to javaws.exe.
Can you please let me know what could be the problem.
Regards,
Nagarjuna Rao Chakka

There's nothing to stop you installing 1.4 or even 1.4.2, it's the jnlp file that specifies which runtime version gets used to run your application - web start can be used to happily switch runtimes like this. You'll just need to have 1.4 and 1.3 installed on each machine. It's a good idea to upgrade the web start client as the old 1.0 version doesn't work at all well with Windows XP, it's structure of storing all the files in c:\program files works against the security restrictions built into XP.
Incidentally the config file you were looking for in under c:\program files\javaws\javaws.cfg, but this is different in later versions.
Your problem is most likely being caused by web start not being able to find the Java runtime version it was installed with, the client may well have installed a newer (or older) version of 1.3 which has broken the configuration.. another reason to upgrade is the old versions are very fragile in this respect; 1.4.2 can find installed runtimes far more dynamically. Fixing the config file above should get things working again, otherwise delete the .javaws directory in the user profile and re-start web start.
1.4.2 is the best at finding runtimes, but is marred by problems with the integration dialogs, locale always reported as en_US and some strange new behaviour with classloaders and malfunctioning auto installers.. jws 1.2 that comes with jre 1.4.1_x is far more reliable.
- Richard

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 and DeployDirector: What's the difference?

I am the product manager for DeployDirector at Sitraka (now part of Quest Software). I'm NOT in sales; I'd simply like to provide you with some information.
From talking with DeployDirector users and evaluators, and from my own discussions with the folks at Sun, I have discovered that there is great deal of confusion about the difference between Java Web Start and DeployDirector. I'd like to clarify this by periodically posting some information about the two.
Though the products seem similar in concept, they are designed for different purposes. They both deploy, auto-update and manage the JRE for client-side Java applications, but beyond that, they are quite different.
Java Web Start is ideally designed for applications deployed over the Internet, where application-provider trust is an issue. Why? The security sandbox guarantees that application can do no harm. (There's some good information about Java Web Start and sandbox apps on ScheduleWorld at http://www.scheduleworld.com/itsYourLife.html) Web Start's architecture simply consists of a client piece that interprets a JNLP file. Because of the sandbox and its simplicity, I believe JWS is best used for independent software vendors, independent developers, etc.
Because DeployDirector is ideally designed for internal enterprise applications, it does not enforce the security sandbox. Trust is not an issue here, because internal users typically trust their internal IT group. DeployDirector's architecture consists of both a client and a server piece, which allows us to support more complex deployment and update scenarios (e.g., scheduled and optional updates) and applications management capabilities like rollback, reporting, exception monitoring, authentication/authorization out of the box. All of this is configured through the DeployDirector administration console.
In some situations, DeployDirector may be unnecessary overhead. In other situations, Java Web Start simply does not provide enough capability and building in this into Web Start can be difficult.
If you'd like more information, we have whitepapers and case studies (including one specifically about DeployDirector and JWS) available on our website at http://www.sitraka.com/software/deploydirector/
If you'd like to discuss some of these differences, or if you have questions about DeployDirector, feel free to email me directly. (Or post here, of course.)
Thanks,
Sonal Champsee
[email protected]

Hi Gerald,
Given what I know about your emnity towards DeployDirector (which is clearly illustrated in this thread: http://forum.java.sun.com/thread.jsp?thread=348061&forum=38&message=1446155 that was evidently a response to this article: http://www.javaworld.com/javaworld/jw-11-2002/jw-1122-autoupdate.html) I'm going to take a (pardon the expression) "don't feed the trolls" approach here.
I'm simply re-iterate that JNLP, and its implementations such as Web Start and OpenJNLP, are designed for a very different set of users that DeployDirector. The differences in functionality between the two products reflect that.
The enterprise has different requirements in a deployment mechanism for its internal, critical applications than software vendors and independant developers. DeployDirector addresses the requirements of the enterprise. Frankly, most of our recent customers only chose to buy the product after initially rejecting it and (unsucessfully) attempting to use JNLP and Web Start. Sometimes people only learn the hard way: different users have different requirements which are suited to different tools or technologies.
Sonal

Java Web Start not working with Proxy

I have Java Web Start program not listening to proxy settings. It tries to access localhost using our proxy settings, but with no user name or password. I'm wondering if Java Web Start has proxy settings somewhere. I'm not sure since when we disable the proxy settings the program works without issue. Any thoughts?
Thanks

For instance Safari uses those System Proxy settings, Firefox uses it's own!
So Java is using it's own, now we're waiting for an expert to drop in!

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

Java Web Start issue

Similar Messages

Maybe you are looking for