Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only

  • 1.  The SystemOut.log indicate that services ARE starting.

    Posted Wed July 28, 2021 11:00 AM
      |   view attached

    When I start Maximo I see these errors in the Systemout log file.

    Maximo is opening connections to the Maximo database and retrieving the system properties.

     The services are starting but the errors that are being generated means that the Maximo front-end is not starting.

    com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0271E: Uncaught init() exception created by servlet [MAXIMOStartupServlet] in application [MAXIMO]: java.lang.UnsupportedClassVersionError: JVMCFRE003 bad major version; class=oracle/jdbc/OracleDriver, offset=6
    at java.lang.ClassLoader.defineClassImpl(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:331)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:155)
    at java.net.URLClassLoader.defineClass(URLClassLoader.java:715)
    at java.net.URLClassLoader.access$400(URLClassLoader.java:94)
    at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1169)
    at java.security.AccessController.doPrivileged(AccessController.java:488)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:598)
    at com.ibm.ws.bootstrap.ExtClassLoader.findClass(ExtClassLoader.java:244)
    at java.lang.ClassLoader.loadClassHelper(ClassLoader.java:786)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:764)
    at com.ibm.ws.bootstrap.ExtClassLoader.loadClass(ExtClassLoader.java:135)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:741)
    at com.ibm.ws.classloader.ProtectionClassLoader.loadClass(ProtectionClassLoader.java:62)
    at com.ibm.ws.classloader.ProtectionClassLoader.loadClass(ProtectionClassLoader.java:58)
    at com.ibm.ws.classloader.CompoundClassLoader.loadClass(CompoundClassLoader.java:587)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:741)
    at java.lang.Class.forNameImpl(Native Method)
    at java.lang.Class.forName(Class.java:263)
    at psdi.server.MXServer.checkMtEnabled(MXServer.java:6320)
    at psdi.server.MXServer.start(MXServer.java:3622)
    at psdi.servlet.MAXIMOStartupServlet.init(MAXIMOStartupServlet.java:92)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:345)
    at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.init(ServletWrapperImpl.java:168)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.loadOnStartupCheck(ServletWrapper.java:1369)
    at com.ibm.ws.webcontainer.webapp.WebApp.doLoadOnStartupActions(WebApp.java:649)
    at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinally(WebApp.java:615)
    at com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:426)
    at com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:88)
    at com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:171)
    at com.ibm.ws.webcontainer.WSWebContainer.addWebApp(WSWebContainer.java:904)
    at com.ibm.ws.webcontainer.WSWebContainer.addWebApplication(WSWebContainer.java:789)
    at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:427)
    at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:719)
    at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1211)
    at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1464)
    at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:642)
    at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:1042)
    at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:795)
    at com.ibm.ws.runtime.component.ApplicationMgrImpl$5.run(ApplicationMgrImpl.java:2279)
    at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:5536)
    at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:5662)
    at com.ibm.ws.security.core.SecurityContext.runAsSystem(SecurityContext.java:255)
    at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2284)
    at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:436)
    at com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:123)
    at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:379)
    at com.ibm.ws.runtime.component.CompositionUnitMgrImpl.access$500(CompositionUnitMgrImpl.java:127)
    at com.ibm.ws.runtime.component.CompositionUnitMgrImpl$CUInitializer.run(CompositionUnitMgrImpl.java:985)
    at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:524)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892)

     

    System information

    -----------

    Database product version: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production

    Version 19.3.0.0.0 -- 19.0

    Database driver: Oracle JDBC driver

    Database driver version: 19.3.0.0.0

     

    WebSphere Platform 8.5.5.18 [ND 8.5.5.18 cf182036.01] [IBMJAVA71 7.1.4.70 cf182036.01]

    Windows Server 2012 R2, version 6.3

    Java version = 1.8.0_261

     

    Tivoli's process automation engine 7.6.0.9 Build 20171127-0100 DB Build V7609-45,

    IBM Maximo Asset Management Work Centers 7.6.0.3 Build 20171121-0723 DB Build V7603-175,

    IBM Maximo Asset Management Scheduler 7.6.7.0 Build 20171127-0100 DB Build V7670-56,

    IBM Maximo Anywhere 7.6.3.0 Build 20180618_173141-0500 DB Build V7630-04,

    IBM TPAE Integration Framework 7.6.0.9 Build 20171126-2330 DB Build V7609-32,

    IBM Maximo Asset Management 7.6.0.9 Build 20171127-0100 DB Build V7604-01,

    TPAE OSLC Object Structure 7.6.3.0 Build 20180618_173131-0500 DB Build V7630-01

     



    ------------------------------
    Faryal Amjad
    ------------------------------

    #Maximo
    #AssetandFacilitiesManagement

    Attachment(s)

    log
    SystemOut.log   158 KB 1 version


  • 2.  RE: The SystemOut.log indicate that services ARE starting.

    Posted Thu July 29, 2021 09:14 AM

    I would confirm that all of your JVMs are actually set to run using the Java 1.8. It looks like they are running as Java 1.6. While 1.8 might be installed, the default is 1.6 for WebSphere 8.5.5 (though they have switched to 1.8 as the bundled version in more recent fixes). I assume at one point you had 1.7 installed and then removed it for 1.8 and the JVMs reverted from 1.7 to 1.6 during that point. 

    You can change the SDK using the managesdk command line utility or you can login to the WebSphere admin console, select each JVM (including the node agents and DMGR if you have them), and then under the "Server Infrastructure" section choose Java SDKs and confirm that 1.8_64 is set to be the default. Screenshot below of what it should look like.



    ------------------------------
    Steven Shull
    ------------------------------

    Original Message


  • 3.  RE: The SystemOut.log indicate that services ARE starting.

    Posted Thu July 29, 2021 12:26 PM
    Steven is spot on.    java.lang.UnsupportedClassVersionError when starting JVM

    ------------------------------
    Bradley K. Downing , MBA
    Solutions Engineer
    IBM
    Bakersfield CA
    ------------------------------

    Original Message


Related Content