May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10355) The non-multicast mod_cluster subsystem template puts attributes in non-xsd order

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-10355: --------------------------------------- Summary: The non-multicast mod_cluster subsystem template puts attributes in non-xsd order Key: WFLY-10355 URL: https://issues.jboss.org/browse/WFLY-10355 Project: WildFly Issue Type: Bug Components: mod_cluster Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor The document we generate should follow the xsd. Galleon will as the server persister marshals in xsd order, so basically fixing this just removes a diff between a galleon built dist and a legacy one. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3787) JMX audit logging should support all the handlers supported by core audit logging

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3787?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-3787: --------------------------------------- [~dlofthouse] What would the security concerns be with instead of having resources for audit logging we just had categories that could be configured via the logging subsystem? e.g. {{org.wildly.security.audit}}. > JMX audit logging should support all the handlers supported by core audit logging > --------------------------------------------------------------------------------- > > Key: WFCORE-3787 > URL: https://issues.jboss.org/browse/WFCORE-3787 > Project: WildFly Core > Issue Type: Feature Request > Components: JMX > Affects Versions: 5.0.0.Alpha5 > Reporter: Yeray Borges > Assignee: Yeray Borges > > Users can enable audit logging for the management interfaces, which will log all operations performed using the management console, management CLI, or custom application that uses the Management API. > JMX subsystem can use the handlers defined for audit logging, but at this moment, only {{file-handler}} and {{syslog-handler}} can be used in JMX subsystem. > This issue will extend the list of supported handlers for JMX subsystem to all handlers supported by core audit logging. > The handlers supported by core audit logging are: > * file-handler > * in-memory-handler > * periodic-rotating-file-handler > * size-rotating-file-handler > * syslog-handler -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9288) EJB session auto-creation is not working

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-9288?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-9288: ----------------------------------- PR #11187 can be reopened with its current branch as soon as the corresponding releases of jboss-ejb-client are done. > EJB session auto-creation is not working > ---------------------------------------- > > Key: WFLY-9288 > URL: https://issues.jboss.org/browse/WFLY-9288 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: David Lloyd > Assignee: David Lloyd > > In {{org.jboss.as.ejb3.remote.AssociationImpl#receiveInvocationRequest}}, when the EJB component is being looked up, two things need to happen which are not happening: > * The incoming locator should be examined; if it is a stateful locator and the physical EJB is stateless, then {{Request#writeNotStateful()}} should be called and processing should be aborted. > * If the incoming locator is a stateless locator and the physical EJB is stateful, then {{component#createSessionRemote()}} should be called and the resultant session ID should be set using {{Request#convertToStateful()}}. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10351) Clean up BMTInterceptor

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-10351?page=com.atlassian.jira.plugin... ] David Lloyd updated WFLY-10351: ------------------------------- Summary: Clean up BMTInterceptor (was: Clean up BMTTxInterceptor) > Clean up BMTInterceptor > ----------------------- > > Key: WFLY-10351 > URL: https://issues.jboss.org/browse/WFLY-10351 > Project: WildFly > Issue Type: Task > Components: EJB > Reporter: David Lloyd > Assignee: David Lloyd > > The BMT interceptor has similar problems to what was fixed in WFLY-10146 for the CMT interceptor, namely use of finally blocks, loss of suppressed exceptions, code duplication, etc., albeit on a slightly smaller scale. > See if we can clean that up a bit as well. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3822) When using offline CLI with different --jboss-home arguments the log directory is not updated

by James Perkins (JIRA)

James Perkins created WFCORE-3822: ------------------------------------- Summary: When using offline CLI with different --jboss-home arguments the log directory is not updated Key: WFCORE-3822 URL: https://issues.jboss.org/browse/WFCORE-3822 Project: WildFly Core Issue Type: Bug Components: CLI, Embedded Reporter: James Perkins Assignee: James Perkins When using the CLI client JAR and specifying different {{--jboss-home}} directories when starting different embedded servers the {{jboss.server.log.dir}} is not updated to the new home directory. The CLI {{EnvironmentRestorer}} likely needs to handle this property as it's specifically set in the command handler. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3821) Upgrade JBoss Modules to 1.8.4.Final

by David Lloyd (JIRA)

David Lloyd created WFCORE-3821: ----------------------------------- Summary: Upgrade JBoss Modules to 1.8.4.Final Key: WFCORE-3821 URL: https://issues.jboss.org/browse/WFCORE-3821 Project: WildFly Core Issue Type: Component Upgrade Components: Modules Reporter: David Lloyd Assignee: David Lloyd -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10330) Revert component-matrix change

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-10330?page=com.atlassian.jira.plugin... ] James Perkins reassigned WFLY-10330: ------------------------------------ Fix Version/s: 13.0.0.Beta1 Assignee: Kabir Khan Resolution: Done > Revert component-matrix change > ------------------------------ > > Key: WFLY-10330 > URL: https://issues.jboss.org/browse/WFLY-10330 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: David Lloyd > Assignee: Kabir Khan > Fix For: 13.0.0.Beta1 > > > Revert the change described in WFLY-9911. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3820) Upgrade jboss-logmanager from 2.1.1.Final to 2.1.2.Final

by James Perkins (JIRA)

James Perkins created WFCORE-3820: ------------------------------------- Summary: Upgrade jboss-logmanager from 2.1.1.Final to 2.1.2.Final Key: WFCORE-3820 URL: https://issues.jboss.org/browse/WFCORE-3820 Project: WildFly Core Issue Type: Component Upgrade Components: Logging Reporter: James Perkins Assignee: James Perkins Upgrade {{org.jboss.logmanager:jboss-logmanager}} from 2.1.1.Final to 2.1.2.Final. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-130) JDK9 Support

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-130?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-130: --------------------------------- Fix Version/s: 2.1.3.Final (was: 2.1.2.Final) > JDK9 Support > ------------ > > Key: LOGMGR-130 > URL: https://issues.jboss.org/browse/LOGMGR-130 > Project: JBoss Log Manager > Issue Type: Feature Request > Reporter: David Lloyd > Fix For: 2.1.3.Final > > > A few enhancements become possible, desirable, and/or necessary when moving to JDK 9. This is an umbrella parent issue to cover them all. > Note that some of these features may require multi-version JAR building, which Maven cannot yet do. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-86) Create an exception filter

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-86?page=com.atlassian.jira.plugin.... ] James Perkins updated LOGMGR-86: -------------------------------- Fix Version/s: 2.1.3.Final (was: 2.1.2.Final) > Create an exception filter > -------------------------- > > Key: LOGMGR-86 > URL: https://issues.jboss.org/browse/LOGMGR-86 > Project: JBoss Log Manager > Issue Type: Feature Request > Reporter: James Perkins > Fix For: 2.1.3.Final > > > For now this is just a thought so that users can filter messages based on an exception in the stack trace. Currently it's not possible to use a regex filter as the stack trace is not used in when testing for matches and it probably shouldn't be used. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 May 2018