【错误4】：No thread-bound request found

最新推荐文章于 2024-03-08 17:02:09 发布
最新推荐文章于 2024-03-08 17:02:09 发布
阅读量2.4k 收藏 1
点赞数 1
分类专栏： 错误收集
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/mr_zql/article/details/95459667
版权

页面报错：
HTTP Status 500 - org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘isLogin’: Scope ‘request’ is not active for the current thread; consider defining a scoped proxy for this bean if you intend to refer to it from a singleton; nested exception is java.lang.IllegalStateException: No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web request and still receive this message, your code is probably running outside of DispatcherServlet/DispatcherPortlet: In this case, use RequestContextListener or RequestContextFilter to expose the current request.

控制台报错

严重: Servlet.service() for servlet [jersey-serlvet] in context with path [/top.zqlweb] threw exception [org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'isLogin': Scope 'request' is not active for the current thread; consider defining a scoped proxy for this bean if you intend to refer to it from a singleton; nested exception is java.lang.IllegalStateException: No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web request and still receive this message, your code is probably running outside of DispatcherServlet/DispatcherPortlet: In this case, use RequestContextListener or RequestContextFilter to expose the current request.] with root cause
java.lang.IllegalStateException: No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web request and still receive this message, your code is probably running outside of DispatcherServlet/DispatcherPortlet: In this case, use RequestContextListener or RequestContextFilter to expose the current request.
	at org.springframework.web.context.request.RequestContextHolder.currentRequestAttributes(RequestContextHolder.java:131)
	at org.springframework.web.context.request.AbstractRequestAttributesScope.get(AbstractRequestAttributesScope.java:41)
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:340)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
	at org.springframework.aop.config.SimpleBeanFactoryAwareAspectInstanceFactory.getAspectInstance(SimpleBeanFactoryAwareAspectInstanceFactory.java:65)
	at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:629)
	at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:611)
	at org.springframework.aop.aspectj.AspectJMethodBeforeAdvice.before(AspectJMethodBeforeAdvice.java:43)
	at org.springframework.aop.framework.adapter.MethodBeforeAdviceInterceptor.invoke(MethodBeforeAdviceInterceptor.java:51)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:168)
	at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
	at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:673)
	at top.zqlweb.rest.mng.MngRootRest$$EnhancerBySpringCGLIB$$8c5c2714.path(<generated>)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.glassfish.jersey.server.internal.routing.SubResourceLocatorRouter$2.run(SubResourceLocatorRouter.java:229)
	at org.glassfish.jersey.server.internal.routing.SubResourceLocatorRouter.getResource(SubResourceLocatorRouter.java:251)
	at org.glassfish.jersey.server.internal.routing.SubResourceLocatorRouter.apply(SubResourceLocatorRouter.java:133)
	at org.glassfish.jersey.server.internal.routing.RoutingStage._apply(RoutingStage.java:128)
	at org.glassfish.jersey.server.internal.routing.RoutingStage._apply(RoutingStage.java:131)
	at org.glassfish.jersey.server.internal.routing.RoutingStage._apply(RoutingStage.java:131)
	at org.glassfish.jersey.server.internal.routing.RoutingStage._apply(RoutingStage.java:131)
	at org.glassfish.jersey.server.internal.routing.RoutingStage._apply(RoutingStage.java:131)
	at org.glassfish.jersey.server.internal.routing.RoutingStage.apply(RoutingStage.java:110)
	at org.glassfish.jersey.server.internal.routing.RoutingStage.apply(RoutingStage.java:65)
	at org.glassfish.jersey.process.internal.Stages.process(Stages.java:197)
	at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:250)
	at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)
	at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)
	at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
	at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
	at org.glassfish.jersey.internal.Errors.process(Errors.java:267)
	at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:319)
	at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:236)
	at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1028)
	at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:373)
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:381)
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:344)
	at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:219)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:218)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:958)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:452)
	at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1087)
	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:637)
	at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	at java.lang.Thread.run(Thread.java:745)

在这里插入图片描述

解决方案：在web.xml中添加监听HTTP请求事件

<listener>
    <listener-class>
		org.springframework.web.context.request.RequestContextListener
	</listener-class>
</listener>
似水流年风萧兮
关注
专栏目录
no thread-bound request found:are you referring to request
lierjun 的专栏
12-11 1399
问题描述： 通过webservice接口调用程序时，发现在执行查询的时候一直报一个错误，错误信息如下： java.lang.IllegalStateExceptino:No thread-bound request found:are you referring to request attributes outside of an actual web request,or processi...
No thread-bound request found 错误以及解决方案
飘雪的随笔
09-20 8183
No thread-bound request found 错误以及解决方案
spring：No thread-bound request found
xinyuan的专栏
08-20 1万+
在 Spring中使用 多线程中， 应注意 新起的线程是不能直接访问主线程的生命周期结束的变量 比如在 在 web应用中 在新起的线程中使用 HttpServletRequest ， 会报出 IllegalStateException 的异常， 需要在使用 Request 的地方捕获异常， 或者把Request的对象传递到新起的线程里面 java.lang.IllegalSta...
IllegalStateException: No thread-bound request
wyhhahaha的博客
02-29 1059
在多线程环境下，由于线程的异步执行特性，可能会导致当前线程尝试访问请求对象时，找不到对应的请求对象，从而抛出异常。我们可以通过RequestContextHolder类来设置当前请求对象的上下文信息。
No thread-bound request found问题处理
愤怒的公牛的博客
03-17 1万+
问题描述 在一个项目中需要实现一个定时上报的任务，由于是分条件上报所以就采用了异步的上报方式，用了自定义的线程池运行上报线程。定时任务执行的时候报了No thread-bound request found: " + "Are you referring to request attributes outside of an actual web request, " + "or processing a request outside of the originally recei
解决No thread-bound request found: Are you referring to request attributes outside of an actual web re
热门推荐
lvxiucai的博客
09-30 6万+
使用背景：今天在spring-cloud项目中，使用多线程异步调用微服务出现的错误 Nothread-boundrequestfound:Areyoureferringtorequestattributesoutsideofanactualwebrequest,orprocessingarequestoutsideoftheoriginallyr...
grails在新建线程进行操作报错：No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web request and still receive this message, your code is probably running outside of DispatcherServlet/DispatcherPortlet: In this case, use RequestContextListener or RequestContextFilter to expose the current request.
07-14
通过上述方法，你可以确保在 Grails 中的相关组件中获取到当前请求对象，并避免 "No thread-bound request found" 的错误。请根据你的具体情况选择适合的方法进行处理。注意，如果你在非Web请求的上下文中使用了与...
定时任务No thread-bound request found
08-19
定时任务 "No thread-bound request found" 错误通常是由于在没有请求上下文的情况下执行了需要请求上下文的操作而引起的。在定时任务中，由于没有与请求关联的线程，无法获取当前请求的上下文。 要解决这个问题，...
No thread-bound request found:
04-22
这个错误通常发生在使用Spring框架的Web应用程序中，是因为没有将请求与线程绑定，导致请求处理过程中无法访问请求对象。可能的解决方案是确保在处理请求时将请求与线程绑定，例如使用Spring提供的...
线程池 No thread-bound request found: Are you referring
12-07
这个错误通常是由于在没有请求的情况下尝试访问请求属性而引起的。这可能是因为您正在尝试在没有请求的情况下访问请求作用域bean。为了解决这个问题，您可以使用aop:scoped-proxy标签来配置请求作用域bean。这将创建...
java.lang.IllegalStateException: No thread-bound request found 解决方法
爱吃榴莲的小白
03-09 1万+
No thread-bound request found: " + "Are you referring to request attributes outside of an actual web request, " + "or processing a request outside of the originally receiving thread?
java代码报错java.lang.IllegalStateException: No thread-bound request found
Esther_77的博客
11-14 3080
java代码报错java.lang.IllegalStateException: No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web
java.lang.IllegalStateException: No thread-bound request found Spring中遇见问题，说是并流了
xu_lo的博客
12-17 1万+
具体原因不知！百度查查解决方法！得到如下 Caused by: java.lang.IllegalStateException: No thread-bound request found: Are you referring to request attributes outside of an actual web request, o
解决 No thread-bound request found:
yk10010的博客
03-29 2505
在开启新线程之前，将servletRequestAttributes设置为子线程共享 ServletRequestAttributes servletRequestAttributes = (ServletRequestAttributes)RequestContextHolder.getRequestAttributes(); //设置子线程共 RequestContextHolder.setRequestAttributes(servletRequestAttributes,true); 如果非we
No thread-bound request found异常
weixin_33912453的博客
04-16 1750
序 本文主要研究下spring mvc的No thread-bound request found异常 分析 该错误信息在RequestContextHolder这个类中，详细如下：spring-web-4.3.7.RELEASE-sources.jar!/org/springframework/web/context/request/R...
解决No thread-bound request found问题
weixin_39284815的博客
09-14 1万+
解决No thread-bound request found问题 今天遇到了启动项目时突然报找不到线程绑定请求：No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operat
JAVA分布式项目中报错：No thread-bound request found: Are you referring to request attributes…
tianjiliuhen的博客
01-13 2万+
原文地址：http://www.5ixiudou.com/portal/detailInfo/1000000005/239   1.错误描述：无法获取 request ，是否是web项目 2.错误原因： 分布式项目中，我们会把一些服务提取出来形成一个服务提供者，并且单独发布为一个项目。一般发布成一个jar包，这个服务提供者可以称之为 soa项目。 soa只是一个简单的接口项目，不是web...
No thread-bound request found: Are you referring to request attributes outside of an actual web req
最新发布
lly576403061的博客
03-08 3081
No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web request and still receive this message,
Java并行流 No thread-bound request found
Gblfy_Blog
06-21 4091
异常如下： java.lang.IllegalStateException: No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiv...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值