September 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (AS7-1821) CLONE - Web Management Interface does not show existing queues, topics and connection factories

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/AS7-1821?page=com.atlassian.jira.plugin.s... ] Heiko Braun commented on AS7-1821: ---------------------------------- I assume we talk about this branch: git://git.app.eng.bos.redhat.com/jbossas/jboss-as.git prod-7.0.1.Final right? > CLONE - Web Management Interface does not show existing queues, topics and connection factories > ----------------------------------------------------------------------------------------------- > > Key: AS7-1821 > URL: https://issues.jboss.org/browse/AS7-1821 > Project: Application Server 7 > Issue Type: Bug > Components: Console > Affects Versions: 7.0.1.Final > Reporter: Miroslav Novak > Assignee: Heiko Braun > Fix For: 7.1.0.CR1 > > Attachments: as-1871.png, domain.xml > > > Web Management Interface does not show existing queues, topics and connection factories in http://localhost:9990/console/App.html#domain/profile/messaging. Could it be fixed please? > Thank you, > Mirek -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-1360) getXXXAddress() protocol methods are annoying

by Paul Ferraro (JIRA)

getXXXAddress() protocol methods are annoying --------------------------------------------- Key: JGRP-1360 URL: https://issues.jboss.org/browse/JGRP-1360 Project: JGroups Issue Type: Enhancement Affects Versions: 2.12.1 Reporter: Paul Ferraro Assignee: Bela Ban Priority: Minor This one has been bothering me for a while. Typically, when an object exposes JavaBean-style methods such as getBindAddress() and setBindAddress(String), one expects a certain level of idempotency. For example: TP transport; String address = "127.0.0.1"; transport.setBindAddress(address); Assert.assertEquals(address, transport.getBindAddress()); However, the assertion fails, because getBindAddress() returns the toString() of the InetAddress composed during setBindAddress(). InetAddress.toString() returns a combination of the host name, and a resolved host address. Therefore, "127.0.0.1" != "/127.0.0.1" More annoying, however, is the inability to do transport.setBindAddress(transport.getBindAddress()), since the result of getBindAddress() is not a valid address as expected by setBindAddress(String). It would be great if all the getXXXAddress() methods returned the result of InetAddress.getHostAddress(). 3.0 is a perfect opportunity to make this kind of change. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
4
0 / 0

[JBoss JIRA] Updated: (AS7-1817) CLONE - Web Management Interface has selector(filter) attribute for creating queue mandatory - should be optional

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/AS7-1817?page=com.atlassian.jira.plugin.s... ] Radoslav Husar updated AS7-1817: -------------------------------- Component/s: Console > CLONE - Web Management Interface has selector(filter) attribute for creating queue mandatory - should be optional > ------------------------------------------------------------------------------------------------------------------ > > Key: AS7-1817 > URL: https://issues.jboss.org/browse/AS7-1817 > Project: Application Server 7 > Issue Type: Bug > Components: Console > Affects Versions: 7.0.1.Final > Reporter: Miroslav Novak > Assignee: Mike Brock > Fix For: 7.1.0.CR1 > > > Creating queue using Web Management Interface requires "selector" attribute. This attribute should be optional. When this field will be left empty then no filter (means store all messages to queue) should be set. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBBUILD-692) The JBoss parent pom should not have any maven profiles

by Geoffrey De Smet (JIRA)

The JBoss parent pom should not have any maven profiles ------------------------------------------------------- Key: JBBUILD-692 URL: https://issues.jboss.org/browse/JBBUILD-692 Project: JBoss Build System Issue Type: Enhancement Components: JBoss Parent POM Affects Versions: JBoss Parent POM - 6 Reporter: Geoffrey De Smet Assignee: Paul Gier This might be a controversial change, but before dismissing this issue, please listen to my experience with profiles: The current profiles in the pom can be removed: - enforce: Instead of doing -Dskip-enforce use -Denforcer.skip=true as documented here: http://maven.apache.org/plugins/maven-enforcer-plugin/enforce-mojo.html#skip - source: Instead of doing -Dskip-sources, create an issue on the maven-source-plugin to skip it there. I see no point in skipping this though as it's not slow. - release: Why is that configuration in a profile? They 'll definitely forget to activate that profile during release. (Especially since -Denforce does not work but -Penforce does, but the later disables the use of other profiles). Fix on the deploy-plugin (by activating updateReleaseInfo on non-SNAPSHOT) - dev-reports: Why does this need to be in a profile? A "mvn clean install" doesn't run them anyway. An everyone knows that a "mvn site" takes forever, so it's ok to add them there by default. Furthermore, the motivation behind this: - Profiles complicate the build, making it harder to understand what's happening. - In practice, contributors want 2 profiles: -- fast (the default, no profile): includes as much as possible (including enforcer and sources jars) but nothing that is slow (like building docbook docs or assemblies) -- full (-Dfull): include everything (docbook docs, javadocs, signing, assemblies, ...): if the output missing something, it's a bug, not a missing build option - Having more than these 2 profiles, confuses contributors and makes build maintance harder. - When importing a pom.xml in IntelliJ or m2eclipse, you get asked which profiles you want to activate. You'll want to check the "full" profile so you get the sources of the slow modules (docbook, assemblies) too. Having other profiles there just confuses the developers. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (AS7-1802) Invalid option error for --pc-address and --pc-port with domain.sh

by Rostislav Svoboda (JIRA)

Invalid option error for --pc-address and --pc-port with domain.sh ------------------------------------------------------------------ Key: AS7-1802 URL: https://issues.jboss.org/browse/AS7-1802 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.1.Final Reporter: Rostislav Svoboda Assignee: Brian Stansberry There is issue with resolving --pc-address and --pc-port options. Character '=' is not expected after these options. org.jboss.as.host.controller.Main contains } else if (CommandLineConstants.INTERPROCESS_PC_PORT.equals(arg)) { ... } else if (CommandLineConstants.INTERPROCESS_PC_ADDRESS.equals(arg)) { So when I specify '--pc-address 10.34.3.15' it continues to start AS7 properly. NOTE: there is typo in ProcessMessages (org.jboss.as.process) change '%n' to '\n' on line 41. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1803) Improve command line help text

by Brian Stansberry (JIRA)

Improve command line help text ------------------------------ Key: AS7-1803 URL: https://issues.jboss.org/browse/AS7-1803 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: 7.1.0.Alpha1 As discussed on the linked dev list thread. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1378) Make module directory configurable using .sh/.bat run scripts

by Rostislav Svoboda (JIRA)

Make module directory configurable using .sh/.bat run scripts ------------------------------------------------------------- Key: AS7-1378 URL: https://issues.jboss.org/browse/AS7-1378 Project: Application Server 7 Issue Type: Feature Request Reporter: Rostislav Svoboda Fix For: 7.1.0.Alpha1 Make module directory configurable using .sh/.bat run scripts, currently you can specify configuration location using '--server-config' or '--domain-config' + '--host-config' , location of modules directory should be configurable too. It's necessary to make changes on .bat/.sh files level to make module directory configurable. Currently it's hard-coded to use module directory under JBOSS_HOME directory {code} -mp \"$JBOSS_HOME/modules\" \ {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (AS7-1668) Usability: Lack of -b binding support in AS7 leads to confusion

by Michael Dobozy (JIRA)

Usability: Lack of -b binding support in AS7 leads to confusion --------------------------------------------------------------- Key: AS7-1668 URL: https://issues.jboss.org/browse/AS7-1668 Project: Application Server 7 Issue Type: Bug Reporter: Michael Dobozy The replacement for -b in AS7, from what I understand, is to edit standalone.xml and, under the public interface section, specify <any-address /> as the binding interface. "<any-address />" doesn't seem like an obvious value for specifying the wildcard interface - I'd think that the standard "0.0.0.0" would lead to less problems. If it's impossible to support 0.0.0.0 specifically, or to add support for -b again, then some additional information on the error message that comes back from when a user attempts the -b argument would be more helpful. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
5
0 / 0

[JBoss JIRA] Resolved: (AS7-1819) CLONE - CLI - Queue is set durable=false by default - should be durable=true according description of add-jms-queue command

by Paul Gier (JIRA)

[ https://issues.jboss.org/browse/AS7-1819?page=com.atlassian.jira.plugin.s... ] Paul Gier resolved AS7-1819. ---------------------------- Fix Version/s: 7.0.2.Final (was: 7.1.0.CR1) Resolution: Done > CLONE - CLI - Queue is set durable=false by default - should be durable=true according description of add-jms-queue command > --------------------------------------------------------------------------------------------------------------------------- > > Key: AS7-1819 > URL: https://issues.jboss.org/browse/AS7-1819 > Project: Application Server 7 > Issue Type: Bug > Components: JMS > Affects Versions: 7.0.1.Final > Reporter: Miroslav Novak > Assignee: Paul Gier > Fix For: 7.0.2.Final > > > When creating new jms queue using add-jms-queue command and not specifying durable attribute then by default is durable=false - should be durable=true according description of add-jms-queue command. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (AS7-1819) CLONE - CLI - Queue is set durable=false by default - should be durable=true according description of add-jms-queue command

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/AS7-1819?page=com.atlassian.jira.plugin.s... ] Alexey Loubyansky updated AS7-1819: ----------------------------------- Assignee: Paul Gier (was: Alexey Loubyansky) Git Pull Request: https://github.com/jbossas/jboss-as/pull/291 (was: https://github.com/jbossas/jboss-as/pull/291) Component/s: JMS (was: CLI) > CLONE - CLI - Queue is set durable=false by default - should be durable=true according description of add-jms-queue command > --------------------------------------------------------------------------------------------------------------------------- > > Key: AS7-1819 > URL: https://issues.jboss.org/browse/AS7-1819 > Project: Application Server 7 > Issue Type: Bug > Components: JMS > Affects Versions: 7.0.1.Final > Reporter: Miroslav Novak > Assignee: Paul Gier > Fix For: 7.1.0.CR1 > > > When creating new jms queue using add-jms-queue command and not specifying durable attribute then by default is durable=false - should be durable=true according description of add-jms-queue command. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 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 September 2011