[JBoss JIRA] (WFLY-3435) jboss-as-infinispan_1_X.xsd schema has incorrect default value for flush-lock-timeout in write-behind
by Radoslav Husar (JIRA)
Radoslav Husar created WFLY-3435:
------------------------------------
Summary: jboss-as-infinispan_1_X.xsd schema has incorrect default value for flush-lock-timeout in write-behind
Key: WFLY-3435
URL: https://issues.jboss.org/browse/WFLY-3435
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: 8.0.0.Final
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Fix For: 8.2.0.CR1, 9.0.0.Alpha1
Description of problem:
In org.infinispan.loaders.decorators.AsyncStoreConfig, the default flushLockTimeout is set to 5000. However, the default in the JBoss Infinispan schema ($JBOSS_HOME/docs/schema/jboss-as-infinispan_1_X.xsd) is set to 1. Because of this, if the thread-pool-size for write-behind is increased, then it is likely that one of the threads will not be able to obtain the state map lock within the 1 millisecond time provided by the schema default. This results in the following error:
ERROR o.i.loaders.decorators.AsyncStore.run - ISPN000051: Unexpected error
org.infinispan.CacheException: Unable to acquire lock on update map
at org.infinispan.loaders.decorators.AsyncStore.acquireLock(AsyncStore.java:293) ~[infinispan-core-5.1.3.FINAL.jar:5.1.3.FINAL]
at org.infinispan.loaders.decorators.AsyncStore.access$900(AsyncStore.java:86) ~[infinispan-core-5.1.3.FINAL.jar:5.1.3.FINAL]
at org.infinispan.loaders.decorators.AsyncStore$AsyncProcessor.innerRun(AsyncStore.java:336) ~[infinispan-core-5.1.3.FINAL.jar:5.1.3.FINAL]
at org.infinispan.loaders.decorators.AsyncStore$AsyncProcessor.run(AsyncStore.java:312) ~[infinispan-core-5.1.3.FINAL.jar:5.1.3.FINAL]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) ~[na:1.6.0_31]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) ~[na:1.6.0_31]
at java.lang.Thread.run(Thread.java:662) ~[na:1.6.0_31]
Version-Release number of selected component (if applicable):
Infinispan version 5.1.8
How reproducible:
Code inspection
Steps to Reproduce:
1. Check the default value for flush-lock-timeout in $JBOSS_HOME/docs/schema/jboss-as-infinispan_1_3.xsd
2. Check the default value for flushLockTimeout in the org.infinispan.loaders.decorators.AsyncStoreConfig class
3. Note the disparity
Actual results:
Default in schema is 1
Expected results:
Default in schema is 5000
Additional info:
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
12 years, 1 month
[JBoss JIRA] (DROOLS-472) Drools Eclipse plugin can't recognize third party classes
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-472?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated DROOLS-472:
-------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1104095
> Drools Eclipse plugin can't recognize third party classes
> ---------------------------------------------------------
>
> Key: DROOLS-472
> URL: https://issues.jboss.org/browse/DROOLS-472
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: * OS: Mac OS X 10.9.2
> * Eclipse Kepler
> * Drool Eclipse Plugin - JBoss Drools Core 6.0.1Final. (I don't have problem with Drools Core 5.6.0Final)
> * Java SE 1.7
> * Drools Runtime 6.0.1
> Reporter: Jinghai Rao
> Assignee: Mario Fusco
> Fix For: 6.1.0.CR1
>
>
> Whenever I use classes from any third party jar files (not in JRE System Library and Drools Library), I got error messages in Eclipse IDE.
> At the place where I import the class, the error message is "Only a type can be imported. ... resolves to a package".
> At the place where I use the class, the error message is "... cannot be resolved to a type".
> However, I have included the jar file in classpath. The project can also be executed successfully even with the error message in IDE.
> Below is my development environment:
> * OS: Mac OS X 10.9.2
> * Eclipse Kepler
> * Drool Eclipse Plugin - JBoss Drools Core 6.0.1Final. (I don't have problem with Drools Core 5.6.0Final)
> * Java SE 1.7
> * Drools Runtime 6.0.1
> !https://lh5.googleusercontent.com/-gltHnzUIUg4/U1qbEzVd_LI/AAAAAAAAEYw/mKxE2jv-VVc/w1796-h1168-no/Screen+Shot+2014-04-25+at+10.20.36+AM.png!
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
12 years, 1 month
[JBoss JIRA] (DROOLS-472) Drools Eclipse plugin can't recognize third party classes
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-472?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on DROOLS-472:
------------------------------------------------
Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1104095|https://bugzilla.redhat.com/show_bug.cgi?id=1104095] from NEW to ASSIGNED
> Drools Eclipse plugin can't recognize third party classes
> ---------------------------------------------------------
>
> Key: DROOLS-472
> URL: https://issues.jboss.org/browse/DROOLS-472
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: * OS: Mac OS X 10.9.2
> * Eclipse Kepler
> * Drool Eclipse Plugin - JBoss Drools Core 6.0.1Final. (I don't have problem with Drools Core 5.6.0Final)
> * Java SE 1.7
> * Drools Runtime 6.0.1
> Reporter: Jinghai Rao
> Assignee: Mario Fusco
> Fix For: 6.1.0.CR1
>
>
> Whenever I use classes from any third party jar files (not in JRE System Library and Drools Library), I got error messages in Eclipse IDE.
> At the place where I import the class, the error message is "Only a type can be imported. ... resolves to a package".
> At the place where I use the class, the error message is "... cannot be resolved to a type".
> However, I have included the jar file in classpath. The project can also be executed successfully even with the error message in IDE.
> Below is my development environment:
> * OS: Mac OS X 10.9.2
> * Eclipse Kepler
> * Drool Eclipse Plugin - JBoss Drools Core 6.0.1Final. (I don't have problem with Drools Core 5.6.0Final)
> * Java SE 1.7
> * Drools Runtime 6.0.1
> !https://lh5.googleusercontent.com/-gltHnzUIUg4/U1qbEzVd_LI/AAAAAAAAEYw/mKxE2jv-VVc/w1796-h1168-no/Screen+Shot+2014-04-25+at+10.20.36+AM.png!
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
12 years, 1 month
[JBoss JIRA] (WFLY-3205) For xa-datasource testConnection should account for deployment classloader
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3205?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3205:
-----------------------------------------------
Jay SenSharma <jsenshar(a)redhat.com> changed the Status of [bug 1083457|https://bugzilla.redhat.com/show_bug.cgi?id=1083457] from NEW to POST
> For xa-datasource testConnection should account for deployment classloader
> --------------------------------------------------------------------------
>
> Key: WFLY-3205
> URL: https://issues.jboss.org/browse/WFLY-3205
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JCA
> Affects Versions: 8.1.0.CR1
> Environment: All
> Reporter: Jay Kumar SenSharma
> Assignee: Stefano Maestri
>
> - The fix mentioned in https://issues.jboss.org/browse/WFLY-2047 is resolves the issue for plain Non-XA dataSources. However if an XA-DataSource is configured with the "ldap" based database connection URL then it fails with the following Error:
> {code}
> 13:49:41,399 ERROR [org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl] (Periodic Recovery) IJ000906: Error during crash recovery: java:/OracleXA_DS (Could not create connection): javax.resource.ResourceException: Could not create connection
> at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:461)
> at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.createManagedConnection(XAManagedConnectionFactory.java:398)
> at org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl.open(XAResourceRecoveryImpl.java:343)
> at org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl.getXAResources(XAResourceRecoveryImpl.java:170)
> at com.arjuna.ats.internal.jbossatx.jta.XAResourceRecoveryHelperWrapper.getXAResources(XAResourceRecoveryHelperWrapper.java:51) [narayana-jts-integration-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)]
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.resourceInitiatedRecoveryForRecoveryHelpers(XARecoveryModule.java:516) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)]
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:182) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)]
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:743) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)]
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)]
> Caused by: java.sql.SQLRecoverableException: Io exception: JNDI Package failurejavax.naming.NamingException: JBAS011843: Failed instantiate InitialContextFactory com.sun.jndi.ldap.LdapCtxFactory from classloader ModuleClassLoader for Module "org.jboss.jts:main" from local module loader @3b70c (finder: local module finder @1e6a820 (roots: /home/userone/XA_DS/wildfly-8.0.1.Final-SNAPSHOT/modules,/home/userone/XA_DS/wildfly-8.0.1.Final-SNAPSHOT/modules/system/layers/base)) [Root exception is java.lang.ClassNotFoundException: com.sun.jndi.ldap.LdapCtxFactory from [Module "org.jboss.jts:main" from local module loader @3b70c (finder: local module finder @1e6a820 (roots: /home/userone/XA_DS/wildfly-8.0.1.Final-SNAPSHOT/modules,/home/userone/XA_DS/wildfly-8.0.1.Final-SNAPSHOT/modules/system/layers/base))]]
> at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:101)
> at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:112)
> at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:173)
> at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:229)
> at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:458)
> at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:411)
> at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:490)
> at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:202)
> at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:33)
> at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:474)
> at oracle.jdbc.pool.OracleDataSource.getPhysicalConnection(OracleDataSource.java:275)
> at oracle.jdbc.xa.client.OracleXADataSource.getPooledConnection(OracleXADataSource.java:454)
> at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:159)
> at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:130)
> at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:444)
> ... 8 morec
> {code}
> - The XA dataSource configuration looks like following:
> {code}
> <subsystem xmlns="urn:jboss:domain:datasources:2.0">
> <datasources>
> <xa-datasource jndi-name="java:/OracleXA_DS" pool-name="OracleXA_DS" enabled="true">
> <xa-datasource-property name="ServerName">
> example.com
> </xa-datasource-property>
> <xa-datasource-property name="DatabaseName">
> TestDB
> </xa-datasource-property>
> <xa-datasource-property name="URL">
> jdbc:oracle:thin:@ldap://example.com:3060/test,cn=OracleA,dc=worldA
> </xa-datasource-property>
> <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
> <driver>oracle</driver>
> <security>
> <user-name>jboss</user-name>
> <password>jboss</password>
> </security>
> </xa-datasource>
> <drivers>
> <driver name="oracle" module="com.oracle.jdbc6"/>
> </drivers>
> </datasources>
> </subsystem>
> {code}
> - When the above datasource is tested via CLI like following then aht above mentioned error is noticed:
> {code}
> /subsystem=datasources/xa-data-source=OracleXA_DS:test-connection-in-pool
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
12 years, 1 month
[JBoss JIRA] (DROOLS-472) Drools Eclipse plugin can't recognize third party classes
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-472?page=com.atlassian.jira.plugin... ]
Mario Fusco resolved DROOLS-472.
--------------------------------
Fix Version/s: 6.1.0.CR1
Resolution: Done
> Drools Eclipse plugin can't recognize third party classes
> ---------------------------------------------------------
>
> Key: DROOLS-472
> URL: https://issues.jboss.org/browse/DROOLS-472
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: * OS: Mac OS X 10.9.2
> * Eclipse Kepler
> * Drool Eclipse Plugin - JBoss Drools Core 6.0.1Final. (I don't have problem with Drools Core 5.6.0Final)
> * Java SE 1.7
> * Drools Runtime 6.0.1
> Reporter: Jinghai Rao
> Assignee: Mario Fusco
> Fix For: 6.1.0.CR1
>
>
> Whenever I use classes from any third party jar files (not in JRE System Library and Drools Library), I got error messages in Eclipse IDE.
> At the place where I import the class, the error message is "Only a type can be imported. ... resolves to a package".
> At the place where I use the class, the error message is "... cannot be resolved to a type".
> However, I have included the jar file in classpath. The project can also be executed successfully even with the error message in IDE.
> Below is my development environment:
> * OS: Mac OS X 10.9.2
> * Eclipse Kepler
> * Drool Eclipse Plugin - JBoss Drools Core 6.0.1Final. (I don't have problem with Drools Core 5.6.0Final)
> * Java SE 1.7
> * Drools Runtime 6.0.1
> !https://lh5.googleusercontent.com/-gltHnzUIUg4/U1qbEzVd_LI/AAAAAAAAEYw/mKxE2jv-VVc/w1796-h1168-no/Screen+Shot+2014-04-25+at+10.20.36+AM.png!
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
12 years, 1 month
[JBoss JIRA] (WFLY-2261) standalone.sh --debug without port number not working
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2261?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2261:
-----------------------------------------------
Emmanuel Hugonnet (ehsavoie) <ehugonne(a)redhat.com> changed the Status of [bug 1072227|https://bugzilla.redhat.com/show_bug.cgi?id=1072227] from ASSIGNED to MODIFIED
> standalone.sh --debug without port number not working
> ------------------------------------------------------
>
> Key: WFLY-2261
> URL: https://issues.jboss.org/browse/WFLY-2261
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Scripts
> Affects Versions: 8.0.0.Beta1
> Reporter: Cheng Fang
> Assignee: Jeff Mesnil
> Fix For: 8.1.0.CR1, 8.1.0.Final
>
>
> ./standalone.sh --debug port-num works, but it failed when omitting port number.
> sh -x standalone.sh --debug (expecting the default port 8787 to be used)
> {noformat}
> + eval '"/Library/Java/JavaVirtualMachines/jdk1.7.0_40.jdk/Contents/Home/bin/java"' '-D"[Standalone]"' -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n '"-Dorg.jboss.boot.log.file=/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/standalone/log/server.log"' '"-Dlogging.configuration=file:/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/standalone/configuration/logging.properties"' -jar '"/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/jboss-modules.jar"' -mp '"/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/modules"' org.jboss.as.standalone '-Djboss.home.dir="/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT"' '-Djboss.server.base.dir="/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/standalone"' ' ""'
> ++ /Library/Java/JavaVirtualMachines/jdk1.7.0_40.jdk/Contents/Home/bin/java '-D[Standalone]' -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n -Dorg.jboss.boot.log.file=/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/standalone/log/server.log -Dlogging.configuration=file:/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/standalone/configuration/logging.properties -jar /Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/jboss-modules.jar -mp /Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/modules org.jboss.as.standalone -Djboss.home.dir=/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT -Djboss.server.base.dir=/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/standalone ''
> Listening for transport dt_socket at address: 8787
> 12:19:36,715 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final
> 12:19:36,886 ERROR [stderr] (main) JBAS015801: Invalid option ''
> 12:19:36,893 INFO [stdout] (main)
> 12:19:36,893 INFO [stdout] (main) Usage: standalone.sh [args...]
> {noformat}
> sh -x standalone.sh --debug 8787 (the working command)
> {noformat}
> + eval '"/Library/Java/JavaVirtualMachines/jdk1.7.0_40.jdk/Contents/Home/bin/java"' '-D"[Standalone]"' -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n '"-Dorg.jboss.boot.log.file=/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/standalone/log/server.log"' '"-Dlogging.configuration=file:/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/standalone/configuration/logging.properties"' -jar '"/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/jboss-modules.jar"' -mp '"/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/modules"' org.jboss.as.standalone '-Djboss.home.dir="/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT"' '-Djboss.server.base.dir="/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/standalone"' ''
> ++ /Library/Java/JavaVirtualMachines/jdk1.7.0_40.jdk/Contents/Home/bin/java '-D[Standalone]' -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n -Dorg.jboss.boot.log.file=/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/standalone/log/server.log -Dlogging.configuration=file:/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/standalone/configuration/logging.properties -jar /Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/jboss-modules.jar -mp /Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/modules org.jboss.as.standalone -Djboss.home.dir=/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT -Djboss.server.base.dir=/Users/cfang/dev/wildfly/build/target/wildfly-8.0.0.Beta2-SNAPSHOT/standalone
> Listening for transport dt_socket at address: 8787
> 12:20:39,251 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final
> 12:20:39,626 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.0.Beta2
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
12 years, 1 month
[JBoss JIRA] (DROOLS-501) Propagation context is not set correctly when nodes are shared
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-501?page=com.atlassian.jira.plugin... ]
Mario Fusco resolved DROOLS-501.
--------------------------------
Resolution: Done
> Propagation context is not set correctly when nodes are shared
> --------------------------------------------------------------
>
> Key: DROOLS-501
> URL: https://issues.jboss.org/browse/DROOLS-501
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 6.1.0.Beta4
> Reporter: Davide Sottara
> Assignee: Mario Fusco
> Priority: Critical
> Fix For: 6.1.0.CR1
>
>
> The following rules
> {code}
> package org.drools.compiler.loop
> rule "Rule 1"
> ruleflow-group "Start"
> no-loop
> when
> $thing1 : String()
> $thing2 : Integer()
> then
> System.out.println( 'At 1' );
> update( $thing2 );
> end
> rule "Rule 2"
> ruleflow-group "End"
> no-loop
> when
> $thing1 : String()
> $thing2 : Integer()
> then
> System.out.println( 'At 2' );
> update( $thing2 );
> end
> {code}
> cause an endless loop even if controlled by a jBPM process with two rule tasks
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
12 years, 1 month