October 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1264) Add schema references to standalone.xml, domain.xml, host.xml

by Gerry Matte (JIRA)

Add schema references to standalone.xml, domain.xml, host.xml ------------------------------------------------------------- Key: AS7-1264 URL: https://issues.jboss.org/browse/AS7-1264 Project: Application Server 7 Issue Type: Task Components: Domain Management Affects Versions: 7.0.0.CR1 Reporter: Gerry Matte Assignee: Brian Stansberry It appears that users of Jboss 7 will be often modifying these configuration files as they fine tune their server and when they discover how to implement new features. It seems quite surprising to me that these files do not have the schema references identified in the file header. Any good XML editor would use those references to validate changes and new entries and thereby avoid a great deal of frustration for users and those who provide support for forum issues. I realise that if jboss validated each xml file when starting up there would be performance penalty that may be unacceptable to many users. A command-line switch could be used to either turn on xml validation (if the default were that no validation is performed) or conversely to turn off xml validation if the default state was that xml validation was on. Personally I favor having a switch that turns off validation - to be used on production servers only. If the schema/dtd files were published online and referenced within the configuration xml files, future changes to the schema structure would be "enforced" upon the user community as they attemted to use an out-of-date version when upgrading to a new version of Jboss 7. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

7
13
0 / 0

[JBoss JIRA] (AS7-3713) JBoss Web module.xml declares clustering sso as optional, when it is instead required

by Tristan Tarrant (JIRA)

Tristan Tarrant created AS7-3713: ------------------------------------ Summary: JBoss Web module.xml declares clustering sso as optional, when it is instead required Key: AS7-3713 URL: https://issues.jboss.org/browse/AS7-3713 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.1.0.Final Reporter: Tristan Tarrant Assignee: Remy Maucherat org/jboss/as/web/main/module.xml contains <module name="org.jboss.as.clustering.web.spi" optional="true"/>, but the clustering classes are imported directly by WebVirtualHostAdd.java, so the optional is kind of required :) -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (AS7-1547) Problem starting jboss 7 with Java Service Wrapper

by andrei povodyrev (JIRA)

Problem starting jboss 7 with Java Service Wrapper -------------------------------------------------- Key: AS7-1547 URL: https://issues.jboss.org/browse/AS7-1547 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.0.0.Final Environment: Red Hat, Windows 7 Reporter: andrei povodyrev Assignee: David Lloyd Fix For: Open To Community Problem starting jboss 7 with Java Service Wrapper We tried to upgrade Java Service Wrapper (JSW) configuration from Jboss 5 to Jboss 7. Jboss fails to start with these messages WARNING: Failed to load the specified logmodule org.jboss.logmanager:main followed by IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager") Software: Jboss-as-7.0.0-Final wrapper-windows-x86-64-3.5.10-st (Java Service Wrapper win 64 distribution) Issue: org.jboss.modules.Main generates the warning as LogManager is already initialized to java.util.logging.LogManager by the Wrapper. With jboss 7 org.jboss.logmanager.LogManager is required. Per LogManager design only one instance may exist in jvm. jboss 7 assume that it is the first in line to initialize java.util.logger.LogManager. Wrapper is the one who inits LogManager first (thus triggering primordial configuration initialization). Jboss then fails to start since it requiresits own logging implementation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

5
5
0 / 0

[JBoss JIRA] (AS7-5788) HttpService authentication/authorisation

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5788: ----------------------------------- Summary: HttpService authentication/authorisation Key: AS7-5788 URL: https://issues.jboss.org/browse/AS7-5788 Project: Application Server 7 Issue Type: Sub-task Components: OSGi, Web Reporter: Thomas Diesler Assignee: David Bosschaert 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, 5 months

2
1
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

13 years, 5 months

3
7
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, 5 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, 5 months

2
9
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, 5 months

1
4
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, 5 months

4
33
0 / 0

[JBoss JIRA] (AS7-2213) Provide an operation to retrieve the last 10 errors form the log

by Heiko Braun (Created) (JIRA)

Provide an operation to retrieve the last 10 errors form the log ---------------------------------------------------------------- Key: AS7-2213 URL: https://issues.jboss.org/browse/AS7-2213 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.1.0.CR1 -- 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, 5 months

8
31
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 October 2012