[
https://issues.apache.org/jira/browse/UNOMI-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15885594#comment-15885594
]
Serge Huber commented on UNOMI-82:
----------------------------------
Yes, one way to do it could be to either store the sessionId in a cookie, or in
the sessionStorage of the browser. As for applications such as mobile
applications they should map session lifecycle with "user interactions".
cheers,
Serge...
> Same profileId associated with different sessions (different users)
> -------------------------------------------------------------------
>
> Key: UNOMI-82
> URL: https://issues.apache.org/jira/browse/UNOMI-82
> Project: Apache Unomi
> Issue Type: Bug
> Components: core
> Affects Versions: 1.2.0-incubating
> Environment: Ubuntu 14.04, ES 5.2 cluster, two EC2 instances behind
> an ELB
> Reporter: Damon Henry
> Fix For: 1.2.0-incubating
>
>
> During testing we've noticed, in some instances, the same profileId is
> associated with large numbers of sessions when calling the
> /profiles/search/sessions endpoint as if the profileId is being cached. The
> sessionCity (and other geo attributes) indicate the sessions are originating
> from unrelated locations making it unlikely the sessions belong the same user
> (e.g. profileId).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
