Clustered Instance Does Not Start with java.util.NoSuchElementException (No server id found)
This article applies to Confluence clustered 5.4 or earlier.
症状
Console に次のエラーが返される。
2013-04-12 16:04:31,604 ERROR [main] [atlassian.confluence.setup.ConfluenceConfigurationListener] contextInitialized An error was encountered while bootstrapping Confluence (see below):
null
java.util.NoSuchElementException
at java.net.NetworkInterface$1checkedAddresses.nextElement(NetworkInterface.java:102)
at java.net.NetworkInterface$1checkedAddresses.nextElement(NetworkInterface.java:78)
at com.atlassian.confluence.cluster.ClusterConfig.getUnicastAddress(ClusterConfig.java:53)
at com.atlassian.confluence.cluster.coherence.TangosolClusterManager.getXmlConfig(TangosolClusterManager.java:511)
at com.atlassian.confluence.cluster.coherence.TangosolClusterManager.mergeConfig(TangosolClusterManager.java:454)
at com.atlassian.confluence.cluster.coherence.TangosolClusterManager.configure(TangosolClusterManager.java:375)
at com.atlassian.confluence.cluster.coherence.TangosolClusterManager.reconfigure(TangosolClusterManager.java:394)
at com.atlassian.confluence.cluster.DefaultClusterConfigurationHelper.bootstrapCluster(DefaultClusterConfigurationHelper.java:165)
at com.atlassian.confluence.setup.DefaultBootstrapManager.afterConfigurationLoaded(DefaultBootstrapManager.java:346)
at com.atlassian.config.bootstrap.DefaultAtlassianBootstrapManager.init(DefaultAtlassianBootstrapManager.java:70)
at com.atlassian.config.util.BootstrapUtils.init(BootstrapUtils.java:35)
at com.atlassian.confluence.setup.ConfluenceConfigurationListener.initialiseBootstrapContext(ConfluenceConfigurationListener.java:86)
at com.atlassian.confluence.setup.ConfluenceConfigurationListener.contextInitialized(ConfluenceConfigurationListener.java:48)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4205)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4704)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
at org.apache.catalina.core.StandardService.start(StandardService.java:525)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
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 org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
Attempts to access Confluence results in the following:
原因
The network interface specified in ConfluenceHomeDirectory/confluence.cfg.xml is no longer valid:
<property name="confluence.cluster.interface">net5</property>ソリューション
インターフェイス名が正しくマッピングされていることを確認するには、以下のツールを使用できます。IP アドレスへのインターフェイス名のマッピングが表示されます。
C:\>java -jar list-interfaces.jar
interfaces.size() = 4
networkInterface[0] = name:lo (MS TCP Loopback interface) index: 1 addresses:
/127.0.0.1;
networkInterface[1] = name:eth0 (VMware Virtual Ethernet Adapter for VMnet8) index: 2 addresses:
/192.168.133.1;
networkInterface[2] = name:eth1 (VMware Virtual Ethernet Adapter for VMnet1) index: 3 addresses:
/192.168.68.1;
networkInterface[3] = name:eth2 (Broadcom NetXtreme 57xx Gigabit Controller - Packet Scheduler Miniport) index: 4 addresses:
/192.168.0.101;Update the confluence.cluster.interface property in confluence.cfg.xml to the correct interface, and try to start the cluster node again
Last modified on Mar 30, 2016
Powered by Confluence and Scroll Viewport.