August 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (LOGMGR-167) Enable fallback on thread context ClassLoader for log context scanning

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-167?page=com.atlassian.jira.plugin... ] James Perkins commented on LOGMGR-167: -------------------------------------- Okay. That would be why a logging profile does not work for them then. A logging profile only works on deployments because it uses the deployments class loader. Modules would have their own class loaders. Basically anything logged from the deployment itself should use the logging profile. Any modules should use the system log context. > Enable fallback on thread context ClassLoader for log context scanning > ---------------------------------------------------------------------- > > Key: LOGMGR-167 > URL: https://issues.jboss.org/browse/LOGMGR-167 > Project: JBoss Log Manager > Issue Type: Enhancement > Reporter: James Netherton > > {{ClassLoaderLogContextSelector}} searches the call stack for a {{ClassLoader}} that's used as a map key to discover the appropriate {{LogContext}}. > If the search fails, can we add an additional check that uses the ThreadContextClassLoader to lookup the {{LogContext}} from the {{contextMap}}? > My reasoning for requesting this is described in this issue: > https://github.com/wildfly-extras/wildfly-camel/issues/1919#issuecomment-... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-167) Enable fallback on thread context ClassLoader for log context scanning

by James Netherton (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-167?page=com.atlassian.jira.plugin... ] James Netherton commented on LOGMGR-167: ---------------------------------------- Ignore the comments about race conditions, that's a bug with our Camel subsystem.... But yes, the Spring and Camel dependencies are installed as a collection of modules. > Enable fallback on thread context ClassLoader for log context scanning > ---------------------------------------------------------------------- > > Key: LOGMGR-167 > URL: https://issues.jboss.org/browse/LOGMGR-167 > Project: JBoss Log Manager > Issue Type: Enhancement > Reporter: James Netherton > > {{ClassLoaderLogContextSelector}} searches the call stack for a {{ClassLoader}} that's used as a map key to discover the appropriate {{LogContext}}. > If the search fails, can we add an additional check that uses the ThreadContextClassLoader to lookup the {{LogContext}} from the {{contextMap}}? > My reasoning for requesting this is described in this issue: > https://github.com/wildfly-extras/wildfly-camel/issues/1919#issuecomment-... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-167) Enable fallback on thread context ClassLoader for log context scanning

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-167?page=com.atlassian.jira.plugin... ] James Perkins commented on LOGMGR-167: -------------------------------------- There is a {{ContextClassLoaderLogContextSelector}} in jboss-logmanager already. However WildFly uses it's own [{{LogContextSelector}}|https://github.com/wildfly/wildfly-core/blob/master/logging/src/main/java/org/jboss/as/logging/logmanager/WildFlyLogContextSelectorImpl.java]. Registering the {{LogContext}} on WildFly is happening during the deployment processing. Nothing in the deployment itself should be invoked until deployment processing is complete so in theory there shouldn't be a race condition. Are the Spring dependencies included in the deployment or are they installed as a module? > Enable fallback on thread context ClassLoader for log context scanning > ---------------------------------------------------------------------- > > Key: LOGMGR-167 > URL: https://issues.jboss.org/browse/LOGMGR-167 > Project: JBoss Log Manager > Issue Type: Enhancement > Reporter: James Netherton > > {{ClassLoaderLogContextSelector}} searches the call stack for a {{ClassLoader}} that's used as a map key to discover the appropriate {{LogContext}}. > If the search fails, can we add an additional check that uses the ThreadContextClassLoader to lookup the {{LogContext}} from the {{contextMap}}? > My reasoning for requesting this is described in this issue: > https://github.com/wildfly-extras/wildfly-camel/issues/1919#issuecomment-... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3181) Review CustomCredentialSecurityFactoryTestCase

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-3181: ---------------------------------------- Summary: Review CustomCredentialSecurityFactoryTestCase Key: WFCORE-3181 URL: https://issues.jboss.org/browse/WFCORE-3181 Project: WildFly Core Issue Type: Bug Components: Security, Test Suite Reporter: Darran Lofthouse Fix For: 4.0.0.Alpha1 The test case CustomCredentialSecurityFactoryTestCase appears to be testing that the 'code does what it does' rather than testing the 'code is doing what it should'. The test is testing a custom credential security factory can be called but the test is using HTTP Basic authentication and relying on SPNEGO authentication being triggered as this is the only mechanism that currently uses this factory. Should a minor change be required to the SPNEGO authentication mechanism which affects when this credential factory is called this test case could subsequently fail. If possible it would be better to convert this test to be a SPNEGO test and then test the behaviour of the credential security factory affects the mechanism as expected. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8767) Changing the max-pool-size of the datasource pool should indicate a "reload required" in the CLI output

by Brad Maxwell (JIRA)

[ https://issues.jboss.org/browse/WFLY-8767?page=com.atlassian.jira.plugin.... ] Brad Maxwell updated WFLY-8767: ------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/10309 > Changing the max-pool-size of the datasource pool should indicate a "reload required" in the CLI output > -------------------------------------------------------------------------------------------------------- > > Key: WFLY-8767 > URL: https://issues.jboss.org/browse/WFLY-8767 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Lin Gao > Assignee: varsha Kamble > Labels: downstream_dependency > Original Estimate: 2 days > Remaining Estimate: 2 days > > In EAP domain mode, when changing the max-pool-size attribute of a datasource via CLI, the response does not indicate that a reload is required. However, reading the statistics of that datasource does not reflect the Available count as per the new max pool value until a restart of the server is performed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-169) [QE] - JMAN4-207 - Fuse integration - add reports

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-169?page=com.atlassian.jira.pl... ] Hayk Hovsepyan updated HAWKULARQE-169: -------------------------------------- Description: See [JMAN4-207|https://issues.jboss.org/browse/JMAN4-207] Test Plan document: https://mojo.redhat.com/docs/DOC-1146429 was:See [JMAN4-207|https://issues.jboss.org/browse/JMAN4-207] > [QE] - JMAN4-207 - Fuse integration - add reports > ------------------------------------------------- > > Key: HAWKULARQE-169 > URL: https://issues.jboss.org/browse/HAWKULARQE-169 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Michael Foley > Labels: 5.0, mm-integration-hawkular-qe > > See [JMAN4-207|https://issues.jboss.org/browse/JMAN4-207] > Test Plan document: https://mojo.redhat.com/docs/DOC-1146429 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-166) [QE] - JMAN4-206 - Fuse integration - support operations on entities in MIQ

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-166?page=com.atlassian.jira.pl... ] Hayk Hovsepyan updated HAWKULARQE-166: -------------------------------------- Description: See [JMAN4-206|https://issues.jboss.org/browse/JMAN4-206] Test Plan template: https://mojo.redhat.com/docs/DOC-1146428 was:See [JMAN4-206|https://issues.jboss.org/browse/JMAN4-206] > [QE] - JMAN4-206 - Fuse integration - support operations on entities in MIQ > --------------------------------------------------------------------------- > > Key: HAWKULARQE-166 > URL: https://issues.jboss.org/browse/HAWKULARQE-166 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Michael Foley > Labels: 5.0, mm-integration-hawkular-qe > > See [JMAN4-206|https://issues.jboss.org/browse/JMAN4-206] > Test Plan template: https://mojo.redhat.com/docs/DOC-1146428 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-163) [QE] - JMAN4-205 - Fuse integration - collect metrics for the supported entities

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-163?page=com.atlassian.jira.pl... ] Hayk Hovsepyan updated HAWKULARQE-163: -------------------------------------- Description: See https://issues.jboss.org/browse/JMAN4-205 Test Plan document: https://mojo.redhat.com/docs/DOC-1146426 was:See https://issues.jboss.org/browse/JMAN4-205 > [QE] - JMAN4-205 - Fuse integration - collect metrics for the supported entities > -------------------------------------------------------------------------------- > > Key: HAWKULARQE-163 > URL: https://issues.jboss.org/browse/HAWKULARQE-163 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Michael Foley > Labels: 5.0, mm-integration-hawkular-qe > > See https://issues.jboss.org/browse/JMAN4-205 > Test Plan document: https://mojo.redhat.com/docs/DOC-1146426 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-160) [QE] - JMAN4-204 - Fuse integration - add Context, Route and Consumer entities

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-160?page=com.atlassian.jira.pl... ] Hayk Hovsepyan updated HAWKULARQE-160: -------------------------------------- Description: See [JMAN4-204|https://issues.jboss.org/browse/JMAN4-204] Test Plan document https://mojo.redhat.com/docs/DOC-1146424 was:See [JMAN4-204|https://issues.jboss.org/browse/JMAN4-204] > [QE] - JMAN4-204 - Fuse integration - add Context, Route and Consumer entities > ------------------------------------------------------------------------------ > > Key: HAWKULARQE-160 > URL: https://issues.jboss.org/browse/HAWKULARQE-160 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Michael Foley > Labels: 5.0, mm-integration-hawkular-qe > > See [JMAN4-204|https://issues.jboss.org/browse/JMAN4-204] > Test Plan document https://mojo.redhat.com/docs/DOC-1146424 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3179) Add Elytron Kerberos tests for native management interface

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3179?page=com.atlassian.jira.plugi... ] Josef Cacek updated WFCORE-3179: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/2709 (was: https://github.com/wildfly/wildfly/pull/10243) > Add Elytron Kerberos tests for native management interface > ---------------------------------------------------------- > > Key: WFCORE-3179 > URL: https://issues.jboss.org/browse/WFCORE-3179 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Reporter: Josef Cacek > Assignee: Josef Cacek > Priority: Critical > > Add Kerberos SASL mechanisms (GSSAPI, GS2-KRB5*) tests into AS TS. > This is follow-up task for JBEAP-11194/WFCORE-2881. As the ApacheDS is only used in the TS of full WildFly, the new tests won't be placed into core, but into full ({{testsuite/integration/elytron}}). > This task relates to RFE EAP7-142. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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