November 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1867) Add operations to add and remove individual entries from the global-modules attribute list

by Brian Stansberry (JIRA)

Add operations to add and remove individual entries from the global-modules attribute list ------------------------------------------------------------------------------------------ Key: AS7-1867 URL: https://issues.jboss.org/browse/AS7-1867 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management, EE Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.1.0.Beta1 Add handlers for ops add-item-global-modules-list and remove-item-from-global-modules-list. Currently the global-modules list can be modified using the write-attribute(name=global-modules,value=["a", "b", "c"]) approach but that forces the user to pass in the entire list to make 1 change. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-9176) List servers in a servergroup below /server-group/<groupname>

by Heiko Rupp (JIRA)

List servers in a servergroup below /server-group/<groupname> ------------------------------------------------------------- Key: JBAS-9176 URL: https://issues.jboss.org/browse/JBAS-9176 Project: JBoss Application Server Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta1 Reporter: Heiko Rupp It would be nice from a consistency standpoint to list the servers of a servergroup in its api below /server-group/groupname/ - just the names would be enough. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-9306) Expose address of DC as runtime attributes on the HC

by Heiko Rupp (JIRA)

Expose address of DC as runtime attributes on the HC ---------------------------------------------------- Key: JBAS-9306 URL: https://issues.jboss.org/browse/JBAS-9306 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Heiko Rupp Currently there is no way to learn about the http management port of the DC from a slave's host.xml or runtime. 17:02:31] <pilhuhn> I am reading host.xml to find the DC, so that I can contact its http port for e.g. querying the /socket-binding-group if the one on the host is undefined [17:02:41] <+bstansberry> I don't want it in the config, but I'm ok with adding it as a runtime attribute [17:04:13] <pilhuhn> bstansberry fine with me when I can query the HC for the http port of the DC [17:04:46] <+bstansberry> pilhuhn: the native API port should be a runtime attribute as well [17:04:51] <+bstansberry> yes please [17:05:04] <+bstansberry> what i mean by that is we should expose it as a runtime attribute 17:05:49] <+bstansberry> the config bit is an instruction to the HC, but we are going to add alternatives, e.g. a multicast address [17:06:55] <+bstansberry> so using the config will not be a reliable source; runtime can be -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
3
0 / 0

[JBoss JIRA] (AS7-494) Convert HA-JNDI stubs to Remoting

by David Lloyd (Updated) (JIRA)

