Hi,

I'm trying to get basic farming to work, as described in the QuickStart guide.

I have three CMP 2.0 entity beans. They default to use the DefaultDS, tables and all 
are created when deploying, so they seem ok.

Further, I have an jboss.xml that containt the follownig:

<?xml version="1.0" encoding="UTF-8"?>
<jboss>
  <enterprise-beans>
    <entity>
      <ejb-name>AuthorEJB</ejb-name>
      <jndi-name>AuthorEJB</jndi-name>
      <clustered>True</clustered>
    </entity>
    <entity>
      <ejb-name>LocationEJB</ejb-name>
      <jndi-name>LocationEJB</jndi-name>
      <clustered>True</clustered>
    </entity>
    <entity>
      <ejb-name>PublicationEJB</ejb-name>
      <jndi-name>PublicationEJB</jndi-name>
      <clustered>True</clustered>
    </entity>
  </enterprise-beans>
</jboss>

(... which resides in the META-INF along with ejb-jar.xml)

Everything is packed in an EAR-file.

Then, for the JBoss configuration:

On both machines in the cluster I did the following:

I renamed the "all" configuration directory to "default" (and "default" to 
"default.old", how does one specify which directory jboss should use, by the way?), so 
that the clustering-service.xml gets deployed (it deploys without errors, it seems).

I created an (almost) exact copy of the farm-service.xml described in the QuickStart 
guide:

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

<!-- Created by martin.solaas on 5. juni 2002, 09:17 -->

<server>

    <classpath codebase="lib" archives="jbossha.jar" />
    
    <mbean code="org.jboss.ha.framework.server.FarmMemberService"
        name="jboss:service=FarmMember,partition=DefaultPartition">
        <attribute name="PartitionName">DefaultPartition</attribute>
        <attribute name="FarmDeployDirectory">./farm</attribute>
        <attribute 
name="ScannerName">jboss.deployment:type=DeploymentScanner,flavor=URL</attribute>
    </mbean>

</server>

... which also seems to deploy flawlessly, on both machines (in the default/deploy 
directory)

Then I created default/deploy/farm directory on both machines, expecting that 
something automagically would happen on one machine when my EAR is deployed in the 
farm-directory on the other. For all I know it might work as it should, but if it does 
so the farm-deployment doesn't leave any trace at all on the "passive" machine, no 
message on the console or in the logfile, and the beans are not listed on 
http//clusternode:8082. (However, the HA/Farm stuff shows up on the admin-url).

I'm not really sure what is the correct JNDI-setup for clustering, so I've tried with 
the default jndi.properties and with the line

java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces commented out

Has anyone got this working?

-- 
[EMAIL PROTECTED]

_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to