Re: Unable to run apache geode 1.14.4 instance

[Deepak Dixit]

There isn't any error in the log.
For reference attaching the log file.

-
Deepak

On Wed, Mar 30, 2022 at 9:51 PM Anthony Baker  wrote:

> Are there any errors in the locator log?  Did the locator log indicate
> that the locator started successfully?
>
> Anthony
>
>
> > On Mar 30, 2022, at 7:14 AM, Deepak Dixit 
> wrote:
> >
> > ⚠ External Email
> >
> > Hello Dev Team,
> >
> > I am facing following issue while starting up Apache Geode 1.14.4
> instance
> >
> > gfsh>start locator --name=test2 --log-level=ALL --bind-address=127.0.0.1
> >
> > Starting a Geode Locator in
> > /Users/deepakdixit/Downloads/apache-geode-1.14.4/test2...
> >
> > 
> >
> > Locator in /Users/deepakdixit/Downloads/apache-geode-1.14.4/test2 on
> > 127.0.0.1[10334] as test2 is currently online.
> >
> > Process ID: 57112
> >
> > Uptime: 12 seconds
> >
> > Geode Version: 1.14.4
> >
> > Java Version: 1.8.0_322
> >
> > Log File:
> /Users/deepakdixit/Downloads/apache-geode-1.14.4/test2/test2.log
> >
> > JVM Arguments: -Dgemfire.enable-cluster-configuration=true
> > -Dgemfire.load-cluster-configuration-from-dir=false
> -Dgemfire.log-level=ALL
> > -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
> > -Dsun.rmi.dgc.server.gcInterval=9223372036854775806
> >
> > Class-Path:
> >
> /Users/deepakdixit/Downloads/apache-geode-1.14.4/lib/geode-core-1.14.4.jar:/Users/deepakdixit/Downloads/apache-geode-1.14.4/lib/geode-dependencies.jar
> >
> >
> > Unable to auto-connect (Security Manager may be enabled). Please use
> > "connect --locator=localhost[10334]" to connect Gfsh to the locator.
> >
> >
> > Failed to connect; unknown cause: Failed to retrieve RMIServer stub:
> > javax.naming.CommunicationException [Root exception is
> > java.rmi.ConnectIOException: error during JRMP connection establishment;
> > nested exception is:
> >
> > java.io.EOFException]
> >
> >
> > Environment:
> > MacOS Monterey V12.3
> > Java Version openjdk version "1.8.0_322"
> >
> > Can someone help to find out the root cause for this?
> >
> >
> >
> > --
> > From:
> >
> > Deepak D Dixit
> > deepakdixit2...@gmail.com
> > +919028507537
> >
> > 
> >
> > ⚠ External Email: This email originated from outside of the
> organization. Do not click links or open attachments unless you recognize
> the sender.
>
>

-- 
From:

Deepak D Dixit
deepakdixit2...@gmail.com
+919028507537

Unable to run apache geode 1.14.4 instance

[Deepak Dixit]

Hello Dev Team,

I am facing following issue while starting up Apache Geode 1.14.4 instance

gfsh>start locator --name=test2 --log-level=ALL --bind-address=127.0.0.1

Starting a Geode Locator in
/Users/deepakdixit/Downloads/apache-geode-1.14.4/test2...



Locator in /Users/deepakdixit/Downloads/apache-geode-1.14.4/test2 on
127.0.0.1[10334] as test2 is currently online.

Process ID: 57112

Uptime: 12 seconds

Geode Version: 1.14.4

Java Version: 1.8.0_322

Log File: /Users/deepakdixit/Downloads/apache-geode-1.14.4/test2/test2.log

JVM Arguments: -Dgemfire.enable-cluster-configuration=true
-Dgemfire.load-cluster-configuration-from-dir=false -Dgemfire.log-level=ALL
-Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true
-Dsun.rmi.dgc.server.gcInterval=9223372036854775806

Class-Path:
/Users/deepakdixit/Downloads/apache-geode-1.14.4/lib/geode-core-1.14.4.jar:/Users/deepakdixit/Downloads/apache-geode-1.14.4/lib/geode-dependencies.jar


Unable to auto-connect (Security Manager may be enabled). Please use
"connect --locator=localhost[10334]" to connect Gfsh to the locator.


Failed to connect; unknown cause: Failed to retrieve RMIServer stub:
javax.naming.CommunicationException [Root exception is
java.rmi.ConnectIOException: error during JRMP connection establishment;
nested exception is:

java.io.EOFException]


Environment:
MacOS Monterey V12.3
Java Version openjdk version "1.8.0_322"

Can someone help to find out the root cause for this?



-- 
From:

Deepak D Dixit
deepakdixit2...@gmail.com
+919028507537

Re: New Committer And PMC Member: Joey McAllister

[Deepak Dixit]

Welcome Joey!

-
Deepak

On Wed, Jul 26, 2017 at 11:26 AM, Amey Barve  wrote:

> Welcome Joey and Congratulations!
>
> Regards,
> Amey
>
> On Wed, Jul 26, 2017 at 1:08 AM, Joey McAllister 
> wrote:
>
> > Thanks, everyone!
> >
> > [drum solos; throws sticks to Fred]
> >
> >
> > On Tue, Jul 25, 2017 at 12:36 PM Nitin Lamba  wrote:
> >
> > > Welcome Joey!
> > >
> > > On Tue, Jul 25, 2017 at 12:21 PM, Fred Krone 
> wrote:
> > >
> > > > Drum solo!
> > > >
> > > > On Tue, Jul 25, 2017 at 12:05 PM, Anthony Baker 
> > > wrote:
> > > >
> > > > > Welcome Joey!
> > > > >
> > > > > > On Jul 25, 2017, at 11:58 AM, Mark Bretl 
> > wrote:
> > > > > >
> > > > > > The Apache Geode Project Management Committee has invited Joey
> > > > > McAllister to
> > > > > > be committer on the project and join the Geode PMC. We are
> pleased
> > to
> > > > > > announce he has accepted.
> > > > > >
> > > > > > Please join me in welcoming Joey!
> > > > > >
> > > > > > Best regards,
> > > > > >
> > > > > > Mark
> > > > > > On behalf of the Apache Geode PMC
> > > > >
> > > > >
> > > >
> > >
> >
>



-- 
From:

Deepak D Dixit
deepakdixit2...@gmail.com
+919028507537

[jira] [Assigned] (GEODE-2960) gfsh create index should trim from field names

[Deepak Dixit (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Deepak Dixit reassigned GEODE-2960:
---

Assignee: Deepak Dixit

> gfsh create index should trim from field names
> --
>
> Key: GEODE-2960
> URL: https://issues.apache.org/jira/browse/GEODE-2960
> Project: Geode
>  Issue Type: Bug
>  Components: lucene
>Reporter: Jason Huynh
>Assignee: Deepak Dixit
>
> When creating an index with specific fields, the parameter expects a comma 
> separated string.  However we are not trimming after splitting the string.  
> So if fields are defined as --field="name, age, height, weight" the indexed 
> fields are actually "name", " age", " height", " weight"
> The command should probably trim the spaces before creating the index.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (GEODE-269) Remove deprecated methods on FunctionService

[Deepak Dixit (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Deepak Dixit reassigned GEODE-269:
--

Assignee: Deepak Dixit

> Remove deprecated methods on FunctionService
> 
>
> Key: GEODE-269
> URL: https://issues.apache.org/jira/browse/GEODE-269
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Darrel Schneider
>    Assignee: Deepak Dixit
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> FunctionService has a three deprecated methods that should be easy to remove. 
> All the deprecated methods have a DistributedSystem parameter. New flavors of 
> these methods exist that do not take the DistributedSystem since it is known 
> implicitly by the FunctionService.
> Many tests use the deprecated methods but it should be easy to change them.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (GEODE-265) Remove deprecated methods on Execution interface

[Deepak Dixit (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Deepak Dixit reassigned GEODE-265:
--

Assignee: Deepak Dixit

> Remove deprecated methods on Execution interface
> 
>
> Key: GEODE-265
> URL: https://issues.apache.org/jira/browse/GEODE-265
> Project: Geode
>  Issue Type: Sub-task
>Reporter: Darrel Schneider
>    Assignee: Deepak Dixit
>   Original Estimate: 5h
>  Remaining Estimate: 5h
>
> The Execution interface has a number of execute methods that have been 
> deprecated. It looks like these could be easily removed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Storing object in deserialized form in geode cache

[Deepak Dixit]

Thanks Darrel and Michael for your suggestion and will evaluate which suits
best for our use case.

-
Deepak





On Thu, Mar 9, 2017 at 3:42 AM, Darrel Schneider <dschnei...@pivotal.io>
wrote:

> Mike is correct that the first time you ask a VMCachedDeserializable for
> the deserialized value that the deserialized value will "stick" in the
> VMCachedDeserializable. If anyone then asks that VMCachedDeserializable for
> the serialized value it has to serialize it each time since it is now stuck
> as deserialized.
>
> Instead of doing inplace modification you might want to check out geode's
> Delta interface. It keeps the values in object form and allows the value to
> be distributed to be a subset of the full object that will be applied to
> the full object on other members.
>
> Also off-heap regions always store their values serialized.
>
> If your value is a "byte []" then it will not be wrapped by a
> VMCachedDeserializable. For "byte []" geode just stores a reference to the
> byte array.
>
> You might also want to checkout geode PDX serialization. It allows you to
> keep the data serialized on the server and still be able to fetch and
> modify fields on the serialized data.
>
> On Wed, Mar 8, 2017 at 10:41 AM, Michael Stolz <mst...@pivotal.io> wrote:
>
> > The rule is, if you deserialize the object in the server side, Geode
> keeps
> > the deserialized version of it around.
> >
> > As for updating in place...this is the position that the docs for
> > Commercial GemFire take on that subject:
> >
> > "If you do not have the cache copy-on-read attribute set to true, do not
> > change the objects returned from the Java entry access methods. Instead,
> > create a copy of the object, then modify the copy and pass it to the Java
> > put method. Modifying a value in place bypasses the entire distribution
> > framework provided by GemFire, including cache listeners and expiration
> > activities, and can produce undesired results."
> >
> > Of course if that's exactly the behavior you WANT, then set
> > copy-on-read=false.
> >
> >
> >
> > --
> > Mike Stolz
> > Principal Engineer, GemFire Product Manager
> > Mobile: +1-631-835-4771
> >
> > On Wed, Mar 8, 2017 at 1:37 AM, Deepak Dixit <deepakdixit2...@gmail.com>
> > wrote:
> >
> > > Hello Geode Team,
> > >
> > > I am working on a use case where I want to store the java object. I
> want
> > to
> > > avoid the serialization and deserialization while reading on server
> > > (function execution).
> > > Also while updating I would like to update in-place rather than to
> create
> > > copy of object, modify and store it again in underlying map.
> > >
> > > Based on my current understanding, every object is wrapped in
> > > "VMCachedDeserializable" and serialized / deserialized while doing
> > get/put.
> > >
> > > Kindly advice the way with which I can store object in deserialized
> form
> > in
> > > cache and do in place modifications.
> > >
> > > Thanks,
> > > Deepak
> > >
> >
>



-- 
From:

Deepak D Dixit
deepakdixit2...@gmail.com
+919028507537

Storing object in deserialized form in geode cache

[Deepak Dixit]

Hello Geode Team,

I am working on a use case where I want to store the java object. I want to
avoid the serialization and deserialization while reading on server
(function execution).
Also while updating I would like to update in-place rather than to create
copy of object, modify and store it again in underlying map.

Based on my current understanding, every object is wrapped in
"VMCachedDeserializable" and serialized / deserialized while doing get/put.

Kindly advice the way with which I can store object in deserialized form in
cache and do in place modifications.

Thanks,
Deepak

Review of Pull request #326

[Deepak Dixit]

Hello Team,

Kindly have a look over the pull request
https://github.com/apache/geode/pull/326.
This should the fix the JIRA GEODE-2103.

Thanks,
Deepak

Re: The right way to remove a region's cache listener?

[Deepak Dixit]

I would like to suggest, adding "add-cache-listener" option in addition to
"remove-cache-listener."
As adding listeners is as difficult as removing when doing alter region.

So alter region will have following options,

1) add-cache-listener - Will add provided cache listener to existing list.
2) remove-cache-listener - Will remove provided cache listeners. (Here we
may consider passing empty list will remove all listeners)

And old option of cache-listeners will be removed to eliminate confusion.

On Thu, Jan 5, 2017 at 5:51 PM, Zhang Xiawei 
wrote:

> Not sure whether I misunderstand/miss something or not, but isn't it
> possible that you have multiple instances of the same type of
> CacheListener? like 2 of ListenerTypeA and 3 of ListenerTypeB, so either
> way shown below modifies at a "category" level?
>
> -Xiawei
>
> > On 5 Jan 2017, at 1:25 AM, Anthony Baker  wrote:
> >
> > Another consideration is that gfsh commands should be easily scriptable,
> IMO.
> >
> > If I want to remove just one of the N listeners using this approach, I
> would need to acquire the list of existing listeners, remove the deselected
> listener, format the list, then pass it to this command.  Is there a way to
> do this in one simple command?
> >
> > Anthony
> >
> >> On Jan 3, 2017, at 11:08 AM, Kirk Lund  wrote:
> >>
> >> +1 I'm for the approach you're proposing. As long as it's documented in
> >> user docs (it's not currently) then this provides a straightforward use
> of
> >> the existing gfsh syntax without introducing too many new command
> options.
> >>
> >> Create the region with two cache listeners:
> >> $ create region --name=data
> >> --cache-listener="my.package.ListenerTypeA,my.package.ListenerTypeB"
> >>
> >> Change my mind and decide to remove one of the cache listeners:
> >> $ alter region --name=data --cache-listener="my.package.ListenerTypeB"
> >>
> >> -Kirk
> >>
> >>
> >>> On Tue, Jan 3, 2017 at 10:52 AM, Kevin Duling 
> wrote:
> >>>
> >>> Is this an intuitive User Experience?
> >>>
> >>> Given these two classes:
> >>>
> >>> public class ListenerTypeA extends CacheListenerAdapter implements
> >>> Declarable
> >>>
> >>> and
> >>>
> >>> public class ListenerTypeB extends CacheListenerAdapter implements
> >>> Declarable
> >>>
> >>> And they are programmatically added to a region:
> >>>
> >>> CacheListener listener1 = new ListenerTypeA();
> >>>
> >>> CacheListener listener2 = new ListenerTypeB();
> >>>
> >>> Region region = cache. >>> Customer>createClientRegionFactory(ClientRegionShortcut.CACHING_PROXY)
> >>>
> >>>   .initCacheListeners(new CacheListener[]{listener1,
> >>> listener2}).create("regionA");
> >>>
> >>>
> >>> What would the expected gfsh command to remove them.  Should we remove
> the
> >>> listeners via omission?  For example, removing listener1 might be:
> >>>
> >>> alter region --name=data --cache-listener='my.package.ListenerTypeB'
> >>>
> >>>
> >>> By only listing the listeners I want...either to keep and/or to add,
> >>> listener1 which is a ListenerTypeA, would be removed.
> >>>
> >>>
> >>>
> >>>
> >>>
>  On Tue, Dec 20, 2016 at 2:11 PM, Kevin Duling 
> wrote:
> 
>  I'm looking at GEODE-2236
>   and protecting
> >>> against
>  the NPE is trivial.  But the question is, what is the right way to do
>  this?  What is the syntax people would expect to use?
> 
> 
>  What if there are multiple listeners and you wanted to delete one or
> more
>  of them?
> >
>



-- 
From:

Deepak D Dixit
deepakdixit2...@gmail.com
+919028507537

[jira] [Commented] (GEODE-2109) calling submit on ExecutionService can cause exceptions to be lost

[Deepak Dixit (JIRA)]

[ 
https://issues.apache.org/jira/browse/GEODE-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15769028#comment-15769028
 ] 

Deepak Dixit commented on GEODE-2109:
-

I think this is for [~deepakddixit]  not for [~deepak.dixit] :)

> calling submit on ExecutionService can cause exceptions to be lost
> --
>
> Key: GEODE-2109
> URL: https://issues.apache.org/jira/browse/GEODE-2109
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Darrel Schneider
>Assignee: Deepak Dixit
>
> Geode has a number of places that call submit on ExecutionService. The submit 
> method returns a Future object. If the caller makes sure it calls "get" on 
> the Future then all is well. But in many places geode is not calling get. In 
> that case if the Runnable that was submitted throws an exception it gets 
> stored in the get and never logged. This can make it very hard to diagnose 
> problems.
> If the caller does not want to call get on the returned Future then it should 
> instead call the "execute" method. In that case the exception will be 
> unhandled and the unhandled exception handler code we have on the 
> LoggingThreadGroup class will cause the exception to be logged.
> Here are the places that should be changed to use execute instead of submit:
> org.apache.geode.internal.util.concurrent.CustomEntryConcurrentHashMap.clear()
> org.apache.geode.internal.cache.DiskStoreImpl.executeDiskStoreTask(Runnable)
> org.apache.geode.internal.cache.lru.HeapEvictor.onEvent(MemoryEvent)
> org.apache.geode.distributed.internal.InternalLocator.restartWithDS(InternalDistributedSystem,
>  GemFireCacheImpl)
> org.apache.geode.distributed.internal.FunctionExecutionPooledExecutor.FunctionExecutionPooledExecutor(BlockingQueue,
>  int, PoolStatHelper, ThreadFactory, int, boolean)
> org.apache.geode.internal.cache.PRHARedundancyProvider.scheduleCreateMissingBuckets()
> org.apache.geode.distributed.internal.InternalLocator.startSharedConfigurationService(GemFireCacheImpl)
> org.apache.geode.cache.client.internal.SingleHopClientExecutor.submitTask(Runnable)
> org.apache.geode.management.internal.FederatingManager.submitTask(Callable)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Assigning Jira tickets to new contributors

[Deepak Dixit]

Thanks William :)
I am able to assign JIRA on my apache id.


On Mon, Dec 12, 2016 at 8:29 AM, William Markito Oliveira <
william.mark...@gmail.com> wrote:

> Great! So assigning people to the "contributors" role is good enough for
> this, glad it worked!
>
> On Sun, Dec 11, 2016 at 6:51 PM Kirk Lund <kl...@apache.org> wrote:
>
> > Thanks William!
> >
> > On Sun, Dec 11, 2016 at 6:30 PM William Markito Oliveira <
> > william.mark...@gmail.com> wrote:
> >
> > > I've just add all 3 (vectorijk, deepakddixit, dalyssakim) as
> > "contributors"
> > >
> > > to the Geode JIRA project, but in the past we had problems with people
> > not
> > >
> > > being able to "self-assign" JIRAs if they're not in the "committers"
> > group.
> > >
> > >
> > >
> > > The workaround was to include them into the committers group on JIRA,
> > which
> > >
> > > don't necessary give them commit privilege on the codebase, just on
> JIRA.
> > >
> > > Alternatively now that we graduated we could try fixing the role
> > >
> > > "contributor" of JIRA to at least allow people to assign JIRAs to
> > >
> > > themselves.
> > >
> > >
> > >
> > > Please give it a try now and see if you can assign the tickets to you,
> > >
> > > otherwise let us know.   Thanks!
> > >
> > >
> > >
> > > On Sun, Dec 11, 2016 at 5:35 AM, Kai Jiang <jiang...@gmail.com> wrote:
> > >
> > >
> > >
> > > > Hi Kirk,
> > >
> > > >
> > >
> > > > I am also a new contributor to GEODE project. Also, I am working on a
> > few
> > >
> > > > issues(GEODE-2172 <https://issues.apache.org/jira/browse/GEODE-2172>
> > >
> > > > GEODE-2167 <https://issues.apache.org/jira/browse/GEODE-2167>
> > GEODE-224
> > >
> > > > <https://issues.apache.org/jira/browse/GEODE-224>) . Maybe these
> issue
> > >
> > > > could be assigned to me.
> > >
> > > > Meanwhile, I will be appreciated if someone could review my pull
> > > requests.
> > >
> > > >
> > >
> > > > JIRA id: vectorijk
> > >
> > > > Github id: vectorijk
> > >
> > > >
> > >
> > > > Thanks,
> > >
> > > > Kai.
> > >
> > > >
> > >
> > > >
> > >
> > > >
> > >
> > > > On Sat, Dec 10, 2016 at 10:57 PM, Deepak Dixit <
> > > deepakdixit2...@gmail.com>
> > >
> > > > wrote:
> > >
> > > >
> > >
> > > > > Hello Kirk,
> > >
> > > > >
> > >
> > > > > I remember some apache help document mentioning need for user to be
> > > added
> > >
> > > > > to the project group.
> > >
> > > > > May be adding user to GEODE project group will help in enabling
> them
> > to
> > >
> > > > > assign issues to themselves.
> > >
> > > > >
> > >
> > > > > Can you please grant similar permission to me (details are added
> > below)
> > >
> > > > so
> > >
> > > > > I can assign JIRA issue I am working on?
> > >
> > > > > I am currently working on GEODE-2109 and just finished with
> > GEODE-734.
> > >
> > > > >
> > >
> > > > > Detail for apache id
> > >
> > > > > Email ID: deepakdixit2...@gmail.com
> > >
> > > > > apache id: deepakddixit
> > >
> > > > >
> > >
> > > > > Thanks,
> > >
> > > > >
> > >
> > > > > Deepak
> > >
> > > > >
> > >
> > > > >
> > >
> > > > > On Dec 11, 2016 9:41 AM, "Kirk Lund" <kl...@apache.org> wrote:
> > >
> > > > >
> > >
> > > > > Does anyone know what needs to be done to enable assigning a Jira
> > > ticket
> > >
> > > > to
> > >
> > > > > a new contributor? Alyssa Kim filed GEODE-2203 and would like to
> have
> > > the
> > >
> > > > > ticket assigned to her but Jira shows either "No Matches" or "User
> > >
> > > > 'Alyssa
> > >
> > > > > Kim' does not exist." -- her user id on the Apache Jira is
> > dalyssakim.
> > >
> > > > >
> > >
> > > > > Thanks,
> > >
> > > > > Kirk
> > >
> > > > >
> > >
> > > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > --
> > >
> > > ~/William
> > >
> > >
> >
>



-- 
From:

Deepak D Dixit
deepakdixit2...@gmail.com
+919028507537

[jira] [Assigned] (GEODE-2109) calling submit on ExecutionService can cause exceptions to be lost

[Deepak Dixit (JIRA)]

 [ 
https://issues.apache.org/jira/browse/GEODE-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Deepak Dixit reassigned GEODE-2109:
---

Assignee: Deepak Dixit

> calling submit on ExecutionService can cause exceptions to be lost
> --
>
> Key: GEODE-2109
> URL: https://issues.apache.org/jira/browse/GEODE-2109
> Project: Geode
>  Issue Type: Bug
>  Components: regions
>Reporter: Darrel Schneider
>Assignee: Deepak Dixit
>
> Geode has a number of places that call submit on ExecutionService. The submit 
> method returns a Future object. If the caller makes sure it calls "get" on 
> the Future then all is well. But in many places geode is not calling get. In 
> that case if the Runnable that was submitted throws an exception it gets 
> stored in the get and never logged. This can make it very hard to diagnose 
> problems.
> If the caller does not want to call get on the returned Future then it should 
> instead call the "execute" method. In that case the exception will be 
> unhandled and the unhandled exception handler code we have on the 
> LoggingThreadGroup class will cause the exception to be logged.
> Here are the places that should be changed to use execute instead of submit:
> org.apache.geode.internal.util.concurrent.CustomEntryConcurrentHashMap.clear()
> org.apache.geode.internal.cache.DiskStoreImpl.executeDiskStoreTask(Runnable)
> org.apache.geode.internal.cache.lru.HeapEvictor.onEvent(MemoryEvent)
> org.apache.geode.distributed.internal.InternalLocator.restartWithDS(InternalDistributedSystem,
>  GemFireCacheImpl)
> org.apache.geode.distributed.internal.FunctionExecutionPooledExecutor.FunctionExecutionPooledExecutor(BlockingQueue,
>  int, PoolStatHelper, ThreadFactory, int, boolean)
> org.apache.geode.internal.cache.PRHARedundancyProvider.scheduleCreateMissingBuckets()
> org.apache.geode.distributed.internal.InternalLocator.startSharedConfigurationService(GemFireCacheImpl)
> org.apache.geode.cache.client.internal.SingleHopClientExecutor.submitTask(Runnable)
> org.apache.geode.management.internal.FederatingManager.submitTask(Callable)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Assigning Jira tickets to new contributors

[Deepak Dixit]

Hello Kirk,

I remember some apache help document mentioning need for user to be added
to the project group.
May be adding user to GEODE project group will help in enabling them to
assign issues to themselves.

Can you please grant similar permission to me (details are added below) so
I can assign JIRA issue I am working on?
I am currently working on GEODE-2109 and just finished with GEODE-734.

Detail for apache id
Email ID: deepakdixit2...@gmail.com
apache id: deepakddixit

Thanks,

Deepak


On Dec 11, 2016 9:41 AM, "Kirk Lund"  wrote:

Does anyone know what needs to be done to enable assigning a Jira ticket to
a new contributor? Alyssa Kim filed GEODE-2203 and would like to have the
ticket assigned to her but Jira shows either "No Matches" or "User 'Alyssa
Kim' does not exist." -- her user id on the Apache Jira is dalyssakim.

Thanks,
Kirk