September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-563) Update the documentation with a Clustering Intro

by Ovidiu Feodorov (JIRA)

Update the documentation with a Clustering Intro ------------------------------------------------ Key: JBMESSAGING-563 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-563 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Critical Fix For: 1.2.0.Alpha1 -- 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, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-561) Write two simple examples (distributed queue/topic) and include them in the set shipped with the release

by Ovidiu Feodorov (JIRA)

Write two simple examples (distributed queue/topic) and include them in the set shipped with the release -------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-561 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-561 Project: JBoss Messaging Issue Type: Feature Request Components: Tests and Performance Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Critical Fix For: 1.2.0.Alpha1 -- 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, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-562) Adjust the installation script to support a clustered installation

by Ovidiu Feodorov (JIRA)

Adjust the installation script to support a clustered installation ------------------------------------------------------------------ Key: JBMESSAGING-562 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-562 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Critical Fix For: 1.2.0.Alpha1 -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-3676) Upgrade jboss-common to 1.0.0.GA

by Dimitris Andreadis (JIRA)

Upgrade jboss-common to 1.0.0.GA -------------------------------- Key: JBAS-3676 URL: http://jira.jboss.com/jira/browse/JBAS-3676 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-4.0.5.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, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-3699) Fix testsuite OOMEs

by Dimitris Andreadis (JIRA)

Fix testsuite OOMEs ------------------- Key: JBAS-3699 URL: http://jira.jboss.com/jira/browse/JBAS-3699 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Fix For: JBossAS-4.0.5.GA Container task to indentify and fix testsuite OOMEs -- 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, 9 months

1
5
0 / 0

[JBoss JIRA] Created: (JBAS-3730) Use caching, serialization and snapshots to speedup JBoss AS startup

by jarkko Lietolahti (JIRA)

Use caching, serialization and snapshots to speedup JBoss AS startup -------------------------------------------------------------------- Key: JBAS-3730 URL: http://jira.jboss.com/jira/browse/JBAS-3730 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: jarkko Lietolahti When using JBoss AS in development i feel that the startup time of AS is waaayyy too long, it's something between 20 seconds (very trimmed down version, almost ripped off of all the required services) to 1 minute on my 2GHz laptop with 2 gigabytes of memory. So speed up the startup time of standard(aka default with ejb3) JBoss AS. By this i mean speed up the startups especially in development environments. It's ok for the initial startup after clean installation to take more time. But during "clean" startup JBoss AS should use caching, serialization, snapshots and all the available ways to make the next startup lightning fast. By lightning fast i mean 2 to 5 seconds. This can ofcourse happen if nothing has changed in the configuration, which is usually the case during development where the AS has been shutdown for reasons like unrecorable error (like hanging transactions), severe hot code replace error (after which the as environment becomes too unstable to continue function correctly), or some configuration change which cannot be done while the as is "online". >From boot.log and system.log i can see that there are places where JBoss AS could "cache"/serialize/etc stuff and on next startup use the information from the "cache". I've been trying to do a graph of JBoss AS startup based on the logs to see where the startup process spends it moments. Maybe it would be possible to "cache" RepositoryClassLoader contents and avoid the cost of scanning default/lib directory for jar libaries which stay unchanged for most of the start-stop cycle (atleast during certain development phases). I also noticed on a dual core machine some of the activity during startup/deployment doesn't scale very well. At these phases total cpu usage is ~48-52 %, which indicates that the activity doesn't get the additional benefit of multi core / cpu environment. Of course, a mechanism to detect a change in the configuration/etc should be build also which would detect a change in configuration and reload the changed information. -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBSEAM-28) Context Listeners

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-28?page=all ] Gavin King closed JBSEAM-28. ---------------------------- Resolution: Done > Context Listeners > ----------------- > > Key: JBSEAM-28 > URL: http://jira.jboss.com/jira/browse/JBSEAM-28 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.1 > > > ContextListener objects would receive notifications of events like destroyContext(), getValue(), setValue(), etc. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBSEAM-28) Context Listeners

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-28?page=comments#action_12344355 ] Gavin King commented on JBSEAM-28: ---------------------------------- done and committed except for the create context events > Context Listeners > ----------------- > > Key: JBSEAM-28 > URL: http://jira.jboss.com/jira/browse/JBSEAM-28 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.1 > > > ContextListener objects would receive notifications of events like destroyContext(), getValue(), setValue(), etc. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBSEAM-28) Context Listeners

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-28?page=comments#action_12344354 ] Gavin King commented on JBSEAM-28: ---------------------------------- Or should it be postCreate/preDestroy instead of / in addition to the EJB events? > Context Listeners > ----------------- > > Key: JBSEAM-28 > URL: http://jira.jboss.com/jira/browse/JBSEAM-28 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.1 > > > ContextListener objects would receive notifications of events like destroyContext(), getValue(), setValue(), etc. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBSEAM-28) Context Listeners

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-28?page=all ] Gavin King updated JBSEAM-28: ----------------------------- Fix Version/s: 1.1 Priority: Major (was: Minor) I have implemented the following events: org.jboss.seam.preSetVariable.<name> org.jboss.seam.postSetVariable.<name> org.jboss.seam.preRemoveVariable.<name> org.jboss.seam.postRemoveVariable.<name> org.jboss.seam.preDestroyContext.<SCOPE> org.jboss.seam.postDestroyContext.<SCOPE> org.jboss.seam.beginConversation org.jboss.seam.endConversation org.jboss.seam.beginPageflow.<name> org.jboss.seam.createProcess.<name> org.jboss.seam.initProcess.<name> org.jboss.seam.initTask.<name> org.jboss.seam.startTask.<name> org.jboss.seam.endTask.<name> org.jboss.seam.postConstruct.<name> org.jboss.seam.preDestroy.<name> org.jboss.seam.prePassivate.<name> org.jboss.seam.postActivate.<name> Still need to do: org.jboss.seam.preCreateContext.<SCOPE> org.jboss.seam.postCreateContext.<SCOPE> > Context Listeners > ----------------- > > Key: JBSEAM-28 > URL: http://jira.jboss.com/jira/browse/JBSEAM-28 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.1 > > > ContextListener objects would receive notifications of events like destroyContext(), getValue(), setValue(), etc. -- 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, 9 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 September 2006