May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10339) Broadcast/discovery-group resources have ambiguous requirement specs

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-10339: ----------------------------------- Summary: Broadcast/discovery-group resources have ambiguous requirement specs Key: WFLY-10339 URL: https://issues.jboss.org/browse/WFLY-10339 Project: WildFly Issue Type: Bug Components: JMS Affects Versions: 12.0.0.Final Reporter: Paul Ferraro Assignee: Jeff Mesnil Currently, the broadcast/discovery-group resources have messy requirement specs, as the capabilities that they require are dependent whether or not the jgroups-cluster attribute is defined. I suggest splitting these resources into 2: /server=*/jgroups-broadcast-group=* /server=*/jgroups-discovery-group=* which requires clustering capabilities and /server=*/socket-broadcast-group=* /server=*/socket-discovery-group=* which requires a socket-binding capability. This results in clearer requirement specs - which helps simplify the introspection of this subsystem for provisioning purposes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10338) Discovery subsystem is missing from the domain profiles

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-10338: --------------------------------------- Summary: Discovery subsystem is missing from the domain profiles Key: WFLY-10338 URL: https://issues.jboss.org/browse/WFLY-10338 Project: WildFly Issue Type: Bug Components: Build System, Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 13.0.0.Beta1 Same problem as WFCORE-3784 except in the full feature-pack. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-204) Kiali Test Mesh App fails after 60 running interruptly

by Guilherme Baufaker Rêgo (JIRA)

