April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6828) Cannot add empty messaging subsystem using CLI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6828?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6828: ---------------------------------------------- Radim Hatlapatka <rhatlapa(a)redhat.com> made a comment on [bug 947779|https://bugzilla.redhat.com/show_bug.cgi?id=947779] Verified in EAP 6.1.0.ER5 > Cannot add empty messaging subsystem using CLI > ---------------------------------------------- > > Key: AS7-6828 > URL: https://issues.jboss.org/browse/AS7-6828 > Project: Application Server 7 > Issue Type: Bug > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > It's not possible to add empty messaging subsystem using CLI: > [standalone@localhost:9999 /] /subsystem=messaging/hornetq-server=backup:add() > { > "outcome" => "failed", > "failure-description" => "JBAS011679: No connectors definition present.", > "rolled-back" => true > } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6828) Cannot add empty messaging subsystem using CLI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6828?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6828: ---------------------------------------------- Radim Hatlapatka <rhatlapa(a)redhat.com> changed the Status of [bug 947779|https://bugzilla.redhat.com/show_bug.cgi?id=947779] from ON_QA to VERIFIED > Cannot add empty messaging subsystem using CLI > ---------------------------------------------- > > Key: AS7-6828 > URL: https://issues.jboss.org/browse/AS7-6828 > Project: Application Server 7 > Issue Type: Bug > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > It's not possible to add empty messaging subsystem using CLI: > [standalone@localhost:9999 /] /subsystem=messaging/hornetq-server=backup:add() > { > "outcome" => "failed", > "failure-description" => "JBAS011679: No connectors definition present.", > "rolled-back" => true > } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6371) Clearing server environment in bootstrap breaks embedded server restart

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-6371?page=com.atlassian.jira.plugin.s... ] Thomas Diesler commented on AS7-6371: ------------------------------------- If the test suite passes it works for me > Clearing server environment in bootstrap breaks embedded server restart > ----------------------------------------------------------------------- > > Key: AS7-6371 > URL: https://issues.jboss.org/browse/AS7-6371 > Project: Application Server 7 > Issue Type: Bug > Components: Server > Reporter: Thomas Diesler > Assignee: Bartosz Baranowski > Fix For: 8.0.0.Alpha1 > > > Recursively deleting tmp directories as part of Bootstrap.bootstrap() prevents multiple embedded server restarts. I believe it has to do with how directories are crated as part of static VFS initialisation. > TempFileProvider has this static code > {code} > static { > String configTmpDir = System.getProperty(JBOSS_TMP_DIR_PROPERTY); > if (configTmpDir == null) > configTmpDir = System.getProperty(JVM_TMP_DIR_PROPERTY); > try { > TMP_ROOT = new File(configTmpDir, "vfs"); > TMP_ROOT.mkdirs(); > } > catch (Exception e) { > throw new RuntimeException("Can't set up temp file provider", e); > } > } > {code} > which creates the vfs directory only once that [this patch|https://github.com/jbossas/jboss-as/commit/ad3e878098] removes. As a consequence on server restart with jboss-vfs on the boot classpath hte vfs directory is missing an no tmp file can be created. > Generally, the server should only remove state on shutdown that it creates itself on startup/run. Alternatively, jboss-vfs should support a start/stop lifecycle in the TempFileProvider and possibly in other entities that also use static initialisers. > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6939) Remove direct connections parameter

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6939?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6939: ---------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 908720|https://bugzilla.redhat.com/show_bug.cgi?id=908720] from ASSIGNED to POST > Remove direct connections parameter > ----------------------------------- > > Key: AS7-6939 > URL: https://issues.jboss.org/browse/AS7-6939 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Affects Versions: 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > The direct connection parameter makes no sense. Currently console allows to create cluster connection only with broadcast group( which, if present, renders direct connection mute) > One could define cluster connection like that(to have static connectors), but from console POV, there is no way to tell the difference. Hence this parameter makes no sense. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6939) Remove direct connections parameter

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6939?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6939: ---------------------------------------------- baranowb <bbaranow(a)redhat.com> made a comment on [bug 908720|https://bugzilla.redhat.com/show_bug.cgi?id=908720] https://issues.jboss.org/browse/AS7-6939 https://github.com/hal/core/pull/4 > Remove direct connections parameter > ----------------------------------- > > Key: AS7-6939 > URL: https://issues.jboss.org/browse/AS7-6939 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Affects Versions: 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > The direct connection parameter makes no sense. Currently console allows to create cluster connection only with broadcast group( which, if present, renders direct connection mute) > One could define cluster connection like that(to have static connectors), but from console POV, there is no way to tell the difference. Hence this parameter makes no sense. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1622) Add a commandline troubleshooting tool

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1622?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1622: -------------------------------- It already exists: Chat. Can you resolve this JIRA ? > Add a commandline troubleshooting tool > -------------------------------------- > > Key: JGRP-1622 > URL: https://issues.jboss.org/browse/JGRP-1622 > Project: JGroups > Issue Type: Feature Request > Reporter: Ray Tsang > Assignee: Bela Ban > > There is currently a troubleshooting tool called "draw" documented here: http://www.jgroups.org/tutorial-3.x/html/ch01.html#d0e130 > In many troubleshooting scenarios, however, command line only troubleshooting tool would be much easier to use (since a lot of troubleshooting occurs in a remote server anyways). > Proposing to create a commandline only tool that can probably simply echo what gets typed between nodes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6940) Add support for static connectors

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/AS7-6940?page=com.atlassian.jira.plugin.s... ] Bartosz Baranowski reassigned AS7-6940: --------------------------------------- Assignee: Bartosz Baranowski (was: Harald Pehl) > Add support for static connectors > --------------------------------- > > Key: AS7-6940 > URL: https://issues.jboss.org/browse/AS7-6940 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > There is no way to declare cluster connection in messaging subsystem as "static" > http://docs.jboss.org/hornetq/2.3.0.CR2/docs/user-manual/html_single/inde... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6940) Add support for static connectors

by Bartosz Baranowski (JIRA)

Bartosz Baranowski created AS7-6940: --------------------------------------- Summary: Add support for static connectors Key: AS7-6940 URL: https://issues.jboss.org/browse/AS7-6940 Project: Application Server 7 Issue Type: Feature Request Components: Console Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) Reporter: Bartosz Baranowski Assignee: Harald Pehl Priority: Minor Fix For: 8.0.0.Alpha1 There is no way to declare cluster connection in messaging subsystem as "static" http://docs.jboss.org/hornetq/2.3.0.CR2/docs/user-manual/html_single/inde... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6939) Remove direct connections parameter

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/AS7-6939?page=com.atlassian.jira.plugin.s... ] Bartosz Baranowski reassigned AS7-6939: --------------------------------------- Assignee: Bartosz Baranowski > Remove direct connections parameter > ----------------------------------- > > Key: AS7-6939 > URL: https://issues.jboss.org/browse/AS7-6939 > Project: Application Server 7 > Issue Type: Feature Request > Affects Versions: 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > The direct connection parameter makes no sense. Currently console allows to create cluster connection only with broadcast group( which, if present, renders direct connection mute) > One could define cluster connection like that(to have static connectors), but from console POV, there is no way to tell the difference. Hence this parameter makes no sense. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6939) Remove direct connections parameter

by Harald Pehl (JIRA)

[ https://issues.jboss.org/browse/AS7-6939?page=com.atlassian.jira.plugin.s... ] Harald Pehl updated AS7-6939: ----------------------------- Component/s: Console > Remove direct connections parameter > ----------------------------------- > > Key: AS7-6939 > URL: https://issues.jboss.org/browse/AS7-6939 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Affects Versions: 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Minor > Fix For: 8.0.0.Alpha1 > > > The direct connection parameter makes no sense. Currently console allows to create cluster connection only with broadcast group( which, if present, renders direct connection mute) > One could define cluster connection like that(to have static connectors), but from console POV, there is no way to tell the difference. Hence this parameter makes no sense. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 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 2013