November 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-672) HostController status

by Brian Stansberry (Updated) (JIRA)

[ https://issues.jboss.org/browse/AS7-672?page=com.atlassian.jira.plugin.sy... ] Brian Stansberry updated AS7-672: --------------------------------- Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) > HostController status > --------------------- > > Key: AS7-672 > URL: https://issues.jboss.org/browse/AS7-672 > Project: Application Server 7 > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 7.1.0.CR1 > > > Analogous to a server's status, but for a HostController. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-9139) Eliminate dependency of domain-controller module on server module

by Brian Stansberry (JIRA)

Eliminate dependency of domain-controller module on server module ----------------------------------------------------------------- Key: JBAS-9139 URL: https://issues.jboss.org/browse/JBAS-9139 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.Beta3 Get these separated. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
7
0 / 0

[JBoss JIRA] Created: (JBAS-8423) Ensure that connectors that handle end user request start late in the server start process

by Brian Stansberry (JIRA)

Ensure that connectors that handle end user request start late in the server start process ------------------------------------------------------------------------------------------ Key: JBAS-8423 URL: https://jira.jboss.org/browse/JBAS-8423 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assignee: Emanuel Muckenhuber Fix For: 7.0.0.M1 Ensure all connectors that handle user requests have appropriate behavior with respect to not starting until the overall server start is in a state where the connector can handle the expected requests. Part of this is understanding how the clients work; i.e. for some connectors clients may never send a request that the server can't correctly handle. For others, e.g. web connectors fronted by mod_jk or most hardware load balancers, once the connector is started, it may start receiving requests for apps that are not deployed. This is somewhat related to graceful shutdown, where the connector should stop handling requests at the appropriate point in a shutdown process. -- 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, 6 months

6
7
0 / 0

[JBoss JIRA] Created: (JBAS-8208) Expressing configuration property metadata in domain schema

by Brian Stansberry (JIRA)

Expressing configuration property metadata in domain schema ----------------------------------------------------------- Key: JBAS-8208 URL: https://jira.jboss.org/browse/JBAS-8208 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Emanuel Muckenhuber Fix For: 7.0.0.M1 Clients of the domain management API are going to need to see metadata about the various items they are configuring. Besides simple type stuff, information on things like whether changes require restart, etc, need to be available. This task is to determine where this information comes from and how it can be made available to the layer that provides it to the client. -- 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, 6 months

5
11
0 / 0

[JBoss JIRA] Created: (AS7-1307) Server does not start unless CONSOLE handler is specified in logging.properties.

by Hanai Shisei (JIRA)

Server does not start unless CONSOLE handler is specified in logging.properties. -------------------------------------------------------------------------------- Key: AS7-1307 URL: https://issues.jboss.org/browse/AS7-1307 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.0.0.Final Environment: Ubuntu 10.04 AMD64 java version "1.6.0_20" Java(TM) SE Runtime Environment (build 1.6.0_20-b02) Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode) Reporter: Hanai Shisei Assignee: David Lloyd If I change the logging configuration (standalone/configuration/logging.properties) as the following to prevent console logging: #logger.handlers=FILE,CONSOLE logger.handlers=FILE Server does not start. The log file (standalone/log/boot.log) seems broken and sometimes OutOfMemoryError is recorded: 10:42:26,615 INFO [stdout] ]): java.lang.OutOfMemoryError: Java heap space 10:42:26,615 INFO [stdout] at java.util.Arrays.copyOf(Arrays.java:2882) [:1.6.0_20] 10:42:26,615 INFO [stdout] at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:100) [:1.6.0_20] 10:42:26,615 INFO [stdout] at java.lang.StringBuilder.append(StringBuilder.java:130) [:1.6.0_20] 10:42:26,615 INFO [stdout] at java.lang.StringBuilder.append(StringBuilder.java:171) [:1.6.0_20] 10:42:26,615 INFO [stdout] at org.jboss.logmanager.formatters.Formatters$JustifyingFormatStep.render(Formatters.java:157) [jboss-logmanager-1.2.0.GA.jar:1.2.0.GA] 10:42:26,615 INFO [stdout] at org.jboss.logmanager.formatters.MultistepFormatter.format(MultistepFormatter.java:86) [jboss-logmanager-1.2.0.GA.jar:1.2.0.GA] 10:42:26,616 INFO [stdout] at org.jboss.logmanager.ExtFormatter.format(ExtFormatter.java:35) [jboss-logmanager-1.2.0.GA.jar:1.2.0.GA] 10:42:26,616 INFO [stdout] at org.jboss.logmanager.handlers.WriterHandler.doPublish(WriterHandler.java:49) [jboss-logmanager-1.2.0.GA.jar:1.2.0.GA] 10:42:26,616 INFO [stdout] at org.jboss.logmanager.ExtHandler.publish(ExtHandler.java:64) [jboss-logmanager-1.2.0.GA.jar:1.2.0.GA] 10:42:26,616 INFO [stdout] at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:283) [jboss-logmanager-1.2.0.GA.jar:1.2.0.GA] 10:42:26,616 INFO [stdout] at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:291) [jboss-logmanager-1.2.0.GA.jar:1.2.0.GA] 10:42:26,616 INFO [stdout] at org.jboss.logmanager.Logger.logRaw(Logger.java:649) [jboss-logmanager-1.2.0.GA.jar:1.2.0.GA] 10:42:26,616 INFO [stdout] at org.jboss.logmanager.Logger.log(Logger.java:434) [jboss-logmanager-1.2.0.GA.jar:1.2.0.GA] 10:42:26,616 INFO [stdout] at org.jboss.stdio.AbstractLoggingWriter.write(AbstractLoggingWriter.java:71) 10:42:26,616 INFO [stdout] at org.jboss.stdio.WriterOutputStream.finish(WriterOutputStream.java:137) 10:42:26,616 INFO [stdout] at org.jboss.stdio.WriterOutputStream.write(WriterOutputStream.java:106) 10:42:26,616 INFO [stdout] at java.io.PrintStream.write(PrintStream.java:430) [:1.6.0_20] 10:42:26,616 INFO [stdout] at org.jboss.stdio.StdioContext$DelegatingPrintStream.write(StdioContext.java:225) 10:42:26,616 INFO [stdout] at org.jboss.logmanager.handlers.UncloseableOutputStream.write(UncloseableOutputStream.java:47) [jboss-logmanager-1.2.0.GA.jar:1.2.0.GA] 10:42:26,616 INFO [stdout] at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:202) [:1.6.0_20] 10:42:26,616 INFO [stdout] at sun.nio.cs.StreamEncoder.implWrite(StreamEncoder.java:263) [:1.6.0_20] 10:42:26,616 INFO [stdout] at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:106) [:1.6.0_20] 10:42:26,616 INFO [stdout] at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:116) [:1.6.0_20] 10:42:26,616 INFO [stdout] at java.io.OutputStreamWriter.write(OutputStreamWriter.java:203) [:1.6.0_20] 10:42:26,616 INFO [stdout] at java.io.Writer.write(Writer.java:140) [:1.6.0_20] 10:42:26,616 INFO [stdout] at org.jboss.logmanager.handlers.WriterHandler.doPublish(WriterHandler.java:68) [jboss-logmanager-1.2.0.GA.jar:1.2.0.GA] 10:42:26,616 INFO [stdout] at org.jboss.logmanager.ExtHandler.publish(ExtHandler.java:64) [jboss-logmanager-1.2.0.GA.jar:1.2.0.GA] 10:42:26,616 INFO [stdout] at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:283) [jboss-logmanager-1.2.0.GA.jar:1.2.0.GA] 10:42:26,616 INFO [stdout] at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:291) [jboss-logmanager-1.2.0.GA.jar:1.2.0.GA] 10:42:26,616 INFO [stdout] at org.jboss.logmanager.Logger.logRaw(Logger.java:649) [jboss-logmanager-1.2.0.GA.jar:1.2.0.GA] 10:42:26,616 INFO [stdout] at org.jboss.logmanager.Logger.log(Logger.java:434) [jboss-logmanager-1.2.0.GA.jar:1.2.0.GA] 10:42:26,616 INFO [stdout] at org.jboss.stdio.AbstractLoggingWriter.write(AbstractLoggingWriter.java:71) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

5
9
0 / 0

[JBoss JIRA] (AS7-2455) Size rotating file handler incorrectly handles file size

by Stan Silvert (Created) (JIRA)

Size rotating file handler incorrectly handles file size -------------------------------------------------------- Key: AS7-2455 URL: https://issues.jboss.org/browse/AS7-2455 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.1.0.Alpha1 Reporter: Stan Silvert Assignee: James Perkins In SizeRotatingFileHandler, the file size is defined like this: {code:xml}<xs:complexType name="sizeType"> <xs:attribute name="value"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:pattern value="^[0-9]+[bkmgtp]?$"/> </xs:restriction> </xs:simpleType> </xs:attribute> </xs:complexType>{code} However, the model is using a Long instead of a String. So you can't specify file sizes like "10m" or "256k". -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-831) Domain model to hold security properties

by Anil Saldhana (JIRA)

Domain model to hold security properties ---------------------------------------- Key: AS7-831 URL: https://issues.jboss.org/browse/AS7-831 Project: Application Server 7 Issue Type: Feature Request Components: Security Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: 7.0.0.CR1 It should be possible to configure a set of key value pairs that represent security properties which the AS should turn into Security.setProperty(key,value) calls. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
4
0 / 0

[JBoss JIRA] Created: (AS7-1302) Present a version of JAXP to use as an endorsed library

by David Lloyd (JIRA)

Present a version of JAXP to use as an endorsed library ------------------------------------------------------- Key: AS7-1302 URL: https://issues.jboss.org/browse/AS7-1302 Project: Application Server 7 Issue Type: Task Components: XML Frameworks Reporter: David Lloyd Assignee: Jason Greene Fix For: 7.1.0.Alpha1 With JBoss Modules 1.1, the "jaxpmodule" facility has been eliminated. Instead we will take a simpler approach: simply endorse a JAXP API family of our own. The following tasks are required: # Provide a full JAXP implementation which covers all JAXP APIs # Add a method or methods to these APIs which either: #* allow the default provider for each API to be specified #* allow a selector object for each API to be specified, which returns the appropriate implementation on request # Modify AS startup to include these JARs in the endorsed path # Modify the AS JAXP API modules to filter through to the system class path instead of packaging the JARs as modules # Remove said packaging from build.xml # Remove the AS JAXP implementation modules from build.xml and the build module repository -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-8983) Detect, filter, and act upon system APIs found in deployments

by David Lloyd (JIRA)

Detect, filter, and act upon system APIs found in deployments ------------------------------------------------------------- Key: JBAS-8983 URL: https://issues.jboss.org/browse/JBAS-8983 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.CR1 Implement a fixed set of package paths which are automatically filtered out of deployments. In addition, certain paths should be interpreted as an implicit dependency request. For example if "org/slf4j" is found in a deployment, it should be filtered, and an implicit import dependency upon the org.slf4j module (which provides the org.slf4j package) should be added to the deployment. Use sub-tasks for each API to filter or detect. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

7
14
0 / 0

[JBoss JIRA] Created: (AS7-1128) Allow the server to ignore files or groups of files at deployment time

by Marius Bogoevici (JIRA)

Allow the server to ignore files or groups of files at deployment time ---------------------------------------------------------------------- Key: AS7-1128 URL: https://issues.jboss.org/browse/AS7-1128 Project: Application Server 7 Issue Type: Feature Request Components: Server Affects Versions: 7.0.0.CR1 Reporter: Marius Bogoevici Assignee: Marius Bogoevici Fix For: 7.1.0.Alpha1 Legacy and migrated applications may occasionally contain files which are incompatible with the Java EE specification and can cause the application to fail the deployment. The difference between those cases and really faulty Java EE applications lies in the intent of the developer - whether they wish for those files to be picked up by the server and processed, or not. In such cases, it may be useful to expand the deployment specification and to be able to instruct the server to ignore particular files at deployment time. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

4
4
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 November 2011