Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] Re: ecf-dev Digest, Vol 45, Issue 35 
Hi Roshan,
The assertion you are getting below indicates that the remote service proxy is never getting created and locally registered. This seems likely to me because of some issue with discovery...i.e. since the service is never discovered, a proxy is never created/registered.
With these tests in my own environment, I've been using zeroconf-based discovery (using the jmdns discovery provider). Of course all participating processes are on same lan (actually same host machine for these tests anyway).
There is tracing for both the discovery and distribution components of RFC119, and perhaps you could turn these on and report what they show in your environment. Go to the Debug Configuration for the org.eclipse.ecf.tests.provider.jms.activemq Junit plugin test launch config, go to the tracing tab, and select all the available tracing for org.eclipse.ecf.osgi.services.discovery and org.eclipse.ecf.osgi.services.distribution. Run the tests again and report what it puts out in the console when you run these tests. 

Thanks,

Scott


roshanjose@xxxxxxxxx wrote:

Hi Scott,
Thank you for adding the the test case so fast. I did try it out in my machine and some of the test cases are failing for me. Like I mentioned in my earlier mail, I do see the test creating a server and a client all in a single process. 
With respect to the test cases in
(org.eclipse.ecf.tests.provider.jms.activemq.remoteservice.ActiveMQServiceRegisterTest)
I see my test for testRegisterServer() and testGetExposedServicesFromDistributionProvider() successfully getting executed but the other tests are failing, don’t know the reason all are giving assert failure at these lines below. I am not sure whether the failure happens due to delay/wait time, still trying to see what the problems is. 

// Client - Get service references from service tracker
 ServiceReference [] remoteReferences = st.getServiceReferences();
 assertTrue(remoteReferences != null);
I am executing the test case in junit and the only other process active while running the test is the activemq jms broker for enabling the exampleTopic. I too see the NumberFormatexception in the console like you mentioned in your mail. Will be more than happy to attach a readme.txt once I finish with testing, including all the steps I followed. The error stack for one of the test case is something like this... 

junit.framework.AssertionFailedError
 at junit.framework.Assert.fail(Assert.java:47)
 at junit.framework.Assert.assertTrue(Assert.java:20)
 at junit.framework.Assert.assertTrue(Assert.java:27)
at org.eclipse.ecf.tests.osgi.services.distribution.AbstractServiceRegisterTest.testGetAndUseProxy(AbstractServiceRegisterTest.java:137) 
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
 at java.lang.reflect.Method.invoke(Unknown Source)
 at junit.framework.TestCase.runTest(TestCase.java:164)
 at junit.framework.TestCase.runBare(TestCase.java:130)
 at junit.framework.TestResult$1.protect(TestResult.java:106)
 at junit.framework.TestResult.runProtected(TestResult.java:124)
 at junit.framework.TestResult.run(TestResult.java:109)
 at junit.framework.TestCase.run(TestCase.java:120)
 at junit.framework.TestSuite.runTest(TestSuite.java:230)
 at junit.framework.TestSuite.run(TestSuite.java:225)
at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:62) at org.eclipse.pde.internal.junit.runtime.CoreTestApplication.run(CoreTestApplication.java:23) 
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
 at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:574) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) 
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
 at java.lang.reflect.Method.invoke(Unknown Source)
 at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:556)
 at org.eclipse.equinox.launcher.Main.basicRun(Main.java:511)
 at org.eclipse.equinox.launcher.Main.run(Main.java:1284)
 at org.eclipse.equinox.launcher.Main.main(Main.java:1260)
Once again thank you for all the help and support from you. Regards 
Roshan
--- On *Tue, 5/19/09, ecf-dev-request@xxxxxxxxxxx /<ecf-dev-request@xxxxxxxxxxx>/* wrote: 


    Date: Tue, 19 May 2009 16:35:55 -0700
    From: Scott Lewis <slewis@xxxxxxxxxxxxxxxxx
    <http://us.mc395.mail.yahoo.com/mc/compose?to=slewis@xxxxxxxxxxxxxxxxx>>
    Subject: Re: [ecf-dev] Re: ecf-dev Digest, Vol 45, Issue 35
    To: "Eclipse Communication Framework (ECF) developer mailing list."
        <ecf-dev@xxxxxxxxxxx
    <http://us.mc395.mail.yahoo.com/mc/compose?to=ecf-dev@xxxxxxxxxxx>>
    Message-ID: <4A13425B.9020702@xxxxxxxxxxxxxxxxx
    <http://us.mc395.mail.yahoo.com/mc/compose?to=4A13425B.9020702@xxxxxxxxxxxxxxxxx>>
    Content-Type: text/plain; charset=ISO-8859-1; format=flowed

    Hi Roshan,

    I've created a new test case:

    org.eclipse.ecf.tests.provider.jms.activemq/org.eclipse.ecf.tests.provider.jms.activemq.remoteservice.ActiveMQServiceRegisterTest
That exercises the ActiveMQ pub-sub remote services through RFC 119. With some bug fixes discovered and fixed along the way, the tests in 
    this test class now all pass/work.

    Note that someone/one of us should put together some instructions for

    a) Setting up ActiveMQ broker so that it can be used with this
    test case
    (i.e. add broker topic called 'exampleTopic').
    b) How to run this test case and others

    I will do this asap.  If you are willing/able to do this as well it
    would be appreciated.

    BTW, I found a bug in activemq in the process...during the running of
    these tests ActiveMQ gives a spurious warning with exception trace (a
    NumberFormatException).  I've created the following bug on the
    activemq
bug tracking system for this: https://issues.apache.org/activemq/browse/AMQ-2256 

    When I run the tests with activemq 5.2 I get a number of exception
    and
    stack traces as described in
    https://issues.apache.org/activemq/browse/AMQ-2256.  These do not
    prevent the tests from succeeding, but the console is filled up with
    spurious warnings/stack traces.

    Scott


------------------------------------------------------------------------

_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev

Back to the top