Remedy - D2P - Post running arpayloaddeploymentutil.sh getting error:"Exception in thread "main" java.lang.UnsupportedClassVersionError: com/bmc/arsys/filedeployer/utilities/PayloadDeploymentUtil : Unsupported major.minor version 52.0"

Version 2
    Share:|

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Remedy AR System Server


    COMPONENT:

    AR System


    APPLIES TO:

    Remedy AR System File Deployment



    PROBLEM:

     

    When running arpayloaddeploymentutil.sh the following error is observed:

    ......................
    AR System Deployment Utility
    Deployment Utility has started.
    Deployment Utility has completed. Please check the arfiledeployer.log for the status.
    [ars@<SERVER> filedeployer]$
    Exception in thread "main" java.lang.UnsupportedClassVersionError:
    com/bmc/arsys/filedeployer/utilities/PayloadDeploymentUtil : Unsupported major.minor version 52.0

    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:803)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
    at java.net.URLClassLoader.defineClass(URLClassLoader.java:442)
    at java.net.URLClassLoader.access$100(URLClassLoader.java:64)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:354)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:348)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:347)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:312)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
    at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)

    ......................

    The file deployer log contains:

    ......................
    [ars@<SERVER> db]$ more arfiledeployer.log
    2018-03-15 07:32:16,963 [main] INFO com.bmc.arsys.filedeployer.ARFileDeployerDaemon - Loading AR monitor properties file
    2018-03-15 07:32:16,966 [main] INFO com.bmc.arsys.filedeployer.ARFileDeployerDaemon - Monitor RMI port is 7319
    2018-03-15 07:32:16,966 [main] INFO com.bmc.arsys.filedeployer.ARFileDeployerDaemon - Connecting with ARMonitor
    2018-03-15 07:32:17,179 [main] INFO com.bmc.arsys.filedeployer.ARFileDeployerDaemon - Successfully connected with ARMonitor
    2018-03-15 07:32:17,412 [main] INFO com.bmc.arsys.apitransport.ApiConfig - jrpcMode: true
    2018-03-15 07:32:17,420 [main] INFO com.bmc.arsys.api.Config - jniLoadMode: 1
    2018-03-15 07:32:17,420 [main] INFO com.bmc.arsys.api.Config - apiRecordingMode: 0
    2018-03-15 07:32:17,420 [main] INFO com.bmc.arsys.api.Config - apiRecordingLogDir:
    2018-03-15 07:32:17,420 [main] INFO com.bmc.arsys.api.Config - useConnectionPooling: true
    2018-03-15 07:32:17,420 [main] INFO com.bmc.arsys.api.Config - maxProxiesPerServer: 80
    2018-03-15 07:32:17,420 [main] INFO com.bmc.arsys.api.Config - idleConnectionsPerServer: 5
    2018-03-15 07:32:17,420 [main] INFO com.bmc.arsys.api.Config - connectionTimeout: 0
    2018-03-15 07:32:17,420 [main] INFO com.bmc.arsys.api.Config - connectionLifespan: 0
    2018-03-15 07:32:17,420 [main] INFO com.bmc.arsys.api.Config - timeUnit: MINUTES
    2018-03-15 07:32:17,420 [main] INFO com.bmc.arsys.api.Config - minimumSupportedServerRpcVersion: 12
    2018-03-15 07:32:17,420 [main] INFO com.bmc.arsys.api.Config - connectionMaxRetries: 1
    2018-03-15 07:32:17,420 [main] INFO com.bmc.arsys.api.Config - timeLagBetweenRetriesMillSec: 100
    2018-03-15 07:32:17,420 [main] INFO com.bmc.arsys.api.Config - stringizeFieldAssignments: false
    2018-03-15 07:32:17,420 [main] INFO com.bmc.arsys.api.Config - stringizeSetIfQualification: false
    2018-03-15 07:32:17,420 [main] INFO com.bmc.arsys.api.Config - useLegacyQualParser: false
    2018-03-15 07:32:17,420 [main] INFO com.bmc.arsys.api.Config - useLegacyAssignParser: false
    2018-03-15 07:32:17,420 [main] INFO com.bmc.arsys.api.Config - useLegacyQualFormatter: false
    2018-03-15 07:32:17,420 [main] INFO com.bmc.arsys.api.Config - useLegacyAssignFormatter: false
    2018-03-15 07:32:17,422 [main] INFO com.bmc.arsys.api.ARServerUser - APITIMEOUT from system property : null
    2018-03-15 07:32:17,422 [main] INFO com.bmc.arsys.api.ARServerUser - APITIMEOUT from Environment : null
    2018-03-15 07:32:17,422 [main] INFO com.bmc.arsys.api.ARServerUser - AROVERLAYGROUPS from system property : null
    2018-03-15 07:32:17,422 [main] INFO com.bmc.arsys.api.ARServerUser - AROVERLAYGROUPS from Environment : null
    2018-03-15 07:32:17,454 [main] INFO com.bmc.arsys.filedeployer.ARFileDeployerDaemon - Trying to connect to ARServer {Server_name} Retry No 1
    2018-03-15 07:32:17,981 [main] INFO com.bmc.arsys.apitransport.connection.ApiProxyManager - set timer period 60000 milliSec (00:01:00)
    2018-03-15 07:32:18,008 [main] INFO com.bmc.arsys.apitransport.connection.ApiProxyFactory - Connects to {Server_name}:31000 through com.bmc.arsys.api.ProxyJRpc@a1153bc
    2018-03-15 07:32:18,012 [main] INFO com.bmc.arsys.filedeployer.ARFileDeployerDaemon - Connected to ARServer {Server_name} Remedy Application Service
    2018-03-15 07:32:18,013 [main] INFO com.bmc.arsys.filedeployer.MonitorRegistrar - Registering monitor in AR System Monitor with existing GUID AGGAA5V0F3EKEAPEHIZDPD0PEOB4MG
    2018-03-15 07:32:18,114 [main] INFO com.bmc.arsys.filedeployer.MonitorRegistrar - Successfully registered monitor
    2018-03-15 07:32:18,359 [main] INFO com.bmc.arsys.filedeployer.FileDeployerConfig - Loading CCS settings for component ARServer_{Server_name}_7319_AGGAA5V0F3EKEAPEHIZDPD0PEOB4MG
    ......................

     

     


    CAUSE:

    The JAVA_HOME variable is set to use a different version (lower than the supported version) of Java than what Remedy is configured to use. (Running the Maintenance Tool produces the same error)


    SOLUTION:

     

    Update the JAVA_HOME variable to use the same version of Java that Remedy is configured to use.

     


    Article Number:

    000150785


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles