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

List:       jacorb-bugs
Subject:    [jacorb-bugs] [Bug 217] New: Need meaningful thread names for Request Processor/Controller
From:       bugzilla-daemon () inf ! fu-berlin ! de
Date:       2002-06-22 17:17:31
Message-ID: E17LoVv-0004vj-00 () berners
[Download RAW message or body]

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

           Summary: Need meaningful thread names for Request
                    Processor/Controller
           Product: JacORB
           Version: 1.4 beta 4
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: ORB
        AssignedTo: gerald.brose@acm.org
        ReportedBy: kanis@addc.ch
         QAContact: jacorb-bugs@lists.spline.inf.fu-berlin.de


I request thread information from my servers from an external management client 
and display the thread tree, unfortunately it is not possible to see which 
threads from JacORB are which. I have solved this using a static counter and a 
meaningful thread name in the RequestController and RequestProcessor classes:

    RequestProcessor( RPPoolManager _poolManager )
    {
        super("RequestProcessor-" + (++t_counter));
        ...

    RequestController( POA _poa, org.jacorb.orb.ORB _orb,
                       AOM _aom, LogTrace _logTrace)
    {
        super("RequestController-" + (++t_counter));
        ...

Could you integrate this or something similar into the release version? :^)

Regards
Peter Kanis



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

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