Hi Scott,
thanks, good point, going to try that and see whats coming out. But my feeling is that there is any internal problem, not an external. The snoop gives you what is coming to and going from the port, right? Is there any option disabling the ping on backend?
------------------------------
Jens Petersen
------------------------------
Original Message:
Sent: Mon January 20, 2025 04:16 PM
From: Scott Exton
Subject: Junction not working when Backend was down and comes back online
Jens,
I can't explain why the junction would never come back. My best suggestion is the next time that you have a server which is in this state, to switch on pdweb.snoop.jct tracing.
Thanks.
Scott A. Exton
Senior Software Engineer
Chief Programmer - IBM Security Verify Access
IBM Master Inventor
Original Message:
Sent: 1/20/2025 3:59:00 PM
From: Jens Petersen
Subject: RE: Junction not working when Backend was down and comes back online
Hello Scott,
thanks for the hints. I'm aware of this points, just the question is why doesn't the junction comes back. I'd working perfect for servers not going down for several hours or even once it's opened and saved again. Guess that just recreates the Jct as I'd do with pdamin. And this behavior is occurs for a few weeks while the issue - server down for a longer period - is same since about 4 years.
------------------------------
Jens Petersen
Original Message:
Sent: Mon January 20, 2025 03:41 PM
From: Scott Exton
Subject: Junction not working when Backend was down and comes back online
Jens,
Generally a junction is marked down when a health check fails. A health check fails if the server cannot be reached, or if certain responses are received from the junctioned server (controlled by the 'ping-XXX' configuration entries and the 'rsp-code-rules' configuration entry within the junction stanza). I would double check your configuration here.
I would also check the WebSEAL log file for any hints as to what is happening. If you have a machine which is in this bad state you could also switch on pdweb.snoop.jct tracing to see exactly what is being sent to, and received from, the junction.
I hope that this helps.
Scott A. Exton
Senior Software Engineer
Chief Programmer - IBM Security Verify Access
IBM Master Inventor
Phone: 61-7-5552-4008
E-mail: scotte@au1.ibm.com
1 Corporate Court
Bundall, QLD 4217
Australia
Original Message:
Sent: 1/20/2025 10:57:00 AM
From: Jens Petersen
Subject: Junction not working when Backend was down and comes back online
Hi Team,
quite some weeks ago we started facing an issue that a junction keeps being down even if the backend is online again. I suspect this happens after a longer period being down. Probably several hours. Our dev team uses junctions to there local dev environments for developing their portal apps against AAC info maps. For this junctions we are facing the problems. Open the Jct and save ist solves the issue but causes a lot of support. It may be in conjunction with the 10.0.8 update, but not sure it is.
Any hint welcome :D
------------------------------
Jens Petersen
------------------------------