December 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-2465) Display gadget user preference using checkboxes for BOOL attributes

by Magesh Kumar B (JIRA)

Display gadget user preference using checkboxes for BOOL attributes ------------------------------------------------------------------- Key: JBPORTAL-2465 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2465 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Widget Affects Versions: 2.7.2 Final Reporter: Magesh Kumar B Assignee: Magesh Kumar B Fix For: 2.8 Final Currently BOOL attributes are displayed as text boxes. It would be nice to display them as check boxes as Google gadgets are displayed so. -- 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

15 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1774) maxDeliveryAttempts for MessageSucker shouldn't be -1, resulting message loss

by Howard Gao (JIRA)

maxDeliveryAttempts for MessageSucker shouldn't be -1, resulting message loss ----------------------------------------------------------------------------- Key: JBMESSAGING-1774 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1774 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.6.GA, 1.4.5.GA, 1.4.0.SP3.CP09 Reporter: Howard Gao Assignee: Howard Gao Fix For: 1.4.0.SP3.CP10, 1.4.6.GA.SP1, 1.4.7.GA When a MessageSucker is created, its consumer's maxDeliveryAttempts is set to -1. This will cause possible message loss in the following scenario: 1. in a 2-node cluster, messages are sent to distributed destination on node 1 but are consumed on node 0. Message sucker sucks messages from node 1 and sends to node 0. 2. During the process, node0 shut down normally. Then if there are some prefetched messages still in message sucker, they will be cancelled back to node1. 3. Because the maxDeliveryAttempts is -1, the messages cancelled will be instantly put to DLQ or, if there is no DLQ configured, be discarded. >From user's perspective, the message shouldn't be discarded this way. To fix this: Set the maxDeliveryAttempts to 1. -- 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

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1773) Fix intermittent test failures in DestinationRedeployTest

by Howard Gao (JIRA)

Fix intermittent test failures in DestinationRedeployTest --------------------------------------------------------- Key: JBMESSAGING-1773 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1773 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.4.6.GA, 1.4.5.GA, 1.4.0.SP3.CP09 Reporter: Howard Gao Assignee: Howard Gao Fix For: 1.4.0.SP3.CP10, 1.4.6.GA.SP1, 1.4.7.GA The test testRedeployTopicNoMessageLoss2() fails intermittently. The failure relates to some missing messages (they goes to DLQ) before the test retrieves them. For similar reason probably there may be other tests in this test class with this issue. -- 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

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2361) ServiceManager Mobility, Proxy and Hybrid

by Mark Proctor (JIRA)

ServiceManager Mobility, Proxy and Hybrid ----------------------------------------- Key: JBRULES-2361 URL: https://jira.jboss.org/jira/browse/JBRULES-2361 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: All Reporter: Mark Proctor Assignee: Mauricio Salatino Machines A B C ServiceManager (sm1) is deployed physically on A. With ksessions k1, k2, k3. C gets a remote connection to sm1 and starts working on k1. ServiceManager (sm2) is deployed physically on B. Seamless movement k1 is moved physically from sm1 to sm2. C needs to be able to seamlessly keep working k1, unaware of the move. Seamless proxy B gets remote connection to k2 on A's SM1. B registers k2 in sm2. If C was to lookup sm2.k2 it would be talking via a proxy, via B to C. Hybrid C decides that it needs to move k1 locally for continued work. Currently it only has a remote sm1. k1 should stayed regestered on sm1, but once moved locally to C it would effectively proxy from A to C. If k1 is on C, have we made a "sm1" that is partially natively on A and partially natively on C? This is almost like a clustered sm.... -- 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

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7226) Upgrade to JSF2 Release Candidate

by Stan Silvert (JIRA)

Upgrade to JSF2 Release Candidate --------------------------------- Key: JBAS-7226 URL: https://jira.jboss.org/jira/browse/JBAS-7226 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JSF Reporter: Stan Silvert Assignee: Stan Silvert Fix For: JBossAS-6.0.0.Alpha1 -- 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

15 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-7184) Update JBossWS to 3.2.0.GA

by Richard Opalka (JIRA)

Update JBossWS to 3.2.0.GA -------------------------- Key: JBAS-7184 URL: https://jira.jboss.org/jira/browse/JBAS-7184 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Web Services Reporter: Richard Opalka Assignee: Richard Opalka Fix For: JBossAS-6.0.0.Alpha1 -- 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

15 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-6878) Update JPA to 1.0.0

by Carlo de Wolf (JIRA)

Update JPA to 1.0.0 ------------------- Key: JBAS-6878 URL: https://jira.jboss.org/jira/browse/JBAS-6878 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Reporter: Carlo de Wolf Assignee: Carlo de Wolf -- 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

15 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-6883) Upgrade EJB3 to 1.1.5

by jaikiran pai (JIRA)

Upgrade EJB3 to 1.1.5 --------------------- Key: JBAS-6883 URL: https://jira.jboss.org/jira/browse/JBAS-6883 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Reporter: jaikiran pai Assignee: jaikiran pai -- 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

15 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-7033) Upgrade to JBossXACML 2.0.3.SP2

by Anil Saldhana (JIRA)

Upgrade to JBossXACML 2.0.3.SP2 -------------------------------- Key: JBAS-7033 URL: https://jira.jboss.org/jira/browse/JBAS-7033 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Security Reporter: Anil Saldhana Assignee: Stefan Guilhen Fix For: JBossAS-5.2.0.Beta1, JBossAS-6.0.0.Alpha1 Upgrade to JBossXACML 2.0.3.SP2 Branch_5_x, trunk and the branch corresponding to EAP5 (find out what branch is that). Just update the component/pom.xml Run the ant tests-security-basic-unit test target and see if there are regressions. -- 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

15 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-6685) Update EJB 3 to 1.1.3

by Carlo de Wolf (JIRA)

Update EJB 3 to 1.1.3 --------------------- Key: JBAS-6685 URL: https://jira.jboss.org/jira/browse/JBAS-6685 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Reporter: Carlo de Wolf Assignee: jaikiran pai -- 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

15 years, 10 months

3
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2009