Could you explain what you mean when you say "RMI is a connectionless protocol (not a persistent connection)"
Richard
Finn, Michael wrote:
1. If EJB Timer (2.1) does not fit the bill for you, an MBean is a typically a good solution for this problem. Depends on what you mean by service.
2. Since RMI is a connectionless protocol (not a persistent connection), there is really no 'disconnect' event. Your best bet is probably to use shutdown hooks in your client, and make last ditch effort to do the logout there.
mike
-----Original Message----- From: Sasidharan, Manoj [mailto:[EMAIL PROTECTED] Sent: Friday, June 06, 2003 3:33 AM To: [EMAIL PROTECTED] Subject: [JBoss-user] Some J2EE Design Questions
Hello All,
1. How can a daemon process/service implemented in J2EE world? Any
design pattern?
2. Is there any way to trap J2EE client disconnect events - we want
to timeout user sessions if they fail to logout properly from our
J2EE app and disconnect from App Server
Thanks in advance for your time in helping me with these design issues.
MS
------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
