Sorry, I should be more clear, I had a typo.

   1. First Chrome Browser:
   Connect to the connection group. (works Linux s1 establishes a
   connection)
   2. Second Chrome Incognito Browser:
   Connects to the connection group. (works Linux s2 est conn)
   3. Disconnect and log out of Guacamole Tomcat instance on Second Chrome
   Incognito Browser (works)
   4. Disconnect from Linux s1 on first Chrome Browser (works)
   Still connected to Guacamole Tomcat Front End
   5. Second Chrome Incognito Browser:
   *Authenticates and logs back into Guacamole Tomcat Front end*
   Connects to the connection group. *(works Linux s1 est conn)*
   6. First Chrome Browser (still connected to Tomcat frontend):
   Connect to the connection group. (Connection Error: This connection is
   currently in use, and concurrent access to this connection is not allowed.
   Please try again later.)


Michael Barkdoll


On Fri, May 3, 2019 at 10:15 AM Michael Barkdoll <[email protected]>
wrote:

> First, thank you for a wonderful Apache Project!
>
> Here is what I'm facing:
>
> I have a Balancing type Connection Group with two Linux Ubuntu 19.04 XRDP
> servers with XFCE running and I have some hiccups that I'm trying to iron
> out.
>
> E.g.,
>
>    1. First Chrome Browser:
>    Connect to the connection group. (works Linux s1 establishes a
>    connection)
>    2. Second Chrome Incognito Browser:
>    Connects to the connection group. (works Linux s2 est conn)
>    3. Disconnect and log out of Second Chrome Incognito Browser (works)
>    4. Disconnect from first Chrome Browser (works)
>    5. Second Chrome Incognito Browser:
>    Connects to the connection group. (works Linux s2 est conn)
>    6. First Chrome Browser:
>    Connect to the connection group. (Connection Error: This connection is
>    currently in use, and concurrent access to this connection is not allowed.
>    Please try again later.)
>
>
> [image: image.png]
>
> Screenshot from admin showing only one session is in use from the
> connection group.
>
> [image: image.png]
> Refreshing first Chrome browser does update the connection string:
> https://host/guacamole/#/client/MQBnAG15c3Fs
> <https://localhost/guacamole/#/client/MQBnAG15c3Fs>
>
> However, I can see that both web browsers have this connection string for
> the connection group.
>
> Michael Barkdoll
>

Reply via email to