October 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1912) Redeploy deployment if all missing dependencies for deployment are corrected

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1912?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1912: ------------------------------------------ Doesn't this already work if the rollback-on-runtime-failure=false operation header is used when the deployment is initially deployed? > Redeploy deployment if all missing dependencies for deployment are corrected > ----------------------------------------------------------------------------- > > Key: WFCORE-1912 > URL: https://issues.jboss.org/browse/WFCORE-1912 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Reporter: Miroslav Novak > Assignee: Jason Greene > > If deployment failed to deploy and later all missing dependencies for deployment are corrected then deployment would redeploy automatically. This behavior could be configurable. > For example if you deploy EJB which injects queue like: > {code} > @Resource(mappedName = "java:/jms/queue/OutQueue") > private Queue outQueue; > {code} > and administrator deploys queue later then EJB would automatically get redeployed. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1912) Redeploy deployment if all missing dependencies for deployment are corrected

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1912?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-7394 to WFCORE-1912: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-1912 (was: WFLY-7394) Component/s: Server (was: Server) Affects Version/s: (was: 10.1.0.Final) > Redeploy deployment if all missing dependencies for deployment are corrected > ----------------------------------------------------------------------------- > > Key: WFCORE-1912 > URL: https://issues.jboss.org/browse/WFCORE-1912 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Reporter: Miroslav Novak > Assignee: Jason Greene > > If deployment failed to deploy and later all missing dependencies for deployment are corrected then deployment would redeploy automatically. This behavior could be configurable. > For example if you deploy EJB which injects queue like: > {code} > @Resource(mappedName = "java:/jms/queue/OutQueue") > private Queue outQueue; > {code} > and administrator deploys queue later then EJB would automatically get redeployed. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1911) Port DeploymentScannerTestCase to upstream

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1911?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1911: ------------------------------------------ Yes. The initial test design shouldn't drive the structure of our test suite. Everything it does using Arquillian can be done using similar non-arquillian mechanisms available in core, e.g. WildFlyTestRunner. That's true for any @RunAsClient arquilian test. > Port DeploymentScannerTestCase to upstream > ------------------------------------------ > > Key: WFCORE-1911 > URL: https://issues.jboss.org/browse/WFCORE-1911 > Project: WildFly Core > Issue Type: Task > Components: Deployment Scanner, Test Suite > Reporter: Peter Palaga > Assignee: Tomas Hofman > > The EAP 6.4.x PR https://github.com/jbossas/jboss-eap/pull/2669 added the DeploymentScannerTestCase silently without porting it to upstream, thus not fulfilling the "Upstream First" requirement. Note that https://github.com/jbossas/jboss-eap/pull/2800 updates DeploymentScannerTestCase. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-7429) configurable-sasl-server-factory cannot set mechanism information

by Jan Kalina (JIRA)

Jan Kalina created WFLY-7429: -------------------------------- Summary: configurable-sasl-server-factory cannot set mechanism information Key: WFLY-7429 URL: https://issues.jboss.org/browse/WFLY-7429 Project: WildFly Issue Type: Bug Components: Security Reporter: Jan Kalina Assignee: Jan Kalina sasl-authentication-factory and sasl-server-factory creates chain of SaslServerFactories - for example ServerNameSaslServerFactory only delegates creating to following factory in chain but with rewriting of the server name. In this chain is also *SetMechanismInformationSaslServerFactory*, which call callback handler to send MechanismInformation into ServerAuthenticationContext - there it will cause state change from InactiveState to InitialState. *The problem is,* if the configurable-sasl-server-factory is used, the *SetMechanismInformationSaslServerFactory* is in chain twice. The first occurence (by sasl-authentication-factory) will cause change state to InitialState, but before the serverName+protocol is overriden by SaslServerFactories following in chain. The second occurence (by configurable-sasl-server-factory) already have serverName+protocol set, but because the ServerAuthenticationContext is already in InitialState, the exception "Too late to set" is thrown and createSaslServer returns null - fail completely. The chain of SaslServerFactories: {code:java} AuthenticationTimeoutSSF TrustManagerSSF AuthenticationCompleteSSF SetMechanismInformationSSF => cbh => InactiveState -> InitialState(undefined, null) ServerNameSSF ProtocolSSF SetMechanismInformationSSF => cbh => "Too late to set" => return null SecurityProviderSSF {code} Will have to discuss yet how to correctly solve this... (maybe consider allowing of multiple MechanismInformation setting? In current design the sasl-authentication-factory cannot detect the configurable-sasl-server-factory WILL change the MechanismInformation yet...) -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-702) configurable-sasl-server-factory cannot set mechanism information

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-702?page=com.atlassian.jira.plugin.sy... ] Jan Kalina moved WFLY-7429 to ELY-702: -------------------------------------- Project: WildFly Elytron (was: WildFly) Key: ELY-702 (was: WFLY-7429) Component/s: Authentication Client (was: Security) > configurable-sasl-server-factory cannot set mechanism information > ----------------------------------------------------------------- > > Key: ELY-702 > URL: https://issues.jboss.org/browse/ELY-702 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Reporter: Jan Kalina > Assignee: Jan Kalina > > sasl-authentication-factory and sasl-server-factory creates chain of SaslServerFactories - for example ServerNameSaslServerFactory only delegates creating to following factory in chain but with rewriting of the server name. > In this chain is also *SetMechanismInformationSaslServerFactory*, which call callback handler to send MechanismInformation into ServerAuthenticationContext - there it will cause state change from InactiveState to InitialState. > *The problem is,* if the configurable-sasl-server-factory is used, the *SetMechanismInformationSaslServerFactory* is in chain twice. The first occurence (by sasl-authentication-factory) will cause change state to InitialState, but before the serverName+protocol is overriden by SaslServerFactories following in chain. The second occurence (by configurable-sasl-server-factory) already have serverName+protocol set, but because the ServerAuthenticationContext is already in InitialState, the exception "Too late to set" is thrown and createSaslServer returns null - fail completely. > The chain of SaslServerFactories: > {code:java} > AuthenticationTimeoutSSF > TrustManagerSSF > AuthenticationCompleteSSF > SetMechanismInformationSSF => cbh => InactiveState -> InitialState(undefined, null) > ServerNameSSF > ProtocolSSF > SetMechanismInformationSSF => cbh => "Too late to set" => return null > SecurityProviderSSF > {code} > Will have to discuss yet how to correctly solve this... (maybe consider allowing of multiple MechanismInformation setting? In current design the sasl-authentication-factory cannot detect the configurable-sasl-server-factory WILL change the MechanismInformation yet...) -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-7428) Add ExtendedJBossXATerminator service to the transactions subsystem

