Skip to main content
10-Marble
March 17, 2025
Question

Method Server fails to launch : Nested exception is: java.lang.NullPointerException

  • March 17, 2025
  • 1 reply
  • 520 views

 

 

2025-03-17 23:30:46,267 FATAL [main] wt.method.server - MethodServerMain abort wt.services.ManagerException: wt.util.WTException: java.lang.NullPointerException
Nested exception is: java.lang.NullPointerException
Nested exception is: wt.util.WTException: java.lang.NullPointerException
Nested exception is: java.lang.NullPointerException
	at wt.access.AccessSelector.getQuerySpec(AccessSelector.java:346)
	at wt.access.AccessSelector.getQuerySpec(AccessSelector.java:312)
	at wt.access.StandardAccessControlManager.getPolicyAcl(StandardAccessControlManager.java:2344)
	at wt.access.StandardAccessControlManager.getPolicyAcl(StandardAccessControlManager.java:4272)
	at wt.access.StandardAccessControlManager._hasAccess(StandardAccessControlManager.java:10566)
	at wt.access.StandardAccessControlManager.hasAccess(StandardAccessControlManager.java:538)
	at jdk.internal.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at wt.services.ServiceFactory$ServerInvocationHandler.invoke(ServiceFactory.java:399)
	at com.sun.proxy.$Proxy68.hasAccess(Unknown Source)
	at wt.pds.SurrogateAccessController.checkAccess(SurrogateAccessController.java:94)
	at wt.pds.CompositeAccessController.checkAccess(CompositeAccessController.java:125)
	at wt.pds.StandardACProcessor.processResults(StandardACProcessor.java:130)
	at wt.pds.SequentialResultBuilder.build(SequentialResultBuilder.java:453)
	at wt.pds.BasicResultCursor.next(BasicResultCursor.java:93)
	at wt.pds.SQLDatabasePds.query(SQLDatabasePds.java:880)
	at wt.pom.PersistentObjectManager.query(PersistentObjectManager.java:1077)
	at wt.pom.PersistentObjectManager.query(PersistentObjectManager.java:986)
	at wt.fc.StandardPersistenceManager._query(StandardPersistenceManager.java:1972)
	at wt.fc.StandardPersistenceManager._find(StandardPersistenceManager.java:2008)
	at wt.fc.StandardPersistenceManager.find(StandardPersistenceManager.java:655)
	at wt.fc.StandardPersistenceManager.find(StandardPersistenceManager.java:407)
	at jdk.internal.reflect.GeneratedMethodAccessor38.invoke(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at wt.services.ServiceFactory$ServerInvocationHandler.invoke(ServiceFactory.java:399)
	at com.sun.proxy.$Proxy29.find(Unknown Source)
	at wt.scheduler.StandardSchedulingService.getScheduleItems(StandardSchedulingService.java:632)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at wt.services.ServiceFactory$ServerInvocationHandler.invoke(ServiceFactory.java:399)
	at com.sun.proxy.$Proxy81.getScheduleItems(Unknown Source)
	at wt.scheduler.StandardSchedulingService.addItemUnique(StandardSchedulingService.java:1579)
	at wt.eff.StandardEffService.ensureAuditPurging(StandardEffService.java:2112)
	at wt.eff.StandardEffService$12.notifyVetoableEvent(StandardEffService.java:1726)
	at wt.events.StandardKeyedEventBranch.intDispatchEvent(StandardKeyedEventBranch.java:320)
	at wt.events.StandardKeyedEventBranch.dispatchVetoableEvent(StandardKeyedEventBranch.java:255)
	at wt.events.StandardKeyedEventDispatcher.intDispatchEvent(StandardKeyedEventDispatcher.java:304)
	at wt.events.StandardKeyedEventDispatcher.dispatchVetoableEvent(StandardKeyedEventDispatcher.java:228)
	at wt.services.StandardManagerService.intDispatchVetoableEvent(StandardManagerService.java:410)
	at wt.services.StandardManagerService.dispatchVetoableEvent(StandardManagerService.java:303)
	at wt.services.StandardManagerService.performStartupProcess(StandardManagerService.java:185)
	at wt.services.StandardManager.startup(StandardManager.java:459)
	at wt.services.StandardServicesHandler.start(StandardServicesHandler.java:44)
	at wt.method.MethodServerMain.run(MethodServerMain.java:584)
	at wt.method.MethodServerMain.main(MethodServerMain.java:353)

2025-03-17 23:30:46,402 FATAL [main] wt.method.server.shutdown - Stopping services...
2025-03-17 23:30:47,963 INFO [main] wt.system.err - 2025-00-17 18:00:47 ERROR com.wincomplm.wex.kernel.impl.manager.WexKernelManager - Failed to unload the Wex Kernel [OK for startup]
2025-03-17 23:30:52,542 INFO [QueryBuilder Type Pre-Loader] wt.pom.statementCache.summary - StatementCache: wt.util.Cache%1760851720 [size=50, count=50, hits=6000, misses=247, overflows=95]
2025-03-17 23:30:49,547 INFO [LicenseScheduleQueue.SchedulingThread] wt.licenseusage.licensing.SynchronizeLicense wcadmin - Executing scheduled queue: synchronizeLicense
2025-03-17 23:30:49,137 INFO [commonScheduleQueue.SchedulingThread] wt.pds.passwordexpiry.PasswordExpiryWarningService wcadmin - Datastore password expiry warnings will commence 15 days in advance of expiration. (Configurable via property: wt.pds.passwordExpirationChecking.days)
2025-03-17 23:31:25,451 INFO [main] wt.method.server.shutdown.services - All managers shut down.
2025-03-17 23:31:25,453 FATAL [main] wt.method.server.shutdown - MethodServer stopped

 

 

 

 

1 reply

avillanueva
23-Emerald II
March 17, 2025

What came before this log message? That might be relevant. What state is this system? Was it running before and then just stopped or is this a new install?

Searching knowledge base on "wt.access.AccessSelector.getQuerySpec" comes back with lots of causes for failing to startup. Any that seem relevant?