August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBPORTAL-910) On 2.4 release migration application should be exposed as separate binary

by Rali Genova (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-910?page=comments#action_12341225 ] Rali Genova commented on JBPORTAL-910: -------------------------------------- http://docs.jboss.com/jbportal/v2.4/reference-guide/en/html/changelog.html Docs on how to run the migration app > On 2.4 release migration application should be exposed as separate binary > ------------------------------------------------------------------------- > > Key: JBPORTAL-910 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-910 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Portal Migration > Reporter: Boleslaw Dawidowicz > Assigned To: Rali Genova > Fix For: 2.6 Final > > > When 2.4 will be released we should expose Migration Application as separate pre-build web application archive > It can be placed either at > - portletswap > - portal download area at sourceforge > - both above :) > and will enable people to avoid building it from sources. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBMESSAGING-178) Run TCK continuously in top of JBoss Messaging

by Rajesh Rajasekaran (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-178?page=all ] Rajesh Rajasekaran reassigned JBMESSAGING-178: ---------------------------------------------- Assignee: Prabhat Jha (was: Rajesh Rajasekaran) > Run TCK continuously in top of JBoss Messaging > ---------------------------------------------- > > Key: JBMESSAGING-178 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-178 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Assigned To: Prabhat Jha > Fix For: 1.2.0.CR1 > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-981) meta header elements are not supported

by Chris Laprun (JIRA)

meta header elements are not supported -------------------------------------- Key: JBPORTAL-981 URL: http://jira.jboss.com/jira/browse/JBPORTAL-981 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.4 Final Reporter: Chris Laprun Assigned To: Chris Laprun Priority: Minor Fix For: 2.4 Final HeaderContentMetadata only handles script and link elements. -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-980) Test page in portal is in bad shape....

by Chris Laprun (JIRA)

Test page in portal is in bad shape.... --------------------------------------- Key: JBPORTAL-980 URL: http://jira.jboss.com/jira/browse/JBPORTAL-980 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Samples, Portal Test Affects Versions: 2.4 Final Reporter: Chris Laprun Fix For: 2.4 Final Lots of portlets on the test page cannot be rendered, are not found or otherwise don't work. Plus, the navigation is confusing: the pages portlet comes and goes and its content varies from sub-page (?) to sub-page... -- 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, 11 months

1
2
0 / 0

[JBoss JIRA] Commented: (JBAS-3358) Work directory shouldn't be deleted on Context Destroy

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3358?page=comments#action_12341219 ] Anil Saldhana commented on JBAS-3358: ------------------------------------- Also, as part of this JIRA issue, JBossContextConfig has been made default at the host level. > Work directory shouldn't be deleted on Context Destroy > ------------------------------------------------------ > > Key: JBAS-3358 > URL: http://jira.jboss.com/jira/browse/JBAS-3358 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Affects Versions: JBossAS-4.0.4.GA > Reporter: Javid Jamae > Assigned To: Anil Saldhana > Fix For: JBossAS-4.0.5.GA > > > I tried enabling HTTP session persistence, but found out that the default directory that it writes to is the work directory. Working with JBoss support, I discovered that the work directory is deleted when the server shuts down. > Either the work directory should not be deleted, or the default directory where the persistent HTTP sessions are serialized to a file should be changed to be in a directory other than work (since it is being deleted). -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBAS-3358) Work directory shouldn't be deleted on Context Destroy

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3358?page=all ] Anil Saldhana resolved JBAS-3358. --------------------------------- Resolution: Done Made configurable at the tomcat service level. There is an attribute that can be changed in deploy/jbossweb-tomcat55.sar/META-INF/jboss-service.xml  <attribute name="DeleteWorkDirOnContextDestroy">false</attribute> Do we need a testcase for this? > Work directory shouldn't be deleted on Context Destroy > ------------------------------------------------------ > > Key: JBAS-3358 > URL: http://jira.jboss.com/jira/browse/JBAS-3358 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Affects Versions: JBossAS-4.0.4.GA > Reporter: Javid Jamae > Assigned To: Anil Saldhana > Fix For: JBossAS-4.0.5.GA > > > I tried enabling HTTP session persistence, but found out that the default directory that it writes to is the work directory. Working with JBoss support, I discovered that the work directory is deleted when the server shuts down. > Either the work directory should not be deleted, or the default directory where the persistent HTTP sessions are serialized to a file should be changed to be in a directory other than work (since it is being deleted). -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAOP-281) ObservableUnitTestCase fails in Jboss 4.0.5.CR1

by Kabir Khan (JIRA)

ObservableUnitTestCase fails in Jboss 4.0.5.CR1 ----------------------------------------------- Key: JBAOP-281 URL: http://jira.jboss.com/jira/browse/JBAOP-281 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 1.5.1.GA -- 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, 11 months

1
2
0 / 0

[JBoss JIRA] Closed: (JBAS-2637) Reduce memory footprint of HAPartition's state transfer

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2637?page=all ] Brian Stansberry closed JBAS-2637. ---------------------------------- > Reduce memory footprint of HAPartition's state transfer > ------------------------------------------------------- > > Key: JBAS-2637 > URL: http://jira.jboss.com/jira/browse/JBAS-2637 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > HAPartitionImpl's state transfer mechanism marshalls state to a byte[] using java.io.ByteArrayOutputStream. This memory-inefficient, as BAOS.toByteArray() makes a copy of the internal byte[]. Need to move class org.jboss.cache.util.ExposedByteArrayOutputStream to jboss-common and use it instead. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBAS-2637) Reduce memory footprint of HAPartition's state transfer

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2637?page=all ] Brian Stansberry resolved JBAS-2637. ------------------------------------ Fix Version/s: (was: JBossAS-5.0.0.Beta) Resolution: Won't Fix Once streaming state transfer is in place (JBAS-3315), that's the mechanism to ensure large states transfer effectively. Also, in AS 5 only HASessionState uses ClusterPartition state transfer. > Reduce memory footprint of HAPartition's state transfer > ------------------------------------------------------- > > Key: JBAS-2637 > URL: http://jira.jboss.com/jira/browse/JBAS-2637 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > HAPartitionImpl's state transfer mechanism marshalls state to a byte[] using java.io.ByteArrayOutputStream. This memory-inefficient, as BAOS.toByteArray() makes a copy of the internal byte[]. Need to move class org.jboss.cache.util.ExposedByteArrayOutputStream to jboss-common and use it instead. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-2440) Review use of HashMap vs. Map as a type declaration in DistributedReplicantManagerImpl

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2440?page=all ] Brian Stansberry reassigned JBAS-2440: -------------------------------------- Assignee: Jerry Gauthier (was: Brian Stansberry) Jerry, do you have time to do this as part of the conversion of DRM to use JBoss Cache? > Review use of HashMap vs. Map as a type declaration in DistributedReplicantManagerImpl > -------------------------------------------------------------------------------------- > > Key: JBAS-2440 > URL: http://jira.jboss.com/jira/browse/JBAS-2440 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Brian Stansberry > Assigned To: Jerry Gauthier > > There are a lot of places in DistributedReplicantManagerImpl where variables are declared as HashMap instead of Map. Since a number of internal members have been changed to ConcurrentReaderHashMap, this is dangerous (see JBAS-2439). Need to review and where possible use Map instead of HashMap. -- 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, 11 months

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 August 2006