date:20200928

RE: Issue while deploying the Ignite application in Wildfly Server

2020-09-28 Thread DEEPTHI KOLLIPARA

Dear Ilya,

Its working fine after doing the modifications as suggested in the url.
https://stackoverflow.com/a/59453413/36498

Thank you for the support.

Thanks
Deepthi K

Sent from Mail for Windows 10

From: Ilya Kasnacheev
Sent: Monday, September 28, 2020 7:47 PM
To: user@ignite.apache.org
Subject: Re: Issue while deploying the Ignite application in Wildfly Server

"External email. Open with Caution"
Hello!

Unfortunately, we have this bug, which was never fixed: 
https://issues.apache.org/jira/browse/IGNITE-12483

You will have to apply solution from this SO answer:
https://stackoverflow.com/a/59453413/36498

Regards,
--
Ilya Kasnacheev


пн, 28 сент. 2020 г. в 17:08, DEEPTHI KOLLIPARA 
mailto:deepthi.kollip...@tcs.com>>:
Dear Ilya,
   jar is also added to the 
module.xml.
I have added the below parameters to Java arguments.
--add-exports java.base/jdk.internal.misc=ALL-UNNAMED --add-exports 
java.base/sun.nio.ch=ALL-UNNAMED --add-exports 
java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED --add-exports 
jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED

Below error is thrown after adding the above parameter. Please suggest.

Failed to find empty constructor for class: 
org.apache.ignite.internal.processors.platform.websession.PlatformDotNetSessionLockResult
org.apache.ignite.binary.BinaryObjectException: Failed to find empty 
constructor for class: 
org.apache.ignite.internal.processors.platform.websession.PlatformDotNetSessionLockResult
at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.constructor(BinaryClassDescriptor.java:981)
 ~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.(BinaryClassDescriptor.java:267)
 ~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.binary.BinaryContext.registerPredefinedType(BinaryContext.java:1063)
 ~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.binary.BinaryContext.registerPredefinedType(BinaryContext.java:1048)
 ~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.binary.BinaryContext.(BinaryContext.java:350) 
~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.start(CacheObjectBinaryProcessorImpl.java:208)
 ~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1700) 
~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1013) 
~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
 ~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1730)
 ~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158) 
~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1076) 
~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:962) 
~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:861) 
~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:731) 
~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:700) 
~[ignite-core-2.7.0.jar:2.7.0]
at org.apache.ignite.Ignition.start(Ignition.java:348) 
~[ignite-core-2.7.0.jar:2.7.0]



Sent from Mail for Windows 10

From: Ilya Kasnacheev
Sent: Monday, September 28, 2020 7:31 PM
To: user@ignite.apache.org
Subject: Re: Issue while deploying the Ignite application in Wildfly Server

"External email. Open with Caution"
Hello!

You also need to add ignite-spring 2.7.0 dependency.



Regards,
--
Ilya Kasnacheev


вс, 27 сент. 2020 г. в 15:17, DEEPTHI KOLLIPARA 
mailto:deepthi.kollip...@tcs.com>>:
Dear Team,

  I am trying to deploy a web application with ignite 2.7 version on Wildfly 
server 20.0. Ignite client node will be started from the application.


Below error is thrown from when starting the node. Same war is deployed and 
worked successfully in Tomcat.
I have added the below entry to Wildfly modules. Anything is missed here?

Path of the file:
wildfly-20.0.0.Final/modules/system/layers/base/org/ignite/main















2020-09-25 18:10:45 ERROR FactsLogger:104 - InputMode

Re: Binary memory restoration

2020-09-28 Thread Raymond Wilson

There is a summary log line that also references the time taken by the
'restore binary memory' stage. It also references another stage called
'restore logical state'.

eg:

2020-09-27 20:50:31,423 [1] INF [] Node started : [stage="Configure system
pool" (44 ms),stage="Start managers" (2422 ms),stage="Configure binary
metadata" (487 ms),stage="Start processors" (1089 ms),stage="Init
metastore" (726 ms),stage="Init and start regions" (21 ms),stage="Restore
binary memory" (30289 ms),stage="Restore logical state" (76551
ms),stage="Finish recovery" (201 ms),stage="Join topology" (840
ms),stage="Await transition" (136 ms),stage="Await exchange" (211
ms),stage="Total time" (113017 ms)]

The restore logical state stage takes 76 seconds in this example.

Currently we have around 10 caches with less than 20 Gb of data. Do these
startup times seem reasonable for a node that is shut down gracefully?

Thanks,
Raymond.


On Tue, Sep 29, 2020 at 11:20 AM Raymond Wilson 
wrote:

> Just a general query on Ignite server node startup sequence.
>
> There are a pair of log lines emitted during node startup that look like
> this:
>
> 2020-09-27 20:48:43,191 [1] INF [] Starting binary memory restore for:
> [948695530, -1026154091, -2049124072, -552847479, -2024686410, -1820754607,
> -1907049797, -1029472048, 671082124, -493080817, -2100569601, 928822533]
>
> and
>
> 2020-09-27 20:49:13,025 [1] INF []   Binary memory state restored at node
> startup [restoredPtr=FileWALPointer [idx=1033, fileOff=485201080, len=0]]
>
>
>  This particular example required ~30 seconds to complete.
>
> We are running Ignite 2.8.1 using the C# client with persistence enabled.
>
> Do these messages indicate Ignite is reloading the memory state of the
> caches at the point it was shutdown? If not, what is this activity?
>
> Thanks,
> Raymond.
>
> --
> 
> Raymond Wilson
> Solution Architect, Civil Construction Software Systems (CCSS)
> 11 Birmingham Drive | Christchurch, New Zealand
> +64-21-2013317 Mobile
> raymond_wil...@trimble.com
>
>
> 
>


-- 

Raymond Wilson
Solution Architect, Civil Construction Software Systems (CCSS)
11 Birmingham Drive | Christchurch, New Zealand
+64-21-2013317 Mobile
raymond_wil...@trimble.com

Binary memory restoration

2020-09-28 Thread Raymond Wilson

Just a general query on Ignite server node startup sequence.

There are a pair of log lines emitted during node startup that look like
this:

2020-09-27 20:48:43,191 [1] INF [] Starting binary memory restore for:
[948695530, -1026154091, -2049124072, -552847479, -2024686410, -1820754607,
-1907049797, -1029472048, 671082124, -493080817, -2100569601, 928822533]

and

2020-09-27 20:49:13,025 [1] INF []   Binary memory state restored at node
startup [restoredPtr=FileWALPointer [idx=1033, fileOff=485201080, len=0]]

 This particular example required ~30 seconds to complete.

We are running Ignite 2.8.1 using the C# client with persistence enabled.

Do these messages indicate Ignite is reloading the memory state of the
caches at the point it was shutdown? If not, what is this activity?

Thanks,
Raymond.

-- 

Raymond Wilson
Solution Architect, Civil Construction Software Systems (CCSS)
11 Birmingham Drive | Christchurch, New Zealand
+64-21-2013317 Mobile
raymond_wil...@trimble.com

Re: High number of Exception Unexpected response ID with setTimeout

2020-09-28 Thread Andrei Aleksandrov


Hi,

It will be great to take a look at full logs that contain these errors.

BR,
Andrei

9/28/2020 12:35 PM, AravindJP пишет:

Thank you stepan for your reply , problem is the parent thread calling ignite
cache get has a timeout of 120 ms , hence we allow a max of 100 ms for every
cache read . We are seeing that during non peak time , 80% of cache read is
< 20 ms only . But during peak load application is crashing with some
threads going beyond 400 to 500 ms . That's the reason why we had to limit
timeout to 50 . But why such an exception occurs ? Why such an exception
occurs from Ignite side ?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

2020-09-28 Thread Ilya Kasnacheev

Hello!

I'm afraid that you may need to drop and recreate these caches to change
their configuration, including Cache Store config.

Regards,
-- 
Ilya Kasnacheev


пн, 28 сент. 2020 г. в 00:27, xmw45688 :

