[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
14 years, 9 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
14 years, 9 months
[JBoss JIRA] Created: (JGRP-1371) Unable to suspend self in FLUSH.blockMessageDuringFlush(); Eternal timeouts not supported
by Nicolas Estrada (JIRA)
Unable to suspend self in FLUSH.blockMessageDuringFlush(); Eternal timeouts not supported
-----------------------------------------------------------------------------------------
Key: JGRP-1371
URL: https://issues.jboss.org/browse/JGRP-1371
Project: JGroups
Issue Type: Bug
Affects Versions: 2.12.1
Environment: All
Reporter: Nicolas Estrada
Assignee: Bela Ban
Priority: Critical
If a positive timeout is specified for the FLUSH protocol, if the specified waiting time timeout elapses during the notBlockedDown.await(timeout) invocation, the shouldSuspendByItself flag will be set but it will continue looping forever. The if clause below should be moved into the while block.
If the timeout is 0L or negative, instead of waiting forever, it will instantaneously return from the await(timeout) method, but seeing as it can never suspend itself as mentioned earlier, it will loop forever until a STOP_FLUSH or ABORT_FLUSH event is received.
Changing the method to await() for "eternal" timeouts may be dangerous however; There must be a guarantee that the isBlockingFlushDown is toggled even if the FLUSH coordinator fails.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months