March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3910) Upgrade JBoss Cache to 2.0.0.Alpha2

by Dimitris Andreadis (JIRA)

Upgrade JBoss Cache to 2.0.0.Alpha2 ----------------------------------- Key: JBAS-3910 URL: http://jira.jboss.com/jira/browse/JBAS-3910 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JBoss Cache Reporter: Dimitris Andreadis Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta2 Decide whether to go with an JBC Alpha or Beta version -- 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 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3862) Allow direct injection of target into HASingletonController

by Brian Stansberry (JIRA)

Allow direct injection of target into HASingletonController ----------------------------------------------------------- Key: JBAS-3862 URL: http://jira.jboss.com/jira/browse/JBAS-3862 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta1 HASingletonController currently exposes a targetName attribute of type ObjectName, and then uses JMX calls to invoke the start/stop methods on the target. We need to support direct injection of the target and invocation via reflection. The old targetName attribute should be deprecated (but still supported for backward compatiblity). -- 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 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-4179) Update interfaces for HASingletonEvictionPolicy

by Brian Stansberry (JIRA)

Update interfaces for HASingletonEvictionPolicy ----------------------------------------------- Key: JBAS-4179 URL: http://jira.jboss.com/jira/browse/JBAS-4179 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-5.0.0.Beta1, JBossAS-4.2.0.CR1 Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.GA The interfaces for this are a bit JMX-centric for an AS 5 feature. Will make an HASingletonEvictionPolicy interface, with the current HASingletonEvictionPolicyMBean interface a trivial subinterface. HASingletonSupportMBean method names will just be get/setElectionPolicy with type being HASingletonEvictionPolicy. Want to fix this for 4.2.0.GA as well, since release timing means that release is where this stuff will first appear. -- 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 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1306) On the user portlet, there is an unused "roles" column

by oberiko (JIRA)

On the user portlet, there is an unused "roles" column ------------------------------------------------------ Key: JBPORTAL-1306 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1306 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.6.Alpha2 Reporter: oberiko Priority: Minor The roles column on the user portlet (found on the results screen after searching for users) is never populated. -- 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 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1305) Portlet relocation in management screen causes error

by oberiko (JIRA)

Portlet relocation in management screen causes error ---------------------------------------------------- Key: JBPORTAL-1305 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1305 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.6.Alpha2 Environment: Windows XP SP2, JBoss Portal 2.6A2 + AS (bundle), Firefox 2.0.0.2 Reporter: oberiko Portlets in the home/default screen in the admin region have locational problems. 1) Portlets are initially placed vertically instead of horizontally, even though they are in separate columns (top-down portlets) 2) When the positions are switched between the left and the center, the portlets overlap 3) From the 2nd point, when the management portlet is attempted to move left (into the same column as the catalog portlet), the management portlet displays an error. 4) This error persists until logging out and logging back in. 5) On logging back in, it seems to work until an attempt is made to select the admin --> default page in the management portlet, at which point the error re-appears. -- 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 months

2
7
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1308) Columns in user portlet search results are not aligned correctly.

by oberiko (JIRA)

Columns in user portlet search results are not aligned correctly. ----------------------------------------------------------------- Key: JBPORTAL-1308 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1308 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.6.Alpha2 Environment: Windows XP + SP2, Firefox 2.0.0.2, JBoss Portal 2.6A2 + AS (bundle) Reporter: oberiko Priority: Minor Records in every second column in the users portal search result have an additional space in front of each field. This causes all of the columns to have a zig-zag effect. -- 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 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1304) cms tests fail in CC run

by Prabhat Jha (JIRA)

