[JBoss JIRA] (AS7-6613) ConcurrentModificationException in JBoss OSGi Framework
by Ed Roberts (JIRA)
[ https://issues.jboss.org/browse/AS7-6613?page=com.atlassian.jira.plugin.s... ]
Ed Roberts commented on AS7-6613:
---------------------------------
If it helps. This stack trace was produced when running on the following environment:
Red Hat Enterprise Linux Server release 5.9 64-bit
Kernel: 2.6.18-348.1.1.el5
Java: java version "1.7.0_13"
> ConcurrentModificationException in JBoss OSGi Framework
> -------------------------------------------------------
>
> Key: AS7-6613
> URL: https://issues.jboss.org/browse/AS7-6613
> Project: Application Server 7
> Issue Type: Feature Request
> Components: OSGi
> Affects Versions: 7.2.0.Alpha1
> Environment: Linux and Windows
> Reporter: Ed Roberts
> Assignee: Thomas Diesler
>
> Starting up JBoss AS with a number of deployments, some of which use blueprint to activate services. One of the blueprint activations exposes the concurrency issue
> {code}
> 2013-02-22 15:57:08,193 ERROR [org.eclipse.gemini.blueprint.extender.internal.blueprint.activator.BlueprintLoaderListener](EclipseGeminiBlueprintExtenderThread-29) Application context refresh failed (OsgiBundleXmlApplicationContext(bundle=com.saaconsultants.x, config=bundle://com.saaconsultants.x-170-0-0/OSGI-INF/blueprint/private-beans.xml,bundle://com.saaconsultants.x-170-0-0/OSGI-INF/blueprint/osgi-context.xml,bundle://com.saaconsultants.x-170-0-0/OSGI-INF/blueprint/ee-beans.xml)): org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'otEclInterpreterServiceBean' defined in OSGi resource[bundle://com.saaconsultants.x-170-0-0/OSGI-INF/blueprint/private-beans.xml|bnd.id=170|bnd.sym=com.saaconsultants.x]: Cannot resolve reference to bean 'xService' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'xService': FactoryBean threw exception on object creation; nested exception is java.util.ConcurrentModificationException
> at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:328)
> at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:106)
> at org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:630)
> at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:148)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1035)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:939)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
> at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294)
> at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225)
> at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291)
> at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193)
> at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:585)
> at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:913)
> at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.access$1600(AbstractDelegatedExecutionApplicationContext.java:60)
> at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:325)
> at org.eclipse.gemini.blueprint.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
> at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:290)
> at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:137)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'xService': FactoryBean threw exception on object creation; nested exception is java.util.ConcurrentModificationException
> at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:149)
> at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:102)
> at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1442)
> at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:248)
> at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193)
> at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:322)
> ... 19 more
> Caused by: java.util.ConcurrentModificationException
> at java.util.HashMap$HashIterator.nextEntry(HashMap.java:894)
> at java.util.HashMap$ValueIterator.next(HashMap.java:922)
> at org.jboss.osgi.framework.internal.ServiceManagerImpl.getServiceReferencesInternal(ServiceManagerImpl.java:205)
> at org.jboss.osgi.framework.internal.ServiceManagerImpl.getServiceReferences(ServiceManagerImpl.java:189)
> at org.jboss.osgi.framework.internal.AbstractBundleContext.getServiceReferences(AbstractBundleContext.java:344)
> at org.eclipse.gemini.blueprint.util.OsgiServiceReferenceUtils.getServiceReferences(OsgiServiceReferenceUtils.java:155)
> at org.eclipse.gemini.blueprint.util.OsgiServiceReferenceUtils.getServiceReference(OsgiServiceReferenceUtils.java:70)
> at org.eclipse.gemini.blueprint.util.OsgiServiceReferenceUtils.getServiceReference(OsgiServiceReferenceUtils.java:129)
> at org.eclipse.gemini.blueprint.util.OsgiListenerUtils.addSingleServiceListener(OsgiListenerUtils.java:168)
> at org.eclipse.gemini.blueprint.util.OsgiListenerUtils.addSingleServiceListener(OsgiListenerUtils.java:138)
> at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceDynamicInterceptor.afterPropertiesSet(ServiceDynamicInterceptor.java:467)
> at org.eclipse.gemini.blueprint.service.importer.support.OsgiServiceProxyFactoryBean$2.run(OsgiServiceProxyFactoryBean.java:196)
> at org.eclipse.gemini.blueprint.service.importer.support.AbstractServiceImporterProxyFactoryBean.getObject(AbstractServiceImporterProxyFactoryBean.java:103)
> at org.eclipse.gemini.blueprint.service.importer.support.OsgiServiceProxyFactoryBean.getObject(OsgiServiceProxyFactoryBean.java:125)
> at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:142)
> ... 24 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (AS7-6613) ConcurrentModificationException in JBoss OSGi Framework
by Ed Roberts (JIRA)
Ed Roberts created AS7-6613:
-------------------------------
Summary: ConcurrentModificationException in JBoss OSGi Framework
Key: AS7-6613
URL: https://issues.jboss.org/browse/AS7-6613
Project: Application Server 7
Issue Type: Feature Request
Components: OSGi
Affects Versions: 7.2.0.Alpha1
Environment: Linux and Windows
Reporter: Ed Roberts
Assignee: Thomas Diesler
Starting up JBoss AS with a number of deployments, some of which use blueprint to activate services. One of the blueprint activations exposes the concurrency issue
{code}
2013-02-22 15:57:08,193 ERROR [org.eclipse.gemini.blueprint.extender.internal.blueprint.activator.BlueprintLoaderListener](EclipseGeminiBlueprintExtenderThread-29) Application context refresh failed (OsgiBundleXmlApplicationContext(bundle=com.saaconsultants.x, config=bundle://com.saaconsultants.x-170-0-0/OSGI-INF/blueprint/private-beans.xml,bundle://com.saaconsultants.x-170-0-0/OSGI-INF/blueprint/osgi-context.xml,bundle://com.saaconsultants.x-170-0-0/OSGI-INF/blueprint/ee-beans.xml)): org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'otEclInterpreterServiceBean' defined in OSGi resource[bundle://com.saaconsultants.x-170-0-0/OSGI-INF/blueprint/private-beans.xml|bnd.id=170|bnd.sym=com.saaconsultants.x]: Cannot resolve reference to bean 'xService' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'xService': FactoryBean threw exception on object creation; nested exception is java.util.ConcurrentModificationException
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:328)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:106)
at org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:630)
at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:148)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1035)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:939)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:585)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:913)
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.access$1600(AbstractDelegatedExecutionApplicationContext.java:60)
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:325)
at org.eclipse.gemini.blueprint.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:290)
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:137)
at java.lang.Thread.run(Thread.java:722)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'xService': FactoryBean threw exception on object creation; nested exception is java.util.ConcurrentModificationException
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:149)
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:102)
at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1442)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:248)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:322)
... 19 more
Caused by: java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:894)
at java.util.HashMap$ValueIterator.next(HashMap.java:922)
at org.jboss.osgi.framework.internal.ServiceManagerImpl.getServiceReferencesInternal(ServiceManagerImpl.java:205)
at org.jboss.osgi.framework.internal.ServiceManagerImpl.getServiceReferences(ServiceManagerImpl.java:189)
at org.jboss.osgi.framework.internal.AbstractBundleContext.getServiceReferences(AbstractBundleContext.java:344)
at org.eclipse.gemini.blueprint.util.OsgiServiceReferenceUtils.getServiceReferences(OsgiServiceReferenceUtils.java:155)
at org.eclipse.gemini.blueprint.util.OsgiServiceReferenceUtils.getServiceReference(OsgiServiceReferenceUtils.java:70)
at org.eclipse.gemini.blueprint.util.OsgiServiceReferenceUtils.getServiceReference(OsgiServiceReferenceUtils.java:129)
at org.eclipse.gemini.blueprint.util.OsgiListenerUtils.addSingleServiceListener(OsgiListenerUtils.java:168)
at org.eclipse.gemini.blueprint.util.OsgiListenerUtils.addSingleServiceListener(OsgiListenerUtils.java:138)
at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceDynamicInterceptor.afterPropertiesSet(ServiceDynamicInterceptor.java:467)
at org.eclipse.gemini.blueprint.service.importer.support.OsgiServiceProxyFactoryBean$2.run(OsgiServiceProxyFactoryBean.java:196)
at org.eclipse.gemini.blueprint.service.importer.support.AbstractServiceImporterProxyFactoryBean.getObject(AbstractServiceImporterProxyFactoryBean.java:103)
at org.eclipse.gemini.blueprint.service.importer.support.OsgiServiceProxyFactoryBean.getObject(OsgiServiceProxyFactoryBean.java:125)
at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:142)
... 24 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (AS7-6239) Attribute read for uninstalled bundle breaks console
by Jarkko Rantavuori (JIRA)
[ https://issues.jboss.org/browse/AS7-6239?page=com.atlassian.jira.plugin.s... ]
Jarkko Rantavuori commented on AS7-6239:
----------------------------------------
Seems this affects jboss-cli as well. Started seeing this today
[standalone@localhost:9999 /] /subsystem=osgi:read-children-resources(child-type=bundle,include-runtime=true)
{
"outcome" => "failed",
"rolled-back" => true
}
with this in the logs
18:45:19,027 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014612: Operation ("read-attribute") failed - address: ([
("subsystem" => "osgi"),
("bundle" => "174")
]): java.lang.IllegalStateException: JBOSGI011210: Bundle already uninstalled: osgi-simple-service-api:0.0.2
at org.jboss.osgi.framework.internal.AbstractBundleState.assertNotUninstalled(AbstractBundleState.java:628)
at org.jboss.osgi.framework.internal.UserBundleRevision.getEntry(UserBundleRevision.java:138)
at org.jboss.osgi.framework.internal.HostBundleRevision.getLocalizationEntry(HostBundleRevision.java:199)
at org.jboss.osgi.framework.internal.AbstractBundleState.getLocalizationEntry(AbstractBundleState.java:438)
at org.jboss.osgi.framework.internal.AbstractBundleState.getLocalizationEntry(AbstractBundleState.java:407)
at org.jboss.osgi.framework.internal.AbstractBundleState.getHeaders(AbstractBundleState.java:345)
at org.jboss.osgi.framework.internal.UserBundleState.getHeaders(UserBundleState.java:128)
at org.jboss.osgi.framework.internal.AbstractBundleState.getHeaders(AbstractBundleState.java:320)
> Attribute read for uninstalled bundle breaks console
> ----------------------------------------------------
>
> Key: AS7-6239
> URL: https://issues.jboss.org/browse/AS7-6239
> Project: Application Server 7
> Issue Type: Bug
> Components: Console, OSGi
> Reporter: Thomas Diesler
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (DROOLS-51) Cannot use null as value for a positional constraint
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-51?page=com.atlassian.jira.plugin.... ]
Mario Fusco resolved DROOLS-51.
-------------------------------
Fix Version/s: 5.6
6.0.0.Alpha1
Resolution: Done
> Cannot use null as value for a positional constraint
> ----------------------------------------------------
>
> Key: DROOLS-51
> URL: https://issues.jboss.org/browse/DROOLS-51
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Mario Fusco
> Assignee: Mario Fusco
> Fix For: 5.6, 6.0.0.Alpha1
>
>
> The following DRL generates an infinite loop, while it works correctly if you replace the positional constraint with a normal one as in the commented pattern.
> {code}
> declare Outer
> end
> declare Inner
> outer : Outer
> end
> rule "Init"
> when
> then
> insert( new Inner( null ) );
> insert( new Outer( ) );
> end
> rule "Bind"
> when
> $o : Outer( )
> $i : Inner( null ; ) // $i : Inner( outer == null )
> then
> modify ( $i ) { setOuter( $o ); }
> end
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (AS7-6611) Batch scripts should show some error message when we set JAVA_HOME to nonexisting folder
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-6611:
-------------------------------------
Summary: Batch scripts should show some error message when we set JAVA_HOME to nonexisting folder
Key: AS7-6611
URL: https://issues.jboss.org/browse/AS7-6611
Project: Application Server 7
Issue Type: Enhancement
Components: Scripts
Affects Versions: 7.1.2.Final (EAP)
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 8.0.0.Alpha1
steps to reproduce:
...
{code}jboss-eap-6.0\bin>set JAVA_HOME=c:\dummy
jboss-eap-6.0\bin>standalone.bat
Calling "W:\tmp\pk\jboss-eap-6.0\bin\standalone.conf.bat"
>{code}
...
batch script will end on this line (standalone.bat)
l:73 "%JAVA%" -client -version 2>&1 | findstr /I /C:"Client VM" > nul
On linux we get at least error message:
./standalone.sh: line 178: /home/dummy/bin/java: No such file or directory
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (AS7-6610) Invocation access control context management
by David Lloyd (JIRA)
David Lloyd created AS7-6610:
--------------------------------
Summary: Invocation access control context management
Key: AS7-6610
URL: https://issues.jboss.org/browse/AS7-6610
Project: Application Server 7
Issue Type: Sub-task
Components: Application Client, CDI / Weld, EJB, JMS, POJO, REST, Security, Web
Reporter: David Lloyd
Fix For: 8.0.0.Alpha1
We need to ensure that as part of our security context propagation that we're properly handling access control contexts. For example, an async EJB invocation should have the exact same access control profile as a direct EJB invocation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (AS7-6586) JPA afterCompletion sync may be called from non-application thread, resolve concurrency concern
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/AS7-6586?page=com.atlassian.jira.plugin.s... ]
Scott Marlow updated AS7-6586:
------------------------------
Forum Reference: http://lists.jboss.org/pipermail/jboss-as7-dev/2013-February/007613.html
> JPA afterCompletion sync may be called from non-application thread, resolve concurrency concern
> -----------------------------------------------------------------------------------------------
>
> Key: AS7-6586
> URL: https://issues.jboss.org/browse/AS7-6586
> Project: Application Server 7
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Affects Versions: 7.1.1.Final, 7.1.2.Final (EAP), 7.1.3.Final (EAP)
> Reporter: Scott Marlow
> Assignee: Scott Marlow
> Fix For: 8.0.0.Alpha1
>
>
> For transaction scoped entity managers, the closing the of entity manager is deferred until after the transaction completes.
> It is possible that the transaction manager/service may call the Transaction sync from a non-application thread (tx timeout reaper thread or normal completion in remote propagated tx case). Guards need to be added to make sure that a tx timeout, doesn't interfere with normal application usage of the entity manager.
> I think that there are two main cases to be concerned with that involve the afterCompletion sync being invoked in a non-application thread:
> # TX reaper or other background thread calls afterCompletion while application thread is in (transaction scope) entityManager invocation.
> # TX reaper or other background thread calls afterCompletion while application thread is not in (transaction scope) entityManager invocation.
> Extended persistence contexts do not get closed when the JTA transaction that they are joined to are closed (in case anyone is curious).
> If we are in #1 above, could we delegate the closing of the EntityManager to the in progress EntityManager invocation (to avoid closing the thread unsafe invocation)? Or prevent the background thread from closing the EntityManager until the current EntityManager invocation completes. Or push the requirement up to the top-level EE container (e.g. managed bean, EJB3, web, ...).
> The related classes are org.jboss.as.jpa.container.TransactionScopedEntityManager (or AbstractEntityManager) + org.jboss.as.jpa.transaction.TransactionUtil classes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (DROOLS-51) Cannot use null as value for a positional constraint
by Mario Fusco (JIRA)
Mario Fusco created DROOLS-51:
---------------------------------
Summary: Cannot use null as value for a positional constraint
Key: DROOLS-51
URL: https://issues.jboss.org/browse/DROOLS-51
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Mario Fusco
Assignee: Mario Fusco
The following DRL generates an infinite loop, while it works correctly if you replace the positional constraint with a normal one as in the commented pattern.
{code}
declare Outer
end
declare Inner
outer : Outer
end
rule "Init"
when
then
insert( new Inner( null ) );
insert( new Outer( ) );
end
rule "Bind"
when
$o : Outer( )
$i : Inner( null ; ) // $i : Inner( outer == null )
then
modify ( $i ) { setOuter( $o ); }
end
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months