by Gytis Trikleris (JIRA)

Gytis Trikleris created WFLY-7428: ------------------------------------- Summary: Add ExtendedJBossXATerminator service to the transactions subsystem Key: WFLY-7428 URL: https://issues.jboss.org/browse/WFLY-7428 Project: WildFly Issue Type: Enhancement Components: Transactions Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 11.0.0.Alpha1 ExtendedJBossXATerminator from Narayana SPI is not currently injectable as a service. However, it is needed to check if the specific transaction is available in the server. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-7427) CMTTxInterceptor transaction comparison

by Tomasz Adamski (JIRA)

[ https://issues.jboss.org/browse/WFLY-7427?page=com.atlassian.jira.plugin.... ] Tomasz Adamski closed WFLY-7427. -------------------------------- Resolution: Duplicate Issue > CMTTxInterceptor transaction comparison > --------------------------------------- > > Key: WFLY-7427 > URL: https://issues.jboss.org/browse/WFLY-7427 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.1.0.CR1 > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-7389) Improve undefined statistics-enabled attribute testing in infinispan subsystem for EAP 6.2

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-7389?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-7389: --------------------------------- Summary: Improve undefined statistics-enabled attribute testing in infinispan subsystem for EAP 6.2 (was: Improve undefined statistics-enabled attribute testing in infnispan subsystem for EAP 6.2) > Improve undefined statistics-enabled attribute testing in infinispan subsystem for EAP 6.2 > ------------------------------------------------------------------------------------------ > > Key: WFLY-7389 > URL: https://issues.jboss.org/browse/WFLY-7389 > Project: WildFly > Issue Type: Task > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > > The test file clustering/infinispan/extension/src/test/resources/org/jboss/as/clustering/infinispan/subsystem/infinispan-transformer-reject.xml specifies {code}statistics-enabled="false"{code} for all caches and cache-containers thus the situation when its undefined is never tested. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-7389) Improve undefined statistics-enabled attribute testing in infnispan subsystem for EAP 6.2

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-7389?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-7389: --------------------------------- Affects Version/s: 10.1.0.Final > Improve undefined statistics-enabled attribute testing in infnispan subsystem for EAP 6.2 > ----------------------------------------------------------------------------------------- > > Key: WFLY-7389 > URL: https://issues.jboss.org/browse/WFLY-7389 > Project: WildFly > Issue Type: Task > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > > The test file clustering/infinispan/extension/src/test/resources/org/jboss/as/clustering/infinispan/subsystem/infinispan-transformer-reject.xml specifies {code}statistics-enabled="false"{code} for all caches and cache-containers thus the situation when its undefined is never tested. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-7389) Improve undefined statistics-enabled attribute testing in infnispan subsystem for EAP 6.2

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-7389?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-7389: --------------------------------- Affects Version/s: 10.0.0.Final (was: 10.1.0.Final) > Improve undefined statistics-enabled attribute testing in infnispan subsystem for EAP 6.2 > ----------------------------------------------------------------------------------------- > > Key: WFLY-7389 > URL: https://issues.jboss.org/browse/WFLY-7389 > Project: WildFly > Issue Type: Task > Components: Clustering > Affects Versions: 10.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > > The test file clustering/infinispan/extension/src/test/resources/org/jboss/as/clustering/infinispan/subsystem/infinispan-transformer-reject.xml specifies {code}statistics-enabled="false"{code} for all caches and cache-containers thus the situation when its undefined is never tested. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2016