Guilherme Baufaker Rêgo created SWSQE-204: --------------------------------------------- Summary: Kiali Test Mesh App fails after 60 running interruptly Key: SWSQE-204 URL: https://issues.jboss.org/browse/SWSQE-204 Project: Kiali QE Issue Type: Bug Reporter: Guilherme Baufaker Rêgo Assignee: Michael Foley Attachments: istio-proxy00, istio-proxy01, istio-proxy02, istio-proxy03, istio-proxy04, istio-proxy05, kiali-test-a.out, traffic-generator.log - After running 60h ( from May 3, 2018 8:48:55 AM and first error was logged in May 05, 2018 8:49:52 PM) a kiali-test-service started to appear problems: (extracted from logs attached) 2018/05/05 20:49:52 http: panic serving 127.0.0.1:58310: runtime error: invalid memory address or nil pointer dereference Could it be a memory problem? (there is no limits applied on test mesh pods) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-35) Colors are printed in non interactive mode when echo-command is enabled

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFWIP-35?page=com.atlassian.jira.plugin.s... ] Jean-Francois Denise commented on WFWIP-35: ------------------------------------------- [~iweiss], I think it would be safer to only enable color in interactive session. So for example: - jboss-cli.sh -c - jboss-cli.sh < my file.txt Other cases (--file, --commands and programatic usage without enabling the console) should not enable colouring. I have worked on a fix for it: https://github.com/wildfly/wildfly-core/commit/4c8451196884f54558ebe6c291... You can integrate it in your PR. JF > Colors are printed in non interactive mode when echo-command is enabled > ----------------------------------------------------------------------- > > Key: WFWIP-35 > URL: https://issues.jboss.org/browse/WFWIP-35 > Project: WildFly WIP > Issue Type: Bug > Reporter: Erich Duda > Assignee: Ingo Weiss > Priority: Blocker > Labels: WFCORE-3577 > > If you execute CLI in following non-interactive way, colors are printed out. This can break users automation and do the output hard readable. > {code} > ./bin/jboss-cli.sh --file=commands.txt --echo-command > {code} > {code:title=commands.txt} > embed-server > batch > :read-attribute(name=server-state) > list-batch > run-batch > exit > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10205) Upgrade apache-cxf from 3.2.4 to 3.2.5

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-10205?page=com.atlassian.jira.plugin... ] Alessio Soldano updated WFLY-10205: ----------------------------------- Fix Version/s: 13.0.0.Beta1 > Upgrade apache-cxf from 3.2.4 to 3.2.5 > -------------------------------------- > > Key: WFLY-10205 > URL: https://issues.jboss.org/browse/WFLY-10205 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Services > Reporter: Lin Gao > Assignee: Alessio Soldano > Labels: downstream_dependency > Fix For: 13.0.0.Beta1 > > > apache-cxf needs to be upgraded to include fixes for: > * https://issues.apache.org/jira/browse/CXF-7682 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10205) Upgrade apache-cxf from 3.2.4 to 3.2.5

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-10205?page=com.atlassian.jira.plugin... ] Alessio Soldano updated WFLY-10205: ----------------------------------- Priority: Blocker (was: Major) > Upgrade apache-cxf from 3.2.4 to 3.2.5 > -------------------------------------- > > Key: WFLY-10205 > URL: https://issues.jboss.org/browse/WFLY-10205 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Services > Reporter: Lin Gao > Assignee: Alessio Soldano > Priority: Blocker > Labels: downstream_dependency > Fix For: 13.0.0.Beta1 > > > apache-cxf needs to be upgraded to include fixes for: > * https://issues.apache.org/jira/browse/CXF-7682 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3732) upgrade core to depend on aesh 1.4

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3732?page=com.atlassian.jira.plugi... ] Jean-Francois Denise updated WFCORE-3732: ----------------------------------------- Summary: upgrade core to depend on aesh 1.4 (was: upgrade core to depend on aesh 1.3) > upgrade core to depend on aesh 1.4 > ---------------------------------- > > Key: WFCORE-3732 > URL: https://issues.jboss.org/browse/WFCORE-3732 > Project: WildFly Core > Issue Type: Component Upgrade > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3732) upgrade core to depend on aesh 1.4

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3732?page=com.atlassian.jira.plugi... ] Jean-Francois Denise edited comment on WFCORE-3732 at 5/7/18 11:06 AM: ----------------------------------------------------------------------- in addition aesh-readline 1.7 and aesh-extensions 1.3 was (Author: jdenise): in addition aesh-readline 1.7 and aesh-extensions 1.2 > upgrade core to depend on aesh 1.4 > ---------------------------------- > > Key: WFCORE-3732 > URL: https://issues.jboss.org/browse/WFCORE-3732 > Project: WildFly Core > Issue Type: Component Upgrade > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10053) TM is not forward compatible

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-10053?page=com.atlassian.jira.plugin... ] David Lloyd resolved WFLY-10053. -------------------------------- Resolution: Rejected Assuming that this issue can be closed as there is not actually any compatibility regression here. > TM is not forward compatible > ----------------------------- > > Key: WFLY-10053 > URL: https://issues.jboss.org/browse/WFLY-10053 > Project: WildFly > Issue Type: Bug > Components: Transactions > Affects Versions: 12.0.0.Final > Reporter: Ivan Straka > Assignee: Tom Jenkinson > Attachments: EAP7.0.9.log, WF12.log > > > TM is unable to recover transaction after one of the nodes crash during commit phase of a resource. > Scenario: > # EAP 7.0.9 enlists dummy XA resource, update db value (XADatasource) and call WildFly 12 > # WildFly 12 enlists dummy XA resource, update other db value > # At entry of commit phase of dummy XA resource on WildFly12 byteman crash the server > # WildFly 12 is started > # Recovery process should recover the transaction > Following exception is seen in EAP 7.0.9 log > {code:java} > 2018-03-20 12:42:35,171 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016036: commit on < formatId=131077, gtrid_length=32, bqual_length=36, tx_uid=0:ffff7f000001:643452d5:5ab0f37d:f, node_name=eap1, branch_uid=0:ffff7f000001:643452d5:5ab0f37d:1e, subordinatenodename=null, eis_name=unknown eis name > (RecoveryOnlySerializedEJBXAResource{ejbReceiverNodeName='eap2'}) failed with exception $XAException.XA_RETRY: javax.transaction.xa.XAException > at org.jboss.ejb.client.RecoveryOnlySerializedEJBXAResource.commit(RecoveryOnlySerializedEJBXAResource.java:56) > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelCommit(XAResourceRecord.java:477) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doCommit(BasicAction.java:2869) > at com.arjuna.ats.arjuna.coordinator.BasicAction.doCommit(BasicAction.java:2785) > at com.arjuna.ats.arjuna.coordinator.BasicAction.phase2Commit(BasicAction.java:1853) > at com.arjuna.ats.arjuna.recovery.RecoverAtomicAction.replayPhase2(RecoverAtomicAction.java:71) > at com.arjuna.ats.internal.arjuna.recovery.AtomicActionRecoveryModule.doRecoverTransaction(AtomicActionRecoveryModule.java:152) > at com.arjuna.ats.internal.arjuna.recovery.AtomicActionRecoveryModule.processTransactionsStatus(AtomicActionRecoveryModule.java:253) > at com.arjuna.ats.internal.arjuna.recovery.AtomicActionRecoveryModule.periodicWorkSecondPass(AtomicActionRecoveryModule.java:109) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:811) > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:377) > {code} > Result is that resources on EAP7.0.9 are commited and resources on WF12 are not: > {code:java} > [INFO] there is (are) 1 transaction(s) in tx obj store /home/istraka/manu-units/tests-transactions-propagation/manu-unit-eap-transactions-propagation/out/EAP2_7.2.0/workspace/wildfly-12.0.0.Final/standalone/data/tx-object-store > [INFO] Transaction > Xid:< formatId=131077, gtrid_length=32, bqual_length=40, tx_uid=0:ffff7f000001:-174ad8d9:5ab0fb3b:f, node_name=eap1, branch_uid=0:ffff7f000001:-174ad8d9:5ab0fb3b:1e, subordinatenodename=eap2, eis_name=0 > > Type:StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/SubordinateAtomicAction/JCA > ParentNodeName:eap1 > Participant:false > CreationTime:Tue, 20 Mar 2018 13:15:18 +0100 > AgeInSeconds:269 > Id:0:ffff7f000001:39e6900e:5ab0fb4a:13 > Participant > HeuristicValue:-1 > Status:PREPARED > JndiName:java:/TestXAResource > GlobalTransactionId:[B@5753c786 > HeuristicStatus:UNKNOWN > NodeName:null > Timeout:0 > FormatId:-1 > BranchQualifier:[B@1874640 > Type:/StateManager/AbstractRecord/XAResourceRecord > Participant:true > EisProductVersion:EAP Test > ClassName:com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord > EisProductName:Crash Recovery Test > Id:0:ffff7f000001:39e6900e:5ab0fb4a:1d > Participant > HeuristicValue:-1 > Status:PREPARED > JndiName:java:jboss/eap2-ds-jndi > GlobalTransactionId:[B@4ae75d2d > HeuristicStatus:UNKNOWN > NodeName:null > Timeout:0 > FormatId:-1 > BranchQualifier:[B@5eaa38ce > Type:/StateManager/AbstractRecord/XAResourceRecord > Participant:true > EisProductVersion:9.3.15 > ClassName:com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord > EisProductName:PostgreSQL > Id:0:ffff7f000001:39e6900e:5ab0fb4a:23 > {code} > The issue is valid for: > * 6.4.x -> WF12 > * 7.0.X -> WF12 > The issue is *not* valid for: > * WF12 -> 6.4.x > * WF12-> 7.0.x > * 7.1.0 -> WF 12 > If you have any question (about testsuite, scenario,...) feel free to ask. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-199) Python Client Support Route Rule

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-199?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-199. ------------------------------------------- Resolution: Done > Python Client Support Route Rule > -------------------------------- > > Key: SWSQE-199 > URL: https://issues.jboss.org/browse/SWSQE-199 > Project: Kiali QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 May 2018