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