关于异步的好处我在这里就很少说了,自从servlet3.1规范发布以来,控制层的异步处理也愈来愈多的被人说起。而Spring5的webflux诞生也意味着Spring全方位对异步提供了支持。其实早在SpringMVC3.2版本就开始支持异步了,那么这篇文章咱们就来探讨一下SpringMVC使用异步的方式。java
DeferredResult这个类表明延迟结果,咱们先看一看spring的API文档给咱们的解释:web
{@code DeferredResult} provides an alternative to using a {@link Callable} for asynchronous request processing. While a {@code Callable} is executed concurrently on behalf of the application, with a {@code DeferredResult} the application can produce the result from a thread of its choice.spring
根据文档说明DeferredResult
能够替代Callable
来进行异步的请求处理。只不过这个类能够从其余线程里拿到对应的结果。当使用DeferredResult
,咱们能够将DefferedResult的类型并将其保存到能够获取到该对象的地方,好比说队列或者集合当中,这样方便其它线程可以取到并设置DefferedResult
的值。tomcat
咱们先定义一个Controller,代码内容以下:mvc
package com.bdqn.lyrk.ssm.study.web.controller; import org.springframework.web.bind.annotation.GetMapping; import org.springframework.web.bind.annotation.RestController; import org.springframework.web.context.request.async.DeferredResult; import java.util.concurrent.ArrayBlockingQueue; import java.util.concurrent.BlockingQueue; import java.util.concurrent.Callable; /** * 异步任务的控制器 * * @author chen.nie * @date 2018/8/2 **/ @RestController public class AsyncController { private BlockingQueue<DeferredResult<String>> blockingQueue = new ArrayBlockingQueue(1024); /** * 返回值是DeferredResult类型,若是没有结果请求阻塞 * * @return */ @GetMapping("/quotes") public DeferredResult<String> quotes() { //指定超时时间,及出错时返回的值 DeferredResult<String> result = new DeferredResult(3000L,"error"); blockingQueue.add(result); return result; } /** * 另一个请求(新的线程)设置值 * * @throws InterruptedException */ @GetMapping("take") public void take() throws InterruptedException { DeferredResult<String> result = blockingQueue.take(); result.setResult("route"); } @GetMapping public Callable<String> callable() { return () -> "callable"; } }
控制器能够从不一样的线程异步生成返回值,例如响应外部事件(JMS消息)、计划任务等,那么在这里我先使用另一个请求来模拟这个过程
此时咱们启动tomcat,先访问地址http://localhost:8080/quotes ,此时咱们会看到发送的请求因为等待响应遭到了阻塞:
app
当在规定时间内访问http://localhost:8080/take 时,则能成功显示结果:
框架
根据官网描述:异步
DeferredResult processing:async
将Controller返回的DeferredResult
值保存到内存队列或集合当中,紧接着SpringMVC调用HttpServletRequest
的startAsync()
方法,与此同时DispatcherServlet
和全部配置的Filter
退出当前的请求线程(不过响应时开放的),当其余线程里设置DeferredResult的值时将从新发送请求,此时DispatcherServlet使用异步生成的返回值继续处理。ide
在这里一切的一切还须要经过源代码来解释:
DispatcherServlet
处理时,会试着获取一个WebAsyncManager
对象protected void doDispatch(HttpServletRequest request, HttpServletResponse response) throws Exception { HttpServletRequest processedRequest = request; HandlerExecutionChain mappedHandler = null; boolean multipartRequestParsed = false; WebAsyncManager asyncManager = WebAsyncUtils.getAsyncManager(request); try { // ......省略部分代码 // 执行子控制器的方法 mv = ha.handle(processedRequest, response, mappedHandler.getHandler()); //若是当前的请求须要异步处理,则终止当前请求,可是响应是开放的 if (asyncManager.isConcurrentHandlingStarted()) { return; } //....省略部分代码 } catch (Exception ex) { triggerAfterCompletion(processedRequest, response, mappedHandler, ex); } catch (Throwable err) { triggerAfterCompletion(processedRequest, response, mappedHandler, new NestedServletException("Handler processing failed", err)); } finally { if (asyncManager.isConcurrentHandlingStarted()) { // Instead of postHandle and afterCompletion if (mappedHandler != null) { mappedHandler.applyAfterConcurrentHandlingStarted(processedRequest, response); } } else { // Clean up any resources used by a multipart request. if (multipartRequestParsed) { cleanupMultipart(processedRequest); } } } }
HandlerMethodReturnValueHandler
接口处理的,其中有一个实现类是DeferredResultMethodReturnValueHandler
,关键代码以下:package org.springframework.web.servlet.mvc.method.annotation; import java.util.HashMap; import java.util.Map; import java.util.concurrent.CompletionStage; import java.util.function.BiFunction; import org.springframework.core.MethodParameter; import org.springframework.lang.UsesJava8; import org.springframework.util.Assert; import org.springframework.util.ClassUtils; import org.springframework.util.concurrent.ListenableFuture; import org.springframework.util.concurrent.ListenableFutureCallback; import org.springframework.web.context.request.NativeWebRequest; import org.springframework.web.context.request.async.DeferredResult; import org.springframework.web.context.request.async.WebAsyncUtils; import org.springframework.web.method.support.AsyncHandlerMethodReturnValueHandler; import org.springframework.web.method.support.ModelAndViewContainer; /** * Handler for return values of type {@link DeferredResult}, {@link ListenableFuture}, * {@link CompletionStage} and any other async type with a {@link #getAdapterMap() * registered adapter}. * * @author Rossen Stoyanchev * @since 3.2 */ @SuppressWarnings("deprecation") public class DeferredResultMethodReturnValueHandler implements AsyncHandlerMethodReturnValueHandler { //存放DeferredResult的适配集合 private final Map<Class<?>, DeferredResultAdapter> adapterMap; public DeferredResultMethodReturnValueHandler() { this.adapterMap = new HashMap<Class<?>, DeferredResultAdapter>(5); this.adapterMap.put(DeferredResult.class, new SimpleDeferredResultAdapter()); this.adapterMap.put(ListenableFuture.class, new ListenableFutureAdapter()); if (ClassUtils.isPresent("java.util.concurrent.CompletionStage", getClass().getClassLoader())) { this.adapterMap.put(CompletionStage.class, new CompletionStageAdapter()); } } /** * Return the map with {@code DeferredResult} adapters. * <p>By default the map contains adapters for {@code DeferredResult}, which * simply downcasts, {@link ListenableFuture}, and {@link CompletionStage}. * @return the map of adapters * @deprecated in 4.3.8, see comments on {@link DeferredResultAdapter} */ @Deprecated public Map<Class<?>, DeferredResultAdapter> getAdapterMap() { return this.adapterMap; } private DeferredResultAdapter getAdapterFor(Class<?> type) { for (Class<?> adapteeType : getAdapterMap().keySet()) { if (adapteeType.isAssignableFrom(type)) { return getAdapterMap().get(adapteeType); } } return null; } @Override public boolean supportsReturnType(MethodParameter returnType) { return (getAdapterFor(returnType.getParameterType()) != null); } @Override public boolean isAsyncReturnValue(Object returnValue, MethodParameter returnType) { return (returnValue != null && (getAdapterFor(returnValue.getClass()) != null)); } @Override public void handleReturnValue(Object returnValue, MethodParameter returnType, ModelAndViewContainer mavContainer, NativeWebRequest webRequest) throws Exception { if (returnValue == null) { mavContainer.setRequestHandled(true); return; } //根据返回值的类型获取对应的DeferredResult适配器 DeferredResultAdapter adapter = getAdapterFor(returnValue.getClass()); if (adapter == null) { throw new IllegalStateException( "Could not find DeferredResultAdapter for return value type: " + returnValue.getClass()); } DeferredResult<?> result = adapter.adaptToDeferredResult(returnValue); //开启异步请求 WebAsyncUtils.getAsyncManager(webRequest).startDeferredResultProcessing(result, mavContainer); } }
在这里咱们关注handleReturnValue
的方法,在通过适配包装后获取DeferredResult
开启了异步之旅
WebAsyncManager
的startDeferredResultProcessing
方法/** * Start concurrent request processing and initialize the given * {@link DeferredResult} with a {@link DeferredResultHandler} that saves * the result and dispatches the request to resume processing of that * result. The {@code AsyncWebRequest} is also updated with a completion * handler that expires the {@code DeferredResult} and a timeout handler * assuming the {@code DeferredResult} has a default timeout result. * @param deferredResult the DeferredResult instance to initialize * @param processingContext additional context to save that can be accessed * via {@link #getConcurrentResultContext()} * @throws Exception if concurrent processing failed to start * @see #getConcurrentResult() * @see #getConcurrentResultContext() */ public void startDeferredResultProcessing( final DeferredResult<?> deferredResult, Object... processingContext) throws Exception { Assert.notNull(deferredResult, "DeferredResult must not be null"); Assert.state(this.asyncWebRequest != null, "AsyncWebRequest must not be null"); //设置超时时间 Long timeout = deferredResult.getTimeoutValue(); if (timeout != null) { this.asyncWebRequest.setTimeout(timeout); } //获取全部的延迟结果拦截器 List<DeferredResultProcessingInterceptor> interceptors = new ArrayList<DeferredResultProcessingInterceptor>(); interceptors.add(deferredResult.getInterceptor()); interceptors.addAll(this.deferredResultInterceptors.values()); interceptors.add(timeoutDeferredResultInterceptor); final DeferredResultInterceptorChain interceptorChain = new DeferredResultInterceptorChain(interceptors); this.asyncWebRequest.addTimeoutHandler(new Runnable() { @Override public void run() { try { interceptorChain.triggerAfterTimeout(asyncWebRequest, deferredResult); } catch (Throwable ex) { setConcurrentResultAndDispatch(ex); } } }); this.asyncWebRequest.addCompletionHandler(new Runnable() { @Override public void run() { interceptorChain.triggerAfterCompletion(asyncWebRequest, deferredResult); } }); interceptorChain.applyBeforeConcurrentHandling(this.asyncWebRequest, deferredResult); //开始异步处理 startAsyncProcessing(processingContext); try { interceptorChain.applyPreProcess(this.asyncWebRequest, deferredResult); deferredResult.setResultHandler(new DeferredResultHandler() { @Override public void handleResult(Object result) { result = interceptorChain.applyPostProcess(asyncWebRequest, deferredResult, result); //设置结果并转发 setConcurrentResultAndDispatch(result); } }); } catch (Throwable ex) { setConcurrentResultAndDispatch(ex); } } private void startAsyncProcessing(Object[] processingContext) { clearConcurrentResult(); this.concurrentResultContext = processingContext; //其实是执行的是HttpServletRequest对应方法 this.asyncWebRequest.startAsync(); if (logger.isDebugEnabled()) { HttpServletRequest request = this.asyncWebRequest.getNativeRequest(HttpServletRequest.class); String requestUri = urlPathHelper.getRequestUri(request); logger.debug("Concurrent handling starting for " + request.getMethod() + " [" + requestUri + "]"); } }
在这里首先收集全部配置好的DeferredResultProcessingInterceptor
,而后设置asyncRequest的超时处理,完成时的处理等,同时会分阶段执行拦截器中的各个方法。在这里真的佩服Spring框架的扩展机制作的实在是太好了。最后咱们关注一下以下代码:
deferredResult.setResultHandler(new DeferredResultHandler() { @Override public void handleResult(Object result) { result = interceptorChain.applyPostProcess(asyncWebRequest, deferredResult, result); //设置结果并转发 setConcurrentResultAndDispatch(result); } });
其最终仍是要调用AsyncWebRequest
接口中的dispatch
方法进行转发,让DispatcherServlet
从新处理异步结果:
/** * Dispatch the request to the container in order to resume processing after * concurrent execution in an application thread. */ void dispatch();
其实在这里都是封装自HttpServletRequest
的异步操做,咱们能够看一下StandardServletAsyncWebRequest
的类结构图:
咱们能够在其父类ServletRequestAttributes
里找到对应的实现:
private final HttpServletRequest request; /** * Exposes the native {@link HttpServletRequest} that we're wrapping. */ public final HttpServletRequest getRequest() { return this.request; }
最后我在贴出一段StandardServletAsyncWebRequest
代码,你们就应该知道整个异步是怎么执行的了:
//java.servlet.AsnycContext private AsyncContext asyncContext; @Override public void startAsync() { Assert.state(getRequest().isAsyncSupported(), "Async support must be enabled on a servlet and for all filters involved " + "in async request processing. This is done in Java code using the Servlet API " + "or by adding \"<async-supported>true</async-supported>\" to servlet and " + "filter declarations in web.xml."); Assert.state(!isAsyncComplete(), "Async processing has already completed"); if (isAsyncStarted()) { return; } this.asyncContext = getRequest().startAsync(getRequest(), getResponse()); this.asyncContext.addListener(this); if (this.timeout != null) { this.asyncContext.setTimeout(this.timeout); } } @Override public void dispatch() { Assert.notNull(this.asyncContext, "Cannot dispatch without an AsyncContext"); this.asyncContext.dispatch(); }
使用Callable
做为返回值来实现异步与DeferredResult
相似,咱们先看一看官网描述的具体流程:
Callable processing:
流程上大致与DeferredResult
相似,只不过Callable
是由TaskExecutor
来处理的,而TaskExecutor
继承自java.util.concurrent.Executor
。咱们来看一下它的源代码,它也是在WebAysncManager
中处理的:
/** * Use the given {@link WebAsyncTask} to configure the task executor as well as * the timeout value of the {@code AsyncWebRequest} before delegating to * {@link #startCallableProcessing(Callable, Object...)}. * @param webAsyncTask a WebAsyncTask containing the target {@code Callable} * @param processingContext additional context to save that can be accessed * via {@link #getConcurrentResultContext()} * @throws Exception if concurrent processing failed to start */ public void startCallableProcessing(final WebAsyncTask<?> webAsyncTask, Object... processingContext) throws Exception { Assert.notNull(webAsyncTask, "WebAsyncTask must not be null"); Assert.state(this.asyncWebRequest != null, "AsyncWebRequest must not be null"); Long timeout = webAsyncTask.getTimeout(); if (timeout != null) { this.asyncWebRequest.setTimeout(timeout); } AsyncTaskExecutor executor = webAsyncTask.getExecutor(); if (executor != null) { this.taskExecutor = executor; } List<CallableProcessingInterceptor> interceptors = new ArrayList<CallableProcessingInterceptor>(); interceptors.add(webAsyncTask.getInterceptor()); interceptors.addAll(this.callableInterceptors.values()); interceptors.add(timeoutCallableInterceptor); final Callable<?> callable = webAsyncTask.getCallable(); final CallableInterceptorChain interceptorChain = new CallableInterceptorChain(interceptors); this.asyncWebRequest.addTimeoutHandler(new Runnable() { @Override public void run() { logger.debug("Processing timeout"); Object result = interceptorChain.triggerAfterTimeout(asyncWebRequest, callable); if (result != CallableProcessingInterceptor.RESULT_NONE) { setConcurrentResultAndDispatch(result); } } }); this.asyncWebRequest.addCompletionHandler(new Runnable() { @Override public void run() { interceptorChain.triggerAfterCompletion(asyncWebRequest, callable); } }); interceptorChain.applyBeforeConcurrentHandling(this.asyncWebRequest, callable); startAsyncProcessing(processingContext); //启动线程池的异步处理 try { this.taskExecutor.submit(new Runnable() { @Override public void run() { Object result = null; try { interceptorChain.applyPreProcess(asyncWebRequest, callable); result = callable.call(); } catch (Throwable ex) { result = ex; } finally { result = interceptorChain.applyPostProcess(asyncWebRequest, callable, result); } //设置当前的结果并转发 setConcurrentResultAndDispatch(result); } }); } catch (RejectedExecutionException ex) { Object result = interceptorChain.applyPostProcess(this.asyncWebRequest, callable, ex); setConcurrentResultAndDispatch(result); throw ex; } }
对比DeferredResult
,在这里刚开始也是添加拦截器,只不过拦截器的名称是CallableProcessingInterceptor
,同时也须要设置WebAsyncRequest的超时处理,完成时处理的响应操做。这其中最大的区别就是使用TaskExecutor
来对Callable
进行异步处理