3 Replies Latest reply on Jul 3, 2014 3:58 PM by Travis Owens

    ModClusterConfig in error: Unable to determine type for value:224.0.1.105

    Travis Owens Newbie

      Hello all!

       

      I've been doing Jboss administration for a while, but am new to the clustering side of things. We are running Jboss 5.1.0 GA and have been using mod_proxy_balancer for a while; however, we are seeing an increased need for contextually aware balancer logic and dynamic load shifting (among other things.) We are running Oracle Linux 6.5, and oracle Java 1.7.0_25, and I have pulled down mod_cluster-1.2.6 and in order to just get things functional, I am using a vanilla instance of our Jboss release (no internal/custom/or extra applications) so we're stock-as-a-rock. I have deployed mod_cluster.sar in the deploy directory of the default server and have tried to start it numerous times/ways and it's failing to even start up successfully.

       

      We have an init script for jboss that will execute the following:

      java -Dprogram.name=run.sh -server -Xmx10G -Xms10G -XX:PermSize=512m -XX:MaxPermSize=512m -XX:+UseLargePages -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+ExplicitGCInvokesConcurrent -XX:+CMSScavengeBeforeRemark -Djboss.server.log.dir=/var/log/jboss -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Xloggc:/var/log/jboss/gc.2014-07-01-16-57.log -XX:+PrintGCDateStamps -XX:+PrintGCDetails -XX:+PrintTenuringDistribution -XX:+PrintGCApplicationConcurrentTime -XX:+PrintGCApplicationStoppedTime -Djava.net.preferIPv4Stack=true -Djava.endorsed.dirs=/usr/local/jboss/lib/endorsed -classpath /usr/local/sites/config/classes:/usr/local/jboss/bin/run.jar org.jboss.Main -c default -b 0.0.0.0

       

      We are seeing the error in the topic line:

      DEPLOYMENTS IN ERROR:

        Deployment "ModClusterConfig" is in error due to the following reason(s): java.lang.IllegalArgumentException: Unable to determine type for value: ${jboss.mod_cluster.advertise.address,jboss.modcluster.advertise.address,jboss.partition.udpGroup:224.0.1.105}, **ERROR**

       

      And this gives us concern considering the value it's complaining about is the configuration file's default value: ${jboss.mod_cluster.advertise.address,jboss.modcluster.advertise.address,jboss.partition.udpGroup:224.0.1.105}

       

      I have tried it with just the IP (224.0.1.105) and it still throws the same error.

       

      We have commented the parameter (advertiseGroupAddress) out entirely, hoping to just provide it on the commandline and it threw this error:

      DEPLOYMENTS IN ERROR:

        Deployment "ModClusterService" is in error due to the following reason(s): org.jboss.joinpoint.spi.JoinpointException: Constructor not found org.jboss.modcluster.ModClusterService[org.jboss.modcluster.config.ModClusterConfig, org.jboss.modcluster.load.LoadBalanceFactorProvider] in [ReflectConstructorInfoImpl@35b93cfd{[ReflectClassInfoImpl@14532199{name=org.jboss.modcluster.config.NodeConfiguration}, ReflectClassInfoImpl@5dc2ce3b{name=org.jboss.modcluster.config.BalancerConfiguration}, ReflectClassInfoImpl@2071b394{name=org.jboss.modcluster.config.MCMPHandlerConfiguration}, ReflectClassInfoImpl@8c4ca30{name=org.jboss.modcluster.load.LoadBalanceFactorProviderFactory}, ReflectClassInfoImpl@2fb619cf{name=org.jboss.modcluster.mcmp.MCMPRequestFactory}, ReflectClassInfoImpl@5c587d81{name=org.jboss.modcluster.mcmp.MCMPResponseParser}, ReflectClassInfoImpl@3597cf84{name=org.jboss.modcluster.mcmp.ResetRequestSource}, ReflectClassInfoImpl@1b8fe99{name=org.jboss.modcluster.mcmp.MCMPHandler}, ReflectClassInfoImpl@1852efb1{name=org.jboss.modcluster.advertise.AdvertiseListenerFactory}]}, ReflectConstructorInfoImpl@6cf659f0{[ReflectClassInfoImpl@218ad373{name=org.jboss.modcluster.config.impl.ModClusterConfig}, ReflectClassInfoImpl@8c4ca30{name=org.jboss.modcluster.load.LoadBalanceFactorProviderFactory}, ReflectClassInfoImpl@2fb619cf{name=org.jboss.modcluster.mcmp.MCMPRequestFactory}, ReflectClassInfoImpl@5c587d81{name=org.jboss.modcluster.mcmp.MCMPResponseParser}, ReflectClassInfoImpl@3597cf84{name=org.jboss.modcluster.mcmp.ResetRequestSource}]}, ReflectConstructorInfoImpl@21403439{[ReflectClassInfoImpl@218ad373{name=org.jboss.modcluster.config.impl.ModClusterConfig}, ReflectClassInfoImpl@8c4ca30{name=org.jboss.modcluster.load.LoadBalanceFactorProviderFactory}, ReflectClassInfoImpl@2fb619cf{name=org.jboss.modcluster.mcmp.MCMPRequestFactory}]}, ReflectConstructorInfoImpl@7e249b3c{[ReflectClassInfoImpl@218ad373{name=org.jboss.modcluster.config.impl.ModClusterConfig}, ReflectClassInfoImpl@8c4ca30{name=org.jboss.modcluster.load.LoadBalanceFactorProviderFactory}]}, ReflectConstructorInfoImpl@154bc0d7{[ReflectClassInfoImpl@218ad373{name=org.jboss.modcluster.config.impl.ModClusterConfig}, ReflectClassInfoImpl@20616e2d{name=org.jboss.modcluster.load.LoadBalanceFactorProvider}]}], **ERROR**


      According to everything I've been able to track down so far, all we should have to do is deploy the SAR, update the IP/PORT if desired and setup Apache's mod_cluster configuration to match and presto! Everything is supposed to magically work. Thus far, we can't even get a default, vanilla Jboss instance to stand up cleanly with mod_cluster.


      Has anyone run into anything like this previously? I would so love to find out it's a very simple oversight and it can be up and running with a slight tweak! Or even a huge configuration change, I don't care! I just need some directions to get it going...


      So, to all the mod_clustering gurus around, I beg for you mercy and guidance.