Welcome to the new Gigaspaces XAP forum. To recover your account, please follow these instructions.

Ask Your Question

GS_User's profile - activity

2018-05-23 09:03:03 -0500 asked a question SpaceEvictionStrategy callbacks works for one space model only

SpaceEvictionStrategy callbacks works for one space model only Hi! I am using LRU mechanism with a custom eviction polic

2018-05-23 09:00:51 -0500 asked a question SpaceEvictionStrategy callbacks works for one space model only

SpaceEvictionStrategy callbacks works for one space model only Hi! I am using LRU mechanism with a custom eviction polic

2018-03-19 14:38:44 -0500 commented answer WriteMultiple with space based remoting?

Could you provide a simple example demonstrating usage? Is RemoteRoutingHandler.computeRouting invoked for each element

2018-03-19 13:49:22 -0500 commented answer WriteMultiple with space based remoting?

Could you provide a simple example demonstrating usage? Is RemoteRoutingHandler.computeRouting invoked for each element

2018-03-19 13:38:13 -0500 commented answer WriteMultiple with space based remoting?

Could you provide a simple example demonstrating usage?

2018-03-19 13:38:13 -0500 received badge  Commentator
2018-03-19 13:37:40 -0500 received badge  Famous Question (source)
2018-03-19 13:10:55 -0500 commented answer Get previous on update event

I saw some commented out code though in gigaspaces 12.2.1 suggesting a feature like this will be available in the future

2018-03-14 07:13:41 -0500 received badge  Notable Question (source)
2018-03-14 05:11:05 -0500 commented question WriteMultiple with space based remoting?

@ExecutorRemotingMethod(broadcast = true) void saveEntries(@Routing("[*].getRoutingKey") SomeEntity[] batch) Could be a

2018-03-14 05:10:55 -0500 commented question WriteMultiple with space based remoting?

`@ExecutorRemotingMethod(broadcast = true) void saveEntries(@Routing("[*].getRoutingKey") SomeEntity[] batch)` Could b

2018-03-14 05:10:44 -0500 commented question WriteMultiple with space based remoting?

@ExecutorRemotingMethod(broadcast = true) void saveEntries(@Routing("[*].getRoutingKey") SomeEntity[] batch) Could be a

2018-03-14 05:09:52 -0500 commented question WriteMultiple with space based remoting?

@ExecutorRemotingMethod(broadcast = true) void saveEntries(@Routing("[*].getRoutingKey") SomeEntity[] batch) Could be

2018-03-14 05:09:37 -0500 commented question WriteMultiple with space based remoting?

@ExecutorRemotingMethod(broadcast = true) void saveEntries(@Routing("[*].getRoutingKey") SomeEntity[] batch) Could be a

2018-03-14 04:39:12 -0500 received badge  Popular Question (source)
2018-03-13 07:51:23 -0500 edited question WriteMultiple with space based remoting?

WriteMultiple with space based remoting? With a clustered proxy, we can use writeMultiple to save multiple objects with

2018-03-13 07:35:23 -0500 asked a question WriteMultiple with space based remoting?

WriteMultiple with space based remoting? With a clustered proxy, we can use writeMultiple to save multiple objects with

2018-03-09 06:54:41 -0500 received badge  Famous Question (source)
2018-03-06 02:56:29 -0500 received badge  Notable Question (source)
2018-03-05 04:10:53 -0500 received badge  Popular Question (source)
2018-03-01 06:30:41 -0500 asked a question Get previous on update event

Get previous on update event Is it possible in your notify container get the previous version in an update event? @Not

2018-02-15 09:09:47 -0500 commented answer Expired leases doesn't remove their corresponding entity in persistence

Sorry for being unclear. The downside did I explain where we need to inject a Mongo client etc. This is done in the poll

2018-02-13 16:30:22 -0500 commented answer Expired leases doesn't remove their corresponding entity in persistence

We see leases as a core feature of Gigaspaces. The same goes for mirroring/persistence. Thus, a workaround shouldn't be

2018-02-12 08:11:25 -0500 commented answer Expired leases doesn't remove their corresponding entity in persistence

