Isaac Agudo wrote:
--
Hy everybody ..
..
I want to know all the http sessions that's working my appServer, So exist a
easy way to do that ???..
i see that the orionconsole, has an option to see all the httpsessions, i
want to do the same, but from
my aplication .
--
Thank's in advance.
--
Hi,
How can I determine the number of Http sessions currently active within
Orion? I have a kind of solution (using HttpSessionBindingListener) but I
think it's ugly and there should be a more reliable way of doing this.
Regards,
Tibor
reate them and then bind them to HTTP sessions so that
they can be reused by clients on subsequent requests.
There's no standard way to tell when an HTTP session expires. How, then, is
it possible for the remove() method to be called to release a SB? Does this
not cause
"memory leaks"
expiring HTTP sessions ...
I posted this msg this morning, but I haven't seen it appear on the list
yet. I'm reposting in case it was lost ...
Session beans (SBs) must have their remove() methods called in order to
"clean up" and return to an app server's object pool. I believe
Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Gerald
Gutierrez
Sent: Friday, March 16, 2001 9:33 AM
To: Orion-Interest
Subject: Removal of SBs from expiring HTTP sessions ...
I posted this msg this morning, but I haven't seen it appear on the list
yet
: Removal of SBs from expiring HTTP sessions ...
Does that actually work in the remote EJB model; I mean through the stubs?
If not, the servlets using the sessions could just as easily listen and in
turn inform the SB's.
tim.
Can't you just make the SB a HttpSessionBindingListener
Hello Gerald,
You can create an object that implements HttpSessionListener
interface and override the valueUnbound method to call the
remove method or whatever you need to to with the SB.
Put it in the session, and when the session expires the
valueUnbound method is invoked. Be sure to
Session beans (SBs) must have their remove()
methods called in order to "clean up" and return to an app server's object
pool. I believe one common use of SBs is to create them and then bind them
to HTTP sessions so that they can be reused by clients on subsequent
reques
Hello Mike,
Thursday, March 15, 2001, 7:31:23 PM, you wrote:
MCB Can't you just make the SB a HttpSessionBindingListener and implement
MCB valueUnbound() ?
Nope. For that to work you need your Remote interface to extend
HttpSessionBindingListener, but it already extends EJBObject.
There is a
: Re[2]: Removal of SBs from expiring HTTP sessions ...
Hello Mike,
Thursday, March 15, 2001, 7:31:23 PM, you wrote:
MCB Can't you just make the SB a HttpSessionBindingListener and implement
MCB valueUnbound() ?
Nope. For that to work you need your Remote interface to extend
Hello Mike,
I have to thank you. I wasn't sure of that, so I check it. I write
something like:
public interface test extends java.io.Serializable, javax.ejb.EJBObject {
void dummy();
}
And the compiler throwed and error (fastjavac from Forte CE 2.0). So I stated that it
couldn't be
11 matches
Mail list logo
