[
https://issues.jboss.org/browse/WFLY-1540?page=com.atlassian.jira.plugin....
]
Rich Midwinter commented on WFLY-1540:
--------------------------------------
Just tried to reproduce it myself on alpha2 with a later nginx proxy version and one or
the other (like nginx I guess if this isn't known) seems to have fixed it.
IOException for HTTP DELETE
---------------------------
Key: WFLY-1540
URL:
https://issues.jboss.org/browse/WFLY-1540
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 8.0.0.Alpha1
Reporter: Rich Midwinter
Assignee: Stuart Douglas
I'm seeing the following stack trace at the end of an HTTP DELETE RestEasy method.
I've put a System.out.println() as the last line of the method which I see executed,
I'm confident it's running without error.
06:57:39,897 ERROR [io.undertow.request.io] (default task-55) UT005013: An IOException
occurred: java.nio.channels.ClosedChannelException
at sun.nio.ch.FileChannelImpl.transferFrom(FileChannelImpl.java:644) [rt.jar:1.7.0_21]
at
io.undertow.conduits.ReadDataStreamSourceConduit.transferTo(ReadDataStreamSourceConduit.java:30)
at
org.xnio.conduits.ConduitStreamSourceChannel.transferTo(ConduitStreamSourceChannel.java:83)
[xnio-api-3.1.0.CR3.jar:3.1.0.CR3]
at
io.undertow.server.HttpServerExchange$ReadDispatchChannel.transferTo(HttpServerExchange.java:1544)
at org.xnio.channels.Channels.drain(Channels.java:807)
[xnio-api-3.1.0.CR3.jar:3.1.0.CR3]
at io.undertow.server.HttpServerExchange.endExchange(HttpServerExchange.java:1115)
at io.undertow.server.HttpHandlers.executeRootHandler(HttpHandlers.java:63)
at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:544)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[rt.jar:1.7.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[rt.jar:1.7.0_21]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
In Chrome Developer tools the request remains open with a pending status until
there's a 504 gateway timeout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira