-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
[NodeJS Agent] When oap-server had stoped, java invokes node, the node app will raise "TypeError" and exit. #7505
Comments
|
I have the same problem |
|
Same problem, hope it can be fixed quickly. |
|
@xinnj @820465323 If no one intends to fix it on their own, everyone has to wait. This is how an open-source project works. |
|
I reproduce this issue use :
And I not start OAP. The request message that Httpclient send to node server: Because if OAP is not working, Java agent will create a |
|
Why is this header wrong? I am not sure of your conclusion. |
|
You are right , I'm not sure header is wrong 。
I will read the java agent code in depth |
|
No one could guarantee sw8 is not null. The agent should tolerant this case. |
|
I see , sometimes GRPCChannelStatus (ContextManagerExtendService#status)is not reliable. |
|
Yes, if it requires sw8, then this become a security attach point if this service is exposed. |
Let me investigate this issue and try to fix it as soon as possible. |
|
Case 1 , sw8 header is right , working correctly: Case 2 , sw8 header exist , but value is null , working error : |
|
@ypg521 If you could submit a fix quickly referring Java's validation implementations, we could review that. |
|
Announced CVE-2022-36127 and 0.5.1 fixed this. |

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

Please answer these questions before submitting your issue.
Question
What do you want to know?
When the node agent cannot connect to the server after the server is stopped, the default value is null。Want to confirm whether it can be solved。
Bug
Which version of SkyWalking, OS, and JRE?
Which company or project?
What happened?
If possible, provide a way to reproduce the error. e.g. demo application, component version.
env: k8s for aliyun cloud
docker-engine: 1.18.8-aliyun.1
oap-server: skywalking-oap-server:8.6.0-es7
java: 8.6.0
node: skywalking-backend-js: master
ERROR
Requirement or improvement
Because there is no exception when Java calls Java after the server stops, but when node is called, node throws an exception and exits, affecting the operation of the application. Hope to improve.
The text was updated successfully, but these errors were encountered: