Unable to use SEP - Debugger 3.0.0 - Sporadic Issue

[jman116]

Hi,

Yesterday I was working with a new team member and attempted to show them how to use Code for i to attach a SEP to their immediate program and step through it to debug it. The SEP reported that it attached, but calling the program did not trigger it. Didn't receive any errors through the console, and the log was clear except for "SSLException thrown when reading SEP daemon protocol message".

I recreated the issue today, restarted the debug service and that did not fix the issue. It wasn't until I used the "debug as batch" on a program that I had set a SEP for already that the SEP started to trigger. From then on, it has been triggering on programs as expected. I've had trace logging enabled both client and server side, but there wasn't anything of note that I could find to highlight a possible issue.

Only thing that I can think of is our debug server is ran under a different user profile than the debug service, and that our debug server is shutdown every night.

[jman116]

I'm pretty sure this is because our debug server is shut down every night, but the debug service is left running. Seems like the debug service can't fully reestablish its connection with the debug server. It doesn't report any errors, though. I think that if the debug server is shut down, the service should probably follow suit or be able to reestablish its connection with the server once it's back up, or at least report that it's having an issue instead of stating that SEPs were added correctly.

We shut the debug server down every night because in the past if a user left job in debug, it could lock files and cause issues with batch, but I think ending QB5SERVER jobs would fix that compared to bringing the hammer down on the debug server.

[mkwan01]

This is a different variation of the issue reported in issue #37.