> I'm able to use Cassandra Together with Ignite Persistence (see the example
> below) usingIgnite 2.8.1.  However I could not change to another keyspace
> which has the same tables as the keyspace initially configurfed in the
> ignite config file.  The data changes are still stored in the old keyspace
> instead of the new keyspace that are in ignite config file.  It's seem to
> me
> that the keyspace are cached in the Ignite native persistence layer.
>
> How do I change the keyspaces of Cassandra?
>
> The use case is that we use Ignite as cache initially with the data stored
> in Cassandra.  With the data increase, caching all data is impractical.  So
> we plan to flush the data into the disk when the memory reaches the
> limits.
> We still want to store the data into Cassandra at the same time.  How do we
> load the the existing data from Cassandra Store to Native Persistence store
> when switching from Ignite Cache + Cassandra Store to Ignite Cache +Ignite
> persistence + Cassandra Store?
> Here is what I did -
> 1) duplicated the existing tables (no data) into the another keyspace in
> Cassandra
> 2) read the data from the original keyspace with Cassndra driver. This
> loaded the data into
>   2.1) ignite cache and native persistence
>   2.2) store the data into the new Cassandra keyspace.  it's undesirable to
> the store the original data back to the original keyspace.
> 3) change the cassandra connection setting to switch to the original
> keyspace because Ignite Cache and Native Persistence layer have all data
> from the Cassandra.
>   3.1) switching to the original cassandra keyspace did not take any
> effect.
> The data changes were still stored into the new keyspace.
>
> Config files
> 1. cassandra-connection-settings.xml
> http://www.springframework.org/schema/beans";
>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";>
>
>  class="com.datastax.driver.core.policies.TokenAwarePolicy">
>  type="com.datastax.driver.core.policies.LoadBalancingPolicy">
>  class="com.datastax.driver.core.policies.RoundRobinPolicy"/>
> 
> 
> 
> class="com.datastax.driver.core.policies.ExponentialReconnectionPolicy">
> 
> 
> 
>
>  class="com.datastax.driver.core.policies.DefaultRetryPolicy">
> 
>
>
>  class="org.apache.ignite.cache.store.cassandra.datasource.DataSource"
> name="cassandra">
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
> 
>
> 2. dim_store_key_persistence.xm
> 
> 
> 
> 
> 
> 
>  >
> 
> 
> 
> 
> 
> 
>
> 3. ignite config
> 
> http://www.springframework.org/schema/beans";
>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";>
>
>
>
>
> 
>
> 
>
>
> 
> class="org.apache.ignite.cache.store.cassandra.persistence.KeyValuePersistenceSettings">
>  value="classpath:dim_store_key_persistence.xml" />
> 
>
>
> 
>
> 
> 
>
>
>  value="/c:/apache/data/home/work-cassandra"/>
>
> 
>  class="org.apache.ignite.configuration.DataStorageConfiguration">
>
> 
>  class="org.apache.ignite.configuration.DataRegionConfiguration">
> 
> 
>
> 
>
>
> 
> 
> 
>
>  value="c:/apache/data/simple-cassandra/storage"/>
> 
> 
>  value="c:/apache/data/simple-cassandra/wal"/>
>  value="c:/apache/data/simple-cassandra/wal/archive"/>
>
> 
> 
>
> 
> 
>
>
>  class="org.apache.ignite.configuration.CacheConfiguration">
> 
> 
>  value="TRANSACTIONAL"/>
> 
> 
>
> 
> 
> 
>  type="java.lang.Class">com.procurant.model.IdKey
>  type="java.lang.Class">com.procurant.model.DimStore
> 
> 
>
> 
>  class="org.apache.ignite.cache.store.cassandra.CassandraCacheStoreFactory">
> 
>

Re: Issue while deploying the Ignite application in Wildfly Server

2020-09-28 Thread Ilya Kasnacheev

Hello!

Unfortunately, we have this bug, which was never fixed:
https://issues.apache.org/jira/browse/IGNITE-12483

You will have to apply solution from this SO answer:
https://stackoverflow.com/a/59453413/36498

Regards,
-- 
Ilya Kasnacheev


пн, 28 сент. 2020 г. в 17:08, DEEPTHI KOLLIPARA :

> Dear Ilya,
>
>jar is also added to
> the module.xml.
>
> I have added the below parameters to Java arguments.
>
> *--add-exports java.base/jdk.internal.misc=ALL-UNNAMED --add-exports
> java.base/sun.nio.ch =ALL-UNNAMED --add-exports
> java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED --add-exports
> jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED*
>
>
>
> Below error is thrown after adding the above parameter. Please suggest.
>
>
>
> *Failed to find empty constructor for class:
> org.apache.ignite.internal.processors.platform.websession.PlatformDotNetSessionLockResult*
>
> *org.apache.ignite.binary.BinaryObjectException: Failed to find empty
> constructor for class:
> org.apache.ignite.internal.processors.platform.websession.PlatformDotNetSessionLockResult*
>
> *at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.constructor(BinaryClassDescriptor.java:981)
> ~[ignite-core-2.7.0.jar:2.7.0]*
>
> *at
> org.apache.ignite.internal.binary.BinaryClassDescriptor.(BinaryClassDescriptor.java:267)
> ~[ignite-core-2.7.0.jar:2.7.0]*
>
> *at
> org.apache.ignite.internal.binary.BinaryContext.registerPredefinedType(BinaryContext.java:1063)
> ~[ignite-core-2.7.0.jar:2.7.0]*
>
> *at
> org.apache.ignite.internal.binary.BinaryContext.registerPredefinedType(BinaryContext.java:1048)
> ~[ignite-core-2.7.0.jar:2.7.0]*
>
> *at
> org.apache.ignite.internal.binary.BinaryContext.(BinaryContext.java:350)
> ~[ignite-core-2.7.0.jar:2.7.0]*
>
> *at
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.start(CacheObjectBinaryProcessorImpl.java:208)
> ~[ignite-core-2.7.0.jar:2.7.0]*
>
> *at
> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1700)
> ~[ignite-core-2.7.0.jar:2.7.0]*
>
> *at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1013)
> ~[ignite-core-2.7.0.jar:2.7.0]*
>
> *at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
> ~[ignite-core-2.7.0.jar:2.7.0]*
>
> *at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1730)
> ~[ignite-core-2.7.0.jar:2.7.0]*
>
> *at
> org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158)
> ~[ignite-core-2.7.0.jar:2.7.0]*
>
> *at
> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1076)
> ~[ignite-core-2.7.0.jar:2.7.0]*
>
> *at
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:962)
> ~[ignite-core-2.7.0.jar:2.7.0]*
>
> *at
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:861)
> ~[ignite-core-2.7.0.jar:2.7.0]*
>
> *at
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:731)
> ~[ignite-core-2.7.0.jar:2.7.0]*
>
> *at
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:700)
> ~[ignite-core-2.7.0.jar:2.7.0]*
>
> *at org.apache.ignite.Ignition.start(Ignition.java:348)
> ~[ignite-core-2.7.0.jar:2.7.0]*
>
>
>
>
>
>
>
> Sent from Mail  for
> Windows 10
>
>
>
> *From: *Ilya Kasnacheev 
> *Sent: *Monday, September 28, 2020 7:31 PM
> *To: *user@ignite.apache.org
> *Subject: *Re: Issue while deploying the Ignite application in Wildfly
> Server
>
>
> "External email. Open with Caution"
>
> Hello!
>
>
>
> You also need to add ignite-spring 2.7.0 dependency.
>
>
>
> **
>
>
>
> Regards,
>
> --
>
> Ilya Kasnacheev
>
>
>
>
>
> вс, 27 сент. 2020 г. в 15:17, DEEPTHI KOLLIPARA  >:
>
> Dear Team,
>
>
>
>   I am trying to deploy a web application with ignite 2.7 version on
> Wildfly server 20.0. Ignite client node will be started from the
> application.
>
>
>
>
>
> *Below error is thrown from when starting the node. Same war is deployed
> and worked successfully in Tomcat.*
>
> I have added the below entry to Wildfly modules. Anything is missed here?
>
>
>
> *Path of the file:*
>
> wildfly-20.0.0.Final/modules/system/layers/base/org/ignite/main
>
> **
>
> **
>
> **
>
> **
>
> **
>
> **
>
> **
>
> **
>
> **
>
> **
>
> **
>
>
>
> **
>
> **
>
>
>
> 2020-09-25 18:10:45 ERROR FactsLogger:104 - InputModel.crateTransaction :
> Could not initialize class org.apache.ignite.internal.util.IgniteUtils
>
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.ignite.internal.util.IgniteUtils
>
> at
> org.apache.ignite.inte

RE: Issue while deploying the Ignite application in Wildfly Server

2020-09-28 Thread DEEPTHI KOLLIPARA

Dear Ilya,
   jar is also added to the 
module.xml.
I have added the below parameters to Java arguments.
--add-exports java.base/jdk.internal.misc=ALL-UNNAMED --add-exports 
java.base/sun.nio.ch=ALL-UNNAMED --add-exports 
java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED --add-exports 
jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED

Below error is thrown after adding the above parameter. Please suggest.

Failed to find empty constructor for class: 
org.apache.ignite.internal.processors.platform.websession.PlatformDotNetSessionLockResult
org.apache.ignite.binary.BinaryObjectException: Failed to find empty 
constructor for class: 
org.apache.ignite.internal.processors.platform.websession.PlatformDotNetSessionLockResult
at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.constructor(BinaryClassDescriptor.java:981)
 ~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.(BinaryClassDescriptor.java:267)
 ~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.binary.BinaryContext.registerPredefinedType(BinaryContext.java:1063)
 ~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.binary.BinaryContext.registerPredefinedType(BinaryContext.java:1048)
 ~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.binary.BinaryContext.(BinaryContext.java:350) 
~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.start(CacheObjectBinaryProcessorImpl.java:208)
 ~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1700) 
~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1013) 
~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
 ~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1730)
 ~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158) 
~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1076) 
~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:962) 
~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:861) 
~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:731) 
~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:700) 
~[ignite-core-2.7.0.jar:2.7.0]
at org.apache.ignite.Ignition.start(Ignition.java:348) 
~[ignite-core-2.7.0.jar:2.7.0]



Sent from Mail for Windows 10

From: Ilya Kasnacheev
Sent: Monday, September 28, 2020 7:31 PM
To: user@ignite.apache.org
Subject: Re: Issue while deploying the Ignite application in Wildfly Server

"External email. Open with Caution"
Hello!

You also need to add ignite-spring 2.7.0 dependency.



Regards,
--
Ilya Kasnacheev


вс, 27 сент. 2020 г. в 15:17, DEEPTHI KOLLIPARA 
mailto:deepthi.kollip...@tcs.com>>:
Dear Team,

  I am trying to deploy a web application with ignite 2.7 version on Wildfly 
server 20.0. Ignite client node will be started from the application.


Below error is thrown from when starting the node. Same war is deployed and 
worked successfully in Tomcat.
I have added the below entry to Wildfly modules. Anything is missed here?

Path of the file:
wildfly-20.0.0.Final/modules/system/layers/base/org/ignite/main















2020-09-25 18:10:45 ERROR FactsLogger:104 - InputModel.crateTransaction : Could 
not initialize class org.apache.ignite.internal.util.IgniteUtils
java.lang.NoClassDefFoundError: Could not initialize class 
org.apache.ignite.internal.util.IgniteUtils
at 
org.apache.ignite.internal.IgnitionEx.(IgnitionEx.java:209) 
~[ignite-core-2.7.0.jar:2.7.0]
at org.apache.ignite.Ignition.start(Ignition.java:348) 
~[ignite-core-2.7.0.jar:2.7.0]
at 
com.cmc.facts.grid.matcher.MatcherGridInvoker.loadNode(MatcherGridInvoker.java:160)
 ~[Matcher-2.0-RC4.jar:?]
at 
com.cmc.facts.grid.matcher.MatcherGridInvoker.getIgnite(MatcherGridInvoker.java:96)
 ~[Matcher-2.0-RC4.jar:?]
at 
com.cmc.facts.grid.matcher.MatcherGridInvoker.invokeTPTPCSGrid(MatcherGridInvoker.java:263)
 ~[Matcher-2.0-RC4.jar:?]
at 
com.cmc.facts.model.InputModel.createTr

Re: Issue while deploying the Ignite application in Wildfly Server

2020-09-28 Thread Ilya Kasnacheev

Hello!

You also need to add ignite-spring 2.7.0 dependency.

**

Regards,
-- 
Ilya Kasnacheev


вс, 27 сент. 2020 г. в 15:17, DEEPTHI KOLLIPARA :

> Dear Team,
>
>
>
>   I am trying to deploy a web application with ignite 2.7 version on
> Wildfly server 20.0. Ignite client node will be started from the
> application.
>
>
>
>
>
> *Below error is thrown from when starting the node. Same war is deployed
> and worked successfully in Tomcat.*
>
> I have added the below entry to Wildfly modules. Anything is missed here?
>
>
>
> *Path of the file:*
>
> wildfly-20.0.0.Final/modules/system/layers/base/org/ignite/main
>
> **
>
> **
>
> **
>
> **
>
> **
>
> **
>
> **
>
> **
>
> **
>
> **
>
> **
>
>
>
> **
>
> **
>
>
>
> 2020-09-25 18:10:45 ERROR FactsLogger:104 - InputModel.crateTransaction :
> Could not initialize class org.apache.ignite.internal.util.IgniteUtils
>
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.ignite.internal.util.IgniteUtils
>
> at
> org.apache.ignite.internal.IgnitionEx.(IgnitionEx.java:209)
> ~[ignite-core-2.7.0.jar:2.7.0]
>
> at org.apache.ignite.Ignition.start(Ignition.java:348)
> ~[ignite-core-2.7.0.jar:2.7.0]
>
> at
> com.cmc.facts.grid.matcher.MatcherGridInvoker.loadNode(MatcherGridInvoker.java:160)
> ~[Matcher-2.0-RC4.jar:?]
>
> at
> com.cmc.facts.grid.matcher.MatcherGridInvoker.getIgnite(MatcherGridInvoker.java:96)
> ~[Matcher-2.0-RC4.jar:?]
>
> at
> com.cmc.facts.grid.matcher.MatcherGridInvoker.invokeTPTPCSGrid(MatcherGridInvoker.java:263)
> ~[Matcher-2.0-RC4.jar:?]
>
> at
> com.cmc.facts.model.InputModel.createTransaction(InputModel.java:2349)
> ~[classes:?]
>
> at
> com.cmc.facts.model.InputModel$$FastClassBySpringCGLIB$$d946f9ed.invoke()
> ~[classes:?]
>
> at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
> ~[spring-core-5.1.9.RELEASE.jar:5.1.9.RELEASE]
>
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:749)
> ~[spring-aop-5.1.9.RELEASE.jar:5.1.9.RELEASE]
>
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
> ~[spring-aop-5.1.9.RELEASE.jar:5.1.9.RELEASE]
>
> at
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:88)
> ~[spring-aop-5.1.9.RELEASE.jar:5.1.9.RELEASE]
>
> at
> com.cmc.facts.aop.LoggingInterceptor.logModels(LoggingInterceptor.java:19)
> ~[classes:?]
>
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
>
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[?:?]
>
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:?]
>
> at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
>
> at
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:644)
> ~[spring-aop-5.1.9.RELEASE.jar:5.1.9.RELEASE]
>
> at
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:633)
> ~[spring-aop-5.1.9.RELEASE.jar:5.1.9.RELEASE]
>
> at
> org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:70)
> ~[spring-aop-5.1.9.RELEASE.jar:5.1.9.RELEASE]
>
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
> ~[spring-aop-5.1.9.RELEASE.jar:5.1.9.RELEASE]
>
> at
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:93)
> ~[spring-aop-5.1.9.RELEASE.jar:5.1.9.RELEASE]
>
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
> ~[spring-aop-5.1.9.RELEASE.jar:5.1.9.RELEASE]
>
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:688)
> ~[spring-aop-5.1.9.RELEASE.jar:5.1.9.RELEASE]
>
> at
> com.cmc.facts.model.InputModel$$EnhancerBySpringCGLIB$$29adf337.createTransaction()
> ~[classes:?]
>
> at
> com.cmc.facts.nist.NistReaderModel.preprossingOfNistFile(NistReaderModel.java:326)
> ~[classes:?]
>
> at
> com.cmc.facts.civilian.FactsServiceUtilCivilian.processOne2OneMatch(FactsServiceUtilCivilian.java:912)
> ~[classes:?]
>
> at
> com.cmc.facts.civilian.FactsServiceUtilCivilian.processRequest(FactsServiceUtilCivilian.java:207)
> ~[classes:?]
>
>

Re: [External]Re: how to achieve timeout for get/put/remove operations

2020-09-28 Thread Ilya Kasnacheev

Hello!

You can use it if you're using thin client, sure. I was writing on the
thick client operation.

Regards,
-- 
Ilya Kasnacheev


пн, 28 сент. 2020 г. в 16:07, AravindJP :

> We are also facing a similar issue where complete cluster behaves like
> frozen
> with cache get time > 200 ms , unable to figure out the root cause . I was
> expecting that ClientConfiguration.setTimeout() will work for get read
> timeout
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

RE: [External]Re: how to achieve timeout for get/put/remove operations

2020-09-28 Thread AravindJP

We are also facing a similar issue where complete cluster behaves like frozen
with cache get time > 200 ms , unable to figure out the root cause . I was
expecting that ClientConfiguration.setTimeout() will work for get read
timeout



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Issue while starting the Ignite node in wildfly server

2020-09-28 Thread BEELA GAYATRI

Dear Team,

I am trying to deploy the web application on wildfly server. Ignite client will 
be started from the application.
Ignite Version: 2.7
Wildfly Server version : 20

wildfly-20.0.0.Final/modules/system/layers/base/org/wildfly/extension/io/main

Added Ignite  jars  in
wildfly-20.0.0.Final/modules/system/layers/base/org/apache/ignite/main

We are getting below error . Please suggest
Failed to find empty constructor for class: 
org.apache.ignite.internal.processors.platform.websession.PlatformDotNetSessionLockResult
org.apache.ignite.binary.BinaryObjectException: Failed to find empty 
constructor for class: 
org.apache.ignite.internal.processors.platform.websession.PlatformDotNetSessionLockResult
at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.constructor(BinaryClassDescriptor.java:981)
 ~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.(BinaryClassDescriptor.java:267)
 ~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.binary.BinaryContext.registerPredefinedType(BinaryContext.java:1063)
 ~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.binary.BinaryContext.registerPredefinedType(BinaryContext.java:1048)
 ~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.binary.BinaryContext.(BinaryContext.java:350) 
~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.start(CacheObjectBinaryProcessorImpl.java:208)
 ~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1700) 
~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1013) 
~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2038)
 ~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1730)
 ~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158) 
~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1076) 
~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:962) 
~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:861) 
~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:731) 
~[ignite-core-2.7.0.jar:2.7.0]
at 
org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:700) 
~[ignite-core-2.7.0.jar:2.7.0]
at org.apache.ignite.Ignition.start(Ignition.java:348) 
~[ignite-core-2.7.0.jar:2.7.0]




Sent from Mail for Windows 10




From: DEEPTHI KOLLIPARA
Sent: Sunday, September 27, 2020 5:56 PM
To: user@ignite.apache.org
Subject: Issue while starting the Ignite node in wildfly server

"External email. Open with Caution"
Dear Team,

   I am trying to deploy the web application on wildfly server. Ignite client 
will be started from the application.
Ignite Version: 2.7
Wildfly Server version : 20

Added ignite related jars to Wildfly modules in the below path.
wildfly-20.0.0.Final/modules/system/layers/base/org/ignite/main









   







Below error is thrown at the time of node starts. Same code works fine with 
Tomcat.

Any help is highly appreciated.

2020-09-25 18:10:45 ERROR FactsLogger:104 - InputModel.crateTransaction : Could 
not initialize class org.apache.ignite.internal.util.IgniteUtils
java.lang.NoClassDefFoundError: Could not initialize class 
org.apache.ignite.internal.util.IgniteUtils
at 
org.apache.ignite.internal.IgnitionEx.(IgnitionEx.java:209) 
~[ignite-core-2.7.0.jar:2.7.0]
at org.apache.ignite.Ignition.start(Ignition.java:348) 
~[ignite-core-2.7.0.jar:2.7.0]
at 
com.cmc.facts.grid.matcher.MatcherGridInvoker.loadNode(MatcherGridInvoker.java:160)
 ~[Matcher-2.0-RC4.jar:?]
at 
com.cmc.facts.grid.matcher.MatcherGridInvoker.getIgnite(MatcherGridInvoker.java:96)
 ~[Matcher-2.0-RC4.jar:?]
at 
com.cmc.facts.grid.matcher.MatcherGridInvoker.invokeTPTPCSGrid(MatcherGridInvoker.java:263)
 ~[Matcher-2.0-RC4.jar:?]
at 
com.cmc.facts.model.InputModel.createTransaction(InputModel.java:2349) 
~[classes:?]
at 
com.cmc.facts.model.InputModel$$FastClassBySpringCGLIB$$d946f9ed.invoke()
 ~[classes:?]
at 
org.springframework.cglib.proxy.MethodProxy.invoke(Meth

Re: High number of Exception Unexpected response ID with setTimeout

2020-09-28 Thread AravindJP

Thank you stepan for your reply , problem is the parent thread calling ignite
cache get has a timeout of 120 ms , hence we allow a max of 100 ms for every
cache read . We are seeing that during non peak time , 80% of cache read is
< 20 ms only . But during peak load application is crashing with some
threads going beyond 400 to 500 ms . That's the reason why we had to limit
timeout to 50 . But why such an exception occurs ? Why such an exception
occurs from Ignite side ?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: High number of Exception Unexpected response ID with setTimeout

2020-09-28 Thread Stephen Darlington

50ms isn’t very long. I’d recommend at least a few seconds, maybe 5000 rather 
than 50.

Regards,
Stephen

> On 28 Sep 2020, at 10:01, AravindJP  wrote:
> 
> We are seeing high number of exceptions after setting setTimeout() in 
> ClientConfiguration 
> any idea what's the reason for this ?
> 
> Exception: Unexpected response ID [3630521808404506928], [5259] was expected 
> at 
> org.apache.ignite.internal.client.thin.TcpClientChannel.receive(TcpClientChannel.java:160)
>  
> at 
> org.apache.ignite.internal.client.thin.ReliableChannel.service(ReliableChannel.java:126)
> at 
> org.apache.ignite.internal.client.thin.TcpClientCache.getAll(TcpClientCache.java:165)
>  
> We set timeout as mentioned below
> ClientConfiguration cfg = new ClientConfiguration().setAddresses(IP:PORT); 
> cfg.setTimeout(50); 
> IgniteClient ignite = Ignition.startClient(cfg); 
> Sent from the Apache Ignite Users mailing list archive 
>  at Nabble.com.

High number of Exception Unexpected response ID with setTimeout

2020-09-28 Thread AravindJP

We are seeing high number of exceptions after setting setTimeout() in
ClientConfiguration 
 any idea what's the reason for this ?
Exception: Unexpected response ID [3630521808404506928], [5259] was expected
at
org.apache.ignite.internal.client.thin.TcpClientChannel.receive(TcpClientChannel.java:160)
  
at
org.apache.ignite.internal.client.thin.ReliableChannel.service(ReliableChannel.java:126)
   at
org.apache.ignite.internal.client.thin.TcpClientCache.getAll(TcpClientCache.java:165)
   
We set timeout as mentioned below
ClientConfiguration cfg = new ClientConfiguration().setAddresses(IP:PORT); 
cfg.setTimeout(50); 
IgniteClient ignite =   Ignition.startClient(cfg);



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Issue while deploying the Ignite application in Wildfly Server

Re: Binary memory restoration

Binary memory restoration

Re: High number of Exception Unexpected response ID with setTimeout

Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

Re: Issue while deploying the Ignite application in Wildfly Server

RE: Issue while deploying the Ignite application in Wildfly Server

Re: Issue while deploying the Ignite application in Wildfly Server

Re: [External]Re: how to achieve timeout for get/put/remove operations

RE: [External]Re: how to achieve timeout for get/put/remove operations

RE: Issue while starting the Ignite node in wildfly server

Re: High number of Exception Unexpected response ID with setTimeout

Re: High number of Exception Unexpected response ID with setTimeout

High number of Exception Unexpected response ID with setTimeout

14 matches

Site Navigation

Mail list logo

Footer information