[
https://issues.apache.org/jira/browse/OFBIZ-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228643#comment-14228643 ]
Arun Patidar commented on OFBIZ-4482:
-------------------------------------
Hello Wai,
This behaviour looks correct to me. System logs userlogin/party values for registered users only. After logout system treates user as Anonymous user so in this case empty value of userlogin/party makes sense.
I also noticed that if user logins again then system update same visitor record with value of userlogin/party. So its again seems a right behaviour.
I think this issue can be close now.
> findVisits request shows empty entry for user after logout
> ----------------------------------------------------------
>
> Key: OFBIZ-4482
> URL:
https://issues.apache.org/jira/browse/OFBIZ-4482> Project: OFBiz
> Issue Type: Bug
> Components: party
> Affects Versions: Trunk
> Reporter: Wai
> Priority: Minor
> Attachments: snapshot1.png, snapshot2.png, snapshot3.png
>
>
> When a user login, an entry is shown for the user in
https://localhost:8443/partymgr/control/findVisits.
> (refer to snapshot1.png)
> When the user logout, the same entry contains missing values for partyId, userLoginId, New User, and Thru Date columns are empty.
> (refer to snapshot2.png)
> When the same user logs back in, those entries reappears.
> (refer to snapshot3.png)
> Ofbiz seem to be re-using the same visitorId and visitId after a logout.
> My expectation of how it works is that when a user logs out, the missing entries should appear as it had been when the user was logged in and the Thru Date should have be filled with the time of logout.
> When the same user login again, another entry should have been created.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
