November 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5941) The jboss-as-parent-7.1.2 BOM excludes mandatory transitive dependencies for artifacts and/or has missing artifact types

by Horia Chiorean (JIRA)

Horia Chiorean created AS7-5941: ----------------------------------- Summary: The jboss-as-parent-7.1.2 BOM excludes mandatory transitive dependencies for artifacts and/or has missing artifact types Key: AS7-5941 URL: https://issues.jboss.org/browse/AS7-5941 Project: Application Server 7 Issue Type: Bug Components: Build System Affects Versions: 7.1.2.Final (EAP) Reporter: Horia Chiorean Assignee: Paul Gier Priority: Critical In order for ModeShape 3.1 to be productized, we were asked to update our build system and only use the _jboss-as-parent-7.1.2.Final_ BOM, importing it in our _<dependencyManagement>_ section. While trying to do so, we've identified a couple of blocker issues (from our perspective) with the BOM: *1.* Some of the core artifacts which we need: infinispan and resteasy to name a few, have almost all (if not all) of their mandatory transitive dependencies excluded from the BOM. For example, in the case of _infinispan-core_, the _jboss-marhshalling_ and _jboss-marshalling-river_ dependencies are required for some basic test cases/uses. We don't use these directly in our API, but Infinispan uses them by default in many cases. The only workaround is to redefine these dependencies (in order to avoid the excludes) in our pom(s) which defeats the entire purpose of a BOM. *2.* Since we're based on Infinispan, a lot of our modules use for testing Infinispan's _test-jar_ artifact which isn't present in the BOM. Again, to work around this we're basically having to define a local dependency with a version and the _<type>test-jar<type>_ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
2
0 / 0

[JBoss JIRA] (AS7-4955) JMS Queues created by the Web admin are not durable by default

by Jeff Mesnil (JIRA)

Jeff Mesnil created AS7-4955: -------------------------------- Summary: JMS Queues created by the Web admin are not durable by default Key: AS7-4955 URL: https://issues.jboss.org/browse/AS7-4955 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.2.Final (EAP) Reporter: Jeff Mesnil Assignee: Heiko Braun 1. go to http://localhost:9990/console/App.html#messaging 2. click on "Add" button in Queues or Topic tab => the durable checkbox is not checked while the jms-queue model specifies that a queue is durable by default -- 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, 6 months

3
5
0 / 0

[JBoss JIRA] (JBRULES-3655) Memory leak in stateless session when using CommandFactory.newBatchExecution and jBPM deps are on CP

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3655: ------------------------------------ Summary: Memory leak in stateless session when using CommandFactory.newBatchExecution and jBPM deps are on CP Key: JBRULES-3655 URL: https://issues.jboss.org/browse/JBRULES-3655 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco Using CommandFactory.newInsertElements() together with stateless knowledge session results in memory leak _when_ jBPM dependencies are on classpath. Without jBPM dependencies memory leak is gone. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
9
0 / 0

[JBoss JIRA] (AS7-5953) CLONE - Support Expressions for logging-levels in the logging subsystem

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created AS7-5953: ------------------------------------- Summary: CLONE - Support Expressions for logging-levels in the logging subsystem Key: AS7-5953 URL: https://issues.jboss.org/browse/AS7-5953 Project: Application Server 7 Issue Type: Feature Request Affects Versions: 7.2.0.Alpha1 Reporter: Wolf-Dieter Fink In former version the logging configuration supports expressions. The logger-level and handler-thresholds should be support this in AS7. <console-handler name="CONSOLE"> <level name="${logging.console.threshold:INFO}"/> ... <logger category="com.arjuna"> <level name="${logging.tx.level}"/> </logger> <root-logger> <level name="${logging.root.level}"/> ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-3934) Provide modcluster runtime operation within console

by Heiko Braun (JIRA)

Heiko Braun created AS7-3934: -------------------------------- Summary: Provide modcluster runtime operation within console Key: AS7-3934 URL: https://issues.jboss.org/browse/AS7-3934 Project: Application Server 7 Issue Type: Task Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.2.Final -- 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, 6 months

1
4
0 / 0

[JBoss JIRA] (AS7-5947) EAR deployment may exhaust service threads and fail

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5947: ----------------------------------- Summary: EAR deployment may exhaust service threads and fail Key: AS7-5947 URL: https://issues.jboss.org/browse/AS7-5947 Project: Application Server 7 Issue Type: Bug Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Priority: Critical Fix For: 7.2.0.Alpha1 -Dorg.jboss.server.bootstrap.maxThreads=1 {code} 08:44:59,723 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011002: Bundle started: osgi-ear-test:0.0.0 08:44:59,829 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "osgi-ear-test" 08:44:59,908 INFO [org.jboss.as.repository] (management-handler-thread - 4) JBAS014900: Content added at location /home/tdiesler/git/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/content/3f/c71a8405efa7c357109e2a8627448b851fc9f2/content 08:44:59,912 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "simple.ear" 08:44:59,933 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "simple.war" 08:45:00,251 INFO [org.jboss.web] (MSC service thread 1-1) JBAS018210: Register web context: /simple 08:45:00,479 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS018559: Deployed "simple.ear" 08:45:00,569 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900: Content added at location /home/tdiesler/git/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/content/75/2868c1b3add99cf61f8cc648c666c0f89c90ba/content 08:45:00,571 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "war-structure.ear" 08:45:00,581 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "echo-bundle.jar" 08:45:00,582 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "war-structure-bundle.war" 08:45:00,609 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: echo-bundle.jar:0.0.0 08:45:00,616 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: war-structure-bundle.war:0.0.0 08:45:00,625 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015970: Defer FIRST_MODULE_USE for war-structure.ear making it LAZY 08:45:00,628 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015970: Defer FIRST_MODULE_USE for echo-bundle.jar making it PASSIVE 08:45:02,676 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.module.service."deployment.war-structure.ear.war-structure-bundle.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.war-structure.ear.war-structure-bundle.war".main: JBAS018759: Failed to load module: deployment.war-structure.ear.war-structure-bundle.war:main at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:92) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_33] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_33] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_33] Caused by: org.jboss.modules.ModuleLoadException: JBAS018760: Timeout waiting for module service: deployment.war-structure.ear:main at org.jboss.as.server.moduleservice.ServiceModuleLoader$ModuleSpecLoadListener.getModuleSpec(ServiceModuleLoader.java:133) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.as.server.moduleservice.ServiceModuleLoader.findModule(ServiceModuleLoader.java:174) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222) [jboss-modules.jar:1.1.3.GA] at org.jboss.as.server.moduleservice.ServiceModuleLoader.preloadModule(ServiceModuleLoader.java:158) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] at org.jboss.modules.Module.addPaths(Module.java:851) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.Module.link(Module.java:1206) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.Module.relinkIfNecessary(Module.java:1235) [jboss-modules.jar:1.1.3.GA] at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:208) [jboss-modules.jar:1.1.3.GA] at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:71) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] ... 5 more 08:45:02,802 ERROR [org.jboss.as.server] (management-handler-thread - 2) JBAS015870: Deploy of deployment "war-structure.ear" was rolled back with the following failure message: "JBAS014750: Operation handler failed to complete" {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
7
0 / 0

[JBoss JIRA] (AS7-5950) Streamline :read-resource-description

by Heiko Braun (JIRA)

Heiko Braun created AS7-5950: -------------------------------- Summary: Streamline :read-resource-description Key: AS7-5950 URL: https://issues.jboss.org/browse/AS7-5950 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.2.0.CR1 We have a need for a streamlined read-resource-description operation response. In many cases we only need the attribute descriptions and from those descriptions only a subset of the meta data available. For instance: {noformat} "enable-statistics" => { "type" => BOOLEAN, "description" => "Whether statistics should be enabled.", "expressions-allowed" => true, "nillable" => true, "default" => false, "access-type" => "read-write", "storage" => "configuration", "restart-required" => "all-services" } {noformat} Clients that require information about the structure don't need: - access-type - storage - restart-required In many cases we don't even need - operations - children Would it be possible to further parametrize the read-resource-description operation to allow these distinctions? This would help to reduce the overall payload size when clients communicate with the DC and improve thus improve the overall performance. Not to mention parsing greatly benefits from a streamlined model as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
1
0 / 0