cms tests fail in CC run ------------------------ Key: JBPORTAL-1304 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1304 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.6.Alpha2 Reporter: Prabhat Jha Assigned To: Prabhat Jha We need to figure out why cms tests fail in CC but pass when run locally on Windows. It fails when run locally on dev03 as well. It passes for Thomas in his local linux box. Weird. Most of the tests failw with this error: avax.jcr.RepositoryException at org.apache.jackrabbit.core.SearchManager.initializeQueryHandler(SearchManager.java:525) at org.apache.jackrabbit.core.SearchManager.<init>(SearchManager.java:267) at org.apache.jackrabbit.core.RepositoryImpl$WorkspaceInfo.getSearchManager(RepositoryImpl.java:1509) at org.apache.jackrabbit.core.RepositoryImpl.initWorkspace(RepositoryImpl.java:546) at org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:254) at org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:497) at org.jboss.portal.cms.impl.jcr.jackrabbit.JackrabbitJCRService.start(JackrabbitJCRService.java:105) at org.jboss.portal.cms.impl.jcr.JCRCMS.startJCR(JCRCMS.java:334) at org.jboss.portal.cms.impl.jcr.JCRCMS.startService(JCRCMS.java:299) at org.jboss.portal.test.cms.commands.AbstractCommandTestCase.setUp(AbstractCommandTestCase.java:69) at org.jboss.portal.common.test.junit.POJOJUnitTest.invoke(POJOJUnitTest.java:155) at org.jboss.portal.common.test.junit.JUnitAdapter$3.runBare(JUnitAdapter.java:121) at org.jboss.portal.common.test.junit.JUnitAdapter$2.visit(JUnitAdapter.java:136) at org.jboss.portal.common.test.info.TestInfo.internalVisit(TestInfo.java:138) at org.jboss.portal.common.test.info.TestContainerInfo.internalVisit(TestContainerInfo.java:97) at org.jboss.portal.common.test.info.TestItemInfo.visit(TestItemInfo.java:211) at org.jboss.portal.common.test.junit.JUnitAdapter.run(JUnitAdapter.java:140) at org.jboss.portal.common.test.junit.JUnitAdapter.run(JUnitAdapter.java:89)Caused by: java.lang.IllegalArgumentException at org.apache.commons.collections.BeanMap.put(BeanMap.java:374) at org.apache.jackrabbit.core.config.BeanConfig.newInstance(BeanConfig.java:109) at org.apache.jackrabbit.core.SearchManager.initializeQueryHandler(SearchManager.java:519) ... 30 morejava.lang.IllegalArgumentException at org.apache.commons.collections.BeanMap.put(BeanMap.java:374) at org.apache.jackrabbit.core.config.BeanConfig.newInstance(BeanConfig.java:109) at org.apache.jackrabbit.core.SearchManager.initializeQueryHandler(SearchManager.java:519) at org.apache.jackrabbit.core.SearchManager.<init>(SearchManager.java:267) at org.apache.jackrabbit.core.RepositoryImpl$WorkspaceInfo.getSearchManager(RepositoryImpl.java:1509) at org.apache.jackrabbit.core.RepositoryImpl.initWorkspace(RepositoryImpl.java:546) at org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:254) at org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:497) at org.jboss.portal.cms.impl.jcr.jackrabbit.JackrabbitJCRService.start(JackrabbitJCRService.java:105) at org.jboss.portal.cms.impl.jcr.JCRCMS.startJCR(JCRCMS.java:334) at org.jboss.portal.cms.impl.jcr.JCRCMS.startService(JCRCMS.java:299) at org.jboss.portal.test.cms.commands.AbstractCommandTestCase.setUp(AbstractCommandTestCase.java:69) at org.jboss.portal.common.test.junit.POJOJUnitTest.invoke(POJOJUnitTest.java:155) at org.jboss.portal.common.test.junit.JUnitAdapter$3.runBare(JUnitAdapter.java:121) at org.jboss.portal.common.test.junit.JUnitAdapter$2.visit(JUnitAdapter.java:136) at org.jboss.portal.common.test.info.TestInfo.internalVisit(TestInfo.java:138) at org.jboss.portal.common.test.info.TestContainerInfo.internalVisit(TestContainerInfo.java:97) at org.jboss.portal.common.test.info.TestItemInfo.visit(TestItemInfo.java:211) at org.jboss.portal.common.test.junit.JUnitAdapter.run(JUnitAdapter.java:140) at org.jboss.portal.common.test.junit.JUnitAdapter.run(JUnitAdapter.java:89) -- 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 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-826) RegionManager region map should be ConcurrentReaderHashMap

by Brian Stansberry (JIRA)

RegionManager region map should be ConcurrentReaderHashMap ---------------------------------------------------------- Key: JBCACHE-826 URL: http://jira.jboss.com/jira/browse/JBCACHE-826 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: 2.0.0.GA The regionMap in o.j.c.eviction.RegionManager is a Collections.synchronizedMap. This should be a ConcurrentReaderHashMap. If eviction is used, for every call the EvictionInterceptor makes a call that ends up doing a lookup in this map, so the synchronization becomes a choke point. I already made this change in HEAD along with some refactoring work on eviction configuration. -- 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 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-4123) Need an MC 2.0.0.Beta3 release

by Scott M Stark (JIRA)

Need an MC 2.0.0.Beta3 release ------------------------------ Key: JBAS-4123 URL: http://jira.jboss.com/jira/browse/JBAS-4123 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.Beta2 There is already a 2.0.0.Beta2 MC release that is simply the 2.0.0.Beta with the vfs classes extracted. A 2.0.0.Beta3 release that incorporates the needed JBAS-63 fixes as well as only trunk version updates is needed for AS5 Beta2. -- 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 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1279) Investigate (and solve, if possible) hang on Consumer deployment if Portal hasn't started yet

by Chris Laprun (JIRA)

Investigate (and solve, if possible) hang on Consumer deployment if Portal hasn't started yet --------------------------------------------------------------------------------------------- Key: JBPORTAL-1279 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1279 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.Alpha2 Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6.CR1 Hangs on WSDL access (seems like an error in wsdl4j). Try to see if we can react to WSDL being published... -- 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 months

1
5
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 2007