April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-348) Automate test run against all supported databases

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-348?page=all ] Tim Fox updated JBMESSAGING-348: -------------------------------- Fix Version/s: 1.2.1.CR1 (was: Unscheduled) > Automate test run against all supported databases > ------------------------------------------------- > > Key: JBMESSAGING-348 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-348 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Fix For: 1.2.1.CR1 > > > The test suite should be run continuously against all databases we supply a configuration for. > Initially this should be: > Oracle, MSSQL, MySQL, PostgreSQL, DB2, Sybase and Derby. -- 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
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-494) Add smoke test using ConnectionFactory

by Tim Fox (JIRA)

Add smoke test using ConnectionFactory -------------------------------------- Key: JBMESSAGING-494 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-494 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Fix For: 1.0.1.CR4 Need to add a smoke test that uses /ConnectionFactory as opposed to /JmsXA. This is because there was a classloader bug that only manifests when sending a message from an ejb to a topic using /Connectionfactory. Really, the smoke tests should be refactored to have a more appropriate use of connection factories. -- 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

4
3
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-381) Add param on destination to disable persistence

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-381?page=all ] Tim Fox updated JBMESSAGING-381: -------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > Add param on destination to disable persistence > ----------------------------------------------- > > Key: JBMESSAGING-381 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-381 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 2.0.0 Beta 1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > We should add a configuration param on destinations which id true prevents messages being persisted even if they are persistent. > This should give equivalent functionality to the JBossMQ NullPersistenceManager. > in some circumstances uses want to override persistence for messages but have no access to change the delivery mode at the sender. -- 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
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-352) @Consumer example

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-352?page=all ] Tim Fox updated JBMESSAGING-352: -------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) Priority: Minor (was: Major) > @Consumer example > ----------------- > > Key: JBMESSAGING-352 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-352 > Project: JBoss Messaging > Issue Type: Sub-task > Affects Versions: 1.0.0 > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: 2.0.0 Beta 1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Add a Consumer example, as described in http://docs.jboss.org/ejb3/app-server/tutorial/consumer/consumer.html -- 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
0
0 / 0

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

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-383?page=all ] Tim Fox updated JBMESSAGING-383: -------------------------------- Fix Version/s: 1.2.1.CR1 (was: Unscheduled) > Modify jboss-head build script to include Messaging instead of JBossMQ in the "default" configuration > ----------------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-383 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-383 > Project: JBoss Messaging > Issue Type: Sub-task > Components: AS Integration > Reporter: Ovidiu Feodorov > Priority: Critical > Fix For: 1.2.1.CR1 > > > 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-16) A PointToMultipoint should be able to do delivery on separate threads

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-16?page=all ] Tim Fox updated JBMESSAGING-16: ------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) Priority: Optional (was: Major) I am not convinced this would increase performance for most uses cases. I remain to be convinced - it is worth investigating though- although not major priority. > A PointToMultipoint should be able to do delivery on separate threads > --------------------------------------------------------------------- > > Key: JBMESSAGING-16 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-16 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Messaging Core > Affects Versions: 1.2.0.Alpha1 > Reporter: Ovidiu Feodorov > Priority: Optional > Fix For: 2.0.0 Beta 1 > > -- 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
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-789) Non causality when using Remoting socket transport and one way invocations

by Tim Fox (JIRA)

Non causality when using Remoting socket transport and one way invocations -------------------------------------------------------------------------- Key: JBMESSAGING-789 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-789 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.Beta1 Reporter: Tim Fox Priority: Critical Fix For: 1.2.0.CR1 The remoting socket transport uses an underlying pool of tcp connections, and subsequent invocations get a connection from the pool, use it and return it from the pool. This means that subsequent invocations can use a different underlying TCP connection, and later invocations can overtake earlier ones depending on how the OS schedules the read threads listening on the connections. Temporary work around is to use a pool size of 1, or completely serialize all invocations per VM by encloing in the synchronized block. This gives us effectively one TCP connection per VM. A better approach would be for the remoting Client object to be pinned to the actual TCP connection one to one. I.e. we don't want or need the pool. It is just a big PITA for us. -- 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

4
8
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-25) Integrate ServerPeer with the 5.0 micro-container

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-25?page=all ] Tim Fox updated JBMESSAGING-25: ------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) Priority: Major (was: Critical) > Integrate ServerPeer with the 5.0 micro-container > ------------------------------------------------- > > Key: JBMESSAGING-25 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-25 > Project: JBoss Messaging > Issue Type: Task > Components: AS Integration > Reporter: Ovidiu Feodorov > Fix For: 2.0.0 Beta 1 > > Attachments: JBMESSAGING-26.tar > > Original Estimate: 1 week > Remaining Estimate: 1 week > > This is critical to kick start ESB -- 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
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-382) Make Messaging the default JMS provider for JBoss 5.0

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-382?page=all ] Tim Fox updated JBMESSAGING-382: -------------------------------- Fix Version/s: 1.2.1.CR1 (was: Unscheduled) Assignee: Clebert Suconic > Make Messaging the default JMS provider for JBoss 5.0 > ----------------------------------------------------- > > Key: JBMESSAGING-382 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-382 > Project: JBoss Messaging > Issue Type: Task > Components: AS Integration > Reporter: Ovidiu Feodorov > Assigned To: Clebert Suconic > Priority: Critical > Fix For: 1.2.1.CR1 > > Original Estimate: 1 week > Remaining Estimate: 1 week > -- 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
0
0 / 0

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

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-407?page=all ] Tim Fox updated JBMESSAGING-407: -------------------------------- Fix Version/s: 1.2.1.CR1 (was: Unscheduled) Assignee: Tim Fox > 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 > Assigned To: Tim Fox > Priority: Blocker > Fix For: 1.2.1.CR1 > > 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, 2 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 April 2007