June 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-457) Optimization: make threads return immediately if NAKACK has another active thread for the same sender

by Bela Ban (JIRA)

Optimization: make threads return immediately if NAKACK has another active thread for the same sender ----------------------------------------------------------------------------------------------------- Key: JGRP-457 URL: http://jira.jboss.com/jira/browse/JGRP-457 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Priority: Minor Fix For: 2.5 In NAKACK, when a thread places a message for sender S into the NakReceiverWindow NRW, it subsequently acquires a lock on NRW (lock by sender) and removes as many messages as possible and passes them up. If many threads do this at the same time, all threads but one are blocked, and - when finally unblocked - usually return. This causes context switches and possibly cache flushing, so a better way would be to have the threads check whether another thread is already removing messages using a CAS operation *before* acquiring the lock. The effect should be that no threads will wait on the lock unnecessarily, and thus fewer context switches, and more threads available to the pool. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

2 weeks, 5 days

2
3
0 / 0

[JBoss JIRA] (JBRULES-3445) DSL expander expands lines in /* */comment block

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3445: ------------------------------------ Summary: DSL expander expands lines in /* */comment block Key: JBRULES-3445 URL: https://issues.jboss.org/browse/JBRULES-3445 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco When you comment some code in dslr file, the expander still tries to expand it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

6 months, 1 week

3
10
0 / 0

