Menu
▾
▴
ikasaneip-jira — Mailing list for JIRA notifications
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
(212) |
Nov
(188) |
Dec
(74) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
(154) |
Feb
(71) |
Mar
(50) |
Apr
(103) |
May
(88) |
Jun
(129) |
Jul
(112) |
Aug
(154) |
Sep
(165) |
Oct
(85) |
Nov
(103) |
Dec
(43) |
| 2011 |
Jan
(60) |
Feb
(8) |
Mar
(61) |
Apr
(6) |
May
(8) |
Jun
(34) |
Jul
(3) |
Aug
(17) |
Sep
(20) |
Oct
(4) |
Nov
|
Dec
|
| 2012 |
Jan
(3) |
Feb
(65) |
Mar
(5) |
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(6) |
Nov
(6) |
Dec
(3) |
| 2013 |
Jan
|
Feb
(24) |
Mar
(20) |
Apr
|
May
|
Jun
(13) |
Jul
(117) |
Aug
(33) |
Sep
(21) |
Oct
(5) |
Nov
|
Dec
|
| 2014 |
Jan
(17) |
Feb
|
Mar
(9) |
Apr
(24) |
May
(31) |
Jun
(21) |
Jul
(24) |
Aug
(32) |
Sep
(50) |
Oct
(43) |
Nov
(31) |
Dec
(32) |
| 2015 |
Jan
(85) |
Feb
(63) |
Mar
(58) |
Apr
(108) |
May
(129) |
Jun
(250) |
Jul
(258) |
Aug
(66) |
Sep
(313) |
Oct
(207) |
Nov
(149) |
Dec
(128) |
| 2016 |
Jan
(73) |
Feb
(96) |
Mar
(55) |
Apr
(57) |
May
(57) |
Jun
(22) |
Jul
(63) |
Aug
(21) |
Sep
(49) |
Oct
(21) |
Nov
(22) |
Dec
(6) |
| 2017 |
Jan
(111) |
Feb
(61) |
Mar
(75) |
Apr
(10) |
May
(86) |
Jun
(77) |
Jul
(36) |
Aug
(58) |
Sep
(75) |
Oct
(145) |
Nov
(48) |
Dec
(130) |
| 2018 |
Jan
(66) |
Feb
(34) |
Mar
(112) |
Apr
(155) |
May
(97) |
Jun
(70) |
Jul
(9) |
Aug
(3) |
Sep
(5) |
Oct
(12) |
Nov
(14) |
Dec
(55) |
| 2019 |
Jan
(16) |
Feb
(18) |
Mar
(30) |
Apr
(128) |
May
(124) |
Jun
(115) |
Jul
(101) |
Aug
(217) |
Sep
(51) |
Oct
(137) |
Nov
(114) |
Dec
(40) |
| 2020 |
Jan
(21) |
Feb
(98) |
Mar
(82) |
Apr
(17) |
May
(25) |
Jun
(8) |
Jul
(21) |
Aug
(48) |
Sep
(98) |
Oct
(74) |
Nov
(138) |
Dec
(46) |
| 2021 |
Jan
(98) |
Feb
(29) |
Mar
(30) |
Apr
(18) |
May
(17) |
Jun
(29) |
Jul
(28) |
Aug
(67) |
Sep
(131) |
Oct
(171) |
Nov
(139) |
Dec
(52) |
| 2022 |
Jan
(91) |
Feb
(31) |
Mar
(91) |
Apr
(94) |
May
(37) |
Jun
(58) |
Jul
(22) |
Aug
(13) |
Sep
(39) |
Oct
(43) |
Nov
(57) |
Dec
(23) |
| 2023 |
Jan
(13) |
Feb
(27) |
Mar
(67) |
Apr
(53) |
May
(52) |
Jun
(47) |
Jul
(59) |
Aug
(39) |
Sep
(80) |
Oct
(63) |
Nov
(38) |
Dec
(13) |
| 2024 |
Jan
(70) |
Feb
(73) |
Mar
(47) |
Apr
(64) |
May
(130) |
Jun
(123) |
Jul
(59) |
Aug
(99) |
Sep
(133) |
Oct
(97) |
Nov
(20) |
Dec
|
|
From: Michael S. (JIRA) <ji...@ik...> - 2024-09-20 07:51:16
|
Michael Stewart created IKASAN-2477:
---------------------------------------
Summary: Ikasan BOM pointing at incorrect coordinates for jsch libraries.
Key: IKASAN-2477
URL: https://ikasan.atlassian.net/browse/IKASAN-2477
Project: Ikasan
Issue Type: Story
Components: build
Affects Versions: eip-3.3.5
Reporter: Michael Stewart
Assignee: Michael Stewart
Priority: Critical
Fix For: eip-4.1.0, eip-3.3.6, eip-4.0.3
--
This message was sent by Atlassian Jira
Manage notifications: https://ikasan.atlassian.net/jira/settings/personal/notifications?emailPreferences=true#emailpreferences
(v1001.0.0-SNAPSHOT#100266)
|
|
From: David H. (JIRA) <ji...@ik...> - 2024-09-19 08:12:45
|
[ https://ikasan.atlassian.net/browse/IKASAN-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Hilton resolved IKASAN-2466. ---------------------------------- Resolution: Fixed > IES Agent (Widows OS only) slow to write process files to the file system. Need to add wait/retry mechanism if file does not yet exist when job has completed > -------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: IKASAN-2466 > URL: https://ikasan.atlassian.net/browse/IKASAN-2466 > Project: Ikasan > Issue Type: Improvement > Components: scheduler-agent > Affects Versions: eip-3.3.5 > Reporter: Michael Stewart > Assignee: David Hilton > Priority: Blocker > Fix For: eip-4.1.0, eip-3.3.6, eip-4.0.3 > > -- This message was sent by Atlassian Jira Manage notifications: https://ikasan.atlassian.net/jira/settings/personal/notifications?emailPreferences=true#emailpreferences (v1001.0.0-SNAPSHOT#100266) |
|
From: Michael S. (JIRA) <ji...@ik...> - 2024-09-19 07:36:53
|
[ https://ikasan.atlassian.net/browse/IKASAN-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IKASAN-2476 started by Michael Stewart. ----------------------------------------------- > Ikasan entity viewer (wiretaps, errors, replay events, exclusions) ace editor component not filling layout since Vaadin upgrade > ------------------------------------------------------------------------------------------------------------------------------- > > Key: IKASAN-2476 > URL: https://ikasan.atlassian.net/browse/IKASAN-2476 > Project: Ikasan > Issue Type: Story > Components: visualisation > Affects Versions: dashboard-4.0.0 > Reporter: Michael Stewart > Assignee: Michael Stewart > Priority: Trivial > Fix For: dashboard-4.0.1 > > -- This message was sent by Atlassian Jira Manage notifications: https://ikasan.atlassian.net/jira/settings/personal/notifications?emailPreferences=true#emailpreferences (v1001.0.0-SNAPSHOT#100266) |
|
From: Michael S. (JIRA) <ji...@ik...> - 2024-09-19 07:36:09
|
Michael Stewart created IKASAN-2476:
---------------------------------------
Summary: Ikasan entity viewer (wiretaps, errors, replay events, exclusions) ace editor component not filling layout since Vaadin upgrade
Key: IKASAN-2476
URL: https://ikasan.atlassian.net/browse/IKASAN-2476
Project: Ikasan
Issue Type: Story
Components: visualisation
Affects Versions: dashboard-4.0.0
Reporter: Michael Stewart
Assignee: Michael Stewart
Priority: Trivial
Fix For: dashboard-4.0.1
--
This message was sent by Atlassian Jira
Manage notifications: https://ikasan.atlassian.net/jira/settings/personal/notifications?emailPreferences=true#emailpreferences
(v1001.0.0-SNAPSHOT#100266)
|
|
From: Michael S. (JIRA) <ji...@ik...> - 2024-09-17 06:25:29
|
[ https://ikasan.atlassian.net/browse/IKASAN-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stewart updated IKASAN-2475: ------------------------------------ Components: ootb > Add filter to scheduler agent command job processor flow that filters out jobs that do not have an active job plan. > ------------------------------------------------------------------------------------------------------------------- > > Key: IKASAN-2475 > URL: https://ikasan.atlassian.net/browse/IKASAN-2475 > Project: Ikasan > Issue Type: Story > Components: ootb > Affects Versions: eip-3.3.5 > Reporter: Michael Stewart > Assignee: David Hilton > Fix For: eip-4.1.0, eip-3.3.6, eip-4.0.3 > > -- This message was sent by Atlassian Jira Manage notifications: https://ikasan.atlassian.net/jira/settings/personal/notifications?emailPreferences=true#emailpreferences (v1001.0.0-SNAPSHOT#100266) |
|
From: Michael S. (JIRA) <ji...@ik...> - 2024-09-17 06:25:14
|
[ https://ikasan.atlassian.net/browse/IKASAN-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stewart updated IKASAN-2475: ------------------------------------ Summary: Add filter to scheduler agent command job processor flow that filters out jobs that do not have an active job plan. (was: Add filter to shceduler agent command job processor flow that filters out jobs that do not have an active job plan.) > Add filter to scheduler agent command job processor flow that filters out jobs that do not have an active job plan. > ------------------------------------------------------------------------------------------------------------------- > > Key: IKASAN-2475 > URL: https://ikasan.atlassian.net/browse/IKASAN-2475 > Project: Ikasan > Issue Type: Story > Affects Versions: eip-3.3.5 > Reporter: Michael Stewart > Assignee: David Hilton > Fix For: eip-4.1.0, eip-3.3.6, eip-4.0.3 > > -- This message was sent by Atlassian Jira Manage notifications: https://ikasan.atlassian.net/jira/settings/personal/notifications?emailPreferences=true#emailpreferences (v1001.0.0-SNAPSHOT#100266) |
|
From: Michael S. (JIRA) <ji...@ik...> - 2024-09-17 06:24:44
|
Michael Stewart created IKASAN-2475:
---------------------------------------
Summary: Add filter to shceduler agent command job processor flow that filters out jobs that do not have an active job plan.
Key: IKASAN-2475
URL: https://ikasan.atlassian.net/browse/IKASAN-2475
Project: Ikasan
Issue Type: Story
Affects Versions: eip-3.3.5
Reporter: Michael Stewart
Assignee: David Hilton
Fix For: eip-4.1.0, eip-3.3.6, eip-4.0.3
--
This message was sent by Atlassian Jira
Manage notifications: https://ikasan.atlassian.net/jira/settings/personal/notifications?emailPreferences=true#emailpreferences
(v1001.0.0-SNAPSHOT#100266)
|
|
From: David H. (JIRA) <ji...@ik...> - 2024-09-14 12:51:04
|
[ https://ikasan.atlassian.net/browse/IKASAN-2473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Hilton updated IKASAN-2473: --------------------------------- Description: There is a known issue on Windows where chained processes do not accurately capture the return status of jobs (see {{https://github.com/PowerShell/PowerShell/issues/20400#issuecomment-1740954070}}) We have seen this issue during development and opted to be cautious when a return code of 0 is provided if the error log is not empty, an error has likely occurred, especially on Windows. In this scenario, if {{errorLogWithZeroStatusConsideredError}} has been set to true (default false), we will set the set. {noformat}scheduledProcessEvent.setSuccessful(false); scheduledProcessEvent.setReturnCode(${job.monitoring.broker.errorlog.populated.error.code:-124816});{noformat} Though this feature is targeted at Windows, there is no extra cost in providing it for Unix as well. For commands that (incorrectly) write non-errors to the standard output stream, the advice will be to use the standard error to standard out redirection i.e. 2>&1. This will be covered in user documentation. An additional issue was discovered during testing (edge case). If the child process has completed after the 5-second pause (essential on Windows to allow the process tree to be created) but before the pid of the child is extracted from the process tree, we have a (known) sub-optimal processing route. The previous (sub-optimal) mitigation was to default back to monitoring the parent process (always present in the handle) and of course that would be in non-detached mode. Due to issues with Powershell, we are still exposed to the known Powershell bug that causes return codes to get lost. Now we remain in detached mode even though we are monitoring the parent, which is more reliable with respect to return code. was: There is a known issue on Windows where chained processes do not accurately capture the return status of jobs (see {{https://github.com/PowerShell/PowerShell/issues/20400#issuecomment-1740954070}}) We have seen this issue during development and opted to be cautious when a return code of 0 is provided if the error log is not empty, an error has likely occurred, especially on Windows. In this scenario, if {{errorLogWithZeroStatusConsideredError}} has been set to true (default false), we will set the set. {noformat}scheduledProcessEvent.setSuccessful(false); scheduledProcessEvent.setReturnCode(${job.monitoring.broker.errorlog.populated.error.code:-124816});{noformat} Though this feature is targeted at Windows, there is no extra cost in providing it for Unix as well. For commands that (incorrectly) write non-errors to the standard output stream, the advice will be to use the standard error to standard out redirection i.e. 2>&1. This will be covered in user documentation. > IES Agent add optional alerting when return code 0 but the error log populated. > ------------------------------------------------------------------------------- > > Key: IKASAN-2473 > URL: https://ikasan.atlassian.net/browse/IKASAN-2473 > Project: Ikasan > Issue Type: Story > Components: scheduler-agent > Affects Versions: eip-3.3.5 > Environment: All > Reporter: David Hilton > Assignee: David Hilton > Priority: Minor > > There is a known issue on Windows where chained processes do not accurately capture the return status of jobs (see {{https://github.com/PowerShell/PowerShell/issues/20400#issuecomment-1740954070}}) > We have seen this issue during development and opted to be cautious when a return code of 0 is provided if the error log is not empty, an error has likely occurred, especially on Windows. > In this scenario, if {{errorLogWithZeroStatusConsideredError}} has been set to true (default false), we will set the set. > {noformat}scheduledProcessEvent.setSuccessful(false); > scheduledProcessEvent.setReturnCode(${job.monitoring.broker.errorlog.populated.error.code:-124816});{noformat} > Though this feature is targeted at Windows, there is no extra cost in providing it for Unix as well. > For commands that (incorrectly) write non-errors to the standard output stream, the advice will be to use the standard error to standard out redirection i.e. 2>&1. This will be covered in user documentation. > An additional issue was discovered during testing (edge case). If the child process has completed after the 5-second pause (essential on Windows to allow the process tree to be created) but before the pid of the child is extracted from the process tree, we have a (known) sub-optimal processing route. > The previous (sub-optimal) mitigation was to default back to monitoring the parent process (always present in the handle) and of course that would be in non-detached mode. Due to issues with Powershell, we are still exposed to the known Powershell bug that causes return codes to get lost. Now we remain in detached mode even though we are monitoring the parent, which is more reliable with respect to return code. -- This message was sent by Atlassian Jira Manage notifications: https://ikasan.atlassian.net/jira/settings/personal/notifications?emailPreferences=true#emailpreferences (v1001.0.0-SNAPSHOT#100266) |
|
From: Michael S. (JIRA) <ji...@ik...> - 2024-09-14 06:29:42
|
[ https://ikasan.atlassian.net/browse/IKASAN-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stewart resolved IKASAN-2474. ------------------------------------- Resolution: Fixed > In dashboard scheduler designer, OR relationship turned to AND > -------------------------------------------------------------- > > Key: IKASAN-2474 > URL: https://ikasan.atlassian.net/browse/IKASAN-2474 > Project: Ikasan > Issue Type: Story > Components: job-orchestration, visualisation > Affects Versions: dashboard-4.0.0 > Reporter: Michael Stewart > Assignee: Michael Stewart > Fix For: dashboard-4.0.1 > > Attachments: image-20240913-162329.png, image-20240913-162426.png > > > Steps > # Create a plan with 2 trigger jobs and 2 command execution jobs > # Ensure the 2 trigger jobs are surrounded by an or condition. > # Same the jobplan and close the window > # Reopen the job plan edit window > Expected > The OR condition remains around the triggering jobs > Actual > The triggering jobs are surrounded by 2 nested and conditions. > !image-20240913-162329.png|width=50%,alt="image-20240913-162329.png"! > !image-20240913-162426.png|width=1270,height=901,alt="image-20240913-162426.png"! -- This message was sent by Atlassian Jira Manage notifications: https://ikasan.atlassian.net/jira/settings/personal/notifications?emailPreferences=true#emailpreferences (v1001.0.0-SNAPSHOT#100266) |
|
From: Michael S. (JIRA) <ji...@ik...> - 2024-09-13 16:28:13
|
[ https://ikasan.atlassian.net/browse/IKASAN-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stewart updated IKASAN-2470: ------------------------------------ Fix versions: dashboard-4.0.1 (was: dashboard-4.1.0) > Add feature to hover over the job icon on visualisation screens in order to provide details of the job execution > ---------------------------------------------------------------------------------------------------------------- > > Key: IKASAN-2470 > URL: https://ikasan.atlassian.net/browse/IKASAN-2470 > Project: Ikasan > Issue Type: Improvement > Components: visualisation > Affects Versions: dashboard-4.0.0 > Reporter: Michael Stewart > Assignee: Michael Stewart > Priority: Minor > Fix For: dashboard-4.0.1 > > -- This message was sent by Atlassian Jira Manage notifications: https://ikasan.atlassian.net/jira/settings/personal/notifications?emailPreferences=true#emailpreferences (v1001.0.0-SNAPSHOT#100266) |
|
From: Michael S. (JIRA) <ji...@ik...> - 2024-09-13 16:27:55
|
[ https://ikasan.atlassian.net/browse/IKASAN-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stewart updated IKASAN-2474: ------------------------------------ Fix versions: dashboard-4.0.1 (was: dashboard-4.1.0) > In dashboard scheduler designer, OR relationship turned to AND > -------------------------------------------------------------- > > Key: IKASAN-2474 > URL: https://ikasan.atlassian.net/browse/IKASAN-2474 > Project: Ikasan > Issue Type: Story > Components: job-orchestration, visualisation > Affects Versions: dashboard-4.0.0 > Reporter: Michael Stewart > Assignee: Michael Stewart > Fix For: dashboard-4.0.1 > > Attachments: image-20240913-162329.png, image-20240913-162426.png > > > Steps > # Create a plan with 2 trigger jobs and 2 command execution jobs > # Ensure the 2 trigger jobs are surrounded by an or condition. > # Same the jobplan and close the window > # Reopen the job plan edit window > Expected > The OR condition remains around the triggering jobs > Actual > The triggering jobs are surrounded by 2 nested and conditions. > !image-20240913-162329.png|width=50%,alt="image-20240913-162329.png"! > !image-20240913-162426.png|width=1270,height=901,alt="image-20240913-162426.png"! -- This message was sent by Atlassian Jira Manage notifications: https://ikasan.atlassian.net/jira/settings/personal/notifications?emailPreferences=true#emailpreferences (v1001.0.0-SNAPSHOT#100266) |
|
From: Michael S. (JIRA) <ji...@ik...> - 2024-09-13 16:27:44
|
[ https://ikasan.atlassian.net/browse/IKASAN-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stewart updated IKASAN-2469: ------------------------------------ Fix versions: dashboard-4.0.1 (was: dashboard-3.3.8) (was: dashboard-4.1.0) > Add mouse wheel scrolling to draw2d JS visualisations > ----------------------------------------------------- > > Key: IKASAN-2469 > URL: https://ikasan.atlassian.net/browse/IKASAN-2469 > Project: Ikasan > Issue Type: Improvement > Components: visualisation > Affects Versions: dashboard-3.3.7 > Reporter: Michael Stewart > Assignee: Michael Stewart > Priority: Minor > Fix For: dashboard-4.0.1 > > -- This message was sent by Atlassian Jira Manage notifications: https://ikasan.atlassian.net/jira/settings/personal/notifications?emailPreferences=true#emailpreferences (v1001.0.0-SNAPSHOT#100266) |
|
From: Michael S. (JIRA) <ji...@ik...> - 2024-09-13 16:24:52
|
[ https://ikasan.atlassian.net/browse/IKASAN-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IKASAN-2474 started by Michael Stewart. ----------------------------------------------- > In dashboard scheduler designer, OR relationship turned to AND > -------------------------------------------------------------- > > Key: IKASAN-2474 > URL: https://ikasan.atlassian.net/browse/IKASAN-2474 > Project: Ikasan > Issue Type: Story > Components: job-orchestration, visualisation > Affects Versions: dashboard-4.0.0 > Reporter: Michael Stewart > Assignee: Michael Stewart > Fix For: dashboard-4.1.0 > > Attachments: image-20240913-162329.png, image-20240913-162426.png > > > Steps > # Create a plan with 2 trigger jobs and 2 command execution jobs > # Ensure the 2 trigger jobs are surrounded by an or condition. > # Same the jobplan and close the window > # Reopen the job plan edit window > Expected > The OR condition remains around the triggering jobs > Actual > The triggering jobs are surrounded by 2 nested and conditions. > !image-20240913-162329.png|width=50%,alt="image-20240913-162329.png"! > !image-20240913-162426.png|width=1270,height=901,alt="image-20240913-162426.png"! -- This message was sent by Atlassian Jira Manage notifications: https://ikasan.atlassian.net/jira/settings/personal/notifications?emailPreferences=true#emailpreferences (v1001.0.0-SNAPSHOT#100266) |
|
From: Michael S. (JIRA) <ji...@ik...> - 2024-09-13 16:24:45
|
[ https://ikasan.atlassian.net/browse/IKASAN-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stewart updated IKASAN-2474: ------------------------------------ Description: Steps # Create a plan with 2 trigger jobs and 2 command execution jobs # Ensure the 2 trigger jobs are surrounded by an or condition. # Same the jobplan and close the window # Reopen the job plan edit window Expected The OR condition remains around the triggering jobs Actual The triggering jobs are surrounded by 2 nested and conditions. !image-20240913-162329.png|width=50%,alt="image-20240913-162329.png"! !image-20240913-162426.png|width=1270,height=901,alt="image-20240913-162426.png"! > In dashboard scheduler designer, OR relationship turned to AND > -------------------------------------------------------------- > > Key: IKASAN-2474 > URL: https://ikasan.atlassian.net/browse/IKASAN-2474 > Project: Ikasan > Issue Type: Story > Components: job-orchestration, visualisation > Affects Versions: dashboard-4.0.0 > Reporter: Michael Stewart > Assignee: Michael Stewart > Fix For: dashboard-4.1.0 > > Attachments: image-20240913-162329.png, image-20240913-162426.png > > > Steps > # Create a plan with 2 trigger jobs and 2 command execution jobs > # Ensure the 2 trigger jobs are surrounded by an or condition. > # Same the jobplan and close the window > # Reopen the job plan edit window > Expected > The OR condition remains around the triggering jobs > Actual > The triggering jobs are surrounded by 2 nested and conditions. > !image-20240913-162329.png|width=50%,alt="image-20240913-162329.png"! > !image-20240913-162426.png|width=1270,height=901,alt="image-20240913-162426.png"! -- This message was sent by Atlassian Jira Manage notifications: https://ikasan.atlassian.net/jira/settings/personal/notifications?emailPreferences=true#emailpreferences (v1001.0.0-SNAPSHOT#100266) |
|
From: Michael S. (JIRA) <ji...@ik...> - 2024-09-13 16:22:44
|
Michael Stewart created IKASAN-2474:
---------------------------------------
Summary: In dashboard scheduler designer, OR relationship turned to AND
Key: IKASAN-2474
URL: https://ikasan.atlassian.net/browse/IKASAN-2474
Project: Ikasan
Issue Type: Story
Components: job-orchestration, visualisation
Affects Versions: dashboard-4.0.0
Reporter: Michael Stewart
Assignee: Michael Stewart
Fix For: dashboard-4.1.0
--
This message was sent by Atlassian Jira
Manage notifications: https://ikasan.atlassian.net/jira/settings/personal/notifications?emailPreferences=true#emailpreferences
(v1001.0.0-SNAPSHOT#100266)
|
|
From: David H. (JIRA) <ji...@ik...> - 2024-09-13 11:42:52
|
[ https://ikasan.atlassian.net/browse/IKASAN-2473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Hilton updated IKASAN-2473: --------------------------------- Summary: IES Agent add optional alerting when return code 0 but the error log populated. (was: IES Agent add optional alerting when return code 0 but error log populated.) > IES Agent add optional alerting when return code 0 but the error log populated. > ------------------------------------------------------------------------------- > > Key: IKASAN-2473 > URL: https://ikasan.atlassian.net/browse/IKASAN-2473 > Project: Ikasan > Issue Type: Story > Components: scheduler-agent > Affects Versions: eip-3.3.5 > Environment: All > Reporter: David Hilton > Assignee: David Hilton > Priority: Minor > > There is a known issue on Windows where chained processes do not accurately capture the return status of jobs (see {{https://github.com/PowerShell/PowerShell/issues/20400#issuecomment-1740954070}}) > We have seen this issue during development and opted to be cautious when a return code of 0 is provided if the error log is not empty, an error has likely occurred, especially on Windows. > In this scenario, if {{errorLogWithZeroStatusConsideredError}} has been set to true (default false), we will set the set. > {noformat}scheduledProcessEvent.setSuccessful(false); > scheduledProcessEvent.setReturnCode(${job.monitoring.broker.errorlog.populated.error.code:-124816});{noformat} > Though this feature is targeted at Windows, there is no extra cost in providing it for Unix as well. > For commands that (incorrectly) write non-errors to the standard output stream, the advice will be to use the standard error to standard out redirection i.e. 2>&1. This will be covered in user documentation. -- This message was sent by Atlassian Jira Manage notifications: https://ikasan.atlassian.net/jira/settings/personal/notifications?emailPreferences=true#emailpreferences (v1001.0.0-SNAPSHOT#100266) |
|
From: David H. (JIRA) <ji...@ik...> - 2024-09-13 11:42:00
|
[ https://ikasan.atlassian.net/browse/IKASAN-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21501#comment-21501 ] David Hilton commented on IKASAN-2466: -------------------------------------- The current defaults of 3-second intervals and 20 retries will be updated to 3-second intervals and 60 retries i.e. 3 minutes. This has been based on empirical tests with large parallel command execution jobs. > IES Agent (Widows OS only) slow to write process files to the file system. Need to add wait/retry mechanism if file does not yet exist when job has completed > -------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: IKASAN-2466 > URL: https://ikasan.atlassian.net/browse/IKASAN-2466 > Project: Ikasan > Issue Type: Improvement > Components: scheduler-agent > Affects Versions: eip-3.3.5 > Reporter: Michael Stewart > Assignee: David Hilton > Priority: Blocker > Fix For: eip-4.1.0, eip-3.3.6, eip-4.0.3 > > -- This message was sent by Atlassian Jira Manage notifications: https://ikasan.atlassian.net/jira/settings/personal/notifications?emailPreferences=true#emailpreferences (v1001.0.0-SNAPSHOT#100266) |
|
From: David H. (JIRA) <ji...@ik...> - 2024-09-13 11:40:08
|
[ https://ikasan.atlassian.net/browse/IKASAN-2473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IKASAN-2473 started by David Hilton. -------------------------------------------- > IES Agent add optional alerting when return code 0 but error log populated. > --------------------------------------------------------------------------- > > Key: IKASAN-2473 > URL: https://ikasan.atlassian.net/browse/IKASAN-2473 > Project: Ikasan > Issue Type: Story > Components: scheduler-agent > Affects Versions: eip-3.3.5 > Environment: All > Reporter: David Hilton > Assignee: David Hilton > Priority: Minor > > There is a known issue on Windows where chained processes do not accurately capture the return status of jobs (see {{https://github.com/PowerShell/PowerShell/issues/20400#issuecomment-1740954070}}) > We have seen this issue during development and opted to be cautious when a return code of 0 is provided if the error log is not empty, an error has likely occurred, especially on Windows. > In this scenario, if {{errorLogWithZeroStatusConsideredError}} has been set to true (default false), we will set the set. > {noformat}scheduledProcessEvent.setSuccessful(false); > scheduledProcessEvent.setReturnCode(${job.monitoring.broker.errorlog.populated.error.code:-124816});{noformat} > Though this feature is targeted at Windows, there is no extra cost in providing it for Unix as well. > For commands that (incorrectly) write non-errors to the standard output stream, the advice will be to use the standard error to standard out redirection i.e. 2>&1. This will be covered in user documentation. -- This message was sent by Atlassian Jira Manage notifications: https://ikasan.atlassian.net/jira/settings/personal/notifications?emailPreferences=true#emailpreferences (v1001.0.0-SNAPSHOT#100266) |
|
From: David H. (JIRA) <ji...@ik...> - 2024-09-13 11:39:34
|
David Hilton created IKASAN-2473:
------------------------------------
Summary: IES Agent add optional alerting when return code 0 but error log populated.
Key: IKASAN-2473
URL: https://ikasan.atlassian.net/browse/IKASAN-2473
Project: Ikasan
Issue Type: Story
Components: scheduler-agent
Affects Versions: eip-3.3.5
Environment: All
Reporter: David Hilton
Assignee: David Hilton
Priority: Minor
There is a known issue on Windows where chained processes do not accurately capture the return status of jobs (see {{https://github.com/PowerShell/PowerShell/issues/20400#issuecomment-1740954070}})
We have seen this issue during development and opted to be cautious when a return code of 0 is provided if the error log is not empty, an error has likely occurred, especially on Windows.
In this scenario, if {{errorLogWithZeroStatusConsideredError}} has been set to true (default false), we will set the set.
{noformat}scheduledProcessEvent.setSuccessful(false);
scheduledProcessEvent.setReturnCode(${job.monitoring.broker.errorlog.populated.error.code:-124816});{noformat}
Though this feature is targeted at Windows, there is no extra cost in providing it for Unix as well.
For commands that (incorrectly) write non-errors to the standard output stream, the advice will be to use the standard error to standard out redirection i.e. 2>&1. This will be covered in user documentation.
--
This message was sent by Atlassian Jira
Manage notifications: https://ikasan.atlassian.net/jira/settings/personal/notifications?emailPreferences=true#emailpreferences
(v1001.0.0-SNAPSHOT#100266)
|
|
From: Michael S. (JIRA) <ji...@ik...> - 2024-09-13 05:44:05
|
[ https://ikasan.atlassian.net/browse/IKASAN-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stewart updated IKASAN-2331: ------------------------------------ Affects versions: dashboard-3.3.0 > Upgrade Ikasan to H2 2.2.224 > ---------------------------- > > Key: IKASAN-2331 > URL: https://ikasan.atlassian.net/browse/IKASAN-2331 > Project: Ikasan > Issue Type: Story > Affects Versions: dashboard-3.3.0, eip-3.3.3 > Reporter: Michael Stewart > Assignee: Michael Stewart > Fix For: eip-4.0.0, dashboard-4.0.0 > > -- This message was sent by Atlassian Jira Manage notifications: https://ikasan.atlassian.net/jira/settings/personal/notifications?emailPreferences=true#emailpreferences (v1001.0.0-SNAPSHOT#100266) |
|
From: Michael S. (JIRA) <ji...@ik...> - 2024-09-13 05:43:08
|
[ https://ikasan.atlassian.net/browse/IKASAN-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stewart closed IKASAN-2331. ----------------------------------- > Upgrade Ikasan to H2 2.2.224 > ---------------------------- > > Key: IKASAN-2331 > URL: https://ikasan.atlassian.net/browse/IKASAN-2331 > Project: Ikasan > Issue Type: Story > Affects Versions: dashboard-3.3.0, eip-3.3.3 > Reporter: Michael Stewart > Assignee: Michael Stewart > Fix For: eip-4.0.0, dashboard-4.0.0 > > -- This message was sent by Atlassian Jira Manage notifications: https://ikasan.atlassian.net/jira/settings/personal/notifications?emailPreferences=true#emailpreferences (v1001.0.0-SNAPSHOT#100266) |
|
From: Michael S. (JIRA) <ji...@ik...> - 2024-09-13 05:43:02
|
[ https://ikasan.atlassian.net/browse/IKASAN-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stewart resolved IKASAN-2331. ------------------------------------- Resolution: Fixed > Upgrade Ikasan to H2 2.2.224 > ---------------------------- > > Key: IKASAN-2331 > URL: https://ikasan.atlassian.net/browse/IKASAN-2331 > Project: Ikasan > Issue Type: Story > Affects Versions: dashboard-3.3.0, eip-3.3.3 > Reporter: Michael Stewart > Assignee: Michael Stewart > Fix For: eip-4.0.0, dashboard-4.0.0 > > -- This message was sent by Atlassian Jira Manage notifications: https://ikasan.atlassian.net/jira/settings/personal/notifications?emailPreferences=true#emailpreferences (v1001.0.0-SNAPSHOT#100266) |
|
From: Michael S. (JIRA) <ji...@ik...> - 2024-09-13 05:42:32
|
[ https://ikasan.atlassian.net/browse/IKASAN-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stewart updated IKASAN-2331: ------------------------------------ Fix versions: dashboard-4.0.0 > Upgrade Ikasan to H2 2.2.224 > ---------------------------- > > Key: IKASAN-2331 > URL: https://ikasan.atlassian.net/browse/IKASAN-2331 > Project: Ikasan > Issue Type: Story > Affects Versions: eip-3.3.3 > Reporter: Michael Stewart > Assignee: Michael Stewart > Fix For: eip-4.0.0, dashboard-4.0.0 > > -- This message was sent by Atlassian Jira Manage notifications: https://ikasan.atlassian.net/jira/settings/personal/notifications?emailPreferences=true#emailpreferences (v1001.0.0-SNAPSHOT#100266) |
|
From: Michael S. (JIRA) <ji...@ik...> - 2024-09-13 05:42:19
|
[ https://ikasan.atlassian.net/browse/IKASAN-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stewart reopened IKASAN-2331: ------------------------------------- > Upgrade Ikasan to H2 2.2.224 > ---------------------------- > > Key: IKASAN-2331 > URL: https://ikasan.atlassian.net/browse/IKASAN-2331 > Project: Ikasan > Issue Type: Story > Affects Versions: eip-3.3.3 > Reporter: Michael Stewart > Assignee: Michael Stewart > Fix For: eip-4.0.0 > > -- This message was sent by Atlassian Jira Manage notifications: https://ikasan.atlassian.net/jira/settings/personal/notifications?emailPreferences=true#emailpreferences (v1001.0.0-SNAPSHOT#100266) |