4-16 - Service is closed

4-16 - Service is closed

Possible Causes

Continuing to call org.apache.dubbo.rpc.protocol.tri.service.TriHealthImpl#enterTerminalState or org.apache.dubbo.rpc.protocol.ReferenceCountInvokerWrapper#invoke in an erroneous state, while the call is already in terminal or destroy state.

Troubleshooting and Resolution Steps

Multiple calls to the above methods will trigger reminders. Generally used only for unit testing.

Feedback

Was this page helpful?

Yes No

Last modified September 30, 2024: Update & Translate Overview Docs (#3040) (d37ebceaea7)