Error starting Topology server TPLSPROC
search cancel

Error starting Topology server TPLSPROC

book

Article ID: 226924

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

Topology started tasks ends with RC=100:

IEF695I START TPLSPROC WITH JOBNAME TPLSPROC         
$HASP373 TPLSPROC STARTED                            
IEF403I TPLSPROC - STARTED - TIME=09.21.21           
IGD104I UNIX FILE WAS RETAINED, DDNAME IS (SYS00001) 
FILENAME IS (/etc/resolv.conf)                       
IEF285I   TCPIP.STANDARD.TCPXLBIN                    
IEF285I   VOL SER NOS= Z24RES.                       
IGD104I UNIX FILE WAS RETAINED, DDNAME IS (SYS00006) 
FILENAME IS (/etc/ipnodes)                           
IGD104I UNIX FILE WAS RETAINED, DDNAME IS (SYS00007) 
FILENAME IS (/etc/hosts)                             
IEF285I   BROADCOM.TOPOL.CUSOPTN                     
IEF285I   VOL SER NOS= D12345.                       
IEF285I   BROADCOM.TOPOL.CTPLOPTN                    
IEF285I   VOL SER NOS= D12345.                       
IEF285I   BROADCOM.TOPOL.CUSOPTN                     
IEF285I   VOL SER NOS= D12345.                       
IEF404I TPLSPROC - ENDED - TIME=09.21.31             
$HASP395 TPLSPROC ENDED - RC=0100                    

The joblog shows the messages below:

 JVMJZBL2007E Stack trace follows:
 java.lang.reflect.InvocationTargetException
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
  at java.lang.reflect.Method.invoke(Method.java:508)
  at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48)
  at org.springframework.boot.loader.Launcher.launch(Launcher.java:87)
  at org.springframework.boot.loader.Launcher.launch(Launcher.java:51)
  at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:52)
 Caused by: org.springframework.context.ApplicationContextException: Unable to start web server; nested exception is org.springframew
 ork.boot.web.server.WebServerException: Unable to start embedded Tomcat

 Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'graphQLServletRegistrati
 onBean' defined in class path resource [com/oembedler/moon/graphql/boot/GraphQLWebAutoConfiguration.class]: Unsatisfied dependency e
 xpressed through method 'graphQLServletRegistrationBean' parameter 0; nested exception is org.springframework.beans.factory.Unsatisf
 iedDependencyException: Error creating bean with name 'graphQLHttpServlet' defined in class path resource [com/oembedler/moon/graphq
 l/boot/GraphQLWebAutoConfiguration.class]: Unsatisfied dependency expressed through method 'graphQLHttpServlet' parameter 0; nested 
 exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'invocationInputFactory
 ' defined in class path resource [com/oembedler/moon/graphql/boot/GraphQLWebAutoConfiguration.class]: Unsatisfied dependency express
 ed through method 'invocationInputFactory' parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyE
 xception: Error creating bean with name 'graphQLSchemaProvider' defined in class path resource [com/oembedler/moon/graphql/boot/Grap
 hQLWebAutoConfiguration.class]

errorCode":"TCL105E","message":"SQL Exception occurred while creating the query view","cause
 ":"org.sqlite.SQLiteException","additionalInfo":[]}
  at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:798)
  at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:539)
  at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapab
 leBeanFactory.java:1338)

 

Environment

Release : 14.0

Component : TOPOLOGY

Cause

When using DB_TYPE=SQLITE a possible cause is that the job TPLSERUN has not been run with success.

Resolution

Run the job TPLSERUN and make sure it gets a return code 0.

This job creates the topology.db file required to start the server.

Additional Information

Run the extractor-aggregator (TPLSERUN)