Hi Kirill,
Once a web socket is initiated via WebSEAL it is really only passing packets so I'm not sure you'll see anything more in the websocket trace. Do you see messages when the socket connection is initiated? If not, what is the command you are using to set up the trace - perhaps you need to use a higher trace level (9 is max).
An alternative way to monitor the web socket would be to capture a packet trace on WebSEAL. This can be enabled from the LMI. The captured trace can be read by WireShark or similar and should show you the TCP messages to indicate who terminates the connection.
Jon.
------------------------------
Jon Harry
Consulting IT Security Specialist
IBM
------------------------------
Original Message:
Sent: Wed August 18, 2021 11:08 AM
From: Kirill N
Subject: Problem with WebSocket Debug
Hello!
I have WebSeal based on Appliance 9.0.7.0 with configured WebSocket:
[websocket]
max-worker-threads = 1000
idle-worker-threads = 0
jct-read-inactive-timeout = 1800
clt-read-inactive-timeout = 1800
jct-write-blocked-timeout = 20
clt-write-blocked-timeout = 20
WebSocket connection closes and I want to know, who is initiate the close. But when I start pdweb.websocket - there is nothing happened. Is there any instrunction how can I do this?
Thanks!
------------------------------
Kirill N
------------------------------