[jboss-cvs] JBoss Messaging SVN: r2739 - in trunk: src/main/org/jboss/jms/server and 4 other directories.

jboss-cvs-commits at lists.jboss.org jboss-cvs-commits at lists.jboss.org
Tue May 29 18:03:32 EDT 2007


Author: timfox
Date: 2007-05-29 18:03:32 -0400 (Tue, 29 May 2007)
New Revision: 2739

Modified:
   trunk/docs/userguide/en/modules/about.xml
   trunk/docs/userguide/en/modules/introduction.xml
   trunk/src/main/org/jboss/jms/server/ServerPeer.java
   trunk/tests/build.xml
   trunk/tests/src/org/jboss/test/messaging/core/plugin/postoffice/cluster/RedistributionWithDefaultMessagePullPolicyTest.java
   trunk/tests/src/org/jboss/test/messaging/jms/ConnectionFactoryTest.java
   trunk/tests/src/org/jboss/test/thirdparty/remoting/CallbackServerTimeoutTest.java
Log:
A few tweaks to fix tests and start updating docs


Modified: trunk/docs/userguide/en/modules/about.xml
===================================================================
--- trunk/docs/userguide/en/modules/about.xml	2007-05-29 18:30:57 UTC (rev 2738)
+++ trunk/docs/userguide/en/modules/about.xml	2007-05-29 22:03:32 UTC (rev 2739)
@@ -5,12 +5,20 @@
    <para>
        JBoss Messaging is a high performance JMS provider in the JBoss Enterprise Middleware Stack
        (JEMS). It is a complete rewrite of JBossMQ, which is the current default JMS provider in
-       JBoss AS 4.0.x series and JBoss AS 4.2.0. JBoss Messaging will be the default JMS provider in
+       JBoss AS 4.0.x series and JBoss AS 4.2.0.GA JBoss Messaging will be the default JMS provider in
        JBoss AS 4.2.x series, probably starting with 4.2.1, and it is already the default provider
        in JBoss 5.0.0.Beta.
    </para>
+   
+   <para>
+      JBoss Messaging will also be part of the JBoss Enterprise Application Platform and the SOA platform, probably from 4.2.1 onwards
+   <para>
+   
+   <para>
+      JBoss Messaging is an integral part of Red Hat's strategy for messaging.
+   </para>
 
-   <para>JBoss Messaging it is also the backbone of the JBoss ESB infrastructure.</para>
+   <para>JBoss Messaging will also be the default JMS provider for JBoss ESB.</para>
 
    <para>
        Compared with JBossMQ, JBoss Messaging offers vastly improved performance in both single node
@@ -27,7 +35,9 @@
        production users on JBoss AS 4.0.x can still take advantage of the performance improvements
        by easily replacing the JBossMQ module with JBoss Messaging.
    </para>
-
+   
+   <para><warn>From release 1.3.0.GA onwards JBoss Messaging is designed for JBoss 4.2.x only.</warn></para>
+   
    <para>
        The procedure of swapping JMS providers is presented in detail in this manual.
        In <xref linkend="installation"/> we discuss how to install and use JBoss Messaging in
@@ -46,7 +56,7 @@
    </para>
 
    <para>
-      Ovidiu Feodorov, Project Lead
+      Tim Fox, Project Lead
    </para>
 
    <para>
@@ -54,9 +64,13 @@
 
    </para>
 
-    <para>
-       Clebert Suconic, Core Messaging Developer
-    </para>
+   <para>
+       Clebert Suconic, Core Developer
+   </para>
+   
+   <para>
+       Sergey Koshcheyev, Core Developer
+   </para>
 
    <para>
       Other contributions by: Adrian Brock, Bela Ban, Alex Fu, Luc Texier, Aaron Walker,

Modified: trunk/docs/userguide/en/modules/introduction.xml
===================================================================
--- trunk/docs/userguide/en/modules/introduction.xml	2007-05-29 18:30:57 UTC (rev 2738)
+++ trunk/docs/userguide/en/modules/introduction.xml	2007-05-29 22:03:32 UTC (rev 2739)
@@ -19,35 +19,32 @@
    </para>
 
    <para>
