July 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBFORUMS-221) Rewrite FloodInterceptor

by Ryszard Kozmik (JIRA)

Rewrite FloodInterceptor ------------------------ Key: JBFORUMS-221 URL: http://jira.jboss.com/jira/browse/JBFORUMS-221 Project: JBoss Forums Issue Type: Task Components: Forum Model Layer Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Fix For: 1.1.0 Alpha FloodInterceptor no longer works after view refactoring but we need it and it has to work in a way or another. -- 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

19 years

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1002) Fix MVEL Accumulate to work in multi-workingmemories environments

by Edson Tirelli (JIRA)

Fix MVEL Accumulate to work in multi-workingmemories environments ----------------------------------------------------------------- Key: JBRULES-1002 URL: http://jira.jboss.com/jira/browse/JBRULES-1002 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.0.MR3 Reporter: Edson Tirelli Assigned To: Edson Tirelli Fix For: 4.0.0.MR4 -- 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

19 years

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1008) refactor the event interfaces on working memory so both stateless and stateful sessions can support them

by Mark Proctor (JIRA)

refactor the event interfaces on working memory so both stateless and stateful sessions can support them -------------------------------------------------------------------------------------------------------- Key: JBRULES-1008 URL: http://jira.jboss.com/jira/browse/JBRULES-1008 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 4.0.0.MR4 We need the AuditFileLogger to work with both stateful and stateless sessions, so the event management methods need to be refactored to a common interface. -- 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

19 years

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1007) rename xor-group to activation-group

by Mark Proctor (JIRA)

rename xor-group to activation-group ------------------------------------ Key: JBRULES-1007 URL: http://jira.jboss.com/jira/browse/JBRULES-1007 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Decision tables Reporter: Mark Proctor Assigned To: Michael Neale Fix For: 4.0.0.MR4 -- 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

19 years

2
1
0 / 0

[JBoss JIRA] Resolved: (JBPORTAL-860) Update DTDs to reflect changes in descriptors.

by Chris Laprun (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-860?page=all ] Chris Laprun resolved JBPORTAL-860. ----------------------------------- Resolution: Done > Update DTDs to reflect changes in descriptors. > ---------------------------------------------- > > Key: JBPORTAL-860 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-860 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal Core > Affects Versions: 2.4 Final, 2.6 Final, 2.6.1 Final > Reporter: Chris Laprun > Fix For: 2.6.2 Final, 2.8 Final > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Update and document changes. Should we move to XSD since some of the DTD elements don't seem to reflect the internal structure of descriptors. -- 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

19 years

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1131) Genericize CacheJmxWrapper

by Brian Stansberry (JIRA)

Genericize CacheJmxWrapper -------------------------- Key: JBCACHE-1131 URL: http://jira.jboss.com/jira/browse/JBCACHE-1131 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Manik Surtani Fix For: 2.0.0.CR4 Make it CacheJmxWrapperMBean<K, V> and CacheJmxWrapper<K, V> and public Cache<K, V> getCache(). Manik, I'm leaving it assigned to you to give you a chance to reject it if you don't want this API change in CR4. If it's OK, just assign back to me and I'll do it. -- 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

19 years

2
3
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-265) Soak tests

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-265?page=all ] Clebert Suconic closed JBMESSAGING-265. --------------------------------------- Resolution: Done > Soak tests > ---------- > > Key: JBMESSAGING-265 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-265 > Project: JBoss Messaging > Issue Type: Task > Reporter: Ovidiu Feodorov > Assigned To: Clebert Suconic > Fix For: 1.4.0.CR1 > > > A test that runs long enough and sends a significant number of messages into the server; used to detect memory leaks and failure under load -- 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

19 years

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1004) Update doco for new clustering and attributes

by Tim Fox (JIRA)

Update doco for new clustering and attributes --------------------------------------------- Key: JBMESSAGING-1004 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1004 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.4.0.CR1 Also expand the clustering section describing deploying distributed and non distributed destinations. Explain distributed queues and topics and preserveOrdering setting. -- 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

19 years

1
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-1139) Setting Option ineffective if CacheLoader or BuddyReplication is used

by Brian Stansberry (JIRA)

Setting Option ineffective if CacheLoader or BuddyReplication is used --------------------------------------------------------------------- Key: JBCACHE-1139 URL: http://jira.jboss.com/jira/browse/JBCACHE-1139 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 1.4.1.SP3 Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Critical Fix For: 1.4.1.SP4 Both CacheLoaderInterceptor and DataGravitationInterceptor have "lock" methods that create a MethodCall and pass it to the head of the interceptor chain. Problem is, when the TxInterceptor handles that "lock" call, it will scrub any Option from the thread on the way out. Once this happens, the option is effectively lost from the main call. A major effect of this is BuddyReplication with autoDataGravitationEnabled=false does not work if a CacheLoader is configured. You can't effectively set a setForceDataGravitation(true) option, as the CacheLoaderInterceptor.lock call will scrub the option. This breaks buddy replication for EJB3 SFSBs, which is the reason I marked this Critical. I'm about to check in a change to BuddyReplicationWithCacheLoaderTest that will demonstrate the issue. Buddy replication for EJB3 SFSBs works fine in AS trunk w/ JBC 2.0.0.CR3, so I'm assuming this issue doesn't exist in 2.0. I'll port the unit test to JBC HEAD though. I have a simple solution whereby in the lock() methods, any existing Option is cached before the method call is dispatched, and then rebound to the thread in a finally block. This allows the unit test to pass, and EJB3 BR works. I'll check it in once the JBC testsuite runs and shows no regressions. -- 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

19 years

1
1
0 / 0

[JBoss JIRA] Commented: (JBAS-2065) Web container needs to call javax.faces.FactoryFinder.releaseFactories() at undeployment

by Alexei Novikov (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2065?page=comments#action_12368917 ] Alexei Novikov commented on JBAS-2065: -------------------------------------- Calling releaseFactories() by the MyFaces ServletContextListener does not actually release ClassLoaders because of this bug: http://issues.apache.org/jira/browse/MYFACES-1558 MyFaces FactoryFinder still holds references to ClassLoaders in a static hash map. > Web container needs to call javax.faces.FactoryFinder.releaseFactories() at undeployment > ---------------------------------------------------------------------------------------- > > Key: JBAS-2065 > URL: http://jira.jboss.com/jira/browse/JBAS-2065 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Affects Versions: JBossAS-4.0.3RC1 > Reporter: Stan Silvert > Assigned To: Stan Silvert > Priority: Minor > > Now that we have JSF integrated as part of the Web Container, there will only be one instance of javax.faces.FactoryFinder per JVM. FactoryFinder provides a method called releaseFactories() which is intended to be used in situations where JSF is integrated as ours now is. It dereferences the various per-app factories used. These factories are stored in a Map that is keyed by the web app's context classloader. > See http://java.sun.com/j2ee/javaserverfaces/1.1/docs/api/javax/faces/Factory... > Though I have not verified it, not calling releaseFactories() should cause a memory leak any time a JSF application is undeployed or redeployed. Incidentally, this leak probably occurs 4.0.2 when two JSF applications use JBossWebLoader=true. > To fix this according to the JSF spec, we should call FactoryFinder.releaseFactories() any time we undeploy a web application. Of course, we would also need to make sure that the FactoryFinder class exists in case JSF is removed from JBoss AS. -- 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

19 years

1
0
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 July 2007