For those of you using Mid-Tier 7x...   
Do the logs show any sort of connection ID to tie the entries together?

In Mid-Tier 5 the logs were formatted similar to the other Remedy logs.
You had an ID number that would tie multiple log entries together.
(formatted to show individual entries)   
 <ARTID~218> <Session> <2007-01-06 01:24:53,783>   
    <com.remedy.arsys.session.Login.initWebService(DashOB3391:225)>   
    <DEBUG> <Fetching SessionData object from session ... >   
 <ARTID~218> <Session> <2007-01-06 01:24:53,783>   
    <com.remedy.arsys.session.Login.initWebService(DashOB3391:253)>   
    <DEBUG> <Create new SessionData Object>   

I didn't use the 6.0 Mid-Tier so I can't say what they were like.   

In the 6.3 logs there is no ID so you can't tie the entries together.   
 Mar 29, 2007 9:12:34 AM com.remedy.arsys.support.Log warning   
   WARNING: Reaping cache Group maps for permissions change on server   
 Mar 29, 2007 9:12:34 AM com.remedy.arsys.support.Log warning   
   WARNING: Reaping cache Role maps for permissions change on server   
 Mar 29, 2007 9:12:37 AM com.remedy.arsys.support.Log fine   
   FINE: ConfigServer - post /arsys/servlet/ConfigServlet?action=log   
 Mar 28, 2007 9:14:27 PM com.remedy.arsys.support.Log log   
   FINE: Authentication exception   
   MessageType: 2   
   MessageNum: 623   
   MessageText: Authentication failed   
   AppendedText:   
        at com.remedy.arsys.api.Proxy.ARVerifyUser(Native Method)   

Thanks
Fred  

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Reply via email to