November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMDR-53) Update to jboss-common-core 2.2.9.GA

by Ales Justin (JIRA)

Update to jboss-common-core 2.2.9.GA ------------------------------------ Key: JBMDR-53 URL: https://jira.jboss.org/jira/browse/JBMDR-53 Project: JBoss MetaData Repository Issue Type: Thirdparty Change Components: Release Affects Versions: JBossMDR.2.0.0.GA Reporter: Ales Justin Assignee: Ales Justin Priority: Minor Fix For: JBossMDR-2.0.1.GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBVFS-63) Release JBoss VFS 2.0.0.CR2

by Ales Justin (JIRA)

Release JBoss VFS 2.0.0.CR2 --------------------------- Key: JBVFS-63 URL: https://jira.jboss.org/jira/browse/JBVFS-63 Project: JBoss VFS Issue Type: Release Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR1 Reporter: Ales Justin Assignee: Ales Justin Fix For: 2.0.0.CR2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1151) Guarantee ordering with a delayed redelivery (FIFO)

by Markus Lutum (JIRA)

Guarantee ordering with a delayed redelivery (FIFO) --------------------------------------------------- Key: JBMESSAGING-1151 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1151 Project: JBoss Messaging Issue Type: Feature Request Affects Versions: 1.4.0.GA Reporter: Markus Lutum Assigned To: Tim Fox Make it possible to configure JBM to guarantee ordering with a delayed redelivery means preserve ordering of messages to a Consumer also in case of NACK / rollback. In other words, block any other messages that arrived in the intervening period being delivered. Needed behaviour A and B are in the Queue delivered A (ok) delivered B (NOK/Transaction roll back) C comes in delivered B again after 20 sec (NOK/Transaction roll back) delivered B again after 20 sec (Now processing is OK- Commit) delivered C I have now 2 customers which need this behaviour so I can replace a buggy self written persistent queue package. -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1426) Improve browsing implementation

by Tim Fox (JIRA)

Improve browsing implementation ------------------------------- Key: JBMESSAGING-1426 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1426 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assignee: Tim Fox Fix For: 2.0.0 Beta The current browsing implementation takes a snapshot of the queue which is sub-optimal. Should be reworked - also need ot rethink how browsed messages get back to client - using a remote enumeration approach is clunky. We can probably reuse the consumer functionality - a special consumer which doesn't actually remove the messages from the queue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1328) Unnecessary journal logging on rollback

by Tim Fox (JIRA)

Unnecessary journal logging on rollback --------------------------------------- Key: JBMESSAGING-1328 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1328 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta When cancelling messages we cureently ack them in a tx, then rollback - this creates unnecessary loggingin in journal. Instead acks should be handled differently to cancels in tx -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1203) Align component dependencies with AS 5.0.0.CR1

by Carlo de Wolf (JIRA)

Align component dependencies with AS 5.0.0.CR1 ---------------------------------------------- Key: EJBTHREE-1203 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1203 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Priority: Critical Fix For: AS 5.0.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

17 years, 6 months

2
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1292) Producer flow control

by Tim Fox (JIRA)

Producer flow control --------------------- Key: JBMESSAGING-1292 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1292 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Implement producer flow control to prevent servers being over-run with messages from clients. Two different types of producer flow control should be implemented: 1) Rate based flow control - where a maximum send rate in bytes/sec or messages/sec can be specified. 2) Token based flow control - where producers can only send messages along as it has tokens to avoid exceeding a queues maximum size. -- 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, 6 months

1
7
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1631) Allow different stylesheets for different user-agents

by Thomas Heute (JIRA)

Allow different stylesheets for different user-agents ----------------------------------------------------- Key: JBPORTAL-1631 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1631 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Theme Reporter: Thomas Heute Assigned To: Julien Viet Fix For: 2.8 Final It should be possible to define several stylesheets for a theme that would be applied for different user-agents. Several stylesheets can be handy to respect the differences between IE versions and also with other browsers. -- 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, 6 months

2
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1356) Add thread pool for client/server sessions

by Jay Howell (JIRA)

Add thread pool for client/server sessions ------------------------------------------ Key: JBMESSAGING-1356 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1356 Project: JBoss Messaging Issue Type: Feature Request Components: Messaging Core Affects Versions: 1.4.0.SP3.CP02 Reporter: Jay Howell Assigned To: Tim Fox The threads named jbm-server-session* and jbm-client-session* should be gotten from a thread pool instead of just being created. There's no way to cap the number of session threads. The thread factory is defined in NamedThreadQueuedExecutor as... private class Factory implements ThreadFactory { public Thread newThread(Runnable command) { return new Thread(jbmGroup, command, name); } } This thread factory should really have a thread pool implementation and not just a new thread implementation. This class controls both the server threads and the client threads. -- 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, 6 months

4
15
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1544) Create an EJB3 / AS Integration Project

by Andrew Lee Rubinger (JIRA)

Create an EJB3 / AS Integration Project --------------------------------------- Key: EJBTHREE-1544 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1544 Project: EJB 3.0 Issue Type: Task Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 1.0.0-CR1 Integration project for AS should be the sole imported component, and defines all AS configurations and transitive dependencies. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 6 months

1
1
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 November 2008