Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4741517

javaws can not be used for CLI applications in non-GUI environment

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Duplicate
    • Icon: P4 P4
    • None
    • 1.2.0
    • deploy
    • x86, sparc
    • linux, solaris_8



      Name: nt126004 Date: 09/04/2002


      FULL PRODUCT VERSION :
      java version "1.4.0"
      Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92)
      Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode)

      FULL OPERATING SYSTEM VERSION : Linux linux3 2.2.18 #1 Wed
      Jan 24 12:28:55 GMT 2001 i686 unknown


      A DESCRIPTION OF THE PROBLEM :
      Starting javaws from the commanline (with a valid jnlp file
      as a single argument) throws the exception given below.
      Looks like jawaws needs a GUI, even if the application
      started by javaws does not need a GUI.

      There is no mention of this requirement in any of the available
      online documentation.

      STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
      see description

      ERROR MESSAGES/STACK TRACES THAT OCCUR :
      Java Web Start splash screen process exiting .....
      linux3:/usr/lib/javaws1.2/javaws # Splash: X11 connection failed: No such file
      or directory
      Exception in thread "main" java.lang.InternalError: Can't connect to X11 window
      server using ':0.0' as the value of the DISPLAY variable.
              at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
              at sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:126)
              at java.lang.Class.forName0(Native Method)
              at java.lang.Class.forName(Class.java:130)
              at
      java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:62)
              at sun.awt.motif.MToolkit.<clinit>(MToolkit.java:70)
              at java.lang.Class.forName0(Native Method)
              at java.lang.Class.forName(Class.java:130)
              at java.awt.Toolkit$2.run(Toolkit.java:712)
              at java.security.AccessController.doPrivileged(Native Method)
              at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:703)
              at com.sun.javaws.Launcher.<init>(Launcher.java:83)
              at com.sun.javaws.Main.main(Main.java:144)

      REPRODUCIBILITY :
      This bug can be reproduced always.
      (Review ID: 160072)
      ======================================================================

      Name: nt126004 Date: 09/04/2002


      FULL PRODUCT VERSION :
      java version "1.2.2"
      Solaris VM (build Solaris_JDK_1.2.2_10, native threads, sunwjit)

      Other j2se versions show the same behaviour

      FULL OPERATING SYSTEM VERSION :
      SunOS atss3 5.8 Generic_108528-14 sun4u sparc SUNW,Ultra-
      Enterprise

      ADDITIONAL OPERATING SYSTEMS :
      Windows 2000 Server


      A DESCRIPTION OF THE PROBLEM :
      It is not possible to operate Java Webstart in batch. It
      always needs a window environment to display the splash
      screens, startup screens ("do you trust this user ...") or
      error windows (exceptions). On Windows, you always need a
      user that is logged on, on Unix you always need an Xserver.
      Why can't Webstart operate in a mode where all input/output
      comes from/goes to files ? It seems like Webstart is
      taking over Microsoft's bad habbit of writing "Windows
      Only" applications.
      This is a pitty, since Webstart can do wonderfull things for
      services/daemon processes too.


      STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
      1. Start a JavaWebstart app
      2. Log off your unix workstation
      3. The webstart app will exit because the Xserver stops

      EXPECTED VERSUS ACTUAL BEHAVIOR :
      After step 3, I would like the Webstart app to keep on
      running.

      REPRODUCIBILITY :
      This bug can be reproduced always.

      CUSTOMER WORKAROUND :
      On Unix, we install the VNC product of AT&T Laboratories
      Cambridge. The Xvnc app can run as a daemon process, and
      acts as an XServer that will take all the Webstart windows.

      On Windows, we haven't found a workaround yet.
      (Review ID: 158738)
      ======================================================================

            Unassigned Unassigned
            nthompsosunw Nathanael Thompson (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: