Single Sign-On server fails to start after Domain Name Server modifications
search cancel

Single Sign-On server fails to start after Domain Name Server modifications

book

Article ID: 305676

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

Symptoms:
When you modify the Domain Name Server (DNS):
  • The Single Sign-On (SSO) server fails to start.
  • The catalina.log file (located in C:\Program Files\VMware\Infrastructure\SSOServer\logs\) contains entries similar to:

    SEVERE [pool-3-thread-1] com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized MACHINENAME: failed to parse runtime descriptor: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
    java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
    at com.sun.xml.ws.handler.HandlerChainsModel.parseHandlerFile
    (HandlerChainsModel.java:302)
    at com.sun.xml.ws.util.HandlerAnnotationProcessor.buildHandlerInfo
    (HandlerAnnotationProcessor.java:122)
    at com.sun.xml.ws.server.EndpointFactory.processHandlerAnnotation(EndpointFactory.java:261)
    at com.sun.xml.ws.server.EndpointFactory.createEndpoint(EndpointFactory.java:210)
    at com.sun.xml.ws.api.server.WSEndpoint.create(WSEndpoint.java:467)
    at com.sun.xml.ws.transport.http.DeploymentDescriptorParser.parseAdapters
    (DeploymentDescriptorParser.java:253)
    at com.sun.xml.ws.transport.http.DeploymentDescriptorParser.parse
    (DeploymentDescriptorParser.java:147)
    at com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized
    (WSServletContextListener.java:108)
    at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4779)
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5273)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:897)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:873)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:615)
    at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1095)
    at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1617)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    at java.util.concurrent.FutureTask.run(FutureTask.java:138)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662)
    Caused by: java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sun.xml.ws.handler.HandlerChainsModel.parseHandlerFile(HandlerChainsModel.java:299)
    ... 21 more
    Caused by: java.lang.IllegalStateException: ComponentUtils not initialized
    at com.rsa.ims.components.ComponentUtils.getValidInstance(ComponentUtils.java:142)
    at com.rsa.ims.components.ComponentUtils.getBean(ComponentUtils.java:104)
    at com.rsa.riat.sts.handlers.WSSecurityHandler.init(WSSecurityHandler.java:81)
    ... 26 more
    SEVERE [pool-3-thread-1] org.apache.catalina.core.StandardContext.startInternal Error listenerStart
    SEVERE [pool-3-thread-1] org.apache.catalina.core.StandardContext.startInternal Context [/ims] startup failed due to previous errors
  • The imsTrace.log file (located in C:\Program Files\VMware\Infrastructure\SSOServer\logs\) contains entries similar to:

    Error creating bean with name 'JGroupsConfigFactory' defined in class path resource [ims-components-cache-jgroups.xml]: Invocation of init method failed; nested exception is org.jgroups.ChannelException: unable to setup the protocol stack
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.
    createBean(AbstractAutowireCapableBeanFactory.java:452)
    at org.springframework.beans.factory.support.AbstractBeanFactory$1.
    getObject(AbstractBeanFactory.java:291)
    at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.
    getSingleton(DefaultSingletonBeanRegistry.java:222)
    at org.springframework.beans.factory.support.AbstractBeanFactory.
    doGetBean(AbstractBeanFactory.java:288)
    at org.springframework.beans.factory.support.AbstractBeanFactory.
    getBean(AbstractBeanFactory.java:194)
  • The localhost.log file (located in C:\Program Files\VMware\Infrastructure\SSOServer\logs\) contains entries similar to:

    Caused by: org.jgroups.ChannelException: unable to setup the protocol stack
    at org.jgroups.JChannel.init(JChannel.java:1728)
    at org.jgroups.JChannel.<init>(JChannel.java:249)
    at com.rsa.ims.cache.clustersupport.jgroups.JGroupsConfigFactoryBean.
    updateConfig(JGroupsConfigFactoryBean.java:149)
    at com.rsa.ims.cache.clustersupport.jgroups.JGroupsConfigFactoryBean.
    afterPropertiesSet(JGroupsConfigFactoryBean.java:120)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.
    invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1469)
    at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.
    initializeBean(AbstractAutowireCapableBeanFactory.java:1409)
    ... 159 more
    Caused by: java.lang.Exception: Property assignment of initial_hosts in TCPPING with original property value <MACHINE_NAME>[23456] and converted to null could not be assigned
    at org.jgroups.stack.Configurator.resolveAndAssignField(Configurator.java:1152)
    at org.jgroups.stack.Configurator.createLayer(Configurator.java:444)
    at org.jgroups.stack.Configurator.createProtocols(Configurator.java:393)
    at org.jgroups.stack.Configurator.setupProtocolStack(Configurator.java:88)
    at org.jgroups.stack.Configurator.setupProtocolStack(Configurator.java:55)
    at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:534)
    at org.jgroups.JChannel.init(JChannel.java:1725)
    ... 164 more
    Caused by: java.lang.Exception: Conversion of initial_hosts in TCPPING with original property value <MACHINE_NAME>[23456] failed
    at org.jgroups.conf.PropertyHelper.getConvertedValue(PropertyHelper.java:85)
    at org.jgroups.stack.Configurator.resolveAndAssignField(Configurator.java:1146)
    ... 170 more
    Caused by: java.net.UnknownHostException: <MACHINE_NAME>
    at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
    at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:849)
    at java.net.InetAddress.getAddressFromNameService(InetAddress.java:1202)
    at java.net.InetAddress.getAllByName0(InetAddress.java:1153)
    at java.net.InetAddress.getAllByName(InetAddress.java:1083)
    at java.net.InetAddress.getAllByName(InetAddress.java:1019)
    at java.net.InetAddress.getByName(InetAddress.java:969)
    at org.jgroups.stack.IpAddress.<init>(IpAddress.java:54)
    at org.jgroups.util.Util.parseCommaDelimitedHosts(Util.java:2678)
    at org.jgroups.conf.PropertyConverters$InitialHosts.convert(PropertyConverters.java:63)
    at org.jgroups.conf.PropertyHelper.getConvertedValue(PropertyHelper.java:82)
    ... 171 more


Environment

VMware vCenter Server 5.1.x

Cause

This issue occurs because the MACHINE_NAME is not resolvable to an IP address.

To determine if your MACHINE_NAME is resolvable, use nslookup from your Windows command line:
  • An example of a successful MACHINE_NAME lookup:

    C:\>nslookup myserver
    Server: dns1.mydomain.net <- FQDN of DNS Server that the A record resides

    Address: 10.10.10.20 <- IP Address of DNS Server
Name: myserver <- Machine Name
Address: 10.10.10.30 <- Machine IP Address
  • An example of an unsuccessful MACHINE_NAME lookup:

    C:\>nslookup myserver
Server: dns1.mydomain.net
Address: 10.10.10.20

*** dns1.mydomain.net can't find myserver: Non-existent domain

Resolution

To resolve this issue, add an Address record and Reverse lookup entry in the DNS server for your MACHINE_NAME.
To locate the MACHINE_NAME, open a Windows command prompt and run the command:

hostname

The output provides the MACHINE_NAME.

To add an Address record and Reverse lookup:

  1. Open DNS.
  2. In the console tree, right-click the domain you want to update and click Other New Records.
  3. In Select a resource record type, select the type of resource record you want to add.
  4. Click Create Record.
  5. In New Resource Record, work through the prompts to add the required information for the Address record and Reverse lookup.
  6. Click OK to add the new record to the zone.

For more information on DNS records, see Managing DNS Records from Microsoft Technet.


Additional Information

For related information, see the Microsoft Technet articles Setting Up DNS and Verifying Your Basic DNS Configuration.

 

Powered by Wolken Software