微服务-长轮询异常：SecurityManager accessible to the calling code

原创已于 2022-11-22 12:41:31 修改 · 564 阅读

1 ·

CC 4.0 BY-SA版权

文章标签：

#java #servlet #开发语言

于 2022-11-22 12:41:23 首次发布

本文介绍了解决Shiro在异步环境下配置不当导致的UnavailableSecurityManagerException异常的方法。通过调整Shiro过滤器以支持异步操作，并展示了具体的实现代码。

使用长轮询时，前端出现请求异常，出现如下异常：

[http-nio-18080-exec-5] ERROR o.a.c.c.C.[.[localhost].[/wvp].[dispatcherServlet]:175 - Servlet.service() for servlet [dispatcherServlet] threw exception
org.apache.shiro.UnavailableSecurityManagerException: No SecurityManager accessible to the calling code, either bound to the org.apache.shiro.util.ThreadContext or as a vm static singleton.  This is an invalid application configuration.
	at org.apache.shiro.SecurityUtils.getSecurityManager(SecurityUtils.java:123)
	at org.apache.shiro.subject.Subject$Builder.<init>(Subject.java:626)
	at org.apache.shiro.SecurityUtils.getSubject(SecurityUtils.java:56)

gateway 提示信息：

reactor.netty.http.client.PrematureCloseException: Connection prematurely closed DURING response

如使用shiro，可对shiro设定支持异步，如下增加bean

@Bean
    public FilterRegistrationBean shiroFilterRegistration() {
        FilterRegistrationBean registration = new FilterRegistrationBean();
        registration.setFilter(new DelegatingFilterProxy("shiroFilterFactoryBean"));
        registration.addInitParameter("targetFilterLifecycle", "true");
        registration.setEnabled(true);
        registration.setOrder(Integer.MAX_VALUE - 1);
        registration.addUrlPatterns("/*");

        //支持异步
        registration.setAsyncSupported(true);
        registration.setDispatcherTypes(DispatcherType.REQUEST,DispatcherType.ASYNC);
        return registration;
    }

重新启动后，接口再次调用即可正常返回数据信息。

异常原因：上面错误的原因是我们的shiro filter没有对AsyncContext中的Request没有做拦截，造成SecurityManager为空。

参考：

https://www.jianshu.com/p/aa06c5f2592d

UnavailableSecurityManagerException: No SecurityManager accessible to the calling Spring Shiro异步配置_五菱包工头的博客-优快云博客