Sam,
Thank you a lot!
This is exactly what I was looking for. How did you found out?
I think that random callback port assignment is an ill-designed way to
do things, usually used only by M$ protocols. Having it on a fixed port
allows proper firewall configuration, plus the use of a ssh tunnel to
reach internal services (as things like CORBA have no support for proxy
servers).
# Connection Service Specific Settings
#
*# imq.<service_name>.<protocol_name>.port*
Thank you again.
Piero Filippin
glassfish_at_javadesktop.org wrote:
> Hello Piero,
>
> I encountered the same issue before. Obviously the firewall needs to be configured to allow the appropriate ports to be accessible first off. The second part for the random port number is what I experienced as well.
>
> There is probably a parameter you can pass to the vm to configure this but what I ended up doing was configuring the options in the domains/<yourdomain>/imq/instances/imqbroker/props/config.properties file. The jms.tcp.port kept changing on me randomly so at the end of this file I added the property imq.jms.tcp.port=38669. After a restart it locked this service/protocal to port 38669.
>
> Hope this helps.
>
> S.D.
> [Message sent by forum member 'samdoyle' (samdoyle)]
>
> http://forums.java.net/jive/thread.jspa?messageID=239237
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
>