[jira] [Commented] (GEODE-4721) Being invoked within JTA Region.values() (and all iteration related operations) does return empty collection
[
https://issues.apache.org/jira/browse/GEODE-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379896#comment-16379896
]
Vadim Lotarev commented on GEODE-4721:
--
No, I don't use client proxy region. All operations are invoked within a
function on a server.
> Being invoked within JTA Region.values() (and all iteration related
> operations) does return empty collection
>
>
> Key: GEODE-4721
> URL: https://issues.apache.org/jira/browse/GEODE-4721
> Project: Geode
> Issue Type: Bug
> Components: regions, transactions
>Reporter: Vadim Lotarev
>Assignee: Eric Shu
>Priority: Critical
>
> {{Region.values()}} returns empty collection being invoked within JTA. Other
> operations returns data, for example this workaround works (though less
> efficient): {{region.getAll(region.keySet()).values()}}, also
> {{Region.size()}} returns correct value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4742) OQL operator '/' without surrounding spaces generates syntax error
[
https://issues.apache.org/jira/browse/GEODE-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379627#comment-16379627
]
Diane Hardman commented on GEODE-4742:
--
The fix for this involves significant changes to the OQL parser which will take
longer to implement and test.
In the meantime, please add to the documentation on using operators in the
WHERE clause to surround them with a space character.
> OQL operator '/' without surrounding spaces generates syntax error
> --
>
> Key: GEODE-4742
> URL: https://issues.apache.org/jira/browse/GEODE-4742
> Project: Geode
> Issue Type: Bug
> Components: docs, querying
>Reporter: Diane Hardman
>Priority: Major
>
> The following query will generate a syntax error:
> gfsh>query --query="select * from /example-region x where x.salary/2080 > 30"
> Result : false
> Message : Query is invalid due for error : unexpected token: salary>
> If I add surrounding spaces, the query is successful:
> gfsh>query --query="select * from /example-region x where x.salary / 2080 >
> 30"
> Result : true
> Limit : 100
> Rows : 11
>
> email | emplNumber | firstName | hoursPerWeek | lastName
> | salary
> -- | -- | - | |
> | --
> frankie.fo...@example.com | 10010 | Frankie | 30 | Forth
> | 10
> kris.c...@example.com | 10003 | Kris | 40 | Call
> | 75000
> bertie.b...@example.com | 10001 | Bertie | 40 | Bell
> | 8
> morgan.min...@example.com | 10021 | Morgan | 40 | Minnow
> | 8
> ricky.relia...@example.com | 10036 | Ricky | 40 | Reliable
> | 9
> ryan.r...@example.com | 10078 | Ryan | 40 | Redo
> | 75000
> skyler.s...@example.com | 10091 | Skyler | 40 | Skip
> | 9
> dale.dri...@example.com | 10006 | Dale | 40 | Driver
> | 9
> pat.p...@example.com | 10028 | Pat | 40 | Puts
> | 75000
> jessie@example.com | 10066 | Jessie | 20 | Jam
> | 8
> taylor.t...@example.com | 10045 | Taylor | 40 | Tack
> | 10
> I tested the other operators ('+', '-', '*', '%') which all seem to work
> correctly with or without surrounding spaces.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4742) OQL operator '/' without surrounding spaces generates syntax error
[
https://issues.apache.org/jira/browse/GEODE-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diane Hardman updated GEODE-4742:
-
Component/s: docs
> OQL operator '/' without surrounding spaces generates syntax error
> --
>
> Key: GEODE-4742
> URL: https://issues.apache.org/jira/browse/GEODE-4742
> Project: Geode
> Issue Type: Bug
> Components: docs, querying
>Reporter: Diane Hardman
>Priority: Major
>
> The following query will generate a syntax error:
> gfsh>query --query="select * from /example-region x where x.salary/2080 > 30"
> Result : false
> Message : Query is invalid due for error : unexpected token: salary>
> If I add surrounding spaces, the query is successful:
> gfsh>query --query="select * from /example-region x where x.salary / 2080 >
> 30"
> Result : true
> Limit : 100
> Rows : 11
>
> email | emplNumber | firstName | hoursPerWeek | lastName
> | salary
> -- | -- | - | |
> | --
> frankie.fo...@example.com | 10010 | Frankie | 30 | Forth
> | 10
> kris.c...@example.com | 10003 | Kris | 40 | Call
> | 75000
> bertie.b...@example.com | 10001 | Bertie | 40 | Bell
> | 8
> morgan.min...@example.com | 10021 | Morgan | 40 | Minnow
> | 8
> ricky.relia...@example.com | 10036 | Ricky | 40 | Reliable
> | 9
> ryan.r...@example.com | 10078 | Ryan | 40 | Redo
> | 75000
> skyler.s...@example.com | 10091 | Skyler | 40 | Skip
> | 9
> dale.dri...@example.com | 10006 | Dale | 40 | Driver
> | 9
> pat.p...@example.com | 10028 | Pat | 40 | Puts
> | 75000
> jessie@example.com | 10066 | Jessie | 20 | Jam
> | 8
> taylor.t...@example.com | 10045 | Taylor | 40 | Tack
> | 10
> I tested the other operators ('+', '-', '*', '%') which all seem to work
> correctly with or without surrounding spaces.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-210) Provide a canonical app to test freshly deployed Geode clusters
[ https://issues.apache.org/jira/browse/GEODE-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379572#comment-16379572 ] Anthony Baker commented on GEODE-210: - We have lots of geode examples available at https://github.com/apache/geode-examples. > Provide a canonical app to test freshly deployed Geode clusters > --- > > Key: GEODE-210 > URL: https://issues.apache.org/jira/browse/GEODE-210 > Project: Geode > Issue Type: Improvement > Components: general >Affects Versions: 1.0.0-incubating >Reporter: Roman Shaposhnik >Priority: Minor > > It would be nice to provide a few example apps to test freshly deployed Geode > clusters the same way that all Hadoop cluster deployment ends with running > Pi/Wordcount/etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-210) Provide a canonical app to test freshly deployed Geode clusters
[ https://issues.apache.org/jira/browse/GEODE-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker resolved GEODE-210. - Resolution: Fixed > Provide a canonical app to test freshly deployed Geode clusters > --- > > Key: GEODE-210 > URL: https://issues.apache.org/jira/browse/GEODE-210 > Project: Geode > Issue Type: Improvement > Components: general >Affects Versions: 1.0.0-incubating >Reporter: Roman Shaposhnik >Priority: Minor > > It would be nice to provide a few example apps to test freshly deployed Geode > clusters the same way that all Hadoop cluster deployment ends with running > Pi/Wordcount/etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-178) Spark connector needs to be integrated with Geode build and ci
[ https://issues.apache.org/jira/browse/GEODE-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker resolved GEODE-178. - Resolution: Won't Fix Closing this ticket due to inactivity. > Spark connector needs to be integrated with Geode build and ci > -- > > Key: GEODE-178 > URL: https://issues.apache.org/jira/browse/GEODE-178 > Project: Geode > Issue Type: Improvement >Reporter: Jason Huynh >Assignee: Jason Huynh >Priority: Major > > Currently the Spark connector is not being built during ci. We will want to > integrate the spark connector and it's tests into ci. > Some of the tasks that may be required: > 1.) Remove the dependency of the geode jar because those won't be published > until after spark connector is built. Instead I think we need to add it as > an unmanaged dependency. > 2.) Create gradle taskes to execute sbt build and tests -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-194) Geode Spark Connector does not support Spark 2.0
[ https://issues.apache.org/jira/browse/GEODE-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker resolved GEODE-194. - Resolution: Won't Fix Closing this ticket due to inactivity. > Geode Spark Connector does not support Spark 2.0 > > > Key: GEODE-194 > URL: https://issues.apache.org/jira/browse/GEODE-194 > Project: Geode > Issue Type: Bug > Components: extensions >Reporter: Jianxia Chen >Priority: Major > Labels: experimental, gsoc2016 > > The BasicIntegrationTest fails when using spark 1.4. e.g. > [info] - GemFire OQL query with more complex UDT: Partitioned Region *** > FAILED *** > [info] org.apache.spark.SparkException: Job aborted due to stage failure: > Task 0 in stage 24.0 failed 1 times, most recent failure: Lost task 0.0 in > stage 24.0 (TID 48, localhost): scala.MatchError: > [info]Portfolio [id=3 status=active type=type3 > [info]AOL:Position [secId=AOL qty=978.0 mktValue=40.373], > [info]MSFT:Position [secId=MSFT qty=98327.0 mktValue=23.32]] > (of class ittest.io.pivotal.gemfire.spark.connector.Portfolio) > [info]at > org.apache.spark.sql.catalyst.CatalystTypeConverters$$anonfun$createToCatalystConverter$4.apply(CatalystTypeConverters.scala:178) > [info]at > org.apache.spark.sql.execution.RDDConversions$$anonfun$rowToRowRdd$1$$anonfun$apply$2.apply(ExistingRDD.scala:62) > [info]at > org.apache.spark.sql.execution.RDDConversions$$anonfun$rowToRowRdd$1$$anonfun$apply$2.apply(ExistingRDD.scala:59) > [info]at scala.collection.Iterator$$anon$11.next(Iterator.scala:328) > [info]at scala.collection.Iterator$$anon$11.next(Iterator.scala:328) > [info]at scala.collection.Iterator$class.foreach(Iterator.scala:727) > [info]at > scala.collection.AbstractIterator.foreach(Iterator.scala:1157) > [info]at > scala.collection.generic.Growable$class.$plus$plus$eq(Growable.scala:48) > [info]at > scala.collection.mutable.ArrayBuffer.$plus$plus$eq(ArrayBuffer.scala:103) > [info]at > scala.collection.mutable.ArrayBuffer.$plus$plus$eq(ArrayBuffer.scala:47) > [info]at > scala.collection.TraversableOnce$class.to(TraversableOnce.scala:273) > [info]at scala.collection.AbstractIterator.to(Iterator.scala:1157) > [info]at > scala.collection.TraversableOnce$class.toBuffer(TraversableOnce.scala:265) > [info]at > scala.collection.AbstractIterator.toBuffer(Iterator.scala:1157) > [info]at > scala.collection.TraversableOnce$class.toArray(TraversableOnce.scala:252) > [info]at > scala.collection.AbstractIterator.toArray(Iterator.scala:1157) > [info]at > org.apache.spark.rdd.RDD$$anonfun$collect$1$$anonfun$12.apply(RDD.scala:885) > [info]at > org.apache.spark.rdd.RDD$$anonfun$collect$1$$anonfun$12.apply(RDD.scala:885) > [info]at > org.apache.spark.SparkContext$$anonfun$runJob$5.apply(SparkContext.scala:1765) > [info]at > org.apache.spark.SparkContext$$anonfun$runJob$5.apply(SparkContext.scala:1765) > [info]at > org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:63) > [info]at org.apache.spark.scheduler.Task.run(Task.scala:70) > [info]at > org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:213) > [info]at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > [info]at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > [info]at java.lang.Thread.run(Thread.java:745) > [info] > [info] Driver stacktrace: > [info] at > org.apache.spark.scheduler.DAGScheduler.org$apache$spark$scheduler$DAGScheduler$$failJobAndIndependentStages(DAGScheduler.scala:1266) > [info] at > org.apache.spark.scheduler.DAGScheduler$$anonfun$abortStage$1.apply(DAGScheduler.scala:1257) > [info] at > org.apache.spark.scheduler.DAGScheduler$$anonfun$abortStage$1.apply(DAGScheduler.scala:1256) > [info] at > scala.collection.mutable.ResizableArray$class.foreach(ResizableArray.scala:59) > [info] at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:47) > [info] at > org.apache.spark.scheduler.DAGScheduler.abortStage(DAGScheduler.scala:1256) > [info] at > org.apache.spark.scheduler.DAGScheduler$$anonfun$handleTaskSetFailed$1.apply(DAGScheduler.scala:730) > [info] at > org.apache.spark.scheduler.DAGScheduler$$anonfun$handleTaskSetFailed$1.apply(DAGScheduler.scala:730) > [info] at scala.Option.foreach(Option.scala:236) > [info] at > org.apache.spark.scheduler.DAGScheduler.handleTaskSetFailed(DAGScheduler.scala:730) > [info] ... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-137) Spark Connector: should connect to local GemFire server if possible
[ https://issues.apache.org/jira/browse/GEODE-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker resolved GEODE-137. - Resolution: Incomplete > Spark Connector: should connect to local GemFire server if possible > --- > > Key: GEODE-137 > URL: https://issues.apache.org/jira/browse/GEODE-137 > Project: Geode > Issue Type: Bug >Reporter: Qihong Chen >Assignee: Qihong Chen >Priority: Major > Original Estimate: 96h > Remaining Estimate: 96h > > DefaultGemFireConnection uses ClientCacheFactory with locator info to create > ClientCache instance. In this case, the ClientCache doesn't connect to the > GemFire/Geode server on the same host if there's one. This cause more network > traffic and less efficient. > ClientCacheFactory can create ClientCache based on GemFire server(s) info as > well. Therefore, we can force the ClientCache connects to local GemFire > server if possible. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-137) Spark Connector: should connect to local GemFire server if possible
[ https://issues.apache.org/jira/browse/GEODE-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379565#comment-16379565 ] Anthony Baker commented on GEODE-137: - Closing this ticket due to inactivity. > Spark Connector: should connect to local GemFire server if possible > --- > > Key: GEODE-137 > URL: https://issues.apache.org/jira/browse/GEODE-137 > Project: Geode > Issue Type: Bug >Reporter: Qihong Chen >Assignee: Qihong Chen >Priority: Major > Original Estimate: 96h > Remaining Estimate: 96h > > DefaultGemFireConnection uses ClientCacheFactory with locator info to create > ClientCache instance. In this case, the ClientCache doesn't connect to the > GemFire/Geode server on the same host if there's one. This cause more network > traffic and less efficient. > ClientCacheFactory can create ClientCache based on GemFire server(s) info as > well. Therefore, we can force the ClientCache connects to local GemFire > server if possible. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-62) Commit CI job to make sure develop branch passes the unit test upon patch commits.
[ https://issues.apache.org/jira/browse/GEODE-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker resolved GEODE-62. Resolution: Won't Fix Closing this ticket due to inactivity. > Commit CI job to make sure develop branch passes the unit test upon patch > commits. > -- > > Key: GEODE-62 > URL: https://issues.apache.org/jira/browse/GEODE-62 > Project: Geode > Issue Type: Sub-task > Components: build >Reporter: jun aoki >Priority: Major > > Similar to this > https://builds.apache.org/view/A-D/view/Ambari/job/Ambari-trunk-Commit/ > to make sure develop branch is clean -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-63) Establish contribution workflow
[ https://issues.apache.org/jira/browse/GEODE-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker resolved GEODE-63. Resolution: Won't Fix Closing this ticket due to inactivity. > Establish contribution workflow > > > Key: GEODE-63 > URL: https://issues.apache.org/jira/browse/GEODE-63 > Project: Geode > Issue Type: Sub-task > Components: build >Reporter: jun aoki >Priority: Major > > We can start with Ambari workflow as draft, and let's gather what and how the > Geode community drives the project. > wiki page > https://cwiki.apache.org/confluence/display/AMBARI/Development+Process+for+New+Major+Features > workflow > https://docs.google.com/document/d/1hz7qjGKkNeckMibEs67ZmAa2kxjie0zkG6H_IiC2RgA/edit -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-61) test-patch CI job to make sure submitted patches to Geode jira has minimum quality
[ https://issues.apache.org/jira/browse/GEODE-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker resolved GEODE-61. Resolution: Won't Fix Closing this ticket due to inactivity. > test-patch CI job to make sure submitted patches to Geode jira has minimum > quality > -- > > Key: GEODE-61 > URL: https://issues.apache.org/jira/browse/GEODE-61 > Project: Geode > Issue Type: Sub-task > Components: build >Reporter: jun aoki >Assignee: jun aoki >Priority: Major > > https://builds.apache.org/view/A-D/view/Ambari/job/Ambari-trunk-find-patches-available/ > This job identifies newly submitted patches and create execution queue on the > next job > https://builds.apache.org/view/A-D/view/Ambari/job/Ambari-trunk-test-patch/ > This second job is to make sure a patch does not break build, and run Apache > RAT, unit test etc. > The main script of test-patch should look like this > https://github.com/apache/ambari/blob/trunk/dev-support/test-patch.sh > which I copied one from Hadoop core project and I modified it for Ambari. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-70) Dummy Ticket for test-patch work
[ https://issues.apache.org/jira/browse/GEODE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker resolved GEODE-70. Resolution: Won't Fix Closing this ticket due to inactivity. > Dummy Ticket for test-patch work > > > Key: GEODE-70 > URL: https://issues.apache.org/jira/browse/GEODE-70 > Project: Geode > Issue Type: Sub-task > Components: build >Reporter: jun aoki >Assignee: jun aoki >Priority: Trivial > Attachments: GEODE-70.patch > > > The Geode community. Please ignore this ticket as this is used to test > test-patch job worked on https://issues.apache.org/jira/browse/GEODE-61 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-59) Geode project to have a open process for all contributors and community members
[ https://issues.apache.org/jira/browse/GEODE-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker resolved GEODE-59. Resolution: Won't Fix Closing this ticket due to inactivity. > Geode project to have a open process for all contributors and community > members > --- > > Key: GEODE-59 > URL: https://issues.apache.org/jira/browse/GEODE-59 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: jun aoki >Assignee: jun aoki >Priority: Major > > This involves setting up some CI jobs on builds.apache.org as well as create > a consensus of the contribution workflow. > The initial email discussion is here. > http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201506.mbox/browser > I'm listing a few sub tickets to archive this based on the exercise of Ambari > to start with (but of course we are going to find out what best for the Geode > community) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-55) Support SASL for memcached
[ https://issues.apache.org/jira/browse/GEODE-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker resolved GEODE-55. Resolution: Won't Fix Closing this ticket due to inactivity. > Support SASL for memcached > -- > > Key: GEODE-55 > URL: https://issues.apache.org/jira/browse/GEODE-55 > Project: Geode > Issue Type: Improvement > Components: extensions >Reporter: Swapnil Bawaskar >Priority: Major > > Geode implementation supports memcached protocol and is even > [memcapable|http://libmemcached.org/Memcapable.html]. The current > implementation lacks support for authentication. memcached supports > authentication using SASL. The protocol for SASL commands is described at: > http://code.google.com/p/memcached/wiki/SASLAuthProtocol -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-57) Update Apache Geode dependencies to their latest GA versions.
[
https://issues.apache.org/jira/browse/GEODE-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379548#comment-16379548
]
Anthony Baker commented on GEODE-57:
Closing this issue as this is an ongoing activity. We've also updated library
versions multiple times since this ticket was opened.
> Update Apache Geode dependencies to their latest GA versions.
> -
>
> Key: GEODE-57
> URL: https://issues.apache.org/jira/browse/GEODE-57
> Project: Geode
> Issue Type: Improvement
> Components: build
>Affects Versions: 1.0.0-incubating
> Environment: All
>Reporter: John Blum
>Priority: Major
> Labels: ApacheGeode, Dependencies, LIBS
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Before _Apache Geode_ has it's first official (GA) release, all dependencies
> (such as Apache {{commons-io}}) should be updated to the latest, stable GA
> release and tested accordingly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-4406) Improve granularity of permissions for new client protocol
[ https://issues.apache.org/jira/browse/GEODE-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Rowe resolved GEODE-4406. --- Resolution: Fixed Fix Version/s: 1.5.0 > Improve granularity of permissions for new client protocol > -- > > Key: GEODE-4406 > URL: https://issues.apache.org/jira/browse/GEODE-4406 > Project: Geode > Issue Type: New Feature > Components: client/server >Reporter: Galen O'Sullivan >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Currently, the new client protocol requires all DATA:READ permissions to do a > region.get() . If a user only has DATA:READ:regionName , they won't be > permitted to execute commands on the region, even though they have > permissions. We should fix this for all the other operations too. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-57) Update Apache Geode dependencies to their latest GA versions.
[
https://issues.apache.org/jira/browse/GEODE-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker resolved GEODE-57.
Resolution: Done
> Update Apache Geode dependencies to their latest GA versions.
> -
>
> Key: GEODE-57
> URL: https://issues.apache.org/jira/browse/GEODE-57
> Project: Geode
> Issue Type: Improvement
> Components: build
>Affects Versions: 1.0.0-incubating
> Environment: All
>Reporter: John Blum
>Priority: Major
> Labels: ApacheGeode, Dependencies, LIBS
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Before _Apache Geode_ has it's first official (GA) release, all dependencies
> (such as Apache {{commons-io}}) should be updated to the latest, stable GA
> release and tested accordingly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4685) Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal
[ https://issues.apache.org/jira/browse/GEODE-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379542#comment-16379542 ] ASF subversion and git services commented on GEODE-4685: Commit 830f49b06f1744c85da98c59eb8e030019646be5 in geode's branch refs/heads/feature/GEODE-4685 from Udo [ https://gitbox.apache.org/repos/asf?p=geode.git;h=830f49b ] GEODE-4685: Moving of static DefaultQuery.setPdxReadSerialized to the TypeRegistry. Cleaned up the overriding of readSerialized to reset to previous value. Added cache to AbstractJdbcCallback.java so that children classes can access it. Replaced AtomicLong with LongAdder. > Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal > -- > > Key: GEODE-4685 > URL: https://issues.apache.org/jira/browse/GEODE-4685 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: nabarun >Assignee: Udo Kohlmeyer >Priority: Major > > Replace with the solution from GEODE-4679 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4406) Improve granularity of permissions for new client protocol
[ https://issues.apache.org/jira/browse/GEODE-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379540#comment-16379540 ] ASF subversion and git services commented on GEODE-4406: Commit fa1f2ac98070bf445f24ea3b2a8f3ce5cf6b5b7d in geode's branch refs/heads/develop from [~WireBaron] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=fa1f2ac ] GEODE-4406: Improve authorization granularity for protobuf (#1514) > Improve granularity of permissions for new client protocol > -- > > Key: GEODE-4406 > URL: https://issues.apache.org/jira/browse/GEODE-4406 > Project: Geode > Issue Type: New Feature > Components: client/server >Reporter: Galen O'Sullivan >Priority: Major > Labels: pull-request-available > Time Spent: 1h > Remaining Estimate: 0h > > Currently, the new client protocol requires all DATA:READ permissions to do a > region.get() . If a user only has DATA:READ:regionName , they won't be > permitted to execute commands on the region, even though they have > permissions. We should fix this for all the other operations too. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-2284) HelpCommandsIntegrationTest is too brittle
[ https://issues.apache.org/jira/browse/GEODE-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn resolved GEODE-2284. --- Resolution: Won't Do > HelpCommandsIntegrationTest is too brittle > -- > > Key: GEODE-2284 > URL: https://issues.apache.org/jira/browse/GEODE-2284 > Project: Geode > Issue Type: Bug > Components: gfsh, tests >Affects Versions: 1.0.0-incubating >Reporter: Kirk Lund >Priority: Major > Labels: Brittle, GfshHelpCommands, IntegrationTest > > HelpCommandsIntegrationTest compares the help output for each command to > golden files. Any change to command help requires another change to the > golden file. This does not provide real value other than to tell you that you > changed the help output which then slows you down because you have to change > it again but in the test. > See any resource on JUnit best practices about tests that are too brittle. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-2237) Geode classes should use Log4J2 Logger instead of JUL or LogWriter
[
https://issues.apache.org/jira/browse/GEODE-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barbara Pruijn resolved GEODE-2237.
---
Resolution: Won't Fix
> Geode classes should use Log4J2 Logger instead of JUL or LogWriter
> --
>
> Key: GEODE-2237
> URL: https://issues.apache.org/jira/browse/GEODE-2237
> Project: Geode
> Issue Type: Bug
> Components: logging
>Affects Versions: 1.0.0-incubating, 1.1.0
>Reporter: Kirk Lund
>Priority: Trivial
> Labels: Log4j2
>
> Several classes including AbstractLauncher are using JUL instead of Log4J2:
> {noformat}
> import java.util.logging.Logger;
> ...
> // TODO: use log4j logger instead of JUL
> protected Logger logger = Logger.getLogger(getClass().getName());
> {noformat}
> Any other classes that are using a logger or logwriter that isn't from Log4J2
> API should be modified to use Log4J2.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-2220) StatTypesAreRolledOverRegressionTest.closedInstanceShouldHaveTypeInRolledArchives fails with TimeoutException on Windows
[
https://issues.apache.org/jira/browse/GEODE-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barbara Pruijn resolved GEODE-2220.
---
Resolution: Won't Do
> StatTypesAreRolledOverRegressionTest.closedInstanceShouldHaveTypeInRolledArchives
> fails with TimeoutException on Windows
>
>
> Key: GEODE-2220
> URL: https://issues.apache.org/jira/browse/GEODE-2220
> Project: Geode
> Issue Type: Bug
> Components: statistics, tests
>Affects Versions: 1.0.0-incubating
> Environment: Windows
>Reporter: Kirk Lund
>Priority: Major
> Labels: IntegrationTest, Windows
>
> This test had some interesting timing issues when comparing how it runs on
> Mac vs Linux which seemed to involve the difference in file sizes on file
> system. It's been tuned to pass on Mac and Linux but probably needs further
> work for Windows as well.
> {noformat}
> java.util.concurrent.TimeoutException: File
> C:\cygwin\tmp\junit3404591601445938731\closedInstanceShouldHaveTypeInRolledArchives-01-01.gfs
> does not exist after 3946 samples within 1 MINUTES
> at
> org.apache.geode.internal.statistics.StatTypesAreRolledOverRegressionTest.sampleUntilFileExists(StatTypesAreRolledOverRegressionTest.java:170)
> at
> org.apache.geode.internal.statistics.StatTypesAreRolledOverRegressionTest.closedInstanceShouldHaveTypeInRolledArchives(StatTypesAreRolledOverRegressionTest.java:128)
> 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.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.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:497)
> 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
[jira] [Resolved] (GEODE-2202) AbstractLauncher.ServiceState should be Serializable
[ https://issues.apache.org/jira/browse/GEODE-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn resolved GEODE-2202. --- Resolution: Won't Do > AbstractLauncher.ServiceState should be Serializable > > > Key: GEODE-2202 > URL: https://issues.apache.org/jira/browse/GEODE-2202 > Project: Geode > Issue Type: Bug > Components: gfsh, management >Reporter: Kirk Lund >Priority: Major > Labels: StartLocatorCommand, StartServerCommand, > StatusLocatorCommand, StatusServerCommand > > AbstractLauncher.ServiceState should be Serializable. ServiceState is an > immutable result returned from start/status/stop commands. Making it > serializable will allow it to be more flexible for testing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-2132) Allow PostProcessor to be specified in Region Attributes
[ https://issues.apache.org/jira/browse/GEODE-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn resolved GEODE-2132. --- Resolution: Won't Do > Allow PostProcessor to be specified in Region Attributes > > > Key: GEODE-2132 > URL: https://issues.apache.org/jira/browse/GEODE-2132 > Project: Geode > Issue Type: Wish > Components: security >Reporter: Kirk Lund >Priority: Major > > Different Regions have different types of values and the PostProcessor needed > for different Regions may require very different code. If a single global > PostProcessor is used for values in multiple Regions, then it would get very > complicated with lots of instanceof or other value type checks. > Allowing PostProcessor to be specified in Region Attributes would not > diminish the value of having the current single global PostProcessor added by > GEODE-17. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4685) Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal
[ https://issues.apache.org/jira/browse/GEODE-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379526#comment-16379526 ] ASF subversion and git services commented on GEODE-4685: Commit 4c64927d769daf744f057e619066f2d77af6c64f in geode's branch refs/heads/feature/GEODE-4685 from Udo [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4c64927 ] GEODE-4685: Cleaned up the overriding of readSerialized to reset to previous value. Added cache to AbstractJdbcCallback.java so that children classes can access it. Replaced AtomicLong with LongAdder. > Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal > -- > > Key: GEODE-4685 > URL: https://issues.apache.org/jira/browse/GEODE-4685 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: nabarun >Assignee: Udo Kohlmeyer >Priority: Major > > Replace with the solution from GEODE-4679 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-2010) GFSH DistributedTests are in need overhauling
[ https://issues.apache.org/jira/browse/GEODE-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn resolved GEODE-2010. --- Resolution: Won't Do > GFSH DistributedTests are in need overhauling > - > > Key: GEODE-2010 > URL: https://issues.apache.org/jira/browse/GEODE-2010 > Project: Geode > Issue Type: Bug > Components: gfsh, management, tests >Reporter: Kirk Lund >Priority: Major > > Many of these tests write to the disk without using TemporaryFolder so you > end up with RAT failures after running a test in an IDE unless you remember > to search for the output from the test to delete it. > These tests also use HeadlessGfsh or TestableGfsh. Both are very buggy, eat > exceptions, have strange timeouts and can cause flaky test failures. > List of tests that are known to leave behind testing artifacts on disk: > * CreateAlterDestroyRegionCommandsDUnitTest -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-1928) MBean custom composite data types should be serializable
[ https://issues.apache.org/jira/browse/GEODE-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn resolved GEODE-1928. --- Resolution: Won't Do > MBean custom composite data types should be serializable > > > Key: GEODE-1928 > URL: https://issues.apache.org/jira/browse/GEODE-1928 > Project: Geode > Issue Type: Improvement > Components: management >Reporter: Kirk Lund >Priority: Minor > > While working with the CacheManagementDUnitTest I noticed that OSMetrics and > JVMMetrics (custom composite data types for Geode MBeans) are not > Serializable. These any any other custom composite data types that Geode has > should implement Serializable. This doesn't cause any issues for the User > because of the where/when they are currently constructed but best practice > dictates that they should be and this also facilitates DUnit testing for the > MBeans because you can serialize one and return it from a VM.invoke method. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-2001) Refactor logging tests with a junit rule
[ https://issues.apache.org/jira/browse/GEODE-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn resolved GEODE-2001. --- Resolution: Won't Do > Refactor logging tests with a junit rule > > > Key: GEODE-2001 > URL: https://issues.apache.org/jira/browse/GEODE-2001 > Project: Geode > Issue Type: Wish > Components: logging, tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Minor > > Refactor logging tests with a junit rule > The tests that would benefit the most are: > CustomConfigWithCacheIntegrationTest > CustomConfigWithLogServiceIntegrationTest -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-1946) MBean custom composite data types should return empty arrays instead of null
[
https://issues.apache.org/jira/browse/GEODE-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barbara Pruijn resolved GEODE-1946.
---
Resolution: Won't Do
> MBean custom composite data types should return empty arrays instead of null
>
>
> Key: GEODE-1946
> URL: https://issues.apache.org/jira/browse/GEODE-1946
> Project: Geode
> Issue Type: Wish
> Components: management
>Reporter: Kirk Lund
>Priority: Minor
>
> Example:
> org.apache.geode.management.DiskBackupStatus.getOfflineDiskStores() returns a
> String array of the disk stores that were offline during backup. If there are
> no offline disk stores, it should return new String[]{} instead of null.
> {noformat}
> /**
>* Returns a list of directories for the disk stores that were off-line at
>* the time the backup occurred.
>*/
> public String[] getOfflineDiskStores() {
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-834) Java Util Logging not showing up on server logs
[ https://issues.apache.org/jira/browse/GEODE-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn resolved GEODE-834. -- Resolution: Won't Do > Java Util Logging not showing up on server logs > --- > > Key: GEODE-834 > URL: https://issues.apache.org/jira/browse/GEODE-834 > Project: Geode > Issue Type: Bug > Components: logging >Affects Versions: 1.0.0-incubating, 1.1.0 >Reporter: William Markito Oliveira >Priority: Major > > When trying to use java.util.logging.Logger from a callback (CacheWriter, > Listeners..) it looks like the output is not being displayed on .log > I've checked gemfire-core-dependencies/META-INF/MANIFEST.mf and we are > including log4j-jul-2.5.jar which was supposed to the bridge and capture > those calls. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4703) DestroyGatewayReceiver may cause hang if executed during RollingUpgrade
[ https://issues.apache.org/jira/browse/GEODE-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Huynh resolved GEODE-4703. Resolution: Fixed > DestroyGatewayReceiver may cause hang if executed during RollingUpgrade > --- > > Key: GEODE-4703 > URL: https://issues.apache.org/jira/browse/GEODE-4703 > Project: Geode > Issue Type: Bug > Components: wan >Affects Versions: 1.5.0 >Reporter: Jason Huynh >Assignee: Jason Huynh >Priority: Major > Labels: pull-request-available > Time Spent: 50m > Remaining Estimate: 0h > > GEODE-2667 introduced the ability to destroy gateway receiver -> destroy > cache server. However if executed in a cluster with mixed servers (servers > prior to 1.5) the distribution of the message causes a DSFID deserialization > failure on the older versions, which causes the sender to wait for replies > infinitely. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-1175) Remove random integers from GemfireDataCommandsDUnitTest
[ https://issues.apache.org/jira/browse/GEODE-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn resolved GEODE-1175. --- Resolution: Won't Do > Remove random integers from GemfireDataCommandsDUnitTest > > > Key: GEODE-1175 > URL: https://issues.apache.org/jira/browse/GEODE-1175 > Project: Geode > Issue Type: Test > Components: gfsh, tests >Reporter: Kirk Lund >Priority: Major > > GemfireDataCommandsDUnitTest uses java.util.Random to generate data for use > in its tests. This should change to make the tests deterministic and > repeatable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4703) DestroyGatewayReceiver may cause hang if executed during RollingUpgrade
[ https://issues.apache.org/jira/browse/GEODE-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Huynh updated GEODE-4703: --- Affects Version/s: 1.5.0 > DestroyGatewayReceiver may cause hang if executed during RollingUpgrade > --- > > Key: GEODE-4703 > URL: https://issues.apache.org/jira/browse/GEODE-4703 > Project: Geode > Issue Type: Bug > Components: wan >Affects Versions: 1.5.0 >Reporter: Jason Huynh >Assignee: Jason Huynh >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 50m > Remaining Estimate: 0h > > GEODE-2667 introduced the ability to destroy gateway receiver -> destroy > cache server. However if executed in a cluster with mixed servers (servers > prior to 1.5) the distribution of the message causes a DSFID deserialization > failure on the older versions, which causes the sender to wait for replies > infinitely. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4703) DestroyGatewayReceiver may cause hang if executed during RollingUpgrade
[ https://issues.apache.org/jira/browse/GEODE-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Huynh updated GEODE-4703: --- Fix Version/s: 1.5.0 > DestroyGatewayReceiver may cause hang if executed during RollingUpgrade > --- > > Key: GEODE-4703 > URL: https://issues.apache.org/jira/browse/GEODE-4703 > Project: Geode > Issue Type: Bug > Components: wan >Affects Versions: 1.5.0 >Reporter: Jason Huynh >Assignee: Jason Huynh >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 50m > Remaining Estimate: 0h > > GEODE-2667 introduced the ability to destroy gateway receiver -> destroy > cache server. However if executed in a cluster with mixed servers (servers > prior to 1.5) the distribution of the message causes a DSFID deserialization > failure on the older versions, which causes the sender to wait for replies > infinitely. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-1075) Move Admin REST API code into the geode-web project
[ https://issues.apache.org/jira/browse/GEODE-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn resolved GEODE-1075. --- Resolution: Won't Do > Move Admin REST API code into the geode-web project > --- > > Key: GEODE-1075 > URL: https://issues.apache.org/jira/browse/GEODE-1075 > Project: Geode > Issue Type: Sub-task > Components: rest (admin) >Reporter: Dan Smith >Priority: Major > > The admin rest API is already getting warred up in its own geode-web > subproject, but the code is still in geode-core in the web directory. The > admin REST API code and it's dependencies should move out of the core. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-318) JarClassLoaderJUnitTest testDeclarableFunctionsWithParms and testClassOnClasspath fail on Windows
[
https://issues.apache.org/jira/browse/GEODE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barbara Pruijn resolved GEODE-318.
--
Resolution: Won't Do
> JarClassLoaderJUnitTest testDeclarableFunctionsWithParms and
> testClassOnClasspath fail on Windows
> -
>
> Key: GEODE-318
> URL: https://issues.apache.org/jira/browse/GEODE-318
> Project: Geode
> Issue Type: Bug
> Components: management, tests
>Affects Versions: 1.0.0-incubating
> Environment: Windows
>Reporter: Kirk Lund
>Priority: Major
> Labels: IntegrationTest, Windows
>
> Both tests fail due to "java.io.IOException: The process cannot access the
> file because another process has locked a portion of the file" and the
> failures are 100% consistent/reproducible on Windows for me.
> testClassOnClasspath:
> {noformat}
> java.io.IOException: The process cannot access the file because another
> process has locked a portion of the file
> at java.io.FileOutputStream.writeBytes(Native Method)
> at java.io.FileOutputStream.write(FileOutputStream.java:313)
> at
> org.apache.geode.internal.JarClassLoaderJUnitTest.writeJarBytesToFile(JarClassLoaderJUnitTest.java:782)
> at
> org.apache.geode.internal.JarClassLoaderJUnitTest.testClassOnClasspath(JarClassLoaderJUnitTest.java:125)
> 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.RunAfters.evaluate(RunAfters.java:27)
> 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.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:497)
> 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:497)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.internal.dispatch.ReflectionDispatch.dispatch
[jira] [Resolved] (GEODE-99) BackupInspectorJUnitTest.testIncrementalBackupScript fails on Windows
[
https://issues.apache.org/jira/browse/GEODE-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barbara Pruijn resolved GEODE-99.
-
Resolution: Won't Do
> BackupInspectorJUnitTest.testIncrementalBackupScript fails on Windows
> -
>
> Key: GEODE-99
> URL: https://issues.apache.org/jira/browse/GEODE-99
> Project: Geode
> Issue Type: Bug
> Components: core, management, tests
>Affects Versions: 1.0.0-incubating
> Environment: Windows
>Reporter: Kirk Lund
>Priority: Major
> Labels: IntegrationTest, Windows
>
> testIncrementalBackupScript:
> {code}
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> org.apache.geode.internal.cache.persistence.BackupInspectorJUnitTest.testIncrementalBackupScript(BackupInspectorJUnitTest.java:198)
> 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.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> 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.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:497)
> 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:497)
> 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.MessageHub$Handler.run(MessageHub.java:377)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
> at
> org.gradle.internal.
[jira] [Resolved] (GEODE-1000) LauncherLifecycleCommandsDUnitTest fails on Windows
[ https://issues.apache.org/jira/browse/GEODE-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn resolved GEODE-1000. --- Resolution: Won't Do > LauncherLifecycleCommandsDUnitTest fails on Windows > --- > > Key: GEODE-1000 > URL: https://issues.apache.org/jira/browse/GEODE-1000 > Project: Geode > Issue Type: Bug > Components: management > Environment: Windows >Reporter: Bruce Schuchardt >Priority: Major > Labels: DistributedTest, Windows > > A number of tests fail due to file separators being changed from a > forward-slash to a back-slash: > com.gemstone.gemfire.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest > > test001StartLocatorFailsFastOnMissingGemFirePropertiesFile FAILED > junit.framework.AssertionFailedError: > Warning: The GemFire properties file > C:\path\to\missing\gemfire.properties could not be found. > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at > com.gemstone.gemfire.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest.test001StartLocatorFailsFastOnMissingGemFirePropertiesFile(LauncherLifecycleCommandsDUnitTest.java:384) > com.gemstone.gemfire.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest > > test002StartLocatorFailsFastOnMissingGemFireSecurityPropertiesFile FAILED > junit.framework.AssertionFailedError: > Warning: The GemFire Security properties file > C:\path\to\missing\gemfire-security.properties could not be found. > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at > com.gemstone.gemfire.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest.test002StartLocatorFailsFastOnMissingGemFireSecurityPropertiesFile(LauncherLifecycleCommandsDUnitTest.java:409) > com.gemstone.gemfire.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest > > test003StartServerFailsFastOnMissingCacheXmlFile FAILED > junit.framework.AssertionFailedError: > Warning: The GemFire cache XML file C:\path\to\missing\cache.xml could > not be found. > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at > com.gemstone.gemfire.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest.test003StartServerFailsFastOnMissingCacheXmlFile(LauncherLifecycleCommandsDUnitTest.java:429) > com.gemstone.gemfire.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest > > test004StartServerFailsFastOnMissingGemFirePropertiesFile FAILED > junit.framework.AssertionFailedError: > Warning: The GemFire properties file > C:\path\to\missing\gemfire.properties could not be found. > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at > com.gemstone.gemfire.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest.test004StartServerFailsFastOnMissingGemFirePropertiesFile(LauncherLifecycleCommandsDUnitTest.java:448) > com.gemstone.gemfire.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest > > test005StartServerFailsFastOnMissingGemFireSecurityPropertiesFile FAILED > junit.framework.AssertionFailedError: > Warning: The GemFire Security properties file > C:\path\to\missing\gemfire-securities.properties could not be found. > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at > com.gemstone.gemfire.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest.test005StartServerFailsFastOnMissingGemFireSecurityPropertiesFile(LauncherLifecycleCommandsDUnitTest.java:468) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-955) Remove HeadlessGfsh
[ https://issues.apache.org/jira/browse/GEODE-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn resolved GEODE-955. -- Resolution: Won't Do > Remove HeadlessGfsh > --- > > Key: GEODE-955 > URL: https://issues.apache.org/jira/browse/GEODE-955 > Project: Geode > Issue Type: Test > Components: gfsh >Reporter: Jens Deppe >Priority: Major > > We currently have multiple versions of "testable" Gfsh implementations which > have evolved over time. We should at least investigate removing these in > favor of a single Gfsh implementation. > Features that these other implementations provide should probably be able to > now be implemented in Gfsh as we have move to jline 2.x which provides > additional features such as: > - Better separation of concerns. Specifically the Terminal definition is > separate from the ConsoleReader. We should be able to use a Pipe to drive > Gfsh interactively from code. > - State callbacks which would allow for explicit state change detection such > as command execution. This is important as Jline executes asynchronously. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-737) Unable to specify custom users for Pulse
[
https://issues.apache.org/jira/browse/GEODE-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barbara Pruijn resolved GEODE-737.
--
Resolution: Won't Do
> Unable to specify custom users for Pulse
>
>
> Key: GEODE-737
> URL: https://issues.apache.org/jira/browse/GEODE-737
> Project: Geode
> Issue Type: Bug
> Components: pulse
>Reporter: Jens Deppe
>Priority: Major
>
> Even though we don't have Pulse yet, I'm still adding this from Trac.
> When following these instructions
> http://gemfire.docs.pivotal.io/docs-gemfire/latest/tools_modules/pulse/quickstart.html
> I am unable to get them to work.
> The example which uses a properties file results in not being able to log in
> at all (incorrect credentials). The example which includes a specific set of
> users allows me to log in, but then I get a 403 on any subsequent pages. The
> config I am using looks like this:
> {noformat}
> http://www.springframework.org/schema/security";
>xmlns:beans="http://www.springframework.org/schema/beans";
>xmlns:context="http://www.springframework.org/schema/context";
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xsi:schemaLocation="http://www.springframework.org/schema/beans
>http://www.springframework.org/schema/beans/spring-beans-3.2.xsd
>http://www.springframework.org/schema/security
>http://www.springframework.org/schema/security/spring-security-3.1.xsd
>http://www.springframework.org/schema/context
>http://www.springframework.org/schema/context/spring-context-3.2.xsd";>
>
>
>
>
>
>
>
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-603) Cluster configuration should work when servers are running
[ https://issues.apache.org/jira/browse/GEODE-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn resolved GEODE-603. -- Resolution: Won't Do > Cluster configuration should work when servers are running > -- > > Key: GEODE-603 > URL: https://issues.apache.org/jira/browse/GEODE-603 > Project: Geode > Issue Type: Improvement > Components: configuration >Reporter: Swapnil Bawaskar >Priority: Major > > Currently, cluster configuration cannot be imported when Geode servers are > running. One has to shutdown all the servers to import the cluster config > followed by re-starting them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-1842) Execution of query from GFSH or Pulse may kill a Server with StackOverflowError
[
https://issues.apache.org/jira/browse/GEODE-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barbara Pruijn resolved GEODE-1842.
---
Resolution: Won't Do
> Execution of query from GFSH or Pulse may kill a Server with
> StackOverflowError
> ---
>
> Key: GEODE-1842
> URL: https://issues.apache.org/jira/browse/GEODE-1842
> Project: Geode
> Issue Type: Bug
> Components: gfsh, pulse
>Reporter: Kirk Lund
>Priority: Critical
> Labels: StackOverflowError, gfsh, json
>
> TypedJson is prone to StackOverflowErrors which results in SystemFailure
> shutdown of any Geode server that hits this problem. Below is the latest
> error stack reported against TypedJson:
> {noformat}
> java.lang.StackOverflowError
> at java.lang.Class.getEnclosingMethodInfo(Class.java:1072)
> at java.lang.Class.getEnclosingClass(Class.java:1272)
> at java.lang.Class.getSimpleBinaryName(Class.java:1443)
> at java.lang.Class.getSimpleName(Class.java:1309)
> at java.lang.Class.getCanonicalName(Class.java:1399)
> at
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.internalToExternal(TypedJson.java:626)
> at
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.writeType(TypedJson.java:610)
> at
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.writeKeyValue(TypedJson.java:345)
> at
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.visitSpecialObjects(TypedJson.java:517)
> at
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.writeKeyValue(TypedJson.java:353)
> at
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.visitChildrens(TypedJson.java:670)
> at
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.addVal(TypedJson.java:323)
> at
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.writeVal(TypedJson.java:314)
> at
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.writeKeyValue(TypedJson.java:357)
> at
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.visitChildrens(TypedJson.java:670)
> at
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.addVal(TypedJson.java:323)
> at
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.writeVal(TypedJson.java:314)
> at
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.writeKeyValue(TypedJson.java:357)
> at
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.visitSpecialObjects(TypedJson.java:517)
> at
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.writeKeyValue(TypedJson.java:353)
> at
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.visitChildrens(TypedJson.java:670)
> at
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.addVal(TypedJson.java:323)
> at
> com.gemstone.gemfire.management.internal.cli.json.TypedJson.writeVal(TypedJson.java:314)
> {noformat}
> QueryDataFunction uses TypedJson to serialize query results into JSON to
> return to GFSH or Pulse. Rather than maintain a broken custom JSON parser, we
> should replace TypedJson with Jackson.
> This example will go into infinite recursion until it produces a
> StackOverflowError:
> {noformat}
> public class Root {
> public Root getRoot() {
> return this;
> }
> public Child getChild() { // getter that returns unique instances
> return new Child();
> }
> }
> public class Child {
> public Child getChild() {
> return this;
> }
> }
> {noformat}
> This example will go into an infinite loop until it produces OutOfMemoryError:
> {noformat}
> public class Replicator {
> public Replicator getReplicator() { // getter that returns unique instances
> return new Replicator();
> }
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-604) Remove CacheServerLauncher
[ https://issues.apache.org/jira/browse/GEODE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn resolved GEODE-604. -- Resolution: Won't Do > Remove CacheServerLauncher > -- > > Key: GEODE-604 > URL: https://issues.apache.org/jira/browse/GEODE-604 > Project: Geode > Issue Type: Sub-task > Components: management >Reporter: Swapnil Bawaskar >Priority: Major > > CacheServerLauncher class was used by the old "cacheserver" cli to start a > server. The cli has since been replaced by gfsh and hence CacheServerLauncher > can be removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-1536) Poor documentation and misleading error messages with multi user security
[
https://issues.apache.org/jira/browse/GEODE-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barbara Pruijn resolved GEODE-1536.
---
Resolution: Won't Do
> Poor documentation and misleading error messages with multi user security
> -
>
> Key: GEODE-1536
> URL: https://issues.apache.org/jira/browse/GEODE-1536
> Project: Geode
> Issue Type: Bug
> Components: docs, security
>Reporter: Dan Smith
>Priority: Major
> Labels: bug-hunt
>
> I'm trying to connect a client using multi user security authentication.
> I couldn't find any description of how to use this feature in the manuals.
> The javadocs for ClientCacheFactory.setPoolMultiuserAuthentication basically
> provide no information. If you just set that, you get this misleading error
> message:
> {code}
> java.lang.UnsupportedOperationException: Use Pool APIs for doing operations
> when multiuser-secure-mode-enabled is set to true.
> {code}
> What you actually need to do is call cache.createAuthenticatedView. However,
> if you just do that, you get this error message
> {code}
> com.gemstone.gemfire.cache.client.ServerOperationException: remote server on
> 172.16.115.238(73827:loner):60898:2126f43c:
> com.gemstone.gemfire.security.AuthenticationRequiredException: No security-*
> properties are provided
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:671)
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:772)
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:603)
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:165)
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:110)
> at
> com.gemstone.gemfire.cache.client.internal.PoolImpl.execute(PoolImpl.java:700)
> at
> com.gemstone.gemfire.cache.client.internal.PutOp.execute(PutOp.java:102)
> at
> com.gemstone.gemfire.cache.client.internal.ServerRegionProxy.put(ServerRegionProxy.java:175)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.serverPut(LocalRegion.java:3061)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.cacheWriteBeforePut(LocalRegion.java:3188)
> at
> com.gemstone.gemfire.internal.cache.ProxyRegionMap.basicPut(ProxyRegionMap.java:230)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.virtualPut(LocalRegion.java:5845)
> at
> com.gemstone.gemfire.internal.cache.LocalRegionDataView.putEntry(LocalRegionDataView.java:132)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.basicPut(LocalRegion.java:5240)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.validatedPut(LocalRegion.java:1557)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.put(LocalRegion.java:1544)
> at
> com.gemstone.gemfire.internal.cache.AbstractRegion.put(AbstractRegion.java:288)
> at
> com.gemstone.gemfire.cache.client.internal.ProxyRegion.put(ProxyRegion.java:459)
> at TestClient.test(TestClient.java:29)
> 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.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.runner.JUnitCore.run(JUnitCore.java:137)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:119)
> at
> com.intellij.junit
[jira] [Resolved] (GEODE-1490) Convert all concrete *OperationContexts into interfaces
[ https://issues.apache.org/jira/browse/GEODE-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn resolved GEODE-1490. --- Resolution: Won't Do > Convert all concrete *OperationContexts into interfaces > --- > > Key: GEODE-1490 > URL: https://issues.apache.org/jira/browse/GEODE-1490 > Project: Geode > Issue Type: Improvement > Components: security >Reporter: Jens Deppe >Priority: Major > > Currently the hierarchy of OperationContexts (in > com.gemstone.gemfire.cache.operations) are a mix of abstract and concrete > classes as well as a mix of 'public' and 'internal' packaging. It would be > much cleaner if these were converted to interfaces and all of the concrete > implementations be made internal. > Currently where public packages extend internal packages the javadoc would > also be broken as the public packages would reference (internal) packages for > which no javadoc links will exist. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-1488) Consider making SampleJsonAuthorization dynamic
[ https://issues.apache.org/jira/browse/GEODE-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn resolved GEODE-1488. --- Resolution: Won't Do > Consider making SampleJsonAuthorization dynamic > --- > > Key: GEODE-1488 > URL: https://issues.apache.org/jira/browse/GEODE-1488 > Project: Geode > Issue Type: Improvement > Components: security >Reporter: Jens Deppe >Priority: Major > > This code is only a sample, but it currently requires a full restart whenever > the configuration file changes. It would be useful if it could detect a > change and re-read the config file so as to dynamically update it's > configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-1445) LogService should provide a static method to retrieve a secure logger
[
https://issues.apache.org/jira/browse/GEODE-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barbara Pruijn resolved GEODE-1445.
---
Resolution: Won't Do
> LogService should provide a static method to retrieve a secure logger
> -
>
> Key: GEODE-1445
> URL: https://issues.apache.org/jira/browse/GEODE-1445
> Project: Geode
> Issue Type: Improvement
> Components: logging
>Reporter: Jens Deppe
>Priority: Major
>
> Something like {{LogServe.getSecurityLogger()}} would be useful.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-4751) Add function execution to Protobuf driver
Bruce Schuchardt created GEODE-4751: --- Summary: Add function execution to Protobuf driver Key: GEODE-4751 URL: https://issues.apache.org/jira/browse/GEODE-4751 Project: Geode Issue Type: New Feature Components: client/server Reporter: Bruce Schuchardt The experimental protobuf driver needs to have function execution added to its API. executeFunctionOnServer(s) and executeFunctionOnGroup(s) The functionality has already been implemented in the server. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4685) Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal
[ https://issues.apache.org/jira/browse/GEODE-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379472#comment-16379472 ] ASF subversion and git services commented on GEODE-4685: Commit 4a0ef10d6f35a1e9c7fca208ded92b67d0026baf in geode's branch refs/heads/feature/GEODE-4685 from Udo [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4a0ef10 ] GEODE-4685: Moving of static DefaultQuery.setPdxReadSerialized to the TypeRegistry. > Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal > -- > > Key: GEODE-4685 > URL: https://issues.apache.org/jira/browse/GEODE-4685 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: nabarun >Assignee: Udo Kohlmeyer >Priority: Major > > Replace with the solution from GEODE-4679 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4750) Add finer grained security to OQL queries with protobuf
Dan Smith created GEODE-4750: Summary: Add finer grained security to OQL queries with protobuf Key: GEODE-4750 URL: https://issues.apache.org/jira/browse/GEODE-4750 Project: Geode Issue Type: Improvement Components: client/server Reporter: Dan Smith After GEODE-3126 and GEODE-4406 are implemented, we should update the OqlOperationHandler to allow queries if the user has access to the individual regions. Currently the changes for GEODE-3126 are validating that the user has DATA:READ access for all regions in order to do a query. The QueryCommand class has an example of how to validate the regions involved in the query. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4685) Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal
[ https://issues.apache.org/jira/browse/GEODE-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379467#comment-16379467 ] ASF subversion and git services commented on GEODE-4685: Commit 3207c4ef9911d72c507892e67c5adba72a047f06 in geode's branch refs/heads/feature/GEODE-4685 from Udo [ https://gitbox.apache.org/repos/asf?p=geode.git;h=3207c4e ] GEODE-4685: Spotless > Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal > -- > > Key: GEODE-4685 > URL: https://issues.apache.org/jira/browse/GEODE-4685 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: nabarun >Assignee: Udo Kohlmeyer >Priority: Major > > Replace with the solution from GEODE-4679 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4401) Add a CloseConnection protobuf message
[ https://issues.apache.org/jira/browse/GEODE-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-4401: -- Labels: pull-request-available (was: ) > Add a CloseConnection protobuf message > -- > > Key: GEODE-4401 > URL: https://issues.apache.org/jira/browse/GEODE-4401 > Project: Geode > Issue Type: Task > Components: client/server >Reporter: Bruce Schuchardt >Assignee: Michael Dodge >Priority: Major > Labels: pull-request-available > > The current API has no way for the client to inform a server of its intent to > close its connection. The server is left thinking the client crashed. It > would be nice to have a graceful shutdown message & have the server log > something if the client abnormally closes the connection without sending a > Close message. > See also GEODE-4300 where we added supression of log messages when client > connections are found to be closed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-4404) Update Gfsh command to pass BackupDestination object
[ https://issues.apache.org/jira/browse/GEODE-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Reich reassigned GEODE-4404: - Assignee: Nick Reich > Update Gfsh command to pass BackupDestination object > > > Key: GEODE-4404 > URL: https://issues.apache.org/jira/browse/GEODE-4404 > Project: Geode > Issue Type: Sub-task > Components: persistence >Reporter: Nick Reich >Assignee: Nick Reich >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Gfsh backup command passes File destination as the target location. To > support any destination other than the file system for the target location to > save the backup, we need to be able to pass alternate information in the > backup messages. Having the backup command provide an implementation of > BackupDestination (in this case, FileSystemBackupDestination) will allow for > the future creation of gfsh commands that utilize a different destination. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4404) Update Gfsh command to pass BackupDestination object
[ https://issues.apache.org/jira/browse/GEODE-4404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-4404: -- Labels: pull-request-available (was: ) > Update Gfsh command to pass BackupDestination object > > > Key: GEODE-4404 > URL: https://issues.apache.org/jira/browse/GEODE-4404 > Project: Geode > Issue Type: Sub-task > Components: persistence >Reporter: Nick Reich >Priority: Major > Labels: pull-request-available > > Gfsh backup command passes File destination as the target location. To > support any destination other than the file system for the target location to > save the backup, we need to be able to pass alternate information in the > backup messages. Having the backup command provide an implementation of > BackupDestination (in this case, FileSystemBackupDestination) will allow for > the future creation of gfsh commands that utilize a different destination. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-3875) gfsh command to create jndi binding
[
https://issues.apache.org/jira/browse/GEODE-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barbara Pruijn resolved GEODE-3875.
---
Resolution: Fixed
> gfsh command to create jndi binding
> ---
>
> Key: GEODE-3875
> URL: https://issues.apache.org/jira/browse/GEODE-3875
> Project: Geode
> Issue Type: Sub-task
> Components: docs, gfsh
>Reporter: Swapnil Bawaskar
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> In cache.xml user can specify jndi binding like so:
> {code:java}
>
> jdbc-driver-class="org.postgresql.Driver" user-name="gpadmin"
> password="changeme"
> connection-url="jdbc:postgresql://localhost:5432/gemfire_db">
>
>
> {code}
> A user should be able to create a datasource using the gfsh command {{create
> jndi-binding }}
> Then a datasource will be created with the supplied options and the binding
> will be created without the user having to restart the existing server(s)
> Please look at Geode's schema for a list of attributes that can be set:
> [https://github.com/apache/geode-site/blob/master/website/content/schema/cache/cache-1.0.xsd#L1331]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-3875) gfsh command to create jndi binding
[
https://issues.apache.org/jira/browse/GEODE-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barbara Pruijn updated GEODE-3875:
--
Fix Version/s: 1.5.0
> gfsh command to create jndi binding
> ---
>
> Key: GEODE-3875
> URL: https://issues.apache.org/jira/browse/GEODE-3875
> Project: Geode
> Issue Type: Sub-task
> Components: docs, gfsh
>Reporter: Swapnil Bawaskar
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> In cache.xml user can specify jndi binding like so:
> {code:java}
>
> jdbc-driver-class="org.postgresql.Driver" user-name="gpadmin"
> password="changeme"
> connection-url="jdbc:postgresql://localhost:5432/gemfire_db">
>
>
> {code}
> A user should be able to create a datasource using the gfsh command {{create
> jndi-binding }}
> Then a datasource will be created with the supplied options and the binding
> will be created without the user having to restart the existing server(s)
> Please look at Geode's schema for a list of attributes that can be set:
> [https://github.com/apache/geode-site/blob/master/website/content/schema/cache/cache-1.0.xsd#L1331]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-2020) Add more tests to replace the legacy tests
[ https://issues.apache.org/jira/browse/GEODE-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn resolved GEODE-2020. --- Resolution: Invalid This is an ongoing effort and is being done continuously and has been incorporated into engineering practices. > Add more tests to replace the legacy tests > -- > > Key: GEODE-2020 > URL: https://issues.apache.org/jira/browse/GEODE-2020 > Project: Geode > Issue Type: Task > Components: management >Reporter: Jinmei Liao >Priority: Major > > Whenever a legacy test failed, we should write an integration test or Dunit > test to reproduce it and then fix it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4749) change AnalyzeSerializables to not store method bytecodes in sanctioned/actual files
Bruce Schuchardt created GEODE-4749: --- Summary: change AnalyzeSerializables to not store method bytecodes in sanctioned/actual files Key: GEODE-4749 URL: https://issues.apache.org/jira/browse/GEODE-4749 Project: Geode Issue Type: Bug Components: serialization Reporter: Bruce Schuchardt AnalyzeSerializables stores a string representation of the bytecodes of the toData/fromData methods in sanctionedDataSerializables.txt and actualDataSerializables.dat but it only pays attention to the number of bytecodes when detecting changes to these methods. Many of the bytecode strings are now out of date. Though the methods have the same number of bytecodes the actual code generated by the compiler is different now than it used to be. We need to change the ClassAndMethodDetails class to only care about the number of bytecodes and not hold onto the bytes themselves. Then regenerate all of the sanctionedDataSerializables.txt files in the various modules (run the test and copy the actualDataSerializables.dat file over the sanctionedDataSerializables.txt file). This will help our git pull request diffs be compact and understandable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4685) Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal
[ https://issues.apache.org/jira/browse/GEODE-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379405#comment-16379405 ] ASF subversion and git services commented on GEODE-4685: Commit 7581023d19c51ea1227eb684902325e84f73d947 in geode's branch refs/heads/feature/GEODE-4685 from Udo [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7581023 ] GEODE-4685: Address pre-checkin test failures > Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal > -- > > Key: GEODE-4685 > URL: https://issues.apache.org/jira/browse/GEODE-4685 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: nabarun >Assignee: Udo Kohlmeyer >Priority: Major > > Replace with the solution from GEODE-4679 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4734) Cleanup some tests to use as examples on Geode wiki
[ https://issues.apache.org/jira/browse/GEODE-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-4734: -- Labels: pull-request-available (was: ) > Cleanup some tests to use as examples on Geode wiki > --- > > Key: GEODE-4734 > URL: https://issues.apache.org/jira/browse/GEODE-4734 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > > I'm looking for some tests to use as recommended examples on the Geode wiki. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-1961) Deprecate the ability of individual members to opt out of using cluster configuration
[ https://issues.apache.org/jira/browse/GEODE-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn resolved GEODE-1961. --- Resolution: Not A Problem > Deprecate the ability of individual members to opt out of using cluster > configuration > - > > Key: GEODE-1961 > URL: https://issues.apache.org/jira/browse/GEODE-1961 > Project: Geode > Issue Type: Improvement > Components: configuration >Reporter: Diane Hardman >Priority: Minor > > Once cluster config is selected when starting the locator, this should > automatically apply to all members. There is no reason an individual member > should be opting out. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-1960) Provide protection against malicious developer jars deployed as functions
[ https://issues.apache.org/jira/browse/GEODE-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn resolved GEODE-1960. --- Resolution: Won't Do There are permissions around deploying jars. Referring to last commend in ticket. > Provide protection against malicious developer jars deployed as functions > - > > Key: GEODE-1960 > URL: https://issues.apache.org/jira/browse/GEODE-1960 > Project: Geode > Issue Type: Improvement > Components: configuration, functions, gfsh, management, security >Reporter: Diane Hardman >Priority: Minor > Labels: ClassLoader, DeployCommand, deploy, gfsh, security > > Provide protection for functions that might contain malicious calls like > System.exit(). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-1816) CacheServerLauncher uses static threadlocals to launch server
[
https://issues.apache.org/jira/browse/GEODE-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barbara Pruijn resolved GEODE-1816.
---
Resolution: Won't Do
Is this still an issue?
> CacheServerLauncher uses static threadlocals to launch server
> -
>
> Key: GEODE-1816
> URL: https://issues.apache.org/jira/browse/GEODE-1816
> Project: Geode
> Issue Type: Bug
> Components: management
>Reporter: Dan Smith
>Priority: Major
>
> The CacheServerLauncher class has 3 static threadlocals
> {code}
> public static ThreadLocal serverPort = new ThreadLocal();
> public static ThreadLocal serverBindAddress = new
> ThreadLocal();
> public static ThreadLocal disableDefaultServer = new
> ThreadLocal();
> {code}
> These get set when a server is launched. Then down in CacheCreation.create,
> it reads these thread locals and uses them to add a cache server.
> Unfortunately this causes lots of pain writing unit tests, because tests can
> end up setting these thread locals and they are never cleared. Statics and
> thread locals should pretty much never be used. Especially in this case it
> seems like there are several easy ways to create a cache server after the
> cache is created, or pass properties in while creating the cache.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-1901) authz5_5.dtd and authz6_0.dtd files need to be cleaned up
[
https://issues.apache.org/jira/browse/GEODE-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barbara Pruijn resolved GEODE-1901.
---
Resolution: Won't Do
> authz5_5.dtd and authz6_0.dtd files need to be cleaned up
> -
>
> Key: GEODE-1901
> URL: https://issues.apache.org/jira/browse/GEODE-1901
> Project: Geode
> Issue Type: Bug
> Components: security, tests
>Reporter: Kirk Lund
>Priority: Minor
>
> These files refer to a dtd that's online at gemstone.com:
> http://www.gemstone.com/dtd/authz5_5.dtd
> The authz6_0.dtd refers to http://www.gemstone.com/dtd/authz5_5.dtd and I
> can't find authz6_0.dtd online anywhere (if that's what it's supposed to be).
> This paragraph seems to be messed up:
> {noformat}
> The contents of a declarative XML file correspond to APIs found in the
> org.apache.geode.security.AccessControl
> package. The sample implementation may be used to specify access control
> policies.
> {noformat}
> These files also mention GemStone Systems, Inc. and GemFire (does this need
> to change?).
> These files are currently checked into test resources, but they might
> actually be used by security templates/examples.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-3875) gfsh command to create jndi binding
[
https://issues.apache.org/jira/browse/GEODE-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379168#comment-16379168
]
ASF subversion and git services commented on GEODE-3875:
Commit 40fb4bd8fe7b644350a3b4a3e444d1c7f8a78e96 in geode's branch
refs/heads/develop from [~sai.boorlaga...@gmail.com]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=40fb4bd ]
GEODE-3875: gfsh command to create jndi binding (#1507)
Reworked on a response message text based on review.
> gfsh command to create jndi binding
> ---
>
> Key: GEODE-3875
> URL: https://issues.apache.org/jira/browse/GEODE-3875
> Project: Geode
> Issue Type: Sub-task
> Components: docs, gfsh
>Reporter: Swapnil Bawaskar
>Priority: Major
> Labels: pull-request-available
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> In cache.xml user can specify jndi binding like so:
> {code:java}
>
> jdbc-driver-class="org.postgresql.Driver" user-name="gpadmin"
> password="changeme"
> connection-url="jdbc:postgresql://localhost:5432/gemfire_db">
>
>
> {code}
> A user should be able to create a datasource using the gfsh command {{create
> jndi-binding }}
> Then a datasource will be created with the supplied options and the binding
> will be created without the user having to restart the existing server(s)
> Please look at Geode's schema for a list of attributes that can be set:
> [https://github.com/apache/geode-site/blob/master/website/content/schema/cache/cache-1.0.xsd#L1331]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-4736) New protocol should consistently record statistics
[ https://issues.apache.org/jira/browse/GEODE-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-4736. -- Resolution: Fixed > New protocol should consistently record statistics > -- > > Key: GEODE-4736 > URL: https://issues.apache.org/jira/browse/GEODE-4736 > Project: Geode > Issue Type: Task > Components: client/server >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Some of the ProtobufOperationHandler classes update statistics by calling > startOperation and endOperation on the statistics class. We should update the > statistics consistently at a higher level. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4736) New protocol should consistently record statistics
[ https://issues.apache.org/jira/browse/GEODE-4736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379165#comment-16379165 ] ASF subversion and git services commented on GEODE-4736: Commit be8140dadb386adfb5b18503ef0878d7f7376f56 in geode's branch refs/heads/develop from Dan Smith [ https://gitbox.apache.org/repos/asf?p=geode.git;h=be8140d ] GEODE-4736: Updating statistics in ProtobufOpsProcessor Updating statistics in one place, rather than in each operation. > New protocol should consistently record statistics > -- > > Key: GEODE-4736 > URL: https://issues.apache.org/jira/browse/GEODE-4736 > Project: Geode > Issue Type: Task > Components: client/server >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Some of the ProtobufOperationHandler classes update statistics by calling > startOperation and endOperation on the statistics class. We should update the > statistics consistently at a higher level. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4693) JDBCLoader on region with a pdx-class-name causes exception during deserialization when a get is done
[ https://issues.apache.org/jira/browse/GEODE-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-4693: -- Labels: pull-request-available (was: ) > JDBCLoader on region with a pdx-class-name causes exception during > deserialization when a get is done > - > > Key: GEODE-4693 > URL: https://issues.apache.org/jira/browse/GEODE-4693 > Project: Geode > Issue Type: Bug > Components: extensions, regions >Affects Versions: 1.4.0 >Reporter: Fred Krone >Assignee: Anilkumar Gingade >Priority: Major > Labels: pull-request-available > > When Region.get() is performed with JDBCLoader and pdx-class-name, the > JDBCLoader always creates a PdxInstance whose fields are all of type object. > If the domain class has the fields as some other type, for example string or > int, then deserialization will fail. > Workaround at this time is: > # Don't set the pdx-class-name on the jdbc region mapping. This will cause > deserialization to never happen since the data will remain a PdxInstance. > # Have all your domain class fields serialized as pdx object fields. This > can be hard to do with the ReflectionBasedAutoSerializer so the > recommendation is to use PdxSerializable or your own PdxSerializer. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4685) Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal
[ https://issues.apache.org/jira/browse/GEODE-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379106#comment-16379106 ] ASF subversion and git services commented on GEODE-4685: Commit c89367c866adb30fbd99a464cae8971ca22c02e6 in geode's branch refs/heads/feature/GEODE-4685 from Udo [ https://gitbox.apache.org/repos/asf?p=geode.git;h=c89367c ] GEODE-4685: Renamed the readPdxSerialized override to something more user-friendly > Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal > -- > > Key: GEODE-4685 > URL: https://issues.apache.org/jira/browse/GEODE-4685 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: nabarun >Assignee: Udo Kohlmeyer >Priority: Major > > Replace with the solution from GEODE-4679 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-1784) Remove SecurityTestUtils from test code
[ https://issues.apache.org/jira/browse/GEODE-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn resolved GEODE-1784. --- Resolution: Fixed > Remove SecurityTestUtils from test code > --- > > Key: GEODE-1784 > URL: https://issues.apache.org/jira/browse/GEODE-1784 > Project: Geode > Issue Type: Test > Components: security, tests >Reporter: Kirk Lund >Priority: Minor > > SecurityTestUtils greatly obscures tests. The class should 1st be deprecated > to warn against writing new tests that use it, and then existing tests that > use it should be refactored to not use this class so it can be deleted. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4721) Being invoked within JTA Region.values() (and all iteration related operations) does return empty collection
[
https://issues.apache.org/jira/browse/GEODE-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379082#comment-16379082
]
Eric Shu commented on GEODE-4721:
-
Does your failed case use client proxy region to perform JTA? If so, there is a
workaround by performing a region.get() on a existing/non existing key before
accessing the values.
> Being invoked within JTA Region.values() (and all iteration related
> operations) does return empty collection
>
>
> Key: GEODE-4721
> URL: https://issues.apache.org/jira/browse/GEODE-4721
> Project: Geode
> Issue Type: Bug
> Components: regions, transactions
>Reporter: Vadim Lotarev
>Assignee: Eric Shu
>Priority: Critical
>
> {{Region.values()}} returns empty collection being invoked within JTA. Other
> operations returns data, for example this workaround works (though less
> efficient): {{region.getAll(region.keySet()).values()}}, also
> {{Region.size()}} returns correct value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (GEODE-1783) ConfigurationProperties javadocs contains invalid javadoc syntax and typos
[ https://issues.apache.org/jira/browse/GEODE-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379079#comment-16379079 ] Barbara Pruijn edited comment on GEODE-1783 at 2/27/18 6:20 PM: Low priority. was (Author: bpruijn): old ticket. if not fixed by now, it's not going to happen. > ConfigurationProperties javadocs contains invalid javadoc syntax and typos > -- > > Key: GEODE-1783 > URL: https://issues.apache.org/jira/browse/GEODE-1783 > Project: Geode > Issue Type: Bug > Components: configuration, general >Reporter: Kirk Lund >Priority: Minor > Labels: javadocs > > The javadocs for com.gemstone.gemfire.distributed.ConfigurationProperties > contains invalid javadoc syntax and typos. > The use of and/or (this varies from constant to constant) is > inconsistent with > http://www.oracle.com/technetwork/articles/java/index-137868.html. > There are spelling typos, such as "seperated". > The fix should include: > 1) strict compliance with > http://www.oracle.com/technetwork/articles/java/index-137868.html > 2) consistent formatting for javadocs on all property constants > 3) no misspelled words > 4) javadocs should render properly in Eclipse, IntelliJ and in HTML generated > by javadoc -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-1783) ConfigurationProperties javadocs contains invalid javadoc syntax and typos
[ https://issues.apache.org/jira/browse/GEODE-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn resolved GEODE-1783. --- Resolution: Won't Do old ticket. if not fixed by now, it's not going to happen. > ConfigurationProperties javadocs contains invalid javadoc syntax and typos > -- > > Key: GEODE-1783 > URL: https://issues.apache.org/jira/browse/GEODE-1783 > Project: Geode > Issue Type: Bug > Components: configuration, general >Reporter: Kirk Lund >Priority: Minor > Labels: javadocs > > The javadocs for com.gemstone.gemfire.distributed.ConfigurationProperties > contains invalid javadoc syntax and typos. > The use of and/or (this varies from constant to constant) is > inconsistent with > http://www.oracle.com/technetwork/articles/java/index-137868.html. > There are spelling typos, such as "seperated". > The fix should include: > 1) strict compliance with > http://www.oracle.com/technetwork/articles/java/index-137868.html > 2) consistent formatting for javadocs on all property constants > 3) no misspelled words > 4) javadocs should render properly in Eclipse, IntelliJ and in HTML generated > by javadoc -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-1681) gfsh start server should support more gemfire properties
[ https://issues.apache.org/jira/browse/GEODE-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn resolved GEODE-1681. --- Resolution: Fixed > gfsh start server should support more gemfire properties > > > Key: GEODE-1681 > URL: https://issues.apache.org/jira/browse/GEODE-1681 > Project: Geode > Issue Type: Improvement > Components: gfsh >Reporter: Darrel Schneider >Priority: Major > > The gfsh start server command needs more options for the gemfire properties. > It has support for a bunch of them but for others customers need to add > "--J=-Dgemfire.". If you make a typo in the system property name you will not > get any indication of it. > A user recently was setting the following: > "--J=-Dgemfire.start-dev-rest-api=true > --J=-Dgemfire.http-service-bind-address=10.205.84.13 > --J=-Dgemfire.http-service-bind-port=8081 --J=-Dgemfire.jmx-manager=true > --J=-Dgemfire.jmx-manager-start=true" > They should have been able to do this instead: "--start-dev-rest-api=true > --http-service-bind-address=10.205.84.13 --http-service-bind-port=8081 > --jmx-manager=true --jmx-manager-start=true" and would have been told that > "--http-service-bind-port" was an unknown option (it should have been > "-http-service-port"). > It seems like it would be best for gfsh start server to support all the > gemfire properties that are in the ConfigurationProperties class. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-1564) GFSH help incorrectly reports that "start vsd" is available
[ https://issues.apache.org/jira/browse/GEODE-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn resolved GEODE-1564. --- Resolution: Fixed > GFSH help incorrectly reports that "start vsd" is available > --- > > Key: GEODE-1564 > URL: https://issues.apache.org/jira/browse/GEODE-1564 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Kirk Lund >Assignee: Srikanth Manvi >Priority: Major > > GFSH help incorrectly reports that "start vsd" is available. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-1536) Poor documentation and misleading error messages with multi user security
[
https://issues.apache.org/jira/browse/GEODE-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379062#comment-16379062
]
Barbara Pruijn commented on GEODE-1536:
---
Is this still relevant? If not, please close ticket.
> Poor documentation and misleading error messages with multi user security
> -
>
> Key: GEODE-1536
> URL: https://issues.apache.org/jira/browse/GEODE-1536
> Project: Geode
> Issue Type: Bug
> Components: docs, security
>Reporter: Dan Smith
>Priority: Major
> Labels: bug-hunt
>
> I'm trying to connect a client using multi user security authentication.
> I couldn't find any description of how to use this feature in the manuals.
> The javadocs for ClientCacheFactory.setPoolMultiuserAuthentication basically
> provide no information. If you just set that, you get this misleading error
> message:
> {code}
> java.lang.UnsupportedOperationException: Use Pool APIs for doing operations
> when multiuser-secure-mode-enabled is set to true.
> {code}
> What you actually need to do is call cache.createAuthenticatedView. However,
> if you just do that, you get this error message
> {code}
> com.gemstone.gemfire.cache.client.ServerOperationException: remote server on
> 172.16.115.238(73827:loner):60898:2126f43c:
> com.gemstone.gemfire.security.AuthenticationRequiredException: No security-*
> properties are provided
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:671)
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:772)
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:603)
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:165)
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:110)
> at
> com.gemstone.gemfire.cache.client.internal.PoolImpl.execute(PoolImpl.java:700)
> at
> com.gemstone.gemfire.cache.client.internal.PutOp.execute(PutOp.java:102)
> at
> com.gemstone.gemfire.cache.client.internal.ServerRegionProxy.put(ServerRegionProxy.java:175)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.serverPut(LocalRegion.java:3061)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.cacheWriteBeforePut(LocalRegion.java:3188)
> at
> com.gemstone.gemfire.internal.cache.ProxyRegionMap.basicPut(ProxyRegionMap.java:230)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.virtualPut(LocalRegion.java:5845)
> at
> com.gemstone.gemfire.internal.cache.LocalRegionDataView.putEntry(LocalRegionDataView.java:132)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.basicPut(LocalRegion.java:5240)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.validatedPut(LocalRegion.java:1557)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.put(LocalRegion.java:1544)
> at
> com.gemstone.gemfire.internal.cache.AbstractRegion.put(AbstractRegion.java:288)
> at
> com.gemstone.gemfire.cache.client.internal.ProxyRegion.put(ProxyRegion.java:459)
> at TestClient.test(TestClient.java:29)
> 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.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.runner.JUnitCore.run(JUnitCore.java:137)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner
[jira] [Resolved] (GEODE-1535) NullPointerException from SampleJsonAuthorization with valid credentials
[
https://issues.apache.org/jira/browse/GEODE-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barbara Pruijn resolved GEODE-1535.
---
Resolution: Won't Fix
> NullPointerException from SampleJsonAuthorization with valid credentials
>
>
> Key: GEODE-1535
> URL: https://issues.apache.org/jira/browse/GEODE-1535
> Project: Geode
> Issue Type: Bug
> Components: security
>Reporter: Dan Smith
>Priority: Major
> Labels: bug-hunt
>
> I'm trying to configure a client to connect with authorization using the
> SampleJsonAuthorization class. I got the below NPE when trying to connect.
> {code}
> com.gemstone.gemfire.cache.client.ServerOperationException: remote server on
> 172.16.115.238(72978:loner):60610:2e0de43c: : While performing a remote put
> at
> com.gemstone.gemfire.cache.client.internal.PutOp$PutOpImpl.processAck(PutOp.java:445)
> at
> com.gemstone.gemfire.cache.client.internal.PutOp$PutOpImpl.processResponse(PutOp.java:355)
> at
> com.gemstone.gemfire.cache.client.internal.PutOp$PutOpImpl.attemptReadResponse(PutOp.java:540)
> at
> com.gemstone.gemfire.cache.client.internal.AbstractOp.attempt(AbstractOp.java:378)
> at
> com.gemstone.gemfire.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:274)
> at
> com.gemstone.gemfire.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:328)
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:937)
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:155)
> at
> com.gemstone.gemfire.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:110)
> at
> com.gemstone.gemfire.cache.client.internal.PoolImpl.execute(PoolImpl.java:700)
> at
> com.gemstone.gemfire.cache.client.internal.PutOp.execute(PutOp.java:102)
> at
> com.gemstone.gemfire.cache.client.internal.ServerRegionProxy.put(ServerRegionProxy.java:175)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.serverPut(LocalRegion.java:3061)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.cacheWriteBeforePut(LocalRegion.java:3188)
> at
> com.gemstone.gemfire.internal.cache.ProxyRegionMap.basicPut(ProxyRegionMap.java:230)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.virtualPut(LocalRegion.java:5845)
> at
> com.gemstone.gemfire.internal.cache.LocalRegionDataView.putEntry(LocalRegionDataView.java:132)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.basicPut(LocalRegion.java:5240)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.validatedPut(LocalRegion.java:1557)
> at
> com.gemstone.gemfire.internal.cache.LocalRegion.put(LocalRegion.java:1544)
> at
> com.gemstone.gemfire.internal.cache.AbstractRegion.put(AbstractRegion.java:288)
> at TestClient.test(TestClient.java:20)
> 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.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.runner.JUnitCore.run(JUnitCore.java:137)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:119)
> at
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:42)
> at
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:234)
> at
> com.inte
[jira] [Resolved] (GEODE-1533) After gfsh times out a session, user can no longer reconnect for a period of time
[
https://issues.apache.org/jira/browse/GEODE-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barbara Pruijn resolved GEODE-1533.
---
Resolution: Won't Do
Security Manager framework has replaced the old security framework. Not
focusing on this bug in the old framework.
> After gfsh times out a session, user can no longer reconnect for a period of
> time
> -
>
> Key: GEODE-1533
> URL: https://issues.apache.org/jira/browse/GEODE-1533
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Dan Smith
>Priority: Major
> Labels: bug-hunt
>
> I hit this will following the instructions on
> https://cwiki.apache.org/confluence/display/GEODE/Quickstart+guide+to+securing+JMX%2C+GFSH+and+Pulse
> I launched a locator with a security-client-authorization callback. Then I
> connected gfsh using the super-user account specified in the json file.
> I then walked away for a while. It looks like my session timed out, I see
> this in the console
> {noformat}
> gfsh>stop server --name=server1
> An error occurred while attempting to stop a Cache Server: There is no
> session with id [1358bd30-b44d-45df-acb1-7c30e4b956a4]
> {noformat}
> That's fine, maybe my session timed out. The issue is that even if I
> disconnect and reconnect again, or even exit out of gfsh and try to
> reconnect, I get an authentication error.
> After some more time has elapsed, then I can connect again. Below is my log.
> {noformat}
> gfsh>stop server --name=server1
> An error occurred while attempting to stop a Cache Server: There is no
> session with id [1358bd30-b44d-45df-acb1-7c30e4b956a4]
> gfsh>disconnect
> Disconnecting from: 172.16.115.238[1099]
> Disconnected from : 172.16.115.238[1099]
> gfsh>connect --user=root --password=123
> Connecting to Locator at [host=localhost, port=10334] ..
> Connecting to Manager at [host=172.16.115.238, port=1099] ..
> Could not connect to : [host=172.16.115.238, port=1099]. Authentication
> error. Please check your username/password.
> gfsh>
> Exiting...
> scripts> gfsh
> Picked up JAVA_TOOL_OPTIONS:
> _ __
>/ _/ __/ __/ // /
> / / __/ /___ /_ / _ /
> / /__/ / / _/ / // /
> /__/_/ /__/_//_/1.0.0-incubating.M3-SNAPSHOT
> Monitor and Manage Apache Geode (incubating)
> gfsh>connect --user=root --password=123
> Connecting to Locator at [host=localhost, port=10334] ..
> Connecting to Manager at [host=172.16.115.238, port=1099] ..
> Could not connect to : [host=172.16.115.238, port=1099]. Authentication
> error. Please check your username/password.
> ***Nothing has changed except some time has gone by in this time ***
> gfsh>connect --user=root --password=123
> Connecting to Locator at [host=localhost, port=10334] ..
> Connecting to Manager at [host=172.16.115.238, port=1099] ..
> Successfully connected to: [host=172.16.115.238, port=1099]
> gfsh>
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4685) Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal
[ https://issues.apache.org/jira/browse/GEODE-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379045#comment-16379045 ] ASF subversion and git services commented on GEODE-4685: Commit dab6f1e7b21d27f768338cf8d1a2ee01ef7d40f3 in geode's branch refs/heads/feature/GEODE-4685 from Udo [ https://gitbox.apache.org/repos/asf?p=geode.git;h=dab6f1e ] GEODE-4685: Revert changes to static LuceneExceptionObserver access in LuceneEventListener.java > Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal > -- > > Key: GEODE-4685 > URL: https://issues.apache.org/jira/browse/GEODE-4685 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: nabarun >Assignee: Udo Kohlmeyer >Priority: Major > > Replace with the solution from GEODE-4679 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4747) CI Failure :org.apache.geode.cache.lucene.internal.repository.IndexRepositoryImplJUnitTest - testUpdateAndRemoveBinaryKeys
[
https://issues.apache.org/jira/browse/GEODE-4747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nabarun updated GEODE-4747:
---
Affects Version/s: 1.4.0
> CI Failure
> :org.apache.geode.cache.lucene.internal.repository.IndexRepositoryImplJUnitTest
> - testUpdateAndRemoveBinaryKeys
> ---
>
> Key: GEODE-4747
> URL: https://issues.apache.org/jira/browse/GEODE-4747
> Project: Geode
> Issue Type: Bug
> Components: lucene
>Affects Versions: 1.4.0
>Reporter: nabarun
>Priority: Major
>
> {noformat}
> org.apache.geode.InternalGemFireError: java.io.InvalidClassException: filter
> status: REJECTED
> at
> org.apache.geode.cache.lucene.internal.repository.serializer.SerializerUtil.keyFromBytes(SerializerUtil.java:164)
> at
> org.apache.geode.cache.lucene.internal.repository.serializer.SerializerUtil.getKey(SerializerUtil.java:132)
> at
> org.apache.geode.cache.lucene.internal.repository.IndexRepositoryImpl.query(IndexRepositoryImpl.java:150)
> at
> org.apache.geode.cache.lucene.internal.repository.IndexRepositoryImplJUnitTest.checkQuery(IndexRepositoryImplJUnitTest.java:259)
> at
> org.apache.geode.cache.lucene.internal.repository.IndexRepositoryImplJUnitTest.updateAndRemove(IndexRepositoryImplJUnitTest.java:239)
> at
> org.apache.geode.cache.lucene.internal.repository.IndexRepositoryImplJUnitTest.testUpdateAndRemoveBinaryKeys(IndexRepositoryImplJUnitTest.java:132)
> 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.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.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
> org.gradle.
[jira] [Commented] (GEODE-1445) LogService should provide a static method to retrieve a secure logger
[
https://issues.apache.org/jira/browse/GEODE-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379032#comment-16379032
]
Barbara Pruijn commented on GEODE-1445:
---
Is this still relevant? If not, can we close this ticket?
> LogService should provide a static method to retrieve a secure logger
> -
>
> Key: GEODE-1445
> URL: https://issues.apache.org/jira/browse/GEODE-1445
> Project: Geode
> Issue Type: Improvement
> Components: logging
>Reporter: Jens Deppe
>Priority: Major
>
> Something like {{LogServe.getSecurityLogger()}} would be useful.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-3639) Request: build flag to skip download of previous Geode versions
[ https://issues.apache.org/jira/browse/GEODE-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund resolved GEODE-3639. -- Resolution: Won't Fix > Request: build flag to skip download of previous Geode versions > --- > > Key: GEODE-3639 > URL: https://issues.apache.org/jira/browse/GEODE-3639 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Kirk Lund >Priority: Major > > I need a build flag to skip download of previous Geode versions. Downloading > previous versions of Geode (which occurs on every clean build) takes too > long. I only want to build and run test (UnitTest). The previous versions of > Geode are only used in IntegrationTest. So I want a flag to skip that > download, or better yet, move the downloading of previous versions to the > integrationTest or distributedTest target where it belongs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (GEODE-3639) Request: build flag to skip download of previous Geode versions
[ https://issues.apache.org/jira/browse/GEODE-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund closed GEODE-3639. > Request: build flag to skip download of previous Geode versions > --- > > Key: GEODE-3639 > URL: https://issues.apache.org/jira/browse/GEODE-3639 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Kirk Lund >Priority: Major > > I need a build flag to skip download of previous Geode versions. Downloading > previous versions of Geode (which occurs on every clean build) takes too > long. I only want to build and run test (UnitTest). The previous versions of > Geode are only used in IntegrationTest. So I want a flag to skip that > download, or better yet, move the downloading of previous versions to the > integrationTest or distributedTest target where it belongs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-1398) gfsh "alter runtime --member" affects other members in the cluster
[
https://issues.apache.org/jira/browse/GEODE-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barbara Pruijn resolved GEODE-1398.
---
Resolution: Fixed
This seems to have been resolved at some point.
> gfsh "alter runtime --member" affects other members in the cluster
> --
>
> Key: GEODE-1398
> URL: https://issues.apache.org/jira/browse/GEODE-1398
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Swapnil Bawaskar
>Priority: Major
>
> When altering the runtime to change the log level for a particular member,
> the
> gfsh command {{alter runtime --log-level=fine --member=server1}} works as
> expected, until you start a new member, at which point the new member picks
> up the altered log-level.
> To reproduce:
> 1. Launch gfsh
> 2. Start a locator
> {{gfsh>start locator --name=loc1}}
> 3. start a server
> {{gfsh>start server --name=server1 --server-port=40404}}
> 4. Alter runtime to change log level to fine:
> {{gfsh>alter runtime --log-level=fine --member=server1}}
> 5. Verify that log level of the locator has not changed.
> 6. Start a second server
> {{gfsh>start server --name=server2 --server-port=40406}}
> 7. see that the new server logs at {{fine}} level.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-1398) gfsh "alter runtime --member" affects other members in the cluster
[
https://issues.apache.org/jira/browse/GEODE-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379013#comment-16379013
]
Barbara Pruijn commented on GEODE-1398:
---
2018 log levels settings:
LogWriter Log4J2
---
SEVERE = FATAL
ERROR = ERROR
WARNING = WARN
INFO, CONFIG = INFO
FINE = DEBUG
FINER, FINEST = TRACE
> gfsh "alter runtime --member" affects other members in the cluster
> --
>
> Key: GEODE-1398
> URL: https://issues.apache.org/jira/browse/GEODE-1398
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Swapnil Bawaskar
>Priority: Major
>
> When altering the runtime to change the log level for a particular member,
> the
> gfsh command {{alter runtime --log-level=fine --member=server1}} works as
> expected, until you start a new member, at which point the new member picks
> up the altered log-level.
> To reproduce:
> 1. Launch gfsh
> 2. Start a locator
> {{gfsh>start locator --name=loc1}}
> 3. start a server
> {{gfsh>start server --name=server1 --server-port=40404}}
> 4. Alter runtime to change log level to fine:
> {{gfsh>alter runtime --log-level=fine --member=server1}}
> 5. Verify that log level of the locator has not changed.
> 6. Start a second server
> {{gfsh>start server --name=server2 --server-port=40406}}
> 7. see that the new server logs at {{fine}} level.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4675) CI failure (suspect strings): DistributedSystemDisconnectedException: This connection to a distributed system has been disconnected reported as fatal log message during
[
https://issues.apache.org/jira/browse/GEODE-4675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379003#comment-16379003
]
ASF subversion and git services commented on GEODE-4675:
Commit 889da898b5adf1864dd61a05ab01549ae6edcaf5 in geode's branch
refs/heads/feature/GEODE-4685 from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=889da89 ]
GEODE-4675: remove checkConnected calls while notifying listeners (#1495)
A call of checkConnected ended up being made from notifyListenersMemberRemoved
which could cause it to throw DistributedSystemDisconnectedException if
the distributed system was being shutdown.
So now the distribution manager is made without this check being done.
Also change to log level from fatal to warn and improved the log message.
> CI failure (suspect strings): DistributedSystemDisconnectedException: This
> connection to a distributed system has been disconnected reported as fatal
> log message during shutdown
> -
>
> Key: GEODE-4675
> URL: https://issues.apache.org/jira/browse/GEODE-4675
> Project: Geode
> Issue Type: Bug
> Components: regions
>Affects Versions: 1.5.0
>Reporter: Shelley Lynn Hughes-Godfrey
>Assignee: Darrel Schneider
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This failure occurred during CI on geode:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/140
> {noformat}
> org.apache.geode.internal.cache.wan.concurrent.ConcurrentParallelGatewaySenderOffHeapDUnitTest
> > 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 9339
> [fatal 2018/02/13 21:12:48.099 UTC tid=891]
> Unexpected exception:
> org.apache.geode.distributed.DistributedSystemDisconnectedException: This
> connection to a distributed system has been disconnected.
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.checkConnected(InternalDistributedSystem.java:911)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem.getDistributionManager(InternalDistributedSystem.java:1499)
> at
> org.apache.geode.internal.cache.AbstractRegion.getDistributionManager(AbstractRegion.java:1757)
> at
> org.apache.geode.distributed.internal.DistributionAdvisor.getDistributionManager(DistributionAdvisor.java:380)
> at
> org.apache.geode.distributed.internal.DistributionAdvisor.notifyListenersMemberRemoved(DistributionAdvisor.java:1225)
> at
> org.apache.geode.distributed.internal.DistributionAdvisor.basicRemoveId(DistributionAdvisor.java:897)
> at
> org.apache.geode.distributed.internal.DistributionAdvisor.doRemoveId(DistributionAdvisor.java:964)
> at
> org.apache.geode.distributed.internal.DistributionAdvisor.removeId(DistributionAdvisor.java:926)
> at
> org.apache.geode.internal.cache.CacheDistributionAdvisor.removeId(CacheDistributionAdvisor.java:1183)
> at
> org.apache.geode.internal.cache.partitioned.RegionAdvisor.removeId(RegionAdvisor.java:391)
> at
> org.apache.geode.distributed.internal.DistributionAdvisor$1.memberDeparted(DistributionAdvisor.java:232)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$MemberDepartedEvent.handleEvent(ClusterDistributionManager.java:4198)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$MemberEvent.handleEvent(ClusterDistributionManager.java:4127)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$MemberEvent.handleEvent(ClusterDistributionManager.java:4116)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.handleMemberEvent(ClusterDistributionManager.java:2218)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.access$900(ClusterDistributionManager.java:109)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$MemberEventInvoker.run(ClusterDistributionManager.java:2250)
> at java.lang.Thread.run(Thread.java:748)
> ---
> {noformat}
> According to the logs, this looks like it occurs during shutdown ...
> {noformat}
> [vm1] [info 2018/02/13 21:12:48.075 UTC
> tid=30] Stopping membership service
[jira] [Commented] (GEODE-4738) EventSeqNum and versionVector in a region are accessed when they are not yet initialized
[
https://issues.apache.org/jira/browse/GEODE-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379005#comment-16379005
]
ASF subversion and git services commented on GEODE-4738:
Commit 3dad0a3a0a467bd5cf388af31ccfc69ad0c28443 in geode's branch
refs/heads/feature/GEODE-4685 from [~eshu]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3dad0a3 ]
GEODE-4738: move eventSeqNum and versionVector setting in constructors. (#1504)
* GEODE-4738: move eventSeqNum and versionVector setting in constructors.
> EventSeqNum and versionVector in a region are accessed when they are not yet
> initialized
>
>
> Key: GEODE-4738
> URL: https://issues.apache.org/jira/browse/GEODE-4738
> Project: Geode
> Issue Type: Bug
> Components: regions
>Affects Versions: 1.4.0
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> It is possible that eventSeqNum and versionVector are accessed when they are
> not initialized yet. This could cause transaction to fail on the node just
> start up.
> {noformat}
> Got unexpected exception org.apache.geode.cache.CommitIncompleteException:
> Incomplete commit of transaction TXId:
> rs-FullRegression-2018-02-10-05-01-42-client-1(bridgegemfire6_rs-FullRegression-2018-02-10-05-01-42-client-1_19376:19376):1030:4865.
> Caused by the following exceptions: From member:
> rs-FullRegression-2018-02-10-05-01-42-client-1(bridgegemfire4_rs-FullRegression-2018-02-10-05-01-42-client-1_15810:15810):1026
> java.lang.NullPointerException
> at
> org.apache.geode.internal.concurrent.Atomics.setIfGreater(Atomics.java:56)
> at
> org.apache.geode.internal.cache.BucketRegion.handleWANEvent(BucketRegion.java:576)
> at
> org.apache.geode.internal.cache.AbstractRegionMap.txHandleWANEvent(AbstractRegionMap.java:2938)
> at
> org.apache.geode.internal.cache.AbstractRegionMap.txApplyPut(AbstractRegionMap.java:2647)
> at
> org.apache.geode.internal.cache.LocalRegion.txApplyPut(LocalRegion.java:5068)
> at
> org.apache.geode.internal.cache.TXCommitMessage$RegionCommit.txApplyEntryOp(TXCommitMessage.java:1287)
> at
> org.apache.geode.internal.cache.TXCommitMessage$RegionCommit$FarSideEntryOp.process(TXCommitMessage.java:1597)
> at
> org.apache.geode.internal.cache.TXCommitMessage.basicProcessOps(TXCommitMessage.java:711)
> at
> org.apache.geode.internal.cache.TXCommitMessage.basicProcess(TXCommitMessage.java:638)
> at
> org.apache.geode.internal.cache.TXCommitMessage$CommitProcessMessage.basicProcess(TXCommitMessage.java:1784)
> at
> org.apache.geode.internal.cache.TXCommitMessage$CommitProcessForTXIdMessage.process(TXCommitMessage.java:1747)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
> at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:448)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1117)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:108)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$4$1.run(ClusterDistributionManager.java:788)
> at java.lang.Thread.run(Thread.java:748).
> at
> org.apache.geode.internal.cache.TXCommitMessage$CommitExceptionCollectingException.handlePotentialCommitFailure(TXCommitMessage.java:2203)
> at
> org.apache.geode.internal.cache.TXCommitMessage$CommitReplyProcessor.waitForCommitCompletion(TXCommitMessage.java:2104)
> at
> org.apache.geode.internal.cache.TXCommitMessage.send(TXCommitMessage.java:418)
> at org.apache.geode.internal.cache.TXState.commit(TXState.java:473)
> at
> org.apache.geode.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:228)
> at
> org.apache.geode.internal.cache.TXManagerImpl.commit(TXManagerImpl.java:405)
> at
> org.apache.geode.internal.cache.TXRemoteCommitMessage.operateOnTx(TXRemoteCommitMessage.java:98)
> at org.apache.geode.internal.cache.TXMessage.process(TXMessage.java:94)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
> at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.ja
[jira] [Commented] (GEODE-4737) User Guide: Describe addition of JSON specs to gfsh commands
[ https://issues.apache.org/jira/browse/GEODE-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379008#comment-16379008 ] ASF subversion and git services commented on GEODE-4737: Commit 3eaa095b0e0ba97e83ebce78b1e0163f0e4dba63 in geode's branch refs/heads/feature/GEODE-4685 from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=3eaa095 ] GEODE-4737 Document JSON spec for gfsh command options (#1509) * GEODE-4737 Document JSON spec for gfsh command options * GEODE-4737 Revise gfsh command JSON spec per review > User Guide: Describe addition of JSON specs to gfsh commands > > > Key: GEODE-4737 > URL: https://issues.apache.org/jira/browse/GEODE-4737 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Some new gfsh commands can take a JSON spec. Examples include `alter region > --entry-idle-time-custom-expiry` and `create region --cache-listener`. > Add a general description of the syntax to the gfsh section of the manual so > individual command-reference entries can point to a centralized explanation, > rather than repeating the syntax details each time. > One developer has requested that we state that the JSON parser recognizes > double quotes as well as single quotes. Some JSON parsers accept only single > quotes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4737) User Guide: Describe addition of JSON specs to gfsh commands
[ https://issues.apache.org/jira/browse/GEODE-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379010#comment-16379010 ] ASF subversion and git services commented on GEODE-4737: Commit cd5edfd12c0229ab2f8ee5d516e34e6df5a1c9dd in geode's branch refs/heads/feature/GEODE-4685 from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=cd5edfd ] GEODE-3915 Document use of JSON spec for gfsh create and alter region (#1502) - cache-listener, cache-loader, and cache-writer command-line options can add a JSON specification to the fq class name that are used to populate the init method's parameter for those classes that implement Declarable - see GEODE-4737 for the task to document what the JSON should look like > User Guide: Describe addition of JSON specs to gfsh commands > > > Key: GEODE-4737 > URL: https://issues.apache.org/jira/browse/GEODE-4737 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Some new gfsh commands can take a JSON spec. Examples include `alter region > --entry-idle-time-custom-expiry` and `create region --cache-listener`. > Add a general description of the syntax to the gfsh section of the manual so > individual command-reference entries can point to a centralized explanation, > rather than repeating the syntax details each time. > One developer has requested that we state that the JSON parser recognizes > double quotes as well as single quotes. Some JSON parsers accept only single > quotes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4737) User Guide: Describe addition of JSON specs to gfsh commands
[ https://issues.apache.org/jira/browse/GEODE-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379007#comment-16379007 ] ASF subversion and git services commented on GEODE-4737: Commit 3eaa095b0e0ba97e83ebce78b1e0163f0e4dba63 in geode's branch refs/heads/feature/GEODE-4685 from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=3eaa095 ] GEODE-4737 Document JSON spec for gfsh command options (#1509) * GEODE-4737 Document JSON spec for gfsh command options * GEODE-4737 Revise gfsh command JSON spec per review > User Guide: Describe addition of JSON specs to gfsh commands > > > Key: GEODE-4737 > URL: https://issues.apache.org/jira/browse/GEODE-4737 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Some new gfsh commands can take a JSON spec. Examples include `alter region > --entry-idle-time-custom-expiry` and `create region --cache-listener`. > Add a general description of the syntax to the gfsh section of the manual so > individual command-reference entries can point to a centralized explanation, > rather than repeating the syntax details each time. > One developer has requested that we state that the JSON parser recognizes > double quotes as well as single quotes. Some JSON parsers accept only single > quotes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4738) EventSeqNum and versionVector in a region are accessed when they are not yet initialized
[
https://issues.apache.org/jira/browse/GEODE-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379004#comment-16379004
]
ASF subversion and git services commented on GEODE-4738:
Commit 3dad0a3a0a467bd5cf388af31ccfc69ad0c28443 in geode's branch
refs/heads/feature/GEODE-4685 from [~eshu]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3dad0a3 ]
GEODE-4738: move eventSeqNum and versionVector setting in constructors. (#1504)
* GEODE-4738: move eventSeqNum and versionVector setting in constructors.
> EventSeqNum and versionVector in a region are accessed when they are not yet
> initialized
>
>
> Key: GEODE-4738
> URL: https://issues.apache.org/jira/browse/GEODE-4738
> Project: Geode
> Issue Type: Bug
> Components: regions
>Affects Versions: 1.4.0
>Reporter: Eric Shu
>Assignee: Eric Shu
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> It is possible that eventSeqNum and versionVector are accessed when they are
> not initialized yet. This could cause transaction to fail on the node just
> start up.
> {noformat}
> Got unexpected exception org.apache.geode.cache.CommitIncompleteException:
> Incomplete commit of transaction TXId:
> rs-FullRegression-2018-02-10-05-01-42-client-1(bridgegemfire6_rs-FullRegression-2018-02-10-05-01-42-client-1_19376:19376):1030:4865.
> Caused by the following exceptions: From member:
> rs-FullRegression-2018-02-10-05-01-42-client-1(bridgegemfire4_rs-FullRegression-2018-02-10-05-01-42-client-1_15810:15810):1026
> java.lang.NullPointerException
> at
> org.apache.geode.internal.concurrent.Atomics.setIfGreater(Atomics.java:56)
> at
> org.apache.geode.internal.cache.BucketRegion.handleWANEvent(BucketRegion.java:576)
> at
> org.apache.geode.internal.cache.AbstractRegionMap.txHandleWANEvent(AbstractRegionMap.java:2938)
> at
> org.apache.geode.internal.cache.AbstractRegionMap.txApplyPut(AbstractRegionMap.java:2647)
> at
> org.apache.geode.internal.cache.LocalRegion.txApplyPut(LocalRegion.java:5068)
> at
> org.apache.geode.internal.cache.TXCommitMessage$RegionCommit.txApplyEntryOp(TXCommitMessage.java:1287)
> at
> org.apache.geode.internal.cache.TXCommitMessage$RegionCommit$FarSideEntryOp.process(TXCommitMessage.java:1597)
> at
> org.apache.geode.internal.cache.TXCommitMessage.basicProcessOps(TXCommitMessage.java:711)
> at
> org.apache.geode.internal.cache.TXCommitMessage.basicProcess(TXCommitMessage.java:638)
> at
> org.apache.geode.internal.cache.TXCommitMessage$CommitProcessMessage.basicProcess(TXCommitMessage.java:1784)
> at
> org.apache.geode.internal.cache.TXCommitMessage$CommitProcessForTXIdMessage.process(TXCommitMessage.java:1747)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
> at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:448)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1117)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:108)
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$4$1.run(ClusterDistributionManager.java:788)
> at java.lang.Thread.run(Thread.java:748).
> at
> org.apache.geode.internal.cache.TXCommitMessage$CommitExceptionCollectingException.handlePotentialCommitFailure(TXCommitMessage.java:2203)
> at
> org.apache.geode.internal.cache.TXCommitMessage$CommitReplyProcessor.waitForCommitCompletion(TXCommitMessage.java:2104)
> at
> org.apache.geode.internal.cache.TXCommitMessage.send(TXCommitMessage.java:418)
> at org.apache.geode.internal.cache.TXState.commit(TXState.java:473)
> at
> org.apache.geode.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:228)
> at
> org.apache.geode.internal.cache.TXManagerImpl.commit(TXManagerImpl.java:405)
> at
> org.apache.geode.internal.cache.TXRemoteCommitMessage.operateOnTx(TXRemoteCommitMessage.java:98)
> at org.apache.geode.internal.cache.TXMessage.process(TXMessage.java:94)
> at
> org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:382)
> at
> org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.ja
[jira] [Commented] (GEODE-2673) PartitionedRegionMultipleDUnitTest.testPartitionedRegionDestroyAndContainsAPI fails intermittently with ForcedDisconnectException
[
https://issues.apache.org/jira/browse/GEODE-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379002#comment-16379002
]
ASF subversion and git services commented on GEODE-2673:
Commit 101fd19ba74a1945265b1dee56327313c3a5c14f in geode's branch
refs/heads/feature/GEODE-4685 from [~apa...@the9muses.net]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=101fd19 ]
GEODE-2673: overhaul PartitionedRegion dunit tests (#1486)
* Delete PartitionedRegionDUnitTestCase
* Overhaul every dunit test that extended PartitionedRegionDUnitTestCase
* Fix flakiness in several dunit tests
* Document and update test methods that were named after old TRAC bugs
* Extract regression test methods to new dedicated test classes
* Extract unrelated test methods to new dedicated test classes
* Extract inner classes that are used by multiple test classes
* Change PRIdMap prIdToPR in PartitionedRegion to be private and change tests
to use an accessor to reference it
* Change localBucket2RegionMap in PartitionedRegionDataStore to be private and
change tests to use an accessor to reference it
* Move "Set getSomeKeys(Random rnd)" from PartitionedRegion product code to
PartitionedRegionGetSomeKeys in test code
* Make IgnoredException AutoCloseable so you can use it within try-resource
blocks
* Add "IgnoredException addIgnoredException(final Class exceptionClass)" to
IgnoredException
> PartitionedRegionMultipleDUnitTest.testPartitionedRegionDestroyAndContainsAPI
> fails intermittently with ForcedDisconnectException
> -
>
> Key: GEODE-2673
> URL: https://issues.apache.org/jira/browse/GEODE-2673
> Project: Geode
> Issue Type: Bug
> Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
> Labels: Flaky, pull-request-available
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Test passes when run by itself:
> {noformat}
> ./gradlew -DdistributedTest.single=PartitionedRegionMultipleDUnitTest
> geode-core:distributedTest
> {noformat}
> But fails intermittently in precheckin:
> {noformat}
> org.apache.geode.internal.cache.PartitionedRegionMultipleDUnitTest >
> testPartitionedRegionDestroyAndContainsAPI FAILED
> java.lang.AssertionError: exception during 0
> at org.apache.geode.test.dunit.Assert.fail(Assert.java:60)
> at
> org.apache.geode.internal.cache.PartitionedRegionMultipleDUnitTest.testPartitionedRegionDestroyAndContainsAPI(PartitionedRegionMultipleDUnitTest.java:231)
> Caused by:
> java.lang.AssertionError: Validation failed for key =
> 0testPartitionedRegionDestroyAndContainsAPI3Value got = null
> 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 1807
> [fatal 2017/03/13 23:48:06.633 UTC
> tid=0xc5] Membership service failure: this member is no longer in the view
> but is initiating connections
> org.apache.geode.ForcedDisconnectException: this member is no longer in
> the view but is initiating connections
> at
> org.apache.geode.distributed.internal.membership.gms.mgr.GMSMembershipManager.forceDisconnect(GMSMembershipManager.java:2517)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:998)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processRemoveRequest(GMSJoinLeave.java:635)
> at
> org.apache.geode.distributed.internal.membership.gms.membership.GMSJoinLeave.processMessage(GMSJoinLeave.java:1702)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1286)
> at org.jgroups.JChannel.invokeCallback(JChannel.java:816)
> at org.jgroups.JChannel.up(JChannel.java:741)
> at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1030)
> at org.jgroups.protocols.FRAG2.up(FRAG2.java:165)
> at org.jgroups.protocols.FlowControl.up(FlowControl.java:390)
> at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1070)
> at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:785)
> at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.StatRecorder.up(StatRecorder.java:74)
> at
> org.apache.geode.distributed.internal.membership.gms.messenger.AddressManager.up(AddressManager.java:72)
> at org.jgroups.protocols.T
[jira] [Commented] (GEODE-3915) supply arguments over gfsh while initializing Declarable
[ https://issues.apache.org/jira/browse/GEODE-3915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379009#comment-16379009 ] ASF subversion and git services commented on GEODE-3915: Commit cd5edfd12c0229ab2f8ee5d516e34e6df5a1c9dd in geode's branch refs/heads/feature/GEODE-4685 from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=cd5edfd ] GEODE-3915 Document use of JSON spec for gfsh create and alter region (#1502) - cache-listener, cache-loader, and cache-writer command-line options can add a JSON specification to the fq class name that are used to populate the init method's parameter for those classes that implement Declarable - see GEODE-4737 for the task to document what the JSON should look like > supply arguments over gfsh while initializing Declarable > > > Key: GEODE-3915 > URL: https://issues.apache.org/jira/browse/GEODE-3915 > Project: Geode > Issue Type: Sub-task > Components: docs, gfsh >Reporter: Swapnil Bawaskar >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > User implementations of the Declarable interface may want to pass in > arguments while the class is being initialized. We should provide ability to > pass these arguments from gfsh. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-2667) Need API to destroy gateway receiver
[
https://issues.apache.org/jira/browse/GEODE-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379011#comment-16379011
]
ASF subversion and git services commented on GEODE-2667:
Commit c00ce5390b293b8a9e2fa5a42f5d1fd36d7f430d in geode's branch
refs/heads/feature/GEODE-4685 from [~huynhja]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c00ce53 ]
GEODE-2667: Reword javaDoc for destroy gateway receiver (#1501)
> Need API to destroy gateway receiver
> -
>
> Key: GEODE-2667
> URL: https://issues.apache.org/jira/browse/GEODE-2667
> Project: Geode
> Issue Type: Bug
> Components: docs, wan
>Reporter: Swapnil Bawaskar
>Assignee: Jason Huynh
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> A {{GatewayReceiver}} can be created from {{GatewayReceiverFactory}},
> however, there is no API for destroying the {{GatewayReceiver}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4541) Remove singleton calls from regions product code in org.apache.geode.internal.cache
[ https://issues.apache.org/jira/browse/GEODE-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16378999#comment-16378999 ] ASF subversion and git services commented on GEODE-4541: Commit d752dceaee450ce4d49dcd06766b3dd665211e16 in geode's branch refs/heads/feature/GEODE-4685 from [~dschneider] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d752dce ] GEODE-4541: remove singleton calls (#1463) * removed getAnyInstance call from PartitionedRegionHelper * removed getInstance call from CacheServerLauncher * removed getAnyInstance call from EventStateHelper * DistributedPutAllOperation no longer calls GemFireCacheImpl.getInstance * EntryEventImpl no longer calls getInstance. This fix requires that when an EntryEventImpl is deserialized that setRegion will be called on it before the values are accessed. Also encapsulated the "region" field and got rid of getLocalRegion in favor of getRegion. > Remove singleton calls from regions product code in > org.apache.geode.internal.cache > --- > > Key: GEODE-4541 > URL: https://issues.apache.org/jira/browse/GEODE-4541 > Project: Geode > Issue Type: Sub-task > Components: regions >Reporter: Kirk Lund >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 10m > Remaining Estimate: 0h > > These regions product classes in org.apache.geode.internal.cache invoke > singleton getters. > GemFireCacheImpl.getInstance(): > * CacheServerLauncher > * EntryEventImpl > * GemFireCacheImpl > * DistributedPutAllOperation > InternalDistributedSystem.getAnyInstance(): > * EventStateHelper > * GemFireCacheImpl > * PartitionAttributesImpl > * PartitionedRegionHelper -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4638) review protobuf server error responses and logging for region-not-found
[ https://issues.apache.org/jira/browse/GEODE-4638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379001#comment-16379001 ] ASF subversion and git services commented on GEODE-4638: Commit de2cb20632fb8200a10238bfff206bb70bb97433 in geode's branch refs/heads/feature/GEODE-4685 from [~PivotalSarge] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=de2cb20 ] GEODE-4638: Standardize hanlding of region-not-found errors. (#1492) > review protobuf server error responses and logging for region-not-found > --- > > Key: GEODE-4638 > URL: https://issues.apache.org/jira/browse/GEODE-4638 > Project: Geode > Issue Type: Task > Components: client/server >Reporter: Bruce Schuchardt >Assignee: Michael Dodge >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Some operation handlers log region-not-found problems at error level and some > at warning level. Some return a SERVER_ERROR error code and some return an > INVALID_REQUEST error code. These should probably all behave in the same way. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4737) User Guide: Describe addition of JSON specs to gfsh commands
[ https://issues.apache.org/jira/browse/GEODE-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379006#comment-16379006 ] ASF subversion and git services commented on GEODE-4737: Commit 3eaa095b0e0ba97e83ebce78b1e0163f0e4dba63 in geode's branch refs/heads/feature/GEODE-4685 from Karen Miller [ https://gitbox.apache.org/repos/asf?p=geode.git;h=3eaa095 ] GEODE-4737 Document JSON spec for gfsh command options (#1509) * GEODE-4737 Document JSON spec for gfsh command options * GEODE-4737 Revise gfsh command JSON spec per review > User Guide: Describe addition of JSON specs to gfsh commands > > > Key: GEODE-4737 > URL: https://issues.apache.org/jira/browse/GEODE-4737 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Dave Barnes >Assignee: Karen Smoler Miller >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Some new gfsh commands can take a JSON spec. Examples include `alter region > --entry-idle-time-custom-expiry` and `create region --cache-listener`. > Add a general description of the syntax to the gfsh section of the manual so > individual command-reference entries can point to a centralized explanation, > rather than repeating the syntax details each time. > One developer has requested that we state that the JSON parser recognizes > double quotes as well as single quotes. Some JSON parsers accept only single > quotes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4685) Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal
[ https://issues.apache.org/jira/browse/GEODE-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379012#comment-16379012 ] ASF subversion and git services commented on GEODE-4685: Commit 46b65b86f873173b03bacb228fc88cf70c7d14aa in geode's branch refs/heads/feature/GEODE-4685 from Udo [ https://gitbox.apache.org/repos/asf?p=geode.git;h=46b65b8 ] GEODE-4685: Moving of static DefaultQuery.setPdxReadSerialized to the TypeRegistry. > Replace setPdxReadSerialized in org.apache.geode.cache.lucene.internal > -- > > Key: GEODE-4685 > URL: https://issues.apache.org/jira/browse/GEODE-4685 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: nabarun >Assignee: Udo Kohlmeyer >Priority: Major > > Replace with the solution from GEODE-4679 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4704) GatewaySender batch conflation can incorrectly conflate events causing out of order processing
[
https://issues.apache.org/jira/browse/GEODE-4704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16379000#comment-16379000
]
ASF subversion and git services commented on GEODE-4704:
Commit 147e6bc6b9009aa8e878141ef30e55145732943d in geode's branch
refs/heads/feature/GEODE-4685 from [~barry.oglesby]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=147e6bc ]
GEODE-4704: Modified ConflationKey to use shadowKey when comparing events
> GatewaySender batch conflation can incorrectly conflate events causing out of
> order processing
> --
>
> Key: GEODE-4704
> URL: https://issues.apache.org/jira/browse/GEODE-4704
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: Barry Oglesby
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In the current implementation of \{{AbstractGatewaySenderEventProcessor
> conflate}} can incorrectly conflate two create events on the same key.
> The else clause of the conflate method (meaning the event is not conflatable)
> assumes there isn't already a event with the same region, key and operation
> in the map. It just does a put:
> {noformat}
> ConflationKey key = new ConflationKey(gsEvent.getRegion().getFullPath(),
> gsEvent.getKeyToConflate(), gsEvent.getOperation());
> conflatedEventsMap.put(key, gsEvent);
> {noformat}
> In certain cases, there could already be a create event on the same region,
> key and operation in the batch, so the previous one gets replaced by the
> later once which causes the events to be processed out of order.
> These 4 events:
> {noformat}
> SenderEventImpl[id=EventIDid=57bytes;threadID=0x10018|112;sequenceID=100;bucketId=24];operation=CREATE;region=/dataStoreRegion;key=Object_13964;shadowKey=27709]
> SenderEventImpl[id=EventIDid=57bytes;threadID=0x10018|112;sequenceID=101;bucketId=24];operation=CREATE;region=/dataStoreRegion;key=Object_14024;shadowKey=27822]
> SenderEventImpl[id=EventIDid=57bytes;threadID=0x10018|112;sequenceID=102;bucketId=24];operation=DESTROY;region=/dataStoreRegion;key=Object_13964;shadowKey=27935]
> SenderEventImpl[id=EventIDid=57bytes;threadID=0x10018|112;sequenceID=104;bucketId=24];operation=CREATE;region=/dataStoreRegion;key=Object_14024;shadowKey=28161]
> {noformat}
> Become these 3 events:
> {noformat}
> SenderEventImpl[id=EventIDid=57bytes;threadID=0x10018|112;sequenceID=100;bucketId=24];operation=CREATE;region=/dataStoreRegion;key=Object_13964;shadowKey=27709]
> SenderEventImpl[id=EventIDid=57bytes;threadID=0x10018|112;sequenceID=104;bucketId=24];operation=CREATE;region=/dataStoreRegion;key=Object_14024;shadowKey=28161]
> SenderEventImpl[id=EventIDid=57bytes;threadID=0x10018|112;sequenceID=102;bucketId=24];operation=DESTROY;region=/dataStoreRegion;key=Object_13964;shadowKey=27935]
> {noformat}
> Notice the shadowKeys and sequenceIds are out of order after the conflation.
> The fix will be to include the shadow key in hashCode and equals in the case
> where the event is not conflatable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
