September 2011 - jboss-jira - Jboss List Archives

[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

13 years, 1 month

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

13 years, 1 month

6
5
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

13 years, 1 month

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

13 years, 1 month

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

13 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (AS7-1421) Modcluster subsystem has broken :read-resource-description

by Heiko Rupp (JIRA)

Modcluster subsystem has broken :read-resource-description ---------------------------------------------------------- Key: AS7-1421 URL: https://issues.jboss.org/browse/AS7-1421 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.0.0.Final Reporter: Heiko Rupp Assignee: Brian Stansberry [domain@localhost:9999 subsystem=modcluster] :read-resource-description { "outcome" => "success", "result" => { "description" => "The configuration of the modcluster subsystem.", "head-comment-allowed" => true, "tail-comment-allowed" => true, "namespace" => "urn:jboss:domain:modcluster:1.0", "attributes" => {"mod-cluster-config" => { "type" => OBJECT, "description" => "The common modcluster configuration.", "required" => false, "access-type" => "read-only", "storage" => "configuration" }} } } is not usable at all to use for management operations. Also attributes of mod-cluster-config should directly live in 'attributes'. There is no point in adding one more level here. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (AS7-1638) Exception after reloading in CLI

by Nicklas Karlsson (JIRA)

Exception after reloading in CLI -------------------------------- Key: AS7-1638 URL: https://issues.jboss.org/browse/AS7-1638 Project: Application Server 7 Issue Type: Bug Components: JCA, JMS Affects Versions: 7.1.0.Alpha1 Reporter: Nicklas Karlsson Assignee: Jesper Pedersen Running a CLI batch batch /subsystem=datasources/jdbc-driver=oracle:add(driver-name="oracle",driver-module-name="com.oracle.db") /subsystem=datasources/data-source=...:add.. /socket-binding-group=standard-sockets/socket-binding=http:write-attribute(name="port", value="80") /subsystem=deployment-scanner/scanner=default:write-attribute(name="auto-deploy-exploded", value="true") :reload run-batch gives a 08:52:55,533 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-8) trying to deploy queue jms.topic.testTopic 08:52:55,544 INFO [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) Registered connection factory java:/JmsXA 08:52:55,545 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.raactivator: org.jboss.msc.service.StartException in service jboss.raactivator: Failed to activate resource adapter hornetq-ra at org.jboss.as.connector.services.ResourceAdapterActivatorService.start(ResourceAdapterActivatorService.java:98) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765) at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.7.0] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.7.0] at java.lang.Thread.run(Thread.java:722) [:1.7.0] Caused by: org.jboss.jca.deployers.common.DeployException: IJ020056: Deployment failed: file://RaActivatorhornetq-ra at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:1929) at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:825) at org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator.doDeploy(ResourceAdapterActivatorService.java:140) at org.jboss.as.connector.services.ResourceAdapterActivatorService.start(ResourceAdapterActivatorService.java:93) ... 5 more Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.connector.connection-factory.java:/JmsXA is already registered at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154) at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:226) at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560) at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307) at org.jboss.as.connector.metadata.deployment.AbstractResourceAdapterDeploymentService$AbstractAS7RaDeployer.bindConnectionFactory(AbstractResourceAdapterDeploymentService.java:228) at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:1714) ... 8 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

4
5
0 / 0

[JBoss JIRA] Created: (JBRULES-3131) timer( cron: ...) causes ArrayStoreException with slightly erroneous (?) argument

by Wolfgang Laun (JIRA)

timer( cron: ...) causes ArrayStoreException with slightly erroneous (?) argument --------------------------------------------------------------------------------- Key: JBRULES-3131 URL: https://issues.jboss.org/browse/JBRULES-3131 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.2.0.Final Reporter: Wolfgang Laun Assignee: Mark Proctor Fix For: 5.2.1.Final rule xxx timer( cron: 0/30 * * * * * ) when then end Exception in thread "main" java.lang.ArrayStoreException at java.lang.System.arraycopy(Native Method) at java.util.ArrayList.toArray(ArrayList.java:306) at org.drools.compiler.PackageBuilder.getErrors(PackageBuilder.java:1274) at org.drools.builder.impl.KnowledgeBuilderImpl.getErrors(KnowledgeBuilderImpl.java:70) It would be a Good Thing if timer( cron: ) were documented. It deviates from UNIX crontab in at least two aspects. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

4
3
0 / 0

[JBoss JIRA] Created: (JBRULES-3132) Simple syntax error timer(int 10) causes RuntimeDroolsException in RuleBuilder

by Wolfgang Laun (JIRA)

Simple syntax error timer(int 10) causes RuntimeDroolsException in RuleBuilder ------------------------------------------------------------------------------- Key: JBRULES-3132 URL: https://issues.jboss.org/browse/JBRULES-3132 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.2.0.Final Reporter: Wolfgang Laun Assignee: Mark Proctor Fix For: 5.2.1.Final rule xxx timer(int 10 ) # not the missing colon when then System.out.println( "CRONTAB" ); end causes: Exception in thread "main" org.drools.RuntimeDroolsException: Error parsing time string: [ int ] at org.drools.time.TimeUtils.parseTimeString(TimeUtils.java:127) at org.drools.rule.builder.RuleBuilder.buildTimer(RuleBuilder.java:320) at org.drools.rule.builder.RuleBuilder.buildAttributes(RuleBuilder.java:139) at org.drools.rule.builder.RuleBuilder.build(RuleBuilder.java:92) at org.drools.compiler.PackageBuilder.addRule(PackageBuilder.java:1889) at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:755) at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:365) at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:543) at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:28) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

4
3
0 / 0

[JBoss JIRA] Created: (AS7-703) Display server VM metrics in console

by Heiko Braun (JIRA)

Display server VM metrics in console ------------------------------------ Key: AS7-703 URL: https://issues.jboss.org/browse/AS7-703 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2011