Hi,
We're observing a random issue with some of our customers, after
doing an upgrade of the Jetty from 9.4.11 to 9.4.44. We're starting Jetty
programmatically in a Zulu JRE 8 runtime.
We're initializing the SSLContextFactory as follows
Hi,
On Fri, Feb 17, 2023 at 3:38 PM Srijith Kochunni via jetty-users
wrote:
[snip]
>javax.net.ssl|SEVERE|08 1C|qtp1363141203-2076|2023-02-07
> 12:35:40.763 EST|TransportContext.java:340|Fatal (HANDSHAKE_FAILURE): no
> cipher suites in common (
[snip]
> The problem seems
The ".nodeX" suffix on the the session id can be used by load balancers to
direct traffic to particular nodes in the cluster, ie ensure session
stickiness.
If a session lands on a different node other than the one it originated on
(eg that node failed, or the load balancer is non sticky) then the
Looking at my session ID in my browser's Network tools, I see that
JSESSION=node01.node0
When I do session.getid() inside the running code, I see node01
(without the trailing ".node0").
It's a minor triviality, but can anyone explain why they are different?
Thanks,
--
John English
