-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bernd,
On 8/1/17 12:07 PM, Bernd Wahlen wrote:
>> I wonder if the F5 is not happy with the HTTP response status
>> "reason string" being removed:
>>
>> https://bz.apache.org/bugzilla/show_bug.cgi?id=60362
>>
>> What happens if you add the
Hi chris,
Many thanks!
That's the solution.
Bernd
I wonder if the F5 is not happy with the HTTP response status "reason
string" being removed:
https://bz.apache.org/bugzilla/show_bug.cgi?id=60362
What happens if you add the sendReasonPhrase="true" to your
configuration and try again?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bernd,
On 8/1/17 5:43 AM, Bernd Wahlen wrote:
> Hi Peter and thanks for your help.
>
>> From my perspective the Tomcat is working, responding and
>> serving content.
>>
>> That leads to the thought, that the F5 is not evaluating the
>> response
Hi Peter and thanks for your help.
From my perspective the Tomcat is working, responding and serving content.
That leads to the thought, that the F5 is not evaluating the response correctly.
In my opinion you should talk to the admins and ask them why they are not
activating your service.
The
Bernd,
> Am 01.08.2017 um 11:01 schrieb Bernd Wahlen :
>
> Hi M, Peter and Christoph,
>
> >Have you tried taking the affected server out completely from the >farm? In
> >this way, you have 4 tomcats seen by the loadbalancer. Once >you have done
> >the
Hi M, Peter and Christoph,
>Have you tried taking the affected server out completely from the
>farm? In this way, you have 4 tomcats seen by the loadbalancer. Once
>you have done the upgrade, re-register this server with your load
>balancer.
>If not, can the F5 reach your server, can you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bernd,
On 7/31/17 12:59 PM, Bernd Wahlen wrote:
>
> We are running a cluster of 5 tomcats behind a loadbalancer (shared
> big ip f5). Traffic is http, https and websocket. After upgrading
> one of the servers to Tomcat 8.5.16 this server get no
Hi Bernd,
> Am 31.07.2017 um 19:17 schrieb Bernd Wahlen :
>
> Thanks for your help,
>
> what do you mean with take it off the server farms first?
>
> The upgrade process is like this:
> stop tomcat
> change symlink to new version
> start tomcat
>
>
By farms, I am referring to your setup for 5 Tomcats.
Have you tried taking the affected server out completely from the farm? In
this way, you have 4 tomcats seen by the loadbalancer. Once you have done
the upgrade, re-register this server with your load balancer.
Also, have you checked whether
Thanks for your help,
what do you mean with take it off the server farms first?
The upgrade process is like this:
stop tomcat
change symlink to new version
start tomcat
loadbalancer detect that the server is down and routes the traffic
to the other hosts.
This is like we always do since tomcat
When you upgraded the affected tomcat from 8.0.45 to 8.5.16, Did you take
it off the server farms first? Or did you do it without?
Try to remove the affected tomcat off the server farm. Do you upgrade, and
then put it back inside the farm.
Or have you tried this already?
On 31 July 2017 at
11 matches
Mail list logo