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

[nightly] JNLP file invalid parsing

    XMLWordPrintable

Details

    • b09
    • generic
    • generic
    • Verified

    Backports

      Description

        In nightly build with fix for JDK-8041339

        a test that tries to load a JNLP file with complicated quoting fails. Exception shown in control panel is:

        at java.lang.String.charAt(String.java:646)
        at com.sun.deploy.config.Config.containsUnsupportedCharacters(Unknown Source)
        at com.sun.deploy.config.Config.isLegalArgument(Unknown Source)
        at com.sun.deploy.xml.XMLParser.parseXMLAttribute(Unknown Source)
        at com.sun.deploy.xml.XMLParser.parseXMLElement(Unknown Source)
        at com.sun.deploy.xml.XMLParser.parseXMLElement(Unknown Source)
        at com.sun.deploy.xml.XMLParser.parseXMLElement(Unknown Source)
        at com.sun.deploy.xml.XMLParser.parseXMLElement(Unknown Source)
        at com.sun.deploy.xml.XMLParser.parseXMLElement(Unknown Source)
        at com.sun.deploy.xml.XMLParser.parse(Unknown Source)
        at com.sun.javaws.jnl.XMLFormat.parse(Unknown Source)
        at com.sun.javaws.jnl.XMLFormat.parse(Unknown Source)
        at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
        at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
        at com.sun.javaws.Main.launchApp(Unknown Source)
        at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
        at com.sun.javaws.Main.access$000(Unknown Source)
        at com.sun.javaws.Main$1.run(Unknown Source)
        at java.lang.Thread.run(Thread.java:745)

        Attachments

          Issue Links

            backported by

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8043064 [nightly] JNLP file invalid parsing

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8043067 [nightly] JNLP file invalid parsing

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8043068 [nightly] JNLP file invalid parsing

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8043439 [nightly] JNLP file invalid parsing

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8047537 [nightly] JNLP file invalid parsing

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8050703 [nightly] JNLP file invalid parsing

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8051098 [nightly] JNLP file invalid parsing

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8052918 [nightly] JNLP file invalid parsing

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8060274 [nightly] JNLP file invalid parsing

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8043116 [nightly] JNLP file invalid parsing

            • P2 - Crashes, loss of data, severe memory leak.
            • Closed

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8043430 [nightly] JNLP file invalid parsing

            • P2 - Crashes, loss of data, severe memory leak.
            • Closed
            relates to

            Bug - A problem which impairs or prevents the functions of the product. JDK-8041339 JNLP with java-vm-args whose length exceeded 512 chars failed to get loaded with CouldNotLoadArgumentException

            • P3 - Major loss of function.
            • Resolved

            Activity

              People

                dtitov Daniil Titov (Inactive)
                aluht Anton Luht (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: