October 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2056) EJB jndi bindings don't take into account the overridden application-name in application.xml

by jaikiran pai (Created) (JIRA)

EJB jndi bindings don't take into account the overridden application-name in application.xml -------------------------------------------------------------------------------------------- Key: AS7-2056 URL: https://issues.jboss.org/browse/AS7-2056 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.0.2.Final Reporter: jaikiran pai Assignee: jaikiran pai If a .ear deployment contains a application.xml with a overridden application-name, then that name isn't taken into account while binding the EJBs to JNDI. See the referenced forum thread for details. -- 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
0
0 / 0

[JBoss JIRA] Created: (AS7-787) Create a dummy InitialDirContext to allow for testing.

by Darran Lofthouse (JIRA)

Create a dummy InitialDirContext to allow for testing. ------------------------------------------------------ Key: AS7-787 URL: https://issues.jboss.org/browse/AS7-787 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.0.0.CR1 The testing of any LDAP configuration brings in the dependency on an LDAP server, this is fine for major QA testing but not so fine for the testsuite run in multiple environments. This task is to either find an existing implementation we can use or to implement a dummy InitialDirContext that can simulate the connection to LDAP allowing testing of the LDAP code. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
5
0 / 0

[JBoss JIRA] (AS7-2004) A catastrofic failure in "Controller Boot Thread" leaves process running

by Carlo de Wolf (Created) (JIRA)

A catastrofic failure in "Controller Boot Thread" leaves process running ------------------------------------------------------------------------ Key: AS7-2004 URL: https://issues.jboss.org/browse/AS7-2004 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.0.2.Final Reporter: Carlo de Wolf Assignee: Jason Greene Fix For: 7.1.0.CR1 {noformat} $ ./standalone.sh ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /home/carlo/work/jboss-as/build/target/jboss-as-7.1.0.Alpha2-SNAPSHOT JAVA: /opt/sun/jdk1.6.0_23/bin/java JAVA_OPTS: -server -Xms256m -Xmx1024m -XX:MaxPermSize=512m -Xss1m -XX:+HeapDumpOnOutOfMemoryError -XX:-UseGCOverheadLimit -Dtest.ejb.stateful.timeout.wait.seconds=70 -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true ========================================================================= 10:07:00,288 INFO [org.jboss.modules] JBoss Modules version 1.0.2.GA 10:07:00,660 INFO [org.jboss.msc] JBoss MSC version 1.0.1.GA 10:07:00,750 INFO [org.jboss.as] JBoss AS 7.1.0.Alpha2-SNAPSHOT "Ahoy!" starting 10:07:01,120 ERROR [stderr] Exception in thread "Controller Boot Thread" java.lang.RuntimeException: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to parse configuration 10:07:01,120 ERROR [stderr] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:89) 10:07:01,121 ERROR [stderr] at java.lang.Thread.run(Thread.java:662) 10:07:01,121 ERROR [stderr] Caused by: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to parse configuration 10:07:01,121 ERROR [stderr] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:125) 10:07:01,122 ERROR [stderr] at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:104) 10:07:01,123 ERROR [stderr] at org.jboss.as.server.ServerService.boot(ServerService.java:195) 10:07:01,123 ERROR [stderr] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:83) 10:07:01,123 ERROR [stderr] ... 1 more 10:07:01,124 ERROR [stderr] Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[4,4] 10:07:01,124 ERROR [stderr] Message: Unexpected element '{urn:jboss:domain:1.1}bogus' encountered 10:07:01,124 ERROR [stderr] at org.jboss.as.controller.parsing.ParseUtils.unexpectedElement(ParseUtils.java:83) 10:07:01,124 ERROR [stderr] at org.jboss.as.controller.parsing.StandaloneXml.readServerElement_1_1(StandaloneXml.java:318) 10:07:01,125 ERROR [stderr] at org.jboss.as.controller.parsing.StandaloneXml.readElement(StandaloneXml.java:105) 10:07:01,125 ERROR [stderr] at org.jboss.as.controller.parsing.StandaloneXml.readElement(StandaloneXml.java:84) 10:07:01,125 ERROR [stderr] at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:100) 10:07:01,126 ERROR [stderr] at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:59) 10:07:01,126 ERROR [stderr] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:117) 10:07:01,126 ERROR [stderr] ... 4 more {noformat} -- 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-2041) read-children-resources with include-runtime is broken

by David Bosschaert (Created) (JIRA)

read-children-resources with include-runtime is broken ------------------------------------------------------ Key: AS7-2041 URL: https://issues.jboss.org/browse/AS7-2041 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.0.Alpha1 Reporter: David Bosschaert When adding the include-runtime attribute to :read-children-resources the result is always undefined. When, in the CLI I do: {code} subsystem=osgi] :read-children-resources(child-type=capability,include-runtime=true) { "outcome" => "success", "result" => { "javaee.api" => undefined, "org.apache.aries.jmx" => undefined, "org.apache.aries.util" => undefined, "org.apache.felix.configadmin" => undefined, "org.apache.felix.eventadmin" => undefined, "org.apache.felix.log" => undefined, ... {code} In the above example, if I remove 'include-runtime' things do work normally. I need include-runtime to properly work for the GUI side of subsystem=osgi/bundle=* since all of the attributes of that resources are runtime only ones. -- 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

4
3
0 / 0

[JBoss JIRA] (JBRULES-3236) Add completion support for ruleflow-group name

by Jérémie Lagarde (Created) (JIRA)

Add completion support for ruleflow-group name ---------------------------------------------- Key: JBRULES-3236 URL: https://issues.jboss.org/browse/JBRULES-3236 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-eclipse Reporter: Jérémie Lagarde Assignee: Mark Proctor It would be interesting to list group names and complete the entry with ctrl+space.after ruleflow-group declaration. -- 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
3
0 / 0

[JBoss JIRA] Created: (AS7-1716) SecuritySubsystemParser writes out 1.1 version of schema even if a 1.0 version was originally parsed

by Kabir Khan (JIRA)

SecuritySubsystemParser writes out 1.1 version of schema even if a 1.0 version was originally parsed ---------------------------------------------------------------------------------------------------- Key: AS7-1716 URL: https://issues.jboss.org/browse/AS7-1716 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.1.Final Reporter: Kabir Khan Assignee: Darran Lofthouse Fix For: 7.0.2.Final When parsing the config the parser should probably keep track of the version that was used, and then use that instead of Namespace.CURRENT in writeContent() -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

6
5
0 / 0

[JBoss JIRA] (AS7-2051) JMX subsystem parser should write out using last version of the schema

by Kabir Khan (Created) (JIRA)

JMX subsystem parser should write out using last version of the schema ---------------------------------------------------------------------- Key: AS7-2051 URL: https://issues.jboss.org/browse/AS7-2051 Project: Application Server 7 Issue Type: Feature Request Components: JMX Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 7.1.0.Beta1 See comments in https://issues.jboss.org/browse/AS7-1716 -- 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
0
0 / 0

[JBoss JIRA] Created: (AS7-1114) Create some test fot singleton @DependsOn

by Stuart Douglas (JIRA)

Create some test fot singleton @DependsOn ----------------------------------------- Key: AS7-1114 URL: https://issues.jboss.org/browse/AS7-1114 Project: Application Server 7 Issue Type: Enhancement Affects Versions: 7.0.0.Beta3 Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1352) JCA thread pools must be blocking

by Jesper Pedersen (JIRA)

JCA thread pools must be blocking --------------------------------- Key: AS7-1352 URL: https://issues.jboss.org/browse/AS7-1352 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.0.0.Final Reporter: Jesper Pedersen Assignee: Jeff Zhang Fix For: 7.1.0.Alpha1 The "blocking" attribute for the JCA thread pools should be ignored as it should always be true. In order to align with other subsystems we will just ignore any value set by the user, and hard code to true. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
5
0 / 0

[JBoss JIRA] Created: (AS7-1853) Add descriptions to EE subsystem

by Kabir Khan (JIRA)

Add descriptions to EE subsystem -------------------------------- Key: AS7-1853 URL: https://issues.jboss.org/browse/AS7-1853 Project: Application Server 7 Issue Type: Feature Request Components: EE Reporter: Kabir Khan Assignee: David Lloyd Fix For: 7.0.2.Final, 7.1.0.Alpha1 The description providers are valid but the resource bundle contains empty strings: ee=The configuration of the EE subsystem. ee.add=Adds the EE subsystem. ee.remove=Removes the EE subsystem. ee.global-modules= ee.global-module.name= ee.global-module.slot= ee.ear-subdeployments-isolated= -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2011