[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Incorporating Remoting http transport into Messaging

[ron_sigal]

Here's an update on the current state of the http experimental branch.

With a couple of minor exceptions, the remote tests, in-vm tests, crash tests, and stress tests are passing for both socket and http transports.  I haven't tried the smoke test yet.

1. Remote tests:
   (a) socket:  all pass
   (b) http:    all pass
   
2. In-vm tests:
   (a) socket: 1 failure: a ClassCastException in org.jboss.test.messaging.core.plugin.postoffice.cluster.DefaultClusteredPostOfficeTest
   (b) http:   1 failure:  same
   
3. Crash tests:
   (a) socket: all pass
   (b) http:   1 failure: org.jboss.test.messaging.jms.crash.CallbackFailureTest.testCallbackFailure() fails.  This test disables the mechanism which detects that a connection has failed and then tests that a failed message delivery (in ServerConsumerEndpoint.Deliverer) would lead to the same result, i.e., cleaning up the connection's resources.  The problem is that when the http transport is being used, there is no client invocation on the server side - messages are pulled from the server to the client.  I'm not sure what to do about this failure, but then, I don't really understand the test, since normally the connection listener would not be disabled.
   
4. Stress tests:
   (a) socket: all pass
   (b) http:   all pass
   
There are some cases in which error messages appear in messaging-tests-remote.trace.log, even though the tests pass, but I have verified that they also occurred in the http experimental branch immediately after it was forked.  Perhaps they have already been fixed on HEAD.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985687#3985687

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985687