Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Suggested Answer
  • Replies reply
    1
  • Answers answer
    1
  • Subscribers subscribers
    12
  • Views views
    65
  • Users 0 members are here
Related
Options

PPM 10, ERROR (KNTA-10538) ERROR server:ActiveMQ Task

Pedro_X 
Hello Community, please I need your urgent help to resolve my PPM error. From one moment to the next while I was working on creating a form, the platform began to fail for no apparent reason.

Below is the detail of the error:

[ppm@sgptest bin]$ sh kStart.sh
JAVA_HOME = /usr/lib/jvm/java-1.8.0-openjdk
openjdk version "1.8.0_412"
OpenJDK Runtime Environment (build 1.8.0_412-b08)
OpenJDK 64-Bit Server VM (build 25.412-b08, mixed mode)
JAVA_HOME = /usr/lib/jvm/java-1.8.0-openjdk
openjdk version "1.8.0_412"
OpenJDK Runtime Environment (build 1.8.0_412-b08)
OpenJDK 64-Bit Server VM (build 25.412-b08, mixed mode)
server.conf path: null
STATUS server:main:(?:?):2024/09/05-11:46:14.868 CLT: Logging reconfiguration complete
STATUS server:main:(ServerStartupSanity.java:86):2024/09/05-11:46:14.872 CLT: Running pre-startup checks for node kintana in standalone mode
STATUS server:main:(ServerStartupSanity.java:86):2024/09/05-11:46:14.875 CLT: Checking: /home/ppm/PPM/server.conf
STATUS server:main:(ServerStartupSanity.java:86):2024/09/05-11:46:14.882 CLT: All pre-startup checks completed for node kintana
STATUS server:main:(PPMVersionCheck.java:88):2024/09/05-11:46:14.938 CLT: PPM DB version: 10.0.3.0
STATUS server:main:(PPMVersionCheck.java:89):2024/09/05-11:46:14.938 CLT: PPM version.txt version: 10,0,3,36848
Node kintana sanity passed. See server log for detail.
OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
[ppm@sgptest bin]$ server.conf path: null
STATUS server:main:(?:?):2024/09/05-11:46:16.512 CLT: Logging reconfiguration complete
STATUS server:main:(PPMTomcatMonitor.java:36):2024/09/05-11:46:17.097 CLT: Starting web context: redirect
STATUS server:main:(PPMTomcatMonitor.java:48):2024/09/05-11:46:17.279 CLT: Completed start of web context: redirect
STATUS server:main:(PPMTomcatMonitor.java:32):2024/09/05-11:46:17.279 CLT: Starting web context: dashboard
STATUS server:main:(PPMTomcatMonitor.java:42):2024/09/05-11:46:17.709 CLT: Completed start of web context: dashboard
STATUS server:main:(PPMTomcatMonitor.java:32):2024/09/05-11:46:17.709 CLT: Starting web context: workplan-ng
STATUS server:main:(PPMTomcatMonitor.java:42):2024/09/05-11:46:17.746 CLT: Completed start of web context: workplan-ng
STATUS server:main:(PPMTomcatMonitor.java:32):2024/09/05-11:46:17.747 CLT: Starting web context: utility_portlets
STATUS server:main:(PPMTomcatMonitor.java:42):2024/09/05-11:46:17.798 CLT: Completed start of web context: utility_portlets
STATUS server:main:(PPMTomcatMonitor.java:32):2024/09/05-11:46:17.798 CLT: Starting web context: itg
STATUS server:main:(PPMTomcatMonitor.java:82):2024/09/05-11:46:18.281 CLT: Starting listener: com.mercury.itg.servlet.ServletContextListenerImpl
STATUS server:main:(PPMTomcatMonitor.java:85):2024/09/05-11:46:18.282 CLT: Completed Start of listener: com.mercury.itg.servlet.ServletContextListenerImpl
STATUS server:main:(PPMTomcatMonitor.java:82):2024/09/05-11:46:18.282 CLT: Starting listener: com.kintana.core.web.listener.ServerStartListener
STATUS server:main:(ServerStartListener.java:85):2024/09/05-11:46:18.753 CLT: Servlet container: PPM Web Container
STATUS server:main:(Server.java:853):2024/09/05-11:46:19.662 CLT: Server is starting in standalone mode
STATUS server:main:(Server.java:866):2024/09/05-11:46:19.666 CLT: Verifying Autopass jars ...
STATUS server:main:(Server.java:1486):2024/09/05-11:46:19.797 CLT: Starting RMI on port 1099
STATUS server:main:(Server.java:1332):2024/09/05-11:46:19.810 CLT: Initializing ESAPI Library
STATUS server:main:(Server.java:1011):2024/09/05-11:46:20.003 CLT: Project and Portfolio Management v10.0.3
STATUS server:main:(Server.java:1017):2024/09/05-11:46:20.030 CLT: Dirección IP local = 127.0.0.1
STATUS server:main:(Server.java:1033):2024/09/05-11:46:25.632 CLT: Licencia aceptada.
STATUS server:main:(Server.java:1059):2024/09/05-11:46:25.684 CLT: Thu Sep 05 11:46:25 CLT 2024
ERROR server:main:(Server.java:1122):2024/09/05-11:46:25.731 CLT: Se ha producido un error desconocido. Para obtener más información, póngase en contacto con el administrador de PPM y proporcione el siguiente número de GUID:
GUID=78249B96-60CE-F087-549A-556272D40123
Generated Time=2024/09/05-11:46:25.730 CLT
Se ha producido un error desconocido. Para obtener más información, póngase en contacto con el administrador de PPM y proporcione el siguiente número de GUID:
GUID=78249B96-60CE-F087-549A-556272D40123
Generated Time=2024/09/05-11:46:25.730 CLT
nested detail:Se ha producido un error desconocido. Para obtener más información, póngase en contacto con el administrador de PPM y proporcione el siguiente número de GUID:
GUID=B40091DC-CB44-0184-7AAB-DF0559820608
Generated Time=2024/09/05-11:46:25.730 CLT

Se ha producido un error desconocido. Para obtener más información, póngase en contacto con el administrador de PPM y proporcione el siguiente número de GUID:
GUID=78249B96-60CE-F087-549A-556272D40123
Generated Time=2024/09/05-11:46:25.730 CLT
at com.kintana.core.cache.CacheManager.init(CacheManager.java:119)
at com.kintana.core.cache.CacheManager.<init>(CacheManager.java:78)
at com.kintana.core.cache.CacheManager.loadFromFile(CacheManager.java:298)
at com.kintana.core.server.ISIntegrityServerImpl.<init>(ISIntegrityServerImpl.java:355)
at com.kintana.core.server.Server.main(Server.java:1074)
at com.kintana.core.cache.CacheManager.init(CacheManager.java:117)
... 36 more
Caused by: java.lang.ClassNotFoundException: com.microfocus.ppm.webhook.WebHookConfigCacheLoader
at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1377)
at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1200)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at com.kintana.core.cache.CachePropertiesAccessor.getInstance(CachePropertiesAccessor.java:51)
... 40 more
ERROR server:main:(Server.java:1125):2024/09/05-11:46:25.735 CLT: *** ERROR: No se puede iniciar el servidor de Project and Portfolio Management (KNTA-10538)
STATUS server:main:(Server.java:1177):2024/09/05-11:46:25.736 CLT: The current process ID is saved in: /home/ppm/PPM/server/kintana/tmp/kintana.pid
STATUS server:main:(PPMTomcatMonitor.java:85):2024/09/05-11:46:25.736 CLT: Completed Start of listener: com.kintana.core.web.listener.ServerStartListener
STATUS server:main:(PPMTomcatMonitor.java:82):2024/09/05-11:46:25.737 CLT: Starting listener: org.springframework.web.context.ContextLoaderListener

ERROR server:ActiveMQ Task-434250:(TaskRunnerFactory.java:202):2024/09/05-11:48:39.273 CLT: Error in thread 'ActiveMQ Task-434250'
java.lang.NullPointerException
ERROR server:ActiveMQ Task-434255:(TaskRunnerFactory.java:202):2024/09/05-11:48:39.273 CLT: Error in thread 'ActiveMQ Task-434255'
java.lang.NullPointerException
ERROR server:ActiveMQ Task-434256:(TaskRunnerFactory.java:202):2024/09/05-11:48:39.274 CLT: Error in thread 'ActiveMQ Task-434256'
java.lang.NullPointerException
ERROR server:ActiveMQ Task-434254:(TaskRunnerFactory.java:202):2024/09/05-11:48:39.274 CLT: Error in thread 'ActiveMQ Task-434254'
java.lang.NullPointerException

Searching the Internet I found solutions regarding increasing the size of the java and updating certain Database tables (truncate ACTIVEMQ_LOCK; ACTIVEMQ_ACKS; ACTIVEMQ_MSGS), however the problem still persists.

  • Suggested Answer

    0  

    Hi Pedro,

    The root cause is:  java.lang.ClassNotFoundException: com.microfocus.ppm.webhook.WebHookConfigCacheLoader

    This error occurs in the PPM cache loading mechanism and has nothing to do with ActiveMQ. The ActiveMQ error messages are only symptoms, the root cause is the cache loading failure,

    This issue can happen because of two possible different mistakes:

    1) You've replaced some PPM Jar files with some older Jar file version that don't include this class

    2) You're on a PPM version that doesn't include this class in PPM code, but you have deployed a newer version of cache.conf that include a mention to this class in the cache configuration - so PPM will try to load it and won't find it. Be very careful when modifying cache.conf, if you've modified it before error occured then this is likely the problem.

    If that information doesn't allow you to address the issue, please open a ticket with Support to get that looked into. 

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.