August 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1708) Simplify TransportConfiguration parameters

by Jeff Mesnil (JIRA)

Simplify TransportConfiguration parameters ------------------------------------------ Key: JBMESSAGING-1708 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1708 Project: JBoss Messaging Issue Type: Task Components: Configuration and Management Affects Versions: 2.0.0.beta4 Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 2.0.0 the TransportConfiguration parameters are represented in XML by: <param key="jbm.remoting.netty.tcpnodelay" value="false" type="Boolean"/> The user shouldn't have to specify the type attribute as the Acceptor/Connector implementation knows what type they require for a given param key. We can get rid of it. This would also simplify the Java representation from Map<String, Object> to a more constrained Map<String, String>. The current code to retrieve a param value can already retrieve a value from a String (as is the case for the JCA resource adapter). The key values could also be simplified as they are constrained by the acceptor/connector element. E.g. for INVM configuration, rename "jbm.remoting.invm.serverid" to "id" for Netty, rename "jbm.remoting.netty.host" to "host", etc. This would be more intuitive for the user. With these changes <acceptors> <acceptor name="netty-acceptor"> <factory-class>org.jboss.messaging.integration.transports.netty.NettyAcceptorFactory</factory-class> <param key="jbm.remoting.netty.host" value="192.168.0.10" type="String"/> <param key="jbm.remoting.netty.tcpnodelay" value="false" type="Boolean"/> <param key="jbm.remoting.netty.tcpsendbuffersize" value="1048576" type="Integer"/> <param key="jbm.remoting.netty.tcpreceivebuffersize" value="1048576" type="Integer"/> </acceptor> </acceptors> would become <acceptors> <acceptor name="netty-acceptor"> <factory-class>org.jboss.messaging.integration.transports.netty.NettyAcceptorFactory</factory-class> <param key="host" value="192.168.0.10"/> <param key="tcpnodelay" value="false"/> <param key="tcpsendbuffersize" value="1048576"/> <param key="tcpreceivebuffersize" value="1048576"/> </acceptor> </acceptors> without any loss of information. Another possible refinement would be to get rid of the <factory-class> element and replace if by a type attribute on <acceptor>/<connector> which could be either "invm" or "netty" and we can internally have a map between the type values and the class implementation. <factory-class> is completely generic but I doubt that adding another network framework is a trivial task. It makes the configuration of every user more complex that it could. If we want genericity, we could still externalize the type<->class mapping in a properties file. This will be modified by power users but remain unchanged for 99% of our users. With this change, the configuration would looks like: <acceptors> <acceptor name="netty-acceptor" type="netty"> <param key="host" value="192.168.0.10"/> <param key="tcpnodelay" value="false"/> <param key="tcpsendbuffersize" value="1048576"/> <param key="tcpreceivebuffersize" value="1048576"/> </acceptor> </acceptors> No more implementation detail obfuscates the configuration -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBID-166) Create a single cached JAXBContext for the object models

by Anil Saldhana (JIRA)

Create a single cached JAXBContext for the object models -------------------------------------------------------- Key: JBID-166 URL: https://jira.jboss.org/jira/browse/JBID-166 Project: JBoss Identity Issue Type: Sub-task Components: Identity-Federation Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: IDFED-1.0.0.GA -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7129) Test Target tests-scout-jaxr failures

by Anil Saldhana (JIRA)

Test Target tests-scout-jaxr failures ------------------------------------- Key: JBAS-7129 URL: https://jira.jboss.org/jira/browse/JBAS-7129 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JAXR service, Test Suite Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: JBossAS-5.2.0.Beta1 ============== tests-scout-jaxr: [mkdir] Created dir: /home/anil/Branch_5_x/testsuite/output/log [junit] Running org.jboss.test.jaxr.scout.JaxrBaseTestCase [junit] Running org.jboss.test.jaxr.scout.JaxrBaseTestCase [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1.685 sec [junit] Running org.jboss.test.jaxr.scout.basic.JaxrJNDIConnectionTestCase [junit] Running org.jboss.test.jaxr.scout.basic.JaxrJNDIConnectionTestCase [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.354 sec [junit] Running org.jboss.test.jaxr.scout.publish.JaxrDeleteAssociationTestCase [junit] Running org.jboss.test.jaxr.scout.publish.JaxrDeleteAssociationTestCase [junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 4.051 sec [junit] Test org.jboss.test.jaxr.scout.publish.JaxrDeleteAssociationTestCase FAILED [junit] Running org.jboss.test.jaxr.scout.publish.JaxrDeleteOrganizationTestCase [junit] Running org.jboss.test.jaxr.scout.publish.JaxrDeleteOrganizationTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 2.898 sec [junit] Running org.jboss.test.jaxr.scout.publish.JaxrSaveOrganizationTestCase [junit] Running org.jboss.test.jaxr.scout.publish.JaxrSaveOrganizationTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 2.687 sec [junit] Running org.jboss.test.jaxr.scout.publish.JaxrSaveServiceBindingTestCase [junit] Running org.jboss.test.jaxr.scout.publish.JaxrSaveServiceBindingTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.705 sec [junit] Running org.jboss.test.jaxr.scout.publish.infomodel.JaxrClassficationTestCase [junit] Running org.jboss.test.jaxr.scout.publish.infomodel.JaxrClassficationTestCase [junit] Tests run: 2, Failures: 1, Errors: 0, Time elapsed: 2.193 sec [junit] Test org.jboss.test.jaxr.scout.publish.infomodel.JaxrClassficationTestCase FAILED [junit] Running org.jboss.test.jaxr.scout.publish.infomodel.JaxrConfimAssociationTestCase [junit] Running org.jboss.test.jaxr.scout.publish.infomodel.JaxrConfimAssociationTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 4.265 sec [junit] Running org.jboss.test.jaxr.scout.query.JaxrBusinessQueryTestCase [junit] Running org.jboss.test.jaxr.scout.query.JaxrBusinessQueryTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.187 sec [junit] Running org.jboss.test.jaxr.scout.query.infomodel.JaxrFindAssociationsTestCase [junit] Running org.jboss.test.jaxr.scout.query.infomodel.JaxrFindAssociationsTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 4.505 sec ================================== -- 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

