April 2011 - jboss-jira - Jboss List Archives

[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

13 years

3
3
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

13 years

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

13 years

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

13 years

5
9
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

13 years

5
10
0 / 0

[JBoss JIRA] Created: (JBAS-9011) Deployment phases need cleaning up

by David Lloyd (JIRA)

Deployment phases need cleaning up ---------------------------------- Key: JBAS-9011 URL: https://issues.jboss.org/browse/JBAS-9011 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.CR1 Every deployment phase adds a level of latency to deployment; thus we need to minimize them. There are some phases which are redundant, and some which are wholly unused which need to be consolidated and cleaned up. The deployment phase numbering should be finalized at this time. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-8979) Rename "ejb3" subsystem to "ejb"

by David Lloyd (JIRA)

Rename "ejb3" subsystem to "ejb" -------------------------------- Key: JBAS-8979 URL: https://issues.jboss.org/browse/JBAS-8979 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Priority: Minor Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-8578) JMXConnector should support "jmxconnector" alias used by jmx-remoting.sar

by Scott Marlow (JIRA)

JMXConnector should support "jmxconnector" alias used by jmx-remoting.sar ------------------------------------------------------------------------- Key: JBAS-8578 URL: https://jira.jboss.org/browse/JBAS-8578 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JMX Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 6.0.0.Final, 7.0.0.M2 For users that might of previously used jmx-remoting.sar. Add /jmxrmi alias for AS6+AS7. They could also later change their application for AS6/AS7 to use the "service:jmx:rmi:///jndi/rmi://localhost:1090/jmxrmi" URL. This should be a one line change (I hope :-): registry.rebind("jmxrmi", rmiServer.toStub()); registry.rebind("jmxconnector", rmiServer.toStub()); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
7
0 / 0

[JBoss JIRA] Created: (JBAS-6332) Injection from outside modules

by Carlo de Wolf (JIRA)

Injection from outside modules ------------------------------ Key: JBAS-6332 URL: https://jira.jboss.org/jira/browse/JBAS-6332 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.GA Reporter: Carlo de Wolf When a servlet is packaged standalone (outside ear) and an EJB is packaged standalone, the EJB can't be injected into the servlet without specifying a JNDI name somewhere. It would be nice to have the ability to inject beans from outside your own enterprise application. -- 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

13 years

7
9
0 / 0

[JBoss JIRA] Created: (JBAS-9192) Unclean handling of socket close

by Brian Stansberry (JIRA)

Unclean handling of socket close -------------------------------- Key: JBAS-9192 URL: https://issues.jboss.org/browse/JBAS-9192 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Priority: Minor Fix For: 7.0.0.Beta3 This stuff appears in the DC logs quite a bit, particularly at shutdown: [Host Controller] 10:55:26,174 ERROR [org.jboss.as.management] (Read thread for /127.0.0.1:59552) java.net.SocketException: Connection reset I've marked this as minor as it's not worth much effort unless it continues following the switch from jboss-as-protocol to Remoting3. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2011