Solution for <async-supported>true</async-supported> error in Web. XML configuration file

Why use this:

SSH integrated CXF, when logged into the system, found the system error, the console continuously output the following information:

2016-05-05 11:05:06-[http-bio-8080-exec-4]-warn-exceptionhandler:38-error:java.lang.illegalstateexception:a filt Er or servlet of the current chain does not asynchronous operations.
2016-05-05 11:05:06-[http-bio-8080-exec-9]-warn-exceptionhandler:38-error:java.lang.illegalstateexception:a filt Er or servlet of the current chain does not asynchronous operations.
2016-05-05 11:05:06-[http-bio-8080-exec-6]-warn-exceptionhandler:38-error:java.lang.illegalstateexception:a filt Er or servlet of the current chain does not asynchronous operations.
2016-05-05 11:05:06-[http-bio-8080-exec-10]-warn-exceptionhandler:38-error:java.lang.illegalstateexception:a fil ter or servlet of the current chain does not support asynchronous operations.
2016-05-05 11:05:06-[http-bio-8080-exec-5]-warn-exceptionhandler:38-error:java.lang.illegalstateexception:a filt Er or servlet of the current chain does not asynchronous operations.
2016-05-05 11:05:09-[http-bio-8080-exec-9]-warn-exceptionhandler:38-error:java.lang.illegalstateexception:a filt Er or servlet of the current chain does not asynchronous operations.
2016-05-05 11:05:09-[http-bio-8080-exec-4]-warn-exceptionhandler:38-error:java.lang.illegalstateexception:a filt Er or servlet of the current chain does not asynchronous operations.
2016-05-05 11:05:09-[http-bio-8080-exec-5]-warn-exceptionhandler:38-error:java.lang.illegalstateexception:a filt Er or servlet of the current chain does not asynchronous operations.
2016-05-05 on 11:0

The problem is found in the following search:

The error message is: There is a filter in Web. xml or the servlet does not support asynchrony.

What based on what made the "active" enemy kill 2016/5/4 17:45:03 what container

"Active" Guy 2016/5/4 17:45:42 Tomcat 17:45:54 "active" Enemy kills 2016/5/4 17:45:54 add <asychronized> true< for each filter servlet configuration /asychronized> "active" enemy kills 2016/5/4 17:46:26 normal tomcat or alitomcat "active" Enemy kills 2016/5/4 17:47:28 <async-supported>true </async-supported> "Active" enemy killed 2016/5/4 17:47:40

"Active" enemy killed 2016/5/4 17:47:44 to support asynchronous 17:57:27 "active" Boy 2016/5/4 17:57:27 normal tomcat

"Active" Boy 2016/5/4 17:57:35 alitomcat what is it?

"Active" Guy 2016/5/4 17:58:10 is to say my web. Does all the servlet or filter in the XML need to be added? 18:19:16 "active" enemy kills 2016/5/4 18:19:16 yes "active" enemy kills 2016/5/4 18:19:30 Ali Tomcat 19:44:11 "active" Guy 20 16/5/4 19:44:11 @ The enemy kills me what will happen after that, for the project 19:54:37 "active" Boy 2016/5/4 19:54:37 If the interface is a collection type, such as list, it seems to be a problem.

"Active" Guy 2016/5/4 19:54:47 client generated with CXF "active" enemy kill 2016/5/4 19:56:26 map There will also be problems 19:57:10 "active" enemy killed 2016/5/4 19:57:10 then agreed on the parameter development specification "active "The enemy killed 2016/5/4 19:57:26 because your environment needs to support asynchronous" active "enemies to kill 2016/5/4 19:57:41 Servlet 3.0 supports asynchronous features

"Active" Guy 2016/5/4 19:58:27 I was so changed on the web. XML, what does it have to do with our system? 19:58:41 "active" enemy kills 2016/5/4 19:58:41 will not "active" enemy kill 2016/5/4 19:59:07 just later you have to inherit other open source framework, the other open source framework does not support the problem of "live Leap "enemy kill 2016/5/4 19:59:40 is a chain call, a servlet or filter does not support asynchronous will error" active "enemy killed 2016/5/4 20:00:12 which framework you need to support asynchronous features?" active "Enemy kills 2016/5/4 20:00:17 cxf?

"Active" Guy 2016/5/4 20:00:27 ssh need it "active" enemy kill 2016/5/4 20:00:31 CXF not like this AH

"Active" Boy 2016/5/4 20:00:41 I integrated the cxf into SSH.

20:02:02 "active" enemy kills 2016/5/4 20:02:02 there should be other solutions "active" enemy killed 2016/5/4 20:02:15 the framework itself should have programmatic treatment

"Active" little guy 2016/5/4 20:03:14

"Active" Guy 2016/5/4 20:03:24 I just modified two places.

"Active" little guy 2016/5/4 20:03:29 a web. Xml

"Active" Boy 2016/5/4 20:03:38 there's another struts.xml.

"Active" Guy 2016/5/4 20:04:01 struts.xml to release my WebService address 20:04:42 "active" enemy kill 2016/5/4 20:04:42 CXF itself does not need to be asynchronous AH

The "active" guy will not report that error at the start of 2016/5/4 20:04:56, but will report the error as soon as he logs in to our system. And it's always bouncing out.

"Active" Boy 2016/5/4 20:05:17 is not needed AH

"Active" guy, 2016/5/4 20:05:33 when I started the service, I released the "active" enemy and killed 2016/5/4 20:05:37, and it was the right "active" enemy to kill 2016/5/4 20:05:45 did not support async, so go synchronized "active" enemy kill 201 6/5/4 20:05:52 Synchronization is a constant brush.

"Active" Guy 2016/5/4 20:06:10 So, my cxf doesn't support syncing?

"Active" Guy 2016/5/4 20:06:20 Asynchronous "active" enemy kills 2016/5/4 20:06:26 support sync "active" Enemy kills 2016/5/4 20:06:35 you can invoke the "active" enemy to kill 2016/5/4 20:06 when you call it: 42 is going to keep asking. 20:06:48 "active" boy 2016/5/4 20:06:48 that is to access the system, and someone calls this interface, it will appear

"Active" Guy 2016/5/4 20:06:54 I know your mind. "Active" enemy kills 2016/5/4 20:06:54 call or the "active" enemy that can be invoked normally kills 2016/5/4 20:07:08 you can call it now.

"Active" Boy 2016/5/4 20:07:14 Yes. The system can also operate normally. Call can Also

"Active" Guy 2016/5/4 20:07:25 no impact, is the console has been brushed "active" enemy killed 2016/5/4 20:07:26 is the phenomenon of "active" enemy kill 2016/5/4 20:07:45 no impact or "active" enemy kill 2016/5/4 20:07:52 look at the log can't see the "active" enemy killed 2016/5/4 20:08:04 debugging also can not adjust the "active" enemy killed 2016/5/4 20:08:13 just function normal

"Active" little guy 2016/5/4 20:08:23

"Active" Boy 2016/5/4 20:08:26

"Active" Guy 2016/5/4 20:08:36 that's your way of dealing with that? 20:09:03 "active" enemy kills 2016/5/4 20:09:03 support Async on the line "active" enemy kills 2016/5/4 20:09:24 but I don't know where you're from.

"Active" Guy 2016/5/4 20:09:58 isn't cxfservlet not supported?

"Active" Guy 2016/5/4 20:10:24 There are many asynchronous ways inside our system.

"Active" Guy 2016/5/4 20:10:32 background interaction when "active" enemy kills 2016/5/4 20:10:41 I'm cometd need servlet3.0 asynchronous support "active" enemy kill 2016/5/4 20:10:59 C The XF itself should not need 20:11:12 "active" Boy 2016/5/4 20:11:12 cometd is what ah "active" enemy killed 2016/5/4 20:11:23 you can Baidu under

"Active" guy, 2016/5/4 20:12:24 I'm probably aware of that.

"Active" Boy 2016/5/4 20:12:41 is my web. Xml that does not support asynchronous calls

"Active" Guy 2016/5/4 20:13:12 we used to have a system that was released via Xfire, and there's no such thing. 20:13:41 "active" guy, 2016/5/4 20:13:41 but not integrated into the open source framework, but the soundtrack released by the "Active" enemy killed 2016/5/4 20:13:56 That's not clear, you can separate the whole CXF environment to see 20:16:53 "active" Guy 2016/5/4 20:16:53 Actually, I just need to find the one that doesn't support asynchronous calls, plus the configuration you give, you can kill 2016/5/4 with "active" enemies. 20:17:20 each one plus it's ready.

"Active" Guy 2016/5/4 20:18:15 will all become synchronized "active" enemy kill 2016/5/4 20:19:09 No, chain call is the middle of the broken that don't know not to go "active" enemy kill 2016/5/4 20:19:31 will say a serv Let does not support the asynchronous "active" enemy kill 2016/5/4 20:19:42 you see the error message may be found 20:21:59 "active" Guy 2016/5/4 20:21:59 we released the interface that wrote hibernate

"Active" Guy 2016/5/4 20:22:28 that's what you said. Chained calls

"Active" Boy 2016/5/4 20:23:03 no error message

"Active" Boy 2016/5/4 20:23:09 only 2016-05-04 17:38:44-[http-bio-8080-exec-9]-warn-exceptionhandler:38-error:java.lang.il LEGALSTATEEXCEPTION:A Filter or servlet of the current chain does not support asynchronous operations. "Active" enemy killed 2016/5/4 20:23:36 that's you and the error log didn't hit out "active" enemy killed 2016/5/4 20:23:42 not printed on console "active" Enemy kills 2016/5/4 20:23:51 you hibernate log have you seen it?

"Active" boy, 2016/5/4 20:25:24 didn't look.

"Active" Boy, 2016/5/4 20:25:30, it's already off.

"Active" Boy 2016/5/4 20:25:36 See the "Active" enemy kill 2016/5/4 20:25:40 Oh 88

"Active" Boy 2016/5/4 20:26:06 I'm coming home from work, looking for a solution.

"Active" Guy 2016/5/4 20:27:10 cxf is not a good legend to support the list "T" type of return value

Read the above chat to know: servlet3.0 previously did not support async. And our project is now using 2.4.

This will appear the title of the problem, the solution is as follows:

http://blog.csdn.net/zxz547388910/article/details/50780068

Solutions for <async-supported>true</async-supported> errors in the Web. XML configuration file