[JBoss JIRA] Created: (AS7-1996) Unsuccessfull deployment-scanner:add operation changes runtime state
by Dominik Pospisil (JIRA)
Unsuccessfull deployment-scanner:add operation changes runtime state
--------------------------------------------------------------------
Key: AS7-1996
URL: https://issues.jboss.org/browse/AS7-1996
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.0.Alpha1
Reporter: Dominik Pospisil
Assignee: Brian Stansberry
Steps to reproduce:
1) Start standalone server
2) Issue:
/subsystem=deployment-scanner/scanner=testScanner:add(scan-interval=2000,path="/noexisiting")
where /noexisting is some incorrect path
3) Issue:
/subsystem=deployment-scanner/scanner=testScanner:add(scan-interval=2000,path="/tmp/test")
where /tmp/test is a valid path
I think that the expected result would be that the step 2 fails, however this step should not affect runtime nor configuration model.
The result of step 3 should be then a success however it is actually a failure:
08:45:25,421 ERROR [org.jboss.as.controller] (pool-3-thread-8) Operation ("add") failed - address: ([
("subsystem" => "deployment-scanner"),
("scanner" => "testScanner")
]): org.jboss.msc.service.DuplicateServiceException: Service jboss.server.deployment.scanner.testScanner.path is already registered
at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:226) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2211) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[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
12 years, 7 months
[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
12 years, 7 months
[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
12 years, 7 months
[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
12 years, 7 months
[JBoss JIRA] (AS7-2040) AS7 TS: Running sets of tests from the command line
by Ondrej Zizka (Updated) (JIRA)
[ https://issues.jboss.org/browse/AS7-2040?page=com.atlassian.jira.plugin.s... ]
Ondrej Zizka updated AS7-2040:
------------------------------
Description:
Work out a way, using profiles, to run:
* unit tests and all integration tests in one shot (needed by dev)
* run the integration tests separately (needed by QA)
Running combinations of integration tests was achieved with the
$AS7/testsuite/build.{sh,bat} scripts, but I wasn't expecting the
requirement to have to be able to do this from $AS7/build.{sh,bat}
entirely.
{code}
@Test (groups = {"JMS", "XA"})
{code}
or the new style
{code}
@Category( Integration.class )
{code}
See 3.5.1 of https://docspace.corp.redhat.com/docs/DOC-74146
was:
Work out a way, using profiles, to run:
* unit tests and all integration tests in one shot (needed by dev)
* run the integration tests separately (needed by QA)
Running combinations of integration tests was achieved with the
$AS7/testsuite/build.{sh,bat} scripts, but I wasn't expecting the
requirement to have to be able to do this from $AS7/build.{sh,bat}
entirely.
> AS7 TS: Running sets of tests from the command line
> ---------------------------------------------------
>
> Key: AS7-2040
> URL: https://issues.jboss.org/browse/AS7-2040
> Project: Application Server 7
> Issue Type: Task
> Components: Test Suite
> Reporter: Ondrej Zizka
> Assignee: Ondrej Zizka
>
> Work out a way, using profiles, to run:
> * unit tests and all integration tests in one shot (needed by dev)
> * run the integration tests separately (needed by QA)
> Running combinations of integration tests was achieved with the
> $AS7/testsuite/build.{sh,bat} scripts, but I wasn't expecting the
> requirement to have to be able to do this from $AS7/build.{sh,bat}
> entirely.
> {code}
> @Test (groups = {"JMS", "XA"})
> {code}
> or the new style
> {code}
> @Category( Integration.class )
> {code}
> See 3.5.1 of https://docspace.corp.redhat.com/docs/DOC-74146
--
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