June 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1563) Failed CLI batch command with "deploy --force" for replace deployment

by ted won (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1563?page=com.atlassian.jira.plugi... ] ted won closed WFCORE-1563. --------------------------- > Failed CLI batch command with "deploy --force" for replace deployment > --------------------------------------------------------------------- > > Key: WFCORE-1563 > URL: https://issues.jboss.org/browse/WFCORE-1563 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.1.0.Final, 3.0.0.Alpha1 > Reporter: ted won > Assignee: ted won > Priority: Minor > Labels: cli, jboss > Fix For: 2.2.0.CR2, 3.0.0.Alpha2 > > Attachments: jboss-ejb-in-ear.ear > > > Using 'deploy --force' command on CLI batch mode fails and returns an error message: "Request is missing the address part." > {code:title=Command} > jboss-cli.sh --connect --controller=127.0.0.1:9999 --user=admin --password=xxx --file="deploy.cli" > {code} > {code:title=deploy.cli} > batch > deploy --force ./jboss-ejb-in-ear.ear > run-batch > {code} > {panel:title=Full Error message} > Failed to handle 'run-batch': org.jboss.as.cli.CommandFormatException: Request is missing the address part.: Request is missing the address part. > or > The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): Request is missing the address part. > {panel} > {panel:title=Expected message} > The batch executed successfully > {panel} > However, it's working in "WildFly 10 CLI interactive mode" and "JBoss AS 7 CLI batch" without error. > There is no adding "address" key in buildDeploymentReplace() of DeployHandler like below. > Even though on CLI batch mode it validates existence of "address" key in request with Util.validateRequest(), when 'run-batch' command execute in org.jboss.as.cli.handlers.batch.BatchRunHandler.doHandle() > ------------------------------------------------------------------------------------------- > * First deploy: add by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentAdd() > {code} > { > "operation" => "add", > "address" => {"deployment" => "jboss-ejb-in-ear.ear"}, > "content" => [{"bytes" => bytes { > ... > }}] > } > {code} > ------------------------------------------------------------------------------------------- > * After deploy: replace by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace() > {code} > { > "operation" => "full-replace-deployment", > "name" => "jboss-ejb-in-ear.ear", > "enabled" => true, > "content" => [{"bytes" => bytes { > ... > }}] > } > {code} > ------------------------------------------------------------------------------------------- > * Expected by org.jboss.as.cli.handlers.DeployHandler.buildDeploymentReplace() > {code} > { > "operation" => "full-replace-deployment", > "name" => "jboss-ejb-in-ear.ear", > "address" => [], > "enabled" => true, > "content" => [{"bytes" => bytes { > ... > }}] > } > {code} > ------------------------------------------------------------------------------------------- -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6441) naming context is not setup when starting the persistence unit

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-6441?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-6441: ----------------------------------------------- Chao Wang <chaowan(a)redhat.com> changed the Status of [bug 1320132|https://bugzilla.redhat.com/show_bug.cgi?id=1320132] from ASSIGNED to POST > naming context is not setup when starting the persistence unit > -------------------------------------------------------------- > > Key: WFLY-6441 > URL: https://issues.jboss.org/browse/WFLY-6441 > Project: WildFly > Issue Type: Enhancement > Components: JPA / Hibernate > Affects Versions: JBoss AS7 7.1.1.Final, JBoss AS7 7.2.0.Final, 9.0.2.Final, 10.0.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 10.1.0.Final > > > ookup of env-entry throws NameNotFoundException during persistence unit startup > Version-Release number of selected component (if applicable): > How reproducible: > always > Steps to Reproduce: > 1. add env-entry in application.xml > 2. try to lookup during persistent unit startup, e.g. > public class MyType implements UserType { > ... > @Override > public int[] sqlTypes() { > try { > Object ctx = new InitialContext().lookup("java:app/env"); > log.info("java:app/env from JPA = " + ctx); > } catch (Exception e) { > log.error("unable to get java:app/env from JPA", e); > } > return new int[] { Types.VARCHAR }; > } > Actual results: > NameNotFoundException > Expected results: > value of env-entry is available > Additional info: > On 21.03.2016 23:47, Stuart Douglas wrote: > > This should fix it (I think): https://github.com/stuartwdouglas/wildfly/tree/jpa-java-namespace > > > > Stuart -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6441) naming context is not setup when starting the persistence unit

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-6441?page=com.atlassian.jira.plugin.... ] Scott Marlow closed WFLY-6441. ------------------------------ Resolution: Done > naming context is not setup when starting the persistence unit > -------------------------------------------------------------- > > Key: WFLY-6441 > URL: https://issues.jboss.org/browse/WFLY-6441 > Project: WildFly > Issue Type: Enhancement > Components: JPA / Hibernate > Affects Versions: JBoss AS7 7.1.1.Final, JBoss AS7 7.2.0.Final, 9.0.2.Final, 10.0.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 10.1.0.Final > > > ookup of env-entry throws NameNotFoundException during persistence unit startup > Version-Release number of selected component (if applicable): > How reproducible: > always > Steps to Reproduce: > 1. add env-entry in application.xml > 2. try to lookup during persistent unit startup, e.g. > public class MyType implements UserType { > ... > @Override > public int[] sqlTypes() { > try { > Object ctx = new InitialContext().lookup("java:app/env"); > log.info("java:app/env from JPA = " + ctx); > } catch (Exception e) { > log.error("unable to get java:app/env from JPA", e); > } > return new int[] { Types.VARCHAR }; > } > Actual results: > NameNotFoundException > Expected results: > value of env-entry is available > Additional info: > On 21.03.2016 23:47, Stuart Douglas wrote: > > This should fix it (I think): https://github.com/stuartwdouglas/wildfly/tree/jpa-java-namespace > > > > Stuart -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6667) Servlet attributes are not availble in undertow-handlers.conf as it runs too early

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-6667?page=com.atlassian.jira.plugin.... ] Stuart Douglas reassigned WFLY-6667: ------------------------------------ Component/s: Web (Undertow) Assignee: Stuart Douglas (was: Jason Greene) > Servlet attributes are not availble in undertow-handlers.conf as it runs too early > ---------------------------------------------------------------------------------- > > Key: WFLY-6667 > URL: https://issues.jboss.org/browse/WFLY-6667 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Final > Reporter: Stuart Douglas > Assignee: Stuart Douglas > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6667) Servlet attributes are not availble in undertow-handlers.conf as it runs too early

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-6667: ------------------------------------ Summary: Servlet attributes are not availble in undertow-handlers.conf as it runs too early Key: WFLY-6667 URL: https://issues.jboss.org/browse/WFLY-6667 Project: WildFly Issue Type: Bug Affects Versions: 10.0.0.Final Reporter: Stuart Douglas Assignee: Jason Greene -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6668) Servlet attributes are not availble in undertow-handlers.conf as it runs too early

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-6668: ------------------------------------ Summary: Servlet attributes are not availble in undertow-handlers.conf as it runs too early Key: WFLY-6668 URL: https://issues.jboss.org/browse/WFLY-6668 Project: WildFly Issue Type: Bug Affects Versions: 10.0.0.Final Reporter: Stuart Douglas Assignee: Jason Greene -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-535) Add the ability to handle password updates and resets for the OTP SASL mechanism

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/ELY-535?page=com.atlassian.jira.plugin.sy... ] Farah Juma commented on ELY-535: -------------------------------- As mentioned in [PR #441|https://github.com/wildfly-security/wildfly-elytron/pull/441], instead of using events, we can add a method to {{RealmIdentity}} to handle updating a credential. > Add the ability to handle password updates and resets for the OTP SASL mechanism > -------------------------------------------------------------------------------- > > Key: ELY-535 > URL: https://issues.jboss.org/browse/ELY-535 > Project: WildFly Elytron > Issue Type: Feature Request > Components: SASL > Reporter: Farah Juma > Assignee: Farah Juma > > For the OTP SASL mechanism, the stored credential needs to be updated once a guess has been verified. In the standard case, this involves updating the stored hash based on the guess and decrementing the sequence number by 1. The OTP SASL mechanism also supports OTP sequence resets, where a user provides both a guess and a new OTP password with new parameters. If verification of the guess succeeds, then the stored credential is updated based on the new password and new parameters. However, if verification of the guess succeeds but the new password/parameters are invalid, then the stored hash is updated based on the guess and the sequence number is decremented by 1, as in the non-reset case (note that SASL auth fails in this case though). > PR #277 [adds handling|https://github.com/kabir/wildfly-elytron/blob/otp-test/src/main/...] for a {{CredentialUpdateCallback}} in {{ServerAuthenticationContext}}. This is used to handle both the OTP sequence reset case as well as the non-reset case. Instead of manipulating the realm identity directly in the SAC callback handler, we should be able to make use of [realm events|https://github.com/wildfly-security/wildfly-elytron/pull/295] so that the realm itself can handle OTP updates and resets. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-551) Add the ability to specify a one-time password or pass phrase via AuthenticationConfiguration

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/ELY-551?page=com.atlassian.jira.plugin.sy... ] Farah Juma updated ELY-551: --------------------------- Description: This is needed for the OTP SASL mechanism. We also need to be able to specify a new one-time password (and parameters) or a new pass phrase for OTP sequence re-initializations. (was: This is needed for the OTP SASL mechanism.) > Add the ability to specify a one-time password or pass phrase via AuthenticationConfiguration > --------------------------------------------------------------------------------------------- > > Key: ELY-551 > URL: https://issues.jboss.org/browse/ELY-551 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Authentication Client > Reporter: Farah Juma > Assignee: Farah Juma > > This is needed for the OTP SASL mechanism. We also need to be able to specify a new one-time password (and parameters) or a new pass phrase for OTP sequence re-initializations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6510) HHH-10679: Subselect not used when batch loading by id

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-6510?page=com.atlassian.jira.plugin.... ] Scott Marlow closed WFLY-6510. ------------------------------ Release Notes Text: Closing as a duplicate of issue HHH-10679 Resolution: Duplicate Issue > HHH-10679: Subselect not used when batch loading by id > ------------------------------------------------------ > > Key: WFLY-6510 > URL: https://issues.jboss.org/browse/WFLY-6510 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 10.0.0.Final > Reporter: Stephen Fikes > Assignee: Scott Marlow > > Subselect not used when batch loading by id -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-551) Add the ability to specify a one-time password or pass phrase via AuthenticationConfiguration

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/ELY-551?page=com.atlassian.jira.plugin.sy... ] Farah Juma updated ELY-551: --------------------------- Summary: Add the ability to specify a one-time password or pass phrase via AuthenticationConfiguration (was: Add the ability to specify a one-time password or pass phrase to AuthenticationConfiguration) > Add the ability to specify a one-time password or pass phrase via AuthenticationConfiguration > --------------------------------------------------------------------------------------------- > > Key: ELY-551 > URL: https://issues.jboss.org/browse/ELY-551 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Authentication Client > Reporter: Farah Juma > Assignee: Farah Juma > > This is needed for the OTP SASL mechanism. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2016