February 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2422) FireAllRulesRuleBaseUpdateListener to use a WeakReference<StatefulSession> to prevent memory leaks

by Juergen (JIRA)

FireAllRulesRuleBaseUpdateListener to use a WeakReference<StatefulSession> to prevent memory leaks -------------------------------------------------------------------------------------------------- Key: JBRULES-2422 URL: https://jira.jboss.org/jira/browse/JBRULES-2422 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.0.1.FINAL Reporter: Juergen Assignee: Mark Proctor I had similar issues with StatefulSession (instantiated via JSR94 api) not being released / GCed Investigating the Issue I found JBESB-1796 My problem was also caused by the session still being connected to a GC root via session -> FireAllRulesRuleBaseUpdateListener -> rulebase -> root Wouldn't it be more robust to use a WeakReference to the session in org.drools.base.FireAllRulesRuleBaseUpdateListener? or the listener itself? -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7687) Get the examples out of jbossha.jar

by Brian Stansberry (JIRA)

Get the examples out of jbossha.jar ----------------------------------- Key: JBAS-7687 URL: https://jira.jboss.org/jira/browse/JBAS-7687 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: JBossAS-6.0.0.M2 For years, example classes in the cluster module's src/examples dir have ended up in jbossha.jar. Get them out of there into a org.jboss.jbossas:jboss-as-cluster-examples jar. -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-7610) Update jboss-threads to 2.0.0.CR1

by David Lloyd (JIRA)

Update jboss-threads to 2.0.0.CR1 --------------------------------- Key: JBAS-7610 URL: https://jira.jboss.org/jira/browse/JBAS-7610 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: David Lloyd -- 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, 5 months

1
5
0 / 0

[JBoss JIRA] Created: (JBAS-7670) TomcatInjectionContainer not working for JSF managed beans.

by Stan Silvert (JIRA)

TomcatInjectionContainer not working for JSF managed beans. ----------------------------------------------------------- Key: JBAS-7670 URL: https://jira.jboss.org/jira/browse/JBAS-7670 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JSF, Web (Tomcat) service Affects Versions: JBossAS-6.0.0.M2 Reporter: Stan Silvert Assignee: Emanuel Muckenhuber I have a simple test in testsuite that does @PostConstruct and @PreDestroy on a managed bean. It's the JSFIntegrationUnitTestCase (see linked issue). One of the failures is caused because TomcatInjectionContainer doesn't seem to be doing anything when called. I've verified that the managed bean is passed to the proper postConstruct(), preDestroy(), and processInjectors() methods of TomcatInjectionContainer. However, the methods on the managed bean are never called. This worked in milestone 1 but appears broken in milestone 2. Can you take a look, Emanuel? -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2049) Look into tools for writing load tests

by Sohil Shah (JIRA)

Look into tools for writing load tests -------------------------------------- Key: JBPORTAL-2049 URL: http://jira.jboss.com/jira/browse/JBPORTAL-2049 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal QA Reporter: Sohil Shah Assigned To: Prabhat Jha Basically it would be nice to have a framework for writing load/stress tests to test non-UI components like backend CMS service, stateless business service layer etc. Some ideas but will let Prabhat research the tools to see what fits best: JunitPerf - http://clarkware.com/software/JUnitPerf.html Grinder - http://grinder.sourceforge.net/ -- 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, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2058) load test portal cms

by Prabhat Jha (JIRA)

load test portal cms -------------------- Key: JBPORTAL-2058 URL: http://jira.jboss.com/jira/browse/JBPORTAL-2058 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal CMS Reporter: Prabhat Jha Assigned To: Prabhat Jha This will be load testing just CMS part of JBoss Portal. Is following a valid test setup: I created a new portalcalled cms-test using portal admin ui and made that as a default portal. This portal contains only one CMS file . The resulting URL is http://localhost:8080/portal/portal/cms-test . If I have many simultaneous users hitting this URL, will this constitute a valid CMS load test setup? -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2469) add feature to CMS that allows to build SearchIndex in background not at the server startup time

by Gary Hu (JIRA)

add feature to CMS that allows to build SearchIndex in background not at the server startup time ------------------------------------------------------------------------------------------------ Key: JBPORTAL-2469 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2469 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal CMS Reporter: Gary Hu Assignee: Sohil Shah The SearchIndex feature takes long time during the server startup. Can we set it run at background not at the startup time? -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-237) Release Deployers 2.2.0.Alpha1

by Ales Justin (JIRA)

Release Deployers 2.2.0.Alpha1 ------------------------------ Key: JBDEPLOY-237 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-237 Project: JBoss Deployers Issue Type: Release Affects Versions: JBDEPLOY-2.0.9.GA Reporter: Ales Justin Assignee: Ales Justin Fix For: JBDEPLOY-2.2.0.Alpha1 Release notes: * https://jira.jboss.org/jira/secure/ReleaseNote.jspa?version=12314232&styl... -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-236) Thirdparty changes

by Ales Justin (JIRA)

Thirdparty changes ------------------ Key: JBDEPLOY-236 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-236 Project: JBoss Deployers Issue Type: Thirdparty Change Components: release Affects Versions: JBDEPLOY-2.0.9.GA Reporter: Ales Justin Fix For: JBDEPLOY-2.2.0.Alpha1 -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-235) Check unguarded calls to Logger.debug

by Ales Justin (JIRA)

Check unguarded calls to Logger.debug ------------------------------------- Key: JBDEPLOY-235 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-235 Project: JBoss Deployers Issue Type: Task Components: core Affects Versions: JBDEPLOY-2.0.8.SP1 Reporter: Ales Justin Assignee: Ales Justin Fix For: JBDEPLOY-2.0.9.GA, JBDEPLOY-2.2.x Check the unguarded calls to Logger.debug and Logger.debugf. -- 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, 5 months

1
3
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 February 2010