JBossDeveloper

sure, give me sometime to clear jgroup concepts.

It will be a combination of the two

1. exec will spawn the processes
2. jgroups will choreagraph the events between these processes and the results

this mechanism i am planning to use for the performance tests also.
(remoting does the similar things!) and they have the infrastructure in place.

Only glitch is all the classes like DistributedTestCase,MultipleTestCase are in org.jboss.remoting :

Should i keep using them or should i make a replica for jms/or somebody at jboss abstracts them to a common module, where multiple modules can use them?

Ovidiu,
Spent last week on analysis of jgroups and the distributed testing framework developed by Tom.

i developed the test clients with producer/consumers in separate VMs and notifications through jgroups.
With 3 VMs its very slow and its not so predictable(may be i am doing somethign wrong).I was wondering what will happen when its more that 3 VMs?

so i am thinking of using RMI for the synchronization instead.
Will update on that in a day or two.

The distributed test case framework for JMS using jgroups has been implemented(Based on remoting DTF source base)

Scenario covered
1.One producer
2.One synchronous consumer

Its based on the distributed test framework developed by Tom for remoting org/jboss/dtf/**
I copied it into jboss-head/jms/tests directory.

Result

Testsuite: org.jboss.test.messaging.jms.dist.DistributedProducerSynchConsumerTestCase
Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 35.441 sec
------------- Standard Output ---------------

-------------------------------------------------------
GMS: address is localhost:1821
-------------------------------------------------------
------------- ---------------- ---------------

Testcase: testInvokers took 30.113 sec
FAILED
expected: but was:<ID:3j001-4n2l02-e7k0983a-1-e7k09gkq-3>
junit.framework.ComparisonFailure: expected: but was:<ID:3j001-4n2l02-e7k0983a-1-e7k09gkq-3>
at org.jboss.test.messaging.jms.dist.DistributedProducerSynchConsumerTestCase.testInvokers(DistributedProducerSynchConsumerTestCase.java:125)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at org.jboss.dtf.DistributedTestCase.run(DistributedTestCase.java:509)

The Test Fails, producer is setting the msg id to null,
(similar scenario in a local call passes)
With last weeks' CVS co this was passing, when i did the update yesterday the test started failing.

Issues faced

1.Had to change the {}/jboss-head/jms/src/resources/jgroups-core.jar with the one from thirdparty module
Problem with RPCDispatcher of jgroups-core, not able to make remote calls to methods of super class if they are not overridden in the sub class.

2.Added following property to jgroups props in org.jboss.dtf.DistributedTestCase to make jgroups work on my m/c
bind_addr=127.0.0.1;
please remove this if tests give an error.
Design

The test case has the following java files

org.jboss.test.messaging.jms.dist.DistributedProducerSynchConsumerTestCase
 org.jboss.test.messaging.jms.dist.ProducerClientTest
 org.jboss.test.messaging.jms.dist.SynchConsumerClientTest

public void sendMessage(String type,String message)
 {
 MethodCall call = new MethodCall("receiveMessage",
 new Object[]{type,message}, new Class[]{String.class,String.class});
 disp.callRemoteMethods(null, call, GroupRequest.GET_NONE, 0);
 log.debug("sent Message :" + call);
 }

 public void receiveMessage(String type,String message)
 {
 log.debug("Received Msg:" + type + "::" + message);
 }

public Logger setLogging(String level, String fileName, Class classObj)
 {
 ...
 }

<path id="library.classpath">

 <!--<pathelement path="${module.root}/../src/resources/jgroups-core.jar"/>-->
 <pathelement path="${module.root}/../src/resources/jgroups.jar"/>
 <pathelement path="${module.root}/../../j2ee/output/lib/jboss-j2ee.jar"/>

Added new component
 <path id="jms.classes">
 <pathelement path="./../output/etc"/>
 <pathelement path="./../output/classes"/>
 <pathelement path="${module.root}/../../aspects/output/lib/jboss-aspect-library.jar"/>
 <pathelement path="${module.root}/../../common/output/lib/jboss-common.jar"/>
 <pathelement path="${module.root}/../../remoting/output/lib/jboss-remoting.jar"/>
 <pathelement path="${module.root}/../../j2se/output/lib/jboss-j2se.jar"/>
 <pathelement path="${module.root}/../../naming/output/lib/jnp-client.jar"/>
 <pathelement path="${module.root}/../../thirdparty/javassist/lib/javassist.jar"/>
 <pathelement path="${module.root}/../../thirdparty/oswego-concurrent/lib/concurrent.jar"/>
 <pathelement path="${module.root}/../../thirdparty/apache-commons/lib/commons-httpclient.jar"/>
 <pathelement path="${module.root}/../../thirdparty/trove/lib/trove.jar"/>
 </path>

 <path id="dependentmodule.classpath">
 <path refid="jboss.common.classpath"/>
 <path refid="jboss.jms.classpath"/>
 <path refid="jboss.j2ee.classpath"/>
 <path refid="jboss.j2se.classpath"/>
 <path refid="jms.classes"/>
 <path refid="jboss.remoting.classpath"/>
 <path refid="jboss.aop.classpath"/>
 </path>

<target name="tests-jar"
 depends="compile-test-classes"
 description="Creates the jar file with all the tests">

 <mkdir dir="${build.tests.lib}"/>

 <!-- Build the tests jar -->
 <jar jarfile="${build.tests.lib}/${build.tests.archive}">
 <fileset dir="${build.tests.classes}">
 <include name="org/jboss/test/messaging/**"/>
 <include name="org/jboss/dtf/**"/>
 <include name="org/jboss/dummy/**"/>
 </fileset>
 </jar>
 </target>

 public synchronized static void startRemoteServer(Hashtable ht) throws Exception

 public synchronized static void stopRemoteServer() throws Exception

 public static InitialContext getRemoteInitialContext() throws Exception