• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

size of data stored in a session object and caching

 
Ranch Hand
Posts: 116
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I know this might sound stupid, but is there a size limit on the amount of data that can be stored in a HttpSession object?

I am trying to cache some data for an application that I am using.I am not running an application server, just tomcat 5.5.12. This application uses GIS (Geographical Information System) maps which will be associated with a users location.Each image is about 250x400. Also these maps may be used for subsequent access. These maps reside inside a legacy system(server).

What is the best strategy to cache these maps on to a jsp/servlet framework?
 
Ranch Hand
Posts: 2308
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I think it has been answered in some of the old posts.
Objects always goes to the heap.so it depends on the heap space available to the JVM no matter whereever you store.
 
Author and all-around good cowpoke
Posts: 13078
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

size limit on the amount of data that can be stored in a HttpSession object


Please remember that a session stores a reference to an object, NOT the object itself. How this affects memory limits depends on all the users of the object.
Note that servlet containers are allowed to serialize a session to disk whenever they want - a serialized session WILL contain the serialized object so the object must be Serializable.

Bill
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic