Hi Baptise,
On Fri, Feb 8, 2019 at 6:10 PM Baptiste wrote:
>
>
> On Fri, Feb 8, 2019 at 6:09 AM Igor Cicimov <
> ig...@encompasscorporation.com> wrote:
>
>> On Fri, Feb 8, 2019 at 2:29 PM Igor Cicimov <
>> ig...@encompasscorporation.com> wrote:
>>
>>> Hi,
>>>
>>> I have a Jetty frontend exposed
On Fri, Feb 8, 2019 at 6:09 AM Igor Cicimov
wrote:
> On Fri, Feb 8, 2019 at 2:29 PM Igor Cicimov <
> ig...@encompasscorporation.com> wrote:
>
>> Hi,
>>
>> I have a Jetty frontend exposed for couple of ActiveMQ servers behind SSL
>> terminating Haproxy-1.8.18. They share same storage and state
On Fri, Feb 8, 2019 at 2:29 PM Igor Cicimov
wrote:
> Hi,
>
> I have a Jetty frontend exposed for couple of ActiveMQ servers behind SSL
> terminating Haproxy-1.8.18. They share same storage and state via lock file
> and there is only one active AMQ at any given time. I'm testing this now
> with
Hi,
I have a Jetty frontend exposed for couple of ActiveMQ servers behind SSL
terminating Haproxy-1.8.18. They share same storage and state via lock file
and there is only one active AMQ at any given time. I'm testing this now
with dynamic backend using Consul DNS resolution:
# dig +short
4 matches
Mail list logo