March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-312) De-monolithise persistencemanager

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-312?page=all ] Ovidiu Feodorov updated JBMESSAGING-312: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > De-monolithise persistencemanager > --------------------------------- > > Key: JBMESSAGING-312 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-312 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: Unscheduled > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Refactor PersistenceManager to make less monolithic. > The PersistenceManager should really only deal with simple persistence operations, e..g. addReference, removeReference, addMessage, removeMessage etc. This makes it easy to re-implement for another type of store. > Currently the PM contains logic that belongs elsewhere e.g. in the ChannelState. > The TransactionCallback should be removed to it's own java file. > The locking operations should occur in the caller. > There should be an abstraction PMTxContext which can be passed into PM operations to group them. > This should dramatically clarify and simplify things -- 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 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-384) Modify jboss-head build script to include Messaging instead of JBossMQ in the "all" configuration

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-384?page=all ] Ovidiu Feodorov updated JBMESSAGING-384: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Modify jboss-head build script to include Messaging instead of JBossMQ in the "all" configuration > ------------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-384 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-384 > Project: JBoss Messaging > Issue Type: Sub-task > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Fix For: Unscheduled > > > Make sure JBossMQ still works as an alternate JMS provider -- 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 month

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: Unscheduled (was: 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: Unscheduled > > > 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

19 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-315) Consider abstracting out "generic" jms facade features

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-315?page=all ] Ovidiu Feodorov updated JBMESSAGING-315: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Consider abstracting out "generic" jms facade features > ------------------------------------------------------ > > Key: JBMESSAGING-315 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-315 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Fix For: Unscheduled > > > The JMS facade contains certain architectural constructs and features that are likely to be useful for generic messaging, not just JMS. > E.g. the client and server side AOP stacks, storing transactional state on client side, message consumer are all things that are probably useful for use in other messaging applications. > We should consider abstracting these out so they can be used outside the jms facade. -- 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 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-254) Remove ThreadContextClassLoaderChanger

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-254?page=all ] Ovidiu Feodorov updated JBMESSAGING-254: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.2.1) > Remove ThreadContextClassLoaderChanger > -------------------------------------- > > Key: JBMESSAGING-254 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-254 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Ovidiu Feodorov > Priority: Critical > Fix For: Unscheduled > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Kabir has fixed this in AOP so this is no longer necessary. -- 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 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-287) RemotingTest.testConnectionListener() invalid

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-287?page=all ] Ovidiu Feodorov updated JBMESSAGING-287: ---------------------------------------- Fix Version/s: Unscheduled (was: 1.0.3.CR1) > RemotingTest.testConnectionListener() invalid > --------------------------------------------- > > Key: JBMESSAGING-287 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-287 > Project: JBoss Messaging > Issue Type: Bug > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: Unscheduled > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > I commented out that test because I wanted a clean test run for the release and also because I think the test is invalid. > After the client connects I assume there is a separate thread that renews the lease on server, so even if the main thread sleeps for 5 secs, the client renews its lease and the ConnectionListener doesn't get called. Please verify my assumption and either fix the test or remove 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, 1 month

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: Unscheduled (was: 1.0.2.CR1) > XARecovery integration of JBossMessaging with JBossTS > ----------------------------------------------------- > > Key: JBMESSAGING-407 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-407 > Project: JBoss Messaging > Issue Type: Feature Request > Components: Tests and Performance > Environment: JBoss 4.0.3SP1, JBossTs 4.2GA, JBOSS Messagig 1.0.1CR2 > Reporter: Madhusudhan Konda > Priority: Blocker > Fix For: Unscheduled > > Attachments: artifacts.zip, jms-recovery-patch-all.txt, jms.zip, JMSProviderXAResourceRecovery.java, xa.zip, xarecovery-patch.txt, XATestStandaloneRecovery.java > > Original Estimate: 1 week > Time Spent: 1 week, 4 hours, 30 minutes > Remaining Estimate: 0 minutes > > 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

19 years, 1 month

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-619) outofmemory during ant test suite run

by David Lloyd (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-619?page=all ] David Lloyd resolved JBPM-619. ------------------------------ Resolution: Cannot Reproduce Bug In Linux, using: java version "1.5.0_10" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03) Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode) It works fine for me: $ CLASSPATH=~/local/jdk/repository/junit/3.8.1/lib/junit.jar ant test.report Buildfile: build.xml test.report: [junitreport] Transform time: 7990ms BUILD SUCCESSFUL Total time: 14 seconds > outofmemory during ant test suite run > ------------------------------------- > > Key: JBPM-619 > URL: http://jira.jboss.com/jira/browse/JBPM-619 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM jPDL 3.2 > Reporter: Jim Rigsbee > Assigned To: David Lloyd > Fix For: jBPM jPDL 3.2 > > > MailTests will fail if your local workstation is not setup correctly. These tests are failing in the cruise control build as well. -- 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 month

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3661) LdapExtLoginModule should detect communication failures midstream

by Anil Saldhana (JIRA)

LdapExtLoginModule should detect communication failures midstream ----------------------------------------------------------------- Key: JBAS-3661 URL: http://jira.jboss.com/jira/browse/JBAS-3661 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-4.0.4.GA Reporter: Anil Saldhana Assigned To: Scott M Stark There is a possibility of the context going stale due to communication exceptions with the ldap server when dealing with references etc. It may be useful for the LdapExtLoginModule to implement the: http://java.sun.com/j2se/1.3/docs/api/javax/naming/ldap/UnsolicitedNotifi... such that it can do graceful processing. -- 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 month

3
3
0 / 0

[JBoss JIRA] Created: (JBAOP-374) AspectDefinition is keeping a reference to EJBContainer after undeployment

by Carlo de Wolf (JIRA)

AspectDefinition is keeping a reference to EJBContainer after undeployment -------------------------------------------------------------------------- Key: JBAOP-374 URL: http://jira.jboss.com/jira/browse/JBAOP-374 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.alpha3 Environment: trunk Reporter: Carlo de Wolf Priority: Blocker Static reference from org.jboss.aop.AspectManager.manager (from class org.jboss.aop.AspectManager) : --> org.jboss.aop.AspectManager@0x50007cce (144 bytes) (field aspectDefinitions:) --> EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap@0x50007d4f (52 bytes) (field table:) --> EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap$Entry[]@0x501127a2 (252 bytes) (Element 1 of EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap$Entry[]@0x501127a2:) --> EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap$Entry@0x501129a7 (24 bytes) (field value:) --> org.jboss.aop.advice.AspectDefinition@0x501129a2 (25 bytes) (field advisors:) --> EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap@0x501129a3 (52 bytes) (field lastWrite:) --> EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap$Entry@0x5015945a (24 bytes) (field key:) --> org.jboss.ejb3.stateful.StatefulContainer@0x5012f6a6 (230 bytes) -- 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 month

2
6
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