March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8485) Upgrade Narayana to 5.5.6.Final

by Tom Jenkinson (JIRA)

Tom Jenkinson created WFLY-8485: ----------------------------------- Summary: Upgrade Narayana to 5.5.6.Final Key: WFLY-8485 URL: https://issues.jboss.org/browse/WFLY-8485 Project: WildFly Issue Type: Component Upgrade Components: Transactions Reporter: Tom Jenkinson Assignee: Tom Jenkinson -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1059) RestartParentResourceAdd/RemoveHandler should handle capability registration

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1059?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1059: ------------------------------------------ [~pferraro] is this blocking anything needed for WF 11? If not I want to reschedule it to 4. > RestartParentResourceAdd/RemoveHandler should handle capability registration > ---------------------------------------------------------------------------- > > Key: WFCORE-1059 > URL: https://issues.jboss.org/browse/WFCORE-1059 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.0.0.CR6 > Reporter: Paul Ferraro > Assignee: Tomaz Cerar > Fix For: 3.0.0.Beta13 > > > RestartParentResourceAddHandler and RestartParentResourceRemoveHandler do not extend the respective AbstractAddStepHandler and AbstractRemoveStepHandler base classes, and thus does not handle capability [un]registration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1960) Get rid of attributes of type LIST of PROPERTY; use OBJECT of STRING

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1960?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1960: ------------------------------------- Fix Version/s: 4.0.0.Alpha1 (was: 3.0.0.Beta13) > Get rid of attributes of type LIST of PROPERTY; use OBJECT of STRING > -------------------------------------------------------------------- > > Key: WFCORE-1960 > URL: https://issues.jboss.org/browse/WFCORE-1960 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Ken Wills > Fix For: 4.0.0.Alpha1 > > Attachments: rrd.txt > > > A read-resource-description output of a standalone-full-ha.xml server (see attached) shows a couple attributes that are of type LIST, value-type PROPERTY. (Just text search for PROPERTY.) We should convert those to OBJECT, value-type STRING. Both represent a resource address. An object of string is equivalent to a LinkedHashMap<String, String>, with ordering based on insertion. So such a description is fine for a path address attribute. > I'd like to get rid of the notion of PROPERTY in our spec definition of how to describe attributes, parameters and value-types (https://docs.jboss.org/author/display/WFLY/Description+of+the+Management+...) so removing the only usage of it will help. > We should still accept PROPERTY as inputs when we can do conversion to the defined type. This is all about tightening up the spec to remove the not-really-necessary PROPERTY concept. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2385) There are two different error messages for adding duplicate record to CS by same command.

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2385?page=com.atlassian.jira.plugi... ] Michal Petrov updated WFCORE-2385: ---------------------------------- Git Pull Request: https://github.com/wildfly-security-incubator/wildfly-core/pull/113 (was: https://github.com/wildfly/wildfly-core/pull/2301) > There are two different error messages for adding duplicate record to CS by same command. > ----------------------------------------------------------------------------------------- > > Key: WFCORE-2385 > URL: https://issues.jboss.org/browse/WFCORE-2385 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Michal Petrov > > There are two different error messages for adding duplicate record to CS by same command. > *How to reproduce* > {code} > /subsystem=elytron/credential-store=cs007:add(uri="cr-store://test/customcredCS007.jceks?create.storage=true", credential-reference={clear-text=pass123}) > {code} > {code} > /subsystem=elytron/credential-store=cs007/alias=alias001:add(secret-value=secret) > {code} > And now we try add there same alias with exactly same name and with name in uppercase > {code} > /subsystem=elytron/credential-store=cs007/alias=alias001:add(secret-value=secret) > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0212: Duplicate resource [ > (\"subsystem\" => \"elytron\"), > (\"credential-store\" => \"cs007\"), > (\"alias\" => \"alias001\") > ]", > "rolled-back" => true > } > {code} > {code} > /subsystem=elytron/credential-store=cs007/alias=ALIAS001:add(secret-value=secret) > { > "outcome" => "failed", > "failure-description" => "WFLYELY00913: Credential alias \"alias001\" of credential type \"org.wildfly.security.credential.PasswordCredential\" already exists in the store", > "rolled-back" => true > } > {code} > You can see different error message. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-72) Polarion data cleanup

by Sunil kondkar (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-72?page=com.atlassian.jira.plu... ] Sunil kondkar resolved HAWKULARQE-72. ------------------------------------- Resolution: Done > Polarion data cleanup > --------------------- > > Key: HAWKULARQE-72 > URL: https://issues.jboss.org/browse/HAWKULARQE-72 > Project: Hawkular QE > Issue Type: Task > Reporter: Sunil kondkar > Assignee: Sunil kondkar > > Task to able to have polarion reports in place. > Reports: > 1) PQI Metrics: https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/wiki/... > 2) Standard Reports: https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/wiki/... > 3) Test Run Status by Plan > 4) Test Run Status by Plan and chosen fields > Tasks: > 1) Find and remove duplicates > 2) Each test case has correct fields > * Description > * Level > * Test type and sub type > * Automated or Manual > * Importance (Severity) > 3) Do we need to create a plan in below link? (Like EAP team has release plans created that are used in reports ' Test Run Status by Plan' and 'Test Run Status by Plan and chosen fields' ) > Link: https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/plans > 4) Check if manual test cases are with approved status( Approve if needed) > 5) All automated tests (CF-UI test and CFME tests) - need to be changed to Approved from 'Draft' status. > (Need to check if we can have the polarion export job marking it Approved while executed going forward?) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-72) Polarion data cleanup

