Win a copy of Mesos in Action this week in the Cloud/Virtualizaton forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Stateless Session Bean in Websphere

 
Sri Rangan
Ranch Hand
Posts: 160
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
1)Is there any way to make sure (in websphere3.5) to have always only one particuler stateless session bean instance in the container?
2)Is it possible to set one particular Stateless Session to have highest time out period. Sample deployment descriptor for one stateless session bean which we are using looks like this..(We use ANT for this)
//////////////////////////////////
<buildDeploymentDescriptor <br /> appServer="${appServerName}"<br /> descriptorFileName="${descriptorFileName}"<br /> <br /> beanName="com/TestSessionBean.ser" <br /> timeOut="0"<br /> stateManagement="STATELESS_SESSION"<br /> homeInterface="com.TestSessionBeanHome"<br /> remoteInterface="com.TestSessionBeanService"<br /> enterpriseBean="com.TestSessionBeanBean"<br /> JNDIName="${ejbQualifier}TestSessionBean"<br /> transactionAttribute="TX_REQUIRES_NEW" <br /> isolationLevel="READ_COMMITTED" <br /> runAsMode="SYSTEM_IDENTITY" <br /> dependency1="com.TestSessionBeanHome"<br /> dependency2="com.TestSessionBeanBeanService"<br /> dependency3="com.TestSessionBean"<br /> />
///////////////////////////////////
If you look at the descriptor, the timeout setting is =0. Does it mean that once this statless session bean instance served one cleint request, it would be removed by container from pool?
Is there any maximum limit time for this "timeout". Our requirement is to keep this instance of this one session bean as long as possible.
Thanks
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic