January 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] (WFLY-2580) keytool-maven-plugin does not work on JDK8

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2580?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-2580: ----------------------------------- My branch with fix for JDK8 https://github.com/ctomc/keytool-maven-plugin > keytool-maven-plugin does not work on JDK8 > ------------------------------------------ > > Key: WFLY-2580 > URL: https://issues.jboss.org/browse/WFLY-2580 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: 8.0.0.Beta1 > Reporter: Tomaz Cerar > Assignee: Ondrej Zizka > Fix For: 8.0.0.Final > > > JDK8 has changed JarSigner package / class location > upstream issue https://jira.codehaus.org/browse/MKEYTOOL-35 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-324) xinclude support in the management model

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-324?page=com.atlassian.jira.plugin.s... ] Jason Greene commented on WFLY-324: ----------------------------------- I have a prototype for this, but it requires further discussion. Deferring to 9 > xinclude support in the management model > ---------------------------------------- > > Key: WFLY-324 > URL: https://issues.jboss.org/browse/WFLY-324 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Jason Greene > Fix For: 9.0.0.CR1 > > > Ability to use xinclude in the domain/xml/host.xml/standalone.xml documents. Not necessarily anywhere, but where the model supports storing the information. Upon changes to the model, persistence of the relevant elements would be to the specified file. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-324) xinclude support in the management model

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-324?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-324: ------------------------------ Fix Version/s: 9.0.0.CR1 (was: 8.0.0.CR1) (was: 8.0.0.Final) > xinclude support in the management model > ---------------------------------------- > > Key: WFLY-324 > URL: https://issues.jboss.org/browse/WFLY-324 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Jason Greene > Fix For: 9.0.0.CR1 > > > Ability to use xinclude in the domain/xml/host.xml/standalone.xml documents. Not necessarily anywhere, but where the model supports storing the information. Upon changes to the model, persistence of the relevant elements would be to the specified file. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2821) Intermittent failures in EE resource injection tests

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2821?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2821: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 8.0.0.Final) > Intermittent failures in EE resource injection tests > ---------------------------------------------------- > > Key: WFLY-2821 > URL: https://issues.jboss.org/browse/WFLY-2821 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EE > Affects Versions: 8.0.0.CR1 > Reporter: Brian Stansberry > Assignee: David Lloyd > Fix For: 9.0.0.CR1 > > > The set of 5 failures shown below are recurring intermittently in the WF testsuite: > http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=8698&buildType... > org.jboss.as.test.integration.ee.injection.resource.enventry > EnvEntryInjectionTestCase.testNonExistantResourceCannotBeLookedUp > org.jboss.as.test.integration.ee.injection.resource.noncomponent > NonComponentResourceInjectionTestCase.testBindingDoesNotExist > org.jboss.as.test.integration.ee.injection.resource.persistencecontextref > PersistenceContextRefTestCase.testCorrectPersistenceUnitInjectedFromAnnotation2 > PersistenceContextRefTestCase.testCorrectPersistenceUnitInjectedFromPersistenceUnitRef > PersistenceContextRefTestCase.testCorrectPersistenceUnitInjectedFromRefInjectionTarget2 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-342) Reenable ClusteredSingleSignOnTestCase test to work with Undertow

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-342?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-342: ------------------------------ Fix Version/s: 9.0.0.CR1 (was: 8.0.0.Final) > Reenable ClusteredSingleSignOnTestCase test to work with Undertow > ------------------------------------------------------------------ > > Key: WFLY-342 > URL: https://issues.jboss.org/browse/WFLY-342 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Kabir Khan > Assignee: Paul Ferraro > Priority: Critical > Fix For: 9.0.0.CR1 > > Attachments: ClusteredSingleSignOnTestCase1.html, ClusteredSingleSignOnTestCase2.html, ClusteredSingleSignOnTestCase3.html > > > Test have been @Ignored until Undertow implements SSO. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2774) Non-distributed, stateful web applications cannot be load balanced using sticky sessions

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2774?page=com.atlassian.jira.plugin.... ] Jason Greene commented on WFLY-2774: ------------------------------------ This should be resolved once CR2 of undertow is included > Non-distributed, stateful web applications cannot be load balanced using sticky sessions > ---------------------------------------------------------------------------------------- > > Key: WFLY-2774 > URL: https://issues.jboss.org/browse/WFLY-2774 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.0.0.CR1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > Fix For: 8.0.0.Final > > > In AS7, one could configure a load balancer with sticky sessions to support load balancing for non-distributed web applications. > While the distributed session manager supports parsing and formatting of the instance-id from/to the session id, the in-memory session manager does not. > The use case for this are stateful web applications that do not require high-availability of state (e.g. a stateless web-app that uses container managed authentication), but would also like to scale beyond the capacity of a single server. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1535) SSLEJBRemoteClientTestCase runs into intermittent failures

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-1535?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-1535: ------------------------------- Fix Version/s: 9.0.0.CR1 (was: 8.0.0.Final) > SSLEJBRemoteClientTestCase runs into intermittent failures > ---------------------------------------------------------- > > Key: WFLY-1535 > URL: https://issues.jboss.org/browse/WFLY-1535 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: 8.0.0.Alpha1 > Reporter: jaikiran pai > Assignee: Paul Ferraro > Priority: Critical > Fix For: 9.0.0.CR1 > > > SSLEJBRemoteClientTestCase runs into intermittent failures on TeamCity. To make matters worse, a failure in one test method can have a side effect on other test methods in that testcase, given the way it's written. The entire run is here http://teamcity.cafe-babe.org/viewLog.html?buildId=5251&tab=buildResultsD.... -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2641) ARQ upgrade likely to cause test failures

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2641?page=com.atlassian.jira.plugin.... ] Jason Greene reassigned WFLY-2641: ---------------------------------- Assignee: Jason Greene (was: Aslak Knutsen) > ARQ upgrade likely to cause test failures > ------------------------------------------ > > Key: WFLY-2641 > URL: https://issues.jboss.org/browse/WFLY-2641 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Thomas Diesler > Assignee: Jason Greene > Priority: Blocker > Fix For: 9.0.0.CR1 > > > {code} > testSimpleBundleWithWabExtension(org.jboss.test.osgi.example.webapp.WebAppTestCase) Time elapsed: 0.028 sec <<< ERROR! > java.lang.NullPointerException: null > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:290) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > {code} -- 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, 9 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 January 2014