February 2015 - 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, 4 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] (WFLY-4355) Move deprecated DeploymentUnit methods to the DeploymentResourceSupport

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-4355?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-4355: -------------------------------- Summary: Move deprecated DeploymentUnit methods to the DeploymentResourceSupport (was: Usage of the DeploymentUnit.createDeploymentSubModel need to be reviewed) > Move deprecated DeploymentUnit methods to the DeploymentResourceSupport > ----------------------------------------------------------------------- > > Key: WFLY-4355 > URL: https://issues.jboss.org/browse/WFLY-4355 > Project: WildFly > Issue Type: Task > Reporter: James Perkins > Assignee: James Perkins > > WFCORE-542 added a new API attached to the {{DeploymentUnit}} to interact with the deployments model. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4355) Usage of the DeploymentUnit.createDeploymentSubModel need to be reviewed

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-4355?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-4355: -------------------------------- Description: WFCORE-542 added a new API attached to the {{DeploymentUnit}} to interact with the deployments model. (was: WFCORE-542 is adding new methods and changing/clarifying the contracts for the {{DeploymentUnit.createDeploymentSubModel}} methods. For now only a warning messages will be printed. A review of subsystems that use these methods needs to happen after a core version is released and added to full.) > Usage of the DeploymentUnit.createDeploymentSubModel need to be reviewed > ------------------------------------------------------------------------ > > Key: WFLY-4355 > URL: https://issues.jboss.org/browse/WFLY-4355 > Project: WildFly > Issue Type: Task > Reporter: James Perkins > Assignee: James Perkins > > WFCORE-542 added a new API attached to the {{DeploymentUnit}} to interact with the deployments model. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4355) Usage of the DeploymentUnit.createDeploymentSubModel need to be reviewed

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-4355?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-4355: -------------------------------- Issue Type: Task (was: Enhancement) > Usage of the DeploymentUnit.createDeploymentSubModel need to be reviewed > ------------------------------------------------------------------------ > > Key: WFLY-4355 > URL: https://issues.jboss.org/browse/WFLY-4355 > Project: WildFly > Issue Type: Task > Reporter: James Perkins > Assignee: James Perkins > > WFCORE-542 is adding new methods and changing/clarifying the contracts for the {{DeploymentUnit.createDeploymentSubModel}} methods. For now only a warning messages will be printed. A review of subsystems that use these methods needs to happen after a core version is released and added to full. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-546) Remove warning log from DeploymentModelUtils

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-546?page=com.atlassian.jira.plugin... ] James Perkins closed WFCORE-546. -------------------------------- Resolution: Rejected The scope of WFCORE-542 changed and the methods were deprecated. No warning message will be printed. > Remove warning log from DeploymentModelUtils > -------------------------------------------- > > Key: WFCORE-546 > URL: https://issues.jboss.org/browse/WFCORE-546 > Project: WildFly Core > Issue Type: Task > Components: Server > Reporter: James Perkins > Assignee: James Perkins > > As part of WFCORE-542 a warning was introduced if {{DeploymentUnit.createDeploymentSubModel}} was invoked on a resource that already exists. For WildFly 10 this warning can go away and the error can be thrown. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-542) Deprecate DeploymentUnit deployment resource methods and create new API

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-542?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-542: --------------------------------- Description: Deprecate the methods that interact with the (was: The {{DeploymentUnit.getDeploymentSubsystemModel()}} and the {{DeploymentUnit.createDeploymentSubModel()}} methods were somewhat generic the documentation. The documentation needs to be clarified and the implementation needs to conform to the clarified documentation.) > Deprecate DeploymentUnit deployment resource methods and create new API > ----------------------------------------------------------------------- > > Key: WFCORE-542 > URL: https://issues.jboss.org/browse/WFCORE-542 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Reporter: James Perkins > Assignee: James Perkins > > Deprecate the methods that interact with the -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-542) Deprecate DeploymentUnit deployment resource methods and create new API

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-542?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-542: --------------------------------- Description: Deprecate the methods that interact with the deployments subsystem resources. Create a new API attached to the deployment unit to interact with the deployments resources. (was: Deprecate the methods that interact with the ) > Deprecate DeploymentUnit deployment resource methods and create new API > ----------------------------------------------------------------------- > > Key: WFCORE-542 > URL: https://issues.jboss.org/browse/WFCORE-542 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Reporter: James Perkins > Assignee: James Perkins > > Deprecate the methods that interact with the deployments subsystem resources. Create a new API attached to the deployment unit to interact with the deployments resources. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-542) Deprecate DeploymentUnit deployment resource methods and create new API

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-542?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-542: --------------------------------- Summary: Deprecate DeploymentUnit deployment resource methods and create new API (was: Clarify the JavaDoc for DeploymentUnit sub-models) > Deprecate DeploymentUnit deployment resource methods and create new API > ----------------------------------------------------------------------- > > Key: WFCORE-542 > URL: https://issues.jboss.org/browse/WFCORE-542 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Reporter: James Perkins > Assignee: James Perkins > > The {{DeploymentUnit.getDeploymentSubsystemModel()}} and the {{DeploymentUnit.createDeploymentSubModel()}} methods were somewhat generic the documentation. The documentation needs to be clarified and the implementation needs to conform to the clarified documentation. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4396) mod_cluster subsystem find any http server on the network

by Jose Diaz (JIRA)

Jose Diaz created WFLY-4396: ------------------------------- Summary: mod_cluster subsystem find any http server on the network Key: WFLY-4396 URL: https://issues.jboss.org/browse/WFLY-4396 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 8.2.0.Final Environment: Ubuntu 14.04, wildfly 8.2.0.final, apache http server 2.2.29 Reporter: Jose Diaz Assignee: Paul Ferraro Priority: Critical I configure a Load Balanced HA Standalone Cluster, in my machine however in the network there is other apache http server when I wake up the server I get the next error: MODCLUSTER000043: Failed to send INFO to 10.21.51.121/10.21.51.121:22001: java.net.NoRouteToHostException: No existe ninguna ruta hasta el «host» I configure the mod_cluster in standalone-full-ha with: <subsystem xmlns="urn:jboss:domain:modcluster:1.2"> <mod-cluster-config advertise-socket="modcluster" proxy-list="127.0.0.1:80" balancer="jdcluster" connector="ajp"> <dynamic-load-provider> <load-metric type="cpu"/> </dynamic-load-provider> </mod-cluster-config> </subsystem> Then get the same error. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 8 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 February 2015