August 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (LOGMGR-133) Use StackWalker to get extended log record information

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-133?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-133: --------------------------------- Fix Version/s: 2.1.0.Alpha4 (was: 2.1.0.Alpha3) > Use StackWalker to get extended log record information > ------------------------------------------------------ > > Key: LOGMGR-133 > URL: https://issues.jboss.org/browse/LOGMGR-133 > Project: JBoss Log Manager > Issue Type: Sub-task > Reporter: David Lloyd > Fix For: 2.1.0.Alpha4 > > > Under Java 9, you can use a StackWalker to efficiently traverse the stack and return information about callers. Using this mechanism should be substantially better-performing than snapshotting the stack to acquire the calling class information for the extended log record class. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-132) Remove extended stack trace functionality

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-132?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-132: --------------------------------- Fix Version/s: 2.1.0.Alpha4 (was: 2.1.0.Alpha3) > Remove extended stack trace functionality > ----------------------------------------- > > Key: LOGMGR-132 > URL: https://issues.jboss.org/browse/LOGMGR-132 > Project: JBoss Log Manager > Issue Type: Sub-task > Reporter: David Lloyd > Fix For: 2.1.0.Alpha4 > > > Java 9 stack traces include module name and version number. All our extended stack trace hacky code should be deleted and both format characters should yield a standard stack trace under Java 9. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-131) Add format characters for module name, module version

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-131?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-131: --------------------------------- Fix Version/s: 2.1.0.Alpha4 (was: 2.1.0.Alpha3) > Add format characters for module name, module version > ----------------------------------------------------- > > Key: LOGMGR-131 > URL: https://issues.jboss.org/browse/LOGMGR-131 > Project: JBoss Log Manager > Issue Type: Sub-task > Reporter: David Lloyd > Fix For: 2.1.0.Alpha4 > > > In JDK9, StackTraceElements contain moduleName and moduleVersion fields. This information is useful for debugging purposes, thus format characters should be allocated towards these values. Ideally it'll be something non-conflicting with respect to log4j and other common ancestor/related frameworks, but that is less important than the basic support. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3218) Upgrade jboss-logmanager from 2.0.7.Final to 2.1.0.Alpha3

by James Perkins (JIRA)

James Perkins created WFCORE-3218: ------------------------------------- Summary: Upgrade jboss-logmanager from 2.0.7.Final to 2.1.0.Alpha3 Key: WFCORE-3218 URL: https://issues.jboss.org/browse/WFCORE-3218 Project: WildFly Core Issue Type: Component Upgrade Components: Logging Reporter: James Perkins Assignee: James Perkins Fix For: 4.0.0.Alpha1 Upgrade {{org.jboss.logmanager:jboss-logmanager}} from 2.0.7.Final to 2.1.0.Alpha3. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3003) Elytron subsystem fails to boot if SecurityProvider cannot be loaded.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3003?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-3003: ---------------------------------------- Fix Version/s: 4.0.0.Alpha1 Assignee: Tomaz Cerar Resolution: Done > Elytron subsystem fails to boot if SecurityProvider cannot be loaded. > --------------------------------------------------------------------- > > Key: WFCORE-3003 > URL: https://issues.jboss.org/browse/WFCORE-3003 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Labels: jdk9 > Fix For: 4.0.0.Alpha1 > > > Trying to run secmgr testsuite under JDK9 results in > {noformat} > Caused by: java.util.ServiceConfigurationError: java.security.Provider: Provider com.sun.deploy.security.MozillaJSSProvider could not be instantiated > at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:581) > at java.base/java.util.ServiceLoader.access$100(ServiceLoader.java:390) > at java.base/java.util.ServiceLoader$ProviderImpl.newInstance(ServiceLoader.java:799) > at java.base/java.util.ServiceLoader$ProviderImpl.get(ServiceLoader.java:721) > at java.base/java.util.ServiceLoader$3.next(ServiceLoader.java:1389) > at java.base/java.lang.Iterable.forEach(Iterable.java:74) > at org.wildfly.extension.elytron//org.wildfly.extension.elytron.ProviderDefinitions$1$1.get(ProviderDefinitions.java:201) > at org.wildfly.extension.elytron//org.wildfly.extension.elytron.ProviderDefinitions$1$1.get(ProviderDefinitions.java:158) > at org.wildfly.extension.elytron//org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53) > at org.jboss.msc//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) > at org.jboss.msc//org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) > {noformat} > and server doesn't start. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9286) Unable to remove an installed resource adapter

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-9286: -------------------------------------- Summary: Unable to remove an installed resource adapter Key: WFLY-9286 URL: https://issues.jboss.org/browse/WFLY-9286 Project: WildFly Issue Type: Bug Components: JCA Affects Versions: 11.0.0.CR1 Reporter: John Huntley Assignee: Stefano Maestri Priority: Blocker Fix For: 11.0.0.Final Attachments: wf11-ra-error.txt Running a :remove operation for a defined resource adapter fails with error WFLYCTL0123. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3217) Relax the WFCORE-2849 requirement

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3217?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3217: ------------------------------------- Description: WFCORE-2849 fails ops against domain profile resources if the OSH tries to register a Stage.RUNTIME step. But we are still hitting cases where we have OSHs that try to do this (see WFLY-9281). Since those OSHs have worked for years without this causing major trouble, failing the op seems excessive. Instead I would like to log a WARN, and have the problematic 'addStep' call simply return without adding the step. Perhaps this could be a DEBUG, but really if an OSH is doing this it is a bug and I'd like to not hide that. was: WFCORE-2849 fails ops against domain profile resources if the OSH tries to register a Stage.RUNTIME step. But we are still hitting cases where we have OSHs that try to do this (see WFLY-9821). Since those OSHs have worked for years without this causing major trouble, failing the op seems excessive. Instead I would like to log a WARN, and have the problematic 'addStep' call simply return without adding the step. Perhaps this could be a DEBUG, but really if an OSH is doing this it is a bug and I'd like to not hide that. > Relax the WFCORE-2849 requirement > --------------------------------- > > Key: WFCORE-3217 > URL: https://issues.jboss.org/browse/WFCORE-3217 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Affects Versions: 3.0.0.Final, 3.0.1.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 4.0.0.Alpha1, 3.0.2.Final > > > WFCORE-2849 fails ops against domain profile resources if the OSH tries to register a Stage.RUNTIME step. But we are still hitting cases where we have OSHs that try to do this (see WFLY-9281). Since those OSHs have worked for years without this causing major trouble, failing the op seems excessive. > Instead I would like to log a WARN, and have the problematic 'addStep' call simply return without adding the step. > Perhaps this could be a DEBUG, but really if an OSH is doing this it is a bug and I'd like to not hide that. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3217) Relax the WFCORE-2849 requirement

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3217: ---------------------------------------- Summary: Relax the WFCORE-2849 requirement Key: WFCORE-3217 URL: https://issues.jboss.org/browse/WFCORE-3217 Project: WildFly Core Issue Type: Task Components: Domain Management Affects Versions: 3.0.1.Final, 3.0.0.Final Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Blocker Fix For: 4.0.0.Alpha1, 3.0.2.Final WFCORE-2849 fails ops against domain profile resources if the OSH tries to register a Stage.RUNTIME step. But we are still hitting cases where we have OSHs that try to do this (see WFLY-9821). Since those OSHs have worked for years without this causing major trouble, failing the op seems excessive. Instead I would like to log a WARN, and have the problematic 'addStep' call simply return without adding the step. Perhaps this could be a DEBUG, but really if an OSH is doing this it is a bug and I'd like to not hide that. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9281) Unable to remove an installed resource adapter

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9281?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-9281: ----------------------------------- Fix Version/s: 11.0.0.Final Priority: Blocker (was: Major) This is a regression that we need to fix for 11.0.0.Final. The handler for this :remove op should be fixed so it doesn't violate the WFCORE-2849 requirement, but given the fact that we are still finding issues like this quite a while after the WFCORE-2849 makes me think we need to relax that check and have it just log a WARN or something rather than failing the op. Thank you, [~kznpoike] for the report. > Unable to remove an installed resource adapter > ---------------------------------------------- > > Key: WFLY-9281 > URL: https://issues.jboss.org/browse/WFLY-9281 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 11.0.0.CR1 > Reporter: John Huntley > Assignee: Stefano Maestri > Priority: Blocker > Fix For: 11.0.0.Final > > Attachments: wf11-ra-error.txt > > > Running a :remove operation for a defined resource adapter fails with error WFLYCTL0123. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9285) Make IONA interoperability work with OpenJDK ORB

by Tomasz Adamski (JIRA)

[ https://issues.jboss.org/browse/WFLY-9285?page=com.atlassian.jira.plugin.... ] Tomasz Adamski updated WFLY-9285: --------------------------------- Description: IONA interoperability worked on JacORB, we would like the same functionality to be added to OpenJDK ORB. > Make IONA interoperability work with OpenJDK ORB > ------------------------------------------------ > > Key: WFLY-9285 > URL: https://issues.jboss.org/browse/WFLY-9285 > Project: WildFly > Issue Type: Bug > Reporter: Tomasz Adamski > Assignee: Jason Greene > > IONA interoperability worked on JacORB, we would like the same functionality to be added to OpenJDK ORB. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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