EntranceNode和DefaultNode构建的invocation tree 会一直存在内存中，因此如果资源大于默认2000，将无法再进行限流。

这一块虽然没有那么重要，但是可以采用这种优化

• 当数额未超过MAX_CONTEXT_NAME_SIZE，正常处理
• 当数额超过MAX_CONTEXT_NAME_SIZE，清理 intervalInMs 内无记录的node让出空间。

另外MAX_CONTEXT_NAME_SIZE也可以考虑提供出来供使用者调节。

这样处理在正常情况下应该对性能不会有什么影响，因为一般没有那么多资源限流。而如果真正遇到了需要限流的资源太多，也能够进行处理，而不是直接报错。不过那种场景可能会导致频繁new EntranceNode。而这也可以通过调节MAX_CONTEXT_NAME_SIZE来达到平衡。

_Originally p

Currently this will work:

"method": [
        {
            "name": "send-invalid-request",
            "type": "action",
            "provider": {
                "type": "process",
                "path": "echo",
                "arguments": "${request_file}"
            }
        }
    ]

But this won't:

"method": [
        {
            "name": "send-invalid-

Implement Message.InspectMsg and suitable overrides. This function should be invoked when a message is sent, but only when a debug flag is enabled in a lab load. Its purpose is to verify that the message

• belongs to a valid protocol
• matches its PSM's protocol (if sent by a PSM)
• has a valid signal for its protocol
• contains all parameters that are mandatory for its signal
• contains

Although it's not a high priority, we could get a more fancy and modern wheel.