• 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

WebLogic 6.1 SP3 - Stateful Session Bean Problem

 
Ranch Hand
Posts: 493
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,
I have a question about WebLogic 6.1 with SP3.
Our application has two stateful session beans with the following settings for controlling the bean caching and passivation behavior:
Max Beans in Cache = 1000
Idle Time Out Seconds = 1860
Cahe Type = LRU
I am trying to avoid the cache full exception that we get by switching to LRU from NRU setting and trying to do some load-testing.
Imagine my surprise when after making these changes and rebooting the servers, I get the strangest behavior:
In a nutshell, when I monitor the runtime instances of these stateful session beans, I see that the Bean Passivation Count begins to
increase instantly as soon as I log-on to the application. This happens even if I am the only user on the system and manually logging
in instead of applying the load.
Another thing that I have observed is that the passivation count stays the same as the Lock Manager Access Count, i.e., they both show
increasing values which more or less stay in lock-step, i.e., they both show the same counts.
Note that the Lock Entries Current Count, Waiter Total Count, and Time Out Total Count stay at 0.
The Cached Bean Current Count increases with increasing number of users correctly, i.e., it shows an increase in proportion with the users
logging in. The Cache Access Count and Cache Hit Count show numbers that are slightly below the Passivation Count and Lock Manager
Access Count. The Activation Count stays at 0.
At this point, I am not too concerned about the Activation Count but very concerned about why am I getting bean passivation more or less
as soon as a user logs on even though my Max Beans in Cache size is set to 1000 and Idle Time Out Seconds is set to 1860?
Note that both the beans have a transaction attribute of "NotSupported" since we don't start any transactions in those beans.
Any insight that anyone can provide will be most appreciated.
Thanks.
Bharat
reply
    Bookmark Topic Watch Topic
  • New Topic