April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-91) Administrative destinations

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-91?page=all ] Tim Fox updated JBMESSAGING-91: ------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > Administrative destinations > --------------------------- > > Key: JBMESSAGING-91 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-91 > Project: JBoss Messaging > Issue Type: Feature Request > Components: JMS Facade > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: 2.0.0 Beta 1 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Implement special destinations to allow administration over the jms protocol itself. e.g. You can send a request/response message to the "AdminQueue" that says create me a destination or change my password, etc. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (GPD-52) Enhanced configuration of actor-ids and pooled-actors

by Koen Aers (JIRA)

Enhanced configuration of actor-ids and pooled-actors ----------------------------------------------------- Key: GPD-52 URL: http://jira.jboss.com/jira/browse/GPD-52 Project: JBoss jBPM GPD Issue Type: Feature Request Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.alpha3 Two extra input fields will be provided in the Graphical Process Designer for actor-ids="..." and pooled-actors="...". No code completion will be provided on the assignment expression. The drop down lists will be populated from configuration values in the Eclipse preferences (without connection to the Infor identify component). -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-220) Add the possibility to drop a destination.

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-220?page=all ] Tim Fox closed JBMESSAGING-220. ------------------------------- Resolution: Out of Date Already implemented > Add the possibility to drop a destination. > ------------------------------------------ > > Key: JBMESSAGING-220 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-220 > Project: JBoss Messaging > Issue Type: Feature Request > Components: JMS Destination Manager > Reporter: Ovidiu Feodorov > Priority: Minor > Fix For: Unscheduled > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Add the possiblity to administratively (and possibly programmatically) drop a destination. > Dropping a destination means that all persistent messages maintained by the destination are discarded. This is not what happens during the current deployment/undeployment of a destiantion, which currently have an activation/de-activation semantics. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-138) Adapt performance test harness to be automated by JRUnit

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-138?page=all ] Tim Fox closed JBMESSAGING-138. ------------------------------- Resolution: Won't Fix > Adapt performance test harness to be automated by JRUnit > -------------------------------------------------------- > > Key: JBMESSAGING-138 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-138 > Project: JBoss Messaging > Issue Type: Task > Components: Tests and Performance > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Minor > Fix For: Unscheduled > > > Adapt jms perf testing framework with a JRUnit wrapper so it can automated as part of QA run, and data can be output to perf data database -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-259) Activate compression in marshaller

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-259?page=all ] Tim Fox updated JBMESSAGING-259: -------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > Activate compression in marshaller > ---------------------------------- > > Key: JBMESSAGING-259 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-259 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Priority: Minor > Fix For: 2.0.0 Beta 1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Activate compression in marshaller for messages > x bytes. Make it configurable -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-605) Open connections should not prevent jvm from exiting

by Tim Fox (JIRA)

Open connections should not prevent jvm from exiting ---------------------------------------------------- Key: JBMESSAGING-605 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-605 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.0.1.CR5 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.Beta1 If the client process attempts to exit without explicitly closing connections then it can cause the process to hang. We should explicity close any open connections on jvm exit (install a shutdown hook to handle this) and log warnings (to system.err) so the programming error can be corrected. -- 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, 3 months

5
9
0 / 0

[JBoss JIRA] Created: (GPD-30) add support for descriptions on most elements

by Koen Aers (JIRA)

add support for descriptions on most elements ---------------------------------------------- Key: GPD-30 URL: http://jira.jboss.com/jira/browse/GPD-30 Project: JBoss jBPM GPD Issue Type: Task Affects Versions: jBPM JPDL Designer 3.1.0 alpha1 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.alpha3 -- 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, 3 months

2
3
0 / 0

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

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-390?page=all ] Tim Fox updated JBMESSAGING-390: -------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > ConnectionFactory and Destination should be Referenceable > --------------------------------------------------------- > > Key: JBMESSAGING-390 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-390 > Project: JBoss Messaging > Issue Type: Bug > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 2.0.0 Beta 1 > > > as per spec 4.2 -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-26) Standalone Messaging configuration.

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-26?page=all ] Tim Fox updated JBMESSAGING-26: ------------------------------- Fix Version/s: 2.0.0 Beta 1 (was: Unscheduled) > Standalone Messaging configuration. > ----------------------------------- > > Key: JBMESSAGING-26 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-26 > Project: JBoss Messaging > Issue Type: Task > Components: AS Integration > Reporter: Ovidiu Feodorov > Assigned To: Alex Pinkin > Fix For: 2.0.0 Beta 1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Prepare a stripped-down JBoss configuration that will be the "stand-alone" JBoss Messaging server. > Must have at least the JNDI server, Logging, Remoting and AOP support. > We should provide a pre-packaged downloadable "standalone" config - users don't want to have to download and install the AS just so they can create a standalone installation. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-388) Write a JBossMQ to Messaging migration guide

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-388?page=all ] Tim Fox updated JBMESSAGING-388: -------------------------------- Fix Version/s: Miscellaneous (was: Unscheduled) > Write a JBossMQ to Messaging migration guide > -------------------------------------------- > > Key: JBMESSAGING-388 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-388 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Documentation and Training > Reporter: Ovidiu Feodorov > Fix For: Miscellaneous > > -- 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, 3 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