IBM Support


ConnectException on default WS port during server start

Troubleshooting


Problem

ConnectException on default WS port during server start up after installing madappsvcs.ear

Symptom

The following error is returned after installing and starting com.ibm.mdm.mds.appservices.app (madappsvcs.ear found under native.war/lib/sdk/):
"
00000076 ContextLoader E org.springframework.web.context.ContextLoader initWebApplicationContext Context initialization failed
                                 org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mds' defined in ServletContext resource [/WEB-INF/beans-rest.xml]:
Cannot resolve reference to bean 'serviceMetaData' while setting bean property 'serviceMetaData'; nested exception is org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'serviceMetaData' defined in ServletContext resource [/WEB-INF/beans-rest.xml]:
Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.initiate.client.generic.metadata.ServiceMetaData]:
Factory method 'createInstance' threw exception; nested exception is java.lang.RuntimeException: ErrCode: ECOMM ErrText: null
        at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:359)
...
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'serviceMetaData' defined in ServletContext resource [/WEB-
INF/beans-rest.xml]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instan
tiate [com.initiate.client.generic.metadata.ServiceMetaData]: Factory method 'createInstance' threw exception; nested exception is java.lang.RuntimeException
: ErrCode: ECOMM ErrText: null
        at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:599)
...
Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.initiate.client.generic.metadata.ServiceMetaData]: Factory method
'createInstance' threw exception; nested exception is java.lang.RuntimeException: ErrCode: ECOMM ErrText: null
        at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:189)
        ... 49 more
Caused by: java.lang.RuntimeException: ErrCode: ECOMM ErrText: null
        at com.initiate.client.generic.metadata.BaseMetaDataBuilder.getDictionary(BaseMetaDataBuilder.java:79)
...
"

Cause

MDM Knowledge Center specifies the following limitation regarding the startup order:
The first application might not start completely before the application server tries to start the next application in the startup order. This scenario might cause unexpected results if the second application depends on the first application.

Startup order specifies the order in which applications are started when the server starts. The startup order is like a starting weight. The application with the lowest starting weight is started first.
The Web-service and web-service-virtual have the same 'startup order' 1. Therefore they are started in parallel. Additionally taken into account the before mentioned limitation it will cause a race condition between the startup of both services.

Environment

The issue only occurs during server start up (whether server is started manually or as part of the automated tests).
The deployed REST APIs is not affected (it runs OK after server is started and it produces expected results).

Resolving The Problem

As documented in Knowledge Center madappsvcs (REST API) can be installed on the same server as the operational server or on a different server:
https://www.ibm.com/support/knowledgecenter/en/SSWSR9_11.6.0/com.ibm.mdshs.esoatoolkit.doc/topics/t_esoatoolkit_installingrestservice.html
"You can install it in the same server as the operational server or on a different server."

The issue does not occur if installing madappsvcs on a different server from the operational server (and starting the different server after the operational server has been started).

[{"Product":{"code":"SSWSR9","label":"IBM InfoSphere Master Data Management"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF010","label":"HP-UX"}],"Version":"11.0;11.3;11.4;11.5;11.6;11.6.0.1;11.6.0.2;11.6.0.3;11.6.0.4","Edition":"Standard Edition","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
27 April 2022

UID

swg22011856