Off Topic > General

Do I need to bounce OnDemand to refresh a changed exit routine (ARSLOG)

(1/2) > >>

JFHall:
I changed the ARSLOG exit but my change is not being used by OnDemand.  Do I need to bounce OnDemand to pull in a fresh copy of the exit?  More generally, does OnDemand pull the exits into memory on startup or does it dynamically execute whatever code is in the exit?  Our OnDemand instance is running on AIX.

Justin Derrick:
Last time I changed a running arslog script (admittedly a few years back - I try not to change tires on a moving car!) the changes to arslog take effect nearly instantly.  The code is called each time the user exit is called, and run in it's own process/thread.  Of course, it goes without saying...  test test test test.  :D

If you don't mind the question...  not many sites I've been to are using arslog...  what's your use case, and are you happy with how it works?

-JD.

JFHall:
We're running a rather dated version of CMOD - 9.0.  We use arslog to send notifications for certain Alert and Error level messages.  The latest requirement is an audit requirement which has us writing every single message (believe it or not) to a new log file.  I can run arslog from the command line, passing it test parameters, and it works fine.  But CMOD seems to be ignoring the change.  I have verified that logging is turned on, both system logging and application group logging, in the System Parameters.  Granted, we have nearly zero activity in our test environment, but even the act of logging on and logging off should invoke the exit and cause a message to be written to the new log file.

Justin Derrick:
You'll need to enable user exit logging...  In the CMOD Admin client, right click on the server, choose System Parameters, and in the User Exit Logging group, make sure everything is enabled. 

Now...  just to be able to say that you were warned...  logging every message has the potential to slow down your server to a crawl.  There's only so many times you can call a script per second before the server becomes backlogged, and CMOD stops responding.  If you encounter this issue, you can disable the user exit logging, and it should take effect immediately, and good performance should resume within a few minutes as the backlog clears.

-JD.

JFHall:
Been there, done that.  All boxes under User Exit Logging are selected.  Why this arslog exit is not getting executed is a mystery.
 Only thing left I can think to try is bounce OnDemand, which will only help if this exit truly gets stored in memory when CMOD starts rather then being executed dynamically in CMOD's bin directory, which seems kind of hard to believe........

I appreciate the warning about server performance.  We'll keep a close eye on that when we implement this in production as I have the same concern.  First though, I need to get this thing tested on our test server, which basically has zero activity right now except for my own logins, logouts, queries, and that "every-30-minute ping" from arssockd.

Navigation

[0] Message Index

[#] Next page