August 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-6836) org.jboss.test.xml.DynamicLoginConfigUnitTestCase.testJASPIConfig

by Dimitris Andreadis (JIRA)

org.jboss.test.xml.DynamicLoginConfigUnitTestCase.testJASPIConfig ----------------------------------------------------------------- Key: JBAS-6836 URL: https://jira.jboss.org/jira/browse/JBAS-6836 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Assignee: Anil Saldhana Priority: Critical Fix For: JBossAS-5.1.0.GA This one is failing with the jbossxb upgrade: http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.1.x-test... Either testsuite/main/resources/xml/logingconfig/jaspi-config.xml needs fixing or the corresponding security-config_5_0.xsd (which BTW I don't see it included in docs/schemas?) -- 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

16 years, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1570) Why does QueueImpl::changeMessagePriority delete the ref?

by Tim Fox (JIRA)

Why does QueueImpl::changeMessagePriority delete the ref? --------------------------------------------------------- Key: JBMESSAGING-1570 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1570 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assignee: Jeff Mesnil Fix For: 2.0.0 Beta QueueImpl::changeMessagePriority seems to delete the old ref from storage then only add the new one in memory! -- 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

16 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1526) Improve timeout when closing consumer

by Tim Fox (JIRA)

Improve timeout when closing consumer ------------------------------------- Key: JBMESSAGING-1526 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1526 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assignee: Tim Fox Fix For: 2.0.0.CR1 Currently if there are a lot of messages in a client consumer buffer and they are being consumed by a slow consumrt, then on close, it will timeout since it will wait for all messages to be consumed. Need to improve this so it only waits for the current one to complete. -- 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

16 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1572) Sent to DLQ if routeFromCluster fails

by Tim Fox (JIRA)

Sent to DLQ if routeFromCluster fails ------------------------------------- Key: JBMESSAGING-1572 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1572 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assignee: Tim Fox Fix For: 2.0.0.CR1 If routeFromCluster fails e.g. if queue has been deleted after sending on source, then message should go to DLQ not be deleted. -- 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

16 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1565) Need to check permissions on create producer for JMS

by Tim Fox (JIRA)

Need to check permissions on create producer for JMS ---------------------------------------------------- Key: JBMESSAGING-1565 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1565 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assignee: Tim Fox Fix For: 2.0.0.CR1 For JMS, we need to check permissions when creating a JMS message producer. However if we do this in JBossSession (currently commented out), then sending management messages to JMS fails since there is no actual management queue. The code in JBossSession is temporarily commented out until this is resolved. -- 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

16 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1588) Add netty bridge tests

by Tim Fox (JIRA)

Add netty bridge tests ---------------------- Key: JBMESSAGING-1588 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1588 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assignee: Tim Fox Fix For: 2.0.0.CR1 -- 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

16 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1528) Re-enable producer flow control when adress is full

by Tim Fox (JIRA)

Re-enable producer flow control when adress is full --------------------------------------------------- Key: JBMESSAGING-1528 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1528 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assignee: Tim Fox Fix For: 2.0.0 Beta This can be done by holding back packet confirmations until more space frees up. -- 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

16 years, 11 months

2
3
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-390) ConnectionFactory and JBossDestination should be Referenceable

by Tim Fox (JIRA)

[ https://jira.jboss.org/jira/browse/JBMESSAGING-390?page=com.atlassian.jir... ] Tim Fox updated JBMESSAGING-390: -------------------------------- Fix Version/s: 2.0.0 (was: 2.0.0.beta5) > ConnectionFactory and JBossDestination should be Referenceable > -------------------------------------------------------------- > > Key: JBMESSAGING-390 > URL: https://jira.jboss.org/jira/browse/JBMESSAGING-390 > Project: JBoss Messaging > Issue Type: Bug > Reporter: Tim Fox > Assignee: Tim Fox > Fix For: 2.0.0 > > > as per spec 4.2 -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1584) Client side load balancing integration tests

by Tim Fox (JIRA)

Client side load balancing integration tests -------------------------------------------- Key: JBMESSAGING-1584 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1584 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assignee: Tim Fox Fix For: 2.0.0 Beta We need tests for this, that test different policies etc. -- 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

16 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1557) Race condition in JMS Bridge between enlisting the XAResource in the TX and message delivery

by Jeff Mesnil (JIRA)

Race condition in JMS Bridge between enlisting the XAResource in the TX and message delivery -------------------------------------------------------------------------------------------- Key: JBMESSAGING-1557 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1557 Project: JBoss Messaging Issue Type: Bug Reporter: Jeff Mesnil Assignee: Tim Fox Fix For: 2.0.0 Beta The JMS Bridge code is enlisting the XAResource in the JTA Transaction in a way that can occur concurrently with delivery. more info: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=151340&start=10 -- 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

16 years, 11 months

3
3
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 August 2009