September 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-1049) Concurrent hashmaps: set parameters via system properties

by Bela Ban (JIRA)

Concurrent hashmaps: set parameters via system properties --------------------------------------------------------- Key: JGRP-1049 URL: https://jira.jboss.org/jira/browse/JGRP-1049 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.9 ConcurrentHashMap ----------------- CCHMs have a default initial capacity (16), load factor (0.75) and concurrency level (16). These are OK for most scenarios, but we have to investigate whether these values are sufficient for 1000 node clusters. When for example 1000 threads from different senders access the same CCHM, we need to make sure we don't have high contention, ie. by spreading a 1000 senders over 16 buckets. Investigate whether we should add CCHM initial sizes, load factors and concurrency levels as system properties. With ergonomics [1], we could for example set bucket sizes for CCHMs dynamically, e.g. based on cluster size. [1] https://jira.jboss.org/jira/browse/JGRP-1037 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-8244) Fix org.jboss.test.ws.jaxws.ejb3Integration.WebServiceTestCase

by Brian Stansberry (JIRA)

Fix org.jboss.test.ws.jaxws.ejb3Integration.WebServiceTestCase -------------------------------------------------------------- Key: JBAS-8244 URL: https://jira.jboss.org/browse/JBAS-8244 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite, Web Services Reporter: Brian Stansberry Fix For: 6.0.0.Final http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-test... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

4
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2151) Global interceptor in ejb-jar.xml ignores @Asynchronous

by Juergen Zimmermann (JIRA)

Global interceptor in ejb-jar.xml ignores @Asynchronous ------------------------------------------------------- Key: EJBTHREE-2151 URL: https://jira.jboss.org/browse/EJBTHREE-2151 Project: EJB 3.0 Issue Type: Bug Environment: JBossAS 6.0.0.M4 Reporter: Juergen Zimmermann In ejb-jar.xml I'm having a global interceptor (it's for logging all public methods of an EJB during the development phase). However, when I annotate a method using @Asynchronous, the annotated public method is just ignored. There is no stacktrace or anything else in the log file. Declaration in ejb-jar.xml: <ejb-jar ...version="3.1"> ... <assembly-descriptor> <interceptor-binding> <ejb-name>*</ejb-name> <interceptor-class> de.hska.util.LoggingInterceptor </interceptor-class> </interceptor-binding> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1790) Provide support for resolving @EJB/ejb-local-ref references to no-interface view

by jaikiran pai (JIRA)

Provide support for resolving @EJB/ejb-local-ref references to no-interface view -------------------------------------------------------------------------------- Key: EJBTHREE-1790 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1790 Project: EJB 3.0 Issue Type: Task Affects Versions: EJB 3.1 Reporter: jaikiran pai Assignee: jaikiran pai The EJB3.1 spec allows no-interface view reference, using a @EJB and through ejb-local-ref. We need to have a resolver (similar to FirstMatchEjbReferenceResolver) which does this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-859) Message: add LOOPBACK flag

by Bela Ban (JIRA)

Message: add LOOPBACK flag -------------------------- Key: JGRP-859 URL: https://jira.jboss.org/jira/browse/JGRP-859 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.8 When LOOPBACK is set in a message, the UNICAST.loopback and TP.loopback flags are overridden and a message is looped back up the stack, regardless of the value of the property. This is useful for example for VIEW and SUSPECT messages, where a socket could be disconnected (e.g. cable plugged) and we still need to be able to receive our own messages. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1933) EJB 3.1 - Support deployment of EJBs packaged in .war files

by jaikiran pai (JIRA)

EJB 3.1 - Support deployment of EJBs packaged in .war files ------------------------------------------------------------ Key: EJBTHREE-1933 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1933 Project: EJB 3.0 Issue Type: Task Reporter: jaikiran pai Assignee: jaikiran pai Fix For: EJB 3.1 As per the EJB 3.1 spec section 20.4, implement the support for deploying EJBs packaged in .war files. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2109) Upgrade to jboss-ejb3-timerservice-spi 1.0.1 to utilize the MultiTimeoutMethodTimedObjectInvoker for EJB containers

by jaikiran pai (JIRA)

Upgrade to jboss-ejb3-timerservice-spi 1.0.1 to utilize the MultiTimeoutMethodTimedObjectInvoker for EJB containers ------------------------------------------------------------------------------------------------------------------- Key: EJBTHREE-2109 URL: https://jira.jboss.org/browse/EJBTHREE-2109 Project: EJB 3.0 Issue Type: Task Components: core Reporter: jaikiran pai Assignee: jaikiran pai Fix For: EJB3_1 1.0.8 EJBTHREE-2108 introduced MultiTimeoutMethodTimedObjectInvoker. Upgrade to this latest version of jboss-ejb3-timerservice-spi to utilize this MultiTimeoutMethodTimedObjectInvoker in EJB3 core containers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2093) Log the jndi names to which the singleton bean's views are being bound

by jaikiran pai (JIRA)

Log the jndi names to which the singleton bean's views are being bound ---------------------------------------------------------------------- Key: EJBTHREE-2093 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2093 Project: EJB 3.0 Issue Type: Task Components: singleton Affects Versions: EJB3_1 1.0.7 Reporter: jaikiran pai Assignee: jaikiran pai For non-Singleton beans, we log the JNDI names to which a bean's views are being bound at INFO. However for singleton beans we currently don't do this. It's pretty useful for an end user to quickly find out the jndi names on the console. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2075) Track dependency upgrades for EJB3_1 1.0.8

by jaikiran pai (JIRA)

Track dependency upgrades for EJB3_1 1.0.8 ------------------------------------------ Key: EJBTHREE-2075 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2075 Project: EJB 3.0 Issue Type: Task Components: ejb3_1 Reporter: jaikiran pai Assignee: jaikiran pai Fix For: EJB3_1 1.0.8 Track dependency upgrades for ejb3_1 1.0.8 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2118) Integrate BeanManager with core Container(s)

by jaikiran pai (JIRA)

Integrate BeanManager with core Container(s) -------------------------------------------- Key: EJBTHREE-2118 URL: https://jira.jboss.org/browse/EJBTHREE-2118 Project: EJB 3.0 Issue Type: Task Components: core Reporter: jaikiran pai Assignee: jaikiran pai As discussed over IRC, core containers (org.jboss.ejb3.Container) == org.jboss.ejb3.context.spi.BeanManager. This currently hasn't yet being integrated. Integrating the core containers with the BeanManager will pave the way for allowing to deprecate the TimerServicePropertyInjector and instead use JNDIPropertyInjector, to inject TimerService via ENC (see EJBTHREE-2113 for the details). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
1
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 September 2010