[JBoss JIRA] (AS7-5949) allow custom-formatter configuration

by Aleksandar Kostadinov (JIRA)

Aleksandar Kostadinov created AS7-5949: ------------------------------------------ Summary: allow custom-formatter configuration Key: AS7-5949 URL: https://issues.jboss.org/browse/AS7-5949 Project: Application Server 7 Issue Type: Feature Request Components: Logging Affects Versions: 7.1.3.Final (EAP) Reporter: Aleksandar Kostadinov Assignee: James Perkins Currently only *org.jboss.logmanager.formatters.PatternFormatter* is supported in JBoss AS7 configuration. It would be very useful to allow specifying a custom-formatter (e.g *java.util.logging.XMLFormatter*). At the moment one can specify another formatter in logging.properties but once the logging subsystem is initialized, the settings in logging.properties get overridden. A workaround would be to disable logging subsystem but that has drawbacks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (AS7-5943) StandardConfigsXMLValidationUnitTestCase cannot find jboss-common_6_0.xsd on IBM JDK

by Ivo Studensky (JIRA)

Ivo Studensky created AS7-5943: ---------------------------------- Summary: StandardConfigsXMLValidationUnitTestCase cannot find jboss-common_6_0.xsd on IBM JDK Key: AS7-5943 URL: https://issues.jboss.org/browse/AS7-5943 Project: Application Server 7 Issue Type: Bug Components: Test Suite Affects Versions: 7.1.3.Final (EAP), 7.2.0.Alpha1 Environment: IBM JDK IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr9-20110203_74623 (JIT enabled, AOT enabled) IBM J9 VM (build 2.6, JRE 1.7.0 Linux amd64-64 20120809_118929 (JIT enabled, AOT enabled) Reporter: Ivo Studensky Assignee: Ivo Studensky StandardConfigsXMLValidationUnitTestCase fails on IBM JDK since it cannot find jboss-common_6_0.xsd schema, see the snippet below for more details. The failure is triggered by invocation of StandardConfigsXMLValidationUnitTestCase#DEFAULT_RESOURCE_RESOLVER.resolveResource() method with systemId == 'http://www.jboss.org/j2ee/schema/jboss-common_6_0.xsd' which is missing in a NAMESPACE_MAP field. Furthermore, compared to Oracle JDK the resolveResource method is invoked with different parameters on IBM JDK, i.e. it loads different XSD's into the validation of the same XML files. On Oracle JDK it is never asked for jboss-common systemId. That is weird. {noformat} junit.framework.AssertionFailedError: http://www.jboss.org/j2ee/schema/jboss-common_6_0.xsd not found at junit.framework.Assert.fail(Assert.java:50) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertNotNull(Assert.java:218) at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest.discoverXsd(AbstractValidationUnitTest.java:208) at org.jboss.as.test.smoke.subsystem.xml.AbstractValidationUnitTest$2.resolveResource(AbstractValidationUnitTest.java:124) at org.apache.xerces.util.DOMEntityResolverWrapper.resolveEntity(Unknown Source) at org.apache.xerces.impl.XMLEntityManager.resolveEntity(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaLoader.resolveDocument(Unknown Source) at org.apache.xerces.impl.xs.traversers.XSDHandler.resolveSchema(Unknown Source) at org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown Source) at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaLoader.loadSchema(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(Unknown Source) at org.apache.xerces.jaxp.validation.XMLSchemaFactory.newSchema(Unknown Source) at org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.parseXml(StandardConfigsXMLValidationUnitTestCase.java:150) at org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase.testHostSlave(StandardConfigsXMLValidationUnitTestCase.java:82) {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
7
0 / 0

[JBoss JIRA] (AS7-5758) Safari digest authentication problem

by Heiko Braun (JIRA)

Heiko Braun created AS7-5758: -------------------------------- Summary: Safari digest authentication problem Key: AS7-5758 URL: https://issues.jboss.org/browse/AS7-5758 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.2.0.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
33
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 2012