RE: Explicitly setting the listener port

This is a limitation of 0.7.6 and earlier releases, that has
been fixed in 0.7.7. From the changes report 
(http://openjms.sourceforge.net/changes-report.html#0_7_7):
 

The HTTP and HTTPS connectors now communicate with the OpenJMS server 
via the openjms-tunnel servlet.
 
This replaces the servlets deployed in openjms.war in previous releases. 
The openjms-tunnel servlet supports bidirectional communication. 
This means that the server no longer needs to establish socket connections 
back to clients (which was problematic for hosts with firewalls).

-Tim
 
  _____  

From: openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
[mailto:openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of TJ Greenier
Sent: Friday, 22 July 2005 8:19 AM
To: [email protected]
Subject: [openjms-user] Explicitly setting the listener port



Hi all,

I am wondering if there is a way to set the port number that the message
listener listens on in a pub/sub setup.  I am currently running openJMS
0.7.6.1 and using the http connector.  Everything runs fine when I am
running with in my local area network.  When I try to run my JMS server and
Tomcat server behind a firewall, I can receive the request, but I cannot
publish the messages to the clients because they are running outside the
firewall.  In debugging the issue it seems that the destination client all
listen on different port numbers, which seem to be randomly selected.  Am I
right in this assumption?  What I want to do is force all client listeners
to listen on a specified port, so that I can enable this port on my switch.
Does anybody have an example of specifying the port to listen on.  The error
I am seeing states the JMS is unable to find host on myIP and port (where
the port changes randomly as I re-run my test client).

Thank you for your time in advance.

T.J. Greenier