July 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4925) Log4j appenders should also be allowed for custom handlers

by James Perkins (JIRA)

James Perkins created AS7-4925: ---------------------------------- Summary: Log4j appenders should also be allowed for custom handlers Key: AS7-4925 URL: https://issues.jboss.org/browse/AS7-4925 Project: Application Server 7 Issue Type: Bug Components: Logging Reporter: James Perkins Assignee: James Perkins Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 Currently custom handlers only allows for a {{java.util.logging.Handler}}. log4j appenders also need to be allowed and configured. -- 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

13 years, 10 months

3
13
0 / 0

[JBoss JIRA] (AS7-4791) Convert logging subsystem to ResourceDefinition

by Tomaz Cerar (JIRA)

Tomaz Cerar created AS7-4791: -------------------------------- Summary: Convert logging subsystem to ResourceDefinition Key: AS7-4791 URL: https://issues.jboss.org/browse/AS7-4791 Project: Application Server 7 Issue Type: Sub-task Components: Logging Affects Versions: 7.1.2.Final (EAP), 7.1.1.Final Reporter: Tomaz Cerar Assignee: James Perkins Fix For: 7.2.0.Alpha1 Convert logging subsystem to ResourceDefinition to unify and cleanup the code -- 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

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] (JBJCA-840) Common test suite

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-840: ------------------------------------- Summary: Common test suite Key: JBJCA-840 URL: https://issues.jboss.org/browse/JBJCA-840 Project: IronJacamar Issue Type: Task Components: Common Reporter: Jesper Pedersen Assignee: Vladimir Rastseluev Fix For: 1.1.0.Beta2 * Clean up common/ test suite for duplicated tests * Improve code coverage, especially for resource adapter v1.0 * Remove incorrect DTD tests for v1.5 and v1.6 * Give descriptive names for test classes and resources -- 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

13 years, 10 months

2
2
0 / 0

[JBoss JIRA] (AS7-4249) Inhereted start/stop methods are not invoked on a POJO

by Ivo Studensky (JIRA)

Ivo Studensky created AS7-4249: ---------------------------------- Summary: Inhereted start/stop methods are not invoked on a POJO Key: AS7-4249 URL: https://issues.jboss.org/browse/AS7-4249 Project: Application Server 7 Issue Type: Bug Components: POJO Affects Versions: 7.1.1.Final Reporter: Ivo Studensky Assignee: Ales Justin Fix For: 7.1.2.Final Let's say we have a POJO A which extends a class B. The start/stop methods are defined in the class B. In the jboss-beans.xml file is something like this: <bean name="A" class="blah.blah.A"/> Then, only the constructor of A is invoked by AS7, but no invocation of start/stop methods occur. The start/stop methods are invoked only if they are directly defined in A. -- 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

13 years, 10 months

3
4
0 / 0

[JBoss JIRA] (JBAS-9503) Too many Open files in JBoss AS7

by Suman Alapati (JIRA)

Suman Alapati created JBAS-9503: ----------------------------------- Summary: Too many Open files in JBoss AS7 Key: JBAS-9503 URL: https://issues.jboss.org/browse/JBAS-9503 Project: Application Server 3 4 5 and 6 Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Deployers Reporter: Suman Alapati Assignee: Ales Justin Hi, I am Using Jboss As-7 as my application server in Linux box at the time of deployment i am getting below stack trace. Can one let me the reason behind of the below Stack Trace : ========================================================================= Caused by: java.io.FileNotFoundException: /home/appuser/dpc/jbossas7/standalone/tmp/vfs/deploymentca2dd52bc934385/xbean-2.1.0.jar-972256156c28c093/xbean-2.1.0.jar (Too many open files) at java.io.FileOutputStream.open(Native Method) [rt.jar:1.6.0_22] at java.io.FileOutputStream.<init>(FileOutputStream.java:209) [rt.jar:1.6.0_22] at java.io.FileOutputStream.<init>(FileOutputStream.java:160) [rt.jar:1.6.0_22] at org.jboss.vfs.TempDir.createFile(TempDir.java:93) at org.jboss.vfs.spi.JavaZipFileSystem.<init>(JavaZipFileSystem.java:83) at org.jboss.vfs.VFS.mountZip(VFS.java:408) at org.jboss.vfs.VFS.mountZip(VFS.java:434) at org.jboss.as.web.deployment.WarStructureDeploymentProcessor.createWebInfLibResources(WarStructureDeploymentProcessor.java:170) ... 8 more 13:48:02,874 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "uisearch.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"uisearch.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"uisearch.war\".STRUCTURE: Failed to process phase STRUCTURE of deployment \"uisearch.war\""}} 13:48:02,915 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment uisearch.war in 41ms 13:48:02,917 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report JBAS014777: Services which failed to start: service jboss.deployment.unit."uisearch.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."uisearch.war".STRUCTURE: Failed to process phase STRUCTURE of deployment "uisearch.war" ======================================================================= I am Still Confusing where i am doing wrong . And i would like to know is it because of Jboss or Linux box. Thanks in Advance, Suman Alapati. -- 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

