January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3325) An ACL and Authorization checks for Remote access to JMX.

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3325: ------------------------------------- Summary: An ACL and Authorization checks for Remote access to JMX. Key: AS7-3325 URL: https://issues.jboss.org/browse/AS7-3325 Project: Application Server 7 Issue Type: Task Components: JMX, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] (AS7-2609) Document the Http Management API

by Vimal Kansal (Created) (JIRA)

Document the Http Management API -------------------------------- Key: AS7-2609 URL: https://issues.jboss.org/browse/AS7-2609 Project: Application Server 7 Issue Type: Bug Components: Documentation Reporter: Vimal Kansal The page https://docs.jboss.org/author/display/AS71/The+HTTP+management+API needs update -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-9257) BridgeLogger implementation of Logger does not support Level.OFF or null as parameter values for setLevel method

by Antonio Montanana (JIRA)

BridgeLogger implementation of Logger does not support Level.OFF or null as parameter values for setLevel method ---------------------------------------------------------------------------------------------------------------- Key: JBAS-9257 URL: https://issues.jboss.org/browse/JBAS-9257 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Logging Affects Versions: 6.0.0.M2 Reporter: Antonio Montanana Assignee: David Lloyd Deploying our application on the JBoss 6.0.0 application server we encounter the following NullPointerException (NPE) also logged in the log\server.log file: 2011-03-17 12:52:18,269 ERROR [filenet_error.engine.com.filenet.engine.tasks.TaskManager] (TaskManager$RootTask_RootTask_ScheduledPoolExecutor_9) TaskManager$RootTask:RootTask running with error , with message null: java.lang.NullPointerException at org.jboss.logmanager.log4j.LevelMapping.getLevelFor(LevelMapping.java:65) [:6.0.0.Final] at org.jboss.logmanager.log4j.BridgeLogger.setPriority(BridgeLogger.java:199) [:6.0.0.Final] at org.jboss.logmanager.log4j.BridgeLogger.setLevel(BridgeLogger.java:194) [:6.0.0.Final] at com.filenet.engine.util.Logger.removeTraceLoggerLevel(Logger.java:377) ... The com.filenet.engine.util.Logger.removeTraceLoggerLevel method executes the following two lines of code: org.apache.log4j.Logger traceLogger = getLog4JTraceLogger(subsystem, traceFlag); traceLogger.setLevel(null); Note the setLevel method is passing in a null parameter value (supported by org.apache.log4j.Logger.setLevel) to remove the specified logging level. We've verified that the JBoss LevelMapping.getLevelFor method throws the NPE as a result of the null parameter value passed into setLevel (changing the parameter value to another level (e.g. Level.DEBUG) eliminates the exception). The setLevel(null) code executed with no exceptions in JBoss 5.1.0 and earlier versions of the server and is supported by org.apache.log4j.Logger.setLevel. It appears that the logging mechanism has changed significantly in JBoss 6.0, there is now a BridgeLogger class that extends the org.apache.log4j.Logger class providing the implementation of the setLevel method. That implementation appears to have omitted support for "null" as a parameter value and causes the NPE. Further testing indicates that the Level.OFF value is also not supported either - leaving no way to remove the logging level. We would like to see support for "null" and Level.OFF added to the BridgeLogger extension of Logger. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-8781) Can't parse JSF TLD

by Stan Silvert (JIRA)

Can't parse JSF TLD ------------------- Key: JBAS-8781 URL: https://issues.jboss.org/browse/JBAS-8781 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: 7.0.0.Alpha1 Reporter: Stan Silvert Assignee: Remy Maucherat WAR to reproduce is attached. 15:32:07,764 ERROR [org.jboss.as.server.deployment] (pool-3-thread-1) Caught exc eption handling update (param is 10cd5140-b773-49da-97ab-0fb055b56141): java.lan g.RuntimeException: Failed to process deployment chain. at org.jboss.as.model.ServerDeploymentStartStopHandler.activate(ServerDe ploymentStartStopHandler.java:203) at org.jboss.as.model.ServerDeploymentStartStopHandler.deploy(ServerDepl oymentStartStopHandler.java:87) at org.jboss.as.model.ServerDeploymentStartStopHandler.deploy(ServerDepl oymentStartStopHandler.java:71) at org.jboss.as.model.ServerDeploymentStartStopHandler.redeploy(ServerDe ploymentStartStopHandler.java:117) at org.jboss.as.model.ServerModelDeploymentFullReplaceUpdate.applyUpdate (ServerModelDeploymentFullReplaceUpdate.java:68) at org.jboss.as.server.mgmt.ServerUpdateController$ServerModelUpdateTupl e.applyUpdate(ServerUpdateController.java:430) at org.jboss.as.server.mgmt.ServerUpdateController$ServerModelUpdateTupl e.access$200(ServerUpdateController.java:400) at org.jboss.as.server.mgmt.ServerUpdateController.applyUpdates(ServerUp dateController.java:189) at org.jboss.as.server.mgmt.ServerUpdateController.executeUpdates(Server UpdateController.java:142) at org.jboss.as.server.mgmt.deployment.ServerDeploymentManagerImpl$2.run (ServerDeploymentManagerImpl.java:218) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec utor.java:886) [:1.6.0_18] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor .java:908) [:1.6.0_18] at java.lang.Thread.run(Thread.java:619) [:1.6.0_18] Caused by: org.jboss.as.deployment.unit.DeploymentUnitProcessingException: Faile d to parse "/C:/projects/as7trunk/jboss-as/build/target/jboss-7.0.0.Alpha2/bin/c ontent/mojarra2.0-bundled.war/WEB-INF/lib/jsf-impl-2.0.3-b05.jar/META-INF/html_b asic.tld" at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.parseTLD(Tl dParsingDeploymentProcessor.java:118) at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processTlds (TldParsingDeploymentProcessor.java:97) at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.processDepl oyment(TldParsingDeploymentProcessor.java:77) at org.jboss.as.deployment.chain.DeploymentChainImpl.processDeployment(D eploymentChainImpl.java:50) at org.jboss.as.model.ServerDeploymentStartStopHandler.activate(ServerDe ploymentStartStopHandler.java:201) ... 12 more Caused by: java.lang.IllegalArgumentException: No enum const class org.jboss.met adata.web.spec.BodyContentType. JSP at java.lang.Enum.valueOf(Enum.java:196) [:1.6.0_18] at org.jboss.metadata.web.spec.BodyContentType.valueOf(BodyContentType.j ava:32) at org.jboss.as.metadata.parser.jsp.TagMetaDataParser.parse(TagMetaDataP arser.java:111) at org.jboss.as.metadata.parser.jsp.TldMetaDataParser.parse(TldMetaDataP arser.java:200) at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.parseTLD(Tl dParsingDeploymentProcessor.java:116) ... 16 more -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
13
0 / 0

[JBoss JIRA] Created: (AS7-1946) Supported operation names not documented

by Thomas Diesler (JIRA)

Supported operation names not documented ---------------------------------------- Key: AS7-1946 URL: https://issues.jboss.org/browse/AS7-1946 Project: Application Server 7 Issue Type: Bug Components: CLI Reporter: Thomas Diesler Assignee: Alexey Loubyansky Fix For: 7.1.0.Beta1 The CLI does not document the set of supported operations. It says {code} Operation requests are expected to follow the format: [node-type=node-name (, node-type=node-name)*] : operation-name ['('[name=value [, name=value]*]')'] e.g. /subsystem=web/connector=http:read-attribute(name=protocol) {code} but does not say what read-attribute does. Neither does it say what other operation names the CLI supports. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
6
0 / 0

[JBoss JIRA] (AS7-3521) @ArquillianResource ManagementClient injection does not work in 'manual' container mode

by Ivo Studensky (JIRA)

