December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (HAWKULARQE-201) Middleware Events are triggered automaticaly

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-201?page=com.atlassian.jira.pl... ] Hayk Hovsepyan resolved HAWKULARQE-201. --------------------------------------- Resolution: Done Testcase is executed as of TP3 DR3 and 5.9.0.11.20171127204214_e316988 > Middleware Events are triggered automaticaly > --------------------------------------------- > > Key: HAWKULARQE-201 > URL: https://issues.jboss.org/browse/HAWKULARQE-201 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Labels: 4.6 > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-83) Create test cases for hawkular-wildfly-agent-installer.jar

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-83?page=com.atlassian.jira.plu... ] Hayk Hovsepyan resolved HAWKULARQE-83. -------------------------------------- Resolution: Done Hawkular Wildfly agent will be gone after TP3 release. Task is outdated. > Create test cases for hawkular-wildfly-agent-installer.jar > ---------------------------------------------------------- > > Key: HAWKULARQE-83 > URL: https://issues.jboss.org/browse/HAWKULARQE-83 > Project: Hawkular QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Hayk Hovsepyan > > hawkular-wildfly-agent-installer.jar has following options: > Options: > -D, --D Defines system properties to set > --installer-config Installer .properties configuration file > --encryption-key If specified, this is used to decode the properties that were encrypted. If you do not provide a value with the option, you will be prompted for one. > --encryption-salt The salt used for generating the key. Recommended, if encryption is used. If not specified, the same value as the key will be used. > --enabled Indicates if the agent should be enabled at startup > --config-only Skip installation of the add-ons modules, and only update the server config (e.g. standalone.xml). > --target-location Target home directory of the application server where the agent is to be installed > --module-dist Hawkular WildFly Agent Module distribution zip file - can be a file path or URL > --server-url Server URL where the agent will send its monitoring data. This is a string to be set as the storage adapter URL. > --download-server-url Server URL from which the installer will download content it may need. If not specified and the installer needs to download something then --server-url will be used. > --target-config The target configuration file to write to. Can be either absolute path or relative to target-location > --subsystem-snippet Customized subsystem XML content that overrides the default subsystem configuration > --managed-server-name The agent will use this name to refer to the server where it is deployed and locally managing. > --feed-id The feed ID that the agent will use to identify its data. > --tenant-id The tenant ID that the agent will ask to be used. Usually only used when in metrics-only mode. > --metrics-only If true, the agent will be configured to run in metrics-only mode (inventory will not be stored and no websocket connection to a Hawkular Server will be made.) If true, you must specify a tenant-id. > --managed-server-resource-type-sets If true, the agent will be configured to monitor these resource type sets. If not provided, a default set will be used based on the type of application server where the agent is being installed into (standalone or domain). > --keystore-path Keystore file. Required when server-url protocol is https > --keystore-password Keystore password. When server-url protocol is https and this option is not passed, installer will ask for password > --username User the agent will use when connecting to Hawkular Server. > --password Credentials agent will use when connecting to Hawkular Server. > We need to create test cases to cover that -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9594) url rewriting doesnt work in wildfly 8.2.1

by SATISH POKALWAR (JIRA)

SATISH POKALWAR created WFLY-9594: ------------------------------------- Summary: url rewriting doesnt work in wildfly 8.2.1 Key: WFLY-9594 URL: https://issues.jboss.org/browse/WFLY-9594 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 8.2.1.Final Reporter: SATISH POKALWAR Assignee: Stuart Douglas I have an application running on wildfly 8.2.1 which is upgraded from jboss 6.4. for URL rewriting in jboss 6.4 , we have virtual server section in standlone-full.xml however to do the same on wildfly 8.2.1 its been suggested to write the rule in undertow-handlers.conf and put the same in WEB-INF directory ,however that is not working.Basically i want to rewrite http://ip_address/a and http://ip_address/b to http://ip_address/c , to do the same i have written below rule in undertow-handlers.conf it is not working, regex['^/a/$'] -> rewrite['/c/$1']. Can anyone tell if am doing anything wrong , similiar rule used to work in JBOSS 6.4 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-207) Define set of acceptance tests

by Prachi Yadav (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-207?page=com.atlassian.jira.pl... ] Prachi Yadav reassigned HAWKULARQE-207: --------------------------------------- Assignee: Prachi Yadav (was: Michael Foley) > Define set of acceptance tests > ------------------------------ > > Key: HAWKULARQE-207 > URL: https://issues.jboss.org/browse/HAWKULARQE-207 > Project: Hawkular QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Prachi Yadav > Priority: Blocker > > We need a set of cases which are considered to be "must work" which will be run every time before a release. > Example from JON: > - ssl configuration was not part of such suite and because of that one ugly issue was missed which resulted in unreachable agents after upgrade and critical hot-fix > Following should be done: > * define those cases for each area > * check that those cases are created in polarion > * set the highest possible severity for those cases > * define test run which will contain all those cases for each release > * automate as much as possible > * regularly check and update the suite with new features -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-728) The map backing SimpleMapBackedSecurityRealm should be an identity map not a password map.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-728?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse commented on ELY-728: -------------------------------------- This one was just a name change of the methods to set the map from 'setPasswordMap' to 'setIdentityMap' - but now as we have to maintain compatibility we would need to add new methods and deprecate the old ones. > The map backing SimpleMapBackedSecurityRealm should be an identity map not a password map. > ------------------------------------------------------------------------------------------ > > Key: ELY-728 > URL: https://issues.jboss.org/browse/ELY-728 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI, Realms > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.2.0.Beta12 > > > This realm is useful in cases where we need an identity to exist where the mechanism has performed validation without requiring access to credentials. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1448) API Compatibility for org.wildfly.security.mechanism.MechanismUtil

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1448?page=com.atlassian.jira.plugin.s... ] Jan Kalina reassigned ELY-1448: ------------------------------- Assignee: Jan Kalina > API Compatibility for org.wildfly.security.mechanism.MechanismUtil > ------------------------------------------------------------------ > > Key: ELY-1448 > URL: https://issues.jboss.org/browse/ELY-1448 > Project: WildFly Elytron > Issue Type: Bug > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: Jan Kalina > Priority: Blocker > Fix For: 1.2.0.Beta11 > > > Backwards compatibility has been broken on the public handleCallbacks methods so this needs to be fixed. > However this class should not really be a public API, it has been picked up in the package as we have the AuthenticationMechanismException which does need to be public. > The entire class should be deprecated and the impl moved to a private package. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4947) Upgrade to Undertow 1.1.8.Final

by SATISH POKALWAR (JIRA)

[ https://issues.jboss.org/browse/WFLY-4947?page=com.atlassian.jira.plugin.... ] SATISH POKALWAR commented on WFLY-4947: --------------------------------------- Hi Team , Is it possible for URL re-writing through standalone-full.xml file like we used to do in jboss 6.4 > Upgrade to Undertow 1.1.8.Final > ------------------------------- > > Key: WFLY-4947 > URL: https://issues.jboss.org/browse/WFLY-4947 > Project: WildFly > Issue Type: Component Upgrade > Components: Web (Undertow) > Reporter: Jason Greene > Assignee: Stuart Douglas > Fix For: 8.2.1.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1448) API Compatibility for org.wildfly.security.mechanism.MechanismUtil

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1448?page=com.atlassian.jira.plugin.s... ] Jan Kalina commented on ELY-1448: --------------------------------- The API breaking is already handled by ELY-1452 - this issue should aim the class deprecating/moving into private package. > API Compatibility for org.wildfly.security.mechanism.MechanismUtil > ------------------------------------------------------------------ > > Key: ELY-1448 > URL: https://issues.jboss.org/browse/ELY-1448 > Project: WildFly Elytron > Issue Type: Bug > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Blocker > Fix For: 1.2.0.Beta11 > > > Backwards compatibility has been broken on the public handleCallbacks methods so this needs to be fixed. > However this class should not really be a public API, it has been picked up in the package as we have the AuthenticationMechanismException which does need to be public. > The entire class should be deprecated and the impl moved to a private package. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-728) The map backing SimpleMapBackedSecurityRealm should be an identity map not a password map.

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-728?page=com.atlassian.jira.plugin.sy... ] Jan Kalina commented on ELY-728: -------------------------------- So the realm should be backed by {{Map<String, SimpleMapRealmIdentity>}} instead of {{Map<String, SimpleRealmEntry>}} and creating identities on obtaining - what is the point? The realm can be used without stored credentials already now, or not? > The map backing SimpleMapBackedSecurityRealm should be an identity map not a password map. > ------------------------------------------------------------------------------------------ > > Key: ELY-728 > URL: https://issues.jboss.org/browse/ELY-728 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI, Realms > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.2.0.Beta12 > > > This realm is useful in cases where we need an identity to exist where the mechanism has performed validation without requiring access to credentials. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9509) Default SFSB Lifecycle methods transaction attribute causing warnings

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-9509?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-9509: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1508105|https://bugzilla.redhat.com/show_bug.cgi?id=1508105] from POST to MODIFIED > Default SFSB Lifecycle methods transaction attribute causing warnings > --------------------------------------------------------------------- > > Key: WFLY-9509 > URL: https://issues.jboss.org/browse/WFLY-9509 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 11.0.0.Final > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Fix For: 12.0.0.Alpha1 > > Attachments: warning-reproducer.zip > > > EJB 2 deployment that does not specify transaction attribute for lifecycle methods such as: ejbActivate, ejbRemove, ejbPassivate are logging this warning. > JBAS014279: Invalid transaction attribute type REQUIRED on SFSB lifecyle method Method ejbRemove(), valid types are REQUIRES_NEW and NOT_SUPPORTED. Method will be treated as NOT_SUPPORTED. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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