[JBoss JIRA] (WFLY-5818) Quick redeploy vulnerable to CacheRegistry entry loss
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-5818?page=com.atlassian.jira.plugin.... ]
Paul Ferraro closed WFLY-5818.
------------------------------
Resolution: Done
opened by mistake. Stupid jira interface...
> Quick redeploy vulnerable to CacheRegistry entry loss
> -----------------------------------------------------
>
> Key: WFLY-5818
> URL: https://issues.jboss.org/browse/WFLY-5818
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.0.0.CR4
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
>
> On deploy, CacheRegistry adds its local entry to the cache, and on undeploy removes it entry. However, we use a topology change listener to remove entries for crashed members (since these nodes will not have removed their local entry). However, since the listener is triggered asynchronously, it is possible that the topology change fired in response to an undeploy execute *after* the redeployed CacheRegistry starts - which would cause erroneous removal of the local entry that was added.
> This manifests itself as an intermittent failure of the RegistryTestCase as seen in this PR:
> https://github.com/wildfly/wildfly/pull/8465
> Not surprisingly, this issue only surfaces in the windoze runs, which, according to [~ctomc], execute faster than the linux runs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5818) Quick redeploy vulnerable to CacheRegistry entry loss
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-5818?page=com.atlassian.jira.plugin.... ]
Paul Ferraro reopened WFLY-5818:
--------------------------------
> Quick redeploy vulnerable to CacheRegistry entry loss
> -----------------------------------------------------
>
> Key: WFLY-5818
> URL: https://issues.jboss.org/browse/WFLY-5818
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.0.0.CR4
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
>
> On deploy, CacheRegistry adds its local entry to the cache, and on undeploy removes it entry. However, we use a topology change listener to remove entries for crashed members (since these nodes will not have removed their local entry). However, since the listener is triggered asynchronously, it is possible that the topology change fired in response to an undeploy execute *after* the redeployed CacheRegistry starts - which would cause erroneous removal of the local entry that was added.
> This manifests itself as an intermittent failure of the RegistryTestCase as seen in this PR:
> https://github.com/wildfly/wildfly/pull/8465
> Not surprisingly, this issue only surfaces in the windoze runs, which, according to [~ctomc], execute faster than the linux runs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5817) Read resource of deployment with faulty datasource fails
by Tomaz Cerar (JIRA)
Tomaz Cerar created WFLY-5817:
---------------------------------
Summary: Read resource of deployment with faulty datasource fails
Key: WFLY-5817
URL: https://issues.jboss.org/browse/WFLY-5817
Project: WildFly
Issue Type: Bug
Components: Domain Management
Reporter: Tomaz Cerar
Assignee: Tomaz Cerar
For the setup see HAL-1006. Reading the deployments of a server which contains a deployment with a faulty datasource, yields an undefined result:
{code}
/host=master/server=server-one:read-children-resources(child-type=deployment,recursive=true,include-runtime=true)
{
"outcome" => "success",
"result" => undefined,
"failure-description" => undefined
}
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5816) Quick redeploy vulnerable to CacheRegistry entry loss
by Paul Ferraro (JIRA)
Paul Ferraro created WFLY-5816:
----------------------------------
Summary: Quick redeploy vulnerable to CacheRegistry entry loss
Key: WFLY-5816
URL: https://issues.jboss.org/browse/WFLY-5816
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 10.0.0.CR4
Reporter: Paul Ferraro
Assignee: Paul Ferraro
On deploy, CacheRegistry adds its local entry to the cache, and on undeploy removes it entry. However, we use a topology change listener to remove entries for crashed members (since these nodes will not have removed their local entry). However, since the listener is triggered asynchronously, it is possible that the topology change fired in response to an undeploy execute *after* the redeployed CacheRegistry starts - which would cause erroneous removal of the local entry that was added.
This manifests itself as an intermittent failure of the RegistryTestCase as seen in this PR:
https://github.com/wildfly/wildfly/pull/8465
Not surprisingly, this issue only surfaces in the windoze runs, which, according to [~ctomc], execute faster than the linux runs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFCORE-1197) Enhance missing capability logging during subsystem testing
by Darran Lofthouse (JIRA)
Darran Lofthouse created WFCORE-1197:
----------------------------------------
Summary: Enhance missing capability logging during subsystem testing
Key: WFCORE-1197
URL: https://issues.jboss.org/browse/WFCORE-1197
Project: WildFly Core
Issue Type: Enhancement
Components: Test Suite
Affects Versions: 2.0.4.Final
Reporter: Darran Lofthouse
Assignee: Tomaz Cerar
Fix For: 3.0.0.Alpha1
Making changes to the Undertow subsystem I was presented with the following failure: -
{noformat}
<testcase name="testRuntime" classname="org.wildfly.extension.undertow.UndertowSubsystemTestCase" time="1.611">
<error type="java.lang.NullPointerException:">java.lang.NullPointerException: null
at org.wildfly.extension.undertow.UndertowSubsystemTestCase.testRuntime(UndertowSubsystemTestCase.java:118)
{noformat}
It was only after enabling other logging I found the real cause: -
{noformat}
ec 08, 2015 6:19:22 PM org.jboss.as.controller.OperationContextImpl validateCapabilities
ERROR: WFLYCTL0362: Capabilities required by resource '/subsystem=undertow/application-security-domain=other' are not available:
org.wildfly.security.http-server-mechanism-factory.elytron-factory; There are no known registration points which can provide this capability.
{noformat}
The NullPointerException above is because it is detected the booting failed but the error was never made available.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-4941) WFLYCLEJBINF0005: Failed to cancel expiration/passivation of bean UnknownSessionID on primary owner.: ExecutionException: TimeoutException: timeout sending message
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4941?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-4941:
--------------------------------------
I am seeing this too more frequently than i would expect when testing shutdown locally. This is pending investigation but my guess is that this will need fixing.
> WFLYCLEJBINF0005: Failed to cancel expiration/passivation of bean UnknownSessionID on primary owner.: ExecutionException: TimeoutException: timeout sending message
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4941
> URL: https://issues.jboss.org/browse/WFLY-4941
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.0.0.Alpha6, 10.0.0.Beta1
> Reporter: Michal Vinkler
> Assignee: Paul Ferraro
>
> Seen in our failover tests - this warning message is present in each server log in each test we have run so far.
> When each server in cluster is restarting after failover, other servers get CacheTopology change (the starting server is added) and the servers log this warning message many times:
> (for http session tests, the error identificator is WFLYCL*WEB*INF0005 rather than WFLYCL*EJB*INF0005)
> {code}
> [JBossINF] [0m[0m11:32:27,681 INFO [org.infinispan.CLUSTER] (remote-thread--p5-t12) ISPN000336: Finished cluster-wide rebalance for cache dist, topology id = 10
> [JBossINF] [0m[0m11:32:27,809 INFO [org.infinispan.CLUSTER] (remote-thread--p6-t2) ISPN000310: Starting cluster-wide rebalance for cache clusterbench-ee7.ear/clusterbench-ee7-ejb.jar, topology CacheTopology{id=10, rebalanceId=5, currentCH=DefaultConsistentHash{ns=80, owners = (3)[perf19: 26+28, perf20: 27+26, perf21: 27+26]}, pendingCH=DefaultConsistentHash{ns=80, owners = (4)[perf19: 20+20, perf20: 20+20, perf21: 20+20, perf18: 20+20]}, unionCH=null, actualMembers=[perf19, perf20, perf21, perf18]}
> [JBossINF] [0m[0m11:32:28,347 INFO [org.infinispan.CLUSTER] (remote-thread--p6-t6) ISPN000336: Finished cluster-wide rebalance for cache clusterbench-ee7.ear/clusterbench-ee7-ejb.jar, topology id = 10
> [JBossINF] [0m[33m11:32:28,624 WARN [org.wildfly.clustering.ejb.infinispan] (EJB default - 4) WFLYCLEJBINF0005: Failed to cancel expiration/passivation of bean UnknownSessionID [6855655451695655554868505252524957485470656956657048536848556569] on primary owner.: java.util.concurrent.ExecutionException: java.util.concurrent.TimeoutException: timeout sending message to perf18
> [JBossINF] at org.jgroups.blocks.UnicastRequest.getValue(UnicastRequest.java:203)
> [JBossINF] at org.jgroups.blocks.UnicastRequest.get(UnicastRequest.java:212)
> [JBossINF] at org.wildfly.clustering.server.dispatcher.ChannelCommandDispatcher.executeOnNode(ChannelCommandDispatcher.java:151)
> [JBossINF] at org.wildfly.clustering.ejb.infinispan.InfinispanBeanManager$6.call(InfinispanBeanManager.java:237)
> [JBossINF] at org.wildfly.clustering.ejb.infinispan.InfinispanBeanManager$6.call(InfinispanBeanManager.java:232)
> [JBossINF] at org.wildfly.clustering.ee.infinispan.RetryingInvoker.invoke(RetryingInvoker.java:70)
> [JBossINF] at org.wildfly.clustering.ejb.infinispan.InfinispanBeanManager.executeOnPrimaryOwner(InfinispanBeanManager.java:240)
> [JBossINF] at org.wildfly.clustering.ejb.infinispan.InfinispanBeanManager.cancel(InfinispanBeanManager.java:217)
> [JBossINF] at org.wildfly.clustering.ejb.infinispan.InfinispanBeanManager.findBean(InfinispanBeanManager.java:267)
> [JBossINF] at org.jboss.as.ejb3.cache.distributable.DistributableCache.get(DistributableCache.java:115)
> [JBossINF] at org.jboss.as.ejb3.component.stateful.StatefulComponentInstanceInterceptor.processInvocation(StatefulComponentInstanceInterceptor.java:58)
> [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> [JBossINF] at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:275)
> [JBossINF] at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:327)
> [JBossINF] at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:239)
> [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> [JBossINF] at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropagatingInterceptor.processInvocation(EJBRemoteTransactionPropagatingInterceptor.java:79)
> [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> [JBossINF] at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
> [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> [JBossINF] at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43)
> [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> [JBossINF] at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
> [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> [JBossINF] at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
> [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> [JBossINF] at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:53)
> [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> [JBossINF] at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66)
> [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> [JBossINF] at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
> [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> [JBossINF] at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
> [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> [JBossINF] at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)
> [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> [JBossINF] at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
> [JBossINF] at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:635)
> [JBossINF] at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61)
> [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> [JBossINF] at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
> [JBossINF] at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80)
> [JBossINF] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> [JBossINF] at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> [JBossINF] at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195)
> [JBossINF] at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:331)
> [JBossINF] at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$100(MethodInvocationMessageHandler.java:69)
> [JBossINF] at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:202)
> [JBossINF] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [JBossINF] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [JBossINF] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [JBossINF] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [JBossINF] at java.lang.Thread.run(Thread.java:745)
> [JBossINF] at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> [JBossINF] Caused by: java.util.concurrent.TimeoutException: timeout sending message to perf18
> [JBossINF] ... 54 more
> [JBossINF]
> {code}
> Server log:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-ejb-e...
> Client log:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-7x-failover-ejb-e...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5441) Received unsolicited state from node X for segment Y of cache Z
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5441?page=com.atlassian.jira.plugin.... ]
Radoslav Husar reassigned WFLY-5441:
------------------------------------
Assignee: Radoslav Husar (was: Paul Ferraro)
> Received unsolicited state from node X for segment Y of cache Z
> ---------------------------------------------------------------
>
> Key: WFLY-5441
> URL: https://issues.jboss.org/browse/WFLY-5441
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.0.0.CR5
> Reporter: Richard Janík
> Assignee: Radoslav Husar
> Priority: Minor
>
> Hi,
> we're occasionally seeing these warnings in the server logs:
> {code}
> [JBossINF] [0m[33m08:20:45,364 WARN [org.infinispan.statetransfer.StateConsumerImpl] (stateTransferExecutor-thread--p11-t36) Received unsolicited state from node perf20 for segment 48 of cache clusterbench-ee7.ear/clusterbench-ee7-ejb.jar
> ...
> [JBossINF] [0m[33m08:21:02,793 WARN [org.infinispan.statetransfer.StateConsumerImpl] (stateTransferExecutor-thread--p11-t22) Discarding received cache entries for segment 48 of cache dist because they do not belong to this node.
> {code}
> The warnings seem to be harmless.
> This is the equivalent of https://bugzilla.redhat.com/show_bug.cgi?id=923789 which has been (with EAP6) followed by IllegalStateExceptions and has later been closed as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=922699. However, no IllegalStateExceptions occur with EAP7 and thus these two messages seem to be unrelated.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5441) Received unsolicited state from node X for segment Y of cache Z
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5441?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-5441:
--------------------------------------
This is an upstream issue, see linked ISPN-6012 resolved in Infinispan 8.1.0.Final.
> Received unsolicited state from node X for segment Y of cache Z
> ---------------------------------------------------------------
>
> Key: WFLY-5441
> URL: https://issues.jboss.org/browse/WFLY-5441
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 10.0.0.CR5
> Reporter: Richard Janík
> Assignee: Radoslav Husar
> Priority: Minor
>
> Hi,
> we're occasionally seeing these warnings in the server logs:
> {code}
> [JBossINF] [0m[33m08:20:45,364 WARN [org.infinispan.statetransfer.StateConsumerImpl] (stateTransferExecutor-thread--p11-t36) Received unsolicited state from node perf20 for segment 48 of cache clusterbench-ee7.ear/clusterbench-ee7-ejb.jar
> ...
> [JBossINF] [0m[33m08:21:02,793 WARN [org.infinispan.statetransfer.StateConsumerImpl] (stateTransferExecutor-thread--p11-t22) Discarding received cache entries for segment 48 of cache dist because they do not belong to this node.
> {code}
> The warnings seem to be harmless.
> This is the equivalent of https://bugzilla.redhat.com/show_bug.cgi?id=923789 which has been (with EAP6) followed by IllegalStateExceptions and has later been closed as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=922699. However, no IllegalStateExceptions occur with EAP7 and thus these two messages seem to be unrelated.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (WFLY-5815) Read resource of deployment with faulty datasource fails
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5815?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-5815:
-----------------------------------
It can be reproduce in standalone mode as well, just add both deployments to server.
shutdown server than manually edit standalone.xml and set enable=true for both.
it will fails with similar runtime error than in domain.
> Read resource of deployment with faulty datasource fails
> --------------------------------------------------------
>
> Key: WFLY-5815
> URL: https://issues.jboss.org/browse/WFLY-5815
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Reporter: Harald Pehl
> Assignee: Tomaz Cerar
>
> For the setup see HAL-1006. Reading the deployments of a server which contains a deployment with a faulty datasource, yields an undefined result:
> {code}
> /host=master/server=server-one:read-children-resources(child-type=deployment,recursive=true,include-runtime=true)
> {
> "outcome" => "success",
> "result" => undefined,
> "failure-description" => undefined
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months