alibaba/nacos · error · NacosException

400

400

Error message

request id conflict

What it means

Error "request id conflict" thrown in alibaba/nacos.

Source

Thrown at core/src/main/java/com/alibaba/nacos/core/remote/RpcAckCallbackSynchronizer.java:106

     * @param requestId         requestId
     * @param defaultPushFuture defaultPushFuture
     * @throws NacosException NacosException
     */
    public static void syncCallback(String connectionId, String requestId,
        DefaultRequestFuture defaultPushFuture)
        throws NacosException {
        
        Map<String, DefaultRequestFuture> stringDefaultPushFutureMap =
            initContextIfNecessary(connectionId);
        
        if (!stringDefaultPushFutureMap.containsKey(requestId)) {
            DefaultRequestFuture pushCallBackPrev = stringDefaultPushFutureMap
                .putIfAbsent(requestId, defaultPushFuture);
            if (pushCallBackPrev == null) {
                return;
            }
        }
        throw new NacosException(NacosException.INVALID_PARAM, "request id conflict");
        
    }
    
    /**
     * clear context of connectionId.
     *
     * @param connectionId connectionId
     */
    public static void clearContext(String connectionId) {
        CALLBACK_CONTEXT.remove(connectionId);
    }
    
    /**
     * init context of connectionId if necessary.
     *
     * @param connectionId connectionId
     */
    public static Map<String, DefaultRequestFuture> initContextIfNecessary(String connectionId) {

View on GitHub (pinned to 9b989acdf1)

Solutions

1. Re-read the latest state and retry the operation with the fresh version/md5.

When it happens

Trigger: Thrown at core/src/main/java/com/alibaba/nacos/core/remote/RpcAckCallbackSynchronizer.java:106 when the library encounters an invalid state.

Common situations: Registering an RPC ack callback with an already-used request id.

AI-assisted analysis of alibaba/nacos@9b989acdf1 (2026-08-14). Data as JSON: /api/errors/77b418c11416471f. Report an issue: GitHub.