November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2045) [Deployment overlay] User is not notified when argument '--redeploy-affected' was not specified

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2045?page=com.atlassian.jira.plugi... ] Chao Wang commented on WFCORE-2045: ----------------------------------- The redeployment information is logged on the server side. On the CLI side, the help message describes --redeploy-affected parameter for each possible action. Thus, I think the proposed notification could be an enhancement rather than a bug. > [Deployment overlay] User is not notified when argument '--redeploy-affected' was not specified > ----------------------------------------------------------------------------------------------- > > Key: WFCORE-2045 > URL: https://issues.jboss.org/browse/WFCORE-2045 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Affects Versions: 3.0.0.Alpha12 > Reporter: Chao Wang > Assignee: Chao Wang > > *Problem* > When argument '--redeploy-affected' is not specified in commands where deployments are specified, > user is not informed that the changes will take effect when deployments will be redeployed. > *Proposed solution* > When command affecting deployments is executed and argument '--redeploy-affected' is not given > print message that the redeployment is needed to changes take effect. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2045) [Deployment overlay] User is not notified when argument '--redeploy-affected' was not specified

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2045?page=com.atlassian.jira.plugi... ] Chao Wang moved JBEAP-7504 to WFCORE-2045: ------------------------------------------ Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2045 (was: JBEAP-7504) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: CLI (was: CLI) (was: User Experience) Affects Version/s: 3.0.0.Alpha12 (was: 7.1.0.DR8) > [Deployment overlay] User is not notified when argument '--redeploy-affected' was not specified > ----------------------------------------------------------------------------------------------- > > Key: WFCORE-2045 > URL: https://issues.jboss.org/browse/WFCORE-2045 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Affects Versions: 3.0.0.Alpha12 > Reporter: Chao Wang > Assignee: Chao Wang > > *Problem* > When argument '--redeploy-affected' is not specified in commands where deployments are specified, > user is not informed that the changes will take effect when deployments will be redeployed. > *Proposed solution* > When command affecting deployments is executed and argument '--redeploy-affected' is not given > print message that the redeployment is needed to changes take effect. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7675) Make the changes needed to be compatible with the latest JBoss Marshalling API

by Farah Juma (JIRA)

