Navigation

    Best APM Solution for Oracle WebLogic Server & FMW Product Family
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Download

    SOLVED Scheduled Jobs sending email at every hour

    General Support & Troubleshooting
    schedulerjob wlsdm
    2
    4
    1467
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • wlcommunityusers
      wlcommunityusers last edited by

      Hi Support team,

      Can you please check why we are getting message at every hour. e.g. At server time 1 AM, 2 AM, 3 AM and so on?

      RegardsImage 10.png

      Community Users Case Notes (Diary)

      wlsdmsupport 1 Reply Last reply Reply Quote 0
      • wlsdmsupport
        WLSDM Support last edited by

        Hi,

        This timeout value is a precaution to protect the system.

        That’s why we can’t let the increase the timeout value by users.

        If you need a long-running process; you can trigger your WLST script using a shell command.

        That will cause an immediate return for the main process (Shell Script) but not for the child process (Triggered WLST Script).

        Also, this type of usage means; The script is out of the control to WLSDM.

        Kind regards.

        WLSDM Community Support Team

        1 Reply Last reply Reply Quote 0
        • wlsdmsupport
          WLSDM Support @wlcommunityusers last edited by

          Hi ,

          Please make sure your script completes under 60 seconds.

          Regards.

          WLSDM Community Support Team

          1 Reply Last reply Reply Quote 0
          • wlcommunityusers
            wlcommunityusers last edited by

            Thanks for your reply.

            Seems like 60 seconds threshold is causing the below issue. Can we set threshold value other than 60 seconds?

            Community Users Case Notes (Diary)

            1 Reply Last reply Reply Quote 0
            • wlsdmsupport
              WLSDM Support last edited by

              Hi,

              This timeout value is a precaution to protect the system.

              That’s why we can’t let the increase the timeout value by users.

              If you need a long-running process; you can trigger your WLST script using a shell command.

              That will cause an immediate return for the main process (Shell Script) but not for the child process (Triggered WLST Script).

              Also, this type of usage means; The script is out of the control to WLSDM.

              Kind regards.

              WLSDM Community Support Team

              1 Reply Last reply Reply Quote 0
              • 1 / 1
              • First post
                Last post

              WLSDM: Native WebLogic Monitoring & Diagnostics

              Copyright © 2021 WLSDM Community & Support Portal | WLSDM.COM | WLSDM Blog