[ https://issues.jboss.org/browse/AS7-494?page=com.atlassian.jira.plugin.sy... ] David Lloyd updated AS7-494: ---------------------------- Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) Forum Reference: http://community.jboss.org/thread/82821?tstart=0 (was: http://community.jboss.org/thread/82821?tstart=0) > Convert HA-JNDI stubs to Remoting > --------------------------------- > > Key: AS7-494 > URL: https://issues.jboss.org/browse/AS7-494 > Project: Application Server 7 > Issue Type: Task > Components: Clustering, Naming, Remoting > Reporter: Brian Stansberry > Assignee: David Lloyd > Fix For: 7.1.0.CR1 > > > The HA-JNDI naming service proxy is based on the old HARMIClient and HARMIServer code. We should convert this to use Remoting. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-8952) Fix the testsuite/integration testcase failures

by jaikiran pai (JIRA)

Fix the testsuite/integration testcase failures ----------------------------------------------- Key: JBAS-8952 URL: https://issues.jboss.org/browse/JBAS-8952 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Environment: JBoss AS7 master Reporter: jaikiran pai Assignee: Shelly McGowan Fix For: 7.0.0.CR1 As reported in the mailing list http://lists.jboss.org/pipermail/jboss-as7-dev/2011-March/000759.html thread, the "testsuite/integration" tests are failing with a CCE in JSFUnitApplicationArchiveProcessor: {code} Caused by: java.lang.ClassCastException: org.jboss.shrinkwrap.impl.base.spec.ResourceAdapterArchiveImpl cannot be cast to org.jboss.shrinkwrap.api.spec.WebArchive at org.jboss.jsfunit.arquillian.JSFUnitApplicationArchiveProcessor.process(JSFUnitApplicationArchiveProcessor.java:41) at org.jboss.arquillian.impl.ClientDeploymentGenerator.applyApplicationProcessors(ClientDeploymentGenerator.java:91) at org.jboss.arquillian.impl.ClientDeploymentGenerator.generate(ClientDeploymentGenerator.java:64) at org.jboss.arquillian.impl.handler.ArchiveGenerator.callback(ArchiveGenerator.java:52) at org.jboss.arquillian.impl.handler.ArchiveGenerator.callback(ArchiveGenerator.java:42) at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:63) {code} The tests are currently disabled and need to be fixed and enabled in some upcoming release. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

6
10
0 / 0

[JBoss JIRA] Created: (JBAS-8744) Failure to start the JVM should trigger a management update plan to rollback

by Andrig Miller (JIRA)

Failure to start the JVM should trigger a management update plan to rollback ---------------------------------------------------------------------------- Key: JBAS-8744 URL: https://issues.jboss.org/browse/JBAS-8744 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 7.0.0.Alpha1 Reporter: Andrig Miller Assignee: Brian Stansberry Fix For: 7.0.0.Beta1 I have come across situations where certain JVM options, typically related to NUMA options, can cause the JVM to segfault. With our domain model, we expose the ability to set the JVM options, so I think this certainly would be a possibility. So, as we discussed on the Andiamo call today, this type of situation should cause a rollback of the management update plan, if the JVM fails to start. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-9204) On component stop, destroy all instances

by David Lloyd (JIRA)

On component stop, destroy all instances ---------------------------------------- Key: JBAS-9204 URL: https://issues.jboss.org/browse/JBAS-9204 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EE Reporter: David Lloyd Fix For: 7.0.0.Beta3 This will cause all outstanding component destroy lifecycle methods to be invoked when the component is stopped. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

5
9
0 / 0

[JBoss JIRA] (AS7-2131) Eliminate JNP usage in HornetQ

by David Lloyd (Created) (JIRA)

Eliminate JNP usage in HornetQ ------------------------------ Key: AS7-2131 URL: https://issues.jboss.org/browse/AS7-2131 Project: Application Server 7 Issue Type: Task Components: JMS Reporter: David Lloyd Assignee: Clebert Suconic Priority: Blocker Fix For: 7.1.0.Beta1 Currently HQ is using JNP to get the JNDI mapping for queues and stuff. This will be changed to use a client-side JNDI URL scheme, such as "hq:xxxx" to generate the client-side interfaces much like EJB uses the "ejb:" scheme. There is no server-round trip for this and it will enable us to remove the JNP sockets from the server configuration, which should never have been introduced. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
1
0 / 0

[JBoss JIRA] (AS7-2313) read-operation-name and read-operation-description should be combined

by Kevin Barfield (Created) (JIRA)

read-operation-name and read-operation-description should be combined --------------------------------------------------------------------- Key: AS7-2313 URL: https://issues.jboss.org/browse/AS7-2313 Project: Application Server 7 Issue Type: Bug Components: CLI Reporter: Kevin Barfield Assignee: Alexey Loubyansky For usability, there should be a way to get a list of operation names with the descriptions attached Example: read-resource - This shows you the resources at the this node etc etc etc -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

5
6
0 / 0

[JBoss JIRA] Created: (JBAS-9224) Automatic JNDI implementation

by David Lloyd (JIRA)

Automatic JNDI implementation ----------------------------- Key: JBAS-9224 URL: https://issues.jboss.org/browse/JBAS-9224 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EE, Naming Reporter: David Lloyd Assignee: John Bailey Priority: Critical The JNDI subsystem should become fully service-oriented, meaning: 1) Contexts are always read-only 2) The NamingStore is populated solely by services 3) When the last binding in a context is removed, the context is automatically removed For pesky legacy subsystems which still expect to be able to bind into Context, we could possibly make up a "fake" Context from which the bound ObjectFactory (or whatever) is extracted to create the "real" service. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

5
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2011