Hi Chris,

I recreated the one with spaces too and didn't see any difference either.

In my case I may need to identify which exchange did what, so it might be
nice for me to leave a 'stamp' behind of when an exchange updates the form.
This is because I might have data coming in from more than one source on the
same table, and each of these source might require different workflow
actions performed on them. Unfortunately none of the core data of the form
the exchange is performed on will identify the name of the exchange that
performed an update.

So I have tested running the SQL statement select 'constant' by picking the
SQL option from the 'Rules' display list, and I can set the 'constant' value
to a field 'Exchange Name' that I have created.

A workaround to reducing the number of SQL server processes could be to
start the EIE services using a cron job if you are on UNIX or a batch file
using scheduled tasks on windows, at the time it needs to be run, and then
stop it after it would have finished that job using another cron
job/scheduled task. I've noticed that on an average, over a constant set of
data, the time taken to run the exchange is generally the same, so giving it
a fair degree of standard variation, the service could be stopped after a
significantly longer duration than it takes to run.

It is not a pretty solution (actually its not a solution) but at least can
be used as a workaround.. It should kill the SQL server processes it
initiated after the services are shut down as well as bring down the memory
consumption. Have you tried doing something similar? I think I will attempt
it and see if it will help any..

Joe
  -----Original Message-----
  From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of strauss
  Sent: Tuesday, July 10, 2007 5:21 PM
  To: [email protected]
  Subject: Re: EIE Service crashing periodically with a Windows error...


  **
  The only data exchange I have active is Vendor Data into AR, and is named
"Update UNTPersonShadow" (with a space in the name) and runs on server
instance "ARS_REMEDY7_EIE_REMEDY4_Inst_001."

  I copied it to a new one with no spaces in the name, made the old one
inactive and the new one active, and restarted the service.  Starting the
service created at least one, maybe two connections, running the first
exchange created a total of three.  The second time the exchange ran created
two more, and the exchange that just finished added two more for a total of
seven after three data exchanges.  Peak Memory Usage has grown about 200 K
with each data exchange.  So, changing the name does not seem to make a
difference.  The support folks I talked to said that the actions of the
exchange (vendor into AR, vendor into CMDB, AR into vendor, etc.) had
contrasting effects on memory management, making it hard to optimize the
eie.exe for all supported exchanges.

  Copy and Run buttons work in patch 004 - that was one of the fixes as I
recall.
  Christopher Strauss, Ph.D.
  Remedy Database Administrator
  University of North Texas Computing Center
  http://remedy.unt.edu/helpdesk/


----------------------------------------------------------------------------
--
  From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza
  Sent: Tuesday, July 10, 2007 3:05 PM
  To: [email protected]
  Subject: Re: EIE Service crashing periodically with a Windows error...


  **
  Hi Chris,

  I just noticed something else which I think is worth mentioning.. It looks
like its not releasing the SQL process thread to only one of the 3 exchanges
I have defined on my system.. There are 2 exchanges that I have set up for
receiving updates from an SQL server, and 1 exchange set to update an SQL
server.

  The threads seem to freeze up on one of the 2 exchanges that are set for
receiving updates.. all the settings on this too are identical.. EXCEPT for
the naming convention.. I am wondering if EIE has a preference on no spaces
or special characters in its names?

  I'm just curious as to what naming conventions you are using for your
exchanges?? Any spaces in the names? Special characters? No spaces or
special characters in names???

  Joe
    -----Original Message-----
    From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of strauss
    Sent: Tuesday, July 10, 2007 3:45 PM
    To: [email protected]
    Subject: Re: EIE Service crashing periodically with a Windows error...


    **
    ISS03129616
    Christopher Strauss, Ph.D.
    Remedy Database Administrator
    University of North Texas Computing Center
    http://remedy.unt.edu/helpdesk/


----------------------------------------------------------------------------
    From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza
    Sent: Tuesday, July 10, 2007 2:33 PM
    To: [email protected]
    Subject: Re: EIE Service crashing periodically with a Windows error...


    **
    I wouldn't have noticed mine too but as a habit if I have control of the
backend database I usually am in the habit of restricting number of user
connections if that is possible and since it is on SQL, I had it down to 50.
We hit the 50 limit twice today on our development box, and that's how we
ended up noticing that EIE seems to hog all these 'extra' connections..

    Also one of my co developer was noticing degradation on performance due
to timeouts so we think we know why we were getting these timeouts.

    Right now I am in the process of writing what we have learnt to our
first line of support..

    Is there any chance I could have your Issue number so we could inform
our first line of support that there is a related ticket open? Maybe that
might help them help us.. We don't as yet have a ticket open directly with
Remedy but if we can have our first line understand this is a potential bug
we could have a remedy support ticket created quicker..

    Joe
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.476 / Virus Database: 269.10.2/893 - Release Date: 7/9/2007
5:22 PM

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

Reply via email to