Hi Markus,
On 09/30/2014 12:21 AM, Markus Karg wrote:
>
> Amy,
>
> just for better understanding of your intention one question: That
> trial “should” work because the GF team actually wants a JMS hostname
> of 0.0.0.0 to work but rates it to be a bug that it apparently does
> not when done using the admin GUI, or that trial “should” work because
> GF team knows that this feature is indeed not existing but is aware of
> the fact that it though does work when issued your way?
>
The intention to file a jira for this is to track the issue that you
reported so that the engineer who has been taking care of GlassFish JMS
module when comes back to work can evaluate it. You should put your
setup/environment information and what worked/not worked for you to the
jira so that they can be useful for evaluation.
Thanks,
amy
> Thanks
>
> -Markus
>
> *Von:*Amy Kang [mailto:amy.kang_at_oracle.com]
> *Gesendet:* Freitag, 26. September 2014 20:15
> *An:* users_at_glassfish.java.net
> *Betreff:* [gf-users] Re: JMS host with multiple IP adresses
>
> You can try to set the broker's binding address by the start-args
> attribute in jms-service element of domain.xml
> start-args="-Dimq.hostname=0.0.0.0"
>
> For the GlassFish server JMS host setting
> >whether 0.0.0.0 not working is a bug, or whether having only single IP is a forgotten feature
>
> if you have followed the instruction from the following GlassFish
> server v3 release note and it doesn't work, please file a GLASSFISH jira
> http://docs.oracle.com/cd/E19226-01/820-7688/gjktp/index.html
>
> amy
>
> On 09/26/2014 06:22 AM, Markus Karg wrote:
>
> The client is already happy so far – I bound JMS host to a single
> IP and set up a gateway route to serve the second LAN…
>
> The problem with the code is that it cannot answer whether 0.0.0.0
> not working is a bug, or whether having only single IP is a
> forgotten feature… ;-)
>
> Have a nice weekend
>
> -Markus
>
> *Von:*Steven Siebert [mailto:smsiebe_at_gmail.com]
> *Gesendet:* Freitag, 26. September 2014 15:04
> *An:* users_at_glassfish.java.net <mailto:users_at_glassfish.java.net>
> *Betreff:* [gf-users] Re: JMS host with multiple IP adresses
>
> Always something. =) OK, no additional application software...can
> you perhaps leverage a OS port forwarding feature (ie iptables)?
> I assume you have to open a port for your JMS anyway...I realize
> you're looking for an official comment from the GF team, which I
> can't provide...just trying to get you past your problem so you
> have a happy client =).
>
> The GF code is available, too, and really not very daunting
> (fairly intuitive project structure)...I've had to dig a couple
> times to get answers.
>
> S
>
> On Fri, Sep 26, 2014 at 7:41 AM, Markus Karg <karg_at_quipsy.de
> <mailto:karg_at_quipsy.de>> wrote:
>
> Steven,
>
> sounds interesting, but is not a real solution for us. We must not
> use other software besides GF.
>
> It would be really nice if the GF team could post some official
> opinion whether 0.0.0.0 MUST work (= bug in GF 3.1) or GF 3.1
> simply DOESN’T SUPPORT multiple JMS host IPs. J
>
> Thanks!
>
> -Markus
>
> *Von:*Steven Siebert [mailto:smsiebe_at_gmail.com
> <mailto:smsiebe_at_gmail.com>]
> *Gesendet:* Freitag, 26. September 2014 13:19
>
>
> *An:* users_at_glassfish.java.net <mailto:users_at_glassfish.java.net>
> *Betreff:* [gf-users] Re: JMS host with multiple IP adresses
>
> Not sure if this is an option for you..
>
> I have a similar scenario, multiple IPs, must only bind to two
> (one private, only one of the public) for security requirements.
> I've have several GF 3 and 4 servers running successfully by using
> a JMS server outside GF (ie ActiveMQ) (can even run on the same
> server if you wish...even on the same port if you configure GF to
> disable its own JMS service) and use a RAR to access the
> resource. This works simply by avoiding the problem - ActiveMQ
> supports binding to a any number of IPs by defining one transport
> connector per socket/protocol. On the client side, connection
> information from GF back to ActiveMQ is defined in the RAR
> configuration using the transport url format of ActiveMQ, which
> gives you just as much freedom to define multiple static or
> failover socket/protocols. This required no code changes (I
> programmed to the specification) - only some administrative work.
>
> On Fri, Sep 26, 2014 at 4:17 AM, Markus Karg <karg_at_quipsy.de
> <mailto:karg_at_quipsy.de>> wrote:
>
> I tried this in GF 3.1 but it does not work! 0.0.0.0 results in
> the fact that a remote client tries to connect to “0.0.0.0” which
> obviously does not work. Maybe this is a bug in 3.1, I don’t know.
>
> *Von:*Amy Kang [mailto:amy.kang_at_oracle.com
> <mailto:amy.kang_at_oracle.com>]
> *Gesendet:* Freitag, 26. September 2014 09:15
> *An:* users_at_glassfish.java.net <mailto:users_at_glassfish.java.net>
> *Betreff:* [gf-users] Re: JMS host with multiple IP adresses
>
> In GlassFish server, use 0.0.0.0 for all interfaces, see
> following GlassFish server docs
> http://docs.oracle.com/cd/E19226-01/820-7688/gjktp/index.html
> http://docs.oracle.com/cd/E19798-01/821-1841/gjsdi/index.html
>
> amy
>
> On 09/25/2014 11:37 PM, Markus Karg wrote:
>
> That sounds great! It would be even cooler if the GF manual
> would say that somewhere… J
>
> *Von:*Amy Kang [mailto:amy.kang_at_oracle.com]
> *Gesendet:* Freitag, 26. September 2014 07:23
> *An:* users_at_glassfish.java.net <mailto:users_at_glassfish.java.net>
> *Betreff:* [gf-users] Re: JMS host with multiple IP adresses
>
> The default-jms-host in jms-service is passed to JMSRA to
> broker as broker's imq.hostname property which can be "*" (all
> interfaces on the host) or a specific hostname or IP address
> http://docs.oracle.com/cd/E18930_01/html/821-2438/aeont.html#gbnni
>
> amy
>
> On 09/24/2014 01:13 AM, Markus Karg wrote:
>
> I have set up GlassFish 3.x lots of times, but today I got
> stuck… My current customer’s server has several IP
> adresses. The JMS default host binds to MYHOST:7676, which
> effectively leads to the fact that it is bound to ONE IP
> only – but I need to bind it to SEVERAL. If I understand
> correctly, then 0.0.0.0 should bind to ALL, right? Is
> there a way to provide only a SET of IPs?
>