[tcunning]

Ray,

Are the two juddi registries sharing the same database (check server/default/deploy/jbossesb-registry.sar/juddi-ds.xml)?      Just double checking the simple stuff.

--Tom

[solomonzr]

Tom,

Sorry to reply you so late. I have checked the file (\jboss-5.1.0.GA\server\all\deploy\jbossesb-registry.sar\juddi-ds.xml) on both nodes.

I do not modified it since the JBossAS5.1GA is installed. I don't think them are sharing the same database. Do you mean that it is needed to share the same database? If so, how to configure it? Thanks.

Ray

[tcunning]

Yes.   Given the usecase you've described, you want the two registries sharing the same database.     All you should need to do is alter the juddi-ds.xml files on both servers to point to the same database connection.         If you've been using the default hsql up to this point you might want to configure a production quality database like Oracle or MySQL or PostgresQL or SQL Server (etc, etc) and add the appropriate JDBC driver JAR to server/default/lib.

Then test out the load balancing settings again.

[solomonzr]

Tom,

Great! I configure them as you said, These two nodes shares the same MySQL database. And it works as random mode.

It makes me so happy. But another question appeares. I find that the load balance policy are always random. So I decide to test the other two modes(FirstAvailable and RoundRobin).

I find there are two files setted the load balance policy (\jboss-5.1.0.GA\server\all\data\jbossesb-properties.xml) and (\jboss-5.1.0.GA\server\all\deployers\esb.deployer\jbossesb-properties.xml). They are RoundRobin before I alter them(I don't know why they are not RandomRobin). Then I alter them to FirstAvailable. Then restart both nodes. It doesn't work. It is still random mode. Can you point out what is wrong with it and where to set the load balance policy? Thanks.

Ray

[tcunning]

Ray,

You're running the ServiceInvoker as a standalone client though (remote serviceinvoker), correct?    In that instance you need a jbossesb-properties.xml in the ServiceInvoker's classpath that contains the the load balance policy you want.     I'd go back and change the esb.deployer/jbossesb-properties.xml back to default and either add or change the one on your classpath - I bet that fixes the problem.

--Tom

[solomonzr]

Tom,

Today, I recover the jbossesb-properties.xml on server to default. Then I configure the policy in jbossesb-properties.xml on classpath of the client. The test result is FirstAvailable policy works. The RoundRobin and RandomRobin are likely same. In my opinion, the RoundRobin means the cluster will process request by circles. Just like nodeA, nodeB, nodeA, nodeB..., if there are only two nodes. But in my test, when I configure it as RoundRobin, the cluster behaves like Random. Do you meet the same result and do you know why?

Another question is I'm a little confuse about the policy configure. I know it uses a client-side interceptor architecture. But I think the load balance policy should be configure on the server side. Which means the policy should be transparent to the client. The client doesn't care which load balance policy works, it just care the request are processed. In this case, the client decides which policies are used. Is that reasonable?

Ray

[carl918]

my project structure is above graph ,i'm sure added all jars , But sending ESB-Message with ServiceInvoker doesn't work,make exception following:

Exception in thread "main" org.jboss.soa.esb.listeners.message.MessageDeliverException: org.apache.ws.scout.transport.TransportException: java.lang.reflect.InvocationTargetException

          at org.jboss.soa.esb.client.ServiceInvoker.loadServiceClusterInfo(ServiceInvoker.java:545)

          at org.jboss.soa.esb.client.ServiceInvoker.<init>(ServiceInvoker.java:174)

          at org.jboss.soa.esb.client.ServiceInvoker.<init>(ServiceInvoker.java:155)

          at org.jboss.soa.esb.client.ServiceInvoker.<init>(ServiceInvoker.java:197)

          at org.jboss.soa.esb.samples.quickstart.messagestore.test.SendEsbMessage.main(SendEsbMessage.java:64)

Caused by: org.jboss.soa.esb.services.registry.RegistryException: org.apache.ws.scout.transport.TransportException: java.lang.reflect.InvocationTargetException

          at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.findEPRs(JAXRRegistryImpl.java:348)

          at org.jboss.internal.soa.esb.services.registry.InVMRegistryInterceptor.findEPRs(InVMRegistryInterceptor.java:85)

          at org.jboss.soa.esb.services.registry.RegistryFactory$HeadRegistryInterceptor.findEPRs(RegistryFactory.java:229)

          at org.jboss.soa.esb.listeners.RegistryUtil.getEprs(RegistryUtil.java:226)

          at org.jboss.soa.esb.client.ServiceInvoker.loadServiceClusterInfo(ServiceInvoker.java:532)

          ... 4 more

Caused by: javax.xml.registry.JAXRException: org.apache.ws.scout.transport.TransportException: java.lang.reflect.InvocationTargetException

          at org.apache.ws.scout.registry.BusinessQueryManagerV3Impl.findConcepts(BusinessQueryManagerV3Impl.java:516)

          at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.getJBossESBTModel(JAXRRegistryImpl.java:653)

          at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.findEPRs(JAXRRegistryImpl.java:307)

          ... 8 more

[tcunning]

Carl,

Which version of ESB are you using?   And just to double check - you are running with ESB on top of jboss AS 4.2.3.GA (or using the ESB server)?