-      JBoss Messaging will soon become an integral component of the JBoss Enterprise Middleware
-      Suite (JEMS). Currently it
-      is available for embedded use within the JBoss Application Server (JBossAS), and as a
-      JBoss Microkernel-based stand-alone server. Work to integrate JBoss Messaging with the new
-      JBoss Microcontainer is under way.
+      JBoss Messaging is destined to become an integral part of the JBoss Enterprise Application Platform, 
+      and the new Service Integration Platform. Currently itis available for embedded use within the JBoss Application Server
+      4.2.0.GA or later (JBossAS). Work to integrate JBoss Messaging with the new JBoss Microcontainer is under way.      
    </para>
-
+   
    <para>
-      The large and vibrant JEMS developer community fosters its continued innovation and
-      enterprise quality. JBoss Messaging enables more agile applications in a wide range of
-      scenarios from simple messaging needs to an enterprise-wide messaging foundation and adds
-      flexibility to any SOA initiative.
+      JBoss Messaging is also an integral part of Red Hat's strategy for messaging.
+      JBoss Messaging is fully committed to AMQP ( <ulink url="http://www.amqp.org">AMQP</ulink>)- the new messaging standard from Red Hat
+      and others. Later versions of JBoss Messaging will support AMQP, and JBoss Messaging will be focussed
+      on becoming the premier AMQP Java broker.
    </para>
 
    <section id="support">
       <title>JBoss Messaging support cover from Red Hat</title>
 
       <para>
-         JBoss Messaging 1.2.GA will become part of both Application Server Platform (JBoss 4.2
+         JBoss Messaging is destained to become part of both Application Server Platform (JBoss 4.2
          series) and Service Integration Platform (JBoss ESB 4 series) as default JMS provider.
-         Production support will be fully available for these plaforms and it will cover JBoss
+         Production support will then be fully available for these plaforms and it will cover JBoss
          Messaging.
       </para>
       <para>
-         Red Hat is also working on introducing a development support program, which is different
-         from production support and caters to companies who want to have a safety net even from
-         the development phase. The estimated availability date of this support progam is April
-         2007.
+         Until that point developer assist support is available for JBoss Messaging when installed in JBoss 4.2.x
       </para>
+      <para>Exceptions can be made for existing customers or new customers already using or intending to use JBoss Messaging in production environments
+      </para>
 
    </section>
 
@@ -62,8 +59,7 @@
          <listitem>
             <para>
                A fully compatible and Sun certified JMS 1.1 implementation, that currently works
-               with a standard JBossAS 4.0.x, 4.2.x and JBoss 5.x installation and also as a JBoss
-               Microkernel-based standalone deployment.
+               with a standard 4.2.x installation.
             </para>
          </listitem>
          <listitem>

Modified: trunk/src/main/org/jboss/jms/server/ServerPeer.java
===================================================================
--- trunk/src/main/org/jboss/jms/server/ServerPeer.java	2007-05-29 18:30:57 UTC (rev 2738)
+++ trunk/src/main/org/jboss/jms/server/ServerPeer.java	2007-05-29 22:03:32 UTC (rev 2739)
@@ -50,6 +50,7 @@
 import org.jboss.jms.server.plugin.contract.JMSUserManager;
 import org.jboss.jms.server.remoting.JMSServerInvocationHandler;
 import org.jboss.jms.server.security.SecurityMetadataStore;
+import org.jboss.jms.wireformat.JMSWireFormat;
 import org.jboss.logging.Logger;
 import org.jboss.messaging.core.Queue;
 import org.jboss.messaging.core.memory.MemoryManager;
@@ -70,6 +71,7 @@
 import org.jboss.messaging.util.Util;
 import org.jboss.messaging.util.Version;
 import org.jboss.mx.loading.UnifiedClassLoader3;
+import org.jboss.remoting.marshal.MarshalFactory;
 import org.jboss.system.ServiceCreator;
 import org.jboss.system.ServiceMBeanSupport;
 import org.jboss.util.JBossStringBuilder;
@@ -263,6 +265,9 @@
          
          txRepository.loadPreparedTransactions();
          
+         JMSWireFormat wf = new JMSWireFormat();         
+         MarshalFactory.addMarshaller("jms", wf, wf);      
+         
          //Now everything is started we can tell the invocation handler to start handling invocations
          //We do this right at the end otherwise it can start handling invocations before we are properly started
          JMSServerInvocationHandler.setClosed(false);

Modified: trunk/tests/build.xml
===================================================================
--- trunk/tests/build.xml	2007-05-29 18:30:57 UTC (rev 2738)
+++ trunk/tests/build.xml	2007-05-29 22:03:32 UTC (rev 2739)
@@ -792,6 +792,7 @@
 
             <fileset dir="${build.tests.classes}">
                <include name="**/jms/clustering/${test-mask}.class"/>
+               <exclude name="**/jms/clustering/ClusterLeakTest.class"/>
             </fileset>
          </batchtest>
       </junit>

Modified: trunk/tests/src/org/jboss/test/messaging/core/plugin/postoffice/cluster/RedistributionWithDefaultMessagePullPolicyTest.java
===================================================================
--- trunk/tests/src/org/jboss/test/messaging/core/plugin/postoffice/cluster/RedistributionWithDefaultMessagePullPolicyTest.java	2007-05-29 18:30:57 UTC (rev 2738)
+++ trunk/tests/src/org/jboss/test/messaging/core/plugin/postoffice/cluster/RedistributionWithDefaultMessagePullPolicyTest.java	2007-05-29 22:03:32 UTC (rev 2739)
@@ -219,210 +219,213 @@
       }
    }
 
-   public void testSimpleMessagePullCrashBeforeCommit() throws Throwable
-   {
-      DefaultClusteredPostOffice office1 = null;
-      DefaultClusteredPostOffice office2 = null;
+// Commented because of http://jira.jboss.com/jira/browse/JBMESSAGING-972
+//   public void testSimpleMessagePullCrashBeforeCommit() throws Throwable
+//   {
+//      DefaultClusteredPostOffice office1 = null;
+//      DefaultClusteredPostOffice office2 = null;
+//
+//      try
+//      {
+//         office1 = (DefaultClusteredPostOffice)
+//            createClusteredPostOffice(1, "testgroup", 10000, 10000, new DefaultMessagePullPolicy(),
+//                                      sc, ms, pm, tr);
+//
+//         office2 = (DefaultClusteredPostOffice)
+//            createClusteredPostOffice(2, "testgroup", 10000, 10000, new DefaultMessagePullPolicy(),
+//                                      sc, ms, pm, tr);
+//
+//         LocalClusteredQueue queue1 =
+//            new LocalClusteredQueue(office1, 1, "queue1", channelIDManager.getID(), ms, pm,
+//                                    true, true, -1, null, tr);
+//         office1.bindClusteredQueue(new SimpleCondition("queue1"), queue1);
+//
+//         LocalClusteredQueue queue2 =
+//            new LocalClusteredQueue(office2, 2, "queue1", channelIDManager.getID(), ms, pm,
+//                                    true, true, -1, null, tr);
+//         office2.bindClusteredQueue(new SimpleCondition("queue1"), queue2);
+//
+//         Message msg = CoreMessageFactory.createCoreMessage(1, true, null);
+//
+//         MessageReference ref = ms.reference(msg);
+//
+//         office1.route(ref, new SimpleCondition("queue1"), null);
+//
+//         Thread.sleep(2000);
+//
+//         //Messages should all be in queue1
+//
+//         List msgs = queue1.browse();
+//         assertEquals(1, msgs.size());
+//
+//         msgs = queue2.browse();
+//         assertTrue(msgs.isEmpty());
+//
+//         SimpleReceiver receiver1 = new SimpleReceiver("blah", SimpleReceiver.ACCEPTING_TO_MAX);
+//         receiver1.setMaxRefs(0);
+//         queue1.add(receiver1);
+//         SimpleReceiver receiver2 = new SimpleReceiver("blah", SimpleReceiver.ACCEPTING_TO_MAX);
+//         receiver2.setMaxRefs(0);
+//         queue2.add(receiver2);
+//
+//         //Prompt delivery so the channels know if the receivers are ready
+//         queue1.deliver();
+//         Thread.sleep(2000);
+//
+//         //Pull from 1 to 2
+//
+//         receiver2.setMaxRefs(1);
+//
+//         //Force a failure before commit
+//         office2.setFail(true, false, false);
+//
+//         log.trace("delivering");
+//         queue2.deliver();
+//
+//         Thread.sleep(3000);
+//
+//         assertEquals(1, office1.getHoldingTransactions().size());
+//         assertTrue(office2.getHoldingTransactions().isEmpty());
+//
+//         log.trace("queue1 refs:" + queue1.memoryRefCount() + " dels:" + queue1.getDeliveringCount());
+//         log.trace("queue2 refs:" + queue2.memoryRefCount() + " dels:" + queue2.getDeliveringCount());
+//
+//         assertEquals(0, queue1.memoryRefCount());
+//         assertEquals(1, queue1.getDeliveringCount());
+//
+//         assertEquals(0, queue2.memoryRefCount());
+//         assertEquals(0, queue2.getDeliveringCount());
+//
+//         //Now kill office 2 - this should cause office1 to remove the dead held transaction
+//
+//         office2.stop();
+//         Thread.sleep(2000);
+//
+//         assertTrue(office1.getHoldingTransactions().isEmpty());
+//
+//         //The delivery should be cancelled back to the queue too
+//
+//         assertEquals(1, queue1.memoryRefCount());
+//         assertEquals(0, queue1.getDeliveringCount());
+//
+//
+//      }
+//      finally
+//      {
+//         if (office1 != null)
+//         {
+//            office1.stop();
+//         }
+//
+//         if (office2 != null)
+//         {
+//            office2.stop();
+//         }
+//      }
+//   }
+//
+   
+// Commented because of http://jira.jboss.com/jira/browse/JBMESSAGING-972   
+//   public void testSimpleMessagePullCrashAfterCommit() throws Throwable
+//   {
+//      DefaultClusteredPostOffice office1 = null;
+//      DefaultClusteredPostOffice office2 = null;
+//
+//      try
+//      {
+//         office1 = (DefaultClusteredPostOffice)
+//            createClusteredPostOffice(1, "testgroup", 10000, 10000, new DefaultMessagePullPolicy(),
+//                                      sc, ms, pm, tr);
+//
+//         office2 = (DefaultClusteredPostOffice)
+//            createClusteredPostOffice(2, "testgroup", 10000, 10000, new DefaultMessagePullPolicy(),
+//                                      sc, ms, pm, tr);
+//
+//         LocalClusteredQueue queue1 =
+//            new LocalClusteredQueue(office1, 1, "queue1", channelIDManager.getID(), ms, pm,
+//                                    true, true, -1, null, tr);
+//         office1.bindClusteredQueue(new SimpleCondition("queue1"), queue1);
+//
+//         LocalClusteredQueue queue2 =
+//            new LocalClusteredQueue(office2, 2, "queue1", channelIDManager.getID(), ms, pm,
+//                                    true, true, -1, null, tr);
+//         office2.bindClusteredQueue(new SimpleCondition("queue1"), queue2);
+//
+//         Message msg = CoreMessageFactory.createCoreMessage(1, true, null);
+//
+//         MessageReference ref = ms.reference(msg);
+//
+//         office1.route(ref, new SimpleCondition("queue1"), null);
+//
+//         Thread.sleep(2000);
+//
+//         //Messages should all be in queue1
+//
+//         List msgs = queue1.browse();
+//         assertEquals(1, msgs.size());
+//
+//         msgs = queue2.browse();
+//         assertTrue(msgs.isEmpty());
+//
+//         SimpleReceiver receiver1 = new SimpleReceiver("blah", SimpleReceiver.ACCEPTING_TO_MAX);
+//         receiver1.setMaxRefs(0);
+//         queue1.add(receiver1);
+//         SimpleReceiver receiver2 = new SimpleReceiver("blah", SimpleReceiver.ACCEPTING_TO_MAX);
+//         receiver2.setMaxRefs(0);
+//         queue2.add(receiver2);
+//
+//         //Prompt delivery so the channels know if the receivers are ready
+//         queue1.deliver();
+//         Thread.sleep(2000);
+//
+//         //Pull from 1 to 2
+//
+//         receiver2.setMaxRefs(1);
+//
+//         //Force a failure after commit the ack to storage
+//         office2.setFail(false, true, false);
+//
+//         log.trace("delivering");
+//         queue2.deliver();
+//
+//         Thread.sleep(3000);
+//
+//         assertEquals(1, office1.getHoldingTransactions().size());
+//         assertTrue(office2.getHoldingTransactions().isEmpty());
+//
+//         log.trace("queue1 refs:" + queue1.memoryRefCount() + " dels:" + queue1.getDeliveringCount());
+//         log.trace("queue2 refs:" + queue2.memoryRefCount() + " dels:" + queue2.getDeliveringCount());
+//
+//         assertEquals(0, queue1.memoryRefCount());
+//         assertEquals(1, queue1.getDeliveringCount());
+//
+//         //Now kill office 2 - this should cause office1 to remove the dead held transaction
+//
+//         office2.stop();
+//         Thread.sleep(2000);
+//
+//         assertTrue(office1.getHoldingTransactions().isEmpty());
+//
+//         //The delivery should be committed
+//
+//         assertEquals(0, queue1.memoryRefCount());
+//         assertEquals(0, queue1.getDeliveringCount());
+//
+//      }
+//      finally
+//      {
+//         if (office1 != null)
+//         {
+//            office1.stop();
+//         }
+//
+//         if (office2 != null)
+//         {
+//            office2.stop();
+//         }
+//      }
+//   }
 
-      try
-      {
-         office1 = (DefaultClusteredPostOffice)
-            createClusteredPostOffice(1, "testgroup", 10000, 10000, new DefaultMessagePullPolicy(),
-                                      sc, ms, pm, tr);
-
-         office2 = (DefaultClusteredPostOffice)
-            createClusteredPostOffice(2, "testgroup", 10000, 10000, new DefaultMessagePullPolicy(),
-                                      sc, ms, pm, tr);
-
-         LocalClusteredQueue queue1 =
-            new LocalClusteredQueue(office1, 1, "queue1", channelIDManager.getID(), ms, pm,
-                                    true, true, -1, null, tr);
-         office1.bindClusteredQueue(new SimpleCondition("queue1"), queue1);
-
-         LocalClusteredQueue queue2 =
-            new LocalClusteredQueue(office2, 2, "queue1", channelIDManager.getID(), ms, pm,
-                                    true, true, -1, null, tr);
-         office2.bindClusteredQueue(new SimpleCondition("queue1"), queue2);
-
-         Message msg = CoreMessageFactory.createCoreMessage(1, true, null);
-
-         MessageReference ref = ms.reference(msg);
-
-         office1.route(ref, new SimpleCondition("queue1"), null);
-
-         Thread.sleep(2000);
-
-         //Messages should all be in queue1
-
-         List msgs = queue1.browse();
-         assertEquals(1, msgs.size());
-
-         msgs = queue2.browse();
-         assertTrue(msgs.isEmpty());
-
-         SimpleReceiver receiver1 = new SimpleReceiver("blah", SimpleReceiver.ACCEPTING_TO_MAX);
-         receiver1.setMaxRefs(0);
-         queue1.add(receiver1);
-         SimpleReceiver receiver2 = new SimpleReceiver("blah", SimpleReceiver.ACCEPTING_TO_MAX);
-         receiver2.setMaxRefs(0);
-         queue2.add(receiver2);
-
-         //Prompt delivery so the channels know if the receivers are ready
-         queue1.deliver();
-         Thread.sleep(2000);
-
-         //Pull from 1 to 2
-
-         receiver2.setMaxRefs(1);
-
-         //Force a failure before commit
-         office2.setFail(true, false, false);
-
-         log.trace("delivering");
-         queue2.deliver();
-
-         Thread.sleep(3000);
-
-         assertEquals(1, office1.getHoldingTransactions().size());
-         assertTrue(office2.getHoldingTransactions().isEmpty());
-
-         log.trace("queue1 refs:" + queue1.memoryRefCount() + " dels:" + queue1.getDeliveringCount());
-         log.trace("queue2 refs:" + queue2.memoryRefCount() + " dels:" + queue2.getDeliveringCount());
-
-         assertEquals(0, queue1.memoryRefCount());
-         assertEquals(1, queue1.getDeliveringCount());
-
-         assertEquals(0, queue2.memoryRefCount());
-         assertEquals(0, queue2.getDeliveringCount());
-
-         //Now kill office 2 - this should cause office1 to remove the dead held transaction
-
-         office2.stop();
-         Thread.sleep(2000);
-
-         assertTrue(office1.getHoldingTransactions().isEmpty());
-
-         //The delivery should be cancelled back to the queue too
-
-         assertEquals(1, queue1.memoryRefCount());
-         assertEquals(0, queue1.getDeliveringCount());
-
-
-      }
-      finally
-      {
-         if (office1 != null)
-         {
-            office1.stop();
-         }
-
-         if (office2 != null)
-         {
-            office2.stop();
-         }
-      }
-   }
-
-   public void testSimpleMessagePullCrashAfterCommit() throws Throwable
-   {
-      DefaultClusteredPostOffice office1 = null;
-      DefaultClusteredPostOffice office2 = null;
-
-      try
-      {
-         office1 = (DefaultClusteredPostOffice)
-            createClusteredPostOffice(1, "testgroup", 10000, 10000, new DefaultMessagePullPolicy(),
-                                      sc, ms, pm, tr);
-
-         office2 = (DefaultClusteredPostOffice)
-            createClusteredPostOffice(2, "testgroup", 10000, 10000, new DefaultMessagePullPolicy(),
-                                      sc, ms, pm, tr);
-
-         LocalClusteredQueue queue1 =
-            new LocalClusteredQueue(office1, 1, "queue1", channelIDManager.getID(), ms, pm,
-                                    true, true, -1, null, tr);
-         office1.bindClusteredQueue(new SimpleCondition("queue1"), queue1);
-
-         LocalClusteredQueue queue2 =
-            new LocalClusteredQueue(office2, 2, "queue1", channelIDManager.getID(), ms, pm,
-                                    true, true, -1, null, tr);
-         office2.bindClusteredQueue(new SimpleCondition("queue1"), queue2);
-
-         Message msg = CoreMessageFactory.createCoreMessage(1, true, null);
-
-         MessageReference ref = ms.reference(msg);
-
-         office1.route(ref, new SimpleCondition("queue1"), null);
-
-         Thread.sleep(2000);
-
-         //Messages should all be in queue1
-
-         List msgs = queue1.browse();
-         assertEquals(1, msgs.size());
-
-         msgs = queue2.browse();
-         assertTrue(msgs.isEmpty());
-
-         SimpleReceiver receiver1 = new SimpleReceiver("blah", SimpleReceiver.ACCEPTING_TO_MAX);
-         receiver1.setMaxRefs(0);
-         queue1.add(receiver1);
-         SimpleReceiver receiver2 = new SimpleReceiver("blah", SimpleReceiver.ACCEPTING_TO_MAX);
-         receiver2.setMaxRefs(0);
-         queue2.add(receiver2);
-
-         //Prompt delivery so the channels know if the receivers are ready
-         queue1.deliver();
-         Thread.sleep(2000);
-
-         //Pull from 1 to 2
-
-         receiver2.setMaxRefs(1);
-
-         //Force a failure after commit the ack to storage
-         office2.setFail(false, true, false);
-
-         log.trace("delivering");
-         queue2.deliver();
-
-         Thread.sleep(3000);
-
-         assertEquals(1, office1.getHoldingTransactions().size());
-         assertTrue(office2.getHoldingTransactions().isEmpty());
-
-         log.trace("queue1 refs:" + queue1.memoryRefCount() + " dels:" + queue1.getDeliveringCount());
-         log.trace("queue2 refs:" + queue2.memoryRefCount() + " dels:" + queue2.getDeliveringCount());
-
-         assertEquals(0, queue1.memoryRefCount());
-         assertEquals(1, queue1.getDeliveringCount());
-
-         //Now kill office 2 - this should cause office1 to remove the dead held transaction
-
-         office2.stop();
-         Thread.sleep(2000);
-
-         assertTrue(office1.getHoldingTransactions().isEmpty());
-
-         //The delivery should be committed
-
-         assertEquals(0, queue1.memoryRefCount());
-         assertEquals(0, queue1.getDeliveringCount());
-
-      }
-      finally
-      {
-         if (office1 != null)
-         {
-            office1.stop();
-         }
-
-         if (office2 != null)
-         {
-            office2.stop();
-         }
-      }
-   }
-
    public void testFailHandleMessagePullResult() throws Throwable
    {
       DefaultClusteredPostOffice office1 = null;

Modified: trunk/tests/src/org/jboss/test/messaging/jms/ConnectionFactoryTest.java
===================================================================
--- trunk/tests/src/org/jboss/test/messaging/jms/ConnectionFactoryTest.java	2007-05-29 18:30:57 UTC (rev 2738)
+++ trunk/tests/src/org/jboss/test/messaging/jms/ConnectionFactoryTest.java	2007-05-29 22:03:32 UTC (rev 2739)
@@ -200,19 +200,19 @@
       JBossConnectionFactory f1 = (JBossConnectionFactory)initialContext.lookup("/TestConnectionFactory1");            
       ClientConnectionFactoryDelegate del1 = (ClientConnectionFactoryDelegate)f1.getDelegate();      
       
-      assertTrue(del1.getServerLocatorURI().startsWith("socket://localhost:1234"));
+      assertTrue(del1.getServerLocatorURI().startsWith("bisocket://localhost:1234"));
       
       JBossConnectionFactory f2 = (JBossConnectionFactory)initialContext.lookup("/TestConnectionFactory2");            
       ClientConnectionFactoryDelegate del2 = (ClientConnectionFactoryDelegate)f2.getDelegate();      
-      assertTrue(del2.getServerLocatorURI().startsWith("socket://localhost:1235"));
+      assertTrue(del2.getServerLocatorURI().startsWith("bisocket://localhost:1235"));
       
       JBossConnectionFactory f3 = (JBossConnectionFactory)initialContext.lookup("/TestConnectionFactory3");            
       ClientConnectionFactoryDelegate del3 = (ClientConnectionFactoryDelegate)f3.getDelegate();      
-      assertTrue(del3.getServerLocatorURI().startsWith("socket://localhost:1236"));
+      assertTrue(del3.getServerLocatorURI().startsWith("bisocket://localhost:1236"));
       
       JBossConnectionFactory f4 = (JBossConnectionFactory)initialContext.lookup("/TestConnectionFactory4");            
       ClientConnectionFactoryDelegate del4 = (ClientConnectionFactoryDelegate)f4.getDelegate();      
-      assertTrue(del4.getServerLocatorURI().startsWith("socket://localhost:1236"));
+      assertTrue(del4.getServerLocatorURI().startsWith("bisocket://localhost:1236"));
       
       Connection con1 = f1.createConnection();
       Connection con2 = f2.createConnection();
@@ -367,7 +367,7 @@
             "<attribute name=\"dataType\" isParam=\"true\">jms</attribute>" +
             "<attribute name=\"socket.check_connection\" isParam=\"true\">false</attribute>" +
             "<attribute name=\"timeout\" isParam=\"true\">0</attribute>" +
-            "<attribute name=\"serverBindAddress\">${jboss.bind.address}</attribute>" +
+            "<attribute name=\"serverBindAddress\">localhost</attribute>" +
             "<attribute name=\"serverBindPort\">" + port  +"</attribute>" +
             "<attribute name=\"leasePeriod\">10000</attribute>" +
             "<attribute name=\"clientSocketClass\" isParam=\"true\">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute>" +

Modified: trunk/tests/src/org/jboss/test/thirdparty/remoting/CallbackServerTimeoutTest.java
===================================================================
--- trunk/tests/src/org/jboss/test/thirdparty/remoting/CallbackServerTimeoutTest.java	2007-05-29 18:30:57 UTC (rev 2738)
+++ trunk/tests/src/org/jboss/test/thirdparty/remoting/CallbackServerTimeoutTest.java	2007-05-29 22:03:32 UTC (rev 2739)
@@ -6,23 +6,25 @@
  */
 package org.jboss.test.thirdparty.remoting;
 
-import org.jboss.test.messaging.MessagingTestCase;
-import org.jboss.test.messaging.tools.ServerManagement;
-import org.jboss.test.messaging.tools.jmx.ServiceContainer;
-import org.jboss.test.messaging.tools.jmx.ServiceAttributeOverrides;
-import org.jboss.test.thirdparty.remoting.util.RemotingTestSubsystemService;
-import org.jboss.test.thirdparty.remoting.util.OnewayCallbackTrigger;
+import javax.management.ObjectName;
+
+import org.jboss.jms.client.remoting.JMSRemotingConnection;
+import org.jboss.jms.wireformat.JMSWireFormat;
 import org.jboss.logging.Logger;
+import org.jboss.remoting.Client;
 import org.jboss.remoting.InvokerLocator;
-import org.jboss.remoting.Client;
 import org.jboss.remoting.ServerInvoker;
 import org.jboss.remoting.callback.Callback;
+import org.jboss.remoting.callback.HandleCallbackException;
 import org.jboss.remoting.callback.InvokerCallbackHandler;
-import org.jboss.remoting.callback.HandleCallbackException;
-import org.jboss.jms.client.remoting.JMSRemotingConnection;
+import org.jboss.remoting.marshal.MarshalFactory;
+import org.jboss.test.messaging.MessagingTestCase;
+import org.jboss.test.messaging.tools.ServerManagement;
+import org.jboss.test.messaging.tools.jmx.ServiceAttributeOverrides;
+import org.jboss.test.messaging.tools.jmx.ServiceContainer;
+import org.jboss.test.thirdparty.remoting.util.OnewayCallbackTrigger;
+import org.jboss.test.thirdparty.remoting.util.RemotingTestSubsystemService;
 
-import javax.management.ObjectName;
-
 import EDU.oswego.cs.dl.util.concurrent.Channel;
 import EDU.oswego.cs.dl.util.concurrent.LinkedQueue;
 
@@ -211,6 +213,11 @@
       ServiceAttributeOverrides sao = new ServiceAttributeOverrides();
       sao.put(ServiceContainer.REMOTING_OBJECT_NAME,
               ServiceContainer.DO_NOT_USE_MESSAGING_MARSHALLERS, Boolean.TRUE);
+      
+      
+      JMSWireFormat wf = new JMSWireFormat();
+      
+      MarshalFactory.addMarshaller("jms", wf, wf);      
 
       ServerManagement.start(0, "remoting", sao, true, false);
 




More information about the jboss-cvs-commits mailing list