[JBoss JIRA] (ELY-6) Password type: Trivial digest

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-6?page=com.atlassian.jira.plugin.syst... ] David Lloyd reassigned ELY-6: ----------------------------- Assignee: David Lloyd > Password type: Trivial digest > ----------------------------- > > Key: ELY-6 > URL: https://issues.jboss.org/browse/ELY-6 > Project: WildFly Elytron > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.0.0.Beta1 > > > Some users and systems store passwords as simple, trivial digests. This password type is to support these cases. This password type would not be generally recommended. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3566) JMXSubsystemRemove is unsafe

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-3566?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-3566: ----------------------------------- Description: The service installed by JMXSubsytemAdd is used by quite a few other subsystems (arquillian, infinispan, jgroups, jsr77, sar, perhaps something in webservices) but JMXSubsytemRemove just removes it. 1) Given the number of dependencies, the removal should require the allow-resource-service-restart header. 2) The rollbackRuntime method needs to be implemented. was: The service installed by JMXSubsytemAdd are used by quite a few other subsystems (arquillian, infinispan, jgroups, jsr77, sar, perhaps something in webservices) but JMXSubsytemRemove just removes it. 1) Given the number of dependencies, the removal should require the allow-resource-service-restart header. 2) The rollbackRuntime method needs to be implemented. > JMXSubsystemRemove is unsafe > ---------------------------- > > Key: WFLY-3566 > URL: https://issues.jboss.org/browse/WFLY-3566 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management, JMX > Affects Versions: 8.1.0.Final > Reporter: Brian Stansberry > Fix For: 9.0.0.Alpha1 > > > The service installed by JMXSubsytemAdd is used by quite a few other subsystems (arquillian, infinispan, jgroups, jsr77, sar, perhaps something in webservices) but JMXSubsytemRemove just removes it. > 1) Given the number of dependencies, the removal should require the allow-resource-service-restart header. > 2) The rollbackRuntime method needs to be implemented. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3566) JMXSubsystemRemove is unsafe

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-3566: -------------------------------------- Summary: JMXSubsystemRemove is unsafe Key: WFLY-3566 URL: https://issues.jboss.org/browse/WFLY-3566 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management, JMX Affects Versions: 8.1.0.Final Reporter: Brian Stansberry Fix For: 9.0.0.Alpha1 The service installed by JMXSubsytemAdd are used by quite a few other subsystems (arquillian, infinispan, jgroups, jsr77, sar, perhaps something in webservices) but JMXSubsytemRemove just removes it. 1) Given the number of dependencies, the removal should require the allow-resource-service-restart header. 2) The rollbackRuntime method needs to be implemented. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3566) JMXSubsystemRemove is unsafe

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3566?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3566: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1087711 > JMXSubsystemRemove is unsafe > ---------------------------- > > Key: WFLY-3566 > URL: https://issues.jboss.org/browse/WFLY-3566 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management, JMX > Affects Versions: 8.1.0.Final > Reporter: Brian Stansberry > Fix For: 9.0.0.Alpha1 > > > The service installed by JMXSubsytemAdd are used by quite a few other subsystems (arquillian, infinispan, jgroups, jsr77, sar, perhaps something in webservices) but JMXSubsytemRemove just removes it. > 1) Given the number of dependencies, the removal should require the allow-resource-service-restart header. > 2) The rollbackRuntime method needs to be implemented. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2964) Missing i18n

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2964?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2964: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1067024|https://bugzilla.redhat.com/show_bug.cgi?id=1067024] from NEW to ASSIGNED > Missing i18n > ------------ > > Key: WFLY-2964 > URL: https://issues.jboss.org/browse/WFLY-2964 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB, JMX, Patching > Affects Versions: 8.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 9.0.0.Alpha1 > > > system-jmx/src/main/java/org/jboss/system/ServiceMBeanSupport.java > 379 log.error(e); > patching/src/main/java/org/jboss/as/patching/validation/PatchArtifact.java > 102 ctx.getErrorHandler().error("Failed to load identity info for patch " + patch.getPatchId(), e); > 116 ctx.getErrorHandler().error("Failed to load previous patch", e); > patching/src/main/java/org/jboss/as/patching/validation/XmlFileState.java > 51 ctx.getErrorHandler().error("File doesn't exist: " + file.getAbsolutePath()); > 56 ctx.getErrorHandler().error("Failed to parse file: " + file.getAbsolutePath(), e); > patching/src/main/java/org/jboss/as/patching/validation/PatchElementProviderArtifact.java > 84 ctx.getErrorHandler().error("Layer not found: " + metadata.getName()); > patching/src/main/java/org/jboss/as/patching/runner/IdentityPatchContext.java > 435 PatchLogger.ROOT_LOGGER.warnf(e, "failed to undo change (%s)", modification); > ejb3/src/main/java/org/jboss/as/ejb3/tx/CMTTxInterceptor.java > 169 EjbLogger.ROOT_LOGGER.error(t); -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2964) Missing i18n

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2964?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-2964: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1067024 > Missing i18n > ------------ > > Key: WFLY-2964 > URL: https://issues.jboss.org/browse/WFLY-2964 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB, JMX, Patching > Affects Versions: 8.0.0.Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 9.0.0.Alpha1 > > > system-jmx/src/main/java/org/jboss/system/ServiceMBeanSupport.java > 379 log.error(e); > patching/src/main/java/org/jboss/as/patching/validation/PatchArtifact.java > 102 ctx.getErrorHandler().error("Failed to load identity info for patch " + patch.getPatchId(), e); > 116 ctx.getErrorHandler().error("Failed to load previous patch", e); > patching/src/main/java/org/jboss/as/patching/validation/XmlFileState.java > 51 ctx.getErrorHandler().error("File doesn't exist: " + file.getAbsolutePath()); > 56 ctx.getErrorHandler().error("Failed to parse file: " + file.getAbsolutePath(), e); > patching/src/main/java/org/jboss/as/patching/validation/PatchElementProviderArtifact.java > 84 ctx.getErrorHandler().error("Layer not found: " + metadata.getName()); > patching/src/main/java/org/jboss/as/patching/runner/IdentityPatchContext.java > 435 PatchLogger.ROOT_LOGGER.warnf(e, "failed to undo change (%s)", modification); > ejb3/src/main/java/org/jboss/as/ejb3/tx/CMTTxInterceptor.java > 169 EjbLogger.ROOT_LOGGER.error(t); -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-4175) Deployment content is not always removed from data/content

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-4175?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-4175: ---------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1035345|https://bugzilla.redhat.com/show_bug.cgi?id=1035345] from NEW to CLOSED > Deployment content is not always removed from data/content > ---------------------------------------------------------- > > Key: AS7-4175 > URL: https://issues.jboss.org/browse/AS7-4175 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.0.Final, 7.1.1.Final > Reporter: Brian Stansberry > Assignee: Kabir Khan > Priority: Critical > Fix For: 7.1.2.Final (EAP) > > Attachments: test-ds.xml > > > The AS7-341 fix doesn't seem to be working in some use cases. > I'll attach a test-ds.xml that can be used to manual reproduce this. Using a -ds.xml is useful since it's trivial to modify the deployment file to create a new hash. > From the CLI, this works (i.e. when both steps are done there are zero additional subdirectories in data/content, i.e. zero total directories on a fresh install): > [standalone@localhost:9999 /] deploy /home/me/test-ds.xml > [standalone@localhost:9999 /] undeploy test-ds.xml > However, this does not work (i.e. when both steps are done there is one additional subdirectories in data/content, i.e. one total directory on a fresh install): > [standalone@localhost:9999 /] deploy /home/me/test-ds.xml > manually modify /home/me/test-ds.xml > [standalone@localhost:9999 /] deploy --force /home/me/test-ds.xml > There may be other permutations of the of deploy/redeploy/undeploy that also leave file behind. In particular, the forum thread references using the jboss maven plugin, so whatever ops it is invoking should be checked. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3565) Incorrect use of ReloadRequiredWriteAttributeHandler for host resources

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3565?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3565: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1085228 > Incorrect use of ReloadRequiredWriteAttributeHandler for host resources > ----------------------------------------------------------------------- > > Key: WFLY-3565 > URL: https://issues.jboss.org/browse/WFLY-3565 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.1.0.Final > Reporter: Brian Stansberry > Priority: Critical > Fix For: 8.2.0.CR1, 9.0.0.Alpha1 > > > ReloadRequiredWriteAttributeHandler inherits the default behavior of AbstractWriteAttributeHandler.requiresRuntime(), which is to only process Stage.RUNTIME if context.isNormalServer(). So any use in host resources needs to override that behavior. This isn't done in at least some places. See https://bugzilla.redhat.com/show_bug.cgi?id=1085228 for an example. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

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