Bug 748339

Summary: Java issue after starting the condor service
Product: Red Hat Enterprise MRG Reporter: Petra Svobodová <psvobodo>
Component: condorAssignee: Timothy St. Clair <tstclair>
Status: CLOSED ERRATA QA Contact: Petra Svobodová <psvobodo>
Severity: medium Docs Contact:
Priority: high    
Version: DevelopmentCC: iboverma, jneedle, matt, tstclair
Target Milestone: 2.1Keywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Windows   
Whiteboard:
Fixed In Version: condor-7.6.5-0.3 Doc Type: Bug Fix
Doc Text:
Previously, when the Windows Java detection issued an exception, no Windows clients were visible via the "condor_status -java" command. Now, the default configuration for the JAVA_SEPARATOR module has been updated and Windows clients correctly detect Java details in the described scenario.
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-23 17:29:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 743350    

Description Petra Svobodová 2011-10-24 07:59:06 UTC
Description of problem:
There is a error report in the Starter log: 
"JavaDetect: failure status 1 when executing C:\PROGRA~1\Java\jre6\bin\java.exe -classpath C:\condor/bin:C:\condor/bin/scimark2lib.jar:. CondorJavaInfo old 2"

Version-Release number of selected component (if applicable):
condor-7.6.5-0.2.msi

How reproducible:
100%

Steps to Reproduce:
1. Install the condor.
2. Restart the computer
3. After starting the condor service see the StarterLog.
  
Actual results:
The StarterLog contains an error message.

Expected results:
The StarterLog should contain no error messages.

Additional info:
See the command line transcription below, please:

C:\>C:\PROGRA~1\Java\jre6\bin\java.exe -classpath C:
\condor/bin:C:\condor/bin/scimark2lib.jar:. CondorJavaInfo old 2
Exception in thread "main" java.lang.NoClassDefFoundError: CondorJavaInfo
Caused by: java.lang.ClassNotFoundException: CondorJavaInfo
        at java.net.URLClassLoader$1.run(Unknown Source)
        at java.security.AccessController.doPrivileged(ative Method)
        at java.net.URLClassLoader.findClass(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
Could not find the main class: CondorJavaInfo.  Program will exit.

Comment 1 Timothy St. Clair 2011-10-26 16:05:32 UTC
tracking upstream: https://condor-wiki.cs.wisc.edu/index.cgi/tktview?tn=2586

Comment 3 Petra Svobodová 2011-10-31 13:37:10 UTC
There is no error message in the StarterLog.
Verified on condor-7.6.5.-0.4.msi

--> VERIFIED

Comment 4 Timothy St. Clair 2011-10-31 15:47:15 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:
C: Windows Java detection threw exception
C: No windows clients are visible via condor_status -java
F: Update the default config for JAVA_SEPARATOR.
R: Windows clients will correctly detect JAVA details.

Comment 5 Tomas Capek 2011-11-16 14:08:45 UTC
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,4 +1 @@
-C: Windows Java detection threw exception
+Previously, when the Windows Java detection issued an exception, no Windows clients were visible via the "condor_status -java" command. Now, the default configuration for the JAVA_SEPARATOR module has been updated and Windows clients correctly detect Java details in the described scenario.-C: No windows clients are visible via condor_status -java
-F: Update the default config for JAVA_SEPARATOR.
-R: Windows clients will correctly detect JAVA details.

Comment 6 errata-xmlrpc 2012-01-23 17:29:27 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2012-0045.html