November 2011 - jboss-jira - Jboss List Archives

[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

14 years, 1 month

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

14 years, 1 month

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

14 years, 1 month

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

14 years, 1 month

3
3
0 / 0

[JBoss JIRA] (AS7-2279) SocketBindingGroup not defined for server

by Heiko Braun (Created) (JIRA)

SocketBindingGroup not defined for server ----------------------------------------- Key: AS7-2279 URL: https://issues.jboss.org/browse/AS7-2279 Project: Application Server 7 Issue Type: Clarification Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.1.0.Beta1 How can it be that a server has no explicit socket binding association? See server-one for instance: {noformat} <servers> <server name="server-one" group="main-server-group" auto-start="true"/> <server name="server-two" group="main-server-group" auto-start="false"> <system-properties> <property name="server" value="two" boot-time="false"/> </system-properties> <socket-binding-group ref="standard-sockets" port-offset="150"/> </server> <server name="server-three" group="other-server-group" auto-start="false"> <system-properties> <property name="a" value="a" boot-time="false"/> <property name="b" value="b"/> </system-properties> <socket-binding-group ref="ha-sockets" port-offset="250"/> </server> </servers> {noformat} -- 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

14 years, 1 month

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

14 years, 1 month

4
7
0 / 0

[JBoss JIRA] (AS7-333) Context is lost if a service fails to start for a 'random' reason

by David Lloyd (Updated) (JIRA)

[ https://issues.jboss.org/browse/AS7-333?page=com.atlassian.jira.plugin.sy... ] David Lloyd updated AS7-333: ---------------------------- Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) Priority: Minor (was: Major) > Context is lost if a service fails to start for a 'random' reason > ----------------------------------------------------------------- > > Key: AS7-333 > URL: https://issues.jboss.org/browse/AS7-333 > Project: Application Server 7 > Issue Type: Feature Request > Reporter: Carlo de Wolf > Assignee: David Lloyd > Priority: Minor > Fix For: 7.1.0.CR1 > > > The error message only contains "Failed to start service" it would be nice if the optional causing message is also appended. > {noformat} > 13:58:53,058 INFO [org.jboss.as.server] (MSC service thread 1-9) Service status report > Services which failed to start: > service jboss.deployment.unit."welcome.war": org.jboss.msc.service.StartException in service jboss.deployment.unit."welcome.war": Failed to start service > {noformat} > https://github.com/jbossas/jboss-msc/blob/1.0.0.Beta8/src/main/java/org/j... -- 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

14 years, 1 month

1
0
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

14 years, 1 month

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

14 years, 1 month

4
6
0 / 0

[JBoss JIRA] (AS7-2453) AbstractParser.parseExtension error

by Jesper Pedersen (Created) (JIRA)

AbstractParser.parseExtension error ----------------------------------- Key: AS7-2453 URL: https://issues.jboss.org/browse/AS7-2453 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.1.0.Alpha1 Reporter: Jesper Pedersen Assignee: Stefano Maestri Fix For: 7.1.0.Beta1 {code} ... <validation> <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.novendor.NullExceptionSorter"/> <stale-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.novendor.NullStaleConnectionChecker"/> <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.novendor.NullValidConnectionChecker"/> </validation> ... {code} gives aused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[121,23] Message: Unexpected attribute 'class-name' encountered at org.jboss.as.controller.parsing.ParseUtils.unexpectedAttribute(ParseUtils.java:102) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.controller.parsing.ParseUtils.requireSingleAttribute(ParseUtils.java:352) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.controller.parsing.ParseUtils.readStringAttributeElement(ParseUtils.java:267) [jboss-as-controller-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.connector.util.AbstractParser.parseExtension(AbstractParser.java:103) at org.jboss.as.connector.subsystems.datasources.DsParser.parseValidationSetting(DsParser.java:1022) at org.jboss.as.connector.subsystems.datasources.DsParser.parseDataSource(DsParser.java:719) at org.jboss.as.connector.subsystems.datasources.DsParser.parseDataSources(DsParser.java:195) at org.jboss.as.connector.subsystems.datasources.DsParser.parse(DsParser.java:166) at org.jboss.as.connector.subsystems.datasources.DataSourcesExtension$NewDataSourceSubsystemParser.readElement(DataSourcesExtension.java:704) ... 14 more -- 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

14 years, 1 month

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2011