10:33 a.m.
[
https://issues.jboss.org/browse/AS7-4580?page=com.atlassian.jira.plugin.s...
]
James Scollard commented on AS7-4580:
-------------------------------------
According to this documentation the multicast address range and configuration is correct:
http://hornetq.sourceforge.net/docs/hornetq-2.0.0.GA/user-manual/en/html/...
Also, the multicast service and cluster communications are working on this address space
without issues. The Hornetq service is detecting the IPV4 address type correctly as well.
Since everything but the dicovery service is working and the docs state that everything
shares the same address and port number to communicate, I have to make the assumption that
there is somethign wrong with the discovery service and its configuration. If it were an
OS/VM level issue the other 2 services would not work correctly on the same port and
address settings.
I attempted to set all nodes to use a separate multicast address for discovery and
received an error on startup that my configuration was incorrect so I have to be close.
Not sure what else to look at. (hornetq noob)
Hornetq 2.2.14 Discovery Binding Failing
----------------------------------------
Key: AS7-4580
URL: https://issues.jboss.org/browse/AS7-4580
Project: Application Server 7
Issue Type: Clarification
Components: Clustering, JMS
Affects Versions: 7.1.0.Final
Environment: RHEL 6, jdk 1.6.0_32, hornetq 2.2.14
Reporter: James Scollard
Assignee: Jeff Mesnil
Priority: Minor
Labels: hornetq_jboss_configuration
We have downloaded the new (published yesterday) hornetq 2.2.14 from
https://repository.jboss.org/nexus/content/repositories/releases/org/horn...
and added our config from 2.2.5 which ran without issues. Only submitting this since this
was released yesterday. We are trying to upgrade from 2.2.5 due to the bug that affects
our topic/subscriber configuration preventing clustering. Also the Maven 2.2.14 client
does not seem to be available anywhere in the jboss maven repo.
JBoss's maven repository:
https://repository.jboss.org/nexus/content/repositories/releases/org/horn...
Only 2.2.13 and 2.2.15 are available.
Hornetq 2.2.14 Cluster Settings:
/config/stand-alone/clustered/hornetq-configuration.xml
<broadcast-groups>
<broadcast-group name="Corp-UAT">
<group-address>225.3.2.3</group-address>
<group-port>7777</group-port>
<broadcast-period>5000</broadcast-period>
<connector-ref>netty</connector-ref>
</broadcast-group>
</broadcast-groups>
<discovery-groups>
<discovery-group name="Discovery">
<group-address>225.3.2.3</group-address>
<group-port>7777</group-port>
<refresh-timeout>10000</refresh-timeout>
</discovery-group>
</discovery-groups>
<cluster-connections>
<cluster-connection name="UAT-Cluster">
<address>jms</address>
<connector-ref>netty</connector-ref>
<discovery-group-ref discovery-group-name="Discovery"/>
</cluster-connection>
</cluster-connections>
Error on Startup:
* [main] 20-Apr 13:7:23,775 WARNING [DiscoveryGroupImpl] Could not bind to 225.3.2.3
(IPv4 address); make sure your discovery group-address is of the same type as the IP stack
(IPv4 or IPv6).
Ignoring discovery group-address, but this may lead to cross talking.
java.net.BindException: Cannot assign requested address
at java.net.PlainDatagramSocketImpl.bind0(Native Method)
at java.net.PlainDatagramSocketImpl.bind(PlainDatagramSocketImpl.java:91)
at java.net.DatagramSocket.bind(DatagramSocket.java:372)
at java.net.MulticastSocket.<init>(MulticastSocket.java:147)
at
org.hornetq.core.cluster.impl.DiscoveryGroupImpl.start(DiscoveryGroupImpl.java:129)
at
org.hornetq.core.client.impl.ServerLocatorImpl.initialise(ServerLocatorImpl.java:370)
at
org.hornetq.core.client.impl.ServerLocatorImpl.start(ServerLocatorImpl.java:544)
at
org.hornetq.core.server.cluster.impl.ClusterConnectionImpl.activate(ClusterConnectionImpl.java:707)
at
org.hornetq.core.server.cluster.impl.ClusterConnectionImpl.start(ClusterConnectionImpl.java:385)
at
org.hornetq.core.server.cluster.impl.ClusterManagerImpl.start(ClusterManagerImpl.java:205)
at
org.hornetq.core.server.impl.HornetQServerImpl.initialisePart2(HornetQServerImpl.java:1493)
at
org.hornetq.core.server.impl.HornetQServerImpl.access$1200(HornetQServerImpl.java:138)
at
org.hornetq.core.server.impl.HornetQServerImpl$SharedStoreLiveActivation.run(HornetQServerImpl.java:1919)
at
org.hornetq.core.server.impl.HornetQServerImpl.start(HornetQServerImpl.java:366)
at
org.hornetq.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:269)
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.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)
at
org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)
at
org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
at
org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:241)
at
org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47)
at
org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:109)
at
org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:70)
at
org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221)
at
org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54)
at
org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42)
at
org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
at
org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
at
org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:774)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540)
at
org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean(AbstractKernelDeployer.java:319)
at
org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDeployer.java:297)
at
org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer.java:130)
at
org.jboss.kernel.plugins.deployment.xml.BeanXMLDeployer.deploy(BeanXMLDeployer.java:96)
at
org.hornetq.integration.bootstrap.HornetQBootstrapServer.deploy(HornetQBootstrapServer.java:236)
at
org.hornetq.integration.bootstrap.HornetQBootstrapServer.deploy(HornetQBootstrapServer.java:206)
at
org.hornetq.integration.bootstrap.HornetQBootstrapServer.bootstrap(HornetQBootstrapServer.java:155)
at
org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:83)
at
org.hornetq.integration.bootstrap.HornetQBootstrapServer.run(HornetQBootstrapServer.java:116)
at
org.hornetq.integration.bootstrap.HornetQBootstrapServer.main(HornetQBootstrapServer.java:73)
* [main] 20-Apr 13:7:23,820 INFO [NettyAcceptor] Started Netty Acceptor version
3.2.5.Final-a96d88c 10.60.2.38:7777 for CORE protocol
* [main] 20-Apr 13:7:23,821 INFO [HornetQServerImpl] Server is now live
* [main] 20-Apr 13:7:23,821 INFO [HornetQServerImpl] HornetQ Server version 2.2.14.Final
(HQ_2_2_14_FINAL, 122) [4aab31e6-8b0b-11e1-b160-4db571fc46b1]) started
Then once the second server is started with the same settings:
* [Thread-4
(HornetQ-server-HornetQServerImpl::serverUUID=4aab31e6-8b0b-11e1-b160-4db571fc46b1-1332226643)]
20-Apr 13:14:10,689 INFO [BridgeImpl] Bridge ClusterConnectionBridge@4e842e74
[name=sf.UAT-Cluster.3ba6a1f7-8b0c-11e1-a397-b19663cedaac,
queue=QueueImpl[name=sf.UAT-Cluster.3ba6a1f7-8b0c-11e1-a397-b19663cedaac,
postOffice=PostOfficeImpl
[server=HornetQServerImpl::serverUUID=4aab31e6-8b0b-11e1-b160-4db571fc46b1]]@4805e9f1
targetConnector=ServerLocatorImpl
(identity=(Cluster-connection-bridge::ClusterConnectionBridge@4e842e74
[name=sf.UAT-Cluster.3ba6a1f7-8b0c-11e1-a397-b19663cedaac,
queue=QueueImpl[name=sf.UAT-Cluster.3ba6a1f7-8b0c-11e1-a397-b19663cedaac,
postOffice=PostOfficeImpl
[server=HornetQServerImpl::serverUUID=4aab31e6-8b0b-11e1-b160-4db571fc46b1]]@4805e9f1
targetConnector=ServerLocatorImpl
[initialConnectors=[org-hornetq-core-remoting-impl-netty-NettyConnectorFactory?port=7777&host=10-60-2-39],
discoveryGroupConfiguration=null]]::ClusterConnectionImpl@1224217602[nodeUUID=4aab31e6-8b0b-11e1-b160-4db571fc46b1,
connector=org-hornetq-core-remoting-impl-netty-NettyConnectorFactory?port=7777&host=10-60-2-38,
address=jms, server=HornetQServerImpl::serverUUID=4aab31e6-8b0b-11e1-b160-4db571fc46b1]))
[initialConnectors=[org-hornetq-core-remoting-impl-netty-NettyConnectorFactory?port=7777&host=10-60-2-39],
discoveryGroupConfiguration=null]] is connected
Is there a setting that I may have excluded when adding my configuration to the newer
container? I just copied over the configs that came with the archive but when I look at
the configs that were included in the new version they are the same as the defaults from
2.2.5.
Apologies. We are new to adopting this product so it is very likely that we have missed
something.
Thanks in advance
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira