Hi Sacha,
Thanks for the response!
No,its the same "jboss-3.2.3RC1-jetty4.2.11.gz" distribution file downloaded
as such from sourceforge site!! Not a single file change! Also I am using
"RC1" of jboss3.2.3 and not "RC3" as you have mentioned.
Anyhow,if you think its an old one,can you please send me the new
"cluster-service.xml" which won't give this problem.
I am attaching the "cluster-service.xml" which I got from the distribution.

Thanks in advance,
Nishant.


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Sacha
Labourey
Sent: Wednesday, December 31, 2003 12:56 AM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-user] Exception in JBoss Cluster startup in
JBoss3.2.3RC1_Jetty_4.2.14


Are you using your own (old) cluster-service.xml partition definition? I
think 3.2.3RC3 already uses the new package names i.e. org.jgroups instead
of org.javagroups.

sacha

> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Nishant Aggarwal
> Sent: mercredi, 31. décembre 2003 22:06
> To: [EMAIL PROTECTED]
> Subject: [JBoss-user] Exception in JBoss Cluster startup in
> JBoss3.2.3RC1_Jetty_4.2.14
>
> Hi All,
> I have just started running JBoss3.2.3Rc1_Jetty4.2.14 in
> "all"/clustering
> mode.
> I had enabled "debug" options in "log4j.xml" for the above release.
> On running it ,I found the following exception,when starting
> the deployment
> of "cluster-service.xml",during JBoss startup.
> -------------------------------------------------------
> GMS: address is bplinux58:42181 (additional data: 18 bytes)
> -------------------------------------------------------
> 2003-12-31 00:48:55,186 DEBUG
> [org.javagroups.DefaultPartition] [Wed Dec 31
> 00:48:55 IST 2003] [ERROR] UDP.handleIncomingUdpPacket():
> exception=java.io.IOException: java.lang.ClassNotFoundException: No
> ClassLoaders found for: org.javagroups.protocols.PingRsp
>         at org.jgroups.util.Marshaller.read(Marshaller.java:85)
>         at org.jgroups.Message.readExternal(Message.java:352)
>         at
> org.jgroups.protocols.UDP.handleIncomingUdpPacket(UDP.java:527)
>         at org.jgroups.protocols.UDP$UcastReceiver.run(UDP.java:1119)
>         at java.lang.Thread.run(Thread.java:536)
> -----------------------
>
> Kindly help me sort out this problem as its hampering our
> development!!
> I am also attaching the "Server.log" for this problem.
>
> Thanks in advance,
> Nishant.
>



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

<?xml version="1.0" encoding="UTF-8"?>

<!-- ===================================================================== -->
<!--                                                                       -->
<!--  Sample Clustering Service Configuration                              -->
<!--                                                                       -->
<!-- ===================================================================== -->

<server>

  <classpath codebase="lib" archives="jbossha.jar"/>

  <!-- ==================================================================== -->
  <!-- Cluster Partition: defines cluster                                   -->
  <!-- ==================================================================== -->

  <mbean code="org.jboss.ha.framework.server.ClusterPartition"
         name="jboss:service=DefaultPartition">
         
    <!-- Name of the partition being built -->
    <attribute name="PartitionName">DefaultPartition</attribute>
    <!-- Determine if deadlock detection is enabled -->
    <attribute name="DeadlockDetection">False</attribute>
    <!-- The JGroups protocol configuration -->
    <attribute name="PartitionConfig">
      <Config>
        <!-- UDP: if you have a multihomed machine, 
             set the bind_addr attribute to the appropriate NIC IP address -->
        <!-- UDP: On Windows machines, because of the media sense feature
             being broken with multicast (even after disabling media sense)
             set the loopback attribute to true -->
        <UDP mcast_addr="228.1.2.3" mcast_port="45566" 
             ip_ttl="64" 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" />
        <PING timeout="2000" num_initial_members="3" 
              up_thread="true" down_thread="true" />
        <MERGE2 min_interval="5000" max_interval="10000" />
        <FD shun="true" up_thread="true" down_thread="true" 
            timeout="2500" max_tries="5" />
        <VERIFY_SUSPECT timeout="3000" num_msgs="3"
                        up_thread="true" down_thread="true" />
        <pbcast.NAKACK gc_lag="50" retransmit_timeout="300,600,1200,2400,4800"
                       up_thread="true" down_thread="true" />
        <pbcast.STABLE desired_avg_gossip="20000"
                       up_thread="true" down_thread="true" />
        <UNICAST timeout="5000" window_size="100" min_threshold="10"
                 down_thread="true" />
        <FRAG frag_size="8192"
              down_thread="true" up_thread="true" />
        <pbcast.GMS join_timeout="5000" join_retry_timeout="2000"
                    shun="true" print_local_addr="true" />
        <pbcast.STATE_TRANSFER up_thread="true" down_thread="true" />
      </Config>
    </attribute>
  </mbean>

  <!-- ==================================================================== -->
  <!-- HA Session State Service for SFSB                                    -->
  <!-- ==================================================================== -->

  <mbean code="org.jboss.ha.hasessionstate.server.HASessionStateService"
         name="jboss:service=HASessionState">
     <depends>jboss:service=DefaultPartition</depends>
    <!-- Name of the partition to which the service is linked -->
    <attribute name="PartitionName">DefaultPartition</attribute>
    <!-- JNDI name under which the service is bound -->
    <attribute name="JndiName">/HASessionState/Default</attribute>
    <!-- Max delay before cleaning unreclaimed state.
         Defaults to 30*60*1000 => 30 minutes -->
    <attribute name="BeanCleaningDelay">0</attribute>    
  </mbean>

  <!-- ==================================================================== -->
  <!-- HA JNDI                                                              -->
  <!-- ==================================================================== -->

  <mbean code="org.jboss.ha.jndi.HANamingService" 
         name="jboss:service=HAJNDI">
     <depends>jboss:service=DefaultPartition</depends>
    <!-- Name of the partition to which the service is linked -->
    <attribute name="PartitionName">DefaultPartition</attribute>
    <!-- bind address of HA JNDI RMI endpoint -->
    <attribute name="BindAddress">${jboss.bind.address}</attribute>
    <!-- RmiPort to be used by the HA-JNDI service
         once bound. 0 => auto. -->
    <attribute name="RmiPort">0</attribute>
    <!-- Port on which the HA-JNDI stub is made available -->
    <attribute name="Port">1100</attribute>
    <!-- Backlog to be used for client-server RMI 
         invocations during JNDI queries -->
    <attribute name="Backlog">50</attribute>
    
    <!-- Multicast Address and Group used for auto-discovery -->
    <attribute name="AutoDiscoveryAddress">230.0.0.4</attribute>
    <attribute name="AutoDiscoveryGroup">1102</attribute>

    <!-- IP Address to which should be bound: the Port, the RmiPort and
         the AutoDiscovery multicast socket. -->
    <!-- Client socket factory to be used for client-server
         RMI invocations during JNDI queries -->
    <!--attribute name="ClientSocketFactory">custom</attribute-->
    <!-- Server socket factory to be used for client-server
         RMI invocations during JNDI queries -->
    <!--attribute name="ServerSocketFactory">custom</attribute-->
  </mbean>

  <mbean code="org.jboss.invocation.jrmp.server.JRMPInvokerHA"
         name="jboss:service=invoker,type=jrmpha">
     <attribute name="ServerAddress">${jboss.bind.address}</attribute>
    <!--
    <attribute name="RMIObjectPort">0</attribute>
    <attribute name="RMIClientSocketFactory">custom</attribute>
    <attribute name="RMIServerSocketFactory">custom</attribute>
    -->
  </mbean>

  <!-- ==================================================================== -->
  <!-- Distributed cache invalidation                                       -->
  <!-- ==================================================================== -->

  <mbean code="org.jboss.cache.invalidation.bridges.JGCacheInvalidationBridge" 
         name="jboss.cache:service=InvalidationBridge,type=JavaGroups">
     <depends>jboss:service=DefaultPartition</depends>
     <depends>jboss.cache:service=InvalidationManager</depends>
     <attribute name="InvalidationManager">jboss.cache:service=InvalidationManager</attribute>
     <attribute name="PartitionName">DefaultPartition</attribute>
     <attribute name="BridgeName">DefaultJGBridge</attribute>
  </mbean>

</server>

Reply via email to