[jboss-jira] [JBoss JIRA] (AS7-3589) CLONE - Distributable deployment in a clustering env. in standalone mode with 2 nodes installed in different datacenter does not wokr as expected
Brian Stansberry (JIRA)
jira-events at lists.jboss.org
Thu Feb 9 10:19:48 EST 2012
[ https://issues.jboss.org/browse/AS7-3589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry reopened AS7-3589:
-----------------------------------
> CLONE - Distributable deployment in a clustering env. in standalone mode with 2 nodes installed in different datacenter does not wokr as expected
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-3589
> URL: https://issues.jboss.org/browse/AS7-3589
> Project: Application Server 7
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 7.1.0.CR1b
> Environment: RHEL 6, JBoss EAP 6 DR12
> Reporter: Serge Emmanuel Pagop
> Assignee: Paul Ferraro
> Fix For: 7.1.1.Final
>
>
> I create multiple IP Addresses on a single NIC for this use case.
> Use-Case: Clustering in Standalone mode with 2 nodes installed in different Datacenter
> Action: deployment of a distributable web application in the node 1 from datacenter 1
> Expectation: consequence should be also the deployment of the distributable application in the running node2 from datacenter 2
> Result: no deployment of application in the running node2 from datacenter2
> Info: find the web application example as attach
> All the steps:
> 1) from datacenter 1
> + Start node1 in Standalone mode from datacenter with IP 192.168.178.31
> $EAP6_HOME/bin>./standalone.sh -c=standalone-ha.xml -b=192.168.178.31 -bmanagement=192.168.178.31 -Djboss.node.name=node1
> 2)from datacenter 2
> + Start node2 in standalone mode from datacenter with IP 192.168.178.32
> $EAP6_HOME/bin>./standalone.sh -c=standalone-ha.xml -b=192.168.178.32 -bmanagement=192.168.178.32 -Djboss.node.name=node2
> 3)from datacenter 1
> + deploy a distributable application in the running standalone node1 - copy the application into the directory $EAP6_HOME/standalone/deployments
> during the deployment server log shows this infos:
> - Start Server log infos
> 22:26:28,506 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "version3.war"
> 22:26:29,285 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-1) send buffer of socket java.net.DatagramSocket at 40993028 was set to 640KB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max on Linux)
> 22:26:29,286 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-1) receive buffer of socket java.net.DatagramSocket at 40993028 was set to 20MB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)
> 22:26:29,286 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-1) send buffer of socket java.net.MulticastSocket at 928b33a was set to 640KB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max on Linux)
> 22:26:29,288 WARNING [org.jgroups.protocols.UDP] (MSC service thread 1-1) receive buffer of socket java.net.MulticastSocket at 928b33a was set to 25MB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)
> 22:26:29,303 INFO [stdout] (MSC service thread 1-1)
> 22:26:29,304 INFO [stdout] (MSC service thread 1-1) -------------------------------------------------------------------
> 22:26:29,304 INFO [stdout] (MSC service thread 1-1) GMS: address=node1/web, cluster=web, physical address=192.168.178.31:55200
> 22:26:29,304 INFO [stdout] (MSC service thread 1-1) -------------------------------------------------------------------
> 22:26:31,359 INFO [org.jboss.as.clustering.CoreGroupCommunicationService.web] (MSC service thread 1-4) JBAS010207: Number of cluster members: 1
> 22:26:31,781 WARN [org.infinispan.config.ConfigurationValidatingVisitor] (MSC service thread 1-4) ISPN000152: Passivation configured without a valid eviction policy. This could mean that the cache store will never get used unless code calls Cache.evict() manually.
> 22:26:31,971 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000078: Starting JGroups Channel
> 22:26:31,972 WARNING [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (MSC service thread 1-4) Channel Muxer already has a default up handler installed (org.jboss.as.clustering.jgroups.ClassLoaderAwareUpHandler at 6b7fb9d5) but now it is being overridden
> 22:26:31,972 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000094: Received new cluster view: [node1/web|0] [node1/web]
> 22:26:31,973 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000079: Cache local address is node1/web, physical addresses are [192.168.178.31:55200]
> 22:26:31,976 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-4) ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.0.CR1
> 22:26:32,077 INFO [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-1) ISPN000031: MBeans were successfully registered to the platform mbean server.
> 22:26:32,145 INFO [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-4) ISPN000031: MBeans were successfully registered to the platform mbean server.
> 22:26:32,193 INFO [org.jboss.as.clustering] (MSC service thread 1-1) JBAS010301: Started registry cache from web container
> 22:26:32,193 INFO [org.jboss.as.clustering] (MSC service thread 1-4) JBAS010301: Started repl cache from web container
> 22:26:32,347 INFO [org.jboss.web] (MSC service thread 1-4) registering web context: /version3
> 22:26:32,402 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "version3.war"
> - End Server log infos
> 4) From datacenter 2
> No action deployment in node2
> - Start Server log info
> ...
> 22:25:36,179 INFO [org.jboss.as.remoting] (MSC service thread 1-4) Listening on /192.168.178.32:9999
> 22:25:36,233 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /NotBackedUp/spagop/EAP6_TRAINING/my-labs/clustering/standalone-lab/node2/jboss-eap-6.0/standalone/deployments
> 22:25:36,986 INFO [org.jboss.as] (Controller Boot Thread) JBoss EAP 6.0.0.Alpha2 (AS 7.1.0.CR1-redhat-1) started in 8096ms - Started 152 of 259 services (102 services are passive or on-demand)
> - End Server log info
--
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
More information about the jboss-jira
mailing list