13 years, 10 months

3
4
0 / 0

[JBoss JIRA] (AS7-4167) Admin console: cannot set attribute max-attempts of modcluster subsystem

by Jan Martiska (JIRA)

Jan Martiska created AS7-4167: --------------------------------- Summary: Admin console: cannot set attribute max-attempts of modcluster subsystem Key: AS7-4167 URL: https://issues.jboss.org/browse/AS7-4167 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.1.Final Reporter: Jan Martiska Assignee: Heiko Braun Priority: Minor Under Networking tab of modcluster configuration - property "Max Attempts" cannot be set- console references it as "max-attemps" instead of the correct "max-attempts" {noformat} { "outcome" => "failed", "result" => {"step-1" => { "outcome" => "failed", "failure-description" => "JBAS014792: Unknown attribute max-attemps", "rolled-back" => true }}, "failure-description" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014792: Unknown attribute max-attemps"}}, "rolled-back" => true, "response-headers" => {"process-state" => "reload-required"} } {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

13 years, 10 months

1
5
0 / 0

[JBoss JIRA] (AS7-4166) Admin console: cannot set attribute auto-enable-contexts of modcluster subsystem

by Jan Martiska (JIRA)

Jan Martiska created AS7-4166: --------------------------------- Summary: Admin console: cannot set attribute auto-enable-contexts of modcluster subsystem Key: AS7-4166 URL: https://issues.jboss.org/browse/AS7-4166 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.1.Final Reporter: Jan Martiska Assignee: Heiko Braun Priority: Minor Under Web Contexts tab of modcluster configuration - property "Auto Enable Contexts" cannot be set- console references it as "auto-enableContexts" instead of the correct "auto-enable-contexts" {noformat} { "outcome" => "failed", "result" => {"step-1" => { "outcome" => "failed", "failure-description" => "JBAS014792: Unknown attribute auto-enableContexts", "rolled-back" => true }}, "failure-description" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014792: Unknown attribute auto-enableContexts"}}, "rolled-back" => true, "response-headers" => {"process-state" => "reload-required"} {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

13 years, 10 months

1
5
0 / 0

[JBoss JIRA] Created: (AS7-1263) Publish deployment descriptor schemas and dtd in the dist

by Brian Stansberry (JIRA)

Publish deployment descriptor schemas and dtd in the dist --------------------------------------------------------- Key: AS7-1263 URL: https://issues.jboss.org/browse/AS7-1263 Project: Application Server 7 Issue Type: Task Affects Versions: 7.0.0.Final Reporter: Brian Stansberry Fix For: 7.0.1.Final AS 7.0 has the domain/host/standalone config schemas in docs/schema, but not the deployment descriptor schemas and DTDs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

7
14
0 / 0

[JBoss JIRA] (AS7-4057) Create logging profiles for deployments

by James Perkins (JIRA)

James Perkins created AS7-4057: ---------------------------------- Summary: Create logging profiles for deployments Key: AS7-4057 URL: https://issues.jboss.org/browse/AS7-4057 Project: Application Server 7 Issue Type: Feature Request Components: Logging Reporter: James Perkins Assignee: James Perkins Fix For: 7.2.0.Alpha1 Create logging profiles to be assignable to deployments. The precedence would be deployment configuration -> profile configuration -> default configuration. This would allow profiles to be configured with the management interface. Each profile would have it's own LogContext and the context could be secured. -- 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

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] (AS7-2385) Management - readding file handler logger fails

by Dominik Pospisil (Created) (JIRA)

Management - readding file handler logger fails ----------------------------------------------- Key: AS7-2385 URL: https://issues.jboss.org/browse/AS7-2385 Project: Application Server 7 Issue Type: Bug Components: Domain Management, Logging Affects Versions: 7.1.0.Beta1 Reporter: Dominik Pospisil Assignee: Brian Stansberry Removing and adding file handler fails. Perhaps remove operation does not clean up all resources properlly. Steps to reproduce: [standalone@localhost:9999 /] /subsystem=logging/file-handler=test-fh:add(name="test-fh", level="WARN", file={"path" => "/home/dpospisi/testfh.log"}) {"outcome" => "success"} [standalone@localhost:9999 /] /subsystem=logging/file-handler=test-fh:remove {"outcome" => "success"} [standalone@localhost:9999 /] /subsystem=logging/file-handler=test-fh:add(name="test-fh", level="WARN", file={"path" => "/home/dpospisi/testfh.log"}) { "outcome" => "failed", "failure-description" => "Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service jboss.logging.handler-file.test-fh is already registered", "rolled-back" => true } [standalone@localhost:9999 /] -- 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

13 years, 10 months

6
5
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 July 2012