December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1226) undeploying disabled deployment stops service for same runtime-name in DeploymentUndeployHandler

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1226?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1226: ------------------------------------------------- Abhijit humbe <abhumbe(a)redhat.com> changed the Status of [bug 1280262|https://bugzilla.redhat.com/show_bug.cgi?id=1280262] from NEW to CLOSED > undeploying disabled deployment stops service for same runtime-name in DeploymentUndeployHandler > ------------------------------------------------------------------------------------------------- > > Key: WFCORE-1226 > URL: https://issues.jboss.org/browse/WFCORE-1226 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.0.4.Final > Reporter: Chao Wang > Assignee: Chao Wang > Fix For: 2.0.6.Final > > Attachments: WFCORE-1226-wildflytest.patch, WFCORE-1226.patch > > > {noformat} > 1. Start EAP 6.4.4 in domain mode and deploy application using following CLI command: > ~~ > [domain@localhost:9999 /] deploy /Applications/WebApp-1.war --server-groups=main-server-group --name=WebApp-1.war --runtime-name=WebApp-1.war > ~~~ > 2. Deploy next version of application in "disabled" state with same "runtime-name" > ~~~ > [domain@localhost:9999 /] deploy /Applications/WebApp-2.war --disabled --name=WebApp-2.war --runtime-name=WebApp-1.war > ~~~ > 3. Now use replace-deployment command to access latest version of application: > ~~~ > [domain@localhost:9999 /] /server-group=main-server-group:replace-deployment(name=WebApp-2.war,to-replace=WebApp-1.war) > ~~~ > its working fine,laest version of application is accessable. > 4. Now try to undeploy old version of application > ~~~ > /server-group=main-server-group/deployment=WebApp-1.war:undeploy() > ~~~ > After undploying older version, we are not able to access(404) latest version of application(WebApp-2.war) as well.To access it we have to redeploy it. > Same steps are working fine in Standalone mode. > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9602) Smarter range validation error messages

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-9602: -------------------------------------- Summary: Smarter range validation error messages Key: WFLY-9602 URL: https://issues.jboss.org/browse/WFLY-9602 Project: WildFly Issue Type: Enhancement Components: Domain Management Reporter: Brian Stansberry Priority: Minor A message like this is kind of silly: "Value must be between 0 and 9007199254740991". Smarter would be the ParameterValidator code that detects the message checking if the range max is Integer.MAX_INT (for an int) or Long.MAX_LONG (for a long) and if the bad value is below the max, just saying the equivalent of "Value must be greater than %d". -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9598) Clustering Testsuite 2.0: CLI, no ant, no XSLT, 3-node DIST testing

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9598?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9598: --------------------------------- Summary: Clustering Testsuite 2.0: CLI, no ant, no XSLT, 3-node DIST testing (was: Clustering Testsuite 2.0: no ant, CLI, 3-node DIST testing) > Clustering Testsuite 2.0: CLI, no ant, no XSLT, 3-node DIST testing > ------------------------------------------------------------------- > > Key: WFLY-9598 > URL: https://issues.jboss.org/browse/WFLY-9598 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Fix For: 12.0.0.Alpha1 > > > For starters, move the testsuite away from using XSLT and just rely on the CLI scripts. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-163) Monthly file rotation will continually overwrite the rotated log file

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-163?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on LOGMGR-163: ------------------------------------------------ Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1468746|https://bugzilla.redhat.com/show_bug.cgi?id=1468746] from VERIFIED to CLOSED > Monthly file rotation will continually overwrite the rotated log file > --------------------------------------------------------------------- > > Key: LOGMGR-163 > URL: https://issues.jboss.org/browse/LOGMGR-163 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Perkins > Assignee: James Perkins > Priority: Blocker > Fix For: 1.1.2.CR1, 1.2.3.GA, 1.3.3.Final, 1.4.4.Final, 1.5.8.Final, 2.0.7.Final, 2.1.0.Alpha2 > > > When the next rollover time is calculated a {{java.util.Calendar}} is used. When rotated monthly the day of the week is set to 0 and 1 month is added. This causes the calendar to be set to the last day of the current month. > On the last day of the month this also causes the file to continually rotate with each log message written, overwriting the previous log message. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2240) Log a warning if no binding port in TCP is provided

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2240?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2240: --------------------------- Fix Version/s: 4.0.10 > Log a warning if no binding port in TCP is provided > --------------------------------------------------- > > Key: JGRP-2240 > URL: https://issues.jboss.org/browse/JGRP-2240 > Project: JGroups > Issue Type: Enhancement > Affects Versions: 4.0.9 > Reporter: andrea tarocchi > Assignee: Bela Ban > Priority: Minor > Fix For: 4.0.10 > > > If a bind port is not defined and you don't bind (for some reason) to the default one, log a warning. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3367) Add note to elytron attributes that affects EAP configuration globally

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3367?page=com.atlassian.jira.plugi... ] Jan Kalina closed WFCORE-3367. ------------------------------ Resolution: Rejected As this change as requested more discussion and considerations then appropriate such minor improvement, rejected. > Add note to elytron attributes that affects EAP configuration globally > ---------------------------------------------------------------------- > > Key: WFCORE-3367 > URL: https://issues.jboss.org/browse/WFCORE-3367 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Affects Versions: 3.0.6.Final > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Minor > > There are some attributes in elytron subsystem which have global effect on EAP server state even in case elytron security is not utilized in any way. Those are (at least): > * disallowed-providers > * final-providers > * initial-providers > We should put some note in description of those attributes that they have global effect on EAP server and take effect even in cases elytron security is not utilized anyhow. Reason is that it might be a little confusing for customers to find and configure these attributes in elytron subsystem even in case they use just legacy security-realm. One would expect that when something is configured in elytron subsystem it has not take effect unless explicitely referenced or used (because we still have also legacy security-realm based security). It is not a perfect state/UX but as Elytron is supposed to become a common and only place for server security configuration it is understandable that all new security related things are being put there. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9593) Add clustering externalizers for InetAddress and InetSocketAddress

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-9593?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-9593: ----------------------------- Fix Version/s: 12.0.0.Alpha1 (was: 11.0.0.Final) > Add clustering externalizers for InetAddress and InetSocketAddress > ------------------------------------------------------------------ > > Key: WFLY-9593 > URL: https://issues.jboss.org/browse/WFLY-9593 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 11.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 12.0.0.Alpha1 > > > InetAddress can be marshalled as a fixed sized array depending on whether the address is IPv4 or IPv6, which can be determined by the implementation class. > InetSocketAddress can marshal its address using the InetAddress externalizer, and its port as an unsigned short. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-839) SetCredentialsConfiguration not overriding getCredentialSource()

by Martin Mazanek (JIRA)

[ https://issues.jboss.org/browse/ELY-839?page=com.atlassian.jira.plugin.sy... ] Martin Mazanek commented on ELY-839: ------------------------------------ I think this can be closed > SetCredentialsConfiguration not overriding getCredentialSource() > ---------------------------------------------------------------- > > Key: ELY-839 > URL: https://issues.jboss.org/browse/ELY-839 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client > Reporter: Darran Lofthouse > > Various methods manipulating the CredentialSource attempt to obtain the current one to add to it but as it is never returned they would always use the default one. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

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 commented on HAWKULARQE-207: ----------------------------------------- http://etherpad.corp.redhat.com/HAWKULARQE-207 > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-929) AuthenticationConfiguration uniqueness enhancements

by Martin Mazanek (JIRA)

[ https://issues.jboss.org/browse/ELY-929?page=com.atlassian.jira.plugin.sy... ] Martin Mazanek commented on ELY-929: ------------------------------------ The JavaDoc has already been added, the rest not. What is the purpose of capturing instances of Supplier-driven components? > AuthenticationConfiguration uniqueness enhancements > --------------------------------------------------- > > Key: ELY-929 > URL: https://issues.jboss.org/browse/ELY-929 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: David Lloyd > Fix For: 1.2.0.Beta12 > > > Apply some enhancements to AuthenticationConfiguration uniqueness. > * Add admonishing JavaDoc to {{useCallbackHandler}} to point out the importance of per-identity uniqueness of the callback handler > The following also may be possible and useful: > * Modify the {{AuthenticationConfiguration}} process to capture instances for {{Supplier}}-driven components at the time the configuration is used via the {{AuthenticationContextConfigurationClient}} > * Add a variation of {{useCallbackHandler}} which accepts a {{Supplier<CallbackHandler>}}, or a {{Function<T, CallbackHandler}} and a {{T}}, allowing constructor refs to be given -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 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 December 2017