Ivo Studensky created AS7-3521: ---------------------------------- Summary: @ArquillianResource ManagementClient injection does not work in 'manual' container mode Key: AS7-3521 URL: https://issues.jboss.org/browse/AS7-3521 Project: Application Server 7 Issue Type: Bug Components: Test Suite Reporter: Ivo Studensky Assignee: Andrew Rubinger Priority: Critical Fix For: 7.1.1.Final ManagementClient cannot be injected by @ArquillianResource annotation if the test runs in the manual container mode, i.e. if the test itself controls start/stop actions on the container. In such case the injection fails with ' java.lang.RuntimeException: Could not lookup value for field private org.jboss.as.arquillian.container.ManagementClient'. See the snippet of output log: {noformat} java.lang.RuntimeException: Could not lookup value for field private static org.jboss.as.arquillian.container.ManagementClient org.jboss.jbossts.txbridge.tests.inbound.junit.BasicTests.managementClient at org.jboss.arquillian.test.impl.enricher.resource.ArquillianResourceTestEnricher.enrich(ArquillianResourceTestEnricher.java:61) at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) at org.jboss.arquillian.container.test.impl.ClientTestInstanceEnricher.enrich(ClientTestInstanceEnricher.java:51) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124) . . . Caused by: java.lang.RuntimeException: Provider for type class org.jboss.as.arquillian.container.ManagementClient returned a null value: org.jboss.as.arquillian.container.ManagementClientProvider@3d47358f at org.jboss.arquillian.test.impl.enricher.resource.ArquillianResourceTestEnricher.lookup(ArquillianResourceTestEnricher.java:115) at org.jboss.arquillian.test.impl.enricher.resource.ArquillianResourceTestEnricher.enrich(ArquillianResourceTestEnricher.java:57) ... 71 more {noformat} I've isolated a test-case for this issue into my private branch on github, see: https://github.com/istudens/jboss-as/compare/inject_mgmt_client Steps to reproduce the issue: 1. git clone git@github.com:istudens/jboss-as.git 2. cd jboss-as 3. git checkout inject_mgmt_client 4. ./build.sh clean install -Dts.noSmoke -DskipTests 5. cd testsuite/integration/manual 6. mvn clean install This issue is related to AS7-1415. -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] (AS7-2093) Create deployment management base view

by David Bosschaert (Created) (JIRA)

Create deployment management base view -------------------------------------- Key: AS7-2093 URL: https://issues.jboss.org/browse/AS7-2093 Project: Application Server 7 Issue Type: Sub-task Components: Console Reporter: David Bosschaert Assignee: Heiko Braun A base view for navigating through deployments needs to be created. This view should allow for deployment-type specific editors to be hooked in. An example deployment-type specific editor would be a web deployment editor. -- 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, 2 months

3
2
0 / 0

[JBoss JIRA] (AS7-2092) Manage Web Services deployment information in the console

by David Bosschaert (Created) (JIRA)

Manage Web Services deployment information in the console --------------------------------------------------------- Key: AS7-2092 URL: https://issues.jboss.org/browse/AS7-2092 Project: Application Server 7 Issue Type: Sub-task Components: Console Reporter: David Bosschaert Assignee: Heiko Braun /deployment=mydeployment.jar/subsystem=webservices contains Web Services deployment information which should be made manageable in the console. This should integrate with the overall deployment management views. -- 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, 2 months

3
2
0 / 0

[JBoss JIRA] (AS7-2750) Manage mail subsystem through console

by Heiko Braun (Created) (JIRA)

Manage mail subsystem through console ------------------------------------- Key: AS7-2750 URL: https://issues.jboss.org/browse/AS7-2750 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun -- 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, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-9363) Make available JBoss AS source code and checksum(s) for download

by jaikiran pai (JIRA)

Make available JBoss AS source code and checksum(s) for download ----------------------------------------------------------------- Key: JBAS-9363 URL: https://issues.jboss.org/browse/JBAS-9363 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: jaikiran pai Fix For: 7.0.0.CR1 JBoss AS source code for AS7 isn't currently made available at http://www.jboss.org/jbossas/downloads.html. We should start uploading the source (and other other artifacts like checksum) for our releases. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

5
8
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 January 2012