[JBoss JIRA] (DROOLS-1474) Activation.getObjectsDeep() should include "exists" elements too
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1474?page=com.atlassian.jira.plugi... ]
Mario Fusco commented on DROOLS-1474:
-------------------------------------
This is a totally different requirement from the one regarding the accumulate. The accumulate node actually processes all the accumulated items and also keeps them in its memory to support the reverse operation. Conversely the exists node only matches the first positive occurrence and never evaluates all possible others at all. Evaluating all objects that could match the exists condition will uselessly and dramatically slow down the engine.
This requirement could be possibly fulfilled by plugging in a different implementation of the exists node (enabled through a builder option), but in my opinion the effort to implement this solution largely overcome the advantages.
> Activation.getObjectsDeep() should include "exists" elements too
> ----------------------------------------------------------------
>
> Key: DROOLS-1474
> URL: https://issues.jboss.org/browse/DROOLS-1474
> Project: Drools
> Issue Type: Enhancement
> Components: core engine
> Affects Versions: 7.0.0.Beta6
> Reporter: Geoffrey De Smet
> Assignee: Mario Fusco
>
> _Give them a finger and they'll want a hand. Give them a hand and they'll want an arm._ (dutch proverb)
> The Activation.getObjectDeeps() method introduced for DROOLS-1470 that also includes the accumulates elements, should also include the exists elements. For example:
> {code}
> when
> $c : Computer(id = "c1")
> exists Process(computer == $c)
> then ...
> {code}
> with this data
> {code}
> Computer c1;
> Computer c2;
> Computer c3;
> Process pA = new Process(c1);
> Process pB = new Process(c2);
> Process pC = new Process(c1);
> Process pD = new Process(c3);
> {code}
> gives this result
> {code}
> activation.getObjectsDeep() // includes c1, pA and pC.
> {code}
> The goal is to identify all objects that matched when this rule got fired. In a negative score rule, all those objects are to blame and by focusing to change any of those, it's more likely to improve the overall solution.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-8168) Inter-application depdendency injection failure
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-8168?page=com.atlassian.jira.plugin.... ]
Stuart Douglas resolved WFLY-8168.
----------------------------------
Resolution: Rejected
This is not a supported feature, CDI is scoped to a deployment, if you want to use CDI across multiple deployments your best bet is to package them up in an EAR.
> Inter-application depdendency injection failure
> -----------------------------------------------
>
> Key: WFLY-8168
> URL: https://issues.jboss.org/browse/WFLY-8168
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 10.1.0.Final
> Reporter: Daniel Huss
> Assignee: Stuart Douglas
> Attachments: inter-app-dependency.zip
>
>
> I was trying to implement a simple use case:
> * There's some service.ear providing a _Service_
> * service.ear has a module alias _ModuleAlias_
> * There are add-ons to _Service _that are dynamically deployed as jar files that depend on _ModuleAlias_ via manifest entries
> * The add-ons register/unregister themselves with _Service_ on deployment/undeployment
> The [CDI Reference|https://docs.jboss.org/author/display/WFLY10/CDI+Reference] states that we can depend on other deployments, so this seemed to be the easiest way to get the job done with JEE.
> The registration-on-deployment thing would look like this:
> {code}
> public void register(@Observes @Initialized(ApplicationScoped.class) Object init, AddonContext context)
> {
> context.register(this);
> }
> {code}
> All I get is "WELD-001408: Unsatisfied dependencies".
> So I've created a minimalistic example of the inter-app dependency scenario. See attachment. I've tried moving around module-alias, CDI annotations.... it just won't work.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-7771) Failed to obtain ApplicationPolicy for domain other
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-7771?page=com.atlassian.jira.plugin.... ]
Stuart Douglas resolved WFLY-7771.
----------------------------------
Resolution: Rejected
You have to use graceful shutdown, if the server is being shut down around it then any running requests cannot be properly processed.
If you do a graceful shutdown or a suspend all active websocket connections should be gracefully closed before shutdown commences.
> Failed to obtain ApplicationPolicy for domain other
> ---------------------------------------------------
>
> Key: WFLY-7771
> URL: https://issues.jboss.org/browse/WFLY-7771
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Environment: Centos 7/Wildfly 10.1.0.Final
> Reporter: Albert Borgen
> Assignee: Stuart Douglas
> Priority: Critical
>
> 2016-10-16 21:39:04,743 ERROR [io.undertow.websockets.jsr.request] (default task-242) UT026006: Exception running web socket method: java.lang.RuntimeException: java.lang.IllegalStateException: PBOX00048: Failed to obtain ApplicationPolicy for domain other
> at io.undertow.websockets.jsr.ServerWebSocketContainer.invokeEndpointMethod(ServerWebSocketContainer.java:577)
> at io.undertow.websockets.jsr.ServerWebSocketContainer$6.run(ServerWebSocketContainer.java:561)
> at io.undertow.websockets.jsr.OrderedExecutor$ExecutorTask.run(OrderedExecutor.java:67)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalStateException: PBOX00048: Failed to obtain ApplicationPolicy for domain other
> at org.jboss.security.plugins.mapping.JBossMappingManager.getMappingContext(JBossMappingManager.java:67)
> at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.setup(SecurityContextThreadSetupAction.java:110)
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:42)
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
> at io.undertow.websockets.jsr.ServerWebSocketContainer.invokeEndpointMethod(ServerWebSocketContainer.java:575)
> ... 5 more
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2329) ServerAutoStartTestCase and ServerStartFailureTestCase are never run
by Yeray Borges (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2329?page=com.atlassian.jira.plugi... ]
Yeray Borges commented on WFCORE-2329:
--------------------------------------
Tests were included in surefire.
> ServerAutoStartTestCase and ServerStartFailureTestCase are never run
> --------------------------------------------------------------------
>
> Key: WFCORE-2329
> URL: https://issues.jboss.org/browse/WFCORE-2329
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Test Suite
> Reporter: Brian Stansberry
> Assignee: Yeray Borges
> Labels: domain-mode
>
> Tests in testsuite/domain do not all automatically run just by being called XXXTestCase. They need to be located in one of the packages listed in the surefire config in testsuite/domain/pom.xml or by listed in the @Suite.SuiteClasses annotation of one of the suites that is in one of those packages. ServerAutoStartTestCase and ServerStartFailureTestCase are tests where neither of these are true so they are not running.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-8343) NullPointerException in org.jboss.as.weld.ejb.StatefulSessionObjectReferenceImpl NPE
by David Lloyd (JIRA)
David Lloyd created WFLY-8343:
---------------------------------
Summary: NullPointerException in org.jboss.as.weld.ejb.StatefulSessionObjectReferenceImpl NPE
Key: WFLY-8343
URL: https://issues.jboss.org/browse/WFLY-8343
Project: WildFly
Issue Type: Bug
Components: CDI / Weld
Reporter: David Lloyd
Assignee: Stuart Douglas
An NPE can be found at the following location in a few circumstances:
{noformat}
MSC000004: Failure during stop of service jboss.deployment.unit."17ef036e-b6a1-4660-93b8-d4e55066057d.jar".WeldStartService: java.lang.NullPointerException
at org.jboss.as.weld.ejb.StatefulSessionObjectReferenceImpl.isRemoved(StatefulSessionObjectReferenceImpl.java:134)
at org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:111)
at org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56)
at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100)
at org.jboss.as.test.integration.weld.ejb.multipleviews.EntertainmentDevice$MusicPlayer$1279946549$Proxy$_$$_Weld$EnterpriseProxy$.destroy(Unknown Source)
at org.jboss.weld.bean.SessionBean.destroy(SessionBean.java:162)
at org.jboss.weld.util.bean.IsolatedForwardingBean.destroy(IsolatedForwardingBean.java:50)
at org.jboss.weld.context.AbstractContext.destroyContextualInstance(AbstractContext.java:139)
at org.jboss.weld.context.AbstractContext.destroy(AbstractContext.java:153)
at org.jboss.weld.context.AbstractSharedContext.destroy(AbstractSharedContext.java:61)
at org.jboss.weld.context.AbstractSharedContext.invalidate(AbstractSharedContext.java:56)
at org.jboss.weld.bootstrap.WeldRuntime.shutdown(WeldRuntime.java:56)
at org.jboss.weld.bootstrap.WeldBootstrap.shutdown(WeldBootstrap.java:113)
at org.jboss.as.weld.WeldStartService.stop(WeldStartService.java:128)
at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2150)
at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2101)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{noformat}
{noformat}
WFLYEE0006: Failed to destroy component instance Instance of BMTEPCStatefulBean {UUIDSessionID [37f90331-65e4-4d7e-a5a8-f08e2ec0a509]}: java.lang.NullPointerException
at org.jboss.as.weld.ejb.StatefulSessionObjectReferenceImpl.isRemoved(StatefulSessionObjectReferenceImpl.java:134)
at org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:111)
at org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56)
at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100)
at org.jboss.as.test.integration.jpa.epcpropagation.unsync.CMTPCStatefulBean$Proxy$_$$_Weld$EnterpriseProxy$.destroy(Unknown Source)
at org.jboss.weld.bean.SessionBean.destroy(SessionBean.java:162)
at org.jboss.weld.util.bean.IsolatedForwardingBean.destroy(IsolatedForwardingBean.java:50)
at org.jboss.weld.context.CreationalContextImpl.destroy(CreationalContextImpl.java:142)
at org.jboss.weld.context.CreationalContextImpl.release(CreationalContextImpl.java:130)
at org.jboss.weld.context.CreationalContextImpl.release(CreationalContextImpl.java:121)
at org.jboss.as.weld.injection.WeldManagedReferenceFactory$WeldManagedReference.release(WeldManagedReferenceFactory.java:70)
at org.jboss.as.ee.component.ManagedReferenceReleaseInterceptor.processInvocation(ManagedReferenceReleaseInterceptor.java:60)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.as.ee.component.ManagedReferenceReleaseInterceptor.processInvocation(ManagedReferenceReleaseInterceptor.java:56)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.as.ee.component.ManagedReferenceReleaseInterceptor.processInvocation(ManagedReferenceReleaseInterceptor.java:56)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.as.ee.component.ManagedReferenceReleaseInterceptor.processInvocation(ManagedReferenceReleaseInterceptor.java:56)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.as.jpa.interceptor.SFSBDestroyInterceptor.processInvocation(SFSBDestroyInterceptor.java:49)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53)
at org.jboss.as.ee.component.BasicComponentInstance.destroy(BasicComponentInstance.java:125)
at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.destroyInstance(StatefulSessionComponent.java:159)
at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.destroyInstance(StatefulSessionComponent.java:77)
at org.jboss.as.ejb3.cache.simple.SimpleCache.stop(SimpleCache.java:91)
at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.done(StatefulSessionComponent.java:367)
at org.jboss.as.ejb3.component.EJBComponent.stop(EJBComponent.java:596)
at org.jboss.as.ee.component.ComponentStartService$2.run(ComponentStartService.java:78)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
{noformat}
Both of these exceptions were found in the output of the basic integration test suite.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2329) ServerAutoStartTestCase and ServerStartFailureTestCase are never run
by Yeray Borges (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2329?page=com.atlassian.jira.plugi... ]
Yeray Borges reassigned WFCORE-2329:
------------------------------------
Assignee: Yeray Borges
> ServerAutoStartTestCase and ServerStartFailureTestCase are never run
> --------------------------------------------------------------------
>
> Key: WFCORE-2329
> URL: https://issues.jboss.org/browse/WFCORE-2329
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Test Suite
> Reporter: Brian Stansberry
> Assignee: Yeray Borges
> Labels: domain-mode
>
> Tests in testsuite/domain do not all automatically run just by being called XXXTestCase. They need to be located in one of the packages listed in the surefire config in testsuite/domain/pom.xml or by listed in the @Suite.SuiteClasses annotation of one of the suites that is in one of those packages. ServerAutoStartTestCase and ServerStartFailureTestCase are tests where neither of these are true so they are not running.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-8342) Web sessions and SFSBs cannot be configured with string-based-jdbc-store
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-8342?page=com.atlassian.jira.plugin.... ]
Paul Ferraro moved JBEAP-9507 to WFLY-8342:
-------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-8342 (was: JBEAP-9507)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Clustering
(was: Clustering)
Affects Version/s: 10.1.0.Final
(was: 7.1.0.DR13)
> Web sessions and SFSBs cannot be configured with string-based-jdbc-store
> ------------------------------------------------------------------------
>
> Key: WFLY-8342
> URL: https://issues.jboss.org/browse/WFLY-8342
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.1.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
>
> The binary-keyed-jdbc-store and mixed-keyed-jdbc-store are going away in Infinispan 9. EAP needs to support string-based-jdbc-store.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2524) Revisit Server->Host Controller Authentication
by Darran Lofthouse (JIRA)
Darran Lofthouse created WFCORE-2524:
----------------------------------------
Summary: Revisit Server->Host Controller Authentication
Key: WFCORE-2524
URL: https://issues.jboss.org/browse/WFCORE-2524
Project: WildFly Core
Issue Type: Task
Components: Domain Management, Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Priority: Blocker
Fix For: 3.0.0.Beta8
Previously a server would have a credential generated for it so it could authenticate on the loopback connection to master.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month