16 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBANN-22) Fold annotations from interface methods

by Jesper Pedersen (JIRA)

Fold annotations from interface methods --------------------------------------- Key: JBANN-22 URL: https://jira.jboss.org/jira/browse/JBANN-22 Project: JBoss Annotations Issue Type: Task Components: Core Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha2 Fold the annotations from methods defined on interfaces to the class representation. -- 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

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBANN-21) Annotation: HashCode and Equals

by Jesper Pedersen (JIRA)

Annotation: HashCode and Equals ------------------------------- Key: JBANN-21 URL: https://jira.jboss.org/jira/browse/JBANN-21 Project: JBoss Annotations Issue Type: Task Components: Core Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha2 Implement the public int hashCode() and public boolean equals(Object) methods on Annotation. -- 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

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBANN-13) Add configuration to the AnnotationScanner

by Jesper Pedersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBANN-13?page=com.atlassian.jira.plugi... ] Jesper Pedersen commented on JBANN-13: -------------------------------------- * Register against abstract class * Fold annotations from interfaces to the class > Add configuration to the AnnotationScanner > ------------------------------------------ > > Key: JBANN-13 > URL: https://jira.jboss.org/jira/browse/JBANN-13 > Project: JBoss Annotations > Issue Type: Task > Components: Core > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.0.0.Alpha3 > > > Allow the AnnotationScanner to be configured - switches could be > * Class level > * Constructor level > * Method level > * Field level > * Parameter level > * Throw exception on error -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBANN-19) Add a test case for a class implementing an interface with an annotation

by Jesper Pedersen (JIRA)

Add a test case for a class implementing an interface with an annotation ------------------------------------------------------------------------ Key: JBANN-19 URL: https://jira.jboss.org/jira/browse/JBANN-19 Project: JBoss Annotations Issue Type: Task Components: Core Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha2 -- 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

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBANN-20) AnnotationRepository: API enhancements

by Jesper Pedersen (JIRA)

AnnotationRepository: API enhancements -------------------------------------- Key: JBANN-20 URL: https://jira.jboss.org/jira/browse/JBANN-20 Project: JBoss Annotations Issue Type: Task Components: Core Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha2 Two enhancements to the AnnotationRepository interface. 1) Change List<Annotation> to Collection<Annotation> 2) Add methods which takes String as the lookup key -- 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

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-1016) memory leak in GMS protocol

by Miro Selent (JIRA)

memory leak in GMS protocol --------------------------- Key: JGRP-1016 URL: https://jira.jboss.org/jira/browse/JGRP-1016 Project: JGroups Issue Type: Bug Affects Versions: 2.7 Reporter: Miro Selent Assignee: Bela Ban Priority: Critical Found in org.jgroups.protocols.pbcast.GMS in a scenario where members were killed and restarted very frequently and one member is persistently running. The memory consumption icreased very quickly until OutOfMemory. Our analysis with JProfiler leads to the following assumption: The number of org.jgroups.stack.IpAddress held by merge_ack_collector icreases every time a member was (re)started. These instances were never removed because no MERGE events occured. This is completely clear since there was only one coordinator (the long running member). If GMS receives no MERGE event it never cleans up the stored IpAddress instances in the merge_ack_collector. -- 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

16 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JGRP-1015) Unit tests: enable "gossip-router" tests

by Bela Ban (JIRA)

Unit tests: enable "gossip-router" tests ---------------------------------------- Key: JGRP-1015 URL: https://jira.jboss.org/jira/browse/JGRP-1015 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 2.8 Currently not run with TestNG -- 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

16 years, 11 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 August 2009