Not Included Yet

Q) What are the disadvantages of putting too much data in HTTP Session ?

Ans)

If you have more data into your HTTPSession object , following could be some of the issues you may encounter.

May cause Memory issue when you have max sessions opened at a given point of time.
This also causes read/write overhead, though your application wants a fraction of data from such a big Object graph you app server has to load Full HTTPSession.
This is going cause performance issue when you make your application clusterable due to Session Replication, with which your data modifications would be replicated on all other members of the Cluster.

This is too expensive if you have opted for "Persisted HttpSessions" in your App server.

------------------------- We hope you got necessary Info On -----------------------------------------

Disadvantages of putting too much data in HTTP Session

-------------------------------------------------------------------------------------------------------

This Portal is intended to put all Java/J2ee related topics at one single place for quick referance, not only Technical , but also the Project Management Related thing such as Development Process methodoogies build process, unit testing etc.,

This Portal has More than 500 Java Interview Questions (also could be Considered as Quick Notes) very neatly separated topic by topic with simple diagrams which makes you easily understandable. Importantly these are from our Realtime expericance.

OOPs Interview Questions (Quick Notes)

Core Java Interview Questions (Quick Notes)

Awt/Swing Interview Questions (Quick Notes)

Struts Interview Questions (Quick Notes)

Spring Interview Questions (Quick Notes)

Hibernate Interview Questions (Quick Notes)

XML/Java Interview Questions (Quick Notes)

JSF/Seam Interview Questions (Quick Notes)

UnitTesting Interview Questions (Quick Notes)

UML Interview Questions (Quick Notes)

DataBase Interview Questions (Quick Notes)

JavaScript Interview Questions (Quick Notes)