An error occurred while retrieving the list of Projects during portal login and VSE servers
Article ID: 74980
Updated On:
Products
Issue/Introduction
When logging to the Portal, getting the error "An error occurred while retrieving the list of VSE servers".
Not able to see the list of deployed VSMs under Monitor, Virtual Service Environments, VSE or look at the Server Health tab.
Error while retrieving list of Projects. (500 No JSON Formatted Retrofit Error <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/> <title>Error 503 </title> </head> <body> <h2>HTTP ERROR: 503</h2> <p>Problem accessing /res-hub/v1/projects. Reason: <pre> Service Unavailable</pre></p> <hr /><a href="http://eclipse.org/jetty">Powered by Jetty:// 9.3.z-SNAPSHOT</a><hr/> </body> </html> )
Registry startup logs may show below error:
ERROR org.springframework.boot.SpringApplication - Application startup failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'undertowEmbeddedServletContainerFactory' defined in class path resource [org/springframework/boot/autoconfigure/web/EmbeddedServletContainerAutoConfiguration$EmbeddedUndertow.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.context.embedded.undertow.UndertowEmbeddedServletContainerFactory]: Factory method 'undertowEmbeddedServletContainerFactory' threw exception; nested exception is java.lang.NoClassDefFoundError: io/undertow/servlet/api/InstanceFactory
at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:599)
Environment
All supported DevTest releases.
Cause
This issue happened when:
- activemq-all-5.15.2.jar was being used and was not the correct jar to use for creating Activemq virtual services.
- the content of the $DEVTEST_HOME/hotDelopy folder or custom extensions were duplicated in the $DEVTEST_HOME/lib folder.
- com.ibm.mq.allclient.9.1.1.0.jar and all the other MQ jar files were under the $DEVEST_HOME/lib folder.
- If the registry log shows the error for " 'undertowEmbeddedServletContainerFactory' then it is because of jboss client JAR missing from hotDeploy and(or) placed into /lib/shared. It could also be due to unsupported version of that JAR.
Resolution
The following actions were taken to resolve this issue.
The list below follows the order for the root causes above:
- adding the jars files listed below in $DEVTEST_HOME/hotDeploy folder on VSE server and restarting VSE:
For the above, refer to section "Tutorial 2: JMS Virtual Service Using DevTest Portal" in the documentation of the DevTest release you are running.
- When using custom extensions, place them under $DEVTEST_HOME/hotDelopy folder and it should be enough. No need to place the custom jar files under $DEVTEST_HOME/lib.
- All the MQ jar files were removed and only com.ibm.mq.allclient.jar and com.ibm.mq.commonservices.jar. were maintained.
com.ibm.mq.commonservices.jar
com.ibm.mq.headers.jar
com.ibm.mq.jar
com.ibm.mq.jmqi.jar
com.ibm.mq.pcf.jar
com.ibm.mqjms.jar
- For the above jars, refer to section "WebSphere MQ File Requirements" in the documentation of the DevTest release you are running.
- If "undertowEmbeddedServletContainerFactory" error in Registry is found then look for the jboss jar in hotDeploy folder and at any other location. Make sure the right version of that jar is placed in hotDeploy and is removed from any other location if placed manually.
Additional Information
Feedback
