October 2011 - jboss-jira - Jboss List Archives

[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

12 years, 11 months

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

12 years, 11 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

12 years, 11 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

12 years, 11 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

12 years, 11 months

4
4
0 / 0

[JBoss JIRA] Created: (AS7-814) Fix or remove ignored smoke tests

by Thomas Diesler (JIRA)

Fix or remove ignored smoke tests --------------------------------- Key: AS7-814 URL: https://issues.jboss.org/browse/AS7-814 Project: Application Server 7 Issue Type: Task Reporter: Thomas Diesler Assignee: Jason Greene 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

12 years, 11 months

5
11
0 / 0

[JBoss JIRA] Created: (JBAS-8137) Simple start and stop scripts

by Brian Stansberry (JIRA)

Simple start and stop scripts ----------------------------- Key: JBAS-8137 URL: https://jira.jboss.org/browse/JBAS-8137 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: Unscheduled This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010: >> I would like to see all the configurations that normally get set on the >> command line (JBoss opts and system props) moved to a config file so all >> that is ever required to start a Jboss instance is simply "run.sh >> /<configuration>/". The domain and host configuration files we'll introduce with AS 7 should encapsulate most things that are currently passed in via -D or the arguments to main(). If we start adding additional command line options that need to be processed before the domain/host configuration files are read, we should make it easy to set those in a configuration file (perhaps a simple properties file). -- 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

12 years, 11 months

4
6
0 / 0

[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, 11 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, 11 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, 11 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2011