HI
We're to examine ignite1.5.
We are being developed using the ContinuousQuery.
I put the cache in two server nodes, the update notification leak occurred
It did not occur in ignite1.4
In the ContinuousQuery set RemoteFilter did not use
Piece of code like this:
CacheEntryUpdatedListener
cache
Hi Vladimir...I downloaded 1.5.0 final version binary and am able to run
the examples now. Thanks much for your help.
Murthy.
On Tue, Jan 5, 2016 at 2:57 PM, Vladimir Ozerov
wrote:
> Murthy,
>
> Looks like your IGNITE_HOME is not correct. Please try pointing it to
> "C:\Data\Professional\java\i
Here the object what u are using is wrong
Sent from my iPhone
> On Jan 5, 2016, at 9:33 PM, wychoi wrote:
>
> HI
>
> We're to examine ignite1.5.
> We had an error occurs while using the Continuous Query.
> Piece of code like this:
> It was applied to the CacheEntryEventSerializableFilter.setR
HI
We're to examine ignite1.5.
We had an error occurs while using the Continuous Query.
Piece of code like this:
It was applied to the CacheEntryEventSerializableFilter.setRemoteFilter of
ContinuousQuery.
query.setRemoteFilter(new CacheEntryEventSerializableFilter() {
@Override
public b
Hi Ravi,
Can you please properly subscribe to the mailing list so that community
receives email notifications? Just follow the simple instruction here:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
Ravi wrote
> [13:09:24,794][SEVERE][main][IgniteKerna
Murthy,
Looks like your IGNITE_HOME is not correct. Please try pointing it to
"C:\Data\Professional\java\ignite\software\apache-ignite-1.5.0-b1-src"
Vladimir.
On Tue, Jan 5, 2016 at 4:39 PM, Murthy Kakarlamudi wrote:
> Hi Vladimir,
> I did, but still getting the same error.
>
> [image: I
Hi Vladimir,
I did, but still getting the same error.
[image: Inline image 1]
On Tue, Jan 5, 2016 at 2:13 AM, Vladimir Ozerov
wrote:
> Hi Murthy,
>
> Could you please double-check that you have JAVA_HOME environment variable
> set and pointing to your Java installation directory?
> BTW, 1.
>From what I see thread cannot acquire lock for segment in cache map. Given
it already holds lock for individual entry and "main" thread has acquired
lock for segment and tries to lock that individual entry (which is proper
order we follow in Ignite). This is canonical deadlock and also one of the
