TEC1576694: Why does the “LaunchAnywhere either could not find a Java VM…..” message appear in the IntroscopeEnterpriseManagerSupport.log?

Document created by Tom_Wyszomierski Employee on May 26, 2016Last modified by SamCreek on May 26, 2016
Version 2Show Document
  • View in full screen mode

Document ID:  TEC1576694
Last Modified Date:  4/7/2015

Author: Tom_Wyszomierski
/external-link.jspa?url=http%3A%2F%2Fwww.ca.com%2Fus%2Fsupport%2Fca-support-online%2Fproduct-content%2Fknowledgebase-articles%2Ftec1576694.aspx

  • Products
    • CA Application Performance Management
  • Releases
    • CA Application Performance Management:Release:CA APM 9.7
    • CA Application Performance Management:Release:CA APM 9.6
    • CA Application Performance Management:Release:CA APM 9.5
  • Components
    • INTROSCOPE

 

 

 

Description:

This article explains why the message “LaunchAnywhere either could not find a Java VM...” appears in the support log. This is because this message is an explicitly defined property in the Introscope_Enterprise_Manager.lax file.

 

Solution:

Why does the Message “LaunchAnywhere either could not find a Java VM…..” appear in the IntroscopeEnterpriseManagerSupport.log?

While starting an EM, you may notice the following info message appears:

[INFO] [Manager.Support.Introscope_WebView.lax] lax.nl.message.vm.not.loaded=LaunchAnywhere either could not find a Java VM, or the Java VM on this system is too old. LaunchAnywhere requires a Java 2 VM in order to launch Introscope.

 

Why does this message appear?

This message appears because of auditing purposes. It is the result of the EM reading every property defined in the Intropscope_Enterprise_Manager.lax file. In this case, the below property is read:

# LAX.NL.MESSAGE.VM.NOT.LOADED

# message displayed in a user dialog if NO VM from the lax.nl.valid.vm.list can be found. Note: This property is internal to the InstallAnywhere launcher. Introscope has separate Java requirements. For more information, consult the "System Requirements" section of Introscope's user documentation.

lax.nl.message.vm.not.loaded=LaunchAnywhere either could not find a Java VM, or the Java VM on this system is too old. LaunchAnywhere requires a Java 2 VM in order to launch Introscope.

 

Should I be concerned about this message?

No, this message can be safely ignored. The LaunchAnywhere jvm referred to by this message and defined in the property “lax.nl.valid.vm.list=” is only used during the EM installation. The EM java process uses the property “lax.nl.current.vm=” to run.

 

 

Search the Entire CA APM Knowledge Base

 

search-kb.jpg

 

Attachments

    Outcomes