[QPIDIT-128] misuse of JAVA_HOME causes tests to error without clear indication why

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.1.0, 0.2.0
• Fix Version/s: 0.2.0
• Component/s: Qpid Jms Shim
• Assignee: Kim van der Riet
• Reporter: Robbie Gemmell
• Created: 03/Jul/18 11:27
• Updated: 18/Oct/21 16:47
• Resolved: 16/Jul/18 17:12

Description

The interop suite misuses JAVA_HOME, and in doing so Python tries to run java from the wrong place. This results in the tests erroring out with note of a file not found, but with no indication what file wasn't found. Resorting to some prints for debugging, it emerges that Python is being asked to run Java with the wrong location

JAVA_HOME points to the root of the java installation, with the java command and various others then found in the bin subdir. The interop tests currently omit the bin subdir when JAVA_HOME was actually defined, but do include it (via a fragile and debatable hard coded default) when JAVA_HOME is not defined:

JAVA_HOME = os.getenv('JAVA_HOME', '/usr/bin') # Default only works in Linux
JAVA_EXEC = os.path.join(JAVA_HOME, 'java')