December 2015 - jboss-jira - Jboss List Archives

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

by Claudio Weiler (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1201?page=com.atlassian.jira.plugi... ] Claudio Weiler commented on WFCORE-1201: ---------------------------------------- Edited steps to reproduce. There are theses thread on forum: https://developer.jboss.org/thread/266665 https://developer.jboss.org/thread/266675 This is somehow new, it worked til pass weed, and started with more users. As stated on 2nd link above, this is apparently related to browser, in my case it works on Firefox 42.0 32 bits, but not on Chrome 47.0.2526.73 64 bits. > 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 > > 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)

10 years, 7 months

1
0
0 / 0

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

by Claudio Weiler (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1201?page=com.atlassian.jira.plugi... ] Claudio Weiler updated WFCORE-1201: ----------------------------------- Steps to Reproduce: 1. Go to management interface; 2. Button "Add"; 3. Choose "Upload a new deployment"; 4. Choose file (in my case a .ear); 5. Button "Next"; 6. Button "Finish". 7. Error, go to log to get stack trace. was: Go to management interface; Select artifact to deploy; Request deploy. > 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 > > 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)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-390) Make the group attribute for LegacyPropertiesSecurityRealm default to 'groups'

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-390: ------------------------------------ Summary: Make the group attribute for LegacyPropertiesSecurityRealm default to 'groups' Key: ELY-390 URL: https://issues.jboss.org/browse/ELY-390 Project: WildFly Elytron Issue Type: Enhancement Components: Realms Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta3 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1203) LDAP authentication/authorization fails due to making unneeded role lookup requests

by Brad Maxwell (JIRA)

Brad Maxwell created WFCORE-1203: ------------------------------------ Summary: LDAP authentication/authorization fails due to making unneeded role lookup requests Key: WFCORE-1203 URL: https://issues.jboss.org/browse/WFCORE-1203 Project: WildFly Core Issue Type: Bug Components: Security Reporter: Brad Maxwell Assignee: Darran Lofthouse LDAP authentication/authorization fails due to making unneeded role lookup requests -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1202) LDAP authentication/authorization fails due to making unneeded role lookup requests

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1202?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated WFCORE-1202: -------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1196343 Bugzilla Update: Perform > LDAP authentication/authorization fails due to making unneeded role lookup requests > ----------------------------------------------------------------------------------- > > Key: WFCORE-1202 > URL: https://issues.jboss.org/browse/WFCORE-1202 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Brad Maxwell > Assignee: Darran Lofthouse > > LDAP authentication/authorization fails due to making unneeded role lookup requests -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1202) LDAP authentication/authorization fails due to making unneeded role lookup requests

by Brad Maxwell (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1202?page=com.atlassian.jira.plugi... ] Brad Maxwell moved WFLY-5827 to WFCORE-1202: -------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-1202 (was: WFLY-5827) Component/s: Security (was: Security) > LDAP authentication/authorization fails due to making unneeded role lookup requests > ----------------------------------------------------------------------------------- > > Key: WFCORE-1202 > URL: https://issues.jboss.org/browse/WFCORE-1202 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Brad Maxwell > Assignee: Darran Lofthouse > > LDAP authentication/authorization fails due to making unneeded role lookup requests -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5827) LDAP authentication/authorization fails due to making unneeded role lookup requests

by Brad Maxwell (JIRA)

Brad Maxwell created WFLY-5827: ---------------------------------- Summary: LDAP authentication/authorization fails due to making unneeded role lookup requests Key: WFLY-5827 URL: https://issues.jboss.org/browse/WFLY-5827 Project: WildFly Issue Type: Bug Components: Security Reporter: Brad Maxwell Assignee: Darran Lofthouse LDAP authentication/authorization fails due to making unneeded role lookup requests -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-995) Expose rule attributes of RuleImpl via API

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-995?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-995: ---------------------------------- Assignee: Mario Fusco (was: Duncan Doyle) > Expose rule attributes of RuleImpl via API > ------------------------------------------ > > Key: DROOLS-995 > URL: https://issues.jboss.org/browse/DROOLS-995 > Project: Drools > Issue Type: Feature Request > Components: core engine > Affects Versions: 6.3.0.Final > Environment: Mac OS 10.11.1, Drools 6.4.0-SNAPSHOT > Reporter: Duncan Doyle > Assignee: Mario Fusco > Priority: Minor > Fix For: 6.4.x > > > I've got a use-case where I, at runtime, want to inspect the rule-attributes of our rules (e.g. salience, ruleflow-group, etc.) via the Drools API. Currently, the only way to retrieve that kind of information is via the internal Drools API, ie. org.drools.core.definitions.rule.impl.RuleImpl. > It would be nice if we could expose these rule attributes via a public API. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

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

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1201?page=com.atlassian.jira.plugi... ] Tomaz Cerar reassigned WFCORE-1201: ----------------------------------- Assignee: (was: Stuart Douglas) > 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 > > 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)

10 years, 7 months

1
0
0 / 0

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

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1201?page=com.atlassian.jira.plugi... ] Tomaz Cerar commented on WFCORE-1201: ------------------------------------- 1) can you reproduce this problem with WildFly 10 CR4? 2) how can this be reproduced? > 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: Stuart Douglas > > 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)

10 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2015