October 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1902) Error messages from CLI batch should be more informative

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1902?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1902: ------------------------------------------ Trying to figure out what line in a script sounds like more trouble than it is worth. If it's possible to report the batch step number and the operation invoked by that step, I think that would provide most of the value. Seeing that :readAttribute(name=nonsence) failed should provide enough insight to let people figure out what line in a script was at fault. Side note: be cautious about using DMR syntax to report high level failures that aren't simply showing the output of the low level failure. AFAIK we don't do that elsewhere and it's probably not something we should do on a case by case basis without an overall strategy. > Error messages from CLI batch should be more informative > -------------------------------------------------------- > > Key: WFCORE-1902 > URL: https://issues.jboss.org/browse/WFCORE-1902 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Affects Versions: 3.0.0.Alpha10 > Reporter: Marek Kopecký > Assignee: Jean-Francois Denise > > *Description of problem:* > Error messages from CLI batch should be more informative > *Steps to Reproduce:* > {noformat} > cat <<EOF >a > batch > :read-attribute(name=product-version) > :read-attribute(name=product-name) > :read-attribute(name=nonsence) > :read-attribute(name=product-name) > run-batch > EOF > ./jboss-cli.sh -c --file=a > {noformat} > *Actual results:* > {noformat} > The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-3" => "WFLYCTL0201: Unknown attribute 'nonsence'"}} > {noformat} > *Expected results:* > I can imagine content like following could be helpful for troubleshooting: > {noformat} > { > "WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => { > "Operation step-3" => { > "line number" => 4 > "operation" => ":read-attribute(name=nonsence)" > "response" => "WFLYCTL0201: Unknown attribute 'nonsence'" > } > } > {noformat} -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1407) Test coverage for syslog reconnection

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1407?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1407: ------------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1311440|https://bugzilla.redhat.com/show_bug.cgi?id=1311440] from POST to MODIFIED > Test coverage for syslog reconnection > ------------------------------------- > > Key: WFCORE-1407 > URL: https://issues.jboss.org/browse/WFCORE-1407 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 2.1.0.CR2 > Reporter: Ondrej Lukas > Assignee: Ondrej Lukas > Fix For: 3.0.0.Alpha1 > > > Added test coverage for syslog reconnection issues - https://issues.jboss.org/browse/LOGMGR-123. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4133) Hanging EJB threads because of a persistent timer and failed deployment

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4133?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4133: ----------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1147948|https://bugzilla.redhat.com/show_bug.cgi?id=1147948] from POST to MODIFIED > Hanging EJB threads because of a persistent timer and failed deployment > ------------------------------------------------------------------------ > > Key: WFLY-4133 > URL: https://issues.jboss.org/browse/WFLY-4133 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Enrique González Martínez > Assignee: Enrique González Martínez > Fix For: 9.0.0.Beta1 > > > When there is a time service with pending timeouts a bad redeploy can hang worker threads in the server. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

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 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, 6 months

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, 6 months

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, 6 months

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, 6 months

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, 6 months

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, 6 months

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, 6 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 October 2016