Hello.
Since recently, stored processes periodically stop working: they are endlessly in progress.
We use SAS 9.4M3 and a technical user from SAS General Servers for shared execution of stored processes on the Stored Process Server.
What I see in the Stored Process Server logs:
2022-02-08T08:44:39,009 INFO [00408867] :stp_tech_user@domain - New out call client connection (65) for user john.doe@company.com. Encryption level is Credentials using encryption algorithm SASPROPRIETARY. Peer IP address and port are [::1]:8561.
2022-02-08T08:44:39,011 INFO [00408867] :john.doe@company.com - New client connection (64) accepted from server port 8611 for SAS token user john.doe@company.com. Encryption level is Credentials using encryption algorithm SASProprietary. Peer IP address and port are [::ffff:10.105.166.74]:60332.
2022-02-08T08:44:39,368 INFO [00408886] 64:john.doe@company.com - STP: 31: Creating New Context, sessionID=
No entries until the manual cancellation by user:
2022-02-08T08:49:46,205 INFO [00408875] 64:stp_tech_user@domain - A connection reset indicates the peer has closed their connection to this session. This session will remove the peer from its set of active peers.
2022-02-08T08:49:46,205 INFO [00408875] 64:stp_tech_user@domain - The Bridge Protocol Engine Socket Access Method was unable to read peer data.
How it should be:
2022-02-08T10:38:06,229 INFO [00016162] :stp_tech_user@domain - New out call client connection (17) for user john.doe@company.com. Encryption level is Credentials using encryption algorithm SASPROPRIETARY. Peer IP address and port are [::1]:8561.
2022-02-08T10:38:06,230 INFO [00016162] :john.doe@company.com - New client connection (16) accepted from server port 8611 for SAS token user john.doe@company.com. Encryption level is Credentials using encryption algorithm SASProprietary. Peer IP address and port are [::ffff:10.105.166.74]:63498.
2022-02-08T10:38:06,841 INFO [00016180] 16:john.doe@company.com - STP: 7: Creating New Context, sessionID=
2022-02-08T10:38:06,908 INFO [00016180] 16:john.doe@company.com - STP: Sending cost=101 to Load Balancer. Context Cost=100 STP Session Cost=1
2022-02-08T10:38:07,767 INFO [00016331] 16:john.doe@company.com - STP: 7: Executing !STP_PATH Some_stp.sas
2022-02-08T10:38:07,774 INFO [00000003] :stp_tech_user@domain - [00000007] STPXUTL Execute using file path: path\to\stored processes\Some_stp.sas
2022-02-08T10:38:14,078 INFO [00016331] 16:john.doe@company.com - STP: 7: Execution Complete. Status=0
2022-02-08T10:38:15,756 INFO [00020100] 16:john.doe@company.com - STP: 7: Context Close
2022-02-08T10:38:15,796 INFO [00020100] 16:john.doe@company.com - STP: Sending cost=0 to Load Balancer. Context Cost=0 STP Session Cost=0
2022-02-08T10:38:17,251 INFO [00020119] 16:stp_tech_user@domain - Client connection 16 for user john.doe@company.com closed.
2022-02-08T10:38:17,254 INFO [00020119] 16:stp_tech_user@domain - Client connection 17 for user john.doe@company.com closed.
It seems, STP execution stops on Load Balancer call.
The problem has been periodically temporarily solved by server reboot, but no permanent solution was made.
No configuration changes were made since deployment: it has worked well for 7 years.
Kindly ask you to help with this problem.
