0003481: session replication issue

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0003481

[Resin]

minor

always

05-06-09 09:38

08-06-09 09:22

Reporter

ferg

View Status

public

Assigned To

ferg

Priority

normal

Resolution

fixed

Status

closed

Product Version

4.0.0

Summary

0003481: session replication issue

Description

Env: Windows, servers a and b, front-ended by apache

UserData stored on session: An integer that gets incremented on every request and stored at key "i". It's being System.outted by the JSP on every request and appears in the logs as

alex:i: 0

The session data failed to propagate in the following scenario:

Initial State:
Servers a and b started; attribute (R) on data files cleared

Request 1:
    dispatched to server a; integer is null, init to 0, put on session

Request 2:
    dispatched to server a; integer value is 0, increment, put on session

Shutdown Server a

Request 3:
    dispatched to server b; integer value is 1(successful replication), increment, put on sessoin

Startup Server a

Request 4:
    dispatched to server a: integer value is null.

I've attached the JSP page, and logs from server a and b with com.caucho.server.level=finest

(See eng-staff mail May 1, "session replicate: toggling servers")

Additional Information

Attached Files

Relationships

There are no notes attached to this issue.

Issue History
Date Modified	Username	Field	Change
05-06-09 09:38	ferg	New Issue
08-06-09 09:22	ferg	Assigned To	=> ferg
08-06-09 09:22	ferg	Status	new => closed
08-06-09 09:22	ferg	Resolution	open => fixed
08-06-09 09:22	ferg	Fixed in Version	=> 4.0.1

Mantis 1.0.0rc3[^]

26 total queries executed.
24 unique queries executed.