5 Replies Latest reply on Feb 13, 2009 12:36 AM by Elias Ross

    JBossCache  1.4.0.SP1 And WebSphere 6.0.2.31 in cluster envi

    Vikas Garg Newbie

      I need to deploy application using jboss cache version 1.4.0.SP1 in websphere 6.0.2.31 cluster environment. Websphere environment uses TCP instead of UDP and thus we need settings specifically for TCP. What would be the config file modifications for the same? What configuration I need to do on the websphere cluster environment.
      It would be great if I could get the jbosscache-config.xml for the same.

      Thanks,
      Vikas

        • 1. Re: JBossCache  1.4.0.SP1 And WebSphere 6.0.2.31 in cluster
          Manik Surtani Master

          please have a look at the samples shipped with JBC. Referring docs on JGroups.org will help as well.

          • 2. Re: JBossCache  1.4.0.SP1 And WebSphere 6.0.2.31 in cluster
            Vikas Garg Newbie

            We checked JGroups and it suggests to use bind_addr and start_port and end_port for the server using TCP as the discovery protocol. We asked for the details from websphere admin and he gave us ip addresses for both the servers present in the cluster. Which ip address we need to use in the bind_addr attribute? Or would it be fine not to specify this as JGroups doc mentions it to be useful in case of a multihomed machine. If not specified, the server socket will be created on all available interfaces.

            • 3. Re: JBossCache  1.4.0.SP1 And WebSphere 6.0.2.31 in cluster
              Manik Surtani Master

              How would I know which IP address or interface you want to bind JGroups to on your servers!

              • 4. Re: JBossCache  1.4.0.SP1 And WebSphere 6.0.2.31 in cluster
                Vikas Garg Newbie

                We are getting the following error on both the nodes in the cluster if we deploy the application by specifying TCP discovery protocol in the jbosscache-config.xml.

                Below is the server log:
                [2/12/09 11:18:13:985 PST] 00000030 PropertyConfi I org.jboss.cache.PropertyConfigurator Found existing property editor for org.w3c.dom.Element: org.jboss.util.propertyeditor.ElementEditor@4154831d
                [2/12/09 11:18:14:001 PST] 00000030 PropertyConfi I org.jboss.cache.PropertyConfigurator configure attribute size: 19
                [2/12/09 11:18:14:140 PST] 00000030 TreeCache W org.jboss.cache.TreeCache _createService No transaction manager lookup class has been defined. Transactions cannot be used
                [2/12/09 11:18:14:229 PST] 00000030 InterceptorCh I org.jboss.cache.factories.InterceptorChainFactory createPessimisticInterceptorChain interceptor chain is:
                class org.jboss.cache.interceptors.CallInterceptor
                class org.jboss.cache.aop.interceptors.PojoEvictionInterceptor
                class org.jboss.cache.interceptors.PessimisticLockInterceptor
                class org.jboss.cache.interceptors.UnlockInterceptor
                class org.jboss.cache.interceptors.ReplicationInterceptor
                class org.jboss.cache.interceptors.TxInterceptor
                class org.jboss.cache.interceptors.CacheMgmtInterceptor
                [2/12/09 11:18:14:475 PST] 00000030 UNICAST E org.jgroups.protocols.UNICAST setProperties window_size is deprecated and will be ignored
                [2/12/09 11:18:14:478 PST] 00000030 UNICAST E org.jgroups.protocols.UNICAST setProperties min_threshold is deprecated and will be ignored
                [2/12/09 11:18:14:650 PST] 00000034 ConnectionTab I org.jgroups.blocks.ConnectionTable start server socket created on 127.0.0.1:12000
                [2/12/09 11:18:14:920 PST] 00000035 SystemOut O
                -------------------------------------------------------
                GMS: address is 127.0.0.1:12000
                -------------------------------------------------------
                [2/12/09 11:18:16:965 PST] 00000030 TreeCache I org.jboss.cache.TreeCache startService TreeCache local address is 127.0.0.1:12000
                [2/12/09 11:18:16:966 PST] 00000036 TreeCache I org.jboss.cache.TreeCache viewAccepted viewAccepted(): [127.0.0.1:12000|0] [127.0.0.1:12000]
                [2/12/09 11:18:16:987 PST] 00000037 ConnectionTab I org.jgroups.blocks.ConnectionTable$Connection matchCookie input_cookie is bela
                [2/12/09 11:18:16:987 PST] 00000030 TreeCache I org.jboss.cache.TreeCache fetchStateOnStartup State could not be retrieved (we are the first member in group)
                [2/12/09 11:18:16:997 PST] 00000034 ConnectionTab I org.jgroups.blocks.ConnectionTable getConnection created socket to 127.0.0.1:12000
                [2/12/09 11:18:16:997 PST] 00000030 TreeCache I org.jboss.cache.aop.PojoCache parseConfig parseConfig(): PojoCacheConfig is empty

                jbosscache-config.xml reads as:

                <!-- Transport protocol: http://wiki.jboss.org/wiki/JGroupsUDP -->
                <!--UDP mcast_addr="239.255.133.9" mcast_port="9010"
                ip_ttl="1" ip_mcast="true" mcast_send_buf_size="150000"
                mcast_recv_buf_size="80000" ucast_send_buf_size="150000"
                ucast_recv_buf_size="80000" loopback="false" /-->
                <TCP bind_addr="" start_port="12000" end_port="12000">
                <!-- Discovery protocols: http://wiki.jboss.org/wiki/JGroupsPING -->
                <PING timeout="2000" num_initial_members="3"
                up_thread="false" down_thread="false" />

                <!-- Merging Protocols: http://wiki.jboss.org/wiki/JGroupsMERGE2 -->
                <MERGE2 min_interval="10000" max_interval="20000" />

                <!-- Failure Detection Protocols: http://wiki.jboss.org/wiki/JGroupsFD_SOCK -->
                <FD_SOCK />

                <!-- Failure Detection Protocols: http://wiki.jboss.org/wiki/JGroupsVERIFY_SUSPECT -->
                <VERIFY_SUSPECT timeout="1500" up_thread="false"
                down_thread="false" />

                <!-- Reliable Message Transmission Protocols: http://wiki.jboss.org/wiki/JGroupsPbcastNAKACK -->
                <pbcast.NAKACK gc_lag="50"
                retransmit_timeout="600,1200,2400,4800" max_xmit_size="8192"
                up_thread="false" down_thread="false" />

                <!-- Reliable Message Transmission Protocols: http://wiki.jboss.org/wiki/JGroupsUNICAST-->
                <UNICAST timeout="600,1200,2400" window_size="100"
                min_threshold="10" down_thread="false" />

                <!-- Reliable Message Transmission Protocols: http://wiki.jboss.org/wiki/JGroupsPbcastSTABLE -->
                <pbcast.STABLE desired_avg_gossip="20000"
                up_thread="false" down_thread="false" />

                <!-- Group membership protocol: http://wiki.jboss.org/wiki/JGroupsPbcastGMS -->
                <pbcast.GMS join_timeout="5000"
                join_retry_timeout="2000" shun="true" print_local_addr="true" />

                <!-- Flow control protocol: http://wiki.jboss.org/wiki/JGroupsFC
                <FC max_credits="2000000" down_thread="false" up_thread="false" min_threshold="0.20"/>-->

                <!-- Fragmentation protocol: http://wiki.jboss.org/wiki/JGroupsFRAG -->
                <FRAG frag_size="8192" down_thread="false"
                up_thread="true" />

                <!-- State tranfer protocol: http://wiki.jboss.org/wiki/JGroupsPbcastSTATE_TRANSFER -->
                <pbcast.STATE_TRANSFER up_thread="true"
                down_thread="true" />

                • 5. Re: JBossCache  1.4.0.SP1 And WebSphere 6.0.2.31 in cluster
                  Elias Ross Master

                  If you're using TCP, you need either a gossip server or to list the initial members in your configuration.

                  Think about it!