6.3 has the same filter but that does not help when you have an automated system pushing data into Remedy. We have an automated system that can make up to 15 connections simultaneously. Debugging which transaction (web service XML data) the error was on is a major pain.
Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Axton Sent: Thursday, March 29, 2007 11:25 AM To: [email protected] Subject: Re: Mid-Tier 7 log question In mid-tier 7, you have the option to specify a single user for which to log in the mid-tier config settings page. If you are troubleshooting something for a single user, this can be helpful. If not, the regular remedy logs will tell you everything they do for a regular client. Axton Grams On 3/29/07, Grooms, Frederick W <[EMAIL PROTECTED]> wrote: > 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" > ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
