Version 4
Created by rhusar on Mar 1, 2012 11:00 AM. Last modified by ochaloup on Jun 1, 2012 3:28 AM.

    IPv6 is here!

    If you dare to try out IPv6 with AS7 we will be very happy to get some feedback. Here are some steps to get started.

     

    If you haven't got a chance to get to know IPv6 yet, here are some links from Pavel to get started:

     

    Setup your machine

    Make sure you have IPv6 enabled on your system.

     

    First take a look at your current inet6 addresses:

     

    [rhusar@rhusar jboss-as-7.1.1.Final-SNAPSHOT]$ ifconfig 
eth0      Link encap:Ethernet  HWaddr 00:22:68:0B:F2:2C  
          inet addr:10.34.3.13  Bcast:10.34.3.255  Mask:255.255.255.0
          inet6 addr: fe80::222:68ff:fe0b:f22c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5328647 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1673112 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:7449607775 (6.9 GiB)  TX bytes:141999867 (135.4 MiB)
          Interrupt:20 Memory:fc000000-fc020000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:363739 errors:0 dropped:0 overruns:0 frame:0
          TX packets:363739 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:48071934 (45.8 MiB)  TX bytes:48071934 (45.8 MiB)

     

    I dont have any global one so lets add them.

     

    Lets add some Global-scoped IPv6 addresses to bind the AS7 to using ip utility:

     

    Make sure that the addresses are unique within your network.

     

    [rhusar@rhusar jboss-as-7.1.1.Final-SNAPSHOT]$ sudo ip addr add 1:0:0:1::11 dev eth0
[rhusar@rhusar jboss-as-7.1.1.Final-SNAPSHOT]$ sudo ip addr add 1:0:0:1::12 dev eth0

     

    Check you added them right:

     

    [rhusar@rhusar jboss-as-7.1.1.Final-SNAPSHOT]$ ifconfig | grep inet6
          inet6 addr: 1:0:0:1::11/128 Scope:Global
          inet6 addr: 1:0:0:1::10/128 Scope:Global
          inet6 addr: fe80::222:68ff:fe0b:f22c/64 Scope:Link

     

    Now are are all set to start the AS.

     

    Note: If you want to instead bind to localhost sort-of-thing in IPv6, i.e. ::1, there is a common issue on linux that multicast does not work for this address. To workaround run:

    sudo route -A inet6 add FF01::1 dev lo

     

    Note: It's good to check what is settings of your firewall. In case that you don't want to care of it you can stop it:

    sudo service ip6tables stop

    Start the AS7

     

    Download or build your own AS7 distribution and unzip it.

     

    Before starting lets add some distributable application to see if clustering is working fine. You can use simple ClusterBench, build from here https://github.com/rhusar/clusterbench.

     

    When startin the AS7 we will have to:

    • start the HA profile
    • bind to the added address
    • not prefer ipv4 stack
    • prefer IPv6 addresses
    • use IPv6 multicast address
    • add different node names if running on the same machine

     

    That all translated into command line becomes:

     

    ./bin/standalone.sh -c standalone-ha.xml -Djboss.bind.address=1:0:0:1::11 -Djboss.bind.address.management=1:0:0:1::11 \
-Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true -Djboss.default.multicast.address=ff01::1 -Djboss.node.name=rhusar1

     

    for the second server

     

    ./bin/standalone.sh -c standalone-ha.xml -Djboss.bind.address=1:0:0:1::12 -Djboss.bind.address.management=1:0:0:1::12 \
-Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true -Djboss.default.multicast.address=ff01::1 -Djboss.node.name=rhusar2

     

    (note that jboss.bind.address.management insecurely exposed your console so use just for debugging)

     

    (if you dont want to broadcast outside your machine use -Djboss.default.multicast.address=ff02::1 instead)

     

    Starting the servers you should see something like (2nd node). Interesting parts are highlited in bold.

     

    =========================================================================

     

     

      JBoss Bootstrap Environment

     

      JBOSS_HOME: /home/rhusar/as/jboss-as-7.1.1.Final-SNAPSHOT2/jboss-as-7.1.1.Final-SNAPSHOT

     

      JAVA: /home/rhusar/tools/jdk1.6.0/bin/java

     

      JAVA_OPTS:  -server -XX:+UseCompressedOops -XX:+TieredCompilation -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml

     

    =========================================================================

     

    17:39:24,172 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA

    17:39:24,417 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA

    17:39:24,506 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final-SNAPSHOT "Thunder" starting

    17:39:25,670 INFO  [org.xnio] XNIO Version 3.0.3.GA

    17:39:25,680 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA

    17:39:25,696 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)

    17:39:25,711 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.2.GA

    17:39:25,775 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers

    17:39:25,780 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 28) JBAS016200: Activating ConfigAdmin Subsystem

    17:39:25,799 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 33) JBAS010280: Activating Infinispan subsystem.

    17:39:25,852 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 48) JBAS013101: Activating Security Subsystem

    17:39:25,858 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 43) JBAS011940: Activating OSGi Subsystem

    17:39:25,858 INFO  [org.jboss.as.security] (MSC service thread 1-2) JBAS013100: Current PicketBox version=4.0.6.final

    17:39:25,865 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 42) JBAS011800: Activating Naming Subsystem

    17:39:25,862 INFO  [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 37) JBAS010260: Activating JGroups subsystem.

    17:39:25,905 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 52) JBAS015537: Activating WebServices Extension

    17:39:25,949 INFO  [org.jboss.as.connector] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.7.Final)

    17:39:26,041 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 29) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

    17:39:26,076 INFO  [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service

    17:39:26,088 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-1) JBAS015400: Bound mail session [java:jboss/mail/Default]

    17:39:26,180 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-4) JBoss Web Services - Stack CXF Server 4.0.1.GA

    17:39:26,270 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http--1%3A0%3A0%3A1%3A0%3A0%3A0%3A12%252-8080

    17:39:26,277 INFO  [org.jboss.as.modcluster] (MSC service thread 1-4) JBAS011704: Mod_cluster uses default load balancer provider

    17:39:26,337 INFO  [org.jboss.modcluster.ModClusterService] (MSC service thread 1-4) Initializing mod_cluster 1.2.0.Final

    17:39:26,389 INFO  [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (MSC service thread 1-4) Listening to proxy advertisements on 224.0.1.105:23364

    17:39:26,466 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 33) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

    17:39:26,506 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 33) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

    17:39:26,620 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /1:0:0:1:0:0:0:12%2:9999

    17:39:26,623 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /1:0:0:1:0:0:0:12%2:4447

    17:39:26,655 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /home/rhusar/as/jboss-as-7.1.1.Final-SNAPSHOT2/jboss-as-7.1.1.Final-SNAPSHOT/standalone/deployments

    17:39:26,664 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

    17:39:26,736 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "clusterbench-ee6.ear"

    17:39:26,861 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "clusterbench-ee6-ejb.jar"

    17:39:26,862 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "clusterbench-ee6-web.war"

    17:39:26,989 INFO  [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002: Processing weld deployment clusterbench-ee6.ear

    17:39:27,091 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment clusterbench-ee6-ejb.jar

    17:39:27,093 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named RemoteSingletonSBImpl in deployment unit subdeployment "clusterbench-ee6-ejb.jar" of deployment "clusterbench-ee6.ear" are as follows:

     

        java:global/clusterbench-ee6/clusterbench-ee6-ejb/RemoteSingletonSBImpl!org.jboss.test.clusterbench.ejb.singleton.RemoteSingletonSBImpl

        java:app/clusterbench-ee6-ejb/RemoteSingletonSBImpl!org.jboss.test.clusterbench.ejb.singleton.RemoteSingletonSBImpl

        java:module/RemoteSingletonSBImpl!org.jboss.test.clusterbench.ejb.singleton.RemoteSingletonSBImpl

        java:global/clusterbench-ee6/clusterbench-ee6-ejb/RemoteSingletonSBImpl!org.jboss.test.clusterbench.ejb.singleton.RemoteSingletonSB

        java:app/clusterbench-ee6-ejb/RemoteSingletonSBImpl!org.jboss.test.clusterbench.ejb.singleton.RemoteSingletonSB

        java:module/RemoteSingletonSBImpl!org.jboss.test.clusterbench.ejb.singleton.RemoteSingletonSB

        java:jboss/exported/clusterbench-ee6/clusterbench-ee6-ejb/RemoteSingletonSBImpl!org.jboss.test.clusterbench.ejb.singleton.RemoteSingletonSB

     

    17:39:27,100 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named RemoteStatefulSBImpl in deployment unit subdeployment "clusterbench-ee6-ejb.jar" of deployment "clusterbench-ee6.ear" are as follows:

     

        java:global/clusterbench-ee6/clusterbench-ee6-ejb/RemoteStatefulSBImpl!org.jboss.test.clusterbench.ejb.stateful.RemoteStatefulSB

        java:app/clusterbench-ee6-ejb/RemoteStatefulSBImpl!org.jboss.test.clusterbench.ejb.stateful.RemoteStatefulSB

        java:module/RemoteStatefulSBImpl!org.jboss.test.clusterbench.ejb.stateful.RemoteStatefulSB

        java:jboss/exported/clusterbench-ee6/clusterbench-ee6-ejb/RemoteStatefulSBImpl!org.jboss.test.clusterbench.ejb.stateful.RemoteStatefulSB

        java:global/clusterbench-ee6/clusterbench-ee6-ejb/RemoteStatefulSBImpl

        java:app/clusterbench-ee6-ejb/RemoteStatefulSBImpl

        java:module/RemoteStatefulSBImpl

     

    17:39:27,101 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment clusterbench-ee6-web.war

    17:39:27,107 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named LocalStatefulSB in deployment unit subdeployment "clusterbench-ee6-ejb.jar" of deployment "clusterbench-ee6.ear" are as follows:

     

        java:global/clusterbench-ee6/clusterbench-ee6-ejb/LocalStatefulSB!org.jboss.test.clusterbench.ejb.stateful.LocalStatefulSB

        java:app/clusterbench-ee6-ejb/LocalStatefulSB!org.jboss.test.clusterbench.ejb.stateful.LocalStatefulSB

        java:module/LocalStatefulSB!org.jboss.test.clusterbench.ejb.stateful.LocalStatefulSB

        java:global/clusterbench-ee6/clusterbench-ee6-ejb/LocalStatefulSB

        java:app/clusterbench-ee6-ejb/LocalStatefulSB

        java:module/LocalStatefulSB

     

    17:39:27,109 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-1) JNDI bindings for session bean named LocalSingletonSB in deployment unit subdeployment "clusterbench-ee6-ejb.jar" of deployment "clusterbench-ee6.ear" are as follows:

     

        java:global/clusterbench-ee6/clusterbench-ee6-ejb/LocalSingletonSB!org.jboss.test.clusterbench.ejb.singleton.LocalSingletonSB

        java:app/clusterbench-ee6-ejb/LocalSingletonSB!org.jboss.test.clusterbench.ejb.singleton.LocalSingletonSB

        java:module/LocalSingletonSB!org.jboss.test.clusterbench.ejb.singleton.LocalSingletonSB

        java:global/clusterbench-ee6/clusterbench-ee6-ejb/LocalSingletonSB

        java:app/clusterbench-ee6-ejb/LocalSingletonSB

        java:module/LocalSingletonSB

     

    17:39:27,119 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016005: Starting Services for CDI deployment: clusterbench-ee6.ear

    17:39:27,188 INFO  [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900 1.1.5 (AS71)

    17:39:27,274 INFO  [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016008: Starting weld service for deployment clusterbench-ee6.ear

    17:39:27,740 INFO  [stdout] (pool-14-thread-1)

    17:39:27,741 INFO  [stdout] (pool-14-thread-1) -------------------------------------------------------------------

    17:39:27,741 INFO  [stdout] (pool-14-thread-1) GMS: address=rhusar2/web, cluster=web, physical address=1:0:0:1:0:0:0:12:55200

    17:39:27,741 INFO  [stdout] (pool-14-thread-1) -------------------------------------------------------------------

    17:39:27,758 INFO  [stdout] (pool-19-thread-1)

    17:39:27,762 INFO  [stdout] (pool-19-thread-1) -------------------------------------------------------------------

    17:39:27,762 INFO  [stdout] (pool-19-thread-1) GMS: address=rhusar2/ejb, cluster=ejb, physical address=1:0:0:1:0:0:0:12:55200

    17:39:27,763 INFO  [stdout] (pool-19-thread-1) -------------------------------------------------------------------

    17:39:27,931 INFO  [org.jboss.as.clustering.impl.CoreGroupCommunicationService.web] (MSC service thread 1-1) JBAS010206: Number of cluster members: 2

    17:39:27,946 INFO  [org.jboss.as.clustering.impl.CoreGroupCommunicationService.ejb] (MSC service thread 1-3) JBAS010206: Number of cluster members: 2

    17:39:28,214 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

    17:39:28,218 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-1) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

    17:39:28,246 INFO  [org.infinispan.config.ConfigurationValidatingVisitor] (pool-15-thread-1) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

    17:39:28,377 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-15-thread-1) ISPN000078: Starting JGroups Channel

    17:39:28,379 WARNING [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (pool-15-thread-1) Channel Muxer already has a default up handler installed (org.jboss.as.clustering.jgroups.ClassLoaderAwareUpHandler@2c642c2e) but now it is being overridden

    17:39:28,378 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-21-thread-1) ISPN000078: Starting JGroups Channel

    17:39:28,380 WARNING [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (pool-21-thread-1) Channel Muxer already has a default up handler installed (org.jboss.as.clustering.jgroups.ClassLoaderAwareUpHandler@649096c6) but now it is being overridden

    17:39:28,381 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-21-thread-1) ISPN000094: Received new cluster view: [rhusar1/ejb|1] [rhusar1/ejb, rhusar2/ejb]

    17:39:28,382 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-15-thread-1) ISPN000094: Received new cluster view: [rhusar1/web|1] [rhusar1/web, rhusar2/web]

    17:39:28,384 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-15-thread-1) ISPN000079: Cache local address is rhusar2/web, physical addresses are [1:0:0:1:0:0:0:12:55200]

    17:39:28,383 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-21-thread-1) ISPN000079: Cache local address is rhusar2/ejb, physical addresses are [1:0:0:1:0:0:0:12:55200]

    17:39:28,393 INFO  [org.infinispan.factories.GlobalComponentRegistry] (pool-21-thread-1) ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.1.FINAL

    17:39:28,426 INFO  [org.infinispan.jmx.CacheJmxRegistration] (pool-21-thread-1) ISPN000031: MBeans were successfully registered to the platform mbean server.

    17:39:28,445 INFO  [org.infinispan.jmx.CacheJmxRegistration] (pool-20-thread-1) ISPN000031: MBeans were successfully registered to the platform mbean server.

    17:39:28,446 INFO  [org.infinispan.jmx.CacheJmxRegistration] (pool-15-thread-1) ISPN000031: MBeans were successfully registered to the platform mbean server.

    17:39:28,575 INFO  [org.jboss.as.clustering.infinispan] (pool-15-thread-1) JBAS010281: Started repl cache from web container

    17:39:28,576 INFO  [org.jboss.as.clustering.infinispan] (pool-20-thread-1) JBAS010281: Started repl cache from ejb container

    17:39:28,596 INFO  [org.jboss.as.clustering.infinispan] (pool-21-thread-1) JBAS010281: Started remote-connector-client-mappings cache from ejb container

    17:39:28,649 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

    17:39:28,660 INFO  [org.infinispan.config.ConfigurationValidatingVisitor] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

    17:39:28,681 INFO  [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-2) ISPN000031: MBeans were successfully registered to the platform mbean server.

    17:39:28,709 INFO  [org.jboss.as.clustering.infinispan] (MSC service thread 1-2) JBAS010281: Started //default-host//clusterbench cache from web container

    17:39:28,723 INFO  [org.jboss.ejb.client.ClusterContext] (ejb-client-cluster-node-connection-creation-3-thread-1) Added a new EJB receiver in cluster context ejb for node rhusar2. Total nodes in cluster context = 1

    17:39:28,729 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

    17:39:28,735 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.

    17:39:28,742 INFO  [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-1) ISPN000031: MBeans were successfully registered to the platform mbean server.

    17:39:28,750 INFO  [org.infinispan.jmx.CacheJmxRegistration] (MSC service thread 1-4) ISPN000031: MBeans were successfully registered to the platform mbean server.

    17:39:28,784 INFO  [org.jboss.as.clustering.infinispan] (MSC service thread 1-1) JBAS010281: Started org.jboss.test.clusterbench.ejb.stateful.RemoteStatefulSBImpl cache from ejb container

    17:39:28,788 INFO  [org.jboss.as.clustering.infinispan] (MSC service thread 1-4) JBAS010281: Started org.jboss.test.clusterbench.ejb.stateful.LocalStatefulSB cache from ejb container

    17:39:28,894 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-2) Initializing Mojarra 2.1.5 (SNAPSHOT 20111202) for context '/clusterbench'

    17:39:29,553 INFO  [org.hibernate.validator.util.Version] (MSC service thread 1-2) Hibernate Validator 4.2.0.Final

    17:39:29,730 INFO  [org.jboss.web] (MSC service thread 1-2) JBAS018210: Registering web context: /clusterbench

    17:39:29,734 INFO  [org.jboss.as] (MSC service thread 1-4) JBAS015874: JBoss AS 7.1.1.Final-SNAPSHOT "Thunder" started in 5796ms - Started 324 of 452 services (127 services are passive or on-demand)

    17:39:29,791 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "clusterbench-ee6.ear"

     

     

    Hooray! You have a cluster running over IPv6!

     

    Do some testing

     

    You can now open the welcome page in your browser.

     

    Watch out that URLs with IPv6 enclose the actual address in [ these ] in order not to mess up with the port deliminer.

     

    http://[1:0:0:1:0:0:0:11]:8080/

     

    Unfortunately most popular tools for playing around with sessions just dont work well (curl, wget, opera, ...) so I will update the doc with more info when I get to it.