Mapping a JCA Thread to a Siebel Server Task and Log File

From the JCA logging information, you can find the Siebel Server task and log file, which can be useful in diagnosing threads that use large amounts of CPU time.

To map a JCA thread to a Siebel Server task and log file

1. Examine the JCA log file to find the high-CPU thread, for example:

   [SIEBEL INFO] Thread[Servlet.Engine.Transports : 2,5,main] [2010-11-05 
   07:53:26.243] [SiebelConnection(507473761)] Opened a new connection to Siebel 
   (Siebel session : siebel.tcpip.none.none://myserver.example.com:2321/esblp01/
   SCCObjMgr_enu/!10.6373.3ba70.465c2246)
   

   The Siebel session URL takes the following form:

   siebel[.transport][.encryption][.compression]://host[:port]/EnterpriseServer/
   AppObjMgr_lang/!AppObjMgrID.ProcessID.TaskID.timestamp

   where the Application Object Manager ID, process ID, task ID, and timestamp are represented by hexadecimal numbers.

2. Use the Siebel session URL to find the following parameters, converting hexadecimal numbers to decimal:

   Parameter	Example
   Host	myserver.example.com
   Siebel Enterprise Server	esblp01
   Application Object Manager_lang	SCCObjMgr_enu
   Application Object Manager ID	10 (16 decimal)
   Task ID	3ba70 (244336 decimal)

3. Find the corresponding Siebel Server log file, which is in the SIEBEL_SERVER_ROOT/log directory:

   • Windows:

     AppObjMgr_lang_AppObjMgrID_taskID.log
     

     For example:

     SCCObjMgr_enu_0016_244336.log
     

   • UNIX:

     AppObjMgr_lang_taskID.log
     

     For example:

     SCCObjMgr_enu_244336.log