April 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (EJBTHREE-1969) EJB3 deployments lead to java.lang.IllegalStateException: Null beannMetaData

by G H (JIRA)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-473) Drools spawning a lot of JIT threads

by Frank Pavageau (JIRA)

Frank Pavageau created DROOLS-473: ------------------------------------- Summary: Drools spawning a lot of JIT threads Key: DROOLS-473 URL: https://issues.jboss.org/browse/DROOLS-473 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 5.5.0.Final Reporter: Frank Pavageau Assignee: Mark Proctor {{MvelConstraint}} submits JIT tasks to an {{Executor}} once it has been evaluated enough times, but that {{Executor}} created by {{ExecutorProviderImpl}} is a basic {{CachedThreadPool}} which can create an unbounded number of threads (though they die after idling for a minute). Firing a lot of rules quickly can create several hundreds threads. If you have several JVMs on the same machine processing the same kind of load, it can saturate the OS and result in errors as the JVMs cannot create native threads anymore. The maximum size of the thread pool should probably be limited to a more reasonable default, maybe with a configurable value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3302) TLSSyslog server remove BC provider, does not add it back if it was present

by Bartosz Baranowski (JIRA)

Bartosz Baranowski created WFLY-3302: ---------------------------------------- Summary: TLSSyslog server remove BC provider, does not add it back if it was present Key: WFLY-3302 URL: https://issues.jboss.org/browse/WFLY-3302 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: 8.1.0.CR1, 8.0.0.Final Reporter: Bartosz Baranowski Assignee: Bartosz Baranowski Priority: Trivial Fix For: Awaiting Volunteers Syslog test kills BC provider, this may cause( and did ) random failures. Offending code: https://github.com/wildfly/wildfly/blob/master/testsuite/integration/basi... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3031) Management audit logging logs parallel boot ops in separate records

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3031?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3031: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1092220 > Management audit logging logs parallel boot ops in separate records > ------------------------------------------------------------------- > > Key: WFLY-3031 > URL: https://issues.jboss.org/browse/WFLY-3031 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.1.0.CR1 > > > The parallel boot ops (i.e. the subsystem stuff) are logged in separate log records from the other stuff. > This is questionable because they are actually all part of the same execution. The main execution blocks for the parallel ops. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3031) Management audit logging logs parallel boot ops in separate records

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3031?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3031: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1092220|https://bugzilla.redhat.com/show_bug.cgi?id=1092220] from NEW to ASSIGNED > Management audit logging logs parallel boot ops in separate records > ------------------------------------------------------------------- > > Key: WFLY-3031 > URL: https://issues.jboss.org/browse/WFLY-3031 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.1.0.CR1 > > > The parallel boot ops (i.e. the subsystem stuff) are logged in separate log records from the other stuff. > This is questionable because they are actually all part of the same execution. The main execution blocks for the parallel ops. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2997) AccessAuditContext domainUUID is not set when the domain-uuid header is set

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2997?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2997: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1092213|https://bugzilla.redhat.com/show_bug.cgi?id=1092213] from NEW to ASSIGNED > AccessAuditContext domainUUID is not set when the domain-uuid header is set > --------------------------------------------------------------------------- > > Key: WFLY-2997 > URL: https://issues.jboss.org/browse/WFLY-2997 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.1.0.CR1 > > > org.jboss.as.domain.controller.operations.coordination.PrepareStepHandler creates a UUID and sets "operations-headers" => "domain-uuid" on the op, but it does not pass the same UUID to AccessAuditContext. The result is the log record has null in the domainUUID field but the operation headers part of the "ops" field shows the uuid. Confusing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2997) AccessAuditContext domainUUID is not set when the domain-uuid header is set

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2997?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-2997: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1092213 > AccessAuditContext domainUUID is not set when the domain-uuid header is set > --------------------------------------------------------------------------- > > Key: WFLY-2997 > URL: https://issues.jboss.org/browse/WFLY-2997 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.1.0.CR1 > > > org.jboss.as.domain.controller.operations.coordination.PrepareStepHandler creates a UUID and sets "operations-headers" => "domain-uuid" on the op, but it does not pass the same UUID to AccessAuditContext. The result is the log record has null in the domainUUID field but the operation headers part of the "ops" field shows the uuid. Confusing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBVFS-196) Classpath resources fails due to VFS error

by Matthew Lee (JIRA)

Matthew Lee created JBVFS-196: --------------------------------- Summary: Classpath resources fails due to VFS error Key: JBVFS-196 URL: https://issues.jboss.org/browse/JBVFS-196 Project: JBoss VFS Issue Type: Bug Security Level: Public (Everyone can see) Components: Release Environment: Windows server 2003 Reporter: Matthew Lee Assignee: Tomaz Cerar I tried to access the following link to find a solution but the link could not be accessed. http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4239767#4239767 Does anyone can help me. Thanks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3017) OperationContextImpl.readResourceForUpdate assumes all resources represent persistent config

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3017?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3017: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1092206|https://bugzilla.redhat.com/show_bug.cgi?id=1092206] from NEW to ASSIGNED > OperationContextImpl.readResourceForUpdate assumes all resources represent persistent config > -------------------------------------------------------------------------------------------- > > Key: WFLY-3017 > URL: https://issues.jboss.org/browse/WFLY-3017 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.1.0.CR1 > > > The readResourceForUpdate impl makes a few assumptions regarding the fact that a given Resource represents persistent config (i.e. Resource.isRuntime() == true): > 1) It calls rejectUserDomainServerUpdates() which means an OSH running on a server could not call this. > 2) It calls authorize(false, READ_WRITE_CONFIG) which means an OSH for an op available to the RBAC Operator role could not call this. > Places this impacts include LogStoreProbeHandler and LogStoreTransactionDeleteHandler which should be calling readResourceForUpdate but aren't -- and can't because of this bug. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3017) OperationContextImpl.readResourceForUpdate assumes all resources represent persistent config

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3017?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3017: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1092206 > OperationContextImpl.readResourceForUpdate assumes all resources represent persistent config > -------------------------------------------------------------------------------------------- > > Key: WFLY-3017 > URL: https://issues.jboss.org/browse/WFLY-3017 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 8.1.0.CR1 > > > The readResourceForUpdate impl makes a few assumptions regarding the fact that a given Resource represents persistent config (i.e. Resource.isRuntime() == true): > 1) It calls rejectUserDomainServerUpdates() which means an OSH running on a server could not call this. > 2) It calls authorize(false, READ_WRITE_CONFIG) which means an OSH for an op available to the RBAC Operator role could not call this. > Places this impacts include LogStoreProbeHandler and LogStoreTransactionDeleteHandler which should be calling readResourceForUpdate but aren't -- and can't because of this bug. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 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 April 2014