Bug 692852 - classpath issues cause failure to properly detect presence of java on windows
Summary: classpath issues cause failure to properly detect presence of java on windows
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: condor
Version: Development
Hardware: All
OS: Windows
medium
medium
Target Milestone: 2.0
: ---
Assignee: Timothy St. Clair
QA Contact: Martin Kudlej
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-01 12:06 UTC by Petra Svobodová
Modified: 2011-06-27 14:17 UTC (History)
3 users (show)

Fixed In Version: condor-win-7.6.0-5
Doc Type: Bug Fix
Doc Text:
This bug was actually caused by three separate issues. First, modifications made to the SHARE variable in condor_config caused errors when trying to run java detection on windows. The fix was to modify the installer to update the variable during installation. The second issue was JAVA_MAXHEAP_ARGUMENT= -Xmx causes errors when running on against newer versions of Oracle Java. Upstream fix was to remove the parameter entirely and allow args via traditional methods. Finally, the last issue was a bug caused by the addition of new classads, the compatibility layer was failing to parse attributes which ended in a "\". Upstream fix was to modify the compatibility layer to handle such cases.
Clone Of:
Environment:
Last Closed: 2011-06-27 14:17:15 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Petra Svobodová 2011-04-01 12:06:26 UTC
Description of problem:
Although a path to the java execute file was set during installation on the windows machines; the condor cannot detect it.


Version-Release number of selected component (if applicable):
condor-7.6.0-PRE-RELEASE-GRID.msi


How reproducible:
always


Steps to Reproduce:
1. Install the package; during installation check the path to the java.exe file
2. Restart the machine.
3.
  

Actual results:
The java is not detected by condor; see the Additional info part.


Expected results:
The java should be detected.


Additional info:
Part of the "StarterLog" on the Windows machine:

JavaDetect: failure status 1 when executing C:\PROGRA~2\Java\jre6\bin\java.exe -Xmx -classpath /scimark2lib.jar;. CondorJavaInfo old 2

Part of the terminal transcript on the Rhel central manager and scheduler machine (the windows machines missing):
[root@mrg-qe-06 condor]# condor_status -java

Name               JavaVendor Ver    State     Activity LoadAv Mem   ActvtyTime

slot10 Free Softw 1.4.2  Unclaimed Idle     0.000   503  0+02:25:06
slot11 Free Softw 1.4.2  Unclaimed Idle     0.000   503  0+02:25:07
slot12 Free Softw 1.4.2  Unclaimed Idle     0.000   503  0+02:25:08
slot13 Free Softw 1.4.2  Unclaimed Idle     0.000   503  0+02:25:09
slot14 Free Softw 1.4.2  Unclaimed Idle     0.000   503  0+02:25:10
slot15 Free Softw 1.4.2  Unclaimed Idle     0.000   503  0+02:25:11
slot16 Free Softw 1.4.2  Unclaimed Idle     0.000   503  0+02:25:04
slot1 Free Softw 1.4.2  Unclaimed Idle     1.000   503  0+02:24:47
slot2 Free Softw 1.4.2  Unclaimed Idle     0.250   503  0+02:25:06
slot3 Free Softw 1.4.2  Unclaimed Idle     0.000   503  0+02:25:07
slot4 Free Softw 1.4.2  Unclaimed Idle     0.000   503  0+02:25:08
slot5 Free Softw 1.4.2  Unclaimed Idle     0.000   503  0+02:25:09
slot6 Free Softw 1.4.2  Unclaimed Idle     0.000   503  0+02:25:10
slot7 Free Softw 1.4.2  Unclaimed Idle     0.000   503  0+02:25:11
slot8 Free Softw 1.4.2  Unclaimed Idle     0.000   503  0+02:25:04
slot9 Free Softw 1.4.2  Unclaimed Idle     0.000   503  0+02:25:05

Comment 2 Matthew Farrellee 2011-04-01 12:43:06 UTC
Looks like a classpath issue

Comment 3 Timothy St. Clair 2011-04-01 16:05:53 UTC
There are 3 issues

1.) SHARE : is not set properly 
2.) JAVA_MAXHEAP_ARGUMENT= -Xmx : causes issues on new versions of Java for windows
3.) 04/01/11 10:54:40 failed to create classad; bad expr = JavaIoTmpdir = "C:\Windows\TEMP\"

The first 2 are installer issues, the last is a TBD.

Comment 8 Timothy St. Clair 2011-04-05 14:15:16 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
This bug was actually caused by three separate issues.  First, modifications made to the SHARE variable in condor_config caused errors when trying to run java detection on windows.  The fix was to modify the installer to update the variable during installation.  The second issue was JAVA_MAXHEAP_ARGUMENT= -Xmx causes errors when running on against newer versions of Oracle Java.  Upstream fix was to remove the parameter entirely and allow args via traditional methods.  Finally, the last issue was a bug caused by the addition of new classads, the compatibility layer was failing to parse attributes which ended in a "\".  Upstream fix was to modify the compatibility layer to handle such cases.

Comment 9 Martin Kudlej 2011-05-20 12:34:37 UTC
Tested on all supported Windows versions and it works. -->VERIFIED


Note You need to log in before you can comment on or make changes to this bug.