[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jacorb-bugs
Subject:    [jacorb-bugs] [Bug 632] Thread Growth in JVM with jacorb threads
From:       bugzilla-daemon () inf ! fu-berlin ! de
Date:       2008-01-08 7:29:30
Message-ID: E1JC8tu-0005QO-00 () berners ! inf ! fu-berlin ! de
[Download RAW message or body]

http://www.jacorb.org/cgi-bin/bugzilla/show_bug.cgi?id=632





------- Additional Comments From broeni@osb-systems.com  2008-01-08 08:29 -------
Wrt. to the note of wenlong 2007-12-22:
Our mistake was that we had initialized the ORB for each client connection to a
CORBA server but never called shutdown() on the ORB. Thus the client reader
threads kept waiting for input from the CORBA server.

The fix consists of 2 parts:
1) Store the ORB returned by org.omg.CORBA.ORB.init(...) in a class
2) Handle HTTP session unbinding in that class (we are using JacOrb together
with Tomcat): 

public class OsbClientUser implements HttpSessionBindingListener {
    ...
    // HttpSessionBindingListener interface
    public void valueBound(HttpSessionBindingEvent event)
    {
        // nothing 2do
    }

    public void valueUnbound(HttpSessionBindingEvent event)
    {
        if (null == orb_) return;

        log.debug("Shutdown the ORB...");
        orb_.shutdown(true);
        orb_ = null;
        log.info("ORB shut down.");
    }
    ...
}

In my understanding this issue is invalid in JacOrb 2.3.0.



------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

_______________________________________________
jacorb-bugs mailing list
jacorb-bugs@lists.spline.inf.fu-berlin.de
http://lists.spline.inf.fu-berlin.de/mailman/listinfo/jacorb-bugs

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic