[jboss-jira] [JBoss JIRA] (WFCORE-1201) Could not upload new deployment

[Harald Pehl (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142007#comment-13142007 ] 

Harald Pehl commented on WFCORE-1201:
-------------------------------------

Up to now I was not able to reproduce the error. Tested with WildFly Core 2.0.4.Final "Kenny", HAL 2.8.16.Final and these OS / browser combinations:

- Chrome 47.0.2526.80 on OSX El Capitan 10.11.1 (15B42) *
- Chrome 46.0.2490.86 on OSX El Capitan 10.11.1 (15B42) *
- Chrome 47.0.2526.73 on Windows 10
- Chrome 47.0.2526.73 on Windows 8.1
- Chrome 47.0.2526.73 on Windows 8
- Chrome 47.0.2526.73 on Windows 7

* Wasn't able to get Chrome 47.0.2526.73 for OSX


> Could not upload new deployment
> -------------------------------
>
>                 Key: WFCORE-1201
>                 URL: https://issues.jboss.org/browse/WFCORE-1201
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 1.0.2.Final
>         Environment: 2 different machines
> Linux Debian Squeeze & Jessie
> Oracle Java SE 8
>            Reporter: Claudio Weiler
>            Assignee: Harald Pehl
>            Priority: Blocker
>             Fix For: 2.0.5.Final
>
>
> WildFly stop to accept deployments via interface upload with following stacktrace:
> ERROR [io.undertow.request] (XNIO-1 task-2) Undertow request failed HttpServerExchange{ POST /management-upload}: java.io.IOException: UT000036: Connection terminated parsing multipart data
> 	at io.undertow.server.handlers.form.MultiPartParserDefinition$MultiPartUploadHandler.parseBlocking(MultiPartParserDefinition.java:203)
> 	at org.jboss.as.domain.http.server.DomainApiGenericOperationHandler.handleRequest(DomainApiGenericOperationHandler.java:104)
> 	at io.undertow.server.handlers.encoding.EncodingHandler.handleRequest(EncodingHandler.java:72)
> 	at org.jboss.as.domain.http.server.security.SubjectDoAsHandler$1.run(SubjectDoAsHandler.java:72)
> 	at org.jboss.as.domain.http.server.security.SubjectDoAsHandler$1.run(SubjectDoAsHandler.java:68)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at javax.security.auth.Subject.doAs(Subject.java:422)
> 	at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:92)
> 	at org.jboss.as.domain.http.server.security.SubjectDoAsHandler.handleRequest(SubjectDoAsHandler.java:68)
> 	at org.jboss.as.domain.http.server.security.SubjectDoAsHandler.handleRequest(SubjectDoAsHandler.java:63)
> 	at io.undertow.server.handlers.BlockingHandler.handleRequest(BlockingHandler.java:56)
> 	at org.jboss.as.domain.http.server.DomainApiCheckHandler.handleRequest(DomainApiCheckHandler.java:87)
> 	at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52)
> 	at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199)
> 	at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:774)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 	at java.lang.Thread.run(Thread.java:745)
> Same artifact was used before with success, nothing changed.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)