IT Process Automation

Expand all | Collapse all


  • 1.  PAM SLOW?

    Posted 10-11-2012 03:44 PM
    Is it normal that Pam runng so slow? I have operator that looking at it, it already completed, but it would not goes onto the next operator. It just hang their busy for awhile before proceeding to the next operator.

    Or if i have a lot of operator calling multiple processs at the same time, it seem to slow down Pam pretty badly.

    Any idea or tips that would speed up?


  • 2.  RE: PAM SLOW?

    Posted 10-11-2012 04:25 PM
    Hello Ken,
    It might be different things:
    I would check memory usage on the server, CPU peaks and possible DB bottlenecks.
    As best practice check also that you don't have too many versions for your process, check size of PAM DB and try to delete old archives.

  • 3.  RE: PAM SLOW?

    Posted 10-12-2012 05:21 AM

    I also have a problem with PAM4.0 SP1 performance.
    First of all, my first login of the day takes more than 5min, and I think that this could be related with EEM.
    Second, some times the processes takes some time to start and some time to execute, my log files are full of warnings and error the most of them telling me this:
    2012-10-12 10:14:12,146 WARN [com.arjuna.ats.jta.logging.loggerI18N] [      Thread-12] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] Could not find new XAResource to use for recovering non-serializable XAResource < 131075, 30, 28, 48459755101545310056581005548555852102102535349485458974954101544897551015453100565810055485558521021025353494854589749541015499 >

    I think that XA Transaction are correctly configured.

    Sérgio Castro

  • 4.  RE: PAM SLOW?

    Posted 10-12-2012 05:30 AM

    i changed to Firefox and the performance improved a lot, however it's slower then version 3.2

    best regards


  • 5.  RE: PAM SLOW?

    Posted 04-15-2013 04:47 AM
    Hello Sergio

    I get the following in PAM4 SP1

    WARN [com.arjuna.ats.jta.logging.loggerI18N] [      Thread-12] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa]
    [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] Could not find new XAResource to use for recovering non-serializable XAResource
    < 131075, 31, 29, 4845975056505052565810052995758534856975254989958491005451579998975056505052565810052995758534856975254989958491005451579999 >

    This could be perceived as a non-fatal exception although I'd think that performance would be affected were a new XAResource instance not be possible in addition to the warning messages being written to the log file -
    doing unnecessary writes to disk is expensive.
    If this is a non-fatal exception then I would suggest the Developers/Coders set the log level for this entry to INFO or ERROR (according the log library in use), then at least the user can set the loglevel to WARN which in turn
    will improve the performance. Right now one can do nothing except to turn off logging or to Resolve the XAResource issue - if there is one.
    Resolving the XAResource issue when the client' dba, the msdn Microsoft diagnostic and PAM install claim that XAResource is available does not leave one with many options.

    Let me know if you found a solution to this problem, wasn't SP1 supposed to resolve this issue ... erk ?