File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Performance and the fly likes Particular server got memory issue Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Performance
Bookmark "Particular server got memory issue" Watch "Particular server got memory issue" New topic

Particular server got memory issue

L Willie
Ranch Hand

Joined: Aug 10, 2008
Posts: 51
I have few server running same version of web application.
These application run from One of the server always show "funny" results,which likely due to cache/memory/session problem.
For example,
1)delete/change certain data then save to database,database update data successfully.However come to screen still showing old result.
2)I search result of certain document from Internet Explorer,then I log out and login to previous search document.Those search criteria and result still REMAIN there.
Fine,I login with different browser,such as mozila firefox,those search criteria and result showing on screen.

If I leave this issue few hours,then come back to previous screen or document,it was show uptodate info.
I have tried delete server cache,browser cache,db cache.problem still persisted.

P/S:Other 3 server runnig same version of web application no such issue.

Tito Pathak

Joined: Feb 07, 2012
Posts: 1
Release your cache. Use commit often whenever required and then check it.
Also I will advise you to clear the session once.
Dheeraj Bansal

Joined: Dec 22, 2008
Posts: 6
As you are saying that even after updating the database, search results being shown are old. The only reason for it could be that search results are being cached on persistence layer of the application. Just like there are default caching feature available in hibernate which caches the same query.

You can validate by tracing the logs. Run the search for the first time see the logs for query fired and then re-run the same search, I am sure that it will not fire the query second time. Somehow caching is on in the layer which is interacting with database.
I agree. Here's the link:
subject: Particular server got memory issue
It's not a secret anymore!