January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2232) TS: On -Dtest=..., activate appropriate modules automatically (using package prefix)

by Ondrej Zizka (Created) (JIRA)

TS: On -Dtest=..., activate appropriate modules automatically (using package prefix) ------------------------------------------------------------------------------------ Key: AS7-2232 URL: https://issues.jboss.org/browse/AS7-2232 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Ondrej Zizka Assignee: Ondrej Zizka ...to relieve people from writing `-Dintegration.module` all the time. -- 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

12 years, 7 months

2
1
0 / 0

[JBoss JIRA] (AS7-2961) Context lookup fails during WebService constructor.

by Jeremy Whiting (Created) (JIRA)

Context lookup fails during WebService constructor. ---------------------------------------------------- Key: AS7-2961 URL: https://issues.jboss.org/browse/AS7-2961 Project: Application Server 7 Issue Type: Bug Components: Web Services Affects Versions: 7.1.0.Beta1 Environment: OpenJDK 6 on Fedora16 Reporter: Jeremy Whiting Assignee: Alessio Soldano Attachments: envEntryWeb.tar.gz During a WebService constructor call my application is making a jndi context lookup that is failing. The lookup uses java:comp/env to lookup an entry. The web service is a JEE5 spec application. The application defines an env-entry in the web deployment descriptor. It looks as though the context is not established in time for the WebSevice constructor being called. A sample application is provided to demonstrate the issue. When this application is deployed I am seeing the stack trace in the second attachment. -- 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

12 years, 7 months

9
10
0 / 0

[JBoss JIRA] (AS7-3390) org.apache.commons.collections.ArrayStack in both commons-beanutils-1.8.0.jar , commons-collections-3.2.1.jar

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-3390: --------------------------------- Summary: org.apache.commons.collections.ArrayStack in both commons-beanutils-1.8.0.jar , commons-collections-3.2.1.jar Key: AS7-3390 URL: https://issues.jboss.org/browse/AS7-3390 Project: Application Server 7 Issue Type: Bug Components: Build System Affects Versions: 7.1.0.CR1b Reporter: Ondrej Zizka Assignee: Paul Gier Refer to this TattleTale report: https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Miscellaneous/job/... -- 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

12 years, 7 months

3
3
0 / 0

[JBoss JIRA] (JBRULES-3291) Keyword "Functions" in decision tables (XLS-Format) is not trimmed before comparison

by Heinz Drews (Created) (JIRA)

Keyword "Functions" in decision tables (XLS-Format) is not trimmed before comparison ------------------------------------------------------------------------------------ Key: JBRULES-3291 URL: https://issues.jboss.org/browse/JBRULES-3291 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-decisiontables Affects Versions: 5.2.0.Final Environment: All platforms Reporter: Heinz Drews Assignee: Mark Proctor If the keyword "Functions" is padded with blanks then it is not detected and no code is generated in the DRL -- 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

12 years, 7 months

3
2
0 / 0

[JBoss JIRA] (AS7-3389) jython-standalone-2.5.2.jar contains jline classes, also contained in jline module

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-3389: --------------------------------- Summary: jython-standalone-2.5.2.jar contains jline classes, also contained in jline module Key: AS7-3389 URL: https://issues.jboss.org/browse/AS7-3389 Project: Application Server 7 Issue Type: Bug Components: Build System Affects Versions: 7.1.0.CR1b Reporter: Ondrej Zizka Assignee: Paul Gier The module modules/org/python/jython/standalone/main/jython-standalone-2.5.2.jar contains classes in jline.* package. We already have JLine module. Pls remove JLine classes from the Jython package. Refer to this Tattletale report: https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Miscellaneous/job/... JLine is also used by CLI. (20:53:28) bstansberry: jython is for sure for JDR (20:53:38) pskopek opustil místnost (quit: Quit: Leaving). (20:53:43) bstansberry: jline i believe was introduced by JDR, but now has spread -- 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

12 years, 7 months

5
10
0 / 0

[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

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

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

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

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

12 years, 7 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012