Re: SpiQuery fails with exception

[vkulichenko]

Hi Kamil,

Is it reproduced each time you run the query or only under the load? Is it
possible for you to share the code with us, so that we can investigate?

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/SpiQuery-fails-with-exception-tp3615p3617.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Topic Based Messaging

[vkulichenko]

Hi,

Can you please properly subscribe to the mailing list so that the community
receives email notifications? Her is the instruction:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1


hemanta wrote
> I have two machines with one configured as ignite server and other as
> client. Can I reply on Ignite Topic Based Messaging for sending messages
> from client to server? What would happen when server is down or restarting
> and client wants to send a message?
> 
> Are these topics durable? Will it store message till the time server comes
> up?

Messages are sent asynchronously, so there is no delivery guarantee. I think
you should take a look at Compute Grid [1], which supports failover between
nodes. Can you please check if it can help with your use case?

[1] https://apacheignite.readme.io/docs/compute-grid

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Topic-Based-Messaging-tp3614p3616.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

SpiQuery fails with exception

[knowak]

Hi,
 
We’ve setup custom IndexSpi but when trying to run SpiQuery exception below
shows up. Is there anything we’re missing?
Worth adding that after excluding this validation for SPI queries (at
GridCacheQueryManager.java:663) all seem to be working as expected. Ignite
version - 1.5.0.final.
 

class org.apache.ignite.IgniteCheckedException: Received next page request
after iterator was removed. Consider increasing maximum number of stored
iterators (see GridCacheConfiguration.getMaximumQueryIteratorCount()
configuration property).
at
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.executeFieldsQuery(GridCacheQueryManager.java:666)
at
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.fieldsQueryResult(GridCacheQueryManager.java:1818)
at
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.fieldsQueryResult(GridCacheQueryManager.java:1784)
at
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.runFieldsQuery(GridCacheQueryManager.java:1194)
at
org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.processQueryRequest(GridCacheDistributedQueryManager.java:225)
at
org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager$2.apply(GridCacheDistributedQueryManager.java:105)
at
org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager$2.apply(GridCacheDistributedQueryManager.java:103)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:582)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:280)
(…)

 
Thanks,
Kamil



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/SpiQuery-fails-with-exception-tp3615.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Is there a way to get original object reference from IgniteCache?

[vkulichenko]

Hi Jimmy,

Ignite stores data in serialized form, i.e. the object that you put is
serialized and saved as a byte array.  Having said that, you have to use
IgniteCache.put() to update the cache.

Note that you can always acquire Ignite instance using Ignition.ignite()
method. It's static, so you can do this anywhere in the code. Will this work
for you?

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Is-there-a-way-to-get-original-object-reference-from-IgniteCache-tp3611p3613.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Node discovery

[babu prasad]

Sorry, my mistake. I realized it was a networking issue. Its fixed now.
What ports should I be whitelisting for the setup to work in a firewall?

On Mon, Mar 21, 2016 at 11:33 AM, babu prasad  wrote:

> Thank you!
> Here is the configuration.
> 
>
> 
>
> http://www.springframework.org/schema/beans;
>xmlns:util="http://www.springframework.org/schema/util;
>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.xsd
>http://www.springframework.org/schema/util
>http://www.springframework.org/schema/util/spring-util.xsd;>
> 
>class="org.apache.ignite.configuration.IgniteConfiguration">
> 
>   
> 
>   
>   
>   
>   
> 
>class="org.apache.ignite.cache.eviction.lru.LruEvictionPolicy">
> 
> 
>   
>   
> 
> 
> 
>  
> 
> 
> 
>   
>  class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>   
> 
>   127.0.0.1:47500..47509
> 
> 
>   
>  
>   
> 
> 
> 
>  class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi">
>   
> 
>   
>   
>   
>
> On Mon, Mar 21, 2016 at 1:39 AM, Vladimir Ozerov 
> wrote:
>
>> Hi,
>>
>> Looks like a kind of misconfiguration or networking problem. Please
>> provide XML configuration you used to build the cluster.
>>
>> Vladimir.
>>
>> On Mon, Mar 21, 2016 at 10:29 AM, babu prasad  wrote:
>>
>>> Hi,
>>>
>>> I am trying to automate ignite cluster build.
>>> I am using apache-ignite-fabric-1.5.0.final-bin.zip.
>>> Looks like the nodes are starting up as individual nodes and not as part
>>> of the cluster.
>>>
>>> I tried using both the AWS configuration(using S3) and static IP and I
>>> am still running into the issue where the nodes are not discovered as part
>>> of the cluster.
>>>
>>> Could something be broken?
>>>
>>> Thanks!
>>>
>>> -Babu
>>>
>>
>>
>

Re: Hibernate loadcache error?

[Denis Magda]

Ravi,

If you start a node using ignite.sh/ignite.bat provided with Ignite bundles
then perform the following steps:
- go to {ignite_bundle}/libs/optional folder;
- move ignite-hibernate directory from {ignite_bundle}/libs/optional to
{ignite_bundle}/libs folder
- start the node using ignite.sh/ignite.bat

--
Denis



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Hibernate-loadcache-error-tp3534p3606.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Hibernate connection inspite of jdbc?

[Denis Magda]

Ravi,

Have you tried to launch CacheHibernateStoreExample that is delivered as a
part of Ignite bundles and can be located in
'examples\src\main\java-lgpl\..' directory?

Try to check everything directly from IDE (like IntellijIdea, Eclipse).
Start additional server nodes from IDE as well.

--
Denis



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Hibernate-connection-inspite-of-jdbc-tp3412p3607.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: JMS Data Streamer: Not writing to data to cache when message received by Streamer

[Denis Magda]

Raul,

/If I understand correctly, flushing controls when the changes in the 
streamer will be sent to the grid (can someone confirm?). /


Your understanding is correct. Autoflush allows to trigger data flushing 
to the grid periodically.
If autoflush is disabled then the data is sent either when 
IgniteDataStreamer. perNodeBufferSize is reached or flush()/close() is 
called manually.


--
Denis

On 3/20/2016 1:12 PM, Raul Kripalani wrote:


Auto flush / flushing is a characteristic of all streamers, that's why 
you won't find it explained explicitly in the docs of specific 
streamers, but in the general streamer one.


If I understand correctly, flushing controls when the changes in the 
streamer will be sent to the grid (can someone confirm?).


Autoflush is disabled by default, i.e. meaning that you must call 
flush() manually on the streamer for the writes to be visible in the 
cache.


To avoid that, and if your use case permits it, autoflush will flush 
the buffered entries periodically.


When in doubt, you can check the unit tests for the component you're 
working with.


Cheers,
Raúl.

On 20 Mar 2016 02:02, "techbysample" > wrote:


That worked.  Thank you very much.

Would you please elaborate on how property is used?
Does it imply that by default autoflushFrequency is disabled and
DataStreamer will NOT
write data to cache unless explicitly set?

I basically modeled my JMSStreamer after the following
documentation here:
https://apacheignite.readme.io/docs/jms-data-streamer
The docs do not explicitly mention setting 'autoflushFrequency'..


Here is definition from Apache Ignite docs: -
dataStreamer.autoFlushFrequency:


"Sets automatic flush frequency. Essentially, this is the time
after which
the streamer will make an attempt to submit all data added so far
to remote
nodes. Note that there is no guarantee that data will be delivered
after
this concrete attempt (e.g., it can fail when topology is
changing), but it
won't be lost anyway.

If set to 0, automatic flush is disabled.

Automatic flush is disabled by default (default value is 0)."


Please advise.

Thank you






--
View this message in context:

http://apache-ignite-users.70518.x6.nabble.com/JMS-Data-Streamer-Not-writing-data-to-cache-when-message-received-by-Streamer-tp3590p3592.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

question about how to monitor ignite

[minisoft_rm]

I am using ignite to "select" lots of DB records into cache.
after that, I want to follow the "To start Console Management & Monitoring
run ignitevisorcmd.{sh|bat}".

however, not get correct idea how to use it. the reason is that I ran ignite
test from eclipse... and not xml Configuration File. so what should I do:
[
visor> open
Local configuration files:
++
| #  |Configuration File

|
++
| 0  | config/default-config.xml

|
| 1  | (?) config/router/default-router.xml 

|
| 2  | examples/config/example-cache.xml

|
| 3  | examples/config/example-default.xml  

|

++

Choose configuration file number ('c' to cancel) [0]: c
]

besides, not sure if GridGain provide web style monitoring tool like web
console? thanks~



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/question-about-how-to-monitor-ignite-tp3599.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Node discovery

[babu prasad]

Hi,

I am trying to automate ignite cluster build.
I am using apache-ignite-fabric-1.5.0.final-bin.zip.
Looks like the nodes are starting up as individual nodes and not as part of
the cluster.

I tried using both the AWS configuration(using S3) and static IP and I am
still running into the issue where the nodes are not discovered as part of
the cluster.

Could something be broken?

Thanks!

-Babu

Re: Hibernate loadcache error?

[Ravi Puri]

how to enable ignite hibernate module? 



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Hibernate-loadcache-error-tp3534p3597.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.