解决Microoft Graph API中获取用户活动时的429限流错误

import com.microsoft.graph.requests.GraphServiceClient;

import com.microsoft.graph.requests.UserActivityRecentCollectionPage;

import com.microsoft.graph.authentication.IAuthenticationProvider; // 假设authProvider已正确初始化

// ... 假设authProvider已通过AAD认证并获取到有效的访问令牌 ...

GraphServiceClient graphClient = GraphServiceClient.builder().authenticationProvider( authProvider ).buildClient();

try {

    // 尝试获取用户近期活动

    UserActivityRecentCollectionPage recent = graphClient.me().activities()

        .recent()

        .buildRequest()

        .get();

    // 处理获取到的活动数据

    System.out.println("成功获取到用户近期活动。");

} catch (Exception e) {

    // 捕获异常，特别是429错误

    if (e.getMessage() != null && e.getMessage().contains("429 Too Many Requests")) {

        System.err.println("错误：触发了429限流。请稍后重试或优化请求策略。");

        // 进一步解析错误信息 e.g., {"Message":"Request limit exceeded for Authentication Failure"}

        System.err.println("详细错误信息: " + e.getMessage());

    } else {

        System.err.println("获取用户活动时发生未知错误：" + e.getMessage());

    }

}

public UserActivityRecentCollectionPage getRecentUserActivitiesWithRetry(GraphServiceClient graphClient, int maxRetries) throws Exception {

    int retryCount = 0;

    long sleepTimeMs = 1000; // 初始等待时间1秒

    while (retryCount < maxRetries) {

        try {

            UserActivityRecentCollectionPage recent = graphClient.me().activities()

                .recent()

                .buildRequest()

                .get();

            return recent; // 成功，返回数据

        } catch (Exception e) {

            if (e.getMessage() != null && e.getMessage().contains("429 Too Many Requests")) {

                System.out.println("收到429错误，正在重试（" + (retryCount + 1) + "/" + maxRetries + "）...");

                // 尝试从响应头获取Retry-After

                // 注意：这里需要更复杂的HTTP响应解析，Graph SDK可能需要定制拦截器或异常处理

                // 假设我们能获取到Retry-After秒数

                int retryAfterSeconds = parseRetryAfterFromException(e); // 这是一个假设的方法

                if (retryAfterSeconds > 0) {

                    sleepTimeMs = retryAfterSeconds * 1000L;

                } else {

                    // 如果没有Retry-After，则使用指数退避

                    sleepTimeMs = (long) (Math.pow(2, retryCount) * 1000L); // 1s, 2s, 4s, 8s...

                    // 添加随机抖动，避免所有客户端同时重试

                    sleepTimeMs += (long) (Math.random() * 500); // 随机增加0-500ms

                }

                System.out.println("等待 " + (sleepTimeMs / 1000.0) + " 秒后重试...");

                Thread.sleep(sleepTimeMs);

                retryCount++;

            } else {

                throw e; // 其他错误，直接抛出

            }

        }

    }

    throw new Exception("达到最大重试次数，仍未能成功获取用户活动。");

}

// 辅助方法：从异常中解析Retry-After头，实际实现可能需要深入Graph SDK的异常结构或使用自定义HTTP拦截器

private int parseRetryAfterFromException(Exception e) {

    // 实际实现需要解析HTTP响应头，这通常需要访问底层的HttpResponse对象

    // Graph SDK的ApiException可能包含这些信息，或者需要自定义OkHttpClient拦截器来捕获

    // 简化示例，假设我们无法直接获取，或者返回一个默认值

    return 0; // 默认返回0，表示不使用Retry-After

}