[jira] [Updated] (GEODE-6177) Gateway senders can shut down due to authentication failures
[ https://issues.apache.org/jira/browse/GEODE-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill updated GEODE-6177: Fix Version/s: 1.9.0 > Gateway senders can shut down due to authentication failures > > > Key: GEODE-6177 > URL: https://issues.apache.org/jira/browse/GEODE-6177 > Project: Geode > Issue Type: Bug > Components: security, wan >Reporter: Ryan McMahon >Assignee: Ryan McMahon >Priority: Major > Labels: pull-request-available > Fix For: 1.9.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > When a gateway sender connects to a gateway receiver and authentication is > used, the receiver first determines if the provided credentials are valid. > If they are valid, then event processing/dispatching is allowed. > However, once the initial authentication is performed, it is possible that > the gateway sender stops processing events if the connection with the > receiver is destroyed and the credentials used are no longer valid > (disallowed, password changed, etc). > This is an edge case where the ack reader thread is the first to attempt to > acquire the connection, rather than the dispatcher thread. The ack reader > thread currently does not have the proper retry logic for authentication > exceptions, while the dispatcher thread does. We should ensure that > connection retries occur regardless of which thread gets the authentication > exception. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-6177) Gateway senders can shut down due to authentication failures
[ https://issues.apache.org/jira/browse/GEODE-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill resolved GEODE-6177. - Resolution: Fixed > Gateway senders can shut down due to authentication failures > > > Key: GEODE-6177 > URL: https://issues.apache.org/jira/browse/GEODE-6177 > Project: Geode > Issue Type: Bug > Components: security, wan >Reporter: Ryan McMahon >Assignee: Ryan McMahon >Priority: Major > Labels: pull-request-available > Time Spent: 1h 40m > Remaining Estimate: 0h > > When a gateway sender connects to a gateway receiver and authentication is > used, the receiver first determines if the provided credentials are valid. > If they are valid, then event processing/dispatching is allowed. > However, once the initial authentication is performed, it is possible that > the gateway sender stops processing events if the connection with the > receiver is destroyed and the credentials used are no longer valid > (disallowed, password changed, etc). > This is an edge case where the ack reader thread is the first to attempt to > acquire the connection, rather than the dispatcher thread. The ack reader > thread currently does not have the proper retry logic for authentication > exceptions, while the dispatcher thread does. We should ensure that > connection retries occur regardless of which thread gets the authentication > exception. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5993) QueryMonitor can throw RejectedExecutionException due to race
[ https://issues.apache.org/jira/browse/GEODE-5993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill resolved GEODE-5993. - Resolution: Fixed > QueryMonitor can throw RejectedExecutionException due to race > - > > Key: GEODE-5993 > URL: https://issues.apache.org/jira/browse/GEODE-5993 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: Ryan McMahon >Assignee: Ryan McMahon >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > It is possible for a RejectedExecutionException to be thrown due to the > following race: > Thread 1) > - Call monitorQueryThread() and pass LOW_MEMORY check > Thread 2) > - Call cancelAllQueriesDueToMemory() > - Shutdown executor > Thread 1) > - Schedule cancellation task results in RejectedExecutionException -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5881) consolidate DefaultQuery.TestHook methods
[
https://issues.apache.org/jira/browse/GEODE-5881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill resolved GEODE-5881.
-
Resolution: Fixed
> consolidate DefaultQuery.TestHook methods
> -
>
> Key: GEODE-5881
> URL: https://issues.apache.org/jira/browse/GEODE-5881
> Project: Geode
> Issue Type: Task
> Components: querying
>Reporter: Bill
>Assignee: Bill
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> {{DefaultQuery.TestHook}} (interface) defines three methods. They all take a
> "spot" identifier. But some take an {{int}} as the identifier and others take
> a {{String}}.
> When this task is complete, all the methods will use an {{enum}} to identify
> the spot. The benefit will be that we'll have more readable identifiers (than
> the ints) and we'll be able to {{switch}} on the spot id instead of using
> conditionals and {{equals()}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-5568) Rewrite QueryMonitor to use ScheduledThreadPoolExecutor to eliminate notify/wait bugs and improve performance
[
https://issues.apache.org/jira/browse/GEODE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill resolved GEODE-5568.
-
Resolution: Fixed
Fix Version/s: 1.8.0
> Rewrite QueryMonitor to use ScheduledThreadPoolExecutor to eliminate
> notify/wait bugs and improve performance
> -
>
> Key: GEODE-5568
> URL: https://issues.apache.org/jira/browse/GEODE-5568
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Michael Oleske
>Assignee: Bill
>Priority: Major
> Labels: pull-request-available, swat
> Fix For: 1.8.0
>
> Time Spent: 6.5h
> Remaining Estimate: 0h
>
> h2. Original Description
> (original title of this ticket was *testCacheOpAfterQueryCancel in
> QueryMonitorDUnitTest fails intermittently*)
> *We* should remove flakiness from test
> *Before* we add more features around Query Monitor
> *Because* flaky tests do not inspire confidence
> *Notes*
> When running [PR 2311|https://github.com/apache/geode/pull/2311], a test
> failed that passed on a rerun (see
> [here|http://files.apachegeode-ci.info/builds/geode-pr-2311/test-results/distributedTest/1534096152/classes/org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.html#testCacheOpAfterQueryCancel])
> The build artifacts are available
> [here|http://files.apachegeode-ci.info/builds/geode-pr-2311/test-artifacts/1534096152/distributedtestfiles-geode-pr-2311.tgz]
> Since it is a timing issue, it could be a few things so not sure on best path
> forward.
> h2. Update October, 2018
> After seeing more failures on October 2, we decided to fix this bug. We
> discovered an actual product bug in the {{QueryMonitor}}. We also discovered
> that the "hot path" of of monitoring and then un-monitoring a query scaled
> poorly: time complexity was O(N) where N is the number of queries currently
> being monitored. As a result, our fix entailed mostly rewriting the
> {{QueryMonitor}} class to use a more appropriate (off-the-shelf) data
> structure.
> See [GEODE-5568 Analysis and
> Results|https://docs.google.com/document/d/1FFKH2XJMshCE-dBDXtMCYSylr73H54w4TODj4BRW9Y0/edit#]
> for details.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5568) Rewrite QueryMonitor to use ScheduledThreadPoolExecutor to eliminate notify/wait bugs and improve performance
[
https://issues.apache.org/jira/browse/GEODE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill updated GEODE-5568:
Summary: Rewrite QueryMonitor to use ScheduledThreadPoolExecutor to
eliminate notify/wait bugs and improve performance (was: Rewrite QueryMonitor
to use ScheduledThreadPoolExecutor to eliminate notify/wait bugs and improve
worst-case performance)
> Rewrite QueryMonitor to use ScheduledThreadPoolExecutor to eliminate
> notify/wait bugs and improve performance
> -
>
> Key: GEODE-5568
> URL: https://issues.apache.org/jira/browse/GEODE-5568
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Michael Oleske
>Assignee: Bill
>Priority: Major
> Labels: pull-request-available, swat
> Time Spent: 6h 20m
> Remaining Estimate: 0h
>
> h2. Original Description
> (original title of this ticket was *testCacheOpAfterQueryCancel in
> QueryMonitorDUnitTest fails intermittently*)
> *We* should remove flakiness from test
> *Before* we add more features around Query Monitor
> *Because* flaky tests do not inspire confidence
> *Notes*
> When running [PR 2311|https://github.com/apache/geode/pull/2311], a test
> failed that passed on a rerun (see
> [here|http://files.apachegeode-ci.info/builds/geode-pr-2311/test-results/distributedTest/1534096152/classes/org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.html#testCacheOpAfterQueryCancel])
> The build artifacts are available
> [here|http://files.apachegeode-ci.info/builds/geode-pr-2311/test-artifacts/1534096152/distributedtestfiles-geode-pr-2311.tgz]
> Since it is a timing issue, it could be a few things so not sure on best path
> forward.
> h2. Update October, 2018
> After seeing more failures on October 2, we decided to fix this bug. We
> discovered an actual product bug in the {{QueryMonitor}}. We also discovered
> that the "hot path" of of monitoring and then un-monitoring a query scaled
> poorly: time complexity was O(N) where N is the number of queries currently
> being monitored. As a result, our fix entailed mostly rewriting the
> {{QueryMonitor}} class to use a more appropriate (off-the-shelf) data
> structure.
> See [GEODE-5568 Analysis and
> Results|https://docs.google.com/document/d/1FFKH2XJMshCE-dBDXtMCYSylr73H54w4TODj4BRW9Y0/edit#]
> for details.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5881) consolidate DefaultQuery.TestHook methods
Bill created GEODE-5881:
---
Summary: consolidate DefaultQuery.TestHook methods
Key: GEODE-5881
URL: https://issues.apache.org/jira/browse/GEODE-5881
Project: Geode
Issue Type: Task
Components: querying
Reporter: Bill
Fix For: 1.8.0
{{DefaultQuery.TestHook}} (interface) defines three methods. They all take a
"spot" identifier. But some take an {{int}} as the identifier and others take a
{{String}}.
When this task is complete, all the methods will use an {{enum}} to identify
the spot. The benefit will be that we'll have more readable identifiers (than
the ints) and we'll be able to {{switch}} on the spot id instead of using
conditionals and {{equals()}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-5881) consolidate DefaultQuery.TestHook methods
[
https://issues.apache.org/jira/browse/GEODE-5881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill reassigned GEODE-5881:
---
Assignee: Bill
> consolidate DefaultQuery.TestHook methods
> -
>
> Key: GEODE-5881
> URL: https://issues.apache.org/jira/browse/GEODE-5881
> Project: Geode
> Issue Type: Task
> Components: querying
>Reporter: Bill
>Assignee: Bill
>Priority: Major
> Fix For: 1.8.0
>
>
> {{DefaultQuery.TestHook}} (interface) defines three methods. They all take a
> "spot" identifier. But some take an {{int}} as the identifier and others take
> a {{String}}.
> When this task is complete, all the methods will use an {{enum}} to identify
> the spot. The benefit will be that we'll have more readable identifiers (than
> the ints) and we'll be able to {{switch}} on the spot id instead of using
> conditionals and {{equals()}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5845) Document that an enum should never be used for keys
[
https://issues.apache.org/jira/browse/GEODE-5845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16645479#comment-16645479
]
Bill commented on GEODE-5845:
-
To point (1): it isn't clear to me, why drawing key values from a set of named
constants would, in general, be a bad idea. Is it bad because we envision that
set (of keys) to be relatively small?
I don't see anything particularly wrong with a key having a small number of
distinct values. It seems perfectly reasonable to create a region to hold days
of the week, months of the year, or countries on planet earth.
Point (2) is on point. I have a couple minor suggestions:
I think this would be clearer:
"The hash of an enum is derived from a local memory address, resulting in
different hash values on different servers."
And it seems to me the good advice should be something like:
* don't use an {{enum}} type as a key (for a region)
* don't use the {{hashCode()}} of an {{enum}} type in computing the hash code
of a (non-enum) key type
(Geode could conceivably enforce that first bit of advice at runtime. The
second would be a lot harder.)
Then there's the [{{Region}} class
Javadoc|https://geode.apache.org/releases/latest/javadoc/index.html?org/apache/geode/cache/Region.html]:
{quote}Region entries are identified by their key. Any Object can be used as a
key as long as the key Object is region-wide unique and implements both the
equals and hashCode methods. For regions with distributed scope, the key must
also be Serializable.
{quote}
That Javadoc is correct. But as GEODE-5666 illustrates, it's incomplete. Per
the existing Javadoc: the key type {{K}}, used in a {{Region}} must define
{{equals()}} and {{hashCode()}} methods. What we need to stipulate,
additionally is: if the keys are for a partitioned region, then {{hashCode()}}
must _return the same results when applied to the same key value, in every JVM_.
As alluded to in the first comment, this would not be an insurmountable problem
(with {{enum}} types) if the user could override the {{hashCode()}} method on
an {{enum}} type. Alas, the {{hashCode()}} method on an {{enum}} type is
{{final}}—it cannot be overridden. As a result {{enum}} types should not be
used as key types for regions.
> Document that an enum should never be used for keys
> ---
>
> Key: GEODE-5845
> URL: https://issues.apache.org/jira/browse/GEODE-5845
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> Maybe it should be obvious, but an enum type should never be used for an
> entry key. To make this explicitly clear, add this advice to the docs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5797) CI failure: ConcurrentParallelGatewaySenderDUnitTest.testPartitionedParallelPropagationHA
[
https://issues.apache.org/jira/browse/GEODE-5797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16642160#comment-16642160
]
Bill commented on GEODE-5797:
-
seen again:
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/67
> CI failure:
> ConcurrentParallelGatewaySenderDUnitTest.testPartitionedParallelPropagationHA
> -
>
> Key: GEODE-5797
> URL: https://issues.apache.org/jira/browse/GEODE-5797
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Galen O'Sullivan
>Priority: Major
> Labels: swat
>
> at
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/29
> artifacts at
> http://files.apachegeode-ci.info/builds/1.8.0-build.1482/test-artifacts/1538129994/distributedtestfiles-1.8.0-build.1482.tgz
> {noformat}
> org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderDUnitTest
> > testPartitionedParallelPropagationHA FAILED
>
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
>
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
>
> ---
>
> Found suspect string in log4j at line 5853
>
>
> [error 2018/09/28 09:42:18.421 UTC
> tid=0x692] Unexpected exception during bucket recovery
>
> java.lang.IllegalStateException: Region specified in 'colocated-with'
> (/testPartitionedParallelPropagationHA_PR) for region
> /ln_PARALLEL_GATEWAY_SENDER_QUEUE does not exist. It should be created before
> setting 'colocated-with' attribute for this region.
>
> at
> org.apache.geode.internal.cache.ColocationHelper.getColocatedRegion(ColocationHelper.java:94)
>
> at
> org.apache.geode.internal.cache.ColocationHelper.getLeaderRegion(ColocationHelper.java:455)
>
> at
> org.apache.geode.internal.cache.partitioned.PartitionedRegionRebalanceOp.(PartitionedRegionRebalanceOp.java:134)
>
> at
> org.apache.geode.internal.cache.partitioned.PartitionedRegionRebalanceOp.(PartitionedRegionRebalanceOp.java:114)
>
> at
> org.apache.geode.internal.cache.PRHARedundancyProvider$3.run2(PRHARedundancyProvider.java:1587)
>
> at
> org.apache.geode.internal.cache.partitioned.RecoveryRunnable.run(RecoveryRunnable.java:58)
>
> at
> org.apache.geode.internal.OneTaskOnlyExecutor$DelegatingRunnable.run(OneTaskOnlyExecutor.java:141)
>
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
>
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5813) Serialization filter is rejecting class ConditionTimeoutException
[
https://issues.apache.org/jira/browse/GEODE-5813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16642150#comment-16642150
]
Bill commented on GEODE-5813:
-
Seen again in
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/66
> Serialization filter is rejecting class ConditionTimeoutException
> -
>
> Key: GEODE-5813
> URL: https://issues.apache.org/jira/browse/GEODE-5813
> Project: Geode
> Issue Type: Bug
>Reporter: Bill
>Priority: Major
> Labels: swat
>
> In mass-test-run
> QueryMonitorDUnitTest. testQueryMonitorRegionWithEviction failed on four
> runs. Here's one:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/652
> Looks like the DUnit test has serialized a ConditionTimeoutException, which
> causes an exception on the server during deserialization.
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 1130
> [fatal 2018/09/28 02:22:42.272 UTC
> tid=0x20] Serialization filter is rejecting class
> org.awaitility.core.ConditionTimeoutException
> java.lang.Exception:
> at
> org.apache.geode.internal.ObjectInputStreamFilterWrapper.lambda$createSerializationFilter$0(ObjectInputStreamFilterWrapper.java:225)
> at com.sun.proxy.$Proxy26.checkInput(Unknown Source)
> at java.io.ObjectInputStream.filterCheck(ObjectInputStream.java:1239)
> at
> java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1878)
> at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1751)
> at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2042)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1573)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:431)
> at
> org.apache.geode.internal.InternalDataSerializer.readSerializable(InternalDataSerializer.java:2962)
> at
> org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2906)
> at org.apache.geode.DataSerializer.readObject(DataSerializer.java:2977)
> at
> org.apache.geode.internal.util.BlobHelper.deserializeBlob(BlobHelper.java:99)
> at
> org.apache.geode.internal.cache.tier.sockets.CacheServerHelper.deserialize(CacheServerHelper.java:74)
> at
> org.apache.geode.internal.cache.tier.sockets.Part.getObject(Part.java:267)
> at
> org.apache.geode.internal.cache.tier.sockets.Part.getObject(Part.java:275)
> at
> org.apache.geode.cache.client.internal.AbstractOp.processChunkedResponse(AbstractOp.java:345)
> at
> org.apache.geode.cache.client.internal.QueryOp$QueryOpImpl.processResponse(QueryOp.java:171)
> at
> org.apache.geode.cache.client.internal.AbstractOp.processResponse(AbstractOp.java:225)
> at
> org.apache.geode.cache.client.internal.AbstractOp.attemptReadResponse(AbstractOp.java:198)
> at
> org.apache.geode.cache.client.internal.AbstractOp.attempt(AbstractOp.java:386)
> at
> org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:276)
> at
> org.apache.geode.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:325)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:894)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:171)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:128)
> at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:787)
> at
> org.apache.geode.cache.client.internal.QueryOp.execute(QueryOp.java:59)
> at
> org.apache.geode.cache.client.internal.ServerProxy.query(ServerProxy.java:69)
> at
> org.apache.geode.cache.query.internal.DefaultQuery.executeOnServer(DefaultQuery.java:341)
> at
> org.apache.geode.cache.query.internal.DefaultQuery.execute(DefaultQuery.java:222)
> at
> org.apache.geode.cache.query.internal.DefaultQuery.execute(DefaultQuery.java:203)
> at
> org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.exuteQuery(QueryMonitorDUnitTest.java:360)
> at
> org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.lambda$testQueryMonitorRegionWithEviction$bb17a952$4(QueryMonitorDUnitTest.java:210)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
>
[jira] [Assigned] (GEODE-5568) testCacheOpAfterQueryCancel in QueryMonitorDUnitTest is potentially flaky
[ https://issues.apache.org/jira/browse/GEODE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill reassigned GEODE-5568: --- Assignee: Bill > testCacheOpAfterQueryCancel in QueryMonitorDUnitTest is potentially flaky > - > > Key: GEODE-5568 > URL: https://issues.apache.org/jira/browse/GEODE-5568 > Project: Geode > Issue Type: Test > Components: tests >Reporter: Michael Oleske >Assignee: Bill >Priority: Major > Labels: swat > > *We* should remove flakiness from test > *Before* we add more features around Query Monitor > *Because* flaky tests do not inspire confidence > *Notes* > When running [PR 2311|https://github.com/apache/geode/pull/2311], a test > failed that passed on a rerun (see > [here|http://files.apachegeode-ci.info/builds/geode-pr-2311/test-results/distributedTest/1534096152/classes/org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.html#testCacheOpAfterQueryCancel]) > The build artifacts are available > [here|http://files.apachegeode-ci.info/builds/geode-pr-2311/test-artifacts/1534096152/distributedtestfiles-geode-pr-2311.tgz] > Since it is a timing issue, it could be a few things so not sure on best path > forward. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-1603) CI Failure: WANManagementDUnitTest.testReceiverMBean
[
https://issues.apache.org/jira/browse/GEODE-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637570#comment-16637570
]
Bill commented on GEODE-1603:
-
{noformat}
4 failures (99.600% success
rate)org.apache.geode.management.WANManagementDUnitTest
| .testReceiverMBean: 4 failures (99.600% success rate)
| | Failed build 763 at
https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/763
| | Failed build 574 at
https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/574
| | Failed build 520 at
https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/520
| | Failed build 497 at
https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/497
{noformat}
> CI Failure: WANManagementDUnitTest.testReceiverMBean
>
>
> Key: GEODE-1603
> URL: https://issues.apache.org/jira/browse/GEODE-1603
> Project: Geode
> Issue Type: Bug
> Components: ci, management
>Reporter: Dan Smith
>Priority: Major
> Labels: CI, Flaky, swat
>
> Revision: 7ad9cc9451212f1c8a0acba3ec78a9eb562d3780
> {noformat}
> com.gemstone.gemfire.test.dunit.RMIException: While invoking
> com.gemstone.gemfire.management.WANManagementDUnitTest$2.run in VM 0 running
> on Host cc3-rh6.gemstone.com with 4 VMs
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355)
> at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:293)
> at
> com.gemstone.gemfire.management.WANManagementDUnitTest.checkReceiverNavigationAPIS(WANManagementDUnitTest.java:271)
> at
> com.gemstone.gemfire.management.WANManagementDUnitTest.testReceiverMBean(WANManagementDUnitTest.java:162)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
>
[jira] [Comment Edited] (GEODE-1496) org.eclipse.jetty.io.EofException during CLI command tests
[ https://issues.apache.org/jira/browse/GEODE-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637543#comment-16637543 ] Bill edited comment on GEODE-1496 at 10/3/18 10:01 PM: --- Seen again in mass-test-run running RegionMembershipMBeanOverHttpDUnitTest.testMultiplePartitionedRegions See attached test artifacts for that test class: https://issues.apache.org/jira/secure/attachment/12942329/org.apache.geode.management.internal.cli.commands.RegionMembershipMBeanOverHttpDUnitTest.html ^ standard output from the run is available in there Here's the failing mass-test-run: https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/173 was (Author: bburcham): Seen again in mass-test-run running RegionMembershipMBeanOverHttpDUnitTest.testMultiplePartitionedRegions See attached test artifacts for this run (distributedtestfiles-1.8.0-build.1.tgz) Here's the failing mass-test-run: https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/173 > org.eclipse.jetty.io.EofException during CLI command tests > -- > > Key: GEODE-1496 > URL: https://issues.apache.org/jira/browse/GEODE-1496 > Project: Geode > Issue Type: Bug > Components: management >Reporter: Jason Huynh >Assignee: Jared Stewart >Priority: Major > Labels: CI, Flaky, swat > Attachments: > org.apache.geode.management.internal.cli.commands.RegionMembershipMBeanOverHttpDUnitTest.html > > > Originally seen when running > gemfiredatacommandsdunittest.testsimpleremovecomm...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest > This failed in a private run with the following exception: > java.lang.AssertionError: Suspicious strings were written to the log during > this run. > Fix the strings or use IgnoredException.addIgnoredException to ignore. > --- > Found suspect string in log4j at line 988 > [fatal 2016/06/02 17:15:44.523 PDT tid=0xe66] > org.eclipse.jetty.io.EofException > at > org.eclipse.jetty.server.HttpConnection$SendCallback.reset(HttpConnection.java:663) > at > org.eclipse.jetty.server.HttpConnection$SendCallback.access$300(HttpConnection.java:627) > at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:508) > at > org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:668) > at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:722) > at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:177) > at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:163) > at org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:297) > at org.eclipse.jetty.server.Response.flushBuffer(Response.java:1155) > at > javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java:215) > at > org.springframework.http.server.ServletServerHttpResponse.flush(ServletServerHttpResponse.java:95) > at > org.springframework.web.servlet.mvc.method.annotation.HttpEntityMethodProcessor.handleReturnValue(HttpEntityMethodProcessor.java:186) > at > org.springframework.web.method.support.HandlerMethodReturnValueHandlerComposite.handleReturnValue(HandlerMethodReturnValueHandlerComposite.java:80) > at > org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:126) > at > org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:814) > at > org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:737) > at > org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85) > at > org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959) > at > org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893) > at > org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:969) > at > org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:860) > at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:288) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:704) > at > org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:845) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:821) > at >
[jira] [Updated] (GEODE-1496) org.eclipse.jetty.io.EofException during CLI command tests
[ https://issues.apache.org/jira/browse/GEODE-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill updated GEODE-1496: Attachment: org.apache.geode.management.internal.cli.commands.RegionMembershipMBeanOverHttpDUnitTest.html > org.eclipse.jetty.io.EofException during CLI command tests > -- > > Key: GEODE-1496 > URL: https://issues.apache.org/jira/browse/GEODE-1496 > Project: Geode > Issue Type: Bug > Components: management >Reporter: Jason Huynh >Assignee: Jared Stewart >Priority: Major > Labels: CI, Flaky, swat > Attachments: > org.apache.geode.management.internal.cli.commands.RegionMembershipMBeanOverHttpDUnitTest.html > > > Originally seen when running > gemfiredatacommandsdunittest.testsimpleremovecomm...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest > This failed in a private run with the following exception: > java.lang.AssertionError: Suspicious strings were written to the log during > this run. > Fix the strings or use IgnoredException.addIgnoredException to ignore. > --- > Found suspect string in log4j at line 988 > [fatal 2016/06/02 17:15:44.523 PDT tid=0xe66] > org.eclipse.jetty.io.EofException > at > org.eclipse.jetty.server.HttpConnection$SendCallback.reset(HttpConnection.java:663) > at > org.eclipse.jetty.server.HttpConnection$SendCallback.access$300(HttpConnection.java:627) > at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:508) > at > org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:668) > at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:722) > at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:177) > at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:163) > at org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:297) > at org.eclipse.jetty.server.Response.flushBuffer(Response.java:1155) > at > javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java:215) > at > org.springframework.http.server.ServletServerHttpResponse.flush(ServletServerHttpResponse.java:95) > at > org.springframework.web.servlet.mvc.method.annotation.HttpEntityMethodProcessor.handleReturnValue(HttpEntityMethodProcessor.java:186) > at > org.springframework.web.method.support.HandlerMethodReturnValueHandlerComposite.handleReturnValue(HandlerMethodReturnValueHandlerComposite.java:80) > at > org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:126) > at > org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:814) > at > org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:737) > at > org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85) > at > org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959) > at > org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893) > at > org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:969) > at > org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:860) > at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:288) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:704) > at > org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:845) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:821) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1685) > at > org.springframework.web.filter.HttpPutFormContentFilter.doFilterInternal(HttpPutFormContentFilter.java:87) > at > org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > at >
[jira] [Comment Edited] (GEODE-1496) org.eclipse.jetty.io.EofException during CLI command tests
[ https://issues.apache.org/jira/browse/GEODE-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637543#comment-16637543 ] Bill edited comment on GEODE-1496 at 10/3/18 9:53 PM: -- Seen again in mass-test-run running RegionMembershipMBeanOverHttpDUnitTest.testMultiplePartitionedRegions See attached test artifacts for this run (distributedtestfiles-1.8.0-build.1.tgz) Here's the failing mass-test-run: https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/173 was (Author: bburcham): Seen again in mass-test-run running RegionMembershipMBeanOverHttpDUnitTest.testMultiplePartitionedRegions See attached test artifacts for this run (distributedtestfiles-1.8.0-build.1.tgz) > org.eclipse.jetty.io.EofException during CLI command tests > -- > > Key: GEODE-1496 > URL: https://issues.apache.org/jira/browse/GEODE-1496 > Project: Geode > Issue Type: Bug > Components: management >Reporter: Jason Huynh >Assignee: Jared Stewart >Priority: Major > Labels: CI, Flaky, swat > > Originally seen when running > gemfiredatacommandsdunittest.testsimpleremovecomm...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest > This failed in a private run with the following exception: > java.lang.AssertionError: Suspicious strings were written to the log during > this run. > Fix the strings or use IgnoredException.addIgnoredException to ignore. > --- > Found suspect string in log4j at line 988 > [fatal 2016/06/02 17:15:44.523 PDT tid=0xe66] > org.eclipse.jetty.io.EofException > at > org.eclipse.jetty.server.HttpConnection$SendCallback.reset(HttpConnection.java:663) > at > org.eclipse.jetty.server.HttpConnection$SendCallback.access$300(HttpConnection.java:627) > at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:508) > at > org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:668) > at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:722) > at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:177) > at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:163) > at org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:297) > at org.eclipse.jetty.server.Response.flushBuffer(Response.java:1155) > at > javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java:215) > at > org.springframework.http.server.ServletServerHttpResponse.flush(ServletServerHttpResponse.java:95) > at > org.springframework.web.servlet.mvc.method.annotation.HttpEntityMethodProcessor.handleReturnValue(HttpEntityMethodProcessor.java:186) > at > org.springframework.web.method.support.HandlerMethodReturnValueHandlerComposite.handleReturnValue(HandlerMethodReturnValueHandlerComposite.java:80) > at > org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:126) > at > org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:814) > at > org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:737) > at > org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85) > at > org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959) > at > org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893) > at > org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:969) > at > org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:860) > at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:288) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:704) > at > org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:845) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:821) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1685) > at > org.springframework.web.filter.HttpPutFormContentFilter.doFilterInternal(HttpPutFormContentFilter.java:87) > at > org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668) > at >
[jira] [Comment Edited] (GEODE-1496) org.eclipse.jetty.io.EofException during CLI command tests
[ https://issues.apache.org/jira/browse/GEODE-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637543#comment-16637543 ] Bill edited comment on GEODE-1496 at 10/3/18 9:51 PM: -- Seen again in mass-test-run running RegionMembershipMBeanOverHttpDUnitTest.testMultiplePartitionedRegions See attached test artifacts for this run (distributedtestfiles-1.8.0-build.1.tgz) was (Author: bburcham): Seen again in mass-test-run running RegionMembershipMBeanOverHttpDUnitTest.testMultiplePartitionedRegions See attached test artifacts for this run. > org.eclipse.jetty.io.EofException during CLI command tests > -- > > Key: GEODE-1496 > URL: https://issues.apache.org/jira/browse/GEODE-1496 > Project: Geode > Issue Type: Bug > Components: management >Reporter: Jason Huynh >Assignee: Jared Stewart >Priority: Major > Labels: CI, Flaky, swat > > Originally seen when running > gemfiredatacommandsdunittest.testsimpleremovecomm...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest > This failed in a private run with the following exception: > java.lang.AssertionError: Suspicious strings were written to the log during > this run. > Fix the strings or use IgnoredException.addIgnoredException to ignore. > --- > Found suspect string in log4j at line 988 > [fatal 2016/06/02 17:15:44.523 PDT tid=0xe66] > org.eclipse.jetty.io.EofException > at > org.eclipse.jetty.server.HttpConnection$SendCallback.reset(HttpConnection.java:663) > at > org.eclipse.jetty.server.HttpConnection$SendCallback.access$300(HttpConnection.java:627) > at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:508) > at > org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:668) > at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:722) > at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:177) > at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:163) > at org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:297) > at org.eclipse.jetty.server.Response.flushBuffer(Response.java:1155) > at > javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java:215) > at > org.springframework.http.server.ServletServerHttpResponse.flush(ServletServerHttpResponse.java:95) > at > org.springframework.web.servlet.mvc.method.annotation.HttpEntityMethodProcessor.handleReturnValue(HttpEntityMethodProcessor.java:186) > at > org.springframework.web.method.support.HandlerMethodReturnValueHandlerComposite.handleReturnValue(HandlerMethodReturnValueHandlerComposite.java:80) > at > org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:126) > at > org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:814) > at > org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:737) > at > org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85) > at > org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959) > at > org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893) > at > org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:969) > at > org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:860) > at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:288) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:704) > at > org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:845) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:821) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1685) > at > org.springframework.web.filter.HttpPutFormContentFilter.doFilterInternal(HttpPutFormContentFilter.java:87) > at > org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at >
[jira] [Commented] (GEODE-1496) org.eclipse.jetty.io.EofException during CLI command tests
[ https://issues.apache.org/jira/browse/GEODE-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637543#comment-16637543 ] Bill commented on GEODE-1496: - Seen again in mass-test-run running RegionMembershipMBeanOverHttpDUnitTest.testMultiplePartitionedRegions See attached test artifacts for this run. > org.eclipse.jetty.io.EofException during CLI command tests > -- > > Key: GEODE-1496 > URL: https://issues.apache.org/jira/browse/GEODE-1496 > Project: Geode > Issue Type: Bug > Components: management >Reporter: Jason Huynh >Assignee: Jared Stewart >Priority: Major > Labels: CI, Flaky, swat > > Originally seen when running > gemfiredatacommandsdunittest.testsimpleremovecomm...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest > This failed in a private run with the following exception: > java.lang.AssertionError: Suspicious strings were written to the log during > this run. > Fix the strings or use IgnoredException.addIgnoredException to ignore. > --- > Found suspect string in log4j at line 988 > [fatal 2016/06/02 17:15:44.523 PDT tid=0xe66] > org.eclipse.jetty.io.EofException > at > org.eclipse.jetty.server.HttpConnection$SendCallback.reset(HttpConnection.java:663) > at > org.eclipse.jetty.server.HttpConnection$SendCallback.access$300(HttpConnection.java:627) > at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:508) > at > org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:668) > at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:722) > at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:177) > at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:163) > at org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:297) > at org.eclipse.jetty.server.Response.flushBuffer(Response.java:1155) > at > javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java:215) > at > org.springframework.http.server.ServletServerHttpResponse.flush(ServletServerHttpResponse.java:95) > at > org.springframework.web.servlet.mvc.method.annotation.HttpEntityMethodProcessor.handleReturnValue(HttpEntityMethodProcessor.java:186) > at > org.springframework.web.method.support.HandlerMethodReturnValueHandlerComposite.handleReturnValue(HandlerMethodReturnValueHandlerComposite.java:80) > at > org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:126) > at > org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:814) > at > org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:737) > at > org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85) > at > org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959) > at > org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893) > at > org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:969) > at > org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:860) > at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:288) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:704) > at > org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:845) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:821) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1685) > at > org.springframework.web.filter.HttpPutFormContentFilter.doFilterInternal(HttpPutFormContentFilter.java:87) > at > org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1158) > at >
[jira] [Updated] (GEODE-1496) org.eclipse.jetty.io.EofException thrown during CLI command tests
[ https://issues.apache.org/jira/browse/GEODE-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill updated GEODE-1496: Summary: org.eclipse.jetty.io.EofException thrown during CLI command tests (was: CI Failure: gemfiredatacommandsdunittest.testsimpleremovecomm...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest) > org.eclipse.jetty.io.EofException thrown during CLI command tests > - > > Key: GEODE-1496 > URL: https://issues.apache.org/jira/browse/GEODE-1496 > Project: Geode > Issue Type: Bug > Components: management >Reporter: Jason Huynh >Assignee: Jared Stewart >Priority: Major > Labels: CI, Flaky, swat > > Original subject was: CI Failure: > gemfiredatacommandsdunittest.testsimpleremovecomm...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest > Original description was... > This failed in a private run with the following exception: > java.lang.AssertionError: Suspicious strings were written to the log during > this run. > Fix the strings or use IgnoredException.addIgnoredException to ignore. > --- > Found suspect string in log4j at line 988 > [fatal 2016/06/02 17:15:44.523 PDT tid=0xe66] > org.eclipse.jetty.io.EofException > at > org.eclipse.jetty.server.HttpConnection$SendCallback.reset(HttpConnection.java:663) > at > org.eclipse.jetty.server.HttpConnection$SendCallback.access$300(HttpConnection.java:627) > at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:508) > at > org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:668) > at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:722) > at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:177) > at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:163) > at org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:297) > at org.eclipse.jetty.server.Response.flushBuffer(Response.java:1155) > at > javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java:215) > at > org.springframework.http.server.ServletServerHttpResponse.flush(ServletServerHttpResponse.java:95) > at > org.springframework.web.servlet.mvc.method.annotation.HttpEntityMethodProcessor.handleReturnValue(HttpEntityMethodProcessor.java:186) > at > org.springframework.web.method.support.HandlerMethodReturnValueHandlerComposite.handleReturnValue(HandlerMethodReturnValueHandlerComposite.java:80) > at > org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:126) > at > org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:814) > at > org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:737) > at > org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85) > at > org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959) > at > org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893) > at > org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:969) > at > org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:860) > at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:288) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:704) > at > org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:845) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:821) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1685) > at > org.springframework.web.filter.HttpPutFormContentFilter.doFilterInternal(HttpPutFormContentFilter.java:87) > at > org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > at >
[jira] [Updated] (GEODE-1496) org.eclipse.jetty.io.EofException during CLI command tests
[ https://issues.apache.org/jira/browse/GEODE-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill updated GEODE-1496: Summary: org.eclipse.jetty.io.EofException during CLI command tests (was: org.eclipse.jetty.io.EofException thrown during CLI command tests) > org.eclipse.jetty.io.EofException during CLI command tests > -- > > Key: GEODE-1496 > URL: https://issues.apache.org/jira/browse/GEODE-1496 > Project: Geode > Issue Type: Bug > Components: management >Reporter: Jason Huynh >Assignee: Jared Stewart >Priority: Major > Labels: CI, Flaky, swat > > Original subject was: CI Failure: > gemfiredatacommandsdunittest.testsimpleremovecomm...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest > Original description was... > This failed in a private run with the following exception: > java.lang.AssertionError: Suspicious strings were written to the log during > this run. > Fix the strings or use IgnoredException.addIgnoredException to ignore. > --- > Found suspect string in log4j at line 988 > [fatal 2016/06/02 17:15:44.523 PDT tid=0xe66] > org.eclipse.jetty.io.EofException > at > org.eclipse.jetty.server.HttpConnection$SendCallback.reset(HttpConnection.java:663) > at > org.eclipse.jetty.server.HttpConnection$SendCallback.access$300(HttpConnection.java:627) > at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:508) > at > org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:668) > at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:722) > at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:177) > at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:163) > at org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:297) > at org.eclipse.jetty.server.Response.flushBuffer(Response.java:1155) > at > javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java:215) > at > org.springframework.http.server.ServletServerHttpResponse.flush(ServletServerHttpResponse.java:95) > at > org.springframework.web.servlet.mvc.method.annotation.HttpEntityMethodProcessor.handleReturnValue(HttpEntityMethodProcessor.java:186) > at > org.springframework.web.method.support.HandlerMethodReturnValueHandlerComposite.handleReturnValue(HandlerMethodReturnValueHandlerComposite.java:80) > at > org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:126) > at > org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:814) > at > org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:737) > at > org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85) > at > org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959) > at > org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893) > at > org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:969) > at > org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:860) > at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:288) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:704) > at > org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:845) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:821) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1685) > at > org.springframework.web.filter.HttpPutFormContentFilter.doFilterInternal(HttpPutFormContentFilter.java:87) > at > org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1158) > at >
[jira] [Updated] (GEODE-1496) CI Failure: gemfiredatacommandsdunittest.testsimpleremovecomm...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest
[ https://issues.apache.org/jira/browse/GEODE-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill updated GEODE-1496: Description: Original subject was: CI Failure: gemfiredatacommandsdunittest.testsimpleremovecomm...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest Original description was... This failed in a private run with the following exception: java.lang.AssertionError: Suspicious strings were written to the log during this run. Fix the strings or use IgnoredException.addIgnoredException to ignore. --- Found suspect string in log4j at line 988 [fatal 2016/06/02 17:15:44.523 PDT tid=0xe66] org.eclipse.jetty.io.EofException at org.eclipse.jetty.server.HttpConnection$SendCallback.reset(HttpConnection.java:663) at org.eclipse.jetty.server.HttpConnection$SendCallback.access$300(HttpConnection.java:627) at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:508) at org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:668) at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:722) at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:177) at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:163) at org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:297) at org.eclipse.jetty.server.Response.flushBuffer(Response.java:1155) at javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java:215) at org.springframework.http.server.ServletServerHttpResponse.flush(ServletServerHttpResponse.java:95) at org.springframework.web.servlet.mvc.method.annotation.HttpEntityMethodProcessor.handleReturnValue(HttpEntityMethodProcessor.java:186) at org.springframework.web.method.support.HandlerMethodReturnValueHandlerComposite.handleReturnValue(HandlerMethodReturnValueHandlerComposite.java:80) at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:126) at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:814) at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:737) at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85) at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959) at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893) at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:969) at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:860) at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:288) at javax.servlet.http.HttpServlet.service(HttpServlet.java:704) at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:845) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:821) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1685) at org.springframework.web.filter.HttpPutFormContentFilter.doFilterInternal(HttpPutFormContentFilter.java:87) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1158) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1090) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:109) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:119) at org.eclipse.jetty.server.Server.handle(Server.java:517) at
[jira] [Updated] (GEODE-1496) CI Failure: gemfiredatacommandsdunittest.testsimpleremovecomm...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest
[ https://issues.apache.org/jira/browse/GEODE-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill updated GEODE-1496: Labels: CI Flaky swat (was: CI Flaky) > CI Failure: > gemfiredatacommandsdunittest.testsimpleremovecomm...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest > --- > > Key: GEODE-1496 > URL: https://issues.apache.org/jira/browse/GEODE-1496 > Project: Geode > Issue Type: Bug > Components: management >Reporter: Jason Huynh >Assignee: Jared Stewart >Priority: Major > Labels: CI, Flaky, swat > > This failed in a private run with the following exception: > java.lang.AssertionError: Suspicious strings were written to the log during > this run. > Fix the strings or use IgnoredException.addIgnoredException to ignore. > --- > Found suspect string in log4j at line 988 > [fatal 2016/06/02 17:15:44.523 PDT tid=0xe66] > org.eclipse.jetty.io.EofException > at > org.eclipse.jetty.server.HttpConnection$SendCallback.reset(HttpConnection.java:663) > at > org.eclipse.jetty.server.HttpConnection$SendCallback.access$300(HttpConnection.java:627) > at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:508) > at > org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:668) > at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:722) > at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:177) > at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:163) > at org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:297) > at org.eclipse.jetty.server.Response.flushBuffer(Response.java:1155) > at > javax.servlet.ServletResponseWrapper.flushBuffer(ServletResponseWrapper.java:215) > at > org.springframework.http.server.ServletServerHttpResponse.flush(ServletServerHttpResponse.java:95) > at > org.springframework.web.servlet.mvc.method.annotation.HttpEntityMethodProcessor.handleReturnValue(HttpEntityMethodProcessor.java:186) > at > org.springframework.web.method.support.HandlerMethodReturnValueHandlerComposite.handleReturnValue(HandlerMethodReturnValueHandlerComposite.java:80) > at > org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:126) > at > org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:814) > at > org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:737) > at > org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85) > at > org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959) > at > org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893) > at > org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:969) > at > org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:860) > at javax.servlet.http.HttpServlet.doHead(HttpServlet.java:288) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:704) > at > org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:845) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:821) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1685) > at > org.springframework.web.filter.HttpPutFormContentFilter.doFilterInternal(HttpPutFormContentFilter.java:87) > at > org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1158) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511) > at >
[jira] [Updated] (GEODE-5816) ClusterStartupRule fails to launch JMX manager (port already in use)
[
https://issues.apache.org/jira/browse/GEODE-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill updated GEODE-5816:
Labels: swat (was: )
> ClusterStartupRule fails to launch JMX manager (port already in use)
>
>
> Key: GEODE-5816
> URL: https://issues.apache.org/jira/browse/GEODE-5816
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Bill
>Priority: Major
> Labels: swat
>
> We see these related failures on a couple tests in
> RegionMembershipMBeanOverHttpDUnitTest from our recent mass-test-run.
> From looking at the stack traces though, we surmise that the problem occurs
> in the ClusterStartupRule _before_ the actual tests run. Since it occurs
> before the tests run, we think the problem lies outside the
> RegionMembershipMBeanOverHttpDUnitTest class.
> {noformat}
> 4 failures (99.600% success
> rate)org.apache.geode.management.internal.cli.commands.RegionMembershipMBeanOverHttpDUnitTest
> | .testAddRmNewMemberWithReplicatedRegionsAndSubregions: 1 failures
> (99.900% success rate)
> | | Failed build 24 at
> https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/24
> | .testMultiplePartitionedRegions: 3 failures (99.700% success rate)
> | | Failed build 982 at
> https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/982
> | | Failed build 256 at
> https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/256
> {noformat}
> Here's a stack trace:
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 358
> [error 2018/10/01 06:28:30.869 UTC
> tid=0x20] Jmx manager could not be started because
> java.rmi.server.ExportException: Port already in use: 25305; nested exception
> is:
> java.net.BindException: Failed to create server socket on
> ffd50f3577c5/172.17.0.20[25305]
> org.apache.geode.management.ManagementException:
> java.rmi.server.ExportException: Port already in use: 25305; nested exception
> is:
> java.net.BindException: Failed to create server socket on
> ffd50f3577c5/172.17.0.20[25305]
> at
> org.apache.geode.management.internal.ManagementAgent.startAgent(ManagementAgent.java:162)
> at
> org.apache.geode.management.internal.SystemManagementService.startManager(SystemManagementService.java:435)
> at
> org.apache.geode.management.internal.beans.ManagementAdapter.handleCacheCreation(ManagementAdapter.java:173)
> at
> org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:118)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2201)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:591)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1218)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:793)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:779)
> at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:177)
> at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:224)
> at
> org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:662)
> at
> org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:649)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:311)
> at org.apache.geode.distributed.Locator.startLocator(Locator.java:253)
> at
> org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:140)
> at
> org.apache.geode.test.junit.rules.LocatorStarterRule.startLocator(LocatorStarterRule.java:87)
> at
> org.apache.geode.test.junit.rules.LocatorStarterRule.before(LocatorStarterRule.java:68)
> at
> org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startLocatorVM$22d9b8a8$1(ClusterStartupRule.java:206)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
[jira] [Created] (GEODE-5816) ClusterStartupRule fails to launch JMX manager (port already in use)
Bill created GEODE-5816:
---
Summary: ClusterStartupRule fails to launch JMX manager (port
already in use)
Key: GEODE-5816
URL: https://issues.apache.org/jira/browse/GEODE-5816
Project: Geode
Issue Type: Bug
Components: tests
Reporter: Bill
We see these related failures on a couple tests in
RegionMembershipMBeanOverHttpDUnitTest from our recent mass-test-run.
>From looking at the stack traces though, we surmise that the problem occurs in
>the ClusterStartupRule _before_ the actual tests run. Since it occurs before
>the tests run, we think the problem lies outside the
>RegionMembershipMBeanOverHttpDUnitTest class.
{noformat}
4 failures (99.600% success
rate)org.apache.geode.management.internal.cli.commands.RegionMembershipMBeanOverHttpDUnitTest
| .testAddRmNewMemberWithReplicatedRegionsAndSubregions: 1 failures (99.900%
success rate)
| | Failed build 24 at
https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/24
| .testMultiplePartitionedRegions: 3 failures (99.700% success rate)
| | Failed build 982 at
https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/982
| | Failed build 256 at
https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/256
{noformat}
Here's a stack trace:
{noformat}
java.lang.AssertionError: Suspicious strings were written to the log during
this run.
Fix the strings or use IgnoredException.addIgnoredException to ignore.
---
Found suspect string in log4j at line 358
[error 2018/10/01 06:28:30.869 UTC
tid=0x20] Jmx manager could not be started because
java.rmi.server.ExportException: Port already in use: 25305; nested exception
is:
java.net.BindException: Failed to create server socket on
ffd50f3577c5/172.17.0.20[25305]
org.apache.geode.management.ManagementException:
java.rmi.server.ExportException: Port already in use: 25305; nested exception
is:
java.net.BindException: Failed to create server socket on
ffd50f3577c5/172.17.0.20[25305]
at
org.apache.geode.management.internal.ManagementAgent.startAgent(ManagementAgent.java:162)
at
org.apache.geode.management.internal.SystemManagementService.startManager(SystemManagementService.java:435)
at
org.apache.geode.management.internal.beans.ManagementAdapter.handleCacheCreation(ManagementAdapter.java:173)
at
org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:118)
at
org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2201)
at
org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:591)
at
org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1218)
at
org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:793)
at
org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:779)
at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:177)
at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:224)
at
org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:662)
at
org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:649)
at
org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:311)
at org.apache.geode.distributed.Locator.startLocator(Locator.java:253)
at
org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:140)
at
org.apache.geode.test.junit.rules.LocatorStarterRule.startLocator(LocatorStarterRule.java:87)
at
org.apache.geode.test.junit.rules.LocatorStarterRule.before(LocatorStarterRule.java:68)
at
org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startLocatorVM$22d9b8a8$1(ClusterStartupRule.java:206)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at hydra.MethExecutor.executeObject(MethExecutor.java:244)
at
org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at
[jira] [Comment Edited] (GEODE-5501) CI Failure: NetSearchMessagingDUnitTest.testOneMessageWithReplicates
[
https://issues.apache.org/jira/browse/GEODE-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637364#comment-16637364
]
Bill edited comment on GEODE-5501 at 10/3/18 6:53 PM:
--
occurred again in mass test run...
5 failures (99.500% success
rate)org.apache.geode.internal.cache.NetSearchMessagingDUnitTest
org.apache.geode.internal.cache.NetSearchMessagingDUnitTest: 5 failures
(99.500% success rate)
These first four failures all have the same message as this ticket:
Failed build 921 at
https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/921
Failed build 814 at
https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/814
Failed build 440 at
https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/440
Failed build 188 at
https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/188
This failure looks related but has a slightly different error message:
Failed build 904 at
[https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/904]
Here's the stack trace for this last one:
{noformat}
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.NetSearchMessagingDUnitTest$14.run in VM 0
running on Host 6eb2688a8d32 with 4 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:450)
at org.apache.geode.test.dunit.VM.invoke(VM.java:419)
at org.apache.geode.test.dunit.VM.invoke(VM.java:362)
at
org.apache.geode.internal.cache.NetSearchMessagingDUnitTest.createReplicate(NetSearchMessagingDUnitTest.java:405)
at
org.apache.geode.internal.cache.NetSearchMessagingDUnitTest.testOneMessageWithReplicates(NetSearchMessagingDUnitTest.java:57)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
at
org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
[jira] [Reopened] (GEODE-5501) CI Failure: NetSearchMessagingDUnitTest.testOneMessageWithReplicates
[
https://issues.apache.org/jira/browse/GEODE-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill reopened GEODE-5501:
-
occurred again in mass test run. here is an example failure:
https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/921
> CI Failure: NetSearchMessagingDUnitTest.testOneMessageWithReplicates
>
>
> Key: GEODE-5501
> URL: https://issues.apache.org/jira/browse/GEODE-5501
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Priority: Major
> Labels: pull-request-available, swat
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.NetSearchMessagingDUnitTest$14.run in VM 0
> running on Host 4fad81dffa5f with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:443)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:412)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:355)
> at
> org.apache.geode.internal.cache.NetSearchMessagingDUnitTest.createReplicate(NetSearchMessagingDUnitTest.java:425)
> at
> org.apache.geode.internal.cache.NetSearchMessagingDUnitTest.testOneMessageWithReplicates(NetSearchMessagingDUnitTest.java:57)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
> at
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy1.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
>
[jira] [Updated] (GEODE-5595) CI: DeltaPropagationDUnit.testBug40165ClientReconnects - NoSubscriptionServersAvailableException
[
https://issues.apache.org/jira/browse/GEODE-5595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill updated GEODE-5595:
Description:
This test failed. See _Issue Links_ section below for a bunch of other tests
that seem to fail due to the same underlying product fault. See [~klund]'s
analysis cited in the comment section for that underlying fault. Don't mark
this ticket resolved until that product problem is really fixed please.
{code:java}
org.apache.geode.internal.cache.DeltaPropagationDUnitTest >
testBug40165ClientReconnects FAILED
org.apache.geode.cache.NoSubscriptionServersAvailableException:
org.apache.geode.cache.NoSubscriptionServersAvailableException: Could not
initialize a primary queue on startup. No queue servers available.
at
org.apache.geode.cache.client.internal.QueueManagerImpl.getAllConnections(QueueManagerImpl.java:187)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnQueuesAndReturnPrimaryResult(OpExecutorImpl.java:548)
at
org.apache.geode.cache.client.internal.PoolImpl.executeOnQueuesAndReturnPrimaryResult(PoolImpl.java:855)
at
org.apache.geode.cache.client.internal.RegisterInterestOp.execute(RegisterInterestOp.java:58)
at
org.apache.geode.cache.client.internal.ServerRegionProxy.registerInterest(ServerRegionProxy.java:355)
at
org.apache.geode.internal.cache.LocalRegion.processSingleInterest(LocalRegion.java:3797)
at
org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3888)
at
org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3686)
at
org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3681)
at
org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3676)
at
org.apache.geode.internal.cache.DeltaPropagationDUnitTest.createDurableCacheClient(DeltaPropagationDUnitTest.java:1305)
at
org.apache.geode.internal.cache.DeltaPropagationDUnitTest.testBug40165ClientReconnects(DeltaPropagationDUnitTest.java:647)
Caused by:
org.apache.geode.cache.NoSubscriptionServersAvailableException: Could
not initialize a primary queue on startup. No queue servers available.
at
org.apache.geode.cache.client.internal.QueueManagerImpl.initializeConnections(QueueManagerImpl.java:585)
at
org.apache.geode.cache.client.internal.QueueManagerImpl.start(QueueManagerImpl.java:296)
at
org.apache.geode.cache.client.internal.PoolImpl.start(PoolImpl.java:352)
at
org.apache.geode.cache.client.internal.PoolImpl.finishCreate(PoolImpl.java:176)
at
org.apache.geode.cache.client.internal.PoolImpl.create(PoolImpl.java:162)
at
org.apache.geode.internal.cache.PoolFactoryImpl.create(PoolFactoryImpl.java:349)
at
org.apache.geode.internal.cache.DeltaPropagationDUnitTest.createDurableCacheClient(DeltaPropagationDUnitTest.java:1295)
... 1 more
{code}
was:
{code:java}
org.apache.geode.internal.cache.DeltaPropagationDUnitTest >
testBug40165ClientReconnects FAILED
org.apache.geode.cache.NoSubscriptionServersAvailableException:
org.apache.geode.cache.NoSubscriptionServersAvailableException: Could not
initialize a primary queue on startup. No queue servers available.
at
org.apache.geode.cache.client.internal.QueueManagerImpl.getAllConnections(QueueManagerImpl.java:187)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnQueuesAndReturnPrimaryResult(OpExecutorImpl.java:548)
at
org.apache.geode.cache.client.internal.PoolImpl.executeOnQueuesAndReturnPrimaryResult(PoolImpl.java:855)
at
org.apache.geode.cache.client.internal.RegisterInterestOp.execute(RegisterInterestOp.java:58)
at
org.apache.geode.cache.client.internal.ServerRegionProxy.registerInterest(ServerRegionProxy.java:355)
at
org.apache.geode.internal.cache.LocalRegion.processSingleInterest(LocalRegion.java:3797)
at
org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3888)
at
org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3686)
at
org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3681)
at
org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3676)
at
org.apache.geode.internal.cache.DeltaPropagationDUnitTest.createDurableCacheClient(DeltaPropagationDUnitTest.java:1305)
at
[jira] [Resolved] (GEODE-3742) CI failure: DeltaPropagationDUnitTest.testBug40165ClientReconnects FAILED with no queus server is available
[
https://issues.apache.org/jira/browse/GEODE-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill resolved GEODE-3742.
-
Resolution: Duplicate
> CI failure: DeltaPropagationDUnitTest.testBug40165ClientReconnects FAILED
> with no queus server is available
> ---
>
> Key: GEODE-3742
> URL: https://issues.apache.org/jira/browse/GEODE-3742
> Project: Geode
> Issue Type: Bug
> Components: client queues
>Reporter: Hitesh Khamesra
>Priority: Major
>
> {noformat}
> org.apache.geode.internal.cache.DeltaPropagationDUnitTest >
> testBug40165ClientReconnects FAILED
> org.apache.geode.cache.NoSubscriptionServersAvailableException:
> org.apache.geode.cache.NoSubscriptionServersAvailableException: Could not
> initialize a primary queue on startup. No queue servers available.
> at
> org.apache.geode.cache.client.internal.QueueManagerImpl.getAllConnections(QueueManagerImpl.java:190)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnQueuesAndReturnPrimaryResult(OpExecutorImpl.java:540)
> at
> org.apache.geode.cache.client.internal.PoolImpl.executeOnQueuesAndReturnPrimaryResult(PoolImpl.java:842)
> at
> org.apache.geode.cache.client.internal.RegisterInterestOp.execute(RegisterInterestOp.java:58)
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.registerInterest(ServerRegionProxy.java:359)
> at
> org.apache.geode.internal.cache.LocalRegion.processSingleInterest(LocalRegion.java:3734)
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3823)
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3625)
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3620)
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3615)
> at
> org.apache.geode.internal.cache.DeltaPropagationDUnitTest.createDurableCacheClient(DeltaPropagationDUnitTest.java:1372)
> at
> org.apache.geode.internal.cache.DeltaPropagationDUnitTest.testBug40165ClientReconnects(DeltaPropagationDUnitTest.java:698)
> Caused by:
> org.apache.geode.cache.NoSubscriptionServersAvailableException: Could
> not initialize a primary queue on startup. No queue servers available.
> at
> org.apache.geode.cache.client.internal.QueueManagerImpl.initializeConnections(QueueManagerImpl.java:592)
> at
> org.apache.geode.cache.client.internal.QueueManagerImpl.start(QueueManagerImpl.java:303)
> at
> org.apache.geode.cache.client.internal.PoolImpl.start(PoolImpl.java:346)
> at
> org.apache.geode.cache.client.internal.PoolImpl.finishCreate(PoolImpl.java:172)
> at
> org.apache.geode.cache.client.internal.PoolImpl.create(PoolImpl.java:158)
> at
> org.apache.geode.internal.cache.PoolFactoryImpl.create(PoolFactoryImpl.java:338)
> at
> org.apache.geode.internal.cache.DeltaPropagationDUnitTest.createDurableCacheClient(DeltaPropagationDUnitTest.java:1362)
> ... 1 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (GEODE-5595) CI: DeltaPropagationDUnit.testBug40165ClientReconnects - NoSubscriptionServersAvailableException
[
https://issues.apache.org/jira/browse/GEODE-5595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637295#comment-16637295
]
Bill edited comment on GEODE-5595 at 10/3/18 6:04 PM:
--
six failures in mass-test-run completed around 10/1/2018. Here's one:
https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/981
Not only that, but there are a slew of tickets over the past two years,
pertaining to this same test. Broken, fixed, broken again.
Interestingly, searching for the error message turns up 9 bugs (5
open!), including on current SWAT bug:
https://issues.apache.org/jira/issues/?jql=text%20~%20%22%5C%22NoSubscriptionServersAvailableException%3A%20Could%20not%20initialize%20a%20primary%20queue%20on%20startup%5C%22%22%20ORDER%20BY%20key%20ASC%2C%20created%20DESC
and searching for the test method name turns up a list of 6 tickets (2
open!) with some overlap:
https://issues.apache.org/jira/issues/?jql=text%20~%20testBug40165ClientReconnects%20ORDER%20BY%20key%20ASC%2C%20created%20DESC
[~klund]'s comment
https://issues.apache.org/jira/browse/GEODE-3742?focusedCommentId=16469482=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16469482
is apt:
{quote}Every dunit or integrationTest that creates durable cache clients is
intermittently hitting this same failure. One example is GEODE-5177 – to fix
that ticket I simply removed use of durable client queue which wasn't necessary
for InitializedDiskRegionWithIoExceptionRegressionTest.{quote}
was (Author: bburcham):
six failures in mass-test-run completed around 10/1/2018. Here's one:
https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/981
Not only that, but there are a slew of tickets over the past two years,
pertaining to this same test. Broken, fixed, broken again.
Interestingly, searching for the error message turns up 9 bugs (5
open!), including on current SWAT bug:
https://issues.apache.org/jira/issues/?jql=text%20~%20%22%5C%22NoSubscriptionServersAvailableException%3A%20Could%20not%20initialize%20a%20primary%20queue%20on%20startup%5C%22%22%20ORDER%20BY%20key%20ASC%2C%20created%20DESC
and searching for the test method name turns up a list of 6 tickets (2
open!) with some overlap:
https://issues.apache.org/jira/issues/?jql=text%20~%20testBug40165ClientReconnects%20ORDER%20BY%20key%20ASC%2C%20created%20DESC
[~klund]'s comment
https://issues.apache.org/jira/browse/GEODE-3742?focusedCommentId=16469482=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16469482
is apt
> CI: DeltaPropagationDUnit.testBug40165ClientReconnects -
> NoSubscriptionServersAvailableException
>
>
> Key: GEODE-5595
> URL: https://issues.apache.org/jira/browse/GEODE-5595
> Project: Geode
> Issue Type: Bug
>Reporter: Kenneth Howe
>Priority: Major
> Labels: swat
>
> {code:java}
> org.apache.geode.internal.cache.DeltaPropagationDUnitTest >
> testBug40165ClientReconnects FAILED
>
> org.apache.geode.cache.NoSubscriptionServersAvailableException:
> org.apache.geode.cache.NoSubscriptionServersAvailableException: Could not
> initialize a primary queue on startup. No queue servers available.
>
> at
> org.apache.geode.cache.client.internal.QueueManagerImpl.getAllConnections(QueueManagerImpl.java:187)
>
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnQueuesAndReturnPrimaryResult(OpExecutorImpl.java:548)
>
> at
> org.apache.geode.cache.client.internal.PoolImpl.executeOnQueuesAndReturnPrimaryResult(PoolImpl.java:855)
>
> at
> org.apache.geode.cache.client.internal.RegisterInterestOp.execute(RegisterInterestOp.java:58)
>
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.registerInterest(ServerRegionProxy.java:355)
>
> at
> org.apache.geode.internal.cache.LocalRegion.processSingleInterest(LocalRegion.java:3797)
>
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3888)
>
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3686)
>
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3681)
>
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3676)
>
> at
> org.apache.geode.internal.cache.DeltaPropagationDUnitTest.createDurableCacheClient(DeltaPropagationDUnitTest.java:1305)
>
> at
>
[jira] [Comment Edited] (GEODE-5595) CI: DeltaPropagationDUnit.testBug40165ClientReconnects - NoSubscriptionServersAvailableException
[
https://issues.apache.org/jira/browse/GEODE-5595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637295#comment-16637295
]
Bill edited comment on GEODE-5595 at 10/3/18 6:03 PM:
--
six failures in mass-test-run completed around 10/1/2018. Here's one:
https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/981
Not only that, but there are a slew of tickets over the past two years,
pertaining to this same test. Broken, fixed, broken again.
Interestingly, searching for the error message turns up 9 bugs (5
open!), including on current SWAT bug:
https://issues.apache.org/jira/issues/?jql=text%20~%20%22%5C%22NoSubscriptionServersAvailableException%3A%20Could%20not%20initialize%20a%20primary%20queue%20on%20startup%5C%22%22%20ORDER%20BY%20key%20ASC%2C%20created%20DESC
and searching for the test method name turns up a list of 6 tickets (2
open!) with some overlap:
https://issues.apache.org/jira/issues/?jql=text%20~%20testBug40165ClientReconnects%20ORDER%20BY%20key%20ASC%2C%20created%20DESC
[~klund]'s comment
https://issues.apache.org/jira/browse/GEODE-3742?focusedCommentId=16469482=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16469482
is apt
was (Author: bburcham):
six failures in mass-test-run completed around 10/1/2018. Here's one:
https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/981
Not only that, but there are a slew of tickets over the past two years,
pertaining to this same test. Broken, fixed, broken again.
Interestingly, searching for the error message turns up 9 bugs (5
open!), including on current SWAT bug:
https://issues.apache.org/jira/issues/?jql=text%20~%20%22%5C%22NoSubscriptionServersAvailableException%3A%20Could%20not%20initialize%20a%20primary%20queue%20on%20startup%5C%22%22%20ORDER%20BY%20key%20ASC%2C%20created%20DESC
and searching for the test method name turns up a list of 6 tickets (2
open!) with some overlap:
https://issues.apache.org/jira/issues/?jql=text%20~%20testBug40165ClientReconnects%20ORDER%20BY%20key%20ASC%2C%20created%20DESC
> CI: DeltaPropagationDUnit.testBug40165ClientReconnects -
> NoSubscriptionServersAvailableException
>
>
> Key: GEODE-5595
> URL: https://issues.apache.org/jira/browse/GEODE-5595
> Project: Geode
> Issue Type: Bug
>Reporter: Kenneth Howe
>Priority: Major
> Labels: swat
>
> {code:java}
> org.apache.geode.internal.cache.DeltaPropagationDUnitTest >
> testBug40165ClientReconnects FAILED
>
> org.apache.geode.cache.NoSubscriptionServersAvailableException:
> org.apache.geode.cache.NoSubscriptionServersAvailableException: Could not
> initialize a primary queue on startup. No queue servers available.
>
> at
> org.apache.geode.cache.client.internal.QueueManagerImpl.getAllConnections(QueueManagerImpl.java:187)
>
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnQueuesAndReturnPrimaryResult(OpExecutorImpl.java:548)
>
> at
> org.apache.geode.cache.client.internal.PoolImpl.executeOnQueuesAndReturnPrimaryResult(PoolImpl.java:855)
>
> at
> org.apache.geode.cache.client.internal.RegisterInterestOp.execute(RegisterInterestOp.java:58)
>
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.registerInterest(ServerRegionProxy.java:355)
>
> at
> org.apache.geode.internal.cache.LocalRegion.processSingleInterest(LocalRegion.java:3797)
>
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3888)
>
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3686)
>
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3681)
>
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3676)
>
> at
> org.apache.geode.internal.cache.DeltaPropagationDUnitTest.createDurableCacheClient(DeltaPropagationDUnitTest.java:1305)
>
> at
> org.apache.geode.internal.cache.DeltaPropagationDUnitTest.testBug40165ClientReconnects(DeltaPropagationDUnitTest.java:647)
>
>
> Caused by:
>
> org.apache.geode.cache.NoSubscriptionServersAvailableException: Could
> not initialize a primary queue on startup. No queue servers available.
>
> at
> org.apache.geode.cache.client.internal.QueueManagerImpl.initializeConnections(QueueManagerImpl.java:585)
>
> at
> org.apache.geode.cache.client.internal.QueueManagerImpl.start(QueueManagerImpl.java:296)
>
[jira] [Comment Edited] (GEODE-5595) CI: DeltaPropagationDUnit.testBug40165ClientReconnects - NoSubscriptionServersAvailableException
[
https://issues.apache.org/jira/browse/GEODE-5595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637295#comment-16637295
]
Bill edited comment on GEODE-5595 at 10/3/18 5:55 PM:
--
six failures in mass-test-run completed around 10/1/2018. Here's one:
https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/981
Not only that, but there are a slew of tickets over the past two years,
pertaining to this same test. Broken, fixed, broken again.
Interestingly, searching for the error message turns up 9 bugs (5
open!), including on current SWAT bug:
https://issues.apache.org/jira/issues/?jql=text%20~%20%22%5C%22NoSubscriptionServersAvailableException%3A%20Could%20not%20initialize%20a%20primary%20queue%20on%20startup%5C%22%22%20ORDER%20BY%20key%20ASC%2C%20created%20DESC
and searching for the test method name turns up a list of 6 tickets (2
open!) with some overlap:
https://issues.apache.org/jira/issues/?jql=text%20~%20testBug40165ClientReconnects%20ORDER%20BY%20key%20ASC%2C%20created%20DESC
was (Author: bburcham):
six failures in mass-test-run completed around 10/1/2018. Here's one:
https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/981
> CI: DeltaPropagationDUnit.testBug40165ClientReconnects -
> NoSubscriptionServersAvailableException
>
>
> Key: GEODE-5595
> URL: https://issues.apache.org/jira/browse/GEODE-5595
> Project: Geode
> Issue Type: Bug
>Reporter: Kenneth Howe
>Priority: Major
> Labels: swat
>
> {code:java}
> org.apache.geode.internal.cache.DeltaPropagationDUnitTest >
> testBug40165ClientReconnects FAILED
>
> org.apache.geode.cache.NoSubscriptionServersAvailableException:
> org.apache.geode.cache.NoSubscriptionServersAvailableException: Could not
> initialize a primary queue on startup. No queue servers available.
>
> at
> org.apache.geode.cache.client.internal.QueueManagerImpl.getAllConnections(QueueManagerImpl.java:187)
>
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnQueuesAndReturnPrimaryResult(OpExecutorImpl.java:548)
>
> at
> org.apache.geode.cache.client.internal.PoolImpl.executeOnQueuesAndReturnPrimaryResult(PoolImpl.java:855)
>
> at
> org.apache.geode.cache.client.internal.RegisterInterestOp.execute(RegisterInterestOp.java:58)
>
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.registerInterest(ServerRegionProxy.java:355)
>
> at
> org.apache.geode.internal.cache.LocalRegion.processSingleInterest(LocalRegion.java:3797)
>
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3888)
>
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3686)
>
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3681)
>
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3676)
>
> at
> org.apache.geode.internal.cache.DeltaPropagationDUnitTest.createDurableCacheClient(DeltaPropagationDUnitTest.java:1305)
>
> at
> org.apache.geode.internal.cache.DeltaPropagationDUnitTest.testBug40165ClientReconnects(DeltaPropagationDUnitTest.java:647)
>
>
> Caused by:
>
> org.apache.geode.cache.NoSubscriptionServersAvailableException: Could
> not initialize a primary queue on startup. No queue servers available.
>
> at
> org.apache.geode.cache.client.internal.QueueManagerImpl.initializeConnections(QueueManagerImpl.java:585)
>
> at
> org.apache.geode.cache.client.internal.QueueManagerImpl.start(QueueManagerImpl.java:296)
>
> at
> org.apache.geode.cache.client.internal.PoolImpl.start(PoolImpl.java:352)
>
> at
> org.apache.geode.cache.client.internal.PoolImpl.finishCreate(PoolImpl.java:176)
>
> at
> org.apache.geode.cache.client.internal.PoolImpl.create(PoolImpl.java:162)
>
> at
> org.apache.geode.internal.cache.PoolFactoryImpl.create(PoolFactoryImpl.java:349)
>
> at
> org.apache.geode.internal.cache.DeltaPropagationDUnitTest.createDurableCacheClient(DeltaPropagationDUnitTest.java:1295)
>
> ... 1 more
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5595) CI: DeltaPropagationDUnit.testBug40165ClientReconnects - NoSubscriptionServersAvailableException
[
https://issues.apache.org/jira/browse/GEODE-5595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16637295#comment-16637295
]
Bill commented on GEODE-5595:
-
six failures in mass-test-run completed around 10/1/2018. Here's one:
https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/981
> CI: DeltaPropagationDUnit.testBug40165ClientReconnects -
> NoSubscriptionServersAvailableException
>
>
> Key: GEODE-5595
> URL: https://issues.apache.org/jira/browse/GEODE-5595
> Project: Geode
> Issue Type: Bug
>Reporter: Kenneth Howe
>Priority: Major
> Labels: swat
>
> {code:java}
> org.apache.geode.internal.cache.DeltaPropagationDUnitTest >
> testBug40165ClientReconnects FAILED
>
> org.apache.geode.cache.NoSubscriptionServersAvailableException:
> org.apache.geode.cache.NoSubscriptionServersAvailableException: Could not
> initialize a primary queue on startup. No queue servers available.
>
> at
> org.apache.geode.cache.client.internal.QueueManagerImpl.getAllConnections(QueueManagerImpl.java:187)
>
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnQueuesAndReturnPrimaryResult(OpExecutorImpl.java:548)
>
> at
> org.apache.geode.cache.client.internal.PoolImpl.executeOnQueuesAndReturnPrimaryResult(PoolImpl.java:855)
>
> at
> org.apache.geode.cache.client.internal.RegisterInterestOp.execute(RegisterInterestOp.java:58)
>
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.registerInterest(ServerRegionProxy.java:355)
>
> at
> org.apache.geode.internal.cache.LocalRegion.processSingleInterest(LocalRegion.java:3797)
>
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3888)
>
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3686)
>
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3681)
>
> at
> org.apache.geode.internal.cache.LocalRegion.registerInterest(LocalRegion.java:3676)
>
> at
> org.apache.geode.internal.cache.DeltaPropagationDUnitTest.createDurableCacheClient(DeltaPropagationDUnitTest.java:1305)
>
> at
> org.apache.geode.internal.cache.DeltaPropagationDUnitTest.testBug40165ClientReconnects(DeltaPropagationDUnitTest.java:647)
>
>
> Caused by:
>
> org.apache.geode.cache.NoSubscriptionServersAvailableException: Could
> not initialize a primary queue on startup. No queue servers available.
>
> at
> org.apache.geode.cache.client.internal.QueueManagerImpl.initializeConnections(QueueManagerImpl.java:585)
>
> at
> org.apache.geode.cache.client.internal.QueueManagerImpl.start(QueueManagerImpl.java:296)
>
> at
> org.apache.geode.cache.client.internal.PoolImpl.start(PoolImpl.java:352)
>
> at
> org.apache.geode.cache.client.internal.PoolImpl.finishCreate(PoolImpl.java:176)
>
> at
> org.apache.geode.cache.client.internal.PoolImpl.create(PoolImpl.java:162)
>
> at
> org.apache.geode.internal.cache.PoolFactoryImpl.create(PoolFactoryImpl.java:349)
>
> at
> org.apache.geode.internal.cache.DeltaPropagationDUnitTest.createDurableCacheClient(DeltaPropagationDUnitTest.java:1295)
>
> ... 1 more
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5813) Serialization filter is rejecting class ConditionTimeoutException
[
https://issues.apache.org/jira/browse/GEODE-5813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill updated GEODE-5813:
Description:
In mass-test-run
QueryMonitorDUnitTest. testQueryMonitorRegionWithEviction failed on four runs.
Here's one:
https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/652
Looks like the DUnit test has serialized a ConditionTimeoutException, which
causes an exception on the server during deserialization.
{noformat}
java.lang.AssertionError: Suspicious strings were written to the log during
this run.
Fix the strings or use IgnoredException.addIgnoredException to ignore.
---
Found suspect string in log4j at line 1130
[fatal 2018/09/28 02:22:42.272 UTC
tid=0x20] Serialization filter is rejecting class
org.awaitility.core.ConditionTimeoutException
java.lang.Exception:
at
org.apache.geode.internal.ObjectInputStreamFilterWrapper.lambda$createSerializationFilter$0(ObjectInputStreamFilterWrapper.java:225)
at com.sun.proxy.$Proxy26.checkInput(Unknown Source)
at java.io.ObjectInputStream.filterCheck(ObjectInputStream.java:1239)
at
java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1878)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1751)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2042)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1573)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:431)
at
org.apache.geode.internal.InternalDataSerializer.readSerializable(InternalDataSerializer.java:2962)
at
org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2906)
at org.apache.geode.DataSerializer.readObject(DataSerializer.java:2977)
at
org.apache.geode.internal.util.BlobHelper.deserializeBlob(BlobHelper.java:99)
at
org.apache.geode.internal.cache.tier.sockets.CacheServerHelper.deserialize(CacheServerHelper.java:74)
at
org.apache.geode.internal.cache.tier.sockets.Part.getObject(Part.java:267)
at
org.apache.geode.internal.cache.tier.sockets.Part.getObject(Part.java:275)
at
org.apache.geode.cache.client.internal.AbstractOp.processChunkedResponse(AbstractOp.java:345)
at
org.apache.geode.cache.client.internal.QueryOp$QueryOpImpl.processResponse(QueryOp.java:171)
at
org.apache.geode.cache.client.internal.AbstractOp.processResponse(AbstractOp.java:225)
at
org.apache.geode.cache.client.internal.AbstractOp.attemptReadResponse(AbstractOp.java:198)
at
org.apache.geode.cache.client.internal.AbstractOp.attempt(AbstractOp.java:386)
at
org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:276)
at
org.apache.geode.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:325)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:894)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:171)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:128)
at
org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:787)
at
org.apache.geode.cache.client.internal.QueryOp.execute(QueryOp.java:59)
at
org.apache.geode.cache.client.internal.ServerProxy.query(ServerProxy.java:69)
at
org.apache.geode.cache.query.internal.DefaultQuery.executeOnServer(DefaultQuery.java:341)
at
org.apache.geode.cache.query.internal.DefaultQuery.execute(DefaultQuery.java:222)
at
org.apache.geode.cache.query.internal.DefaultQuery.execute(DefaultQuery.java:203)
at
org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.exuteQuery(QueryMonitorDUnitTest.java:360)
at
org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.lambda$testQueryMonitorRegionWithEviction$bb17a952$4(QueryMonitorDUnitTest.java:210)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at hydra.MethExecutor.executeObject(MethExecutor.java:244)
at
org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at
[jira] [Updated] (GEODE-5813) Serialization filter is rejecting class ConditionTimeoutException
[
https://issues.apache.org/jira/browse/GEODE-5813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill updated GEODE-5813:
Labels: swat (was: )
> Serialization filter is rejecting class ConditionTimeoutException
> -
>
> Key: GEODE-5813
> URL: https://issues.apache.org/jira/browse/GEODE-5813
> Project: Geode
> Issue Type: Bug
>Reporter: Bill
>Priority: Major
> Labels: swat
>
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 1130
> [fatal 2018/09/28 02:22:42.272 UTC
> tid=0x20] Serialization filter is rejecting class
> org.awaitility.core.ConditionTimeoutException
> java.lang.Exception:
> at
> org.apache.geode.internal.ObjectInputStreamFilterWrapper.lambda$createSerializationFilter$0(ObjectInputStreamFilterWrapper.java:225)
> at com.sun.proxy.$Proxy26.checkInput(Unknown Source)
> at java.io.ObjectInputStream.filterCheck(ObjectInputStream.java:1239)
> at
> java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1878)
> at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1751)
> at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2042)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1573)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:431)
> at
> org.apache.geode.internal.InternalDataSerializer.readSerializable(InternalDataSerializer.java:2962)
> at
> org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2906)
> at org.apache.geode.DataSerializer.readObject(DataSerializer.java:2977)
> at
> org.apache.geode.internal.util.BlobHelper.deserializeBlob(BlobHelper.java:99)
> at
> org.apache.geode.internal.cache.tier.sockets.CacheServerHelper.deserialize(CacheServerHelper.java:74)
> at
> org.apache.geode.internal.cache.tier.sockets.Part.getObject(Part.java:267)
> at
> org.apache.geode.internal.cache.tier.sockets.Part.getObject(Part.java:275)
> at
> org.apache.geode.cache.client.internal.AbstractOp.processChunkedResponse(AbstractOp.java:345)
> at
> org.apache.geode.cache.client.internal.QueryOp$QueryOpImpl.processResponse(QueryOp.java:171)
> at
> org.apache.geode.cache.client.internal.AbstractOp.processResponse(AbstractOp.java:225)
> at
> org.apache.geode.cache.client.internal.AbstractOp.attemptReadResponse(AbstractOp.java:198)
> at
> org.apache.geode.cache.client.internal.AbstractOp.attempt(AbstractOp.java:386)
> at
> org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:276)
> at
> org.apache.geode.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:325)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:894)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:171)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:128)
> at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:787)
> at
> org.apache.geode.cache.client.internal.QueryOp.execute(QueryOp.java:59)
> at
> org.apache.geode.cache.client.internal.ServerProxy.query(ServerProxy.java:69)
> at
> org.apache.geode.cache.query.internal.DefaultQuery.executeOnServer(DefaultQuery.java:341)
> at
> org.apache.geode.cache.query.internal.DefaultQuery.execute(DefaultQuery.java:222)
> at
> org.apache.geode.cache.query.internal.DefaultQuery.execute(DefaultQuery.java:203)
> at
> org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.exuteQuery(QueryMonitorDUnitTest.java:360)
> at
> org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.lambda$testQueryMonitorRegionWithEviction$bb17a952$4(QueryMonitorDUnitTest.java:210)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at hydra.MethExecutor.executeObject(MethExecutor.java:244)
> at
> org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>
[jira] [Created] (GEODE-5813) Serialization filter is rejecting class ConditionTimeoutException
Bill created GEODE-5813:
---
Summary: Serialization filter is rejecting class
ConditionTimeoutException
Key: GEODE-5813
URL: https://issues.apache.org/jira/browse/GEODE-5813
Project: Geode
Issue Type: Bug
Reporter: Bill
{noformat}
java.lang.AssertionError: Suspicious strings were written to the log during
this run.
Fix the strings or use IgnoredException.addIgnoredException to ignore.
---
Found suspect string in log4j at line 1130
[fatal 2018/09/28 02:22:42.272 UTC
tid=0x20] Serialization filter is rejecting class
org.awaitility.core.ConditionTimeoutException
java.lang.Exception:
at
org.apache.geode.internal.ObjectInputStreamFilterWrapper.lambda$createSerializationFilter$0(ObjectInputStreamFilterWrapper.java:225)
at com.sun.proxy.$Proxy26.checkInput(Unknown Source)
at java.io.ObjectInputStream.filterCheck(ObjectInputStream.java:1239)
at
java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1878)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1751)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:2042)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1573)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:431)
at
org.apache.geode.internal.InternalDataSerializer.readSerializable(InternalDataSerializer.java:2962)
at
org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2906)
at org.apache.geode.DataSerializer.readObject(DataSerializer.java:2977)
at
org.apache.geode.internal.util.BlobHelper.deserializeBlob(BlobHelper.java:99)
at
org.apache.geode.internal.cache.tier.sockets.CacheServerHelper.deserialize(CacheServerHelper.java:74)
at
org.apache.geode.internal.cache.tier.sockets.Part.getObject(Part.java:267)
at
org.apache.geode.internal.cache.tier.sockets.Part.getObject(Part.java:275)
at
org.apache.geode.cache.client.internal.AbstractOp.processChunkedResponse(AbstractOp.java:345)
at
org.apache.geode.cache.client.internal.QueryOp$QueryOpImpl.processResponse(QueryOp.java:171)
at
org.apache.geode.cache.client.internal.AbstractOp.processResponse(AbstractOp.java:225)
at
org.apache.geode.cache.client.internal.AbstractOp.attemptReadResponse(AbstractOp.java:198)
at
org.apache.geode.cache.client.internal.AbstractOp.attempt(AbstractOp.java:386)
at
org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:276)
at
org.apache.geode.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:325)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:894)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:171)
at
org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:128)
at
org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:787)
at
org.apache.geode.cache.client.internal.QueryOp.execute(QueryOp.java:59)
at
org.apache.geode.cache.client.internal.ServerProxy.query(ServerProxy.java:69)
at
org.apache.geode.cache.query.internal.DefaultQuery.executeOnServer(DefaultQuery.java:341)
at
org.apache.geode.cache.query.internal.DefaultQuery.execute(DefaultQuery.java:222)
at
org.apache.geode.cache.query.internal.DefaultQuery.execute(DefaultQuery.java:203)
at
org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.exuteQuery(QueryMonitorDUnitTest.java:360)
at
org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.lambda$testQueryMonitorRegionWithEviction$bb17a952$4(QueryMonitorDUnitTest.java:210)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at hydra.MethExecutor.executeObject(MethExecutor.java:244)
at
org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
at sun.rmi.transport.Transport$1.run(Transport.java:200)
at
[jira] [Commented] (GEODE-5568) testCacheOpAfterQueryCancel in QueryMonitorDUnitTest is potentially flaky
[
https://issues.apache.org/jira/browse/GEODE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636247#comment-16636247
]
Bill commented on GEODE-5568:
-
We saw this four times in mass-test-run. Here's one example:
https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/883
{noformat}
java.lang.AssertionError: An exception occurred during asynchronous invocation.
at
org.apache.geode.test.dunit.AsyncInvocation.checkException(AsyncInvocation.java:139)
at
org.apache.geode.test.dunit.AsyncInvocation.await(AsyncInvocation.java:332)
at
org.apache.geode.test.dunit.AsyncInvocation.await(AsyncInvocation.java:355)
at
org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.testCacheOpAfterQueryCancel(QueryMonitorDUnitTest.java:333)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at
org.apache.geode.test.junit.rules.DescribedExternalResource$1.evaluate(DescribedExternalResource.java:40)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
at
org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at
org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:117)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:155)
at
[jira] [Issue Comment Deleted] (GEODE-5568) testCacheOpAfterQueryCancel in QueryMonitorDUnitTest is potentially flaky
[ https://issues.apache.org/jira/browse/GEODE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill updated GEODE-5568: Comment: was deleted (was: these two may represent the same failure) > testCacheOpAfterQueryCancel in QueryMonitorDUnitTest is potentially flaky > - > > Key: GEODE-5568 > URL: https://issues.apache.org/jira/browse/GEODE-5568 > Project: Geode > Issue Type: Test > Components: tests >Reporter: Michael Oleske >Priority: Major > Labels: swat > > *We* should remove flakiness from test > *Before* we add more features around Query Monitor > *Because* flaky tests do not inspire confidence > *Notes* > When running [PR 2311|https://github.com/apache/geode/pull/2311], a test > failed that passed on a rerun (see > [here|http://files.apachegeode-ci.info/builds/geode-pr-2311/test-results/distributedTest/1534096152/classes/org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.html#testCacheOpAfterQueryCancel]) > The build artifacts are available > [here|http://files.apachegeode-ci.info/builds/geode-pr-2311/test-artifacts/1534096152/distributedtestfiles-geode-pr-2311.tgz] > Since it is a timing issue, it could be a few things so not sure on best path > forward. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5568) testCacheOpAfterQueryCancel in QueryMonitorDUnitTest is potentially flaky
[ https://issues.apache.org/jira/browse/GEODE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill updated GEODE-5568: Labels: swat (was: ) > testCacheOpAfterQueryCancel in QueryMonitorDUnitTest is potentially flaky > - > > Key: GEODE-5568 > URL: https://issues.apache.org/jira/browse/GEODE-5568 > Project: Geode > Issue Type: Test > Components: tests >Reporter: Michael Oleske >Priority: Major > Labels: swat > > *We* should remove flakiness from test > *Before* we add more features around Query Monitor > *Because* flaky tests do not inspire confidence > *Notes* > When running [PR 2311|https://github.com/apache/geode/pull/2311], a test > failed that passed on a rerun (see > [here|http://files.apachegeode-ci.info/builds/geode-pr-2311/test-results/distributedTest/1534096152/classes/org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.html#testCacheOpAfterQueryCancel]) > The build artifacts are available > [here|http://files.apachegeode-ci.info/builds/geode-pr-2311/test-artifacts/1534096152/distributedtestfiles-geode-pr-2311.tgz] > Since it is a timing issue, it could be a few things so not sure on best path > forward. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5568) testCacheOpAfterQueryCancel in QueryMonitorDUnitTest is potentially flaky
[ https://issues.apache.org/jira/browse/GEODE-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636242#comment-16636242 ] Bill commented on GEODE-5568: - these two may represent the same failure > testCacheOpAfterQueryCancel in QueryMonitorDUnitTest is potentially flaky > - > > Key: GEODE-5568 > URL: https://issues.apache.org/jira/browse/GEODE-5568 > Project: Geode > Issue Type: Test > Components: tests >Reporter: Michael Oleske >Priority: Major > > *We* should remove flakiness from test > *Before* we add more features around Query Monitor > *Because* flaky tests do not inspire confidence > *Notes* > When running [PR 2311|https://github.com/apache/geode/pull/2311], a test > failed that passed on a rerun (see > [here|http://files.apachegeode-ci.info/builds/geode-pr-2311/test-results/distributedTest/1534096152/classes/org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.html#testCacheOpAfterQueryCancel]) > The build artifacts are available > [here|http://files.apachegeode-ci.info/builds/geode-pr-2311/test-artifacts/1534096152/distributedtestfiles-geode-pr-2311.tgz] > Since it is a timing issue, it could be a few things so not sure on best path > forward. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5121) CI Failure: org.apache.geode.session.tests.Jetty9Test > failureShouldStillAllowOtherContainersDataAccess
[
https://issues.apache.org/jira/browse/GEODE-5121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636190#comment-16636190
]
Bill commented on GEODE-5121:
-
saw this again on mass-test-run:
https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/333
> CI Failure: org.apache.geode.session.tests.Jetty9Test >
> failureShouldStillAllowOtherContainersDataAccess
>
>
> Key: GEODE-5121
> URL: https://issues.apache.org/jira/browse/GEODE-5121
> Project: Geode
> Issue Type: Bug
> Components: http session
>Reporter: Barry Oglesby
>Priority: Major
> Labels: swat
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.6.0/jobs/DistributedTest/builds/10
> [http://files.apachegeode-ci.info/builds/1.6.0-build.9/test-results/distributedTest/1524217535/]
> {noformat}
> java.lang.RuntimeException: Something very bad happened when trying to start
> container
> JETTY9_peer-to-peer_failureShouldStillAllowOtherContainersDataAccess_1_8563772118360307_
> at
> org.apache.geode.session.tests.ContainerManager.startContainer(ContainerManager.java:80)
> at
> org.apache.geode.session.tests.ContainerManager.startContainers(ContainerManager.java:91)
> at
> org.apache.geode.session.tests.ContainerManager.startAllInactiveContainers(ContainerManager.java:98)
> at
> org.apache.geode.session.tests.CargoTestBase.failureShouldStillAllowOtherContainersDataAccess(CargoTestBase.java:136)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
>
[jira] [Updated] (GEODE-5121) CI Failure: org.apache.geode.session.tests.Jetty9Test > failureShouldStillAllowOtherContainersDataAccess
[
https://issues.apache.org/jira/browse/GEODE-5121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill updated GEODE-5121:
Labels: swat (was: )
> CI Failure: org.apache.geode.session.tests.Jetty9Test >
> failureShouldStillAllowOtherContainersDataAccess
>
>
> Key: GEODE-5121
> URL: https://issues.apache.org/jira/browse/GEODE-5121
> Project: Geode
> Issue Type: Bug
> Components: http session
>Reporter: Barry Oglesby
>Priority: Major
> Labels: swat
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.6.0/jobs/DistributedTest/builds/10
> [http://files.apachegeode-ci.info/builds/1.6.0-build.9/test-results/distributedTest/1524217535/]
> {noformat}
> java.lang.RuntimeException: Something very bad happened when trying to start
> container
> JETTY9_peer-to-peer_failureShouldStillAllowOtherContainersDataAccess_1_8563772118360307_
> at
> org.apache.geode.session.tests.ContainerManager.startContainer(ContainerManager.java:80)
> at
> org.apache.geode.session.tests.ContainerManager.startContainers(ContainerManager.java:91)
> at
> org.apache.geode.session.tests.ContainerManager.startAllInactiveContainers(ContainerManager.java:98)
> at
> org.apache.geode.session.tests.CargoTestBase.failureShouldStillAllowOtherContainersDataAccess(CargoTestBase.java:136)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
>
[jira] [Updated] (GEODE-5811) Tomcat tests fail when they can't download zip from archive.apache.org
[
https://issues.apache.org/jira/browse/GEODE-5811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill updated GEODE-5811:
Labels: swat (was: )
> Tomcat tests fail when they can't download zip from archive.apache.org
> --
>
> Key: GEODE-5811
> URL: https://issues.apache.org/jira/browse/GEODE-5811
> Project: Geode
> Issue Type: Bug
>Reporter: Bill
>Priority: Major
> Labels: swat
>
> In the geode-assembly module, it appears that the test sometimes fails to
> download the tomcat zip from archive.apache.org site.
> Would it be possible to not rely on that external site in our test?
> Saw this problem in at least these test classes:
> {noformat}
> Tomcat7ClientServerTest
> Tomcat7Test
> Tomcat8Test
> {noformat}
> During this mass-test-run:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/671
>
> {noformat}
> org.codehaus.cargo.container.ContainerException: Failed to download
> [http://archive.apache.org/dist/tomcat/tomcat-7/v7.0.73/bin/apache-tomcat-7.0.73.zip]
> at
> org.codehaus.cargo.container.installer.ZipURLInstaller.download(ZipURLInstaller.java:456)
> at
> org.codehaus.cargo.container.installer.ZipURLInstaller.install(ZipURLInstaller.java:222)
> at
> org.apache.geode.session.tests.ContainerInstall.(ContainerInstall.java:143)
> at
> org.apache.geode.session.tests.TomcatInstall.(TomcatInstall.java:142)
> at
> org.apache.geode.session.tests.TomcatInstall.(TomcatInstall.java:121)
> at
> org.apache.geode.session.tests.Tomcat7Test.setupTomcatInstall(Tomcat7Test.java:32)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
> at
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:117)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:155)
> at
>
[jira] [Updated] (GEODE-5810) events not drained from secondary queues in testPartitionedParallelPropagationHA test
[
https://issues.apache.org/jira/browse/GEODE-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill updated GEODE-5810:
Description:
There are a number of failures in this test method (in different runs). They
seem to be related…
The test appears to be testing WAN replication by doing puts across
WAN-replicated regions and then looking both for entries to appear in regions
on various servers and also by looking for replication queues to empty.
This failure occurred on mass-test-run in
https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/692:
{noformat}
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderDUnitTest$$Lambda$207/164240.run
in VM 2 running on Host 4edee9492058 with 8 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:450)
at org.apache.geode.test.dunit.VM.invoke(VM.java:419)
at org.apache.geode.test.dunit.VM.invoke(VM.java:362)
at
org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderDUnitTest.testPartitionedParallelPropagationHA(ConcurrentParallelGatewaySenderDUnitTest.java:614)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
at
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
at
org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66)
at
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at
org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at
org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:117)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
[jira] [Commented] (GEODE-5797) CI failure: ConcurrentParallelGatewaySenderDUnitTest.testPartitionedParallelPropagationHA
[
https://issues.apache.org/jira/browse/GEODE-5797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16636146#comment-16636146
]
Bill commented on GEODE-5797:
-
We saw this numerous (approx 5) times in 1000 iteration mass-test-run for
example:
https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/727
> CI failure:
> ConcurrentParallelGatewaySenderDUnitTest.testPartitionedParallelPropagationHA
> -
>
> Key: GEODE-5797
> URL: https://issues.apache.org/jira/browse/GEODE-5797
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Galen O'Sullivan
>Priority: Major
> Labels: swat
>
> at
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/29
> artifacts at
> http://files.apachegeode-ci.info/builds/1.8.0-build.1482/test-artifacts/1538129994/distributedtestfiles-1.8.0-build.1482.tgz
> {noformat}
> org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderDUnitTest
> > testPartitionedParallelPropagationHA FAILED
>
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
>
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
>
> ---
>
> Found suspect string in log4j at line 5853
>
>
> [error 2018/09/28 09:42:18.421 UTC
> tid=0x692] Unexpected exception during bucket recovery
>
> java.lang.IllegalStateException: Region specified in 'colocated-with'
> (/testPartitionedParallelPropagationHA_PR) for region
> /ln_PARALLEL_GATEWAY_SENDER_QUEUE does not exist. It should be created before
> setting 'colocated-with' attribute for this region.
>
> at
> org.apache.geode.internal.cache.ColocationHelper.getColocatedRegion(ColocationHelper.java:94)
>
> at
> org.apache.geode.internal.cache.ColocationHelper.getLeaderRegion(ColocationHelper.java:455)
>
> at
> org.apache.geode.internal.cache.partitioned.PartitionedRegionRebalanceOp.(PartitionedRegionRebalanceOp.java:134)
>
> at
> org.apache.geode.internal.cache.partitioned.PartitionedRegionRebalanceOp.(PartitionedRegionRebalanceOp.java:114)
>
> at
> org.apache.geode.internal.cache.PRHARedundancyProvider$3.run2(PRHARedundancyProvider.java:1587)
>
> at
> org.apache.geode.internal.cache.partitioned.RecoveryRunnable.run(RecoveryRunnable.java:58)
>
> at
> org.apache.geode.internal.OneTaskOnlyExecutor$DelegatingRunnable.run(OneTaskOnlyExecutor.java:141)
>
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
>
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5810) events not drained from secondary queues in testPartitionedParallelPropagationHA test
[
https://issues.apache.org/jira/browse/GEODE-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill updated GEODE-5810:
Description:
This failure occurred on mass-test-run in at least this run:
https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/809
Stack trace:
{noformat}
org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderDUnitTest
> testPartitionedParallelPropagationHA FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderDUnitTest$$Lambda$214/55002370.run
in VM 7 running on Host e1abfa396082 with 8 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:450)
at org.apache.geode.test.dunit.VM.invoke(VM.java:419)
at org.apache.geode.test.dunit.VM.invoke(VM.java:362)
at
org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderDUnitTest.testPartitionedParallelPropagationHA(ConcurrentParallelGatewaySenderDUnitTest.java:634)
Caused by:
org.awaitility.core.ConditionTimeoutException: Assertion condition
defined as a lambda expression in
org.apache.geode.internal.cache.wan.WANTestBase that uses
org.apache.geode.internal.cache.wan.AbstractGatewaySender,
org.apache.geode.internal.cache.wan.AbstractGatewaySenderorg.apache.geode.internal.cache.RegionQueue
Expected events in all secondary queues are drained but actual is 1. Queue
content is: bucketId=6:[206]; expected:<0> but was:<1> within 120 seconds.
at
org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
at
org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122)
at
org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
at
org.awaitility.core.ConditionFactory.until(ConditionFactory.java:890)
at
org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:711)
at
org.apache.geode.internal.cache.wan.WANTestBase.validateParallelSenderQueueAllBucketsDrained(WANTestBase.java:3290)
at
org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderDUnitTest.lambda$testPartitionedParallelPropagationHA$bb17a952$17(ConcurrentParallelGatewaySenderDUnitTest.java:634)
Caused by:
java.lang.AssertionError: Expected events in all secondary queues
are drained but actual is 1. Queue content is: bucketId=6:[206]; expected:<0>
but was:<1>
{noformat}
was:
Stack trace:
{noformat}
org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderDUnitTest
> testPartitionedParallelPropagationHA FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderDUnitTest$$Lambda$214/55002370.run
in VM 7 running on Host e1abfa396082 with 8 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:450)
at org.apache.geode.test.dunit.VM.invoke(VM.java:419)
at org.apache.geode.test.dunit.VM.invoke(VM.java:362)
at
org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderDUnitTest.testPartitionedParallelPropagationHA(ConcurrentParallelGatewaySenderDUnitTest.java:634)
Caused by:
org.awaitility.core.ConditionTimeoutException: Assertion condition
defined as a lambda expression in
org.apache.geode.internal.cache.wan.WANTestBase that uses
org.apache.geode.internal.cache.wan.AbstractGatewaySender,
org.apache.geode.internal.cache.wan.AbstractGatewaySenderorg.apache.geode.internal.cache.RegionQueue
Expected events in all secondary queues are drained but actual is 1. Queue
content is: bucketId=6:[206]; expected:<0> but was:<1> within 120 seconds.
at
org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
at
org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122)
at
org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
at
org.awaitility.core.ConditionFactory.until(ConditionFactory.java:890)
at
org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:711)
at
org.apache.geode.internal.cache.wan.WANTestBase.validateParallelSenderQueueAllBucketsDrained(WANTestBase.java:3290)
at
org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderDUnitTest.lambda$testPartitionedParallelPropagationHA$bb17a952$17(ConcurrentParallelGatewaySenderDUnitTest.java:634)
Caused by:
java.lang.AssertionError: Expected events in all secondary queues
are drained but actual is 1. Queue content is: bucketId=6:[206]; expected:<0>
but was:<1>
{noformat}
> events not drained from secondary queues in
> testPartitionedParallelPropagationHA test
>
[jira] [Updated] (GEODE-5810) events not drained from secondary queues in testPartitionedParallelPropagationHA test
[
https://issues.apache.org/jira/browse/GEODE-5810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill updated GEODE-5810:
Labels: swat (was: )
> events not drained from secondary queues in
> testPartitionedParallelPropagationHA test
> -
>
> Key: GEODE-5810
> URL: https://issues.apache.org/jira/browse/GEODE-5810
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Bill
>Priority: Major
> Labels: swat
>
> This failure occurred on mass-test-run in at least this run:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/809
> Stack trace:
> {noformat}
> org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderDUnitTest
> > testPartitionedParallelPropagationHA FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderDUnitTest$$Lambda$214/55002370.run
> in VM 7 running on Host e1abfa396082 with 8 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:450)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:419)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:362)
> at
> org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderDUnitTest.testPartitionedParallelPropagationHA(ConcurrentParallelGatewaySenderDUnitTest.java:634)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.internal.cache.wan.WANTestBase that uses
> org.apache.geode.internal.cache.wan.AbstractGatewaySender,
> org.apache.geode.internal.cache.wan.AbstractGatewaySenderorg.apache.geode.internal.cache.RegionQueue
> Expected events in all secondary queues are drained but actual is 1. Queue
> content is: bucketId=6:[206]; expected:<0> but was:<1> within 120 seconds.
> at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122)
> at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
> at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:890)
> at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:711)
> at
> org.apache.geode.internal.cache.wan.WANTestBase.validateParallelSenderQueueAllBucketsDrained(WANTestBase.java:3290)
> at
> org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderDUnitTest.lambda$testPartitionedParallelPropagationHA$bb17a952$17(ConcurrentParallelGatewaySenderDUnitTest.java:634)
> Caused by:
> java.lang.AssertionError: Expected events in all secondary queues
> are drained but actual is 1. Queue content is: bucketId=6:[206]; expected:<0>
> but was:<1>
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5810) events not drained from secondary queues in testPartitionedParallelPropagationHA test
Bill created GEODE-5810:
---
Summary: events not drained from secondary queues in
testPartitionedParallelPropagationHA test
Key: GEODE-5810
URL: https://issues.apache.org/jira/browse/GEODE-5810
Project: Geode
Issue Type: Bug
Components: wan
Reporter: Bill
Stack trace:
{noformat}
org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderDUnitTest
> testPartitionedParallelPropagationHA FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderDUnitTest$$Lambda$214/55002370.run
in VM 7 running on Host e1abfa396082 with 8 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:450)
at org.apache.geode.test.dunit.VM.invoke(VM.java:419)
at org.apache.geode.test.dunit.VM.invoke(VM.java:362)
at
org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderDUnitTest.testPartitionedParallelPropagationHA(ConcurrentParallelGatewaySenderDUnitTest.java:634)
Caused by:
org.awaitility.core.ConditionTimeoutException: Assertion condition
defined as a lambda expression in
org.apache.geode.internal.cache.wan.WANTestBase that uses
org.apache.geode.internal.cache.wan.AbstractGatewaySender,
org.apache.geode.internal.cache.wan.AbstractGatewaySenderorg.apache.geode.internal.cache.RegionQueue
Expected events in all secondary queues are drained but actual is 1. Queue
content is: bucketId=6:[206]; expected:<0> but was:<1> within 120 seconds.
at
org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
at
org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122)
at
org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
at
org.awaitility.core.ConditionFactory.until(ConditionFactory.java:890)
at
org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:711)
at
org.apache.geode.internal.cache.wan.WANTestBase.validateParallelSenderQueueAllBucketsDrained(WANTestBase.java:3290)
at
org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderDUnitTest.lambda$testPartitionedParallelPropagationHA$bb17a952$17(ConcurrentParallelGatewaySenderDUnitTest.java:634)
Caused by:
java.lang.AssertionError: Expected events in all secondary queues
are drained but actual is 1. Queue content is: bucketId=6:[206]; expected:<0>
but was:<1>
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-3912) Incorrect regions shown in Pulse ClusterView
[ https://issues.apache.org/jira/browse/GEODE-3912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16629508#comment-16629508 ] Bill commented on GEODE-3912: - Closing since I was unable to reproduce this. It seems to be fixed. > Incorrect regions shown in Pulse ClusterView > > > Key: GEODE-3912 > URL: https://issues.apache.org/jira/browse/GEODE-3912 > Project: Geode > Issue Type: Bug > Components: pulse >Reporter: Jens Deppe >Assignee: Bill >Priority: Major > Labels: starter > Fix For: 1.8.0 > > Attachments: screenshot-1.png, screenshot-2.png > > > I have a 3-node cluster and have created 2 replicated regions and 1 > partitioned. Each region contains 20 entries. I'm using the > SimpleSecurityManager for access control. > Under the 'ClusterView' each server shows an incorrect view of the regions it > is hosting. Specifically it only shows a single region where it should be > showing all 3 regions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-3912) Incorrect regions shown in Pulse ClusterView
[ https://issues.apache.org/jira/browse/GEODE-3912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill resolved GEODE-3912. - Resolution: Fixed Fix Version/s: 1.8.0 No new changes needed. > Incorrect regions shown in Pulse ClusterView > > > Key: GEODE-3912 > URL: https://issues.apache.org/jira/browse/GEODE-3912 > Project: Geode > Issue Type: Bug > Components: pulse >Reporter: Jens Deppe >Assignee: Bill >Priority: Major > Labels: starter > Fix For: 1.8.0 > > Attachments: screenshot-1.png, screenshot-2.png > > > I have a 3-node cluster and have created 2 replicated regions and 1 > partitioned. Each region contains 20 entries. I'm using the > SimpleSecurityManager for access control. > Under the 'ClusterView' each server shows an incorrect view of the regions it > is hosting. Specifically it only shows a single region where it should be > showing all 3 regions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-3912) Incorrect regions shown in Pulse ClusterView
[ https://issues.apache.org/jira/browse/GEODE-3912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill reassigned GEODE-3912: --- Assignee: Bill > Incorrect regions shown in Pulse ClusterView > > > Key: GEODE-3912 > URL: https://issues.apache.org/jira/browse/GEODE-3912 > Project: Geode > Issue Type: Bug > Components: pulse >Reporter: Jens Deppe >Assignee: Bill >Priority: Major > Labels: starter > Attachments: screenshot-1.png, screenshot-2.png > > > I have a 3-node cluster and have created 2 replicated regions and 1 > partitioned. Each region contains 20 entries. I'm using the > SimpleSecurityManager for access control. > Under the 'ClusterView' each server shows an incorrect view of the regions it > is hosting. Specifically it only shows a single region where it should be > showing all 3 regions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-3912) Incorrect regions shown in Pulse ClusterView
[ https://issues.apache.org/jira/browse/GEODE-3912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16629292#comment-16629292 ] Bill commented on GEODE-3912: - On that same commit, I tested with the `SimpleSecurityManager` and I still do not see the problem. It would seem that this bug is fixed. > Incorrect regions shown in Pulse ClusterView > > > Key: GEODE-3912 > URL: https://issues.apache.org/jira/browse/GEODE-3912 > Project: Geode > Issue Type: Bug > Components: pulse >Reporter: Jens Deppe >Priority: Major > Labels: starter > Attachments: screenshot-1.png, screenshot-2.png > > > I have a 3-node cluster and have created 2 replicated regions and 1 > partitioned. Each region contains 20 entries. I'm using the > SimpleSecurityManager for access control. > Under the 'ClusterView' each server shows an incorrect view of the regions it > is hosting. Specifically it only shows a single region where it should be > showing all 3 regions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-3912) Incorrect regions shown in Pulse ClusterView
[ https://issues.apache.org/jira/browse/GEODE-3912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill updated GEODE-3912: Attachment: screenshot-2.png > Incorrect regions shown in Pulse ClusterView > > > Key: GEODE-3912 > URL: https://issues.apache.org/jira/browse/GEODE-3912 > Project: Geode > Issue Type: Bug > Components: pulse >Reporter: Jens Deppe >Priority: Major > Labels: starter > Attachments: screenshot-1.png, screenshot-2.png > > > I have a 3-node cluster and have created 2 replicated regions and 1 > partitioned. Each region contains 20 entries. I'm using the > SimpleSecurityManager for access control. > Under the 'ClusterView' each server shows an incorrect view of the regions it > is hosting. Specifically it only shows a single region where it should be > showing all 3 regions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-3912) Incorrect regions shown in Pulse ClusterView
[ https://issues.apache.org/jira/browse/GEODE-3912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16628050#comment-16628050 ] Bill commented on GEODE-3912: - I was unable to reproduce this bug on commit `dee93f40faa82e97aa05fe34bbc7ee2adac79cbc` on the `develop` branch. Created the 3 regions (2 replicated, 1 partitioned) and then added 20 entries to each. *I did not explicitly configure `SimpleSecurityManager`—is that the default?* The number of regions and the number of entries, displayed by pulse, were correct for all three servers: !screenshot-2.png! > Incorrect regions shown in Pulse ClusterView > > > Key: GEODE-3912 > URL: https://issues.apache.org/jira/browse/GEODE-3912 > Project: Geode > Issue Type: Bug > Components: pulse >Reporter: Jens Deppe >Priority: Major > Labels: starter > Attachments: screenshot-1.png, screenshot-2.png > > > I have a 3-node cluster and have created 2 replicated regions and 1 > partitioned. Each region contains 20 entries. I'm using the > SimpleSecurityManager for access control. > Under the 'ClusterView' each server shows an incorrect view of the regions it > is hosting. Specifically it only shows a single region where it should be > showing all 3 regions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-369) CI failure: RedundancyLevelPart1DUnitTest.testRedundancySpecifiedNonPrimaryEPFailsDetectionByPut fails intermittently with assertion
[
https://issues.apache.org/jira/browse/GEODE-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill resolved GEODE-369.
Resolution: Fixed
> CI failure:
> RedundancyLevelPart1DUnitTest.testRedundancySpecifiedNonPrimaryEPFailsDetectionByPut
> fails intermittently with assertion
>
>
> Key: GEODE-369
> URL: https://issues.apache.org/jira/browse/GEODE-369
> Project: Geode
> Issue Type: Bug
> Components: client queues, client/server
>Reporter: Darrel Schneider
>Assignee: Bill
>Priority: Minor
> Labels: CI, pull-request-available, swat
> Fix For: 1.8.0
>
> Attachments: Test results - Class
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest.htm
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> failed on a private build of git rev :
> {code}
> junit.framework.AssertionFailedError: Event never occurred after 6 ms:
> Redundant servers ([doomtwo.gemstone.com29009]) does not contain
> doomtwo.gemstone.com27615
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> dunit.DistributedTestCase.waitForCriterion(DistributedTestCase.java:1162)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.RedundancyLevelTestBase.verifyRedundantServersContain(RedundancyLevelTestBase.java:267)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest.testRedundancySpecifiedNonPrimaryEPFailsDetectionByPut(RedundancyLevelPart1DUnitTest.java:505)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-369) CI failure: RedundancyLevelPart1DUnitTest.testRedundancySpecifiedNonPrimaryEPFailsDetectionByPut fails intermittently with assertion
[
https://issues.apache.org/jira/browse/GEODE-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill updated GEODE-369:
---
Fix Version/s: (was: 1.0.0-incubating.M2)
1.8.0
> CI failure:
> RedundancyLevelPart1DUnitTest.testRedundancySpecifiedNonPrimaryEPFailsDetectionByPut
> fails intermittently with assertion
>
>
> Key: GEODE-369
> URL: https://issues.apache.org/jira/browse/GEODE-369
> Project: Geode
> Issue Type: Bug
> Components: client queues, client/server
>Reporter: Darrel Schneider
>Assignee: Bill
>Priority: Minor
> Labels: CI, pull-request-available, swat
> Fix For: 1.8.0
>
> Attachments: Test results - Class
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest.htm
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> failed on a private build of git rev :
> {code}
> junit.framework.AssertionFailedError: Event never occurred after 6 ms:
> Redundant servers ([doomtwo.gemstone.com29009]) does not contain
> doomtwo.gemstone.com27615
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> dunit.DistributedTestCase.waitForCriterion(DistributedTestCase.java:1162)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.RedundancyLevelTestBase.verifyRedundantServersContain(RedundancyLevelTestBase.java:267)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest.testRedundancySpecifiedNonPrimaryEPFailsDetectionByPut(RedundancyLevelPart1DUnitTest.java:505)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5679) Test failed StatSamplerIntegrationTest.testStatSampler FAILED
[
https://issues.apache.org/jira/browse/GEODE-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill updated GEODE-5679:
Fix Version/s: 1.8.0
> Test failed StatSamplerIntegrationTest.testStatSampler FAILED
> -
>
> Key: GEODE-5679
> URL: https://issues.apache.org/jira/browse/GEODE-5679
> Project: Geode
> Issue Type: Bug
> Components: core
>Affects Versions: 1.8.0
>Reporter: Mark Hanson
>Assignee: Bill
>Priority: Major
> Labels: pull-request-available, swat
> Fix For: 1.8.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> This test failed during integration tests. Concourse URL is
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/351
> java.lang.AssertionError: Value 5 for int_counter_6 is wrong:
> {double_gauge_4=8.0, long_counter_10=6, sampled_double=7.0,
> long_counter_9=24, double_counter_1=10.0, double_counter_2=8.0,
> int_counter_5=18, int_counter_6=8, sampled_long=6, long_gauge_12=6,
> long_gauge_11=24, int_gauge_8=6, sampled_int=5, int_gauge_7=16,
> double_gauge_3=10.0} expected:<8.0> but was:<7.0>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:553)
> at
> org.apache.geode.internal.statistics.StatSamplerIntegrationTest.testStatSampler(StatSamplerIntegrationTest.java:308)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
> at
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown
[jira] [Resolved] (GEODE-5679) Test failed StatSamplerIntegrationTest.testStatSampler FAILED
[
https://issues.apache.org/jira/browse/GEODE-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill resolved GEODE-5679.
-
Resolution: Fixed
> Test failed StatSamplerIntegrationTest.testStatSampler FAILED
> -
>
> Key: GEODE-5679
> URL: https://issues.apache.org/jira/browse/GEODE-5679
> Project: Geode
> Issue Type: Bug
> Components: core
>Affects Versions: 1.8.0
>Reporter: Mark Hanson
>Assignee: Bill
>Priority: Major
> Labels: pull-request-available, swat
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> This test failed during integration tests. Concourse URL is
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/351
> java.lang.AssertionError: Value 5 for int_counter_6 is wrong:
> {double_gauge_4=8.0, long_counter_10=6, sampled_double=7.0,
> long_counter_9=24, double_counter_1=10.0, double_counter_2=8.0,
> int_counter_5=18, int_counter_6=8, sampled_long=6, long_gauge_12=6,
> long_gauge_11=24, int_gauge_8=6, sampled_int=5, int_gauge_7=16,
> double_gauge_3=10.0} expected:<8.0> but was:<7.0>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:553)
> at
> org.apache.geode.internal.statistics.StatSamplerIntegrationTest.testStatSampler(StatSamplerIntegrationTest.java:308)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
> at
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
>
[jira] [Updated] (GEODE-5679) Test failed StatSamplerIntegrationTest.testStatSampler FAILED
[
https://issues.apache.org/jira/browse/GEODE-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill updated GEODE-5679:
Affects Version/s: 1.8.0
> Test failed StatSamplerIntegrationTest.testStatSampler FAILED
> -
>
> Key: GEODE-5679
> URL: https://issues.apache.org/jira/browse/GEODE-5679
> Project: Geode
> Issue Type: Bug
> Components: core
>Affects Versions: 1.8.0
>Reporter: Mark Hanson
>Assignee: Bill
>Priority: Major
> Labels: swat
>
> This test failed during integration tests. Concourse URL is
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/351
> java.lang.AssertionError: Value 5 for int_counter_6 is wrong:
> {double_gauge_4=8.0, long_counter_10=6, sampled_double=7.0,
> long_counter_9=24, double_counter_1=10.0, double_counter_2=8.0,
> int_counter_5=18, int_counter_6=8, sampled_long=6, long_gauge_12=6,
> long_gauge_11=24, int_gauge_8=6, sampled_int=5, int_gauge_7=16,
> double_gauge_3=10.0} expected:<8.0> but was:<7.0>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:553)
> at
> org.apache.geode.internal.statistics.StatSamplerIntegrationTest.testStatSampler(StatSamplerIntegrationTest.java:308)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
> at
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
>
[jira] [Assigned] (GEODE-5679) Test failed StatSamplerIntegrationTest.testStatSampler FAILED
[
https://issues.apache.org/jira/browse/GEODE-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill reassigned GEODE-5679:
---
Assignee: Bill
> Test failed StatSamplerIntegrationTest.testStatSampler FAILED
> -
>
> Key: GEODE-5679
> URL: https://issues.apache.org/jira/browse/GEODE-5679
> Project: Geode
> Issue Type: Bug
> Components: core
>Reporter: Mark Hanson
>Assignee: Bill
>Priority: Major
> Labels: swat
>
> This test failed during integration tests. Concourse URL is
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/351
> java.lang.AssertionError: Value 5 for int_counter_6 is wrong:
> {double_gauge_4=8.0, long_counter_10=6, sampled_double=7.0,
> long_counter_9=24, double_counter_1=10.0, double_counter_2=8.0,
> int_counter_5=18, int_counter_6=8, sampled_long=6, long_gauge_12=6,
> long_gauge_11=24, int_gauge_8=6, sampled_int=5, int_gauge_7=16,
> double_gauge_3=10.0} expected:<8.0> but was:<7.0>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:553)
> at
> org.apache.geode.internal.statistics.StatSamplerIntegrationTest.testStatSampler(StatSamplerIntegrationTest.java:308)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
> at
> org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:117)
> at
[jira] [Updated] (GEODE-5760) CI failure: Expected exception Not found in QueryMonitorDUnitTest.testQueryMonitorRegionWithIndex
[
https://issues.apache.org/jira/browse/GEODE-5760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill updated GEODE-5760:
Labels: swat (was: )
> CI failure: Expected exception Not found in
> QueryMonitorDUnitTest.testQueryMonitorRegionWithIndex
> -
>
> Key: GEODE-5760
> URL: https://issues.apache.org/jira/browse/GEODE-5760
> Project: Geode
> Issue Type: Bug
> Components: cq
>Reporter: Bill
>Priority: Major
> Labels: swat
>
> In
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/415
> {code}
> > Task :geode-cq:distributedTest
> org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest >
> testQueryMonitorRegionWithIndex FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest$$Lambda$104/648688972.run
> in VM 4 running on Host 17a0abd8c00d with 5 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:450)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:419)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:362)
> at
> org.apache.geode.test.junit.rules.VMProvider.invoke(VMProvider.java:70)
> at
> org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.testQueryMonitorRegionWithIndex(QueryMonitorDUnitTest.java:239)
> Caused by:
> java.lang.AssertionError: Expected exception Not found. Expected
> exception with message:
> "Query execution taking more than the max execution time"
> Found
> Pool unexpected socket timed out on client connection=Pooled
> Connection to localhost:37885: Connection[localhost:37885]@176708196). Server
> unreachable: could not connect after 1 attempts
> at org.junit.Assert.fail(Assert.java:88)
> at
> org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.verifyException(QueryMonitorDUnitTest.java:410)
> at
> org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.exuteQuery(QueryMonitorDUnitTest.java:363)
> at
> org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.lambda$testQueryMonitorRegionWithIndex$bb17a952$3(QueryMonitorDUnitTest.java:239)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5760) CI failure: Expected exception Not found in QueryMonitorDUnitTest.testQueryMonitorRegionWithIndex
Bill created GEODE-5760:
---
Summary: CI failure: Expected exception Not found in
QueryMonitorDUnitTest.testQueryMonitorRegionWithIndex
Key: GEODE-5760
URL: https://issues.apache.org/jira/browse/GEODE-5760
Project: Geode
Issue Type: Bug
Components: cq
Reporter: Bill
In
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/415
{code}
> Task :geode-cq:distributedTest
org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest >
testQueryMonitorRegionWithIndex FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest$$Lambda$104/648688972.run
in VM 4 running on Host 17a0abd8c00d with 5 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:450)
at org.apache.geode.test.dunit.VM.invoke(VM.java:419)
at org.apache.geode.test.dunit.VM.invoke(VM.java:362)
at
org.apache.geode.test.junit.rules.VMProvider.invoke(VMProvider.java:70)
at
org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.testQueryMonitorRegionWithIndex(QueryMonitorDUnitTest.java:239)
Caused by:
java.lang.AssertionError: Expected exception Not found. Expected
exception with message:
"Query execution taking more than the max execution time"
Found
Pool unexpected socket timed out on client connection=Pooled Connection
to localhost:37885: Connection[localhost:37885]@176708196). Server unreachable:
could not connect after 1 attempts
at org.junit.Assert.fail(Assert.java:88)
at
org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.verifyException(QueryMonitorDUnitTest.java:410)
at
org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.exuteQuery(QueryMonitorDUnitTest.java:363)
at
org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.lambda$testQueryMonitorRegionWithIndex$bb17a952$3(QueryMonitorDUnitTest.java:239)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-369) CI failure: RedundancyLevelPart1DUnitTest.testRedundancySpecifiedNonPrimaryEPFailsDetectionByPut fails intermittently with assertion
[
https://issues.apache.org/jira/browse/GEODE-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill reassigned GEODE-369:
--
Assignee: Bill
> CI failure:
> RedundancyLevelPart1DUnitTest.testRedundancySpecifiedNonPrimaryEPFailsDetectionByPut
> fails intermittently with assertion
>
>
> Key: GEODE-369
> URL: https://issues.apache.org/jira/browse/GEODE-369
> Project: Geode
> Issue Type: Bug
> Components: client queues, client/server
>Reporter: Darrel Schneider
>Assignee: Bill
>Priority: Minor
> Labels: CI, swat
> Fix For: 1.0.0-incubating.M2
>
> Attachments: Test results - Class
> org.apache.geode.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest.htm
>
>
> failed on a private build of git rev :
> {code}
> junit.framework.AssertionFailedError: Event never occurred after 6 ms:
> Redundant servers ([doomtwo.gemstone.com29009]) does not contain
> doomtwo.gemstone.com27615
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> dunit.DistributedTestCase.waitForCriterion(DistributedTestCase.java:1162)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.RedundancyLevelTestBase.verifyRedundantServersContain(RedundancyLevelTestBase.java:267)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.RedundancyLevelPart1DUnitTest.testRedundancySpecifiedNonPrimaryEPFailsDetectionByPut(RedundancyLevelPart1DUnitTest.java:505)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-5732) TxCommitMessageTest doesn't actually test for presence/absence of shadow key flag
[ https://issues.apache.org/jira/browse/GEODE-5732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill reassigned GEODE-5732: --- Assignee: Bill > TxCommitMessageTest doesn't actually test for presence/absence of shadow key > flag > - > > Key: GEODE-5732 > URL: https://issues.apache.org/jira/browse/GEODE-5732 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Bill >Assignee: Bill >Priority: Major > Labels: swat > > The various toDataXX and fromDataXX methods purport to test > serialization/deserialization of TXCommitMessage between different product > versions. Primarily, this entails looking for presence/absence of the shadow > key boolean. Unfortunately, since the move to Mockito, only 1/7 of the tests > actually fail when we break the product. > The fix is to not use mocking for these tests, and to instead > serialize/deserialize to/from buffers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5732) TxCommitMessageTest doesn't actually test for presence/absence of shadow key flag
[ https://issues.apache.org/jira/browse/GEODE-5732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill updated GEODE-5732: Labels: swat (was: ) > TxCommitMessageTest doesn't actually test for presence/absence of shadow key > flag > - > > Key: GEODE-5732 > URL: https://issues.apache.org/jira/browse/GEODE-5732 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Bill >Priority: Major > Labels: swat > > The various toDataXX and fromDataXX methods purport to test > serialization/deserialization of TXCommitMessage between different product > versions. Primarily, this entails looking for presence/absence of the shadow > key boolean. Unfortunately, since the move to Mockito, only 1/7 of the tests > actually fail when we break the product. > The fix is to not use mocking for these tests, and to instead > serialize/deserialize to/from buffers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5732) TxCommitMessageTest doesn't actually test for presence/absence of shadow key flag
[ https://issues.apache.org/jira/browse/GEODE-5732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill updated GEODE-5732: Description: The various toDataXX and fromDataXX methods purport to test serialization/deserialization of TXCommitMessage between different product versions. Primarily, this entails looking for presence/absence of the shadow key boolean. Unfortunately, since the move to Mockito, only 1/7 of the tests actually fail when we break the product. The fix is to not use mocking for these tests, and to instead serialize/deserialize to/from buffers. was:the various toDataXX > TxCommitMessageTest doesn't actually test for presence/absence of shadow key > flag > - > > Key: GEODE-5732 > URL: https://issues.apache.org/jira/browse/GEODE-5732 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Bill >Priority: Major > Labels: swat > > The various toDataXX and fromDataXX methods purport to test > serialization/deserialization of TXCommitMessage between different product > versions. Primarily, this entails looking for presence/absence of the shadow > key boolean. Unfortunately, since the move to Mockito, only 1/7 of the tests > actually fail when we break the product. > The fix is to not use mocking for these tests, and to instead > serialize/deserialize to/from buffers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
