[jira] [Updated] (GEODE-3682) Trace displaying incorrect indexes being used
[ https://issues.apache.org/jira/browse/GEODE-3682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nabarun updated GEODE-3682: --- Fix Version/s: (was: 1.3.0) > Trace displaying incorrect indexes being used > - > > Key: GEODE-3682 > URL: https://issues.apache.org/jira/browse/GEODE-3682 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: nabarun > > This issue is occurs in an instance with region entries with indexes present. > Running a query with trace option set shows indexes being used which are not > supposed to be used for that particular query. > This sometimes occurs when indexes are being created or destroyed in between > queries. > This also occurs if different types of queries are executed one after > another. It sometimes feels like it is showing the residue of the index used > in the previous query execution. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (GEODE-3743) Deprecate option for manual restart of Gateway senders
Diane Hardman created GEODE-3743: Summary: Deprecate option for manual restart of Gateway senders Key: GEODE-3743 URL: https://issues.apache.org/jira/browse/GEODE-3743 Project: Geode Issue Type: Bug Components: wan Reporter: Diane Hardman Deprecate manual restart for gateway senders so it can be removed in GemFire 10.0. With manual start of senders, it is possible that events, created prior to the start of the senders, are not sent to the remote site. Some users have tripped over this limitation which has resulted in data loss. In the valid use-case of using this option to gather a limited amount of data from a production cluster to populate a test cluster, using the snapshot feature is a better choice. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (GEODE-3712) PartitionedRegionQueryEvaluator should shuffle node list
[ https://issues.apache.org/jira/browse/GEODE-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16190576#comment-16190576 ] ASF subversion and git services commented on GEODE-3712: Commit 09bb75c850f64456a673d4cf85744faee60df257 in geode's branch refs/heads/develop from [~huynhja] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=09bb75c ] GEODE-3712: PartitionedRegionQueryEvaluator should shuffle node list > PartitionedRegionQueryEvaluator should shuffle node list > > > Key: GEODE-3712 > URL: https://issues.apache.org/jira/browse/GEODE-3712 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: Jason Huynh >Assignee: Jason Huynh > > When executing a query from a peer, the peer will retrieve a node list and > determine which nodes contain which buckets. If this node list is ordered, > then the same nodes will continue to get hit. > Instead we should probably shuffle this list to allow different nodes to be > queried against. > This does not affect client/server queries. Just peer accessors. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (GEODE-3703) rename JAR resource to DEPLOY
[ https://issues.apache.org/jira/browse/GEODE-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller reassigned GEODE-3703: -- Assignee: Karen Smoler Miller > rename JAR resource to DEPLOY > - > > Key: GEODE-3703 > URL: https://issues.apache.org/jira/browse/GEODE-3703 > Project: Geode > Issue Type: Sub-task > Components: docs, security >Reporter: Swapnil Bawaskar >Assignee: Karen Smoler Miller > Fix For: 1.3.0 > > > We currently have a JAR resource introduced with finer grained security (not > released yet). Since the idea behind this resource is to control who has > authorization to deploy jar files to the geode cluster, I think a better name > for this resource would be DEPLOY. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (GEODE-3687) create gateway receiver ignores bind-address setting from gemfire.properties
[ https://issues.apache.org/jira/browse/GEODE-3687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16190497#comment-16190497 ] ASF subversion and git services commented on GEODE-3687: Commit 6b96a8aa16cd2dc175c1fd152587162c5aa2c3c2 in geode's branch refs/heads/feature/GEODE-3687 from [~lhughesgodfrey] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=6b96a8a ] GEODE-3687: GatewayReceiverImpl constructor and create method updates - bind-address specified in gemfire.properties is now used to configure Profile and ServerLocations - removed host field (previously calculated at config time based on hostname-for-sender and bind-address parameters) with result then passed to CacheServerImpl.start() - replaced host field with hostnameForSenders, which is now used (when set) to set hostnameForClients in CacheServerImpl. - replaced getHost with getHostnameForSenders - associated tests, including those to set bind-address and server-bind-address through gemfire.properties > create gateway receiver ignores bind-address setting from gemfire.properties > > > Key: GEODE-3687 > URL: https://issues.apache.org/jira/browse/GEODE-3687 > Project: Geode > Issue Type: Bug > Components: wan >Reporter: Shelley Lynn Hughes-Godfrey >Assignee: Shelley Lynn Hughes-Godfrey > > Users report that even with `bind-address` set to the ip in > `gemfire.properties`, the receivers are still giving hostnames to the senders > instead of ip addresses. > The GatewayReceiverImpl should not be invoking: > receiver.setHostnameForClients(host); > with the local hostname (based on hostname-for-senders and bind-address > settings). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (GEODE-3248) Validate OQL bind parameters
[
https://issues.apache.org/jira/browse/GEODE-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Huynh resolved GEODE-3248.
Resolution: Fixed
Fix Version/s: 1.3.0
> Validate OQL bind parameters
>
>
> Key: GEODE-3248
> URL: https://issues.apache.org/jira/browse/GEODE-3248
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Anthony Baker
>Assignee: Jason Huynh
> Fix For: 1.3.0
>
>
> When passing a {{Region}} as a bind parameter, validate the region name to
> prevent errors.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (GEODE-3247) Improve OQL expression execution
[ https://issues.apache.org/jira/browse/GEODE-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Huynh updated GEODE-3247: --- Fix Version/s: 1.3.0 > Improve OQL expression execution > > > Key: GEODE-3247 > URL: https://issues.apache.org/jira/browse/GEODE-3247 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: Anthony Baker >Assignee: Jason Huynh > Fix For: 1.3.0 > > > We should validate an OQL expression before attempting to invoke it to > prevent undesirable behavior. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (GEODE-3247) Improve OQL expression execution
[ https://issues.apache.org/jira/browse/GEODE-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Huynh resolved GEODE-3247. Resolution: Fixed > Improve OQL expression execution > > > Key: GEODE-3247 > URL: https://issues.apache.org/jira/browse/GEODE-3247 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: Anthony Baker >Assignee: Jason Huynh > Fix For: 1.3.0 > > > We should validate an OQL expression before attempting to invoke it to > prevent undesirable behavior. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (GEODE-3247) Improve OQL expression execution
[ https://issues.apache.org/jira/browse/GEODE-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16190419#comment-16190419 ] ASF subversion and git services commented on GEODE-3247: Commit 02b9646618e074f80b3d5fed0e5b512a34b5897a in geode's branch refs/heads/develop from [~huynhja] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=02b9646 ] GEODE-3247:Improve OQL expression execution (#837) * GEODE-3247: Restrict method invocation in OQL when new security service is enabled * GEODE-3248: Regions being passed in through bind parameters should have authorized access * GEODE-3247: MethodInvocationAuthorizer is created at start up * MethodInvocationAuthorizer can now be passed down from InternalCache * Broke apart new tests into smaller files and removed complex query maps from UserPerms * Modified Customer Test Object for Rest Security tests > Improve OQL expression execution > > > Key: GEODE-3247 > URL: https://issues.apache.org/jira/browse/GEODE-3247 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: Anthony Baker >Assignee: Jason Huynh > > We should validate an OQL expression before attempting to invoke it to > prevent undesirable behavior. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (GEODE-3247) Improve OQL expression execution
[ https://issues.apache.org/jira/browse/GEODE-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16190421#comment-16190421 ] ASF subversion and git services commented on GEODE-3247: Commit 02b9646618e074f80b3d5fed0e5b512a34b5897a in geode's branch refs/heads/develop from [~huynhja] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=02b9646 ] GEODE-3247:Improve OQL expression execution (#837) * GEODE-3247: Restrict method invocation in OQL when new security service is enabled * GEODE-3248: Regions being passed in through bind parameters should have authorized access * GEODE-3247: MethodInvocationAuthorizer is created at start up * MethodInvocationAuthorizer can now be passed down from InternalCache * Broke apart new tests into smaller files and removed complex query maps from UserPerms * Modified Customer Test Object for Rest Security tests > Improve OQL expression execution > > > Key: GEODE-3247 > URL: https://issues.apache.org/jira/browse/GEODE-3247 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: Anthony Baker >Assignee: Jason Huynh > > We should validate an OQL expression before attempting to invoke it to > prevent undesirable behavior. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (GEODE-3248) Validate OQL bind parameters
[
https://issues.apache.org/jira/browse/GEODE-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16190420#comment-16190420
]
ASF subversion and git services commented on GEODE-3248:
Commit 02b9646618e074f80b3d5fed0e5b512a34b5897a in geode's branch
refs/heads/develop from [~huynhja]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=02b9646 ]
GEODE-3247:Improve OQL expression execution (#837)
* GEODE-3247: Restrict method invocation in OQL when new security service is
enabled
* GEODE-3248: Regions being passed in through bind parameters should have
authorized access
* GEODE-3247: MethodInvocationAuthorizer is created at start up
* MethodInvocationAuthorizer can now be passed down from InternalCache
* Broke apart new tests into smaller files and removed complex query maps
from UserPerms
* Modified Customer Test Object for Rest Security tests
> Validate OQL bind parameters
>
>
> Key: GEODE-3248
> URL: https://issues.apache.org/jira/browse/GEODE-3248
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Anthony Baker
>Assignee: Jason Huynh
>
> When passing a {{Region}} as a bind parameter, validate the region name to
> prevent errors.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (GEODE-3247) Improve OQL expression execution
[ https://issues.apache.org/jira/browse/GEODE-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16190418#comment-16190418 ] ASF subversion and git services commented on GEODE-3247: Commit 02b9646618e074f80b3d5fed0e5b512a34b5897a in geode's branch refs/heads/develop from [~huynhja] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=02b9646 ] GEODE-3247:Improve OQL expression execution (#837) * GEODE-3247: Restrict method invocation in OQL when new security service is enabled * GEODE-3248: Regions being passed in through bind parameters should have authorized access * GEODE-3247: MethodInvocationAuthorizer is created at start up * MethodInvocationAuthorizer can now be passed down from InternalCache * Broke apart new tests into smaller files and removed complex query maps from UserPerms * Modified Customer Test Object for Rest Security tests > Improve OQL expression execution > > > Key: GEODE-3247 > URL: https://issues.apache.org/jira/browse/GEODE-3247 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: Anthony Baker >Assignee: Jason Huynh > > We should validate an OQL expression before attempting to invoke it to > prevent undesirable behavior. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (GEODE-3242) User can add a LuceneSerializer using GFSH
[ https://issues.apache.org/jira/browse/GEODE-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-3242: --- Component/s: docs > User can add a LuceneSerializer using GFSH > -- > > Key: GEODE-3242 > URL: https://issues.apache.org/jira/browse/GEODE-3242 > Project: Geode > Issue Type: Sub-task > Components: docs, lucene >Reporter: Dan Smith > > As a user, I can pass in a LuceneSerializer when creating an index through > gfsh. > Acceptance: > A user can pass a LuceneSerializer as a parameter when creating a lucene > index through gfsh. That serializer is called when entries are added to the > region, and the results are what get stored in the lucene index. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (GEODE-3722) gfsh search lucene command has a typo: queryStrings
[ https://issues.apache.org/jira/browse/GEODE-3722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Smoler Miller updated GEODE-3722: --- Component/s: docs > gfsh search lucene command has a typo: queryStrings > > > Key: GEODE-3722 > URL: https://issues.apache.org/jira/browse/GEODE-3722 > Project: Geode > Issue Type: Bug > Components: docs, lucene >Reporter: Dan Smith >Assignee: Dan Smith > Fix For: 1.3.0 > > > The gfsh command search lucene takes a query string as a parameter. > Unfortunately, that parameter is named queryStrings (plural). It should be > queryString -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (GEODE-3495) Review and update dependencies for 1.3.0
[ https://issues.apache.org/jira/browse/GEODE-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker resolved GEODE-3495. -- Resolution: Fixed > Review and update dependencies for 1.3.0 > > > Key: GEODE-3495 > URL: https://issues.apache.org/jira/browse/GEODE-3495 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Anthony Baker > Fix For: 1.3.0 > > > Review and update dependencies to latest versions for the Geode 1.3.0 release. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (GEODE-3742) CI failure: DeltaPropagationDUnitTest.testBug40165ClientReconnects FAILED with no queus server is available
Hitesh Khamesra created GEODE-3742: -- Summary: 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 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 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (GEODE-3741) Double free in ThinClientRegion::executeFunctionSH
Ernest Burghardt created GEODE-3741: --- Summary: Double free in ThinClientRegion::executeFunctionSH Key: GEODE-3741 URL: https://issues.apache.org/jira/browse/GEODE-3741 Project: Geode Issue Type: Bug Components: native client Reporter: Ernest Burghardt It is possible to have a double free of workers in this method -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (GEODE-3647) Race condition in AttributesMutator methods on partitioned regions can result in buckets with incorrect information
[ https://issues.apache.org/jira/browse/GEODE-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16190220#comment-16190220 ] ASF subversion and git services commented on GEODE-3647: Commit 96149530d82e0b62e9df1a043bfd7d0e01d3411a in geode's branch refs/heads/feature/GEODE-3604 from [~nreich] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=9614953 ] GEODE-3647: Fix race condition Partitioned region attributes mutation can fail to be applied to buckets created concurrently. Preventing bucket creation during the mutation of attributes solves this issue. > Race condition in AttributesMutator methods on partitioned regions can result > in buckets with incorrect information > --- > > Key: GEODE-3647 > URL: https://issues.apache.org/jira/browse/GEODE-3647 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Nick Reich >Assignee: Nick Reich > Fix For: 1.3.0 > > > When buckets are created at the same time that mutations are made to > attributes of a partitioned region, the created buckets can be missing the > mutated attributes. This was fixed for AttributesMutator.setCacheLoader(...) > in GEODE-716 and similar fixes should be applied to other mutator methods. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (GEODE-3539) Add more test coverage for p2p commands
[ https://issues.apache.org/jira/browse/GEODE-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16190217#comment-16190217 ] ASF subversion and git services commented on GEODE-3539: Commit b0348cd3d656848217ed6bb4e06d568203882ddb in geode's branch refs/heads/feature/GEODE-3604 from [~khowe] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b0348cd ] GEODE-3539: Additional test refactoring Separated remaining tests from ConfigCommandDUnitTest into command specific classes. > Add more test coverage for p2p commands > --- > > Key: GEODE-3539 > URL: https://issues.apache.org/jira/browse/GEODE-3539 > Project: Geode > Issue Type: Improvement > Components: gfsh >Reporter: Jinmei Liao > > Add more command tests that would eventually get rid of the legacy tests. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (GEODE-3647) Race condition in AttributesMutator methods on partitioned regions can result in buckets with incorrect information
[ https://issues.apache.org/jira/browse/GEODE-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16190221#comment-16190221 ] ASF subversion and git services commented on GEODE-3647: Commit 201cc525b757301a677a94f4a2adcd0eb2cbe256 in geode's branch refs/heads/feature/GEODE-3604 from [~nreich] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=201cc52 ] Feature/geode 3647 (#852) GEODE-3647: Fix race condition This reverts commit 5cb2a591199845190751f52e4da758c5ccd4d44e. Fix change to import that caused previous commit to fail. > Race condition in AttributesMutator methods on partitioned regions can result > in buckets with incorrect information > --- > > Key: GEODE-3647 > URL: https://issues.apache.org/jira/browse/GEODE-3647 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Nick Reich >Assignee: Nick Reich > Fix For: 1.3.0 > > > When buckets are created at the same time that mutations are made to > attributes of a partitioned region, the created buckets can be missing the > mutated attributes. This was fixed for AttributesMutator.setCacheLoader(...) > in GEODE-716 and similar fixes should be applied to other mutator methods. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (GEODE-3715) Improve DistributedTest framework with CacheRule and SharedCountersRule
[ https://issues.apache.org/jira/browse/GEODE-3715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16190219#comment-16190219 ] ASF subversion and git services commented on GEODE-3715: Commit 75c8a74b7a976d14ce33b84f4a187cafd64aacb7 in geode's branch refs/heads/feature/GEODE-3604 from [~apa...@the9muses.net] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=75c8a74 ] GEODE-3715: improve javadocs of DistributedTest rules > Improve DistributedTest framework with CacheRule and SharedCountersRule > --- > > Key: GEODE-3715 > URL: https://issues.apache.org/jira/browse/GEODE-3715 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund > Labels: DistributedTest > Fix For: 1.3.0 > > > Improve the DistributedTest framework with the following changes: > * CacheRule for use instead of CacheTestCase > * SharedCountersRule for shared counters across DUnit VMs > * Move disconnect methods to Disconnect > * Add withVMCount support to DistributedTestRule > * Improve API for DUnit Locator in DistributedTestUtils > These improvements are used by my new tests for GEODE-3693. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (GEODE-3604) Refactor new protobuf protocol code, to be less intrusive on core
[ https://issues.apache.org/jira/browse/GEODE-3604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16190223#comment-16190223 ] ASF subversion and git services commented on GEODE-3604: Commit c37a6dc1bb5b10158d70b8b5d2725324d363e12f in geode's branch refs/heads/feature/GEODE-3604 from kohlmu-pivotal [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c37a6dc ] GEODE-3604: Completed rebase and refactor > Refactor new protobuf protocol code, to be less intrusive on core > - > > Key: GEODE-3604 > URL: https://issues.apache.org/jira/browse/GEODE-3604 > Project: Geode > Issue Type: Improvement > Components: client/server >Reporter: Udo Kohlmeyer > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (GEODE-3441) Tomcat8SessionsClientServerDUnitTest uses default port
[
https://issues.apache.org/jira/browse/GEODE-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16190222#comment-16190222
]
ASF subversion and git services commented on GEODE-3441:
Commit 666b2b73ede8a3706ca6e8b459fa408ca0cd68a6 in geode's branch
refs/heads/feature/GEODE-3604 from [~upthewaterspout]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=666b2b7 ]
GEODE-3441: Use random port in Tomcat8SessionsClientServerDUnitTest
Changing this test to use a random port for the geode server.
> Tomcat8SessionsClientServerDUnitTest uses default port
> --
>
> Key: GEODE-3441
> URL: https://issues.apache.org/jira/browse/GEODE-3441
> Project: Geode
> Issue Type: Bug
> Components: http session
>Reporter: Dan Smith
>Assignee: Dan Smith
> Fix For: 1.3.0
>
>
> The Tomcat8SessionsClientServerDUnitTest client server test recently failed
> in jenkins. It looks like there was already a geode server running on the
> default port.
> This test should use a random port for the cache server, not the default port.
> With revision 566ff6c70a91e052be558df80b76f2eef611c1c8, from build 922
> {noformat}
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.modules.session.Tomcat8SessionsClientServerDUnitTest$$Lambda$57/1625836960.call
> in VM 1 running on Host asf905.gq1.ygridcore.net with 4 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:387)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:357)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:325)
> at
> org.apache.geode.modules.session.Tomcat8SessionsClientServerDUnitTest.setupServer(Tomcat8SessionsClientServerDUnitTest.java:60)
> at
> org.apache.geode.modules.session.Tomcat8SessionsClientServerDUnitTest.postSetUp(Tomcat8SessionsClientServerDUnitTest.java:44)
> Caused by: java.net.BindException: Failed to create server socket on
> null[40,404]
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:783)
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:745)
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:712)
> at
> org.apache.geode.internal.cache.tier.sockets.AcceptorImpl.(AcceptorImpl.java:469)
> at
> org.apache.geode.internal.cache.CacheServerImpl.start(CacheServerImpl.java:344)
> at
> org.apache.geode.modules.session.Tomcat8SessionsClientServerDUnitTest.lambda$setupServer$f0fd67c5$1(Tomcat8SessionsClientServerDUnitTest.java:65)
> Caused by: java.net.BindException: Address already in use (Bind failed)
> at java.net.PlainSocketImpl.socketBind(Native Method)
> at
> java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
> at java.net.ServerSocket.bind(ServerSocket.java:375)
> at
> org.apache.geode.internal.net.SocketCreator.createServerSocket(SocketCreator.java:779)
> ... 27 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (GEODE-3715) Improve DistributedTest framework with CacheRule and SharedCountersRule
[ https://issues.apache.org/jira/browse/GEODE-3715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16190218#comment-16190218 ] ASF subversion and git services commented on GEODE-3715: Commit 6e1beb834edb1388f53588d567d2bbb25537b1fb in geode's branch refs/heads/feature/GEODE-3604 from [~apa...@the9muses.net] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=6e1beb8 ] GEODE-3715: introduce CacheRule and SharedCountersRule Also minor improvements to DUnit: * Move disconnect methods to Disconnect * Add withVMCount support to DistributedTestRule * Improve API for DUnit Locator in DistributedTestUtils > Improve DistributedTest framework with CacheRule and SharedCountersRule > --- > > Key: GEODE-3715 > URL: https://issues.apache.org/jira/browse/GEODE-3715 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund > Labels: DistributedTest > Fix For: 1.3.0 > > > Improve the DistributedTest framework with the following changes: > * CacheRule for use instead of CacheTestCase > * SharedCountersRule for shared counters across DUnit VMs > * Move disconnect methods to Disconnect > * Add withVMCount support to DistributedTestRule > * Improve API for DUnit Locator in DistributedTestUtils > These improvements are used by my new tests for GEODE-3693. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (GEODE-3740) Document CachePerfStats diskTasksWaiting statistic
Karen Smoler Miller created GEODE-3740: -- Summary: Document CachePerfStats diskTasksWaiting statistic Key: GEODE-3740 URL: https://issues.apache.org/jira/browse/GEODE-3740 Project: Geode Issue Type: New Feature Components: docs Reporter: Karen Smoler Miller This statistic does not appear in the documentation, and it should. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (GEODE-3736) CI failure: org.apache.geode.cache.query.dunit.CorruptedIndexIntegrationTest > rangeIndexCreationMustPassIfEntriesArePresentInDifferentBucketsAndQueriesMustUseThem fails
[
https://issues.apache.org/jira/browse/GEODE-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shelley Lynn Hughes-Godfrey updated GEODE-3736:
---
Summary: CI failure:
org.apache.geode.cache.query.dunit.CorruptedIndexIntegrationTest >
rangeIndexCreationMustPassIfEntriesArePresentInDifferentBucketsAndQueriesMustUseThem
fails with ClassCastException (was: CI failure: )
> CI failure: org.apache.geode.cache.query.dunit.CorruptedIndexIntegrationTest
> >
> rangeIndexCreationMustPassIfEntriesArePresentInDifferentBucketsAndQueriesMustUseThem
> fails with ClassCastException
> -
>
> Key: GEODE-3736
> URL: https://issues.apache.org/jira/browse/GEODE-3736
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Shelley Lynn Hughes-Godfrey
>
> {noformat}
> org.apache.geode.cache.query.dunit.CorruptedIndexIntegrationTest >
> rangeIndexCreationMustPassIfEntriesArePresentInDifferentBucketsAndQueriesMustUseThem
> FAILED
> java.lang.ClassCastException: java.lang.Integer cannot be cast to
> java.lang.String
> at java.lang.String.compareTo(String.java:111)
> at
> org.apache.geode.cache.query.internal.types.ExtendedNumericComparator.compare(ExtendedNumericComparator.java:46)
> at
> java.util.concurrent.ConcurrentSkipListMap.cpr(ConcurrentSkipListMap.java:655)
> at
> java.util.concurrent.ConcurrentSkipListMap.findPredecessor(ConcurrentSkipListMap.java:682)
> at
> java.util.concurrent.ConcurrentSkipListMap.doGet(ConcurrentSkipListMap.java:781)
> at
> java.util.concurrent.ConcurrentSkipListMap.get(ConcurrentSkipListMap.java:1546)
> at
> org.apache.geode.cache.query.internal.index.MemoryIndexStore.size(MemoryIndexStore.java:550)
> at
> org.apache.geode.cache.query.internal.index.CompactRangeIndex.getSizeEstimate(CompactRangeIndex.java:299)
> at
> org.apache.geode.cache.query.internal.index.AbstractMapIndex.getSizeEstimate(AbstractMapIndex.java:281)
> at
> org.apache.geode.cache.query.internal.CompiledComparison.getSizeEstimate(CompiledComparison.java:316)
> at
> org.apache.geode.cache.query.internal.AbstractGroupOrRangeJunction.getCondtionsSortedOnIncreasingEstimatedIndexResultSize(AbstractGroupOrRangeJunction.java:226)
> at
> org.apache.geode.cache.query.internal.AbstractGroupOrRangeJunction.auxFilterEvaluate(AbstractGroupOrRangeJunction.java:257)
> at
> org.apache.geode.cache.query.internal.AbstractGroupOrRangeJunction.filterEvaluate(AbstractGroupOrRangeJunction.java:169)
> at
> org.apache.geode.cache.query.internal.CompiledJunction.filterEvaluate(CompiledJunction.java:187)
> at
> org.apache.geode.cache.query.internal.CompiledSelect.evaluate(CompiledSelect.java:536)
> at
> org.apache.geode.cache.query.internal.CompiledSelect.evaluate(CompiledSelect.java:54)
> at
> org.apache.geode.cache.query.internal.DefaultQuery.executeUsingContext(DefaultQuery.java:558)
> at
> org.apache.geode.internal.cache.PRQueryProcessor.executeQueryOnBuckets(PRQueryProcessor.java:382)
> at
> org.apache.geode.internal.cache.PRQueryProcessor.executeSequentially(PRQueryProcessor.java:347)
> at
> org.apache.geode.internal.cache.PRQueryProcessor.executeQuery(PRQueryProcessor.java:138)
> at
> org.apache.geode.internal.cache.PartitionedRegionQueryEvaluator.executeQueryOnLocalNode(PartitionedRegionQueryEvaluator.java:909)
> at
> org.apache.geode.internal.cache.PartitionedRegionQueryEvaluator.executeQueryOnRemoteAndLocalNodes(PartitionedRegionQueryEvaluator.java:327)
> at
> org.apache.geode.internal.cache.PartitionedRegionQueryEvaluator.queryBuckets(PartitionedRegionQueryEvaluator.java:445)
> at
> org.apache.geode.internal.cache.PartitionedRegion.doExecuteQuery(PartitionedRegion.java:1888)
> at
> org.apache.geode.internal.cache.PartitionedRegion.executeQuery(PartitionedRegion.java:1817)
> at
> org.apache.geode.cache.query.internal.DefaultQuery.execute(DefaultQuery.java:361)
> at
> org.apache.geode.cache.query.internal.DefaultQuery.execute(DefaultQuery.java:319)
> at
> org.apache.geode.cache.query.dunit.CorruptedIndexIntegrationTest.rangeIndexCreationMustPassIfEntriesArePresentInDifferentBucketsAndQueriesMustUseThem(CorruptedIndexIntegrationTest.java:281)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (GEODE-3736) CI failure:
[
https://issues.apache.org/jira/browse/GEODE-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shelley Lynn Hughes-Godfrey updated GEODE-3736:
---
Summary: CI failure: (was:
org.apache.geode.cache.query.dunit.CorruptedIndexIntegrationTest >
rangeIndexCreationMustPassIfEntriesArePresentInDifferentBucketsAndQueriesMustUseThem
fails with ClassCastException)
> CI failure:
>
>
> Key: GEODE-3736
> URL: https://issues.apache.org/jira/browse/GEODE-3736
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Shelley Lynn Hughes-Godfrey
>
> {noformat}
> org.apache.geode.cache.query.dunit.CorruptedIndexIntegrationTest >
> rangeIndexCreationMustPassIfEntriesArePresentInDifferentBucketsAndQueriesMustUseThem
> FAILED
> java.lang.ClassCastException: java.lang.Integer cannot be cast to
> java.lang.String
> at java.lang.String.compareTo(String.java:111)
> at
> org.apache.geode.cache.query.internal.types.ExtendedNumericComparator.compare(ExtendedNumericComparator.java:46)
> at
> java.util.concurrent.ConcurrentSkipListMap.cpr(ConcurrentSkipListMap.java:655)
> at
> java.util.concurrent.ConcurrentSkipListMap.findPredecessor(ConcurrentSkipListMap.java:682)
> at
> java.util.concurrent.ConcurrentSkipListMap.doGet(ConcurrentSkipListMap.java:781)
> at
> java.util.concurrent.ConcurrentSkipListMap.get(ConcurrentSkipListMap.java:1546)
> at
> org.apache.geode.cache.query.internal.index.MemoryIndexStore.size(MemoryIndexStore.java:550)
> at
> org.apache.geode.cache.query.internal.index.CompactRangeIndex.getSizeEstimate(CompactRangeIndex.java:299)
> at
> org.apache.geode.cache.query.internal.index.AbstractMapIndex.getSizeEstimate(AbstractMapIndex.java:281)
> at
> org.apache.geode.cache.query.internal.CompiledComparison.getSizeEstimate(CompiledComparison.java:316)
> at
> org.apache.geode.cache.query.internal.AbstractGroupOrRangeJunction.getCondtionsSortedOnIncreasingEstimatedIndexResultSize(AbstractGroupOrRangeJunction.java:226)
> at
> org.apache.geode.cache.query.internal.AbstractGroupOrRangeJunction.auxFilterEvaluate(AbstractGroupOrRangeJunction.java:257)
> at
> org.apache.geode.cache.query.internal.AbstractGroupOrRangeJunction.filterEvaluate(AbstractGroupOrRangeJunction.java:169)
> at
> org.apache.geode.cache.query.internal.CompiledJunction.filterEvaluate(CompiledJunction.java:187)
> at
> org.apache.geode.cache.query.internal.CompiledSelect.evaluate(CompiledSelect.java:536)
> at
> org.apache.geode.cache.query.internal.CompiledSelect.evaluate(CompiledSelect.java:54)
> at
> org.apache.geode.cache.query.internal.DefaultQuery.executeUsingContext(DefaultQuery.java:558)
> at
> org.apache.geode.internal.cache.PRQueryProcessor.executeQueryOnBuckets(PRQueryProcessor.java:382)
> at
> org.apache.geode.internal.cache.PRQueryProcessor.executeSequentially(PRQueryProcessor.java:347)
> at
> org.apache.geode.internal.cache.PRQueryProcessor.executeQuery(PRQueryProcessor.java:138)
> at
> org.apache.geode.internal.cache.PartitionedRegionQueryEvaluator.executeQueryOnLocalNode(PartitionedRegionQueryEvaluator.java:909)
> at
> org.apache.geode.internal.cache.PartitionedRegionQueryEvaluator.executeQueryOnRemoteAndLocalNodes(PartitionedRegionQueryEvaluator.java:327)
> at
> org.apache.geode.internal.cache.PartitionedRegionQueryEvaluator.queryBuckets(PartitionedRegionQueryEvaluator.java:445)
> at
> org.apache.geode.internal.cache.PartitionedRegion.doExecuteQuery(PartitionedRegion.java:1888)
> at
> org.apache.geode.internal.cache.PartitionedRegion.executeQuery(PartitionedRegion.java:1817)
> at
> org.apache.geode.cache.query.internal.DefaultQuery.execute(DefaultQuery.java:361)
> at
> org.apache.geode.cache.query.internal.DefaultQuery.execute(DefaultQuery.java:319)
> at
> org.apache.geode.cache.query.dunit.CorruptedIndexIntegrationTest.rangeIndexCreationMustPassIfEntriesArePresentInDifferentBucketsAndQueriesMustUseThem(CorruptedIndexIntegrationTest.java:281)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (GEODE-3735) CI failure: FunctionCommandsDUnitTest should be refactored to use new new test rules
[
https://issues.apache.org/jira/browse/GEODE-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shelley Lynn Hughes-Godfrey updated GEODE-3735:
---
Summary: CI failure: FunctionCommandsDUnitTest should be refactored to use
new new test rules (was: FunctionCommandsDUnitTest should be refactored to use
new new test rules)
> CI failure: FunctionCommandsDUnitTest should be refactored to use new new
> test rules
>
>
> Key: GEODE-3735
> URL: https://issues.apache.org/jira/browse/GEODE-3735
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.3.0
>Reporter: Shelley Lynn Hughes-Godfrey
>
> FunctionCommandsDUnitTest is using CliCommandTestBase, which is a deprecated
> class. It should be refactored to use more current test rules.
> This causes the test to fail periodically:
> {noformat}
> org.apache.geode.management.internal.cli.commands.FunctionCommandsDUnitTest >
> testExecuteFunctionOnMembersWithArgsAndCustomResultCollector FAILED
> java.lang.AssertionError: Execution of connect
> --jmx-manager=d7f7e5c3-e656-43bc-67eb-97cb1606b8fc[20827] failed to connect
> to manager d7f7e5c3-e656-43bc-67eb-97cb1606b8fc[20827] result=Could not
> connect to : [host=d7f7e5c3-e656-43bc-67eb-97cb1606b8fc, port=20827]. Failed
> to retrieve RMIServer stub: javax.naming.CommunicationException [Root
> exception is java.rmi.NoSuchObjectException: no such object in table]
> at
> org.apache.geode.management.internal.cli.commands.CliCommandTestBase.connect(CliCommandTestBase.java:270)
> at
> org.apache.geode.management.internal.cli.commands.CliCommandTestBase.connect(CliCommandTestBase.java:242)
> at
> org.apache.geode.management.internal.cli.commands.CliCommandTestBase.setUpJmxManagerOnVm0ThenConnect(CliCommandTestBase.java:143)
> at
> org.apache.geode.management.internal.cli.commands.FunctionCommandsDUnitTest.testExecuteFunctionOnMembersWithArgsAndCustomResultCollector(FunctionCommandsDUnitTest.java:396)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (GEODE-3739) Amend current protocol Username / password to mimic the current SecurityManager implementation
Udo Kohlmeyer created GEODE-3739: Summary: Amend current protocol Username / password to mimic the current SecurityManager implementation Key: GEODE-3739 URL: https://issues.apache.org/jira/browse/GEODE-3739 Project: Geode Issue Type: Improvement Components: client/server Reporter: Udo Kohlmeyer The current implementation of the simple username password authentication has a very specific message. The SimpleUsernamePassword authentication class then processes that messages and populates very specific properties and passes that through to the SecurityManager. Given that the securityManager implementation is custom this approach is very limiting. The new implementation would need to better mimic the generic properties that are passed through without having to manually set any properties. A suggestion is to use a more generic Properties-based authenticator, that will take the properties that a client sets and pass them through directly to the SecurityManager without interfering with the message other than deserializing it from a hash into properties. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (GEODE-3739) Amend current protocol Username / password to mimic the current SecurityManager implementation
[ https://issues.apache.org/jira/browse/GEODE-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer reassigned GEODE-3739: Assignee: Galen O'Sullivan > Amend current protocol Username / password to mimic the current > SecurityManager implementation > -- > > Key: GEODE-3739 > URL: https://issues.apache.org/jira/browse/GEODE-3739 > Project: Geode > Issue Type: Improvement > Components: client/server >Reporter: Udo Kohlmeyer >Assignee: Galen O'Sullivan > > The current implementation of the simple username password authentication has > a very specific message. The SimpleUsernamePassword authentication class then > processes that messages and populates very specific properties and passes > that through to the SecurityManager. > Given that the securityManager implementation is custom this approach is very > limiting. The new implementation would need to better mimic the generic > properties that are passed through without having to manually set any > properties. > A suggestion is to use a more generic Properties-based authenticator, that > will take the properties that a client sets and pass them through directly to > the SecurityManager without interfering with the message other than > deserializing it from a hash into properties. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (GEODE-3738) CI Failure: org.apache.geode.security.ClientAuthorizationDUnitTest
[
https://issues.apache.org/jira/browse/GEODE-3738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16189952#comment-16189952
]
Jared Stewart commented on GEODE-3738:
--
{noformat}
Standard Output
running against these versions: [000, 120, 110, 111, 100]
Previously run tests: [RemoveAllCacheListenerClientServerRegressionTest,
ConnectionPoolAndLoaderDUnitTest, PartitionRegionHelperDUnitTest,
ParallelSnapshotDUnitTest, SnapshotByteArrayDUnitTest, SnapshotDUnitTest,
IntegratedSecurityPeerAuthDistributedTest, ClientMultiUserAuthzDUnitTest,
ClientGetPutAuthDUnitTest, PostProcessorDUnitTest, PDXPostProcessorDUnitTest,
ClientAuthorizationDUnitTest, SecurityManagerLifecycleDistributedTest,
ClientDestroyInvalidateAuthDUnitTest, ClientAuthenticationDUnitTest]
[vm0] [info 2017/10/03 08:41:28.026 UTC
tid=0x1b] Received method: org.apache.geode.test.dunit.NamedRunnable.run with 0
args on object: runnable(setupVM)
[vm0] [info 2017/10/03 08:41:28.027 UTC
tid=0x1b] Got result: null
[vm0] from org.apache.geode.test.dunit.NamedRunnable.run with 0 args on
object: runnable(setupVM) (took 0 ms)
[vm1] [info 2017/10/03 08:41:28.027 UTC
tid=0x1b] Received method: org.apache.geode.test.dunit.NamedRunnable.run with 0
args on object: runnable(setupVM)
[vm1] [info 2017/10/03 08:41:28.028 UTC
tid=0x1b] Got result: null
[vm1] from org.apache.geode.test.dunit.NamedRunnable.run with 0 args on
object: runnable(setupVM) (took 0 ms)
[vm2] [info 2017/10/03 08:41:28.029 UTC
tid=0x24] Received method: org.apache.geode.test.dunit.NamedRunnable.run with 0
args on object: runnable(setupVM)
[vm2] [info 2017/10/03 08:41:28.029 UTC
tid=0x24] Got result: null
[vm2] from org.apache.geode.test.dunit.NamedRunnable.run with 0 args on
object: runnable(setupVM) (took 0 ms)
[vm3] [info 2017/10/03 08:41:28.031 UTC
tid=0x1b] Received method: org.apache.geode.test.dunit.NamedRunnable.run with 0
args on object: runnable(setupVM)
[vm3] [info 2017/10/03 08:41:28.032 UTC
tid=0x1b] Got result: null
[vm3] from org.apache.geode.test.dunit.NamedRunnable.run with 0 args on
object: runnable(setupVM) (took 0 ms)
[setup] START TEST ClientAuthenticationDUnitTest.testNoCredentials[0]
[vm0] [info 2017/10/03 08:41:28.047 UTC
tid=0x1b] Received method:
org.apache.geode.security.ClientAuthenticationTestCase$$Lambda$100/503795804.call
with 0 args on object:
org.apache.geode.security.ClientAuthenticationTestCase$$Lambda$100/503795804@670492ac
[vm0] [info 2017/10/03 08:41:28.048 UTC
tid=0x1b] Got result: false
[vm0] from
org.apache.geode.security.ClientAuthenticationTestCase$$Lambda$100/503795804.call
with 0 args on object:
org.apache.geode.security.ClientAuthenticationTestCase$$Lambda$100/503795804@670492ac
(took 0 ms)
[vm1] [info 2017/10/03 08:41:28.061 UTC
tid=0x1b] Received method:
org.apache.geode.security.ClientAuthenticationTestCase$$Lambda$112/468472380.call
with 0 args on object:
org.apache.geode.security.ClientAuthenticationTestCase$$Lambda$112/468472380@3452fdf
[vm1] [info 2017/10/03 08:41:28.061 UTC
tid=0x1b] Got result: false
[vm1] from
org.apache.geode.security.ClientAuthenticationTestCase$$Lambda$112/468472380.call
with 0 args on object:
org.apache.geode.security.ClientAuthenticationTestCase$$Lambda$112/468472380@3452fdf
(took 0 ms)
[info 2017/10/03 08:41:28.061 UTC tid=0x13] Connection refused: connect
[info 2017/10/03 08:41:28.062 UTC tid=0x13] Connection refused: connect
[vm0] [info 2017/10/03 08:41:28.062 UTC
tid=0x1b] Received method: org.apache.geode.test.dunit.IgnoredException$2.run
with 0 args on object: "IgnoredException addIgnoredException"
[vm0] [info 2017/10/03 08:41:28.062 UTC
tid=0x1b] Connection refused:
connect
[vm0] [info 2017/10/03 08:41:28.062 UTC
tid=0x1b] Connection refused:
connect
[vm0] [info 2017/10/03 08:41:28.062 UTC
tid=0x1b] Got result: null
[vm0] from org.apache.geode.test.dunit.IgnoredException$2.run with 0 args on
object: "IgnoredException addIgnoredException" (took 0 ms)
[vm1] [info 2017/10/03 08:41:28.063 UTC
tid=0x1b] Received method: org.apache.geode.test.dunit.IgnoredException$2.run
with 0 args on object: "IgnoredException addIgnoredException"
[vm1] [info 2017/10/03 08:41:28.063 UTC
tid=0x1b] Connection refused:
connect
[vm1] [info 2017/10/03 08:41:28.063 UTC
tid=0x1b] Connection refused:
connect
[vm1] [info 2017/10/03 08:41:28.063 UTC
tid=0x1b] Got result: null
[vm1] from org.apache.geode.test.dunit.IgnoredException$2.run with 0 args on
object: "IgnoredException addIgnoredException" (took 0 ms)
[vm2] [info 2017/10/03 08:41:28.064 UTC
tid=0x24] Received method: org.apache.geode.test.dunit.IgnoredException$2.run
with 0 args on object: "IgnoredException addIgnoredException"
[vm2] [info 2017/10/03 08:41:28.064 UTC
tid=0x24] Connection refused:
connect
[vm2] [info 2017/10/03 08:41:28.065 UTC
tid=0x24] Connection refused:
connect
[vm2] [info 2017/10/03 08:41:2
[jira] [Created] (GEODE-3738) CI Failure: org.apache.geode.security.ClientAuthorizationDUnitTest
Jared Stewart created GEODE-3738:
Summary: CI Failure:
org.apache.geode.security.ClientAuthorizationDUnitTest
Key: GEODE-3738
URL: https://issues.apache.org/jira/browse/GEODE-3738
Project: Geode
Issue Type: Bug
Components: security, tests
Reporter: Jared Stewart
{noformat}
Error
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.security.ClientAuthorizationDUnitTest$$Lambda$177/351125497.run
in VM 2 running on Host 2d21656aaf6b with 4 VMs with version 120
Stacktrace
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.security.ClientAuthorizationDUnitTest$$Lambda$177/351125497.run
in VM 2 running on Host 2d21656aaf6b with 4 VMs with version 120
at org.apache.geode.test.dunit.VM.invoke(VM.java:393)
at org.apache.geode.test.dunit.VM.invoke(VM.java:363)
at org.apache.geode.test.dunit.VM.invoke(VM.java:308)
at
org.apache.geode.security.ClientAuthorizationDUnitTest.testPutsGetsWithFailover(ClientAuthorizationDUnitTest.java:350)
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.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
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.GeneratedMethodAccessor443.invoke(Unknown Source)
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.GeneratedMethodAccessor442.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(Delegatin
[jira] [Closed] (GEODE-3573) Hang in start locator gfsh script
[
https://issues.apache.org/jira/browse/GEODE-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Deppe closed GEODE-3573.
-
Assignee: Jens Deppe (was: Jared Stewart)
> Hang in start locator gfsh script
> -
>
> Key: GEODE-3573
> URL: https://issues.apache.org/jira/browse/GEODE-3573
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.2.0
>Reporter: Jared Stewart
>Assignee: Jens Deppe
>
> The script used to start a cluster for testing by the native-client is
> hanging after "start locator":
> {noformat}
> #!/bin/sh
> set -e
> IPADDRESS="35.160.147.71"
> INTERNAL_IPADDRESS="172.31.38.126"
> /home/geode/geode/bin/gfsh \
> -e "start locator --name=locator
> --properties-file=/home/geode/ssl-settings/gemfire-security.properties
> --security-properties-file=/home/geode/ssl-settings/gfsecurity.properties
> --hostname-for-clients=${INTERNAL_IPADDRESS}
> --J=-Dgemfire.jmx-manager-hostname-for-clients=${INTERNAL_IPADDRESS}
> --bind-address=${INTERNAL_IPADDRESS}
> --J=-Dgeode.feature-protobuf-protocol=true" \
> -e "start server --name=protobuf
> --properties-file=/home/geode/ssl-settings/gemfire-security.properties
> --security-properties-file=/home/geode/ssl-settings/gfsecurity.properties
> --hostname-for-clients=${INTERNAL_IPADDRESS}
> --bind-address=${INTERNAL_IPADDRESS}
> --J=-Dgeode.feature-protobuf-protocol=true" \
> -e "create region --name=testregionname --type=PARTITION"
> {noformat}
> It appears that the locator is started and responding normally, but gfsh
> hangs and never moves on to "start server".
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (GEODE-3573) Hang in start locator gfsh script
[
https://issues.apache.org/jira/browse/GEODE-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Deppe resolved GEODE-3573.
---
Resolution: Cannot Reproduce
Worked with Mike, but couldn't reproduce the problem.
> Hang in start locator gfsh script
> -
>
> Key: GEODE-3573
> URL: https://issues.apache.org/jira/browse/GEODE-3573
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.2.0
>Reporter: Jared Stewart
>Assignee: Jared Stewart
>
> The script used to start a cluster for testing by the native-client is
> hanging after "start locator":
> {noformat}
> #!/bin/sh
> set -e
> IPADDRESS="35.160.147.71"
> INTERNAL_IPADDRESS="172.31.38.126"
> /home/geode/geode/bin/gfsh \
> -e "start locator --name=locator
> --properties-file=/home/geode/ssl-settings/gemfire-security.properties
> --security-properties-file=/home/geode/ssl-settings/gfsecurity.properties
> --hostname-for-clients=${INTERNAL_IPADDRESS}
> --J=-Dgemfire.jmx-manager-hostname-for-clients=${INTERNAL_IPADDRESS}
> --bind-address=${INTERNAL_IPADDRESS}
> --J=-Dgeode.feature-protobuf-protocol=true" \
> -e "start server --name=protobuf
> --properties-file=/home/geode/ssl-settings/gemfire-security.properties
> --security-properties-file=/home/geode/ssl-settings/gfsecurity.properties
> --hostname-for-clients=${INTERNAL_IPADDRESS}
> --bind-address=${INTERNAL_IPADDRESS}
> --J=-Dgeode.feature-protobuf-protocol=true" \
> -e "create region --name=testregionname --type=PARTITION"
> {noformat}
> It appears that the locator is started and responding normally, but gfsh
> hangs and never moves on to "start server".
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
