August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-460) Get rid of derelict SVN branches and tags

by Ovidiu Feodorov (JIRA)

Get rid of derelict SVN branches and tags ----------------------------------------- Key: JBMESSAGING-460 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-460 Project: JBoss Messaging Issue Type: Sub-task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Alpha1 There are a lot of unused branches and tags in the new SVN repository. These are migration artifacts and must be removed. -- 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

17 years, 11 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-222) Run "findbugs" on the code base

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-222?page=all ] Ovidiu Feodorov updated JBMESSAGING-222: ---------------------------------------- Assignee: (was: rajdeep dua) > Run "findbugs" on the code base > ------------------------------- > > Key: JBMESSAGING-222 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-222 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: 1.2.1 > > Attachments: build.xml, findbugs-0.9.5.zip, findbugs.patch, findbugs.patch, report-fb.xml > > > Run "findbugs" or similar regularily on the code base. Integrate it in the continous build process. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBMESSAGING-122) Implement the stats and monitoring MBean operations on destinations

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-122?page=all ] Ovidiu Feodorov reassigned JBMESSAGING-122: ------------------------------------------- Assignee: (was: Alex Fu) > Implement the stats and monitoring MBean operations on destinations > ------------------------------------------------------------------- > > Key: JBMESSAGING-122 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-122 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Configuration and Management > Affects Versions: 1.0.0 alpha PR1 (non-clustered) > Reporter: Tim Fox > Priority: Critical > Fix For: 1.2.1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Implement all the statistics and monitoring MBean operations on topics and queues, to bring up to level of functionality of JBossMQ. > E.g. message counts, message lists, subscription lists 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-185) Run objectweb JMS tests in top of JBoss Messaging

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-185?page=all ] Ovidiu Feodorov updated JBMESSAGING-185: ---------------------------------------- Assignee: (was: rajdeep dua) > Run objectweb JMS tests in top of JBoss Messaging > ------------------------------------------------- > > Key: JBMESSAGING-185 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-185 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Fix For: 1.2.1 > > Original Estimate: 4 days > Remaining Estimate: 4 days > -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-407) XARecovery integration of JBossMessaging with JBossTS

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-407?page=all ] Ovidiu Feodorov updated JBMESSAGING-407: ---------------------------------------- Fix Version/s: 1.2.0.Alpha1 > XARecovery integration of JBossMessaging with JBossTS > ----------------------------------------------------- > > Key: JBMESSAGING-407 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-407 > Project: JBoss Messaging > Issue Type: Patch > Components: Tests and Performance > Environment: JBoss 4.0.3SP1, JBossTs 4.2GA, JBOSS Messagig 1.0.1CR2 > Reporter: Madhusudhan Konda > Assigned To: Ovidiu Feodorov > Fix For: 1.2.0.Alpha1 > > Attachments: jms-recovery-patch-all.txt, jms.zip, JMSProviderXAResourceRecovery.java, xa.zip, XATestStandaloneRecovery.java > > Original Estimate: 1 week > Remaining Estimate: 1 week > > To make JBossMessaging XAResource as recoverable using JBossTS RecoveryManager -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-412) Please use build.properties for jboss.home in examples and the auto-install script

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-412?page=all ] Ovidiu Feodorov updated JBMESSAGING-412: ---------------------------------------- Fix Version/s: 1.2.0.CR1 Description: Right now, the build relies on JBOSS_HOME system variable. It is not the way most other projects do and it is broken on Mac. I would suggest to use a build.properties file in the root of the distribution. It has a jboss.home property that the user can edit. The user edits it once and can then use all ant tasks (auto install, examples etc.) in the distribution. (was: Right now, the build relies on JBOSS_HOME system variable. It is not the way most other projects do and it is broken on Mac. I would suggest to use a build.properties file in the root of the distribution. It has a jboss.home property that the user can edit. The user edits it once and can then use all ant tasks (auto install, examples etc.) in the distribution.) > Please use build.properties for jboss.home in examples and the auto-install script > ---------------------------------------------------------------------------------- > > Key: JBMESSAGING-412 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-412 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Build System > Reporter: Michael Yuan > Assigned To: Ovidiu Feodorov > Priority: Minor > Fix For: 1.2.0.CR1 > > > Right now, the build relies on JBOSS_HOME system variable. It is not the way most other projects do and it is broken on Mac. I would suggest to use a build.properties file in the root of the distribution. It has a jboss.home property that the user can edit. The user edits it once and can then use all ant tasks (auto install, examples etc.) in the distribution. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-407) XARecovery integration of JBossMessaging with JBossTS

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-407?page=comments#action_12... ] Ovidiu Feodorov commented on JBMESSAGING-407: --------------------------------------------- We need to take a decision on whether to use this or Adrian's or a combination. ASAP. > XARecovery integration of JBossMessaging with JBossTS > ----------------------------------------------------- > > Key: JBMESSAGING-407 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-407 > Project: JBoss Messaging > Issue Type: Patch > Components: Tests and Performance > Environment: JBoss 4.0.3SP1, JBossTs 4.2GA, JBOSS Messagig 1.0.1CR2 > Reporter: Madhusudhan Konda > Assigned To: Ovidiu Feodorov > Fix For: 1.2.0.Alpha1 > > Attachments: jms-recovery-patch-all.txt, jms.zip, JMSProviderXAResourceRecovery.java, xa.zip, XATestStandaloneRecovery.java > > Original Estimate: 1 week > Remaining Estimate: 1 week > > To make JBossMessaging XAResource as recoverable using JBossTS RecoveryManager -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-431) Socket transports should use configurable port

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-431?page=all ] Ovidiu Feodorov updated JBMESSAGING-431: ---------------------------------------- Fix Version/s: 1.2.0.Alpha1 Affects Version/s: 1.0.1.CR4 (was: 1.2.0.Alpha1) > Socket transports should use configurable port > ---------------------------------------------- > > Key: JBMESSAGING-431 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-431 > Project: JBoss Messaging > Issue Type: Task > Affects Versions: 1.0.1.CR4 > Reporter: Tim Fox > Assigned To: Ron Sigal > Fix For: 1.2.0.Alpha1 > > > Currently, for the socket and ssl transports, callbackservers will be opened on the next available port obtained. > Very occasionally this can fail since some other service uses the port before the callback server can. > Instead, the user should be able to configure a port used by the callbackserver to listen. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-431) Socket transports should use configurable port

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-431?page=all ] Ovidiu Feodorov updated JBMESSAGING-431: ---------------------------------------- Affects Version/s: 1.2.0.Alpha1 Assignee: Ron Sigal (was: Tim Fox) > Socket transports should use configurable port > ---------------------------------------------- > > Key: JBMESSAGING-431 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-431 > Project: JBoss Messaging > Issue Type: Task > Affects Versions: 1.0.1.CR4 > Reporter: Tim Fox > Assigned To: Ron Sigal > Fix For: 1.2.0.Alpha1 > > > Currently, for the socket and ssl transports, callbackservers will be opened on the next available port obtained. > Very occasionally this can fail since some other service uses the port before the callback server can. > Instead, the user should be able to configure a port used by the callbackserver to listen. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-406) Enable file based persistent stores

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-406?page=all ] Ovidiu Feodorov updated JBMESSAGING-406: ---------------------------------------- Fix Version/s: 1.2.1 > Enable file based persistent stores > ----------------------------------- > > Key: JBMESSAGING-406 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-406 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.2.1 > > > Implement non shared file based persistent store. > Look at whether we can re-use stuff (ObjectStore) from JBoss Transactions to implement this. > Also look at HOWL. http://howl.objectweb.org/ -- 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

17 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2006