Farah Juma created WFLY-7675: -------------------------------- Summary: Make the changes needed to be compatible with the latest JBoss Marshalling API Key: WFLY-7675 URL: https://issues.jboss.org/browse/WFLY-7675 Project: WildFly Issue Type: Task Reporter: Farah Juma Assignee: Farah Juma As part of the wildfly-naming-client integration work, we need to update to JBoss Marshalling 2.0.0. Some updates will be needed to be compatible with this new version. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7666) Authentication against HTTP management interface with empty username causes Internal Server Error (status 500)

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7666?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7666: ----------------------------------- Summary: Authentication against HTTP management interface with empty username causes Internal Server Error (status 500) (was: Login to Management Console with empty username causes Internal Server Error (status 500)) > Authentication against HTTP management interface with empty username causes Internal Server Error (status 500) > -------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7666 > URL: https://issues.jboss.org/browse/WFLY-7666 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Blocker > > In case when empty username is passed during authentication to Management Console then exception is thrown to server log and Internal Server Error (status 500) is returned to user (which leads to displaying "Connect to Management Interface" page. User is not able to try to login again. > In WildFly 10.1.0 this scenario works fine - after passing empty username during authentication, authentication failed and login window is displayed again. I request blocker due to regression. > Exception thrown to server log: > {code} > ERROR [io.undertow.request] (management task-3) UT005071: Undertow request failed HttpServerExchange{ GET /management request {Accept=[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8], Accept-Language=[en-US,en;q=0.5], Accept-Encoding=[gzip, deflate], User-Agent=[Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:44.0) Gecko/20100101 Firefox/44.0], Connection=[keep-alive], Authorization=[Digest username="", realm="ManagementRealm", nonce="AAAAAwAAAlzTPVPLC0qPi6CaEhTCHZa+QjsuAjn3OsQXcuDYAxrOtc+rRMs=", uri="/management", algorithm=MD5, response="cbd764e6c09577625476340f7bcfc84d", opaque="00000000000000000000000000000000"], Content-Type=[text/plain; charset=utf-8], Cookie=[__utma=111872281.1874867570.1477040206.1479886566.1479982414.11; __utmz=111872281.1477040206.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utmb=111872281.5.10.1479982414; __utmt=1; __utmc=111872281], Referer=[http://localhost:9990/console/App.html], Host=[localhost:9990]} response {X-Frame-Options=[SAMEORIGIN]}}: java.lang.IllegalArgumentException > at javax.security.auth.callback.NameCallback.<init>(NameCallback.java:90) > at org.wildfly.security.http.impl.DigestAuthenticationMechanism.getH_A1(DigestAuthenticationMechanism.java:233) > at org.wildfly.security.http.impl.DigestAuthenticationMechanism.validateResponse(DigestAuthenticationMechanism.java:189) > at org.wildfly.security.http.impl.DigestAuthenticationMechanism.evaluateRequest(DigestAuthenticationMechanism.java:121) > at org.wildfly.security.http.util.SetMechanismInformationMechanismFactory$1.evaluateRequest(SetMechanismInformationMechanismFactory.java:115) > at org.wildfly.security.http.util.SecurityIdentityServerMechanismFactory$1.evaluateRequest(SecurityIdentityServerMechanismFactory.java:77) > at org.wildfly.security.http.HttpAuthenticator$AuthenticationExchange.authenticate(HttpAuthenticator.java:106) > at org.wildfly.security.http.HttpAuthenticator$AuthenticationExchange.access$100(HttpAuthenticator.java:90) > at org.wildfly.security.http.HttpAuthenticator.authenticate(HttpAuthenticator.java:74) > at org.wildfly.elytron.web.undertow.server.SecurityContextImpl.authenticate(SecurityContextImpl.java:82) > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:50) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:207) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:809) > 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) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7666) Login to Management Console with empty username causes Internal Server Error (status 500)

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7666?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-7666: -------------------------------------- Assignee: Darran Lofthouse (was: Harald Pehl) > Login to Management Console with empty username causes Internal Server Error (status 500) > ----------------------------------------------------------------------------------------- > > Key: WFLY-7666 > URL: https://issues.jboss.org/browse/WFLY-7666 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Blocker > > In case when empty username is passed during authentication to Management Console then exception is thrown to server log and Internal Server Error (status 500) is returned to user (which leads to displaying "Connect to Management Interface" page. User is not able to try to login again. > In WildFly 10.1.0 this scenario works fine - after passing empty username during authentication, authentication failed and login window is displayed again. I request blocker due to regression. > Exception thrown to server log: > {code} > ERROR [io.undertow.request] (management task-3) UT005071: Undertow request failed HttpServerExchange{ GET /management request {Accept=[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8], Accept-Language=[en-US,en;q=0.5], Accept-Encoding=[gzip, deflate], User-Agent=[Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:44.0) Gecko/20100101 Firefox/44.0], Connection=[keep-alive], Authorization=[Digest username="", realm="ManagementRealm", nonce="AAAAAwAAAlzTPVPLC0qPi6CaEhTCHZa+QjsuAjn3OsQXcuDYAxrOtc+rRMs=", uri="/management", algorithm=MD5, response="cbd764e6c09577625476340f7bcfc84d", opaque="00000000000000000000000000000000"], Content-Type=[text/plain; charset=utf-8], Cookie=[__utma=111872281.1874867570.1477040206.1479886566.1479982414.11; __utmz=111872281.1477040206.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utmb=111872281.5.10.1479982414; __utmt=1; __utmc=111872281], Referer=[http://localhost:9990/console/App.html], Host=[localhost:9990]} response {X-Frame-Options=[SAMEORIGIN]}}: java.lang.IllegalArgumentException > at javax.security.auth.callback.NameCallback.<init>(NameCallback.java:90) > at org.wildfly.security.http.impl.DigestAuthenticationMechanism.getH_A1(DigestAuthenticationMechanism.java:233) > at org.wildfly.security.http.impl.DigestAuthenticationMechanism.validateResponse(DigestAuthenticationMechanism.java:189) > at org.wildfly.security.http.impl.DigestAuthenticationMechanism.evaluateRequest(DigestAuthenticationMechanism.java:121) > at org.wildfly.security.http.util.SetMechanismInformationMechanismFactory$1.evaluateRequest(SetMechanismInformationMechanismFactory.java:115) > at org.wildfly.security.http.util.SecurityIdentityServerMechanismFactory$1.evaluateRequest(SecurityIdentityServerMechanismFactory.java:77) > at org.wildfly.security.http.HttpAuthenticator$AuthenticationExchange.authenticate(HttpAuthenticator.java:106) > at org.wildfly.security.http.HttpAuthenticator$AuthenticationExchange.access$100(HttpAuthenticator.java:90) > at org.wildfly.security.http.HttpAuthenticator.authenticate(HttpAuthenticator.java:74) > at org.wildfly.elytron.web.undertow.server.SecurityContextImpl.authenticate(SecurityContextImpl.java:82) > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:50) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:207) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:809) > 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) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7666) Login to Management Console with empty username causes Internal Server Error (status 500)

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7666?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7666: ----------------------------------- Component/s: Security (was: Web Console) > Login to Management Console with empty username causes Internal Server Error (status 500) > ----------------------------------------------------------------------------------------- > > Key: WFLY-7666 > URL: https://issues.jboss.org/browse/WFLY-7666 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Blocker > > In case when empty username is passed during authentication to Management Console then exception is thrown to server log and Internal Server Error (status 500) is returned to user (which leads to displaying "Connect to Management Interface" page. User is not able to try to login again. > In WildFly 10.1.0 this scenario works fine - after passing empty username during authentication, authentication failed and login window is displayed again. I request blocker due to regression. > Exception thrown to server log: > {code} > ERROR [io.undertow.request] (management task-3) UT005071: Undertow request failed HttpServerExchange{ GET /management request {Accept=[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8], Accept-Language=[en-US,en;q=0.5], Accept-Encoding=[gzip, deflate], User-Agent=[Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:44.0) Gecko/20100101 Firefox/44.0], Connection=[keep-alive], Authorization=[Digest username="", realm="ManagementRealm", nonce="AAAAAwAAAlzTPVPLC0qPi6CaEhTCHZa+QjsuAjn3OsQXcuDYAxrOtc+rRMs=", uri="/management", algorithm=MD5, response="cbd764e6c09577625476340f7bcfc84d", opaque="00000000000000000000000000000000"], Content-Type=[text/plain; charset=utf-8], Cookie=[__utma=111872281.1874867570.1477040206.1479886566.1479982414.11; __utmz=111872281.1477040206.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utmb=111872281.5.10.1479982414; __utmt=1; __utmc=111872281], Referer=[http://localhost:9990/console/App.html], Host=[localhost:9990]} response {X-Frame-Options=[SAMEORIGIN]}}: java.lang.IllegalArgumentException > at javax.security.auth.callback.NameCallback.<init>(NameCallback.java:90) > at org.wildfly.security.http.impl.DigestAuthenticationMechanism.getH_A1(DigestAuthenticationMechanism.java:233) > at org.wildfly.security.http.impl.DigestAuthenticationMechanism.validateResponse(DigestAuthenticationMechanism.java:189) > at org.wildfly.security.http.impl.DigestAuthenticationMechanism.evaluateRequest(DigestAuthenticationMechanism.java:121) > at org.wildfly.security.http.util.SetMechanismInformationMechanismFactory$1.evaluateRequest(SetMechanismInformationMechanismFactory.java:115) > at org.wildfly.security.http.util.SecurityIdentityServerMechanismFactory$1.evaluateRequest(SecurityIdentityServerMechanismFactory.java:77) > at org.wildfly.security.http.HttpAuthenticator$AuthenticationExchange.authenticate(HttpAuthenticator.java:106) > at org.wildfly.security.http.HttpAuthenticator$AuthenticationExchange.access$100(HttpAuthenticator.java:90) > at org.wildfly.security.http.HttpAuthenticator.authenticate(HttpAuthenticator.java:74) > at org.wildfly.elytron.web.undertow.server.SecurityContextImpl.authenticate(SecurityContextImpl.java:82) > at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:50) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:207) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:809) > 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) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7674) Remove workaround for HHH-11254 following hibernate orm 5.2.5.Final upgrade

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-7674: ---------------------------------- Summary: Remove workaround for HHH-11254 following hibernate orm 5.2.5.Final upgrade Key: WFLY-7674 URL: https://issues.jboss.org/browse/WFLY-7674 Project: WildFly Issue Type: Task Components: Clustering Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 11.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7673) Upgrade Hibernate ORM to 5.2.5.Final

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-7673: ---------------------------------- Summary: Upgrade Hibernate ORM to 5.2.5.Final Key: WFLY-7673 URL: https://issues.jboss.org/browse/WFLY-7673 Project: WildFly Issue Type: Component Upgrade Components: JPA / Hibernate Reporter: Paul Ferraro Assignee: Scott Marlow Fix For: 11.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7672) Upgrade to JBoss EJB Client 3.0.0.Beta4

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-7672: -------------------------------------- Summary: Upgrade to JBoss EJB Client 3.0.0.Beta4 Key: WFLY-7672 URL: https://issues.jboss.org/browse/WFLY-7672 Project: WildFly Issue Type: Component Upgrade Components: EJB Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 11.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1326) Stateful working memory regression OCT-2016: nurserostering long_hint01.xml

by Jiri Locker (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1326?page=com.atlassian.jira.plugi... ] Jiri Locker updated DROOLS-1326: -------------------------------- Attachment: Drools1326Test.java > Stateful working memory regression OCT-2016: nurserostering long_hint01.xml > --------------------------------------------------------------------------- > > Key: DROOLS-1326 > URL: https://issues.jboss.org/browse/DROOLS-1326 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.Beta2 > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > Priority: Blocker > Attachments: Drools1326Test.java, screenshot-1.png > > > Something regressed in Drools master between 27-SEP and 11-OCT. > See: > https://kie-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/optaplanner-turtl... > I 'll ask [~jlocker] to isolate. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 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 November 2016