- Re: BisocketServerInvoker and random port issue 2007-08-09 - By ron.sigal@(protected)
Back
anonymous wrote : Can anyone please clarify if there is any way to configure
the BisocketServerInvoker to not use a random port when starting the secondary
server?
There is a JIRA issue for this feature: JBREM-749 (See http://REM-749.ora-code.com) "BisocketServerInvoker: Make
configurable the address and port of secondary server socket". It is scheduled
for the next Remoting release.
anonymous wrote : If this is true, am I correct in assuming that it is
impossible to operate an application (jboss-4 (See http://oss-4.ora-code.com).2.0.GA + jboss-messaging-1 (See http://ing-1.ora-code.com).3.0.GA
) that utilizes it behind a firewall unless all ports are open? If this is true,
was there a reason for it?
Until the fix for JBREM-749 (See http://REM-749.ora-code.com) is available, you're correct. The motivation for
the bisocket transport was to support *clients* behind a firewall.
anonymous wrote : Is the thought here to use the multiplex transport instead of
the bisocket? Would there be any performance impacts by using the different
transport? I am assuming bisocket would give the best performance, is that
correct?
I'm recommending, whenever possible, bisocket over multiplex. It's faster (we
don't have any statistics yet, but I'd guess at least 50% faster). It's also,
in my opinion, more reliable. It's used by JBossMessaging, which means it's
being used in production in many places. It's relatively new, and we're still
shaking out some wrinkles, but I'm not aware of any comparable use of multiplex
.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic
&p=4072724#4072724
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode
=reply&p=4072724
__ ____ ____ ____ ____ ____ ____ ____ ____ ____
jboss-user mailing list
jboss-user@(protected)
https://lists.jboss.org/mailman/listinfo/jboss-user
|
|
