Describe the bug
RPS crashes with an uncaught exception during remote activation when using rpc-go (v3.0.0-beta.40) in Cloud Deployment v2 scenarios.
Steps to reproduce
- Deploy Cloud Deployment v2 ( tag: v2.36.0) stack with RPS version in v2.39.2
- Run activation from rpc-go:
- sudo ./rpc activate -u wss://10.49.97.55/activate --profile dllprofile --skip-cert-check
- rpc activation will fail, and we can see the error in docker logs of RPS.
Expected behavior
RPS should handle WSMAN timeout/empty response paths gracefully. Activation should fail with a controlled error response (no process crash). No uncaught exception in activation state machine.
Screenshots
RPS:

RPC-GO:

AMT Version
16.1.25
Configuration Mode
CCM
Operating System
Linux
AMT Device Information
No response
Service Deployment Information
No response
Additional context
- rpc-go: v3.0.0-beta.42 binaries - Works with v2.52.2
- RPS versions tested: v2.39.1, v2.39.2
Describe the bug
RPS crashes with an uncaught exception during remote activation when using rpc-go (v3.0.0-beta.40) in Cloud Deployment v2 scenarios.
Steps to reproduce
Expected behavior
RPS should handle WSMAN timeout/empty response paths gracefully. Activation should fail with a controlled error response (no process crash). No uncaught exception in activation state machine.
Screenshots
RPS:

RPC-GO:

AMT Version
16.1.25
Configuration Mode
CCM
Operating System
Linux
AMT Device Information
No response
Service Deployment Information
No response
Additional context