Tomcat cluster problem record

Source: Internet
Author: User
Tags apache tomcat

Add the cluster child element to the engine element of Server.xml, as described in the official documentation, configured as follows:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/6F/68/wKiom1WbV2PyqbrHACWaM3wGtc8648.jpg "title=" According to the official website configuration. png "alt=" wkiom1wbv2pyqbrhacwam3wgtc8648.jpg "/>


However, there are always the following errors when starting Tomcat on my Linux virtual machine:

Info: Starting Servlet engine:apache tomcat/7.0.62

July 07, 2015 10:15:38 am org.apache.catalina.ha.tcp.SimpleTcpCluster startinternal

Info: Cluster is about to start

July 07, 2015 10:15:38 am org.apache.catalina.tribes.transport.ReceiverBase bind

Info: Receiver Server Socket bound to:/127.0.0.1:4000

July 07, 2015 10:15:38 am Org.apache.catalina.tribes.membership.McastServiceImpl setupsocket

Info: Setting cluster mcast sotimeout to 500

July 07, 2015 10:15:38 am Org.apache.catalina.tribes.membership.McastServiceImpl start

Critical: Unable to join multicast group, make sure your system have multicasting enabled.

July 07, 2015 10:15:38 am org.apache.catalina.ha.tcp.SimpleTcpCluster startinternal

Critical: Unable to start cluster.

Org.apache.catalina.tribes.ChannelException:java.net.SocketException: Without that device; No faulty members identified.

At Org.apache.catalina.tribes.group.ChannelCoordinator.internalStart

(channelcoordinator.java:177)

At Org.apache.catalina.tribes.group.ChannelCoordinator.start

(channelcoordinator.java:98)

At Org.apache.catalina.tribes.group.ChannelInterceptorBase.start

(channelinterceptorbase.java:160)

At Org.apache.catalina.tribes.group.interceptors.MessageDispatchInterceptor.start

(messagedispatchinterceptor.java:157)

At Org.apache.catalina.tribes.group.ChannelInterceptorBase.start

(channelinterceptorbase.java:160)

At Org.apache.catalina.tribes.group.ChannelInterceptorBase.start

(channelinterceptorbase.java:160)

At Org.apache.catalina.tribes.group.GroupChannel.start

(groupchannel.java:419)

At org.apache.catalina.ha.tcp.SimpleTcpCluster.startInternal

(simpletcpcluster.java:690)

At Org.apache.catalina.util.LifecycleBase.start (lifecyclebase.java:150)

At Org.apache.catalina.core.ContainerBase.startInternal (containerbase.java:1106)

At Org.apache.catalina.core.StandardEngine.startInternal (standardengine.java:300)

At Org.apache.catalina.util.LifecycleBase.start (lifecyclebase.java:150)

At Org.apache.catalina.core.StandardService.startInternal (standardservice.java:443)

At Org.apache.catalina.util.LifecycleBase.start (lifecyclebase.java:150)

At Org.apache.catalina.core.StandardServer.startInternal (standardserver.java:739)

At Org.apache.catalina.util.LifecycleBase.start (lifecyclebase.java:150)

At Org.apache.catalina.startup.Catalina.start (catalina.java:689)

At Sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)

At Sun.reflect.NativeMethodAccessorImpl.invoke (nativemethodaccessorimpl.java:57)

At Sun.reflect.DelegatingMethodAccessorImpl.invoke (delegatingmethodaccessorimpl.java:43)

At Java.lang.reflect.Method.invoke (method.java:606)

At Org.apache.catalina.startup.Bootstrap.start (bootstrap.java:321)

At Org.apache.catalina.startup.Bootstrap.main (bootstrap.java:455)

Caused by:java.net.SocketException: not that device.

At Java.net.PlainDatagramSocketImpl.join (Native Method)

At Java.net.AbstractPlainDatagramSocketImpl.join (abstractplaindatagramsocketimpl.java:179)

At Java.net.MulticastSocket.joinGroup (multicastsocket.java:319)

At Org.apache.catalina.tribes.membership.McastServiceImpl.start (mcastserviceimpl.java:253)

At Org.apache.catalina.tribes.membership.McastService.start (mcastservice.java:444)

At Org.apache.catalina.tribes.group.ChannelCoordinator.internalStart (channelcoordinator.java:162)

... More


July 07, 2015 10:15:38 am Org.apache.catalina.startup.Catalina start

Critical: The required Server component failed to start so Tomcat was unable to start.

org.apache.catalina.LifecycleException:Failed to start component [standardserver[8005]

At Org.apache.catalina.util.LifecycleBase.start (lifecyclebase.java:154)

At Org.apache.catalina.startup.Catalina.start (catalina.java:689)

At Sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)

At Sun.reflect.NativeMethodAccessorImpl.invoke (nativemethodaccessorimpl.java:57)

At Sun.reflect.DelegatingMethodAccessorImpl.invoke (delegatingmethodaccessorimpl.java:43)

At Java.lang.reflect.Method.invoke (method.java:606)

At Org.apache.catalina.startup.Bootstrap.start (bootstrap.java:321)

At Org.apache.catalina.startup.Bootstrap.main (bootstrap.java:455)

caused by:org.apache.catalina.LifecycleException:Failed to start component [Standardservice[catalina]

At Org.apache.catalina.util.LifecycleBase.start (lifecyclebase.java:154)

At Org.apache.catalina.core.StandardServer.startInternal (standardserver.java:739)

At Org.apache.catalina.util.LifecycleBase.start (lifecyclebase.java:150)

... 7 more

caused by:org.apache.catalina.LifecycleException:Failed to start component [Standardengine[catalina]

At Org.apache.catalina.util.LifecycleBase.start (lifecyclebase.java:154)

At Org.apache.catalina.core.StandardService.startInternal (standardservice.java:443)

At Org.apache.catalina.util.LifecycleBase.start (lifecyclebase.java:150)

... 9 more

caused by:org.apache.catalina.LifecycleException:Failed to start component [ Org.apache.catalina.ha.tcp.simpletcpcluster[catalina]]

At Org.apache.catalina.util.LifecycleBase.start (lifecyclebase.java:154)

At Org.apache.catalina.core.ContainerBase.startInternal (containerbase.java:1106)

At Org.apache.catalina.core.StandardEngine.startInternal (standardengine.java:300)

At Org.apache.catalina.util.LifecycleBase.start (lifecyclebase.java:150)

... One more

Caused by:org.apache.catalina.LifecycleException:org.apache.catalina.tribes.ChannelException: Java.net.SocketException: Without that device; No faulty members identified.

At Org.apache.catalina.ha.tcp.SimpleTcpCluster.startInternal (simpletcpcluster.java:695)

At Org.apache.catalina.util.LifecycleBase.start (lifecyclebase.java:150)

... More

caused by:org.apache.catalina.tribes.ChannelException:java.net.SocketException: without that device; No faulty members identified.

At Org.apache.catalina.tribes.group.ChannelCoordinator.internalStart (channelcoordinator.java:177)

At Org.apache.catalina.tribes.group.ChannelCoordinator.start (channelcoordinator.java:98)

At Org.apache.catalina.tribes.group.ChannelInterceptorBase.start (channelinterceptorbase.java:160)

At Org.apache.catalina.tribes.group.interceptors.MessageDispatchInterceptor.start ( messagedispatchinterceptor.java:157)

At Org.apache.catalina.tribes.group.ChannelInterceptorBase.start (channelinterceptorbase.java:160)

At Org.apache.catalina.tribes.group.ChannelInterceptorBase.start (channelinterceptorbase.java:160)

At Org.apache.catalina.tribes.group.GroupChannel.start (groupchannel.java:419)

At Org.apache.catalina.ha.tcp.SimpleTcpCluster.startInternal (simpletcpcluster.java:690)

... More

Caused by:java.net.SocketException: not that device.

At Java.net.PlainDatagramSocketImpl.join (Native Method)

At Java.net.AbstractPlainDatagramSocketImpl.join (abstractplaindatagramsocketimpl.java:179)

At Java.net.MulticastSocket.joinGroup (multicastsocket.java:319)

At Org.apache.catalina.tribes.membership.McastServiceImpl.start (mcastserviceimpl.java:253)

At Org.apache.catalina.tribes.membership.McastService.start (mcastservice.java:444)

At Org.apache.catalina.tribes.group.ChannelCoordinator.internalStart (channelcoordinator.java:162)

... More


July 07, 2015 10:15:38 am Org.apache.coyote.AbstractProtocol Pause

Info: Pausing protocolhandler ["http-bio-8080"]

July 07, 2015 10:15:38 am Org.apache.coyote.AbstractProtocol Pause

Info: Pausing protocolhandler ["ajp-bio-8009"]

July 07, 2015 10:15:38 am org.apache.catalina.core.StandardService stopinternal

Information: Stopping service Catalina

July 07, 2015 10:15:38 am org.apache.coyote.AbstractProtocol destroy

Info: Destroying Protocolhandler ["http-bio-8080"]

July 07, 2015 10:15:38 am org.apache.coyote.AbstractProtocol destroy

Info: Destroying Protocolhandler ["ajp-bio-8009"]



I guess it should be a multicast problem, which is essentially a problem with the network of my virtual machine, which makes it impossible to join the multicast group.

Later, in the online collection of some information, there is no good plan

Some people say that the address of receiver is changed to its own IP, do not use auto

Some say it's hostname and/etc/hosts. Inconsistent configuration

More people say it's because there's no cable.

......

I have tried, but still reported this mistake, even if I put the SELinux and the firewall is also closed.

Later, I put Tomcat on my Win7 to start the success (even if I unplug the network cable)

I think, put it under the Win7, can you put it on Linux? , I put the boot-up tomcat from the virtual machine into the company's

Linux server, it can also start success. I'm confused ...

Later, I changed the broadcast address of the NIC Eth0 on the virtual machine to 228.0.0.4

Ipconfig eth0 broadcast 228.0.0.4

Start Tomcat again, God, often started successfully, do not know why ...

In the end, I made a bold attempt

I changed the network connection of the virtual machine from "host mode only" to "bridge mode" so that the virtual machine can be networked

Start Tomcat again in the virtual machine, the result started successfully, very unexpectedly


Booting Tomcat in a virtual machine environment with a network connection mode of "host-only mode", error

Change the broadcast address of the virtual machine to 228.0.0.4, launch Tomcat, success

Put the Tomcat in the virtual machine into the Win7 environment and start the success on the real Linux server

Does not change the broadcast address of the virtual machine, changes the network connection mode to "Bridging Mode", launches Tomcat, and successfully


Just so confused, Tomcat started success, I do not know why, it seems that the virtual machine environment is still a problem ah!

Here too lazy to dig down, in short, do experiment with bridge mode bar!

In the future meet the Tall man and ask again ......



This article is from the "ten-li Rice flower" blog, please be sure to keep this source http://5880861.blog.51cto.com/5870861/1671622

Tomcat cluster problem record

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.