processLauncher/Mustang and space-in-path

[glassfishrobot]

See this thread for a report of an issue on Windows when they have space in the path of the processLauncher.xml file and they are running against Mustang (don't know which version)

User orginally reported this by using NetBeans to start the spp server.

Later in thread they duplicated the issue using asadmin.

http://www.netbeans.org/servlets/BrowseList?list=nbj2ee&by=thread&from=464317

Environment

Operating System: Windows XP Platform: PC

Affected Versions

[9.0pe]

[glassfishrobot]

• Issue Imported From: https://github.com/javaee/glassfish/issues/690
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @yaminikb
• Original Issue Closed By:@glassfishrobot

[glassfishrobot]

@glassfishrobot Commented km105526 said: It is very tempting to close this bug as a duplicate of the one reported as: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6425843

This is simply because 6425843 predates this one. Apparently, there is something wrong with environment while running atop Mustang.

Submitter: Will you be OK to actually close this bug and monitor the other one? That way, we can minimize updating duplicate information.

[glassfishrobot]

@glassfishrobot Commented km105526 said: ..

[glassfishrobot]

@glassfishrobot Commented @vkraemer said: Opinion the query interface for the bug database (http://bugs.sun.com/bugdatabase/index.jsp) is really poor compared to this databases query interface. I think folks in the community are better served by Issue Tracker (https://glassfish.dev.java.net/servlets/ProjectIssues)

[glassfishrobot]

@glassfishrobot Commented ludo said: km105526 : Do the opposite: close the bug filed in closed bugsystem, since it is hard to find, to track, to understand (referring to sunone_application_server:configuration ...Uhuuhh), and incomplete: some fields are not visible from the web. Space in dir issue is critical even with current JDK 1.6 builds... From public website, it is not clear why the bug is marked as incomplete. The priority and severity are not even mentioned. The workaround (do not install with space in dir) is not described. Ludo

[glassfishrobot]

@glassfishrobot Commented msreddy said: Able to reproduce the bug using jdk 1.6, build 1.6.0-beta-b59g.

[glassfishrobot]

@glassfishrobot Commented msreddy said: The reported bug can be reproduced independent of application server as the issue is releated to xml parser. The test program TestSpace.java and the xml file used for testing are attached.

01 using jdk 1.5

Y:\DEV\JDEV\JDK16>java -version java version "1.5.0_06" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05) Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode, sharing)

Y:\DEV\JDEV\JDK16>javac TestSpace.java

Y:\DEV\JDEV\JDK16>java TestSpace TestSpace

02 using jdk 1.6 beta

Y:\DEV\JDEV\JDK16>rm *.class

Y:\DEV\JDEV\JDK16>"c:\Program Files\java\jdk1.6.0"\bin\java -version java version "1.6.0-beta" Java(TM) 2 Runtime Environment, Standard Edition (build 1.6.0-beta-b59g) Java HotSpot(TM) Client VM (build 1.6.0-beta-b59g, mixed mode, sharing)

Y:\DEV\JDEV\JDK16>"c:\Program Files\java\jdk1.6.0"\bin\javac TestSpace.java

Y:\DEV\JDEV\JDK16>"c:\Program Files\java\jdk1.6.0"\bin\java TestSpace TestSpace Caught exception ... java.net.MalformedURLException: unknown protocol: d at java.net.URL.(URL.java:574) at java.net.URL.(URL.java:464) at java.net.URL.(URL.java:413) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:647) at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:186) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:771) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107) at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:225) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:283) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:180) at TestSpace.main(TestSpace.java:26)

Y:\DEV\JDEV\JDK16>

It can be seen from the above that this a regression in jdk.

• • • (#2 of 2): 2006-05-30 12:26:31 PDT sreenivas.munnangi@sun.com

[glassfishrobot]

@glassfishrobot Commented msreddy said: Created an attachment (id=284) java code to test jdk 1.6 xml parser

[glassfishrobot]

@glassfishrobot Commented msreddy said: Created an attachment (id=285) xml file which is used by TestSpace.java

[glassfishrobot]

@glassfishrobot Commented msreddy said: Fix for 690 depends on jdk bug# 6425843

[glassfishrobot]

@glassfishrobot Commented msreddy said: The fix has been integrated.

01 Also refer to bug# 6425843 Can`t start domain if installation path contains spaces (java.net.MalformedURLException thrown)

02 code change RCS file: /cvs/glassfish/tools/src/java/com/sun/enterprise/tools/launcher/ProcessLauncherConfig.java,v retrieving revision 1.3 diff -r1.3 ProcessLauncherConfig.java 284c284 < return db.parse(file); —

return db.parse(new File(file));

03 tests performed on windows-xp:

• pe quicklook using jdk 1.6 beta2 b85
• pe quicklook using jdk 150_06

[glassfishrobot]

@glassfishrobot Commented msreddy said: Updated the integrated build version.

[glassfishrobot]

@glassfishrobot Commented File: processLauncher.xml Attached By: msreddy

[glassfishrobot]

@glassfishrobot Commented File: TestSpace.java Attached By: msreddy

[glassfishrobot]

@glassfishrobot Commented Was assigned to msreddy

[glassfishrobot]

@glassfishrobot Commented This issue was imported from java.net JIRA GLASSFISH-690

[glassfishrobot]

@glassfishrobot Commented Reported by @vkraemer

[glassfishrobot]

@glassfishrobot Commented Marked as fixed on Thursday, May 17th 2007, 4:05:53 am