Troubleshooting
Problem
ITIC fusion log shows error "Calling method login on proxy for service ApiServerServiceInterface failed permanently"
Symptom
Full error message from fusion.log:
Error Message: Database connection failed
com.ibm.cdb.platform.remoting.UnavailableServiceException: Calling method login on proxy for service ApiServerServiceInterface failed permanently
Error occurred during: Connecting to data source
Error occurred in: CMDBConnection.testConnection()
Operation failed on: Data Schema: null, Host: 1.2.3.4, Port: 9433, Trusted Store Location: null, Use SSL: false, Version: 0, User: <user>, Password: <hidden>
Error resolution action: Stopped processing
Error trace:
23 Mar 2015 13:26:29:157 [ERROR]
--------------------------------
com.ibm.cdb.platform.remoting.UnavailableServiceException: Calling method login on proxy for service ApiServerServiceInterface failed permanently
com.mro.fusion.util.FusionException: com.ibm.cdb.platform.remoting.UnavailableServiceException: Calling method login on proxy for service ApiServerServiceInterface failed permanently
at com.collation.proxy.api.client.ApiSessionImpl.init(ApiSessionImpl.java:157)
Error Message: Database connection failed
com.ibm.cdb.platform.remoting.UnavailableServiceException: Calling method login on proxy for service ApiServerServiceInterface failed permanently
Error occurred during: Connecting to data source
Error occurred in: CMDBConnection.testConnection()
Operation failed on: Data Schema: null, Host: 1.2.3.4, Port: 9433, Trusted Store Location: null, Use SSL: false, Version: 0, User: <user>, Password: <hidden>
Error resolution action: Stopped processing
Error trace:
23 Mar 2015 13:26:29:157 [ERROR]
--------------------------------
com.ibm.cdb.platform.remoting.UnavailableServiceException: Calling method login on proxy for service ApiServerServiceInterface failed permanently
com.mro.fusion.util.FusionException: com.ibm.cdb.platform.remoting.UnavailableServiceException: Calling method login on proxy for service ApiServerServiceInterface failed permanently
at com.collation.proxy.api.client.ApiSessionImpl.init(ApiSessionImpl.java:157)
Diagnosing The Problem
Review the error message above and confirm the host, port and user are correct. If they are check the following.
Resolving The Problem
1) Confirm that the port in the message matches com.ibm.cdb.service.registry.public.port in
dist/etc/collation.properties on the TADDM server ITIC is configured for.
2) Confirm that there is no firewall between the ITIC server and the TADDM server blocking
communication. Both the Public service registry port (default 9433) and the Api server port(default 9530/9531) need to be open both ways between these two servers.
3) Confirm via control status that TADDM is running on the server. Also check dist/bin for recent javacore* files since the last TADDM start. If TADDM had an OutOfMemory it may be unavailable to service requests even if it is running.
4) Confirm that the user/password configured in ITIC is correct, run an api query on the TADDM server ensuring it works, for example, this api find will return a count of computer system objects if the user, password and host are valid;
dist/etc/collation.properties on the TADDM server ITIC is configured for.
2) Confirm that there is no firewall between the ITIC server and the TADDM server blocking
communication. Both the Public service registry port (default 9433) and the Api server port(default 9530/9531) need to be open both ways between these two servers.
3) Confirm via control status that TADDM is running on the server. Also check dist/bin for recent javacore* files since the last TADDM start. If TADDM had an OutOfMemory it may be unavailable to service requests even if it is running.
4) Confirm that the user/password configured in ITIC is correct, run an api query on the TADDM server ensuring it works, for example, this api find will return a count of computer system objects if the user, password and host are valid;
dist/sdk/bin/api.sh -u <user> -p <password> -H <host> find --count ComputerSystem
5) Check the values of these properties in dist/etc/collation.properties;
com.ibm.cdb.global.hostname=
com.ibm.cdb.interserver.hostname=
Normally they are valued at all 0's, eg. 0.0.0.0 which means 'all interfaces'. If you value the global property at a specific host or IP, use the same host/IP in ITIC.
If Incase, 0.0.0.0 interface is disabled/restricted, then use below:
com.ibm.cdb.global.hostname=<hostname of PSS > or <FQDN>
com.ibm.cdb.interserver.hostname=<hostname of PSS > or <FQDN>
If issue still persist, then raise ticket with IBM TADDM support.
[{"Product":{"code":"SSPLFC","label":"Tivoli Application Dependency Discovery Manager"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"7.2.2;7.3","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
Modified date:
20 May 2020
UID
swg21882599