November 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5954) IIOP tests fail on IBM JDK due to an XSLT error

by Ivo Studensky (JIRA)

Ivo Studensky created AS7-5954: ---------------------------------- Summary: IIOP tests fail on IBM JDK due to an XSLT error Key: AS7-5954 URL: https://issues.jboss.org/browse/AS7-5954 Project: Application Server 7 Issue Type: Bug Components: Test Suite Affects Versions: 7.1.3.Final (EAP), 7.2.0.Alpha1 Environment: IBM JDK 6 IBM JDK 7 Reporter: Ivo Studensky Assignee: Ivo Studensky Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP) IIOP tests from AS testsuite fail when running on IBM JDK due to an XSLT error in the enableJTS.xsl template file. The current template creates an invalid configuration file on IBM JDK which causes that server cannot parse the configuration and fails to start up. Affected tests: {noformat} org.jboss.as.test.iiop.basic.BasicIIOPInvocationTestCase org.jboss.as.test.iiop.transaction.TransactionIIOPInvocationTestCase org.jboss.as.test.integration.ejb.iiop.naming.IIOPNamingTestCase {noformat} I am preparing a pull request with the fix. -- 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

11 years, 12 months

1
3
0 / 0

[JBoss JIRA] (SECURITY-705) DatabaseServerLoginModule has regression for the option transactionManagerJndiName

by Tom Fonteyne (JIRA)

Tom Fonteyne created SECURITY-705: ------------------------------------- Summary: DatabaseServerLoginModule has regression for the option transactionManagerJndiName Key: SECURITY-705 URL: https://issues.jboss.org/browse/SECURITY-705 Project: PicketBox Issue Type: Bug Security Level: Public (Everyone can see) Components: PicketBox Affects Versions: JBossSecurity_2.0.5.Final Reporter: Tom Fonteyne Assignee: Tom Fonteyne Fix For: JBossSecurity_2.0.6.Final line 127: String jname = (String) options.get("TRANSACTION_MANAGER_JNDI_NAME"); should be: String jname = (String) options.get(TRANSACTION_MANAGER_JNDI_NAME); -- 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

11 years, 12 months

1
1
0 / 0

[JBoss JIRA] (AS7-5955) Cannot deploy OSGi fragment as part of an EAR

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5955: ----------------------------------- Summary: Cannot deploy OSGi fragment as part of an EAR Key: AS7-5955 URL: https://issues.jboss.org/browse/AS7-5955 Project: Application Server 7 Issue Type: Bug Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.2.0.Alpha1 {code} 15:16:16,156 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "good-fragment.ear" 15:16:16,167 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "good-bundle.jar" 15:16:16,168 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "good-fragment.jar" 15:16:16,185 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: good-bundle.jar:0.0.0 15:16:16,189 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: good-fragment.jar:0.0.0 15:16:16,197 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015970: Defer FIRST_MODULE_USE for good-fragment.ear making it LAZY 15:16:16,206 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015970: Defer FIRST_MODULE_USE for good-bundle.jar making it PASSIVE 15:16:16,438 ERROR [org.jboss.as.server] (OSGi ModelControllerClient Thread) JBAS015870: Deploy of deployment "good-fragment.ear" was rolled back with the following failure message: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"good-fragment.ear\".FIRST_MODULE_USE is missing [jboss.module.spec.service.\"deployment.good-fragment.ear.good-fragment.jar\".main]"]} {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

11 years, 12 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-693) The attribute 'roleAttributeIsDN' is not in the list of allowed attributes for the LdapExtLoginModule

by Darran Lofthouse (JIRA)

Darran Lofthouse created SECURITY-693: ----------------------------------------- Summary: The attribute 'roleAttributeIsDN' is not in the list of allowed attributes for the LdapExtLoginModule Key: SECURITY-693 URL: https://issues.jboss.org/browse/SECURITY-693 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: PicketBox Affects Versions: PicketBox_4_0_12.Final Reporter: Darran Lofthouse Assignee: Anil Saldhana The following warning is logged as a result of this attribute being missing: - 04:11:16,582 WARN [org.jboss.security] (http-/127.0.0.1:8080-2) PBOX000234: Invalid or misspelled module option: roleAttributeIsDN Probably not a major issue but this warning may lead users to believe their configuration is incorectly wrong when trying to diagnose a problem. -- 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

11 years, 12 months

3
7
0 / 0

[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

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

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

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

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

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

11 years, 12 months

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2012