by Sunil kondkar (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-72?page=com.atlassian.jira.plu... ] Sunil kondkar commented on HAWKULARQE-72: ----------------------------------------- -Some research on reports based on plans, added plans and child iterations in Polarion. https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/plans -Some maintenance on existing test runs, linked test runs to respective iterations in Polarion. -Reports can be generated now based on plans: https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/wiki/... > Polarion data cleanup > --------------------- > > Key: HAWKULARQE-72 > URL: https://issues.jboss.org/browse/HAWKULARQE-72 > Project: Hawkular QE > Issue Type: Task > Reporter: Sunil kondkar > Assignee: Sunil kondkar > > Task to able to have polarion reports in place. > Reports: > 1) PQI Metrics: https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/wiki/... > 2) Standard Reports: https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/wiki/... > 3) Test Run Status by Plan > 4) Test Run Status by Plan and chosen fields > Tasks: > 1) Find and remove duplicates > 2) Each test case has correct fields > * Description > * Level > * Test type and sub type > * Automated or Manual > * Importance (Severity) > 3) Do we need to create a plan in below link? (Like EAP team has release plans created that are used in reports ' Test Run Status by Plan' and 'Test Run Status by Plan and chosen fields' ) > Link: https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/plans > 4) Check if manual test cases are with approved status( Approve if needed) > 5) All automated tests (CF-UI test and CFME tests) - need to be changed to Approved from 'Draft' status. > (Need to check if we can have the polarion export job marking it Approved while executed going forward?) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8484) Dead Links

by David Hladky (JIRA)

David Hladky created WFLY-8484: ---------------------------------- Summary: Dead Links Key: WFLY-8484 URL: https://issues.jboss.org/browse/WFLY-8484 Project: WildFly Issue Type: Bug Components: Documentation Reporter: David Hladky Quoting [https://engineering.redhat.com/rt/Ticket/Display.html?id=442077] {quote} https://docs.jboss.org/author/display/WFLY8/Helloworld+quickstart https://docs.jboss.org/author/display/WFLY8/The+helloworld+example+in+depth have broken links Yan B. {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8483) Upgrade IronJacamar to 1.4.3 from 1.4.2

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/WFLY-8483?page=com.atlassian.jira.plugin.... ] Stefano Maestri moved JBEAP-10059 to WFLY-8483: ----------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8483 (was: JBEAP-10059) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JCA (was: JCA) Fix Version/s: (was: 7.1.0.DR12) > Upgrade IronJacamar to 1.4.3 from 1.4.2 > --------------------------------------- > > Key: WFLY-8483 > URL: https://issues.jboss.org/browse/WFLY-8483 > Project: WildFly > Issue Type: Component Upgrade > Components: JCA > Reporter: Stefano Maestri > Assignee: Stefano Maestri > > This is needed to adjust the SPI needed for the Elytron integration for the three JCA subsystems -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1338) CheckValidConnectionSQL can open a transaction, preventing application from changing transaction isolation level (PostgreSQL)

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1338?page=com.atlassian.jira.plugin... ] Tomas Hofman commented on JBJCA-1338: ------------------------------------- New PR with solution #2 from previous post: https://github.com/ironjacamar/ironjacamar/pull/623 > CheckValidConnectionSQL can open a transaction, preventing application from changing transaction isolation level (PostgreSQL) > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBJCA-1338 > URL: https://issues.jboss.org/browse/JBJCA-1338 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: 1.2.7.Final > Reporter: Tomas Hofman > Assignee: Tomas Hofman > > PostgreSQL driver only allows changing the transaction isolation level when transaction is not opened. Under certain circumstances, an application can receive a connection with already opened transaction and an attempt to change transaction isolation level will lead to exception. > This happens with the PostgreSQL driver and with CheckValidConnectionSQL checker configured to run a select statement to verify connections retrieved from the pool. > The scenario is as follows: > # A connection is retrieved from the pool for the 1st app and CheckValidConnectionSQL verifies it by running a select statement (autocommit is set to true by default). This statement is run directly via the jdbc connection, not the wrapper. > # 1st app receives the connection, sets autocommit=false, perform some work and commits a transaction. > # The connection is returned to the pool, {{cleanup()}} method is called on LocalManagedConnection wrapper, which sets autocommit=true. This however doesn't reset autocommit on the wrapped jdbc connection yet, which would only happen just before executing another SQL statement f.i. > # The same connection is retrieved from the pool for the 2nd app and CheckValidConnectionSQL runs the query. Because the jdbc connection has still autocommit=false, new transaction is opened. > # 2nd app receives the connection and calls {{setTransactionIsolation()}}, which throws an exception because the transaction is open. > Possible solution could be that the {{cleanup()}} method propagates the autocommit=true to the wrapped jdbc connection immediately. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-1) [QE] - JMAN4-111 - Immutability of JBoss Middleware services running in containers

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-1?page=com.atlassian.jira.plug... ] Hayk Hovsepyan commented on HAWKULARQE-1: ----------------------------------------- Tested on upstream MiQ with EAP7 installed and manually configured from zip file. When immutable="true" it hides the menu operations from MiQ UI. Waiting for downstream productized version to test on. > [QE] - JMAN4-111 - Immutability of JBoss Middleware services running in containers > ---------------------------------------------------------------------------------- > > Key: HAWKULARQE-1 > URL: https://issues.jboss.org/browse/HAWKULARQE-1 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Blocker > Labels: mm-integration-hawkular-qe > > See [JMAN4-111|https://issues.jboss.org/browse/JMAN4-111] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

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 March 2017