To JRun-talk-list: We are currently developing a application with a JSP front end that makes frequent use of objects stored in a client's session. We have not experienced any problems on our development environment (JRun 3.0 on NT), however when deploying the application onto our testing environment (JRun 3.0 on Solaris) we encounter a very strange behavior. JRun seems to try and serve a single session object to all clients who access the application. Basically, the first client makes a request to the application and a session is created, this client then proceeds to set and retrieve objects from the session. Any subsequent clients, while apparently assigned a different session (based on the session id attribute) are unable to set or retrieve objects from "their" respective session. This problem persists across restarts of the application (session persistence flag is set to "false"). Has anyone experienced behavior similar to this or have any clue as to the cuse of such behavior? Thanks in advance for any help or information. - Ian Brown Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
