-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SEP debugger - communication failure when trying to add a SEP #2309
Comments
This may be the same issue as #2247 ? |
@heymchri Please include the contents of the following files for further diagnosis:
Please note that the second file (.log) is a hidden file. We need to use "ls -a" to show the file in Unix file system. |
@mkwan01 Not sure what changed now, but in any case, as I was testing CA signed vs. internal certs, I managed to get the CA cert installed without the 'Self signed certificate in certificate chain' error. When setting the SEP (with the CA signed cert in place), I get the following error message: Log files show the following: .log:
DebugService_log.txt:
|
Also note that regular 'Debug as Batch' debugging works OK with this same CA signed cert. |
@heymchri The NPE at DAPSession.getVersionJSON() is harmless. The communication dropped message usually indicates a connection drop between the client and host. You can restart the debug service and try to set the SEP again. If you can reproduce the communication dropped issue consistently when setting a SEP, please also include the Debug Adapter Protocol trace from the Debug Console when you set the SEP. |
Hi @mkwan01 the communication drops consistently when setting a SEP. Nothing much is reported in the Debug Console (other than that NPE). I do have Debug Tracing turned on. Where should I see the Debug Adapter Protocol trace? |
@heymchri The text in the video is very small. I can hardly read any text there. I can see that you use the "Create Service Entry Point" toolbar action to create a SEP, but I cannot see the text you entered into the prompt. Please try to use the integrated action from the Object Browser view to set a SEP and report whether this action works for you. |
For the DAP trace, we will try to look for a message like the following:
|
Please remove the password when copying the DAP text and include the other statements after the launch request, so that we can see what happens next. |
Hi @mkwan01 I didn't even see that DAP trace message you pointed me to at all, until I disconnected from the system and reconnected. Even without me setting any kind of SEP at all, so just the mere fact of connecting to my system, spits out the entries shown below in the Debug Console. So to be clear, that's BEFORE I even attempt to set the SEP.
Then, when I set the SEP from the object browser like in your screenshot, it generates the following in the Debug console:
If this doesn't show what you're looking for, maybe a screen share session might be useful? |
When trying to add an SEP, the UI briefly shows it's being added in the list of SEPs but then it is immediately removed.
Error message shown:
EQAVS1010E Communication required by Service Entry Point function dropped. Service Entry Point(s) set by user HEYMCHR on server USALID06.INFOR.COM will be removed.
The Debug Service job is active and stays active throughout this.
I'm using a valid CA signed cert because when using the internally generated one, I get the 'self-signed certificate' error (which I can't figure out either why that's happening as it works just fine on several of our other partitions).
Debug Console shows:
From client: initialize({"clientID":"vscode","clientName":"Visual Studio Code","adapterID":"IBMiDebug","pathFormat":"path","linesStartAt1":true,"columnsStartAt1":true,"supportsVariableType":true,"supportsVariablePaging":true,"supportsRunInTerminalRequest":true,"locale":"en","supportsProgressReporting":true,"supportsInvalidatedEvent":true,"supportsMemoryReferences":true,"supportsArgsCanBeInterpretedByShell":true,"supportsMemoryEvent":true,"supportsStartDebuggingRequest":true,"supportsANSIStyling":true})
To client: {"seq":0,"type":"response","request_seq":1,"command":"initialize","success":true,"body":{"supportsEvaluateForHovers":true,"supportsSetVariable":true,"supportsValueFormattingOptions":true,"supportsModulesRequest":true,"supportTerminateDebuggee":true,"supportsFunctionBreakpoints":true,"supportsConfigurationDoneRequest":true}}
From client: launch({"type":"IBMiDebug","request":"launch","subType":"sep","action":"set","name":"Service Entry Point","user":"HEYMCHR","password":"xxxxxx","host":"USALID06.INFOR.COM","port":8005,"sepDaemonPort":8008,"secure":true,"ignoreCertificateErrors":false,"library":"HEYMCHR","program":"CHGDECFMT","programType":"*PGM","module":"*ALL","procedure":"*ALL","trace":true,"workbenchSettings":{"updateProductionFiles":false,"enableDebugTracing":false},"__sessionId":"7a7e14fd-214d-4c9d-9bbe-0d828908c398"})
To client: {"type":"event","seq":2,"event":"initialized"}
From client: setFunctionBreakpoints({"breakpoints":[]})
To client: {"type":"response","seq":0,"request_seq":3,"success":true,"command":"setFunctionBreakpoints","body":{"breakpoints":[]}}
From client: configurationDone(undefined)
To client: {"type":"response","seq":0,"request_seq":4,"success":true,"command":"configurationDone"}
From client: threads(undefined)
To client: {"type":"response","seq":0,"request_seq":5,"success":true,"command":"threads","body":{"threads":[]}}
To client: {"type":"event","seq":7,"event":"terminated"}
To client: {"type":"response","seq":0,"request_seq":2,"success":true,"command":"launch"}
To client: {"type":"response","seq":0,"request_seq":4,"success":false,"command":"configurationDone","body":{"error":{"id":"8999","format":"java.lang.NullPointerException\n\tat com.ibm.debug.pdt.daas.internal.dap.DAPSession.getVersionJSON(DAPSession.java:439)\n\tat com.ibm.debug.pdt.daas.internal.dap.events.DAPEvent.getEvent(DAPEvent.java:117)\n\tat com.ibm.debug.pdt.daas.internal.dap.requests.DAPConfigurationDoneRequest.generateEvents(DAPConfigurationDoneRequest.java:123)\n\tat com.ibm.debug.pdt.daas.internal.dap.requests.DAPRequest.process(DAPRequest.java:139)\n\tat com.ibm.debug.pdt.daas.internal.dap.requests.DAPRequest.process(DAPRequest.java:97)\n\tat com.ibm.debug.pdt.daas.internal.dap.DAPRequestProcessor$1.run(DAPRequestProcessor.java:119)\n\tat org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)\n"}}}
From client: disconnect({"restart":false,"terminateDebuggee":false})
Active extensions
Remote system
Enabled features
Shell env
Variants
Errors
The text was updated successfully, but these errors were encountered: