Few possibilities:

1)      Server is too busy and all threads Max'ed out

2)      Database too busy in responding ARS request resulting timeout

3)      If you are sure that timeout is always cause on GSI call and this is 
always been the pattern then you need to see whether all GSI call shows timeout 
or only specific day/time of the day

4)      If this is server group environment then you need to make sure you have 
correct Server-Name and Server-Connect-Name values set in ar.cfg

5)      You may try Log Analyzer tool to find out what all 20 longest running 
calls at the time of timeout error

If nothing helps, I would suggest to create a support case with BMC support as 
timeout errors are very broad and needs very deep level investigation.



Best Regards,

Kiran

From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Ben Chernys
Sent: Monday, June 10, 2013 5:09 PM
To: [email protected]
Subject: Odd 93 timeout behaviour in 8.1.0

**
Hi Folks,

Just another odd behaviour I am noticing and wondering if, firstly, anyone else 
does this, and secondly, if there is any work-around for this.  This behaviour 
is only noticed on 8.1 and not on 8.0 or other versions of ARS though my memory 
gets murkier as time passes.

Environment:

ITSM 8.1 Full suite running on Windows and MS SQL on a separate server.

ARS Version       8.1.00 201301251157
DB Type               SQL -- SQL Server
DB Version          2008 R2 (SP2) - 10.50.4000.0 (X64)
OS                          Windows 6.1
2 element server group.  I connect to the admin server.

Issue:

I am getting 93s regularly though intermittently at a single point when the 
server is actually busy.  The oddity is that point.

I initialise by authenticating to the server and then asking for a very few 
pieces of information from that server including its name and version.

I then build a complete list of available, readable info items and get that as 
well (some 350ish).  It is here that I get the timeouts albeit when the server 
is busy.  The call is "ARGetServerInfo".  I obviously select only the readable 
items.

If I get through that, I have generally no further time-outs and processing 
runs at normal speeds.

I now execute the same three calls on another 7.1 server - that is: session 
initiation, a few items in a single getinfo call, all available items in a 
further get info call.  I then process queries, updates, schema and field gets 
across the two servers - all without further ado.

Most if not all the info for this call would be in memory of the arserver,  So 
the oddity is why this call often returns a 93, only on the 8.1 server, and 
only when the server is actually busy, having responded very quickly to the 
same call with only a few items in the request block.

Ben Chernys
Senior Software Architect
[cid:[email protected]]

Canada / Deutschland
Mobile:      +49 171 380 2329    GMT + 1 + [ DST ]
Email:       Ben.Chernys_AT_softwaretoolhouse.com
<mailto:Ben.Chernys_AT_softwaretoolhouse.com>Web:         
www.softwaretoolhouse.com<http://www.softwaretoolhouse.com/>

We are a BMC Technology Alliance Partner.

Check out Software Tool House's free Diary Editor and out Freebies
Section for ITSM 7.6.04 and 8.0.0 Fields spreadsheets.

Meta-Update, our premium ARS Data tool, lets you automate
your imports, migrations, in no time at all, without programming,
without staging forms, without merge workflow.
http://www.softwaretoolhouse.com/


_ARSlist: "Where the Answers Are" and have been for 20 years_

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

<<inline: image001.jpg>>

Reply via email to