from:"Rishi Yagnik"

Re: How to configure ignite-jcl and Ignite-slf4j logger

2017-09-05 Thread Rishi Yagnik

Just sending it for your reference -

Copied ignite-log* library in ignite lib folder
Renamed ignite-log4j to log4j.xml for log4j configuration
Renamed ignite-log4j2 to log4j2.xml for log4j configuration
Copied respective log file config in config location so that it can be
picked up during start up of ignite























On Tue, Sep 5, 2017 at 5:52 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Prachi,
>
> Parameter of Log4JLogger constructor is not the path to XML file, it's just
> a name of root logger. Ignite logger configuration should look like this:
>
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
> ignite-log4j.xml file should be renamed to log4j.xml and moved to root of
> classpath (e.g. in 'resources' folder). This way it will be picked up
> automatically.
>
> -Val
>
> On Mon, Sep 4, 2017 at 11:01 PM, Prachi Garg <pg...@gridgain.com> wrote:
>
> > Valentin, Nikolai,
> >
> > I have published my example on github -
> > https://github.com/pgarg/myIgniteExamples
> >
> > On Mon, Sep 4, 2017 at 7:57 PM, Rishi Yagnik <rishiyag...@gmail.com>
> > wrote:
> >
> > > I have configured log4j, log4j-2 in our environment, can share
> additional
> > > details here if you need it.
> > >
> > > On Mon, Sep 4, 2017 at 11:54 AM, Nikolai Tikhonov <
> ntikho...@apache.org>
> > > wrote:
> > >
> > >> Prachi,
> > >>
> > >> I've published on github example with configured JCL logger. Please,
> > have
> > >> a
> > >> look: https://github.com/TikhonovNikolay/jcl-ignite-example
> > >>
> > >> On Sat, Sep 2, 2017 at 12:36 AM, Prachi Garg <pg...@gridgain.com>
> > wrote:
> > >>
> > >> > Yes, I tried using it, but strangely this is the output I get when
> use
> > >> > -DIGNITE_QUIET=false
> > >> > ( I set this property in Idea ->Run -> Edit Configurations -> VM
> > >> options)
> > >> >
> > >> > log4j:WARN No appenders could be found for logger
> > >> > (org.apache.ignite.internal.util.typedef.G).
> > >> > log4j:WARN Please initialize the log4j system properly.
> > >> > log4j:WARN See http://logging.apache.org/
> log4j/1.2/faq.html#noconfig
> > >> for
> > >> > more info.
> > >> > Sep 01, 2017 2:33:07 PM java.util.logging.LogManager$RootLogger log
> > >> > SEVERE: Failed to resolve default logging config file:
> > >> > config/java.util.logging.properties
> > >> > class org.apache.ignite.internal.GridLoggerProxy
> > >> >
> > >> > Process finished with exit code 0
> > >> >
> > >> >
> > >> > On Fri, Sep 1, 2017 at 2:30 PM, Valentin Kulichenko <
> > >> > valentin.kuliche...@gmail.com> wrote:
> > >> >
> > >> > > Prachi,
> > >> > >
> > >> > > It looks like you're running in quiet mode. Did you try to set
> > >> > > -DIGNITE_QUIET=false
> > >> > > system property?
> > >> > >
> > >> > > -Val
> > >> > >
> > >> > > On Fri, Sep 1, 2017 at 10:43 AM, Prachi Garg <pg...@gridgain.com>
> > >> wrote:
> > >> > >
> > >> > > > Nikolai,
> > >> > > >
> > >> > > > I have specified 'gridlogger' property in 'IgniteConfiguration',
> > but
> > >> > > looks
> > >> > > > like it does not get instantiated.
> > >> > > >
> > >> > > >  > >> > > > class="org.apache.ignite.configuration.IgniteConfiguration">
> > >> > > >
> > >> > > > 
> > >> > > > 
> > >> > > > 
> > >> > > > 
> > >> > > >  > >> > > > value="/Users/prachig/myexamples/config/ignite-log4j.xml"/>
> > >> > > > 
> > >> > > > 
> > >> > > > 
> > >> > > > 
> > >> > > >
> > >> > > > 
> > >> > > > ...
> > >> > > >
&

Re: How to configure ignite-jcl and Ignite-slf4j logger

2017-09-04 Thread Rishi Yagnik

; Users/prachig/.m2/repository/org/apache/ignite/ignite-core/
> > > > > > 2.1.0/ignite-core-2.1.0.jar:/Users/prachig/.m2/repository/
> > > > > > javax/cache/cache-api/1.0.0/cache-api-1.0.0.jar:/Users/
> > > > > > prachig/.m2/repository/org/jetbrains/annotations/13.0/
> > > > > > annotations-13.0.jar:/Users/prachig/.m2/repository/org/
> > > > > > gridgain/ignite-shmem/1.0.0/ignite-shmem-1.0.0.jar:/Users/
> > > > > > prachig/.m2/repository/org/apache/ignite/ignite-spring/2.
> > > > > > 1.0/ignite-spring-2.1.0.jar:/Users/prachig/.m2/repository/
> > > > > > org/apache/ignite/ignite-indexing/2.1.0/ignite-
> > > > > indexing-2.1.0.jar:/Users/
> > > > > > prachig/.m2/repository/commons-codec/commons-codec/1.
> > > > > > 6/commons-codec-1.6.jar:/Users/prachig/.m2/repository/
> > > > > > org/apache/lucene/lucene-core/5.5.2/lucene-core-5.5.2.jar:/
> > > > > > Users/prachig/.m2/repository/org/apache/lucene/lucene-
> > > > > > analyzers-common/5.5.2/lucene-analyzers-common-5.5.2.jar:/
> > > > > > Users/prachig/.m2/repository/org/apache/lucene/lucene-
> > > > > > queryparser/5.5.2/lucene-queryparser-5.5.2.jar:/Users/
> > > > > > prachig/.m2/repository/org/apache/lucene/lucene-queries/
> > > > > > 5.5.2/lucene-queries-5.5.2.jar:/Users/prachig/.m2/
> > > > > > repository/org/apache/lucene/lucene-sandbox/5.5.2/lucene-
> > > > > > sandbox-5.5.2.jar:/Users/prachig/.m2/repository/com/
> > > > > > h2database/h2/1.4.195/h2-1.4.195.jar:/Users/prachig/.m2/
> > > > repository/org/
> > > > > > springframework/spring-core/4.3.7.RELEASE/spring-core-4.3.7.
> > > > > > RELEASE.jar:/Users/prachig/.m2/repository/commons-logging/
> > > > > > commons-logging/1.1.1/commons-logging-1.1.1.jar:/Users/
> > > > > > prachig/.m2/repository/org/springframework/spring-aop/4.
> > > > > > 3.7.RELEASE/spring-aop-4.3.7.RELEASE.jar:/Users/prachig/.
> > > > > > m2/repository/org/springframework/spring-beans/
> > > > > > 4.3.7.RELEASE/spring-beans-4.3.7.RELEASE.jar:/Users/
> > > > > > prachig/.m2/repository/org/springframework/spring-
> > > > > > context/4.3.7.RELEASE/spring-context-4.3.7.RELEASE.jar:/
> > > > > > Users/prachig/.m2/repository/org/springframework/spring-
> > > > > > expression/4.3.7.RELEASE/spring-expression-4.3.7.
> > > > > > RELEASE.jar:/Users/prachig/.m2/repository/org/
> > > > > > springframework/spring-tx/4.3.7.RELEASE/spring-tx-4.3.7.
> > > > > > RELEASE.jar:/Users/prachig/.m2/repository/org/
> > > > > > springframework/spring-jdbc/4.3.7.RELEASE/spring-jdbc-4.3.7.
> > > > > > RELEASE.jar:/Users/prachig/.m2/repository/org/apache/
> > > > > > ignite/ignite-log4j2/2.1.0/ignite-log4j2-2.1.0.jar:/
> > > > > > Users/prachig/.m2/repository/org/apache/logging/log4j/
> > > > > > log4j-api/2.8.1/log4j-api-2.8.1.jar:/Users/prachig/.m2/
> > > > > > repository/org/apache/logging/log4j/log4j-core/2.8.1/log4j-
> > > > > > core-2.8.1.jar:/Users/prachig/.m2/repository/org/apache/
> > > > > > ignite/ignite-log4j/2.1.0/ignite-log4j-2.1.0.jar:/Users/
> > > > > > prachig/.m2/repository/log4j/log4j/1.2.17/log4j-1.2.17.jar:
> > > > > > /Users/prachig/.m2/repository/org/apache/ignite/ignite-jcl/
> > > > > > 2.1.0/ignite-jcl-2.1.0.jar:/Users/prachig/.m2/repository/
> > > > > > org/apache/ignite/ignite-slf4j/2.1.0/ignite-slf4j-2.1.
> > > > > > 0.jar:/Users/prachig/.m2/repository/org/slf4j/slf4j-
> > > > > > api/1.7.7/slf4j-api-1.7.7.jar:/Users/prachig/.m2/repository/
> > > > > > mysql/mysql-connector-java/5.1.6/mysql-connector-java-5.1.
> > > > > > 6.jar:/Users/prachig/.m2/repository/net/spy/spymemcached/2.11.7/
> > > > > > spymemcached-2.11.7.jar:/Applications/IntelliJ
> > > > > > > IDEA CE.app/Contents/lib/idea_rt.jar"
> > > > > > > com.intellij.rt.execution.application.AppMain
> > > > > > > ignite.myexamples.LoggerExample
> > > > > > > log4j:WARN No appenders could be found for logger
> > > > > > > (org.apache.ignite.internal.util.typedef.G).
> > > > > > > log4j:WARN Please initialize the log4j system properly.
> > > > > > > log4j:WARN See http://logging.apache.org/
> > > log4j/1.2/faq.html#noconfig
> > > > <
> > > > > > http://logging.apache.org/log4j/1.2/faq.html#noconfig>
> > > > > > > for more info.
> > > > > > > [15:59:49]__  
> > > > > > > [15:59:49]   /  _/ ___/ |/ /  _/_  __/ __/
> > > > > > > [15:59:49]  _/ // (7 7// /  / / / _/
> > > > > > > [15:59:49] /___/\___/_/|_/___/ /_/ /___/
> > > > > > > [15:59:49]
> > > > > > > [15:59:49] ver. 2.1.0#20170720-sha1:a6ca5c8a
> > > > > > > [15:59:49] 2017 Copyright(C) Apache Software Foundation
> > > > > > > [15:59:49]
> > > > > > > [15:59:49] Ignite documentation: http://ignite.apache.org <
> > > > > > http://ignite.apache.org/>
> > > > > > > [15:59:49]
> > > > > > > [15:59:49] Quiet mode.
> > > > > > > [15:59:49]   ^-- To see **FULL** console log here add
> > > > > > > -DIGNITE_QUIET=false or "-v" to ignite.{sh|bat}
> > > > > > > [15:59:49]
> > > > > > > [15:59:49] OS: Mac OS X 10.12.1 x86_64
> > > > > > > [15:59:49] VM information: Java(TM) SE Runtime Environment
> > > > > > > 1.8.0_74-b02 Oracle Corporation Java HotSpot(TM) 64-Bit Server
> VM
> > > > > > > 25.74-b02
> > > > > > > [15:59:49] Initial heap size is 256MB (should be no less than
> > > 512MB,
> > > > > > > use -Xms512m -Xmx512m).
> > > > > > > [15:59:49] Configured plugins:
> > > > > > > [15:59:49]   ^-- None
> > > > > > > [15:59:49]
> > > > > > > [15:59:49] Message queue limit is set to 0 which may lead to
> > > > potential
> > > > > > > OOMEs when running cache operations in FULL_ASYNC or
> PRIMARY_SYNC
> > > > > > > modes due to message queues growth on sender and receiver
> sides.
> > > > > > > [15:59:49] Security status [authentication=off, tls/ssl=off]
> > > > > > > Aug 31, 2017 3:59:49 PM java.util.logging.LogManager$
> RootLogger
> > > log
> > > > > > > SEVERE: Failed to resolve default logging config file:
> > > > > > > config/java.util.logging.properties
> > > > > > > [15:59:50] Performance suggestions for grid  (fix if possible)
> > > > > > > [15:59:50] To disable, set -DIGNITE_PERFORMANCE_
> > > > > > SUGGESTIONS_DISABLED=true
> > > > > > > [15:59:50]   ^-- Enable G1 Garbage Collector (add
> '-XX:+UseG1GC'
> > to
> > > > JVM
> > > > > > options)
> > > > > > > [15:59:50]   ^-- Specify JVM heap max size (add
> > > > > > > '-Xmx[g|G|m|M|k|K]' to JVM options)
> > > > > > > [15:59:50]   ^-- Set max direct memory size if getting 'OOME:
> > > Direct
> > > > > > > buffer memory' (add '-XX:MaxDirectMemorySize=<
> > size>[g|G|m|M|k|K]'
> > > to
> > > > > > > JVM options)
> > > > > > > [15:59:50]   ^-- Disable processing of calls to System.gc()
> (add
> > > > > > > '-XX:+DisableExplicitGC' to JVM options)
> > > > > > > [15:59:50] Refer to this page for more performance suggestions:
> > > > > > > https://apacheignite.readme.io/docs/jvm-and-system-tuning <
> > > > > > https://apacheignite.readme.io/docs/jvm-and-system-tuning>
> > > > > > > [15:59:50]
> > > > > > > [15:59:50] To start Console Management & Monitoring run
> > > > > > ignitevisorcmd.{sh|bat}
> > > > > > > [15:59:50]
> > > > > > > [15:59:50] Ignite node started OK (id=fa20d03b)
> > > > > > > [15:59:50] Topology snapshot [ver=1, servers=1, clients=0,
> > CPUs=4,
> > > > > > heap=3.6GB]
> > > > > > > class org.apache.ignite.internal.GridLoggerProxy
> > > > > > > [15:59:50] Ignite node stopped OK [uptime=00:00:00:085]
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > How can I make it work?
> > > > > > >
> > > > > > > -P
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>



-- 
Rishi Yagnik

Re: usage analytics

2017-07-05 Thread Rishi Yagnik

With such statistics collected by Ignite , we won't ever accept ignite in our 
environment.

However, turning on and off stats collection capabilities would be helpful here 
if the feature is accepted further for implementation.

Take Care,
Rishi

> On Jul 5, 2017, at 8:15 PM, Roman Shtykh  wrote:
> 
> NIkita,
> 
> While this will help improve Ignite, it will prevent its adoption by many 
> projects -- sending and retaining IP adresses, OS versions, etc. raises tons 
> of questions when considering to use Ignite. Even if it can be opted out.
> -- Roman
> 
> 
>On Thursday, July 6, 2017 5:38 AM, Nikita Ivanov  
> wrote:
> 
> 
> Igniters,
> I would like to kick off the discussion on the idea of collecting Ignite
> usage statistics. The basic idea behind this is to better understand
> general and anonymous Ignite usage information to better calibrate
> community efforts in developing new features, improving existing ones,
> delivering better documentation - and in every other way to make our
> project a better software solution.
> 
> Although such instrumentation is standard practice in commercially
> developed software, for an ASF project this could be a sensitive issue.
> Therefore I would like to initiate a full community discussion on how best
> to implement such practice for the benefit of project while ensuring the
> privacy protection of Ignite users.
> 
> To ignite (pun intended) the discussion I'll outline below some of the
> basic thoughts that I have on this subject. They are here only to give an
> idea of what such instrumentation may potentially look like so that we can
> discuss the merits of this idea in a tangible context.
> 
> Overview
> -
> Upon start and every hour thereafter each Ignite node will collect, encrypt
> and send usage statistics over HTTPS to the ASF-hosted server. That server
> will accept such HTTPS packets, decrypt them and store them in a
> time-series DB. A web interface will be provided to view the usage
> information.
> 
> Opt-In or Opt-out
> -
> Opt-out. Ignite website will offer simple instructions (system property) on
> how to disable this instrumentation.
> 
> Code, Infra, Access
> ---
> Ignite instrumentation will be part of the Ignite code base. The collection
> server will be a separate module in the Ignite code base (released
> separately from Ignite). The collection server will be hosted by ASF Infra.
> 
> Usage statistics will be publicly accessible by anyone in the community.
> 
> Private, Personal Data
> --
> No private or personal data will ever be transferred. No emails, usernames,
> company names, grid names, etc.
> 
> Data Retention
> 
> All data will be retained for 1 year and deleted permanently thereafter.
> 
> Usage Data
> 
> The following data will be collected in each packet sent to the collection
> server:
> - GRID_SIZE (to correspond our testing environment with the more frequent
> cluster sizes)
> - IP_ADDR (for general geo-tracking as well as to know what documentation
> language should be a priority)
> - SES_ID (to track continues uptime vs. re-starts)
> - USERNAME_TYPE (privilege username vs. standard, to track production vs.
> dev/testing usage; note - this is not an actual username)
> - OS_NAME
> - OS_VER
> - OS_ARCH
> - JAVA_VER
> - JAVA_VENDOR
> - COMP_SQL (whether or not this feature was used)
> - COMP_COMPUTE (whether or not this feature was used)
> - COMP_DATAGRID (whether or not this feature was used)
> - COMP_STREAMING (whether or not this feature was used)
> - COMP_IGFS (whether or not this feature was used)
> - COMP_SERVICE (whether or not this feature was used)
> - COMP_PERSISTENCE (whether or not this feature was used)
> 
> Please let's discuss this idea. Everyone's comments and suggestions are
> *extremely* welcome.
> 
> Thanks,
> Nikita Ivanov.
> 
>

Re: Session Replication Update on spring boot platform

2017-05-23 Thread Rishi Yagnik

Hello Val,

we are in the middle of the sprint so cant hijack any of our environment
but would keep you posted with the timelines.

Thank you for all your help,
Rishi

On Tue, May 23, 2017 at 2:37 AM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Hi Rishi,
>
> It was working for me in cluster environment after the fix [1] we
> discussed in previous thread [2]. The fix was included in Ignite 2.0.
>
> Can you please reattach the latest version of your app based on Ignite 2.0
> and give a detailed step by step instruction on how to reproduce the issue
> you're having?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-4948
> [2] http://apache-ignite-developers.2346864.n4.nabble.
> com/IGNITE-2741-spring-session-design-td14560.html
>
> -Val
>
> On Mon, May 22, 2017 at 8:35 PM, Rishi Yagnik <rishiyag...@gmail.com>
> wrote:
>
>> Hello Val,
>>
>> As I discussed earlier, the problem arises in the cluster environment.
>>
>> we have 2 SB staleless instance backed by Ignite data store.
>>
>> The local environment is working fine and I am able to see the user
>> sessions are being stored correctly.
>>
>> I could not make session replication working with Ignite 2.0 in cluster
>> environment so my fixes are of no use.
>>
>> IMO,The web filter approach is very intrusive approach with spring
>> security and that is why I thought we need to come up with the solution
>> which sits on top of spring security.
>>
>> The possible solution could be spring session.
>>
>> The example which I posted can be tested on cluster as well. Would Ignite
>> team try out the clustering ?
>>
>> Looking for your inputs / suggestions on the issue.
>>
>> Thank you for all your help,
>> Rishi
>>
>>
>>
>>
>> On Mon, May 22, 2017 at 1:02 PM, Valentin Kulichenko <
>> valentin.kuliche...@gmail.com> wrote:
>>
>>> Hi Rishi,
>>>
>>> I'm not sure I understand what the issue is. Can you elaborate a bit
>>> more and provide exact examples of what is not working? What code tweaks
>>> are required and how critical are they? Also I recall that your example was
>>> working fine after the latest fixes in 1.9 (if I'm not mistaken). Did you
>>> make any changes after that?
>>>
>>> -Val
>>>
>>> On Fri, May 19, 2017 at 11:34 PM, Rishi Yagnik <rishiyag...@gmail.com>
>>> wrote:
>>>
>>>> Hello Dmitriy,
>>>>
>>>> Thank you for the response, I would await for Val's feedback.
>>>>
>>>> I would like to discuss the possible approach for implementation here,
>>>> and
>>>> it could be one of this -
>>>>
>>>> https://issues.apache.org/jira/browse/IGNITE-2741
>>>>
>>>> Hope we all come on to conclusion here.
>>>>
>>>> Thanks,
>>>>
>>>> On Fri, May 19, 2017 at 3:57 PM, Dmitriy Setrakyan <
>>>> dsetrak...@apache.org>
>>>> wrote:
>>>>
>>>> > Hi Rishi,
>>>> >
>>>> > I think the best way is to file a ticket in Ignite Jira with your
>>>> > findings. This ticket does not seem tremendously difficult, so
>>>> hopefully
>>>> > someone from the community will pick it up. All we need to do is to
>>>> take
>>>> > our existing Web Session Clustering [1][2] code and port it to work
>>>> with
>>>> > Spring Boot.
>>>> >
>>>> > BTW, feel free to contribute it yourself if you have time.
>>>> >
>>>> > [1] https://ignite.apache.org/use-cases/caching/web-session-
>>>> > clustering.html
>>>> > [2] https://apacheignite-mix.readme.io/docs/web-session-clustering
>>>> >
>>>> > D.
>>>> >
>>>> > On Fri, May 19, 2017 at 11:43 AM, Rishi Yagnik <rishiyag...@gmail.com
>>>> >
>>>> > wrote:
>>>> >
>>>> >> Hello Val,
>>>> >>
>>>> >> I tested out the session replication on spring boot cluster and here
>>>> is
>>>> >> the
>>>> >> result.
>>>> >>
>>>> >> My finding were as follows with Ignite 2.0 on session replication
>>>> and hope
>>>> >> that helps the team –
>>>> >>
>>>> >>- Spring Security Filters requires context to be set with
>&g

Re: Session Replication Update on spring boot platform

2017-05-22 Thread Rishi Yagnik

Hello Val,

As I discussed earlier, the problem arises in the cluster environment.

we have 2 SB staleless instance backed by Ignite data store.

The local environment is working fine and I am able to see the user
sessions are being stored correctly.

I could not make session replication working with Ignite 2.0 in cluster
environment so my fixes are of no use.

IMO,The web filter approach is very intrusive approach with spring security
and that is why I thought we need to come up with the solution which sits
on top of spring security.

The possible solution could be spring session.

The example which I posted can be tested on cluster as well. Would Ignite
team try out the clustering ?

Looking for your inputs / suggestions on the issue.

Thank you for all your help,
Rishi




On Mon, May 22, 2017 at 1:02 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Hi Rishi,
>
> I'm not sure I understand what the issue is. Can you elaborate a bit more
> and provide exact examples of what is not working? What code tweaks are
> required and how critical are they? Also I recall that your example was
> working fine after the latest fixes in 1.9 (if I'm not mistaken). Did you
> make any changes after that?
>
> -Val
>
> On Fri, May 19, 2017 at 11:34 PM, Rishi Yagnik <rishiyag...@gmail.com>
> wrote:
>
>> Hello Dmitriy,
>>
>> Thank you for the response, I would await for Val's feedback.
>>
>> I would like to discuss the possible approach for implementation here, and
>> it could be one of this -
>>
>> https://issues.apache.org/jira/browse/IGNITE-2741
>>
>> Hope we all come on to conclusion here.
>>
>> Thanks,
>>
>> On Fri, May 19, 2017 at 3:57 PM, Dmitriy Setrakyan <dsetrak...@apache.org
>> >
>> wrote:
>>
>> > Hi Rishi,
>> >
>> > I think the best way is to file a ticket in Ignite Jira with your
>> > findings. This ticket does not seem tremendously difficult, so hopefully
>> > someone from the community will pick it up. All we need to do is to take
>> > our existing Web Session Clustering [1][2] code and port it to work with
>> > Spring Boot.
>> >
>> > BTW, feel free to contribute it yourself if you have time.
>> >
>> > [1] https://ignite.apache.org/use-cases/caching/web-session-
>> > clustering.html
>> > [2] https://apacheignite-mix.readme.io/docs/web-session-clustering
>> >
>> > D.
>> >
>> > On Fri, May 19, 2017 at 11:43 AM, Rishi Yagnik <rishiyag...@gmail.com>
>> > wrote:
>> >
>> >> Hello Val,
>> >>
>> >> I tested out the session replication on spring boot cluster and here is
>> >> the
>> >> result.
>> >>
>> >> My finding were as follows with Ignite 2.0 on session replication and
>> hope
>> >> that helps the team –
>> >>
>> >>- Spring Security Filters requires context to be set with
>> >> Authentication
>> >>object, later on when user authentication object is set on the
>> ignite
>> >>filter from Ignite cache, the spring security treat that as a new
>> >> session
>> >>just to prevent session fixation issue.
>> >>- As spring security creates a new session and since there is no
>> way to
>> >>tell Ignite that user session has been changed, the user session is
>> no
>> >> good
>> >>here despite the fact that user session holds by the ignite is a
>> true
>> >>session for that user.
>> >>- Configuring web session filter does not work OOTB in spring boot
>> >>platform, it require some additional tweaking in the code to make it
>> >> work.
>> >>
>> >>
>> >> So in the nutshell, I would think having spring session on ignite
>> platform
>> >> would support full session replication with spring boot platform.
>> >>
>> >>
>> >> Please note that we have 2 SB instances, serving request round robin
>> via
>> >> F5
>> >> ( load balancers) supported by 2 node ignite cluster.
>> >>
>> >> Any suggestions on how we want to conquer the issue ?
>> >>
>> >> Thanks,
>> >>
>> >> --
>> >> Rishi Yagnik
>> >>
>> >
>> >
>>
>>
>> --
>> Rishi Yagnik
>>
>
>


-- 
Rishi Yagnik

Re: Session Replication Update on spring boot platform

2017-05-19 Thread Rishi Yagnik

Hello Dmitriy,

Thank you for the response, I would await for Val's feedback.

I would like to discuss the possible approach for implementation here, and
it could be one of this -

https://issues.apache.org/jira/browse/IGNITE-2741

Hope we all come on to conclusion here.

Thanks,

On Fri, May 19, 2017 at 3:57 PM, Dmitriy Setrakyan <dsetrak...@apache.org>
wrote:

> Hi Rishi,
>
> I think the best way is to file a ticket in Ignite Jira with your
> findings. This ticket does not seem tremendously difficult, so hopefully
> someone from the community will pick it up. All we need to do is to take
> our existing Web Session Clustering [1][2] code and port it to work with
> Spring Boot.
>
> BTW, feel free to contribute it yourself if you have time.
>
> [1] https://ignite.apache.org/use-cases/caching/web-session-
> clustering.html
> [2] https://apacheignite-mix.readme.io/docs/web-session-clustering
>
> D.
>
> On Fri, May 19, 2017 at 11:43 AM, Rishi Yagnik <rishiyag...@gmail.com>
> wrote:
>
>> Hello Val,
>>
>> I tested out the session replication on spring boot cluster and here is
>> the
>> result.
>>
>> My finding were as follows with Ignite 2.0 on session replication and hope
>> that helps the team –
>>
>>- Spring Security Filters requires context to be set with
>> Authentication
>>object, later on when user authentication object is set on the ignite
>>filter from Ignite cache, the spring security treat that as a new
>> session
>>just to prevent session fixation issue.
>>- As spring security creates a new session and since there is no way to
>>tell Ignite that user session has been changed, the user session is no
>> good
>>here despite the fact that user session holds by the ignite is a true
>>session for that user.
>>- Configuring web session filter does not work OOTB in spring boot
>>platform, it require some additional tweaking in the code to make it
>> work.
>>
>>
>> So in the nutshell, I would think having spring session on ignite platform
>> would support full session replication with spring boot platform.
>>
>>
>> Please note that we have 2 SB instances, serving request round robin via
>> F5
>> ( load balancers) supported by 2 node ignite cluster.
>>
>> Any suggestions on how we want to conquer the issue ?
>>
>> Thanks,
>>
>> --
>> Rishi Yagnik
>>
>
>


-- 
Rishi Yagnik

Session Replication Update on spring boot platform

2017-05-19 Thread Rishi Yagnik

Hello Val,

I tested out the session replication on spring boot cluster and here is the
result.

My finding were as follows with Ignite 2.0 on session replication and hope
that helps the team –

   - Spring Security Filters requires context to be set with Authentication
   object, later on when user authentication object is set on the ignite
   filter from Ignite cache, the spring security treat that as a new session
   just to prevent session fixation issue.
   - As spring security creates a new session and since there is no way to
   tell Ignite that user session has been changed, the user session is no good
   here despite the fact that user session holds by the ignite is a true
   session for that user.
   - Configuring web session filter does not work OOTB in spring boot
   platform, it require some additional tweaking in the code to make it work.


So in the nutshell, I would think having spring session on ignite platform
would support full session replication with spring boot platform.


Please note that we have 2 SB instances, serving request round robin via F5
( load balancers) supported by 2 node ignite cluster.

Any suggestions on how we want to conquer the issue ?

Thanks,

-- 
Rishi Yagnik

Re: Ignite Visor issue with 2.0

2017-05-05 Thread Rishi Yagnik

Yes this is the issue on my side, sir.

Please ignore it.

On Fri, May 5, 2017 at 12:40 PM, Denis Magda <dma...@apache.org> wrote:

> Seems the issue was on Rishi’s side:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-
> 0-visor-issue-tp12460p12461.html <http://apache-ignite-users.
> 70518.x6.nabble.com/Ignite-2-0-visor-issue-tp12460p12461.html>
>
> —
> Denis
>
> > On May 5, 2017, at 10:26 AM, Denis Magda <dma...@apache.org> wrote:
> >
> > Please share logs, command you’re executing and the configuration of
> your cluster.
> >
> > *Alex K.*, please keep an eye on this.
> >
> > —
> > Denis
> >
> >> On May 5, 2017, at 9:49 AM, Rishi Yagnik <rishiyag...@gmail.com> wrote:
> >>
> >> I am seeing some weird issue with Ignite 2.0
> >>
> >> I cant see any stats on visor console, it s always empty.
> >>
> >> Did you all ever see this issue ?
> >>
> >> Thanks,
> >> Rishi
> >
>
>


-- 
Rishi Yagnik

Re: Apache Ignite 2.0 Documentation

2017-05-05 Thread Rishi Yagnik

Thank you Alexey..

On Fri, May 5, 2017 at 10:49 AM, Alexey Kuznetsov <akuznet...@apache.org>
wrote:

> Rishi,
>
> May be not all mirrors are updated yet?
> On [1] I see ignite-2.0 and can download jars from [2].
>
> [1] http://search.maven.org
> [2] https://repo1.maven.org/maven2/org/apache/ignite/ignite-core/2.0.0/
>
> On Fri, May 5, 2017 at 10:22 PM, Rishi Yagnik <rishiyag...@gmail.com>
> wrote:
>
> > I tried upgrading Ignite 2.0 but cant find ignite libs on maven
> repository.
> >
> > https://mvnrepository.com/artifact/org.apache.ignite/ignite-core
> >
> >
> >
> --
> Alexey Kuznetsov
>



-- 
Rishi Yagnik

Re: Apache Ignite 2.0 Documentation

2017-05-05 Thread Rishi Yagnik

I tried upgrading Ignite 2.0 but cant find ignite libs on maven repository.

https://mvnrepository.com/artifact/org.apache.ignite/ignite-core



On Thu, May 4, 2017 at 1:43 PM, Denis Magda <dma...@apache.org> wrote:

> Evgeniy,
>
> Thanks a lot for pointing out to this! I’ve fixed the docs.
>
> —
> Denis
>
> > On May 3, 2017, at 11:56 PM, Evgeniy Ignatiev <
> yevgeniy.ignat...@gmail.com> wrote:
> >
> > Hello.
> >
> > On a "Resource Injection" page LoadBalancerResource line states that it
> injects IgniteLogger - seems to be an issue with docs. Also on
> "Asynchronous Support" in "Closures Execution and Thread Pools" section
> there seems to be some typos/missed words:
> >
> > asynchronous operation has been *comp* completed
> > Otherwise, the closure will be  asynchronously upon the
> operation completion
> >
> > On 5/4/2017 3:07 AM, Denis Magda wrote:
> >> Well, so many stuff that I eventually forgot about RocketMQ
> integration, sorry Roman ;)
> >> Just released the latest doc: https://apacheignite-mix.
> readme.io/docs/rocketmq-streamer
> >>
> >> —
> >> Denis
> >>
> >>> On May 3, 2017, at 4:00 PM, Denis Magda <dma...@apache.org> wrote:
> >>>
> >>> Igniters, thanks to all of you who helped documenting 2.0 features! We
> could complete the documentation just in time and I’ve just released it.
> >>>
> >>> Just to give you a sense on how many things were added to Ignite 2.0
> here is a list of completely new or significantly updated docs:
> >>> * Page memory: https://apacheignite.readme.io/docs/page-memory
> >>> * Memory & Cache Metrics: https://apacheignite.readme.
> io/docs/memory-and-cache-metrics
> >>> * Eviction policies: https://apacheignite.readme.io/docs/evictions
> >>>
> >>> * DDL: https://apacheignite.readme.io/docs/distributed-ddl
> >>>
> >>> * Machine Learning Grid (beta): https://apacheignite.readme.
> io/docs/machine-learning
> >>>
> >>> * Renewed Async API: https://apacheignite.readme.
> io/docs/async-support
> >>> * Apache Ignite thread pools including the new custom one:
> https://apacheignite.readme.io/docs/thread-pools
> >>>
> >>> * .NET Plugins: https://apacheignite-net.readme.io/docs/plugins
> >>>
> >>> * C++ Continuous Queries remote filters: https://apacheignite-cpp.
> readme.io/docs/continuous-queries#section-remote-filter
> >>>
> >>> * Spring Data Integration: https://apacheignite-mix.
> readme.io/v2.0/docs/spring-data
> >>>
> >>> And, for the first time we prepare a migration guide for you dear
> users: https://apacheignite.readme.io/docs/apache-ignite-20
> >>>
> >>> —
> >>> Denis
> >>>
> >>>> On Apr 13, 2017, at 6:46 PM, Dmitriy Setrakyan <dsetrak...@apache.org>
> wrote:
> >>>>
> >>>> Denis, thanks for tracking the documentation changes! This is the
> part that
> >>>> usually gets missed by the community.
> >>>>
> >>>> On Thu, Apr 13, 2017 at 12:46 PM, Denis Magda <dma...@apache.org>
> wrote:
> >>>>
> >>>>> Folks,
> >>>>>
> >>>>> I’ve prepared a list of changes that have to be documented before the
> >>>>> public release of 2.0:
> >>>>> https://issues.apache.org/jira/browse/IGNITE-4960
> >>>>>
> >>>>> That’s an impressive release and there are some many things to
> document.
> >>>>> Actually, I’ll try to document the biggest part contacting
> contributors in
> >>>>> person but still need a help from some of you:
> >>>>>
> >>>>> * Nikita, Oleg (Machine Learning): https://issues.apache.org/
> >>>>> jira/browse/IGNITE-4964
> >>>>> * Vovan or Alex P. (DDL indexing statements):
> https://issues.apache.org/
> >>>>> jira/browse/IGNITE-4967
> >>>>> * Vovan (custom thread pools): https://issues.apache.org/
> >>>>> jira/browse/IGNITE-4969
> >>>>> * Vovan or Taras (next gen async API): https://issues.apache.org/
> >>>>> jira/browse/IGNITE-4972
> >>>>> * Val (Hibernate improvements): https://issues.apache.org/
> >>>>> jira/browse/IGNITE-4972
> >>>>> * Pavel (.NET plugin system): https://issues.apache.org/
> >>>>> jira/browse/IGNITE-4973
> >>>>> * Pavel (.NET dynamically registered classes):
> https://issues.apache.org/
> >>>>> jira/browse/IGNITE-4974
> >>>>> * Igor Sapego (C++ CQ remote filters): https://issues.apache.org/
> >>>>> jira/browse/IGNITE-4976
> >>>>>
> >>>>> Let’s pull together and accomplish this part of the release together.
> >>>>>
> >>>>> —
> >>>>> Denis
> >>>>>
> >>>>>
> >
>
>


-- 
Rishi Yagnik

Re: [VOTE] Apache Ignite 2.0.0 RC2

2017-05-03 Thread Rishi Yagnik

 join, "contains" and DateTime property support.
> > > > > > > >
> > > > > > > > Ignite CPP:
> > > > > > > > * Implemented Cache::Invoke.
> > > > > > > > * Added remote filters support to continuous queries.
> > > > > > > >
> > > > > > > > Ignite Web Console:
> > > > > > > > * Multi-cluster support.
> > > > > > > > * Possibility to configure Kubernetes IP finder.
> > > > > > > > * EnforceJoinOrder option on Queries screen.
> > > > > > > >
> > > > > > > > Complete list of closed issues:
> > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%
> > > > > > 3D%20IGNITE%20AND%
> > > > > > > > 20fixVersion%20%3D%202.0%20AND%20(status%20%3D%
> > > > > > > > 20closed%20or%20status%20%3D%20resolved) <
> > > > https://issues.apache.org/
> > > > > > > > jira/issues/?jql=project%20%3D%20IGNITE%20AND%
> > > > > > 20fixVersion%20%3D%202.0%
> > > > > > > > 20AND%20(status%20%3D%20closed%20or%20status%20%3D%
> > 20resolved)>
> > > > > > > >
> > > > > > > > DEVNOTES
> > > > > > > > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > > > > > > > plain;f=DEVNOTES.txt;hb=refs/tags/2.0.0-rc2 <
> > > > > https://git-wip-us.apache
> > > > > > .
> > > > > > > > org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=
> > > > > > > > refs/tags/2.0.0-rc1>
> > > > > > > >
> > > > > > > > RELEASENOTES
> > > > > > > > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > > > > > > > plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.0.0-rc2 <
> > > > > > > > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=
> > > > > > > > blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.0.0-rc1>
> > > > > > > >
> > > > > > > > Please start voting.
> > > > > > > >
> > > > > > > > +1 - to accept Apache Ignite 2.0.0-rc2
> > > > > > > > 0 - don't care either way
> > > > > > > > -1 - DO NOT accept Apache Ignite 2.0.0-rc2 (explain why)
> > > > > > > >
> > > > > > > > This vote will go for 72 hours.
> > > > > > >
> > > > > >
> > > > > > --
> > > > > > Alexey Kuznetsov
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>



-- 
Rishi Yagnik

Re: 2.0 Migration Guide

2017-05-01 Thread Rishi Yagnik

OK good to know ..Thanks..

On Mon, May 1, 2017 at 5:03 PM, Denis Magda <dma...@apache.org> wrote:

> Yes, this affected the XML part either. Honestly, I don’t think we should
> say about the XML explicitly because there we define and instantiate the
> same Java beans. It’s just one more way how you can create your object like
> IgniteConfiguration.
>
> —
> Denis
>
> > On May 1, 2017, at 2:56 PM, Rishi Yagnik <rishiyag...@gmail.com> wrote:
> >
> > Denis,
> >
> > IgniteConfiguration's `getGridName/setGridName` methods are deprecated
> and
> > will be removed in later releases. Use IgniteConfiguration's
> > `getIgniteInstanceName/setIgniteInstanceName` instead.
> >
> > For example,
> >
> >  > class="org.apache.ignite.configuration.IgniteConfiguration">
> >
> >
> >
> > 
> >
> > Does it mean that xml configuration would also be no longer supported ?
> if
> > yes, shall we add one liner in the document related to xml configuration
> ?
> >
> > Thanks,
> >
> >
> > On Mon, May 1, 2017 at 4:47 PM, Denis Magda <dma...@apache.org> wrote:
> >
> >> Folks,
> >>
> >> I’ve walked through the changes that broke compatibility with Ignite 1.x
> >> and polished the migration guide:
> >> https://cwiki.apache.org/confluence/display/IGNITE/
> >> Apache+Ignite+2.0+Migration+Guide
> >>
> >> * Vovan, Sergi, please introduce and fill in SQL part.
> >> * Vovan, please review and extend “Binary Marshalling” section if
> needed.
> >> * Igor Sapego, do we need to mention any C++ changes there?
> >>
> >>
> >> —
> >> Denis
> >>
> >>> On Jan 11, 2017, at 8:47 PM, Denis Magda <dma...@gridgain.com> wrote:
> >>>
> >>> Dmitriy,
> >>>
> >>> Few number of people contribute to readme.io documentation and I don’t
> >> want to create an account only if someone needs to put a row in the
> >> migration guide. On the other hand, everyone can have an access to the
> wiki
> >> and update page there directly. I’ll create a page on readme.io with
> >> content from the wiki page once 2.0 gets released. That was the plan.
> >>>
> >>> —
> >>> Denis
> >>>
> >>>> On Jan 11, 2017, at 6:34 PM, Dmitriy Setrakyan <dsetrak...@apache.org
> >
> >> wrote:
> >>>>
> >>>> Denis,
> >>>>
> >>>> I would rather have these changes tracked on a hidden readme.io page.
> >> This
> >>>> way we can publish it whenever 2.0 is released. You can have the URL
> to
> >>>> that page on Ignite wiki.
> >>>>
> >>>> D.
> >>>>
> >>>> On Wed, Jan 11, 2017 at 2:18 PM, Denis Magda <dma...@apache.org>
> wrote:
> >>>>
> >>>>> Igniters,
> >>>>>
> >>>>> There will be many changes in 2.0. Some API can be deprecated while
> the
> >>>>> other removed completely. Let’s track all this kind of changes in 2.0
> >>>>> migration guide making a life for our users easier when they will be
> >>>>> switching from 1.x to 2.0 version. Add this page to your bookmarks
> and
> >>>>> don’t forget to update whenever is needed:
> >>>>> https://cwiki.apache.org/confluence/display/IGNITE/
> >>>>> Apache+Ignite+2.0+Migration+Guide <https://cwiki.apache.org/
> >>>>> confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide>
> >>>>>
> >>>>> —
> >>>>> Denis
> >>>
> >>
> >>
> >
> >
> > --
> > Rishi Yagnik
>
>


-- 
Rishi Yagnik

Re: 2.0 Migration Guide

2017-05-01 Thread Rishi Yagnik

Denis,

IgniteConfiguration's `getGridName/setGridName` methods are deprecated and
will be removed in later releases. Use IgniteConfiguration's
`getIgniteInstanceName/setIgniteInstanceName` instead.

For example,







Does it mean that xml configuration would also be no longer supported ? if
yes, shall we add one liner in the document related to xml configuration ?

Thanks,


On Mon, May 1, 2017 at 4:47 PM, Denis Magda <dma...@apache.org> wrote:

> Folks,
>
> I’ve walked through the changes that broke compatibility with Ignite 1.x
> and polished the migration guide:
> https://cwiki.apache.org/confluence/display/IGNITE/
> Apache+Ignite+2.0+Migration+Guide
>
> * Vovan, Sergi, please introduce and fill in SQL part.
> * Vovan, please review and extend “Binary Marshalling” section if needed.
> * Igor Sapego, do we need to mention any C++ changes there?
>
>
> —
> Denis
>
> > On Jan 11, 2017, at 8:47 PM, Denis Magda <dma...@gridgain.com> wrote:
> >
> > Dmitriy,
> >
> > Few number of people contribute to readme.io documentation and I don’t
> want to create an account only if someone needs to put a row in the
> migration guide. On the other hand, everyone can have an access to the wiki
> and update page there directly. I’ll create a page on readme.io with
> content from the wiki page once 2.0 gets released. That was the plan.
> >
> > —
> > Denis
> >
> >> On Jan 11, 2017, at 6:34 PM, Dmitriy Setrakyan <dsetrak...@apache.org>
> wrote:
> >>
> >> Denis,
> >>
> >> I would rather have these changes tracked on a hidden readme.io page.
> This
> >> way we can publish it whenever 2.0 is released. You can have the URL to
> >> that page on Ignite wiki.
> >>
> >> D.
> >>
> >> On Wed, Jan 11, 2017 at 2:18 PM, Denis Magda <dma...@apache.org> wrote:
> >>
> >>> Igniters,
> >>>
> >>> There will be many changes in 2.0. Some API can be deprecated while the
> >>> other removed completely. Let’s track all this kind of changes in 2.0
> >>> migration guide making a life for our users easier when they will be
> >>> switching from 1.x to 2.0 version. Add this page to your bookmarks and
> >>> don’t forget to update whenever is needed:
> >>> https://cwiki.apache.org/confluence/display/IGNITE/
> >>> Apache+Ignite+2.0+Migration+Guide <https://cwiki.apache.org/
> >>> confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide>
> >>>
> >>> —
> >>> Denis
> >
>
>


-- 
Rishi Yagnik

Re: Webinar: Apache Ignite as a backbone for microservices-based architectures

2017-04-18 Thread Rishi Yagnik

Thanks, Denis.

I will surely join the conference.

Take Care,
Rishi

> On Apr 18, 2017, at 7:38 PM, Denis Magda  wrote:
> 
> Igniters,
> 
> Just a final reminder for those who might be interested. The slides are 
> ready, the demo is running..so waiting for all of you tomorrow April 19, 
> 11:00 AM PST on the line ;)
> http://bit.ly/2nEmyv1
> 
> Plus, look at our “news” section for upcoming conferences where the community 
> is going to present Ignite:
> https://ignite.apache.org/news.html
> 
> —
> Denis
> 
>> On Apr 12, 2017, at 6:35 PM, Denis Magda  wrote:
>> 
>> Dear community,
>> 
>> Welcome you to join the next Apache Ignite related webinar where you can 
>> learn more about Service Grid component and how to apply it for 
>> microservices-based solutions.
>> 
>> Description and registration: http://bit.ly/2nEmyv1  
>> 
>> Tweet: https://twitter.com/ApacheIgnite/status/852165280700796928
>> 
>> *Prachi*, would you add the event to the news feed?
>> https://ignite.apache.org/news.html 
>> 
>> —
>> Denis
>> 
>> 
>

Re: IGNITE-2741 - spring session design

2017-04-13 Thread Rishi Yagnik

Hello Val,

I debug further and found out that issue exist with SPA ( Angular APP ) and
it needs a fix on their end so don't worry about it.

Next week, I will deploy it in a cluster and let you know if that fixes
session replication issue on cluster.

Thanks,
Rishi


On Thu, Apr 13, 2017 at 7:55 AM, Rishi Yagnik <rishiyag...@gmail.com> wrote:

> Val,
>
> Yes I would provide you the exact steps today and I will also test it in
> cluster environment.
>
> The local environment is working as expected with the fix.
>
> Take Care,
> Rishi
>
> > On Apr 13, 2017, at 2:18 AM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
> >
> > Rishi,
> >
> > Can you tell exact steps to reproduce? It's working for me in my
> > environment.
> >
> > Do I understand correctly that apart from the token issue, it works fine
> > with new version?
> >
> > -Val
> >
> > On Wed, Apr 12, 2017 at 10:00 PM, Rishi Yagnik <rishiyag...@gmail.com>
> > wrote:
> >
> >> Val,
> >>
> >> I build it from master s and was able to integrate with our app, but as
> I
> >> mentioned to you previously, I see the XSRF-Token errors in debug log,
> >>
> >> [DEBUG] [XNIO-2 task-4] org.springframework.security.
> web.FilterChainProxy
> >> -
> >> /app/xxx/yyy/zz/A at position 3 of 13 in additional filter chain; firing
> >> Filter: 'HeaderWriterFilter'
> >> [DEBUG] [XNIO-2 task-4] org.springframework.security.
> web.FilterChainProxy
> >> -
> >> /app/xxx/yyy/zz/A at position 4 of 13 in additional filter chain; firing
> >> Filter: 'CsrfFilter'
> >>
> >> [DEBUG] [XNIO-2 task-4] org.springframework.security.web.csrf.CsrfFilter
> -
> >> Invalid CSRF token found for http://localhost:9002/app/xxx/yyy/zz/A
> >>
> >> And, then after, CSRF filter does not like the session, redirects to
> /403
> >> error.
> >>
> >> Just wondering why the XSRF Token is not being saved in the session  ?
> >>
> >> More debugging is require for sure..
> >>
> >> of course there is a work around to the problem, I can just use Cookie
> >> based Token repository to avoid this issue.
> >>
> >> .csrfTokenRepository(CookieCsrfTokenRepository.withHttpOnlyFalse())
> >>
> >>
> >> will let you know my findings..
> >>
> >> As always, thanks for all your help.
> >>
> >> Thanks,
> >> Rishi
> >>
> >>
> >> On Tue, Apr 11, 2017 at 4:18 PM, Rishi Yagnik <rishiyag...@gmail.com>
> >> wrote:
> >>
> >>> Hi Val,
> >>>
> >>> I will build it from master s and let you know by tomorrow.
> >>>
> >>> Thanks,
> >>>
> >>>
> >>> On Tue, Apr 11, 2017 at 3:53 PM, Valentin Kulichenko <
> >>> valentin.kuliche...@gmail.com> wrote:
> >>>
> >>>> Hi Rishi,
> >>>>
> >>>> What was the issue with the HttpSessionCsrfTokenRepository? I didn't
> >> have
> >>>> any problems after I added code you provided.
> >>>>
> >>>> The fix for [1] is already in master. Can you try building from there
> >> and
> >>>> check if everything works fine for you?
> >>>>
> >>>> [1] https://issues.apache.org/jira/browse/IGNITE-4948
> >>>>
> >>>> -Val
> >>>>
> >>>> On Sat, Mar 18, 2017 at 5:15 PM, Denis Magda <dma...@gridgain.com>
> >> wrote:
> >>>>
> >>>>> Somewhere in April. This will be clarified on the dev list soon.
> >>>>>
> >>>>> On Saturday, March 18, 2017, Rishi Yagnik <rishiyag...@gmail.com>
> >>>> wrote:
> >>>>>
> >>>>>> Thanks, Val.
> >>>>>>
> >>>>>> When are we going to release Ignite 2.0 ? June ??
> >>>>>>
> >>>>>> Thanks,
> >>>>>>
> >>>>>> On Sat, Mar 18, 2017 at 6:02 AM, Valentin Kulichenko <
> >>>>>> valentin.kuliche...@gmail.com <javascript:;>> wrote:
> >>>>>>
> >>>>>>> Denis,
> >>>>>>>
> >>>>>>> Yes, this should be possible. I will try to finalize the fix asap.
> >>>>>>>
> >>>>>>> -Val
> >>>>>>>
> >>>>&g

Re: IGNITE-2741 - spring session design

2017-04-13 Thread Rishi Yagnik

Val,

Yes I would provide you the exact steps today and I will also test it in 
cluster environment.

The local environment is working as expected with the fix.

Take Care,
Rishi

> On Apr 13, 2017, at 2:18 AM, Valentin Kulichenko 
> <valentin.kuliche...@gmail.com> wrote:
> 
> Rishi,
> 
> Can you tell exact steps to reproduce? It's working for me in my
> environment.
> 
> Do I understand correctly that apart from the token issue, it works fine
> with new version?
> 
> -Val
> 
> On Wed, Apr 12, 2017 at 10:00 PM, Rishi Yagnik <rishiyag...@gmail.com>
> wrote:
> 
>> Val,
>> 
>> I build it from master s and was able to integrate with our app, but as I
>> mentioned to you previously, I see the XSRF-Token errors in debug log,
>> 
>> [DEBUG] [XNIO-2 task-4] org.springframework.security.web.FilterChainProxy
>> -
>> /app/xxx/yyy/zz/A at position 3 of 13 in additional filter chain; firing
>> Filter: 'HeaderWriterFilter'
>> [DEBUG] [XNIO-2 task-4] org.springframework.security.web.FilterChainProxy
>> -
>> /app/xxx/yyy/zz/A at position 4 of 13 in additional filter chain; firing
>> Filter: 'CsrfFilter'
>> 
>> [DEBUG] [XNIO-2 task-4] org.springframework.security.web.csrf.CsrfFilter -
>> Invalid CSRF token found for http://localhost:9002/app/xxx/yyy/zz/A
>> 
>> And, then after, CSRF filter does not like the session, redirects to /403
>> error.
>> 
>> Just wondering why the XSRF Token is not being saved in the session  ?
>> 
>> More debugging is require for sure..
>> 
>> of course there is a work around to the problem, I can just use Cookie
>> based Token repository to avoid this issue.
>> 
>> .csrfTokenRepository(CookieCsrfTokenRepository.withHttpOnlyFalse())
>> 
>> 
>> will let you know my findings..
>> 
>> As always, thanks for all your help.
>> 
>> Thanks,
>> Rishi
>> 
>> 
>> On Tue, Apr 11, 2017 at 4:18 PM, Rishi Yagnik <rishiyag...@gmail.com>
>> wrote:
>> 
>>> Hi Val,
>>> 
>>> I will build it from master s and let you know by tomorrow.
>>> 
>>> Thanks,
>>> 
>>> 
>>> On Tue, Apr 11, 2017 at 3:53 PM, Valentin Kulichenko <
>>> valentin.kuliche...@gmail.com> wrote:
>>> 
>>>> Hi Rishi,
>>>> 
>>>> What was the issue with the HttpSessionCsrfTokenRepository? I didn't
>> have
>>>> any problems after I added code you provided.
>>>> 
>>>> The fix for [1] is already in master. Can you try building from there
>> and
>>>> check if everything works fine for you?
>>>> 
>>>> [1] https://issues.apache.org/jira/browse/IGNITE-4948
>>>> 
>>>> -Val
>>>> 
>>>> On Sat, Mar 18, 2017 at 5:15 PM, Denis Magda <dma...@gridgain.com>
>> wrote:
>>>> 
>>>>> Somewhere in April. This will be clarified on the dev list soon.
>>>>> 
>>>>> On Saturday, March 18, 2017, Rishi Yagnik <rishiyag...@gmail.com>
>>>> wrote:
>>>>> 
>>>>>> Thanks, Val.
>>>>>> 
>>>>>> When are we going to release Ignite 2.0 ? June ??
>>>>>> 
>>>>>> Thanks,
>>>>>> 
>>>>>> On Sat, Mar 18, 2017 at 6:02 AM, Valentin Kulichenko <
>>>>>> valentin.kuliche...@gmail.com <javascript:;>> wrote:
>>>>>> 
>>>>>>> Denis,
>>>>>>> 
>>>>>>> Yes, this should be possible. I will try to finalize the fix asap.
>>>>>>> 
>>>>>>> -Val
>>>>>>> 
>>>>>>> On Fri, Mar 17, 2017 at 7:46 PM, Denis Magda <dma...@apache.org
>>>>>> <javascript:;>> wrote:
>>>>>>> 
>>>>>>>> Val,
>>>>>>>> 
>>>>>>>> Will it be possible to incorporate the fix into the nearest 2.0
>>>>>> release?
>>>>>>>> 
>>>>>>>> —
>>>>>>>> Denis
>>>>>>>> 
>>>>>>>>> On Mar 17, 2017, at 11:43 AM, Rishi Yagnik <
>>>> rishiyag...@gmail.com
>>>>>> <javascript:;>>
>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>> Hi Val,
>>>>>>>>> 
>>>>>>>>> Hope you are well, any

Re: IGNITE-2766 Spring Cache Manager ReConnect Issue

2017-04-12 Thread Rishi Yagnik

Hi Val,

Just want to share my experience here -

with the code changes I suggested we run into issue,out of memory on ignite
with ignite thread whenever ignite cluster looses the client connection (
we had a cluster with multicast communication) .


However, we changed our cluster with ip based configuration few days back
and hoping that solves our issues.

Do you still think that listening events on spring cache manager is a good
design here ?

will await for your feedback..

Thanks,

On Fri, Mar 31, 2017 at 11:51 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Hi Rishi,
>
> I looked at your changes and added a comment in the ticket.
>
> -Val
>
> On Wed, Mar 29, 2017 at 10:04 AM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > Hi Rishi,
> >
> > I will review in next couple of days.
> >
> > -Val
> >
> > On Tue, Mar 28, 2017 at 8:24 PM, Rishi Yagnik <rishiyag...@gmail.com>
> > wrote:
> >
> >> Hi Val,
> >>
> >> Committed changes on IGNITE-2786, would like you to review the
> >> changes.Would you please review it ?
> >>
> >> Thanks,
> >>
> >> On Mon, Mar 27, 2017 at 6:11 PM, Valentin Kulichenko <
> >> valentin.kuliche...@gmail.com> wrote:
> >>
> >> > Rishi,
> >> >
> >> > You should be able to assign to tickets to yourself now.
> >> >
> >> > -Val
> >> >
> >> > On Mon, Mar 27, 2017 at 1:23 PM, Rishi Yagnik <rishiyag...@gmail.com>
> >> > wrote:
> >> >
> >> > > Hi Val,
> >> > >
> >> > > My user name is ryagnik
> >> > >
> >> > > Thanks,
> >> > > Rishi
> >> > >
> >> > > On Mon, Mar 27, 2017 at 12:14 PM, Valentin Kulichenko <
> >> > > valentin.kuliche...@gmail.com> wrote:
> >> > >
> >> > > > Hi Rishi,
> >> > > >
> >> > > > What is your username in Jira? I will add you as a contributor.
> >> > > >
> >> > > > Also please go through [1] and [2] for all the details about our
> >> > process.
> >> > > >
> >> > > > [1] https://ignite.apache.org/community/contribute.html#
> contribute
> >> > > > [2] https://cwiki.apache.org/confluence/display/IGNITE/
> >> > > Development+Process
> >> > > >
> >> > > > -Val
> >> > > >
> >> > > > On Sun, Mar 26, 2017 at 5:56 PM, Rishi Yagnik <
> >> rishiyag...@gmail.com>
> >> > > > wrote:
> >> > > >
> >> > > > > Hi Val,
> >> > > > >
> >> > > > > I started working on it but could not assign issue to me, how
> do I
> >> > > assign
> >> > > > > ticket to my self ?
> >> > > > >
> >> > > > > Do I need contributor access to contribute the fix ?
> >> > > > >
> >> > > > > Please clarify..
> >> > > > >
> >> > > > > Thanks,
> >> > > > >
> >> > > > > On Fri, Mar 24, 2017 at 12:10 AM, Rishi Yagnik <
> >> > rishiyag...@gmail.com>
> >> > > > > wrote:
> >> > > > >
> >> > > > > > Hi Val,
> >> > > > > >
> >> > > > > > Sorry for the delay, I will work on the fix on weekend.
> >> > > > > >
> >> > > > > > Thanks,
> >> > > > > >
> >> > > > > >
> >> > > > > > On Mon, Mar 13, 2017 at 12:08 PM, Rishi Yagnik <
> >> > > rishiyag...@gmail.com>
> >> > > > > > wrote:
> >> > > > > >
> >> > > > > >> Hi Val,
> >> > > > > >>
> >> > > > > >> I will work on it in my spare time..
> >> > > > > >>
> >> > > > > >> Take Care,
> >> > > > > >> Rishi
> >> > > > > >>
> >> > > > > >> > On Mar 13, 2017, at 10:54 AM, Valentin Kulichenko <
> >> > > > > >> valentin.kuliche...@gmail.com> wrote:
> >> > > > > >> >
> >> > > > > >> > Hi Rishi,
&

Re: build failure in the master branch

2017-04-12 Thread Rishi Yagnik

I build it last night it worked for me..I am using Jdk8-121, hope that helps ..

Take Care,
Rishi

> On Apr 12, 2017, at 5:37 AM, Vyacheslav Daradur  wrote:
> 
> Does anyone has the same problem?
> 
> 2017-04-12 12:30 GMT+03:00 Vyacheslav Daradur :
> 
>> Last commit [1] 12.04.2017 6:19:06
>> 
>> mvn -X clean package -DskipTests
>> 
>> result:
>> ***
>> [DEBUG] parsing done in 2ms.
>> JavaDoc error: 'Other Packages' section should not be present, all
>> packages shou
>> ld have corresponding documentation groups: C:\Users\SBT-Daradur-V\
>> Projects\igni
>> te\target\javadoc\core/overview-summary.html
>> [DEBUG] parsing started
>> [DEBUG] DomTree builder started.
>> [DEBUG] LagartoDom tree created in 4 ms.
>> [DEBUG] parsing done in 5ms.
>> [DEBUG] parsing started
>> [DEBUG] DomTree builder started.
>> [DEBUG] LagartoDom tree created in 4 ms.
>> [DEBUG] parsing done in 4ms.
>> [INFO] 
>> 
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] ignite-apache-license-gen .. SUCCESS [
>> 1.473 s]
>> [INFO] ignite-tools ... SUCCESS [
>> 5.950 s]
>> [INFO] ignite-core  SUCCESS
>> [02:25 min]
>> [INFO] ignite-log4j ... SUCCESS [
>> 4.440 s]
>> [INFO] ignite-indexing  SUCCESS [
>> 12.198 s]
>> [INFO] ignite-urideploy ... SUCCESS [
>> 4.338 s]
>> [INFO] ignite-spring .. SUCCESS [
>> 5.500 s]
>> [INFO] ignite-hadoop .. SUCCESS [
>> 15.860 s]
>> [INFO] ignite-extdata-p2p . SUCCESS [
>> 4.629 s]
>> [INFO] ignite-extdata-uri-dep . SUCCESS [
>> 2.210 s]
>> [INFO] ignite-extdata-uri . SUCCESS [
>> 1.033 s]
>> [INFO] ignite-rest-http ... SUCCESS [
>> 4.003 s]
>> [INFO] ignite-clients . SUCCESS [
>> 2.153 s]
>> [INFO] ignite-spring-data . SUCCESS [
>> 3.284 s]
>> [INFO] ignite-web . SUCCESS [
>> 3.487 s]
>> [INFO] ignite-aop . SUCCESS [
>> 3.365 s]
>> [INFO] ignite-ssh . SUCCESS [
>> 3.135 s]
>> [INFO] ignite-jta . SUCCESS [
>> 3.762 s]
>> [INFO] ignite-aws . SUCCESS [
>> 3.550 s]
>> [INFO] ignite-log4j2 .. SUCCESS [
>> 3.074 s]
>> [INFO] ignite-slf4j ... SUCCESS [
>> 2.650 s]
>> [INFO] ignite-jcl . SUCCESS [
>> 2.515 s]
>> [INFO] ignite-codegen . SUCCESS [
>> 2.364 s]
>> [INFO] ignite-gce . SUCCESS [
>> 2.713 s]
>> [INFO] ignite-cloud ... SUCCESS [
>> 4.806 s]
>> [INFO] ignite-mesos ... SUCCESS [
>> 4.260 s]
>> [INFO] ignite-kafka ... SUCCESS [
>> 4.889 s]
>> [INFO] ignite-flume ... SUCCESS [
>> 3.584 s]
>> [INFO] ignite-yarn  SUCCESS [
>> 10.306 s]
>> [INFO] ignite-jms11 ... SUCCESS [
>> 3.234 s]
>> [INFO] ignite-twitter . SUCCESS [
>> 3.141 s]
>> [INFO] ignite-mqtt  SUCCESS [
>> 3.578 s]
>> [INFO] ignite-zookeeper ... SUCCESS [
>> 3.395 s]
>> [INFO] ignite-camel ... SUCCESS [
>> 3.579 s]
>> [INFO] ignite-storm ... SUCCESS [
>> 3.147 s]
>> [INFO] ignite-osgi-paxlogging . SUCCESS [
>> 0.728 s]
>> [INFO] ignite-osgi-karaf .. SUCCESS [
>> 0.381 s]
>> [INFO] ignite-osgi  SUCCESS [
>> 4.074 s]
>> [INFO] ignite-appserver-test .. SUCCESS [
>> 0.591 s]
>> [INFO] ignite-websphere-test .. SUCCESS [
>> 3.345 s]
>> [INFO] ignite-cassandra ... SUCCESS [
>> 0.355 s]
>> [INFO] ignite-cassandra-store . SUCCESS [
>> 10.290 s]
>> [INFO] ignite-cassandra-serializers ... SUCCESS [
>> 3.740 s]
>> [INFO] ignite-flink ... SUCCESS [
>> 3.553 s]
>> [INFO] ignite-kubernetes .. SUCCESS [
>> 2.646 s]
>> [INFO] ignite-zeromq .. SUCCESS [
>> 2.621 s]
>> [INFO] ignite-scalar

Re: IGNITE-2741 - spring session design

2017-04-11 Thread Rishi Yagnik

Hi Val,

I will build it from master s and let you know by tomorrow.

Thanks,


On Tue, Apr 11, 2017 at 3:53 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Hi Rishi,
>
> What was the issue with the HttpSessionCsrfTokenRepository? I didn't have
> any problems after I added code you provided.
>
> The fix for [1] is already in master. Can you try building from there and
> check if everything works fine for you?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-4948
>
> -Val
>
> On Sat, Mar 18, 2017 at 5:15 PM, Denis Magda <dma...@gridgain.com> wrote:
>
> > Somewhere in April. This will be clarified on the dev list soon.
> >
> > On Saturday, March 18, 2017, Rishi Yagnik <rishiyag...@gmail.com> wrote:
> >
> > > Thanks, Val.
> > >
> > > When are we going to release Ignite 2.0 ? June ??
> > >
> > > Thanks,
> > >
> > > On Sat, Mar 18, 2017 at 6:02 AM, Valentin Kulichenko <
> > > valentin.kuliche...@gmail.com <javascript:;>> wrote:
> > >
> > > > Denis,
> > > >
> > > > Yes, this should be possible. I will try to finalize the fix asap.
> > > >
> > > > -Val
> > > >
> > > > On Fri, Mar 17, 2017 at 7:46 PM, Denis Magda <dma...@apache.org
> > > <javascript:;>> wrote:
> > > >
> > > > > Val,
> > > > >
> > > > > Will it be possible to incorporate the fix into the nearest 2.0
> > > release?
> > > > >
> > > > > —
> > > > > Denis
> > > > >
> > > > > > On Mar 17, 2017, at 11:43 AM, Rishi Yagnik <
> rishiyag...@gmail.com
> > > <javascript:;>>
> > > > > wrote:
> > > > > >
> > > > > > Hi Val,
> > > > > >
> > > > > > Hope you are well, any update on web session clustering.
> > > > > >
> > > > > > Thanks,
> > > > > > Rishi
> > > > > >
> > > > > > On Sat, Mar 11, 2017 at 12:29 PM, Rishi Yagnik <
> > > rishiyag...@gmail.com <javascript:;>>
> > > > > > wrote:
> > > > > >
> > > > > >> Hi Val,
> > > > > >>
> > > > > >> Thanks looking forward for the fix..
> > > > > >>
> > > > > >> Take Care,
> > > > > >> Rishi
> > > > > >>
> > > > > >>> On Mar 11, 2017, at 11:31 AM, Valentin Kulichenko <
> > > > > >> valentin.kuliche...@gmail.com <javascript:;>> wrote:
> > > > > >>>
> > > > > >>> Hi Rishi,
> > > > > >>>
> > > > > >>> I want to fix the bug first. It takes a bit longer than I
> > thought,
> > > > but
> > > > > I
> > > > > >>> should finish it over the weekend.
> > > > > >>>
> > > > > >>> -Val
> > > > > >>>
> > > > > >>>> On Fri, Mar 10, 2017 at 4:13 AM, Rishi Yagnik <
> > > > rishiyag...@gmail.com <javascript:;>>
> > > > > >> wrote:
> > > > > >>>>
> > > > > >>>> Hi Val,
> > > > > >>>>
> > > > > >>>> Did you chance to look into session handling issue ?
> > > > > >>>>
> > > > > >>>> Thanks,
> > > > > >>>>
> > > > > >>>> On Mon, Mar 6, 2017 at 3:37 PM, Rishi Yagnik <
> > > rishiyag...@gmail.com <javascript:;>
> > > > >
> > > > > >>>> wrote:
> > > > > >>>>
> > > > > >>>>> Hi Val,
> > > > > >>>>>
> > > > > >>>>> Do you think I can test a fix in 1.9 RC releases ? How are
> you
> > > > > planning
> > > > > >>>> to
> > > > > >>>>> release a fix ?
> > > > > >>>>>
> > > > > >>>>> Did you also look into problem where storing xsrf token in
> > Ignite
> > > > > >> returns
> > > > > >>>>> an exception and does not behave as expected ?
> > > > > >>>>>
>

Re: IGNITE-2766 Spring Cache Manager ReConnect Issue

2017-03-28 Thread Rishi Yagnik

Hi Val,

Committed changes on IGNITE-2786, would like you to review the
changes.Would you please review it ?

Thanks,

On Mon, Mar 27, 2017 at 6:11 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Rishi,
>
> You should be able to assign to tickets to yourself now.
>
> -Val
>
> On Mon, Mar 27, 2017 at 1:23 PM, Rishi Yagnik <rishiyag...@gmail.com>
> wrote:
>
> > Hi Val,
> >
> > My user name is ryagnik
> >
> > Thanks,
> > Rishi
> >
> > On Mon, Mar 27, 2017 at 12:14 PM, Valentin Kulichenko <
> > valentin.kuliche...@gmail.com> wrote:
> >
> > > Hi Rishi,
> > >
> > > What is your username in Jira? I will add you as a contributor.
> > >
> > > Also please go through [1] and [2] for all the details about our
> process.
> > >
> > > [1] https://ignite.apache.org/community/contribute.html#contribute
> > > [2] https://cwiki.apache.org/confluence/display/IGNITE/
> > Development+Process
> > >
> > > -Val
> > >
> > > On Sun, Mar 26, 2017 at 5:56 PM, Rishi Yagnik <rishiyag...@gmail.com>
> > > wrote:
> > >
> > > > Hi Val,
> > > >
> > > > I started working on it but could not assign issue to me, how do I
> > assign
> > > > ticket to my self ?
> > > >
> > > > Do I need contributor access to contribute the fix ?
> > > >
> > > > Please clarify..
> > > >
> > > > Thanks,
> > > >
> > > > On Fri, Mar 24, 2017 at 12:10 AM, Rishi Yagnik <
> rishiyag...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi Val,
> > > > >
> > > > > Sorry for the delay, I will work on the fix on weekend.
> > > > >
> > > > > Thanks,
> > > > >
> > > > >
> > > > > On Mon, Mar 13, 2017 at 12:08 PM, Rishi Yagnik <
> > rishiyag...@gmail.com>
> > > > > wrote:
> > > > >
> > > > >> Hi Val,
> > > > >>
> > > > >> I will work on it in my spare time..
> > > > >>
> > > > >> Take Care,
> > > > >> Rishi
> > > > >>
> > > > >> > On Mar 13, 2017, at 10:54 AM, Valentin Kulichenko <
> > > > >> valentin.kuliche...@gmail.com> wrote:
> > > > >> >
> > > > >> > Hi Rishi,
> > > > >> >
> > > > >> > Can you please assign the ticket to yourself and create a pull
> > > request
> > > > >> as
> > > > >> > described in [1]?
> > > > >> >
> > > > >> > Let's follow the process :)
> > > > >> >
> > > > >> > [1] https://cwiki.apache.org/confluence/display/IGNITE/How+to+
> > > > >> Contribute
> > > > >> >
> > > > >> > -Val
> > > > >> >
> > > > >> > On Sun, Mar 12, 2017 at 2:04 AM, ignite_dev2017 <
> > > > rishiyag...@gmail.com>
> > > > >> > wrote:
> > > > >> >
> > > > >> >> Hi Val,
> > > > >> >>
> > > > >> >> The fix which we applied as follows with SpringCacheManager -
> > > > >> >>
> > > > >> >> 1) Design was to listen for ignite re connect event
> > > > >> >> 2) And clear the cache on reconnect
> > > > >> >>
> > > > >> >> See the following code below and let us know if this is
> helpful -
> > > > >> >>
> > > > >> >> In afterPropertiesSet -
> > > > >> >>
> > > > >> >> //Handles the reconnect event, on server crashes OR network
> > > failure,
> > > > >> client
> > > > >> >> connects to server and
> > > > >> >>// destroy the cache
> > > > >> >>IgnitePredicate lsnr = iEvt -> {
> > > > >> >>LOGGER.info("Received discovery event [iEvt=" +
> > > > iEvt.name()
> > > > >> +
> > > > >> >> ",
> > > > >> >> discovery=" + iEvt.shortDisplay() + ']');
> > > > >> >>
> > > > >> >>caches.keySet().forEach(key -> {
> > > > >> >>ignite.destroyCache(key);
> > > > >> >>caches.remove(key);
> > > > >> >>} );
> > > > >> >>
> > > > >> >>
> > > > >> >>
> > > > >> >> Let me know if you see any side effects with the fix.
> > > > >> >>
> > > > >> >> Thanks,
> > > > >> >> Rishi
> > > > >> >>
> > > > >> >>
> > > > >> >>
> > > > >> >> --
> > > > >> >> View this message in context: http://apache-ignite-
> > > > >> >> developers.2346864.n4.nabble.com/IGNITE-2766-Spring-Cache-
> > > > >> >> Manager-ReConnect-Issue-tp15362.html
> > > > >> >> Sent from the Apache Ignite Developers mailing list archive at
> > > > >> Nabble.com.
> > > > >> >>
> > > > >>
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Rishi Yagnik
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Rishi Yagnik
> > > >
> > >
> >
> >
> >
> > --
> > Rishi Yagnik
> >
>



-- 
Rishi Yagnik

Re: IGNITE-2766 Spring Cache Manager ReConnect Issue

2017-03-27 Thread Rishi Yagnik

Hi Val,

My user name is ryagnik

Thanks,
Rishi

On Mon, Mar 27, 2017 at 12:14 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Hi Rishi,
>
> What is your username in Jira? I will add you as a contributor.
>
> Also please go through [1] and [2] for all the details about our process.
>
> [1] https://ignite.apache.org/community/contribute.html#contribute
> [2] https://cwiki.apache.org/confluence/display/IGNITE/Development+Process
>
> -Val
>
> On Sun, Mar 26, 2017 at 5:56 PM, Rishi Yagnik <rishiyag...@gmail.com>
> wrote:
>
> > Hi Val,
> >
> > I started working on it but could not assign issue to me, how do I assign
> > ticket to my self ?
> >
> > Do I need contributor access to contribute the fix ?
> >
> > Please clarify..
> >
> > Thanks,
> >
> > On Fri, Mar 24, 2017 at 12:10 AM, Rishi Yagnik <rishiyag...@gmail.com>
> > wrote:
> >
> > > Hi Val,
> > >
> > > Sorry for the delay, I will work on the fix on weekend.
> > >
> > > Thanks,
> > >
> > >
> > > On Mon, Mar 13, 2017 at 12:08 PM, Rishi Yagnik <rishiyag...@gmail.com>
> > > wrote:
> > >
> > >> Hi Val,
> > >>
> > >> I will work on it in my spare time..
> > >>
> > >> Take Care,
> > >> Rishi
> > >>
> > >> > On Mar 13, 2017, at 10:54 AM, Valentin Kulichenko <
> > >> valentin.kuliche...@gmail.com> wrote:
> > >> >
> > >> > Hi Rishi,
> > >> >
> > >> > Can you please assign the ticket to yourself and create a pull
> request
> > >> as
> > >> > described in [1]?
> > >> >
> > >> > Let's follow the process :)
> > >> >
> > >> > [1] https://cwiki.apache.org/confluence/display/IGNITE/How+to+
> > >> Contribute
> > >> >
> > >> > -Val
> > >> >
> > >> > On Sun, Mar 12, 2017 at 2:04 AM, ignite_dev2017 <
> > rishiyag...@gmail.com>
> > >> > wrote:
> > >> >
> > >> >> Hi Val,
> > >> >>
> > >> >> The fix which we applied as follows with SpringCacheManager -
> > >> >>
> > >> >> 1) Design was to listen for ignite re connect event
> > >> >> 2) And clear the cache on reconnect
> > >> >>
> > >> >> See the following code below and let us know if this is helpful -
> > >> >>
> > >> >> In afterPropertiesSet -
> > >> >>
> > >> >> //Handles the reconnect event, on server crashes OR network
> failure,
> > >> client
> > >> >> connects to server and
> > >> >>// destroy the cache
> > >> >>IgnitePredicate lsnr = iEvt -> {
> > >> >>LOGGER.info("Received discovery event [iEvt=" +
> > iEvt.name()
> > >> +
> > >> >> ",
> > >> >> discovery=" + iEvt.shortDisplay() + ']');
> > >> >>
> > >> >>caches.keySet().forEach(key -> {
> > >> >>ignite.destroyCache(key);
> > >> >>caches.remove(key);
> > >> >>} );
> > >> >>
> > >> >>
> > >> >>
> > >> >> Let me know if you see any side effects with the fix.
> > >> >>
> > >> >> Thanks,
> > >> >> Rishi
> > >> >>
> > >> >>
> > >> >>
> > >> >> --
> > >> >> View this message in context: http://apache-ignite-
> > >> >> developers.2346864.n4.nabble.com/IGNITE-2766-Spring-Cache-
> > >> >> Manager-ReConnect-Issue-tp15362.html
> > >> >> Sent from the Apache Ignite Developers mailing list archive at
> > >> Nabble.com.
> > >> >>
> > >>
> > >
> > >
> > >
> > > --
> > > Rishi Yagnik
> > >
> >
> >
> >
> > --
> > Rishi Yagnik
> >
>



-- 
Rishi Yagnik

Re: IGNITE-2766 Spring Cache Manager ReConnect Issue

2017-03-26 Thread Rishi Yagnik

Hi Val,

I started working on it but could not assign issue to me, how do I assign
ticket to my self ?

Do I need contributor access to contribute the fix ?

Please clarify..

Thanks,

On Fri, Mar 24, 2017 at 12:10 AM, Rishi Yagnik <rishiyag...@gmail.com>
wrote:

> Hi Val,
>
> Sorry for the delay, I will work on the fix on weekend.
>
> Thanks,
>
>
> On Mon, Mar 13, 2017 at 12:08 PM, Rishi Yagnik <rishiyag...@gmail.com>
> wrote:
>
>> Hi Val,
>>
>> I will work on it in my spare time..
>>
>> Take Care,
>> Rishi
>>
>> > On Mar 13, 2017, at 10:54 AM, Valentin Kulichenko <
>> valentin.kuliche...@gmail.com> wrote:
>> >
>> > Hi Rishi,
>> >
>> > Can you please assign the ticket to yourself and create a pull request
>> as
>> > described in [1]?
>> >
>> > Let's follow the process :)
>> >
>> > [1] https://cwiki.apache.org/confluence/display/IGNITE/How+to+
>> Contribute
>> >
>> > -Val
>> >
>> > On Sun, Mar 12, 2017 at 2:04 AM, ignite_dev2017 <rishiyag...@gmail.com>
>> > wrote:
>> >
>> >> Hi Val,
>> >>
>> >> The fix which we applied as follows with SpringCacheManager -
>> >>
>> >> 1) Design was to listen for ignite re connect event
>> >> 2) And clear the cache on reconnect
>> >>
>> >> See the following code below and let us know if this is helpful -
>> >>
>> >> In afterPropertiesSet -
>> >>
>> >> //Handles the reconnect event, on server crashes OR network failure,
>> client
>> >> connects to server and
>> >>// destroy the cache
>> >>IgnitePredicate lsnr = iEvt -> {
>> >>LOGGER.info("Received discovery event [iEvt=" + iEvt.name()
>> +
>> >> ",
>> >> discovery=" + iEvt.shortDisplay() + ']');
>> >>
>> >>caches.keySet().forEach(key -> {
>> >>ignite.destroyCache(key);
>> >>caches.remove(key);
>> >>} );
>> >>
>> >>
>> >>
>> >> Let me know if you see any side effects with the fix.
>> >>
>> >> Thanks,
>> >> Rishi
>> >>
>> >>
>> >>
>> >> --
>> >> View this message in context: http://apache-ignite-
>> >> developers.2346864.n4.nabble.com/IGNITE-2766-Spring-Cache-
>> >> Manager-ReConnect-Issue-tp15362.html
>> >> Sent from the Apache Ignite Developers mailing list archive at
>> Nabble.com.
>> >>
>>
>
>
>
> --
> Rishi Yagnik
>



-- 
Rishi Yagnik

Re: IGNITE-2766 Spring Cache Manager ReConnect Issue

2017-03-23 Thread Rishi Yagnik

Hi Val,

Sorry for the delay, I will work on the fix on weekend.

Thanks,


On Mon, Mar 13, 2017 at 12:08 PM, Rishi Yagnik <rishiyag...@gmail.com>
wrote:

> Hi Val,
>
> I will work on it in my spare time..
>
> Take Care,
> Rishi
>
> > On Mar 13, 2017, at 10:54 AM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
> >
> > Hi Rishi,
> >
> > Can you please assign the ticket to yourself and create a pull request as
> > described in [1]?
> >
> > Let's follow the process :)
> >
> > [1] https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> >
> > -Val
> >
> > On Sun, Mar 12, 2017 at 2:04 AM, ignite_dev2017 <rishiyag...@gmail.com>
> > wrote:
> >
> >> Hi Val,
> >>
> >> The fix which we applied as follows with SpringCacheManager -
> >>
> >> 1) Design was to listen for ignite re connect event
> >> 2) And clear the cache on reconnect
> >>
> >> See the following code below and let us know if this is helpful -
> >>
> >> In afterPropertiesSet -
> >>
> >> //Handles the reconnect event, on server crashes OR network failure,
> client
> >> connects to server and
> >>// destroy the cache
> >>IgnitePredicate lsnr = iEvt -> {
> >>LOGGER.info("Received discovery event [iEvt=" + iEvt.name() +
> >> ",
> >> discovery=" + iEvt.shortDisplay() + ']');
> >>
> >>caches.keySet().forEach(key -> {
> >>ignite.destroyCache(key);
> >>caches.remove(key);
> >>} );
> >>
> >>
> >>
> >> Let me know if you see any side effects with the fix.
> >>
> >> Thanks,
> >> Rishi
> >>
> >>
> >>
> >> --
> >> View this message in context: http://apache-ignite-
> >> developers.2346864.n4.nabble.com/IGNITE-2766-Spring-Cache-
> >> Manager-ReConnect-Issue-tp15362.html
> >> Sent from the Apache Ignite Developers mailing list archive at
> Nabble.com.
> >>
>



-- 
Rishi Yagnik

Re: Apache Ignite 2.0 Release

2017-03-22 Thread Rishi Yagnik

Val knows the issue well, the web session clustering we provide does not
work on spring boot at this point however in previous discussion, Val
mentioned that the fix can be made and released in 2.0.

On Wed, Mar 22, 2017 at 1:01 PM, Dmitriy Setrakyan <dsetrak...@apache.org>
wrote:

> On Wed, Mar 22, 2017 at 10:29 AM, Rishi Yagnik <rishiyag...@gmail.com>
> wrote:
>
> > Val,
> >
> > do you think we will have a web session clustering in Ignite 2.0 ?
> >
>
> Rishi, to my knowledge, we already have web sessions clustering in Ignite:
>
>  https://apacheignite-mix.readme.io/docs/web-session-clustering
>
> Is this what you are looking for?
>

-- 
Rishi Yagnik

Re: Apache Ignite 2.0 Release

2017-03-22 Thread Rishi Yagnik

Val,

do you think we will have a web session clustering in Ignite 2.0 ?

Thanks,

On Wed, Mar 22, 2017 at 12:18 PM, Denis Magda <dma...@apache.org> wrote:

> Igniters,
>
> Branch ignite-2.0 was merged to master and removed after that.
>
> All the commits must go to master. AI 2.0 release branch will be created
> in a matter of 1-2 weeks based on final code freeze dates which we need to
> define together.
>
> I propose the timeline below:
>
> Code Freeze: April 14th, 2017
> QA and Final Benchmarking:  April 14th - April 24th, 2017
> Voting Date: April 24th, 2017.
> Release Date: April 28th, 2017.
>
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0
>
> Does anyone have any concerns?
>
>
> —
> Denis




-- 
Rishi Yagnik

Re: IGNITE-2741 - spring session design

2017-03-18 Thread Rishi Yagnik

Thanks, Val.

When are we going to release Ignite 2.0 ? June ??

Thanks,

On Sat, Mar 18, 2017 at 6:02 AM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Denis,
>
> Yes, this should be possible. I will try to finalize the fix asap.
>
> -Val
>
> On Fri, Mar 17, 2017 at 7:46 PM, Denis Magda <dma...@apache.org> wrote:
>
> > Val,
> >
> > Will it be possible to incorporate the fix into the nearest 2.0 release?
> >
> > —
> > Denis
> >
> > > On Mar 17, 2017, at 11:43 AM, Rishi Yagnik <rishiyag...@gmail.com>
> > wrote:
> > >
> > > Hi Val,
> > >
> > > Hope you are well, any update on web session clustering.
> > >
> > > Thanks,
> > > Rishi
> > >
> > > On Sat, Mar 11, 2017 at 12:29 PM, Rishi Yagnik <rishiyag...@gmail.com>
> > > wrote:
> > >
> > >> Hi Val,
> > >>
> > >> Thanks looking forward for the fix..
> > >>
> > >> Take Care,
> > >> Rishi
> > >>
> > >>> On Mar 11, 2017, at 11:31 AM, Valentin Kulichenko <
> > >> valentin.kuliche...@gmail.com> wrote:
> > >>>
> > >>> Hi Rishi,
> > >>>
> > >>> I want to fix the bug first. It takes a bit longer than I thought,
> but
> > I
> > >>> should finish it over the weekend.
> > >>>
> > >>> -Val
> > >>>
> > >>>> On Fri, Mar 10, 2017 at 4:13 AM, Rishi Yagnik <
> rishiyag...@gmail.com>
> > >> wrote:
> > >>>>
> > >>>> Hi Val,
> > >>>>
> > >>>> Did you chance to look into session handling issue ?
> > >>>>
> > >>>> Thanks,
> > >>>>
> > >>>> On Mon, Mar 6, 2017 at 3:37 PM, Rishi Yagnik <rishiyag...@gmail.com
> >
> > >>>> wrote:
> > >>>>
> > >>>>> Hi Val,
> > >>>>>
> > >>>>> Do you think I can test a fix in 1.9 RC releases ? How are you
> > planning
> > >>>> to
> > >>>>> release a fix ?
> > >>>>>
> > >>>>> Did you also look into problem where storing xsrf token in Ignite
> > >> returns
> > >>>>> an exception and does not behave as expected ?
> > >>>>>
> > >>>>> In SecurityConfig.java use HttpSessionCsrfTokenRepository with
> > >> following
> > >>>>> code -
> > >>>>>
> > >>>>> .csrfTokenRepository(csrfTokenRepository())
> > >>>>>
> > >>>>> private CsrfTokenRepository csrfTokenRepository() {
> > >>>>>   HttpSessionCsrfTokenRepository repository = new
> > >>>> HttpSessionCsrfTokenRepository();
> > >>>>>   repository.setHeaderName("X-XSRF-TOKEN");
> > >>>>>   return repository;
> > >>>>> }
> > >>>>>
> > >>>>> Thank you for all your help,
> > >>>>>
> > >>>>>
> > >>>>> On Mon, Mar 6, 2017 at 2:34 PM, Valentin Kulichenko <
> > >>>>> valentin.kuliche...@gmail.com> wrote:
> > >>>>>
> > >>>>>> Hi Rishi,
> > >>>>>>
> > >>>>>> I got to the bottom of it. Basically, the session is replaced in
> > >> Spring
> > >>>>>> filter, but caching happens based on the old version which doesn't
> > >> have
> > >>>>>> security attributes. The fix is going to be very easy, I will do
> it
> > >>>>>> tomorrow.
> > >>>>>>
> > >>>>>> -Val
> > >>>>>>
> > >>>>>> On Mon, Mar 6, 2017 at 7:34 PM, Rishi Yagnik <
> rishiyag...@gmail.com
> > >
> > >>>>>> wrote:
> > >>>>>>
> > >>>>>>> Val,
> > >>>>>>>
> > >>>>>>> Did you get chance to play around with the code ?
> > >>>>>>>
> > >>>>>>> Thanks,
> > >>>>>>>
> > >>>>>>> On Sun, Mar 5, 2017 at 7:25 PM, Rishi Yagnik <
> > rishiyag...@gmail.com>
> > >>>

Re: IGNITE-2741 - spring session design

2017-03-17 Thread Rishi Yagnik

Hi Val,

Hope you are well, any update on web session clustering.

Thanks,
Rishi

On Sat, Mar 11, 2017 at 12:29 PM, Rishi Yagnik <rishiyag...@gmail.com>
wrote:

> Hi Val,
>
> Thanks looking forward for the fix..
>
> Take Care,
> Rishi
>
> > On Mar 11, 2017, at 11:31 AM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
> >
> > Hi Rishi,
> >
> > I want to fix the bug first. It takes a bit longer than I thought, but I
> > should finish it over the weekend.
> >
> > -Val
> >
> >> On Fri, Mar 10, 2017 at 4:13 AM, Rishi Yagnik <rishiyag...@gmail.com>
> wrote:
> >>
> >> Hi Val,
> >>
> >> Did you chance to look into session handling issue ?
> >>
> >> Thanks,
> >>
> >> On Mon, Mar 6, 2017 at 3:37 PM, Rishi Yagnik <rishiyag...@gmail.com>
> >> wrote:
> >>
> >>> Hi Val,
> >>>
> >>> Do you think I can test a fix in 1.9 RC releases ? How are you planning
> >> to
> >>> release a fix ?
> >>>
> >>> Did you also look into problem where storing xsrf token in Ignite
> returns
> >>> an exception and does not behave as expected ?
> >>>
> >>> In SecurityConfig.java use HttpSessionCsrfTokenRepository with
> following
> >>> code -
> >>>
> >>> .csrfTokenRepository(csrfTokenRepository())
> >>>
> >>> private CsrfTokenRepository csrfTokenRepository() {
> >>>HttpSessionCsrfTokenRepository repository = new
> >> HttpSessionCsrfTokenRepository();
> >>>repository.setHeaderName("X-XSRF-TOKEN");
> >>>return repository;
> >>> }
> >>>
> >>> Thank you for all your help,
> >>>
> >>>
> >>> On Mon, Mar 6, 2017 at 2:34 PM, Valentin Kulichenko <
> >>> valentin.kuliche...@gmail.com> wrote:
> >>>
> >>>> Hi Rishi,
> >>>>
> >>>> I got to the bottom of it. Basically, the session is replaced in
> Spring
> >>>> filter, but caching happens based on the old version which doesn't
> have
> >>>> security attributes. The fix is going to be very easy, I will do it
> >>>> tomorrow.
> >>>>
> >>>> -Val
> >>>>
> >>>> On Mon, Mar 6, 2017 at 7:34 PM, Rishi Yagnik <rishiyag...@gmail.com>
> >>>> wrote:
> >>>>
> >>>>> Val,
> >>>>>
> >>>>> Did you get chance to play around with the code ?
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> On Sun, Mar 5, 2017 at 7:25 PM, Rishi Yagnik <rishiyag...@gmail.com>
> >>>>> wrote:
> >>>>>
> >>>>>> Val,
> >>>>>>
> >>>>>> Adding a filter before csrf filter will invoke the custom ignite
> >>>> filter.
> >>>>>>
> >>>>>> Declare a custom filter class extends it with websession filter
> >>>>>>
> >>>>>> public class CustomWebSessionFilter extends WebSessionFilter {
> >>>>>>
> >>>>>> private static boolean igniteInitialize = false
> >>>>>>
> >>>>>> @Override public void doFilter(ServletRequest req, ServletResponse
> >>>> res,
> >>>>>> FilterChain chain)
> >>>>>>throws IOException, ServletException {
> >>>>>>if(!igniteInitialize) {
> >>>>>>super.init(new FilterConfig() {
> >>>>>>@Override
> >>>>>>public String getFilterName() {
> >>>>>>return "CustomWebSessionFilter";
> >>>>>>        }
> >>>>>>
> >>>>>>@Override
> >>>>>>public ServletContext getServletContext() {
> >>>>>>return req.getServletContext();
> >>>>>>}
> >>>>>>
> >>>>>>@Override
> >>>>>>public String getInitParameter(String name) {
> >>>>>>return null;
> >>>>>>}
> >>>>>>
> >>>>

Re: IGNITE-2766 Spring Cache Manager ReConnect Issue

2017-03-13 Thread Rishi Yagnik

Hi Val,

I will work on it in my spare time..

Take Care,
Rishi

> On Mar 13, 2017, at 10:54 AM, Valentin Kulichenko 
>  wrote:
> 
> Hi Rishi,
> 
> Can you please assign the ticket to yourself and create a pull request as
> described in [1]?
> 
> Let's follow the process :)
> 
> [1] https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> 
> -Val
> 
> On Sun, Mar 12, 2017 at 2:04 AM, ignite_dev2017 
> wrote:
> 
>> Hi Val,
>> 
>> The fix which we applied as follows with SpringCacheManager -
>> 
>> 1) Design was to listen for ignite re connect event
>> 2) And clear the cache on reconnect
>> 
>> See the following code below and let us know if this is helpful -
>> 
>> In afterPropertiesSet -
>> 
>> //Handles the reconnect event, on server crashes OR network failure, client
>> connects to server and
>>// destroy the cache
>>IgnitePredicate lsnr = iEvt -> {
>>LOGGER.info("Received discovery event [iEvt=" + iEvt.name() +
>> ",
>> discovery=" + iEvt.shortDisplay() + ']');
>> 
>>caches.keySet().forEach(key -> {
>>ignite.destroyCache(key);
>>caches.remove(key);
>>} );
>> 
>> 
>> 
>> Let me know if you see any side effects with the fix.
>> 
>> Thanks,
>> Rishi
>> 
>> 
>> 
>> --
>> View this message in context: http://apache-ignite-
>> developers.2346864.n4.nabble.com/IGNITE-2766-Spring-Cache-
>> Manager-ReConnect-Issue-tp15362.html
>> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
>>

Re: IGNITE-2741 - spring session design

2017-03-11 Thread Rishi Yagnik

Hi Val, 

Thanks looking forward for the fix..

Take Care,
Rishi

> On Mar 11, 2017, at 11:31 AM, Valentin Kulichenko 
> <valentin.kuliche...@gmail.com> wrote:
> 
> Hi Rishi,
> 
> I want to fix the bug first. It takes a bit longer than I thought, but I
> should finish it over the weekend.
> 
> -Val
> 
>> On Fri, Mar 10, 2017 at 4:13 AM, Rishi Yagnik <rishiyag...@gmail.com> wrote:
>> 
>> Hi Val,
>> 
>> Did you chance to look into session handling issue ?
>> 
>> Thanks,
>> 
>> On Mon, Mar 6, 2017 at 3:37 PM, Rishi Yagnik <rishiyag...@gmail.com>
>> wrote:
>> 
>>> Hi Val,
>>> 
>>> Do you think I can test a fix in 1.9 RC releases ? How are you planning
>> to
>>> release a fix ?
>>> 
>>> Did you also look into problem where storing xsrf token in Ignite returns
>>> an exception and does not behave as expected ?
>>> 
>>> In SecurityConfig.java use HttpSessionCsrfTokenRepository with following
>>> code -
>>> 
>>> .csrfTokenRepository(csrfTokenRepository())
>>> 
>>> private CsrfTokenRepository csrfTokenRepository() {
>>>HttpSessionCsrfTokenRepository repository = new
>> HttpSessionCsrfTokenRepository();
>>>repository.setHeaderName("X-XSRF-TOKEN");
>>>return repository;
>>> }
>>> 
>>> Thank you for all your help,
>>> 
>>> 
>>> On Mon, Mar 6, 2017 at 2:34 PM, Valentin Kulichenko <
>>> valentin.kuliche...@gmail.com> wrote:
>>> 
>>>> Hi Rishi,
>>>> 
>>>> I got to the bottom of it. Basically, the session is replaced in Spring
>>>> filter, but caching happens based on the old version which doesn't have
>>>> security attributes. The fix is going to be very easy, I will do it
>>>> tomorrow.
>>>> 
>>>> -Val
>>>> 
>>>> On Mon, Mar 6, 2017 at 7:34 PM, Rishi Yagnik <rishiyag...@gmail.com>
>>>> wrote:
>>>> 
>>>>> Val,
>>>>> 
>>>>> Did you get chance to play around with the code ?
>>>>> 
>>>>> Thanks,
>>>>> 
>>>>> On Sun, Mar 5, 2017 at 7:25 PM, Rishi Yagnik <rishiyag...@gmail.com>
>>>>> wrote:
>>>>> 
>>>>>> Val,
>>>>>> 
>>>>>> Adding a filter before csrf filter will invoke the custom ignite
>>>> filter.
>>>>>> 
>>>>>> Declare a custom filter class extends it with websession filter
>>>>>> 
>>>>>> public class CustomWebSessionFilter extends WebSessionFilter {
>>>>>> 
>>>>>> private static boolean igniteInitialize = false
>>>>>> 
>>>>>> @Override public void doFilter(ServletRequest req, ServletResponse
>>>> res,
>>>>>> FilterChain chain)
>>>>>>throws IOException, ServletException {
>>>>>>if(!igniteInitialize) {
>>>>>>super.init(new FilterConfig() {
>>>>>>@Override
>>>>>>public String getFilterName() {
>>>>>>return "CustomWebSessionFilter";
>>>>>>}
>>>>>> 
>>>>>>@Override
>>>>>>public ServletContext getServletContext() {
>>>>>>return req.getServletContext();
>>>>>>}
>>>>>> 
>>>>>>@Override
>>>>>>public String getInitParameter(String name) {
>>>>>>return null;
>>>>>>}
>>>>>> 
>>>>>>@Override
>>>>>>public Enumeration getInitParameterNames() {
>>>>>>return null;
>>>>>>}
>>>>>>});
>>>>>>igniteInitialize = true;
>>>>>>}
>>>>>>super.doFilter(req,res,chain);
>>>>>>}
>>>>>> }
>>>>>> 
>>>>>> And in SecurityConfig.java add following line to invoke filter
>> before
>>>>>> Ignite Web Session filter -
>>>>>> 
&g

Re: IGNITE-2741 - spring session design

2017-03-06 Thread Rishi Yagnik

Hi Val,

Do you think I can test a fix in 1.9 RC releases ? How are you planning to
release a fix ?

Did you also look into problem where storing xsrf token in Ignite returns
an exception and does not behave as expected ?

In SecurityConfig.java use HttpSessionCsrfTokenRepository with following
code -

.csrfTokenRepository(csrfTokenRepository())

private CsrfTokenRepository csrfTokenRepository() {
HttpSessionCsrfTokenRepository repository = new
HttpSessionCsrfTokenRepository();
repository.setHeaderName("X-XSRF-TOKEN");
return repository;
}

Thank you for all your help,


On Mon, Mar 6, 2017 at 2:34 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Hi Rishi,
>
> I got to the bottom of it. Basically, the session is replaced in Spring
> filter, but caching happens based on the old version which doesn't have
> security attributes. The fix is going to be very easy, I will do it
> tomorrow.
>
> -Val
>
> On Mon, Mar 6, 2017 at 7:34 PM, Rishi Yagnik <rishiyag...@gmail.com>
> wrote:
>
> > Val,
> >
> > Did you get chance to play around with the code ?
> >
> > Thanks,
> >
> > On Sun, Mar 5, 2017 at 7:25 PM, Rishi Yagnik <rishiyag...@gmail.com>
> > wrote:
> >
> > > Val,
> > >
> > > Adding a filter before csrf filter will invoke the custom ignite
> filter.
> > >
> > > Declare a custom filter class extends it with websession filter
> > >
> > > public class CustomWebSessionFilter extends WebSessionFilter {
> > >
> > >  private static boolean igniteInitialize = false
> > >
> > > @Override public void doFilter(ServletRequest req, ServletResponse res,
> > > FilterChain chain)
> > > throws IOException, ServletException {
> > > if(!igniteInitialize) {
> > > super.init(new FilterConfig() {
> > > @Override
> > > public String getFilterName() {
> > > return "CustomWebSessionFilter";
> > > }
> > >
> > > @Override
> > > public ServletContext getServletContext() {
> > > return req.getServletContext();
> > > }
> > >
> > > @Override
> > > public String getInitParameter(String name) {
> > > return null;
> > > }
> > >
> > > @Override
> > > public Enumeration getInitParameterNames() {
> > > return null;
> > > }
> > > });
> > > igniteInitialize = true;
> > > }
> > > super.doFilter(req,res,chain);
> > > }
> > > }
> > >
> > > And in SecurityConfig.java add following line to invoke filter before
> > > Ignite Web Session filter -
> > >
> > >  .addFilterBefore(new ArWebSessionFilter(), CsrfFilter.class)
> > >
> > > Hope it helps..
> > >
> > > Thanks,
> > >
> > > On Sun, Mar 5, 2017 at 1:28 PM, Valentin Kulichenko <
> > > valentin.kuliche...@gmail.com> wrote:
> > >
> > >> Rishi,
> > >>
> > >> Can you please share how you forced Ignite filter to be invoked before
> > >> security filter?
> > >>
> > >> -Val
> > >>
> > >> On Sun, Mar 5, 2017 at 11:20 AM, Rishi Yagnik <rishiyag...@gmail.com>
> > >> wrote:
> > >>
> > >> > Hi Val,
> > >> >
> > >> > Thanks for the response, we have executed ignite filter before
> spring
> > >> > security filter but somehow the ignite filter does not do the job of
> > >> > setting spring principle context.
> > >> >
> > >> > As a result even though we have spring principle in session, spring
> > >> filter
> > >> > does not recognize it and sends us back to log in page.
> > >> >
> > >> > I think there s some more work needed here to change the filter and
> > make
> > >> > it work with spring boot application.
> > >> >
> > >> > Take Care,
> > >> > Rishi
> > >> >
> > >> > > On Mar 5, 2017, at 10:16 AM, Valentin Kulichenko <
> > >> > valentin.kuliche...@gmail.com> wrote:
> > >> > >
> > >>

Re: IGNITE-2741 - spring session design

2017-03-06 Thread Rishi Yagnik

Val,

Did you get chance to play around with the code ?

Thanks,

On Sun, Mar 5, 2017 at 7:25 PM, Rishi Yagnik <rishiyag...@gmail.com> wrote:

> Val,
>
> Adding a filter before csrf filter will invoke the custom ignite filter.
>
> Declare a custom filter class extends it with websession filter
>
> public class CustomWebSessionFilter extends WebSessionFilter {
>
>  private static boolean igniteInitialize = false
>
> @Override public void doFilter(ServletRequest req, ServletResponse res,
> FilterChain chain)
> throws IOException, ServletException {
> if(!igniteInitialize) {
> super.init(new FilterConfig() {
> @Override
> public String getFilterName() {
> return "CustomWebSessionFilter";
> }
>
> @Override
> public ServletContext getServletContext() {
> return req.getServletContext();
> }
>
> @Override
> public String getInitParameter(String name) {
> return null;
> }
>
> @Override
> public Enumeration getInitParameterNames() {
> return null;
> }
> });
> igniteInitialize = true;
> }
> super.doFilter(req,res,chain);
> }
> }
>
> And in SecurityConfig.java add following line to invoke filter before
> Ignite Web Session filter -
>
>  .addFilterBefore(new ArWebSessionFilter(), CsrfFilter.class)
>
> Hope it helps..
>
> Thanks,
>
> On Sun, Mar 5, 2017 at 1:28 PM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
>> Rishi,
>>
>> Can you please share how you forced Ignite filter to be invoked before
>> security filter?
>>
>> -Val
>>
>> On Sun, Mar 5, 2017 at 11:20 AM, Rishi Yagnik <rishiyag...@gmail.com>
>> wrote:
>>
>> > Hi Val,
>> >
>> > Thanks for the response, we have executed ignite filter before spring
>> > security filter but somehow the ignite filter does not do the job of
>> > setting spring principle context.
>> >
>> > As a result even though we have spring principle in session, spring
>> filter
>> > does not recognize it and sends us back to log in page.
>> >
>> > I think there s some more work needed here to change the filter and make
>> > it work with spring boot application.
>> >
>> > Take Care,
>> > Rishi
>> >
>> > > On Mar 5, 2017, at 10:16 AM, Valentin Kulichenko <
>> > valentin.kuliche...@gmail.com> wrote:
>> > >
>> > > Hi Rishi,
>> > >
>> > > I did some debugging. Apparently, the reason for this behavior is that
>> > > Spring Security filter resides before Ignite's filter in the chain
>> list.
>> > I
>> > > think that eventually this should be fixed in the product, but in the
>> > > meantime there must be a way to work around the problem by controlling
>> > the
>> > > order. Do you know how this can be done in Spring Boot?
>> > >
>> > > -Val
>> > >
>> > >> On Tue, Feb 28, 2017 at 9:31 AM, Rishi Yagnik <rishiyag...@gmail.com
>> >
>> > wrote:
>> > >>
>> > >> Hi Val,
>> > >>
>> > >> Sorry for pestering, thanks for all your help.
>> > >>
>> > >> Rishi
>> > >>
>> > >> On Mon, Feb 27, 2017 at 7:22 PM, Valentin Kulichenko <
>> > >> valentin.kuliche...@gmail.com> wrote:
>> > >>
>> > >>> Hi Rishi,
>> > >>>
>> > >>> Sorry, not yet. But this on my short list of TODOs, will try to
>> give an
>> > >>> update as soon as possible.
>> > >>>
>> > >>> -Val
>> > >>>
>> > >>> On Mon, Feb 27, 2017 at 7:47 AM, Rishi Yagnik <
>> rishiyag...@gmail.com>
>> > >>> wrote:
>> > >>>
>> > >>>> Hi Val,
>> > >>>>
>> > >>>> any update on session replication issue ?
>> > >>>>
>> > >>>> Thanks,
>> > >>>> Rishi
>> > >>>>
>> > >>>> On Thu, Feb 23, 2017 at 8:07 AM, Rishi Yagnik <
>> rishiyag...@gmail.com>
>> > >>>

Re: IGNITE-2741 - spring session design

2017-03-05 Thread Rishi Yagnik

Val,

Adding a filter before csrf filter will invoke the custom ignite filter.

Declare a custom filter class extends it with websession filter

public class CustomWebSessionFilter extends WebSessionFilter {

 private static boolean igniteInitialize = false

@Override public void doFilter(ServletRequest req, ServletResponse res,
FilterChain chain)
throws IOException, ServletException {
if(!igniteInitialize) {
super.init(new FilterConfig() {
@Override
public String getFilterName() {
return "CustomWebSessionFilter";
}

@Override
public ServletContext getServletContext() {
return req.getServletContext();
}

@Override
public String getInitParameter(String name) {
return null;
}

@Override
public Enumeration getInitParameterNames() {
return null;
}
});
igniteInitialize = true;
}
super.doFilter(req,res,chain);
}
}

And in SecurityConfig.java add following line to invoke filter before
Ignite Web Session filter -

 .addFilterBefore(new ArWebSessionFilter(), CsrfFilter.class)

Hope it helps..

Thanks,

On Sun, Mar 5, 2017 at 1:28 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Rishi,
>
> Can you please share how you forced Ignite filter to be invoked before
> security filter?
>
> -Val
>
> On Sun, Mar 5, 2017 at 11:20 AM, Rishi Yagnik <rishiyag...@gmail.com>
> wrote:
>
> > Hi Val,
> >
> > Thanks for the response, we have executed ignite filter before spring
> > security filter but somehow the ignite filter does not do the job of
> > setting spring principle context.
> >
> > As a result even though we have spring principle in session, spring
> filter
> > does not recognize it and sends us back to log in page.
> >
> > I think there s some more work needed here to change the filter and make
> > it work with spring boot application.
> >
> > Take Care,
> > Rishi
> >
> > > On Mar 5, 2017, at 10:16 AM, Valentin Kulichenko <
> > valentin.kuliche...@gmail.com> wrote:
> > >
> > > Hi Rishi,
> > >
> > > I did some debugging. Apparently, the reason for this behavior is that
> > > Spring Security filter resides before Ignite's filter in the chain
> list.
> > I
> > > think that eventually this should be fixed in the product, but in the
> > > meantime there must be a way to work around the problem by controlling
> > the
> > > order. Do you know how this can be done in Spring Boot?
> > >
> > > -Val
> > >
> > >> On Tue, Feb 28, 2017 at 9:31 AM, Rishi Yagnik <rishiyag...@gmail.com>
> > wrote:
> > >>
> > >> Hi Val,
> > >>
> > >> Sorry for pestering, thanks for all your help.
> > >>
> > >> Rishi
> > >>
> > >> On Mon, Feb 27, 2017 at 7:22 PM, Valentin Kulichenko <
> > >> valentin.kuliche...@gmail.com> wrote:
> > >>
> > >>> Hi Rishi,
> > >>>
> > >>> Sorry, not yet. But this on my short list of TODOs, will try to give
> an
> > >>> update as soon as possible.
> > >>>
> > >>> -Val
> > >>>
> > >>> On Mon, Feb 27, 2017 at 7:47 AM, Rishi Yagnik <rishiyag...@gmail.com
> >
> > >>> wrote:
> > >>>
> > >>>> Hi Val,
> > >>>>
> > >>>> any update on session replication issue ?
> > >>>>
> > >>>> Thanks,
> > >>>> Rishi
> > >>>>
> > >>>> On Thu, Feb 23, 2017 at 8:07 AM, Rishi Yagnik <
> rishiyag...@gmail.com>
> > >>>> wrote:
> > >>>>
> > >>>>> Thanks Val for looking into it.
> > >>>>>
> > >>>>> On Wed, Feb 22, 2017 at 9:32 PM, Valentin Kulichenko <
> > >>>>> valentin.kuliche...@gmail.com> wrote:
> > >>>>>
> > >>>>>> Hi Rishi,
> > >>>>>>
> > >>>>>> Got it, I think I'm reproducing the issue. I'll take a look and
> let
> > >>> you
> > >>>>>> know my findings soon.
> > >>>>>>
> > >>>>>> -Val
> > >>>>>>
> > >>>>&

Re: IGNITE-2741 - spring session design

2017-02-28 Thread Rishi Yagnik

Hi Val,

Sorry for pestering, thanks for all your help.

Rishi

On Mon, Feb 27, 2017 at 7:22 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Hi Rishi,
>
> Sorry, not yet. But this on my short list of TODOs, will try to give an
> update as soon as possible.
>
> -Val
>
> On Mon, Feb 27, 2017 at 7:47 AM, Rishi Yagnik <rishiyag...@gmail.com>
> wrote:
>
> > Hi Val,
> >
> > any update on session replication issue ?
> >
> > Thanks,
> > Rishi
> >
> > On Thu, Feb 23, 2017 at 8:07 AM, Rishi Yagnik <rishiyag...@gmail.com>
> > wrote:
> >
> > > Thanks Val for looking into it.
> > >
> > > On Wed, Feb 22, 2017 at 9:32 PM, Valentin Kulichenko <
> > > valentin.kuliche...@gmail.com> wrote:
> > >
> > >> Hi Rishi,
> > >>
> > >> Got it, I think I'm reproducing the issue. I'll take a look and let
> you
> > >> know my findings soon.
> > >>
> > >> -Val
> > >>
> > >> On Tue, Feb 21, 2017 at 7:27 PM, Rishi Yagnik <rishiyag...@gmail.com>
> > >> wrote:
> > >>
> > >> > Hi Val,
> > >> >
> > >> > The issue will occur in cluster environment, please setup the spring
> > >> boot
> > >> > on 2 different host with LB (F5 OR Reverse proxy) in front and try
> to
> > >> > login.
> > >> >
> > >> > In cluster environment, Spring security does not recognize the
> session
> > >> on
> > >> > the host you are not logged in, as a result, spring security will
> > >> redirect
> > >> > to login url however the correct behavior should be that user would
> > stay
> > >> > logged in with session replication.
> > >> >
> > >> > Do let me know if you need more information.
> > >> >
> > >> > Thanks,
> > >> > Rishi
> > >> >
> > >> >
> > >> >
> > >> > On Tue, Feb 21, 2017 at 7:08 PM, Valentin Kulichenko <
> > >> > valentin.kuliche...@gmail.com> wrote:
> > >> >
> > >> > > Hi Rishi,
> > >> > >
> > >> > > I was able to build and run the application. Can you give some
> > >> > description
> > >> > > on what should I test to understand the issue? What exactly didn't
> > >> work
> > >> > for
> > >> > > you?
> > >> > >
> > >> > > -Val
> > >> > >
> > >> > > On Wed, Feb 15, 2017 at 10:52 AM, Valentin Kulichenko <
> > >> > > valentin.kuliche...@gmail.com> wrote:
> > >> > >
> > >> > > > Hi Rishi,
> > >> > > >
> > >> > > > Thanks, I'll take a look.
> > >> > > >
> > >> > > > -Val
> > >> > > >
> > >> > > > On Wed, Feb 15, 2017 at 9:07 AM, Rishi Yagnik <
> > >> rishiyag...@gmail.com>
> > >> > > > wrote:
> > >> > > >
> > >> > > >> Hi Val,
> > >> > > >>
> > >> > > >> As promised, please find attached code for spring boot
> > integration
> > >> > with
> > >> > > >> spring security along with Ignite.
> > >> > > >>
> > >> > > >> Some more information on project -
> > >> > > >>
> > >> > > >>- It is a maven project ( Ignite 1.7.0, SB 1.4.3 )
> > >> > > >>- spring security integrated with boot project along with
> > ignite
> > >> > > >>- HttpSessionCookieCsrfTokenRepository does not work, gives
> > >> > > >>intermediate errors on single instance so used
> > >> > > CookieCsrfTokenRepository
> > >> > > >>for CSRF token, again I think we need a fix here from
> Ignite.
> > >> > > >>
> > >> > > >> I cant reproduce this errors while I am running on single
> > instance,
> > >> > you
> > >> > > >> need to run this app on 2 spring boot instance having proxy in
> > >> front (
> > >> > > F5,
> > >> > > >> OR any proxy ) with round robin fashion ( no sticky session on
> F5
>

Re: IGNITE-2741 - spring session design

2017-02-27 Thread Rishi Yagnik

Hi Val,

any update on session replication issue ?

Thanks,
Rishi

On Thu, Feb 23, 2017 at 8:07 AM, Rishi Yagnik <rishiyag...@gmail.com> wrote:

> Thanks Val for looking into it.
>
> On Wed, Feb 22, 2017 at 9:32 PM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
>> Hi Rishi,
>>
>> Got it, I think I'm reproducing the issue. I'll take a look and let you
>> know my findings soon.
>>
>> -Val
>>
>> On Tue, Feb 21, 2017 at 7:27 PM, Rishi Yagnik <rishiyag...@gmail.com>
>> wrote:
>>
>> > Hi Val,
>> >
>> > The issue will occur in cluster environment, please setup the spring
>> boot
>> > on 2 different host with LB (F5 OR Reverse proxy) in front and try to
>> > login.
>> >
>> > In cluster environment, Spring security does not recognize the session
>> on
>> > the host you are not logged in, as a result, spring security will
>> redirect
>> > to login url however the correct behavior should be that user would stay
>> > logged in with session replication.
>> >
>> > Do let me know if you need more information.
>> >
>> > Thanks,
>> > Rishi
>> >
>> >
>> >
>> > On Tue, Feb 21, 2017 at 7:08 PM, Valentin Kulichenko <
>> > valentin.kuliche...@gmail.com> wrote:
>> >
>> > > Hi Rishi,
>> > >
>> > > I was able to build and run the application. Can you give some
>> > description
>> > > on what should I test to understand the issue? What exactly didn't
>> work
>> > for
>> > > you?
>> > >
>> > > -Val
>> > >
>> > > On Wed, Feb 15, 2017 at 10:52 AM, Valentin Kulichenko <
>> > > valentin.kuliche...@gmail.com> wrote:
>> > >
>> > > > Hi Rishi,
>> > > >
>> > > > Thanks, I'll take a look.
>> > > >
>> > > > -Val
>> > > >
>> > > > On Wed, Feb 15, 2017 at 9:07 AM, Rishi Yagnik <
>> rishiyag...@gmail.com>
>> > > > wrote:
>> > > >
>> > > >> Hi Val,
>> > > >>
>> > > >> As promised, please find attached code for spring boot integration
>> > with
>> > > >> spring security along with Ignite.
>> > > >>
>> > > >> Some more information on project -
>> > > >>
>> > > >>- It is a maven project ( Ignite 1.7.0, SB 1.4.3 )
>> > > >>- spring security integrated with boot project along with ignite
>> > > >>- HttpSessionCookieCsrfTokenRepository does not work, gives
>> > > >>intermediate errors on single instance so used
>> > > CookieCsrfTokenRepository
>> > > >>for CSRF token, again I think we need a fix here from Ignite.
>> > > >>
>> > > >> I cant reproduce this errors while I am running on single instance,
>> > you
>> > > >> need to run this app on 2 spring boot instance having proxy in
>> front (
>> > > F5,
>> > > >> OR any proxy ) with round robin fashion ( no sticky session on F5
>> OR
>> > > >> proxies ).
>> > > >>
>> > > >> We were thinking with round robin the user session will active
>> since
>> > we
>> > > >> used session replication on backend.
>> > > >>
>> > > >> Do let me know if you need more information here.
>> > > >>
>> > > >> Thanks,
>> > > >>
>> > > >> Rishi
>> > > >>
>> > > >>
>> > > >>
>> > > >>
>> > > >> On Tue, Feb 14, 2017 at 9:57 PM, Rishi Yagnik <
>> rishiyag...@gmail.com>
>> > > >> wrote:
>> > > >>
>> > > >>> Val,
>> > > >>>
>> > > >>> My SB sample project is ready however I have asked for an
>> approval to
>> > > >>> submit sample project to you, it would take day or two.
>> > > >>>
>> > > >>> I will keep you posted.
>> > > >>>
>> > > >>> Thanks for all your help,
>> > > >>>
>> > > >>> On Tue, Feb 14, 2017 at 3:51 PM, Rishi Yagnik <
>> rishiyag...@gmail.com
>> > >
>> > &

Re: IGNITE-2741 - spring session design

2017-02-23 Thread Rishi Yagnik

Thanks Val for looking into it.

On Wed, Feb 22, 2017 at 9:32 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Hi Rishi,
>
> Got it, I think I'm reproducing the issue. I'll take a look and let you
> know my findings soon.
>
> -Val
>
> On Tue, Feb 21, 2017 at 7:27 PM, Rishi Yagnik <rishiyag...@gmail.com>
> wrote:
>
> > Hi Val,
> >
> > The issue will occur in cluster environment, please setup the spring boot
> > on 2 different host with LB (F5 OR Reverse proxy) in front and try to
> > login.
> >
> > In cluster environment, Spring security does not recognize the session on
> > the host you are not logged in, as a result, spring security will
> redirect
> > to login url however the correct behavior should be that user would stay
> > logged in with session replication.
> >
> > Do let me know if you need more information.
> >
> > Thanks,
> > Rishi
> >
> >
> >
> > On Tue, Feb 21, 2017 at 7:08 PM, Valentin Kulichenko <
> > valentin.kuliche...@gmail.com> wrote:
> >
> > > Hi Rishi,
> > >
> > > I was able to build and run the application. Can you give some
> > description
> > > on what should I test to understand the issue? What exactly didn't work
> > for
> > > you?
> > >
> > > -Val
> > >
> > > On Wed, Feb 15, 2017 at 10:52 AM, Valentin Kulichenko <
> > > valentin.kuliche...@gmail.com> wrote:
> > >
> > > > Hi Rishi,
> > > >
> > > > Thanks, I'll take a look.
> > > >
> > > > -Val
> > > >
> > > > On Wed, Feb 15, 2017 at 9:07 AM, Rishi Yagnik <rishiyag...@gmail.com
> >
> > > > wrote:
> > > >
> > > >> Hi Val,
> > > >>
> > > >> As promised, please find attached code for spring boot integration
> > with
> > > >> spring security along with Ignite.
> > > >>
> > > >> Some more information on project -
> > > >>
> > > >>- It is a maven project ( Ignite 1.7.0, SB 1.4.3 )
> > > >>- spring security integrated with boot project along with ignite
> > > >>- HttpSessionCookieCsrfTokenRepository does not work, gives
> > > >>intermediate errors on single instance so used
> > > CookieCsrfTokenRepository
> > > >>for CSRF token, again I think we need a fix here from Ignite.
> > > >>
> > > >> I cant reproduce this errors while I am running on single instance,
> > you
> > > >> need to run this app on 2 spring boot instance having proxy in
> front (
> > > F5,
> > > >> OR any proxy ) with round robin fashion ( no sticky session on F5 OR
> > > >> proxies ).
> > > >>
> > > >> We were thinking with round robin the user session will active since
> > we
> > > >> used session replication on backend.
> > > >>
> > > >> Do let me know if you need more information here.
> > > >>
> > > >> Thanks,
> > > >>
> > > >> Rishi
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> On Tue, Feb 14, 2017 at 9:57 PM, Rishi Yagnik <
> rishiyag...@gmail.com>
> > > >> wrote:
> > > >>
> > > >>> Val,
> > > >>>
> > > >>> My SB sample project is ready however I have asked for an approval
> to
> > > >>> submit sample project to you, it would take day or two.
> > > >>>
> > > >>> I will keep you posted.
> > > >>>
> > > >>> Thanks for all your help,
> > > >>>
> > > >>> On Tue, Feb 14, 2017 at 3:51 PM, Rishi Yagnik <
> rishiyag...@gmail.com
> > >
> > > >>> wrote:
> > > >>>
> > > >>>> Let me build an example app for you and send it across to you.
> > > >>>>
> > > >>>> Thanks,
> > > >>>>
> > > >>>> On Tue, Feb 14, 2017 at 3:28 PM, Valentin Kulichenko <
> > > >>>> valentin.kuliche...@gmail.com> wrote:
> > > >>>>
> > > >>>>> Rishi,
> > > >>>>>
> > > >>>>> No I don't, and I think that's what we should start with. I want
> to
> > > >>>>> unde

Re: IGNITE-2741 - spring session design

2017-02-21 Thread Rishi Yagnik

Hi Val,

The issue will occur in cluster environment, please setup the spring boot
on 2 different host with LB (F5 OR Reverse proxy) in front and try to login.

In cluster environment, Spring security does not recognize the session on
the host you are not logged in, as a result, spring security will redirect
to login url however the correct behavior should be that user would stay
logged in with session replication.

Do let me know if you need more information.

Thanks,
Rishi



On Tue, Feb 21, 2017 at 7:08 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Hi Rishi,
>
> I was able to build and run the application. Can you give some description
> on what should I test to understand the issue? What exactly didn't work for
> you?
>
> -Val
>
> On Wed, Feb 15, 2017 at 10:52 AM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > Hi Rishi,
> >
> > Thanks, I'll take a look.
> >
> > -Val
> >
> > On Wed, Feb 15, 2017 at 9:07 AM, Rishi Yagnik <rishiyag...@gmail.com>
> > wrote:
> >
> >> Hi Val,
> >>
> >> As promised, please find attached code for spring boot integration with
> >> spring security along with Ignite.
> >>
> >> Some more information on project -
> >>
> >>- It is a maven project ( Ignite 1.7.0, SB 1.4.3 )
> >>- spring security integrated with boot project along with ignite
> >>- HttpSessionCookieCsrfTokenRepository does not work, gives
> >>intermediate errors on single instance so used
> CookieCsrfTokenRepository
> >>for CSRF token, again I think we need a fix here from Ignite.
> >>
> >> I cant reproduce this errors while I am running on single instance, you
> >> need to run this app on 2 spring boot instance having proxy in front (
> F5,
> >> OR any proxy ) with round robin fashion ( no sticky session on F5 OR
> >> proxies ).
> >>
> >> We were thinking with round robin the user session will active since we
> >> used session replication on backend.
> >>
> >> Do let me know if you need more information here.
> >>
> >> Thanks,
> >>
> >> Rishi
> >>
> >>
> >>
> >>
> >> On Tue, Feb 14, 2017 at 9:57 PM, Rishi Yagnik <rishiyag...@gmail.com>
> >> wrote:
> >>
> >>> Val,
> >>>
> >>> My SB sample project is ready however I have asked for an approval to
> >>> submit sample project to you, it would take day or two.
> >>>
> >>> I will keep you posted.
> >>>
> >>> Thanks for all your help,
> >>>
> >>> On Tue, Feb 14, 2017 at 3:51 PM, Rishi Yagnik <rishiyag...@gmail.com>
> >>> wrote:
> >>>
> >>>> Let me build an example app for you and send it across to you.
> >>>>
> >>>> Thanks,
> >>>>
> >>>> On Tue, Feb 14, 2017 at 3:28 PM, Valentin Kulichenko <
> >>>> valentin.kuliche...@gmail.com> wrote:
> >>>>
> >>>>> Rishi,
> >>>>>
> >>>>> No I don't, and I think that's what we should start with. I want to
> >>>>> understand a use case that is currently not supported (if any) and
> then
> >>>>> find the best solution. And I would like to reuse existing code as
> >>>>> much as
> >>>>> possible.
> >>>>>
> >>>>> Do you have any code that reproduces the problem you had and how you
> >>>>> tried
> >>>>> to utilize current web session clustering? Can you share it with us?
> >>>>>
> >>>>> -Val
> >>>>>
> >>>>> On Tue, Feb 14, 2017 at 11:28 AM, Rishi Yagnik <
> rishiyag...@gmail.com>
> >>>>> wrote:
> >>>>>
> >>>>> > Hi Val,
> >>>>> >
> >>>>> > I am working on SB platform with spring security and we found out
> >>>>> that the
> >>>>> > web session filter ignite provides does not work for session
> >>>>> management on
> >>>>> > 2 node spring boot cluster.
> >>>>> >
> >>>>> > Somehow, spring security filter kicks in result in some weird
> errors
> >>>>> with
> >>>>> > web session filter.
> >>>>> >
> >>>>> > So making compatible with spring security som

Re: IGNITE-2741 - spring session design

2017-02-14 Thread Rishi Yagnik

Val,

My SB sample project is ready however I have asked for an approval to
submit sample project to you, it would take day or two.

I will keep you posted.

Thanks for all your help,

On Tue, Feb 14, 2017 at 3:51 PM, Rishi Yagnik <rishiyag...@gmail.com> wrote:

> Let me build an example app for you and send it across to you.
>
> Thanks,
>
> On Tue, Feb 14, 2017 at 3:28 PM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
>> Rishi,
>>
>> No I don't, and I think that's what we should start with. I want to
>> understand a use case that is currently not supported (if any) and then
>> find the best solution. And I would like to reuse existing code as much as
>> possible.
>>
>> Do you have any code that reproduces the problem you had and how you tried
>> to utilize current web session clustering? Can you share it with us?
>>
>> -Val
>>
>> On Tue, Feb 14, 2017 at 11:28 AM, Rishi Yagnik <rishiyag...@gmail.com>
>> wrote:
>>
>> > Hi Val,
>> >
>> > I am working on SB platform with spring security and we found out that
>> the
>> > web session filter ignite provides does not work for session management
>> on
>> > 2 node spring boot cluster.
>> >
>> > Somehow, spring security filter kicks in result in some weird errors
>> with
>> > web session filter.
>> >
>> > So making compatible with spring security somehow, we need to write
>> > implementation on spring session.
>> >
>> > Do you have any test cases that says web session filter would work with
>> > spring security on boot platform ?
>> >
>> > Thanks,
>> >
>> >
>> > On Tue, Feb 14, 2017 at 1:03 PM, Valentin Kulichenko <
>> > valentin.kuliche...@gmail.com> wrote:
>> >
>> > > Hi Rishi,
>> > >
>> > > Can you please take a look at web session clustering feature [1]
>> provided
>> > > by Ignite? I'm looking at Spring Session docs and it seems to me it
>> does
>> > > exactly the same - replaces HttpSession with custom implementation
>> that
>> > has
>> > > a backend storage. If it doesn't provide any additional API or
>> > > functionality, I'm not sure I understand the benefit of this feature.
>> > >
>> > > Let me know if I'm missing something.
>> > >
>> > > [1] https://apacheignite-mix.readme.io/docs/web-session-clustering
>> > >
>> > > -Val
>> > >
>> > > On Mon, Feb 13, 2017 at 2:41 PM, Rishi Yagnik <rishiyag...@gmail.com>
>> > > wrote:
>> > >
>> > > > I would like to discuss session replication / fail over design on
>> > spring
>> > > > boot platform and wanted to find what is the best out to get started
>> > > here ?
>> > > >
>> > > > Possible approaches are as follows -
>> > > >
>> > > >- Make use of Spring Session for session replication and fail
>> over
>> > > >- Extend the web session filter and make it work on spring boot
>> > > >application
>> > > >
>> > > >
>> > > > I am thinking that best approach would be to get started here with
>> > spring
>> > > > session design however I am open for feedback here.
>> > > >
>> > > > --
>> > > > Rishi Yagnik
>> > > >
>> > >
>> >
>> >
>> >
>> > --
>> > Rishi Yagnik
>> >
>>
>
>
>
> --
> Rishi Yagnik
>



-- 
Rishi Yagnik

Re: IGNITE-2741 - spring session design

2017-02-14 Thread Rishi Yagnik

Let me build an example app for you and send it across to you.

Thanks,

On Tue, Feb 14, 2017 at 3:28 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Rishi,
>
> No I don't, and I think that's what we should start with. I want to
> understand a use case that is currently not supported (if any) and then
> find the best solution. And I would like to reuse existing code as much as
> possible.
>
> Do you have any code that reproduces the problem you had and how you tried
> to utilize current web session clustering? Can you share it with us?
>
> -Val
>
> On Tue, Feb 14, 2017 at 11:28 AM, Rishi Yagnik <rishiyag...@gmail.com>
> wrote:
>
> > Hi Val,
> >
> > I am working on SB platform with spring security and we found out that
> the
> > web session filter ignite provides does not work for session management
> on
> > 2 node spring boot cluster.
> >
> > Somehow, spring security filter kicks in result in some weird errors with
> > web session filter.
> >
> > So making compatible with spring security somehow, we need to write
> > implementation on spring session.
> >
> > Do you have any test cases that says web session filter would work with
> > spring security on boot platform ?
> >
> > Thanks,
> >
> >
> > On Tue, Feb 14, 2017 at 1:03 PM, Valentin Kulichenko <
> > valentin.kuliche...@gmail.com> wrote:
> >
> > > Hi Rishi,
> > >
> > > Can you please take a look at web session clustering feature [1]
> provided
> > > by Ignite? I'm looking at Spring Session docs and it seems to me it
> does
> > > exactly the same - replaces HttpSession with custom implementation that
> > has
> > > a backend storage. If it doesn't provide any additional API or
> > > functionality, I'm not sure I understand the benefit of this feature.
> > >
> > > Let me know if I'm missing something.
> > >
> > > [1] https://apacheignite-mix.readme.io/docs/web-session-clustering
> > >
> > > -Val
> > >
> > > On Mon, Feb 13, 2017 at 2:41 PM, Rishi Yagnik <rishiyag...@gmail.com>
> > > wrote:
> > >
> > > > I would like to discuss session replication / fail over design on
> > spring
> > > > boot platform and wanted to find what is the best out to get started
> > > here ?
> > > >
> > > > Possible approaches are as follows -
> > > >
> > > >- Make use of Spring Session for session replication and fail over
> > > >- Extend the web session filter and make it work on spring boot
> > > >application
> > > >
> > > >
> > > > I am thinking that best approach would be to get started here with
> > spring
> > > > session design however I am open for feedback here.
> > > >
> > > > --
> > > > Rishi Yagnik
> > > >
> > >
> >
> >
> >
> > --
> > Rishi Yagnik
> >
>



-- 
Rishi Yagnik

Re: IGNITE-2741 - spring session design

2017-02-14 Thread Rishi Yagnik

Hi Val,

I am working on SB platform with spring security and we found out that the
web session filter ignite provides does not work for session management on
2 node spring boot cluster.

Somehow, spring security filter kicks in result in some weird errors with
web session filter.

So making compatible with spring security somehow, we need to write
implementation on spring session.

Do you have any test cases that says web session filter would work with
spring security on boot platform ?

Thanks,


On Tue, Feb 14, 2017 at 1:03 PM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:

> Hi Rishi,
>
> Can you please take a look at web session clustering feature [1] provided
> by Ignite? I'm looking at Spring Session docs and it seems to me it does
> exactly the same - replaces HttpSession with custom implementation that has
> a backend storage. If it doesn't provide any additional API or
> functionality, I'm not sure I understand the benefit of this feature.
>
> Let me know if I'm missing something.
>
> [1] https://apacheignite-mix.readme.io/docs/web-session-clustering
>
> -Val
>
> On Mon, Feb 13, 2017 at 2:41 PM, Rishi Yagnik <rishiyag...@gmail.com>
> wrote:
>
> > I would like to discuss session replication / fail over design on spring
> > boot platform and wanted to find what is the best out to get started
> here ?
> >
> > Possible approaches are as follows -
> >
> >- Make use of Spring Session for session replication and fail over
> >- Extend the web session filter and make it work on spring boot
> >application
> >
> >
> > I am thinking that best approach would be to get started here with spring
> > session design however I am open for feedback here.
> >
> > --
> > Rishi Yagnik
> >
>



-- 
Rishi Yagnik

New Joinee

2016-07-13 Thread Rishi Yagnik

Hello Everybody,

I would like to participate in Ignite Development so do provide your guidance 
to kick start my development.

Thanks,

Take Care,
___
RISHI YAGNIK | PDX, Inc.
Architect, Enterprise Architecture Team
Asserting the Role of Pharmacy in Healthcare  
www.pdxinc.com<http://www.pdxinc.com/>  |  www.rx.com<http://www.rx.com/>
main: 817-367-4540 | x4540 | mobile: 614-905-0636

101 Jim Wright Freeway South, Suite 200, Fort Worth, Texas 
76108-2202<http://maps.google.com/maps?q=PDX,+Inc.=en=32.758696,-97.476397=0.006295,0.006295=0=1=h=17=A>

P Please consider the environment before printing this email.


This e-mail and its contents (to include attachments) are the property of 
National Health Systems, Inc., its subsidiaries and affiliates, including but 
not limited to Rx.com Community Healthcare Network, Inc. and its subsidiaries, 
and may contain confidential and proprietary or privileged information. If you 
are not the intended recipient of this e-mail, you are hereby notified that any 
unauthorized disclosure, copying, or distribution of this e-mail or of its 
attachments, or the taking of any unauthorized action based on information 
contained herein is strictly prohibited. Unauthorized use of information 
contained herein may subject you to civil and criminal prosecution and 
penalties. If you are not the intended recipient, please immediately notify the 
sender by telephone at 800-433-5719 or return e-mail and permanently delete the 
original e-mail.

40 matches

Mail list logo