RE: Open JMS TCP and HTTP connectors

See inline. 

> From: [email protected]
> 
> I have been making some performance tests of OpenJMS 0.7.7, 
> comparing HTTP and TCP transport and have found that TCP is 
> about a factor 2 faster than HTTP ( Tomcat is used in HTTP case).
> I have also found that even when using TCP transport, no 
> backward connections, from server to client, appear, as in 
> the case of HTTP tunneling.

Correct. 

> I have also found some problems with HTTP connections. It 
> appears that the connections remain open after the client 
> program has finished. This does not occur when using TCP connections.

Shouldn't do. Connections will remain open while there are references
to them. You can clean up unused connections by running System.gc().

> 
> As far as I understand, the TCP connector could be run on port 80.

You could, except that port 80 is traditionally reserved for HTTP.

> So my question is, Is there any advantage of using HTTP 
> transport instead of TCP?

You would use HTTP if:
. the server is behind a firewall
. you can't open up a port (e.g, 3035) for the TCP connector
. port 80 is open and has a webserver listening on it

> I could run OpenJMS with TCP connector running on port 80, 
> and this would avoid the intermediate Tomcat and increase 
> performance, am I right?

Yes.



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf