This week's giveaway is in the EJB and other Java EE Technologies forum.
We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line!
See this thread for details.
The moose likes Websphere and the fly likes Stateless Session bean in Websphere Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "Stateless Session bean in Websphere" Watch "Stateless Session bean in Websphere" New topic
Author

Stateless Session bean in Websphere

Sri Rangan
Ranch Hand

Joined: Dec 08, 2001
Posts: 160
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 in advance
Sri
Thomas Paul
mister krabs
Ranch Hand

Joined: May 05, 2000
Posts: 13974
Moving this to the IBM WebSphere Forum.
------------------
Tom
Sun Certified Programmer for the Java� 2 Platform
Moderator of the forums:
J2EE and EJB
Other Java APIs


Associate Instructor - Hofstra University
Amazon Top 750 reviewer - Blog - Unresolved References - Book Review Blog
Kyle Brown
author
Ranch Hand

Joined: Aug 10, 2001
Posts: 3879
(1) No, that's explicitly forbidden by the specification. EJB's are not singletons -- why would you want to do that anyway?
(2) We don't support the Use of ANT in deploying EJB's to WebSphere... I don't know what timeout you could be referring to... Could you please provide clarification.
Kyle
------------------
Kyle Brown,
Author of Enterprise Java (tm) Programming with IBM Websphere
See my homepage at http://members.aol.com/kgb1001001 for other WebSphere information.


Kyle Brown, Author of Persistence in the Enterprise and Enterprise Java Programming with IBM Websphere, 2nd Edition
See my homepage at http://www.kyle-brown.com/ for other WebSphere information.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Stateless Session bean in Websphere
 
Similar Threads
Stateless Session Bean in Websphere
Handling of Exceptions Thrown by the Timeout Callback Method
Stateless Session bean in Websphere
Confused reg. a passage in Ed Roman's Book
Timers question