5 Replies Latest reply on Jan 23, 2008 9:30 AM by erasmo2 marciano2

    problem with Jboss cluster- JNDI help

    Ramesh kesavanarayanan Newbie

      We have an application running on 2 JBoss nodes running on the same machine.



      I have Apache mod_jk sitting in front of the application servers.



      I have enabled BuddyReplication and session replication(web.xml has the tag )

      jboss-4.2.2.GA\server\node1\deploy\jboss-web-cluster.sar\META-INF\ jboss-service.xml
      SERIALIZABLE



      jboss-4.2.2.GA\server\node1\deploy\jboss-web-cluster.sar\META-INF\ jboss-service.xml




      true

      org.jboss.cache.buddyreplication.NextMemberBuddyLocator



      numBuddies = 1

      ignoreColocatedBuddies = true





      default

      2000



      false

      true

      true









      All of a sudden I have lots of DEBUG messages in the log files

      “DEBUG [org.jboss.web.tomcat.service.session.JBossCacheManager] - Looking for sessions that have expired ...�

      DEBUG [org.jboss.web.tomcat.service.session.JvmRouteValve] - checkJvmRoute(): check if need to re-route based on JvmRoute. Session id: yGDtf+7isob8Q5alzt5hMg**.node1 jvmRoute: node1



      How do I prevent this??

        • 1. Re: problem with Jboss cluster- JNDI help
          Ramesh kesavanarayanan Newbie

           

          "kesavramesh" wrote:
          We have an application running on 2 JBoss nodes running on the same machine (RMI ports 1199, 1299) I checked up the same in the JMX-CONSOLE too.

          I have Apache mod_jk sitting in front of the application servers.

          I have enabled BuddyReplication and session replication(web.xml has the tag <distributable/>)

          jboss-4.2.2.GA\server\node1\deploy\jboss-web-cluster.sar\META-INF\ jboss-service.xml
          <attribute name="IsolationLevel">SERIALIZABLE</attribute>

          jboss-4.2.2.GA\server\node1\deploy\jboss-web-cluster.sar\META-INF\ jboss-service.xml
          <attribute name="BuddyReplicationConfig">
          <config>
          <buddyReplicationEnabled>true</buddyReplicationEnabled>
          <buddyLocatorClass>org.jboss.cache.buddyreplication.NextMemberBuddyLocator</buddyLocatorClass>
          <buddyLocatorProperties>
          numBuddies = 1
          ignoreColocatedBuddies = true
          </buddyLocatorProperties>
          <buddyPoolName>default</buddyPoolName>
          <buddyCommunicationTimeout>2000</buddyCommunicationTimeout>
          <autoDataGravitation>false</autoDataGravitation>
          <dataGravitationRemoveOnFind>true</dataGravitationRemoveOnFind>
          <dataGravitationSearchBackupTrees>true</dataGravitationSearchBackupTrees>
          </config>
          </attribute>



          All of a sudden I have lots of DEBUG messages in the log files
          œDEBUG [org.jboss.web.tomcat.service.session.JBossCacheManager] - Looking for sessions that have expired ...

          DEBUG [org.jboss.web.tomcat.service.session.JvmRouteValve] - checkJvmRoute(): check if need to re-route based on JvmRoute. Session id: yGDtf+7isob8Q5alzt5hMg**.node1 jvmRoute: node1

          How do I prevent this??

          Also when I use the cluster jnp address as “jnp://ipaddress:1199,jnp:ipaddress:1299â€Â�, it throws ServiceLocator exception.
          "kesavramesh" wrote:


          • 2. Re: problem with Jboss cluster- JNDI help
            Brian Stansberry Master

            Turn off DEBUG logging in conf/jboss-log4j.xml (conf/log4j.xml in earlier versions).

            Those are totally normal log messages.

            • 3. Re: problem with Jboss cluster- JNDI help
              Ramesh kesavanarayanan Newbie

              but what about the ServiceLocator Exception when I give the jnp address?

              • 4. Re: problem with Jboss cluster- JNDI help
                Ramesh kesavanarayanan Newbie

                Is there a difference between enabling replication of web application (web.xml) and enabling Buddy replication??

                Is it mandatory to use clustering of EJB's (3.0) using the @clustered interface??