We see leases as a core feature of Gigaspaces. The same goes for mirroring/persistence. Thus, a workaround shouldn't be

2018-02-12 07:59:11 -0500 commented answer Expired leases doesn't remove their corresponding entity in persistence

We see leases as a core feature of Gigaspaces. The same goes for mirroring/persistence. Thus, a workaround shouldn't be

2018-02-12 07:55:31 -0500 commented answer Expired leases doesn't remove their corresponding entity in persistence

We see leases as a core feature of Gigaspaces. The same goes for mirroring/persistence. Thus, a workaround shouldn't be

2018-02-12 05:14:54 -0500 commented answer Expired leases doesn't remove their corresponding entity in persistence

We see leases as a core feature of Gigaspaces. The same goes for mirroring/persistence. Thus, a workaround shouldn't be

2018-02-06 06:11:56 -0500 received badge  Famous Question (source)
2018-02-04 07:01:10 -0500 received badge  Notable Question (source)
2018-02-01 11:46:20 -0500 received badge  Notable Question (source)
2018-02-01 10:31:16 -0500 received badge  Popular Question (source)
2018-02-01 07:04:00 -0500 received badge  Popular Question (source)
2018-01-31 10:14:00 -0500 edited question Expired leases doesn't remove their corresponding entity in persistence

Expired leases doesn't remove their corresponding entity in persistence We use Gigaspaces as an in-memory database and b

2018-01-31 10:02:16 -0500 edited question Expired leases doesn't remove their corresponding entity in persistence

Expired leases doesn't remove their corresponding entity in persistence We use Gigaspaces as an in-memory database and b

2018-01-31 10:00:42 -0500 edited question Expired leases doesn't remove their corresponding entity in persistence

Expired leases doesn't remove their corresponding entity in persistence? We use Gigaspaces as an in-memory database and

2018-01-31 09:49:19 -0500 asked a question Expired leases doesn't remove their corresponding entity in persistence

Expired leases doesn't remove their corresponding entity in persistence? We use Gigaspaces as an in-memory database and

2018-01-31 09:46:33 -0500 asked a question Removing entity from persistence storage when lease expire?

Removing entity from persistence storage when lease expire? We use Gigaspaces as an in-memory database and back up our d

2018-01-24 03:50:20 -0500 received badge  Enthusiast
2018-01-23 03:09:09 -0500 commented answer Remoting serivce route incorrectly?

Sure! Where do we report bugs?

2018-01-18 09:42:36 -0500 received badge  Supporter (source)
2018-01-18 09:42:34 -0500 marked best answer Remoting serivce route incorrectly?

Hi!

I have this method in my remoting interface:

void create(@Routing("getId") User user);

getId returns a java.lang.Long object.

If I invoke this method with an id that's something low, for example 100, everything works great. The end object is created and returns correctly.

If the id is really high, for example 6986832704440059829, I get an error later in the stack when I try to create the object in the space. It tells me that the object should not be in this partition.

Here is the exact message:

Operation is rejected - the routing value in the written entry of type 'com.company.User' does not match this space partition id. The value within the entry's routing property named 'id' is 6986832704440059829 which matches partition id 2 while current partition id is 1.

So far, we have done a workaround by creating wrapper classes around Long/Integer and also Strings(they suffer from this as well) and implementing a custom hashCode(java.util.Objects.hash).

But this worwkaround feels wrong. java.lang.Long for example should work with any value.

So my question is, is this a bug? If so, will it be fixed? Or am I doing something wrong?

2018-01-18 09:42:34 -0500 received badge  Scholar (source)
2018-01-18 09:42:24 -0500 commented answer Remoting serivce route incorrectly?

Hi! Setting property com.gs.disable-precise-long-routing to true resolves indeed our issues. The space based remoting ro

2018-01-17 03:40:36 -0500 commented answer Remoting serivce route incorrectly?

I am using version 12 and me and my colleague are still suffering from this. Basically, having java.lang.Long as id won

2018-01-17 03:40:28 -0500 commented answer Remoting serivce route incorrectly?

I am well aware that an entity must be saved in the correct partition in order for it to be retrieved. Otherwise it's fo

2018-01-16 08:29:55 -0500 received badge  Famous Question (source)