[
https://issues.apache.org/jira/browse/UNOMI-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875686#comment-15875686
]
Serge Huber commented on UNOMI-82:
----------------------------------
Hello,
It depends on your testing. If you are reusing the same session across multiple
devices or browsers, then it will merge all the information. Sessions should be
generated frequently, basically they are similar to server-side sessions, in
order to avoid this problem.
Could you maybe tell me more about how you are using the sessions ?
Best regards,
Serge Huber.
> 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)
