March 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-1147) TP: make logical_addr_cache's timeout configurable

by Bela Ban (JIRA)

TP: make logical_addr_cache's timeout configurable -------------------------------------------------- Key: JGRP-1147 URL: https://jira.jboss.org/jira/browse/JGRP-1147 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.9 [email Maher Al Kilani] I am using jgroups lib. I noticed that when one of the nodes is down, the lazyRemovalCache class tags it removable and all the nodes stay in logical_addr_cache (in TP.java). So when sending a message we are actually sending to all the removable and the alive ones. How can configure the lazyRemovalCache class to not tag as removable but rather remove the dead nodes? Bela: let's make the timeout and max size configurable. Plus, possibly add a getter, so we can hard-flush the caceh programmatically -- 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, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBAOP-577) Optimize adding aspect bindings to instance advisors

by Kabir Khan (JIRA)

Optimize adding aspect bindings to instance advisors ---------------------------------------------------- Key: JBAOP-577 URL: http://jira.jboss.com/jira/browse/JBAOP-577 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.1.0.GA With the changes from JBAOP-575, it seems that the chains are still fully calculated when woven with GeneratedAdvisorInstrumentor if added for an instance. Run org.jboss.test.aop.dynamicgenadvisor.DynamicTester.testSimpleInstanceUsingDomainForMethod() and testInstanceUsingDomainForMethod() in a debugger to see what I mean -- 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

16 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBAOP-777) Remove aop.xml from asintegration/src/etc

by Flavia Rainone (JIRA)

Remove aop.xml from asintegration/src/etc ----------------------------------------- Key: JBAOP-777 URL: https://jira.jboss.org/jira/browse/JBAOP-777 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.1.9.Alpha1 Reporter: Flavia Rainone Assignee: Flavia Rainone The aop.xml file is being added to the jboss-60-install-jboss-aop-build.xml script as part of JBAOP-772. This file can be removed as soon as the bootstrap version in AS is updated with the classpool changes. -- 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, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-5570) URLDeploymentScanner: relies on FileInputStream finalizer - causes too many open files too easily

by Toomas Rￃﾃￂﾶmer (JIRA)

URLDeploymentScanner: relies on FileInputStream finalizer - causes too many open files too easily ------------------------------------------------------------------------------------------------- Key: JBAS-5570 URL: http://jira.jboss.com/jira/browse/JBAS-5570 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Deployers Affects Versions: JBossAS-4.2.2.GA Environment: Running on Debian unstable with JDK 1.6_06 Reporter: Toomas Rￃﾃￂﾶmer Assigned To: Ales Justin I'm a JavaRebel developer from ZeroTurnaround and have been debugging an issue with "Too many open files" with JBoss that we got reported against JavaRebel. The problem: Users are getting "Too many open files" exceptions when starting and then using JBoss. The reason: *) JBoss by default has configured a mbean org.jboss.deployment.scanner.URLDeploymentScanner which scans every 5 seconds for changes in the deployment descriptors *) The implementation does a connection = URL.openConnection() and then connection.getLastModified() to check for changes. *) The underlying implementation for regular files is java.io.FileInputStream *) The resource is not explicitly closed as FileInputStream will doit it by itself in the finalizer() *) Handles are freed when GC happens (finalizer logic) I came to this conclusion by getting the number of filehandles (lsof -p <jboss-pid>). Stepping through URLDeploymentScanner and seeing the handles grow by one after every connection.getLastModified(). In all tests the handles grow by one after this call. I also let the handles grow to a few thousand and then attached a debugger and after hitting a breakpoint called System.gc() on the JVM and the number of filehandles nicely went down to ~380 with my deployment folder. Possible solution: Check for the file modification date with explicit closing. -- 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

16 years, 1 month

8
9
0 / 0

[JBoss JIRA] Created: (JBNAME-49) Provide more context when a link fails to resolve

by Carlo de Wolf (JIRA)

Provide more context when a link fails to resolve ------------------------------------------------- Key: JBNAME-49 URL: https://jira.jboss.org/jira/browse/JBNAME-49 Project: JBoss Naming Issue Type: Feature Request Affects Versions: 5.0.5.Final Reporter: Carlo de Wolf Assignee: Carlo de Wolf Fix For: 5.1.0.Beta1 Caused by: javax.naming.NameNotFoundException: mdbtest not bound at org.jnp.server.NamingServer.getBinding(NamingServer.java:771) at org.jnp.server.NamingServer.getBinding(NamingServer.java:779) at org.jnp.server.NamingServer.getObject(NamingServer.java:785) at org.jnp.server.NamingServer.lookup(NamingServer.java:443) at org.jnp.server.NamingServer.lookup(NamingServer.java:399) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:728) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:688) at javax.naming.InitialContext.lookup(InitialContext.java:392) at org.jnp.interfaces.NamingContext.resolveLink(NamingContext.java:1350) ... 59 more -- 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, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2064) Remove references to outdated SNAP modules

by Andrew Lee Rubinger (JIRA)

Remove references to outdated SNAP modules ------------------------------------------ Key: EJBTHREE-2064 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2064 Project: EJB 3.0 Issue Type: Task Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger EJB3 trunk build is now failing on systems where older SNAPSHOTs are not cached, and they're no longer in the JBoss M2 Repo. Fix. -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2063) Document Build Instructions

by Andrew Lee Rubinger (JIRA)

Document Build Instructions --------------------------- Key: EJBTHREE-2063 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2063 Project: EJB 3.0 Issue Type: Task Reporter: Andrew Lee Rubinger Could be a top-level README in the trunk aggregator, pointing to a URL. From there we must document how all modules (and components) are built. Currently http://www.jboss.org/ejb3/build.html is a start. -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBREFLECT-107) Get BeanInfo working using the javassist implementation

by Kabir Khan (JIRA)

Get BeanInfo working using the javassist implementation ------------------------------------------------------- Key: JBREFLECT-107 URL: https://jira.jboss.org/jira/browse/JBREFLECT-107 Project: JBoss Reflection Issue Type: Feature Request Components: BeanInfo Reporter: Kabir Khan Assignee: Kabir Khan Fix For: JBossReflection.2.2.0-Alpha5 -- 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, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBREFLECT-112) Support lookup of dynamic proxies, javassist proxies and other generated classes from JavassistTypeInfoFactory

by Kabir Khan (JIRA)

Support lookup of dynamic proxies, javassist proxies and other generated classes from JavassistTypeInfoFactory -------------------------------------------------------------------------------------------------------------- Key: JBREFLECT-112 URL: https://jira.jboss.org/jira/browse/JBREFLECT-112 Project: JBoss Reflection Issue Type: Feature Request Reporter: Kabir Khan Assignee: Kabir Khan Fix For: JBossReflection.2.2.0-Alpha5 Simply return the Introspection implementation of the info -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7833) Upgrade to JBossWS 3.3.0.CR1

by Alessio Soldano (JIRA)

Upgrade to JBossWS 3.3.0.CR1 ---------------------------- Key: JBAS-7833 URL: https://jira.jboss.org/jira/browse/JBAS-7833 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Web Services Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: JBossAS-6.0.0.M3 -- 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, 1 month

2
7
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 March 2010