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
(128) |
Oct
|
Nov
|
Dec
|
From: Michael S. (JIRA) <ji...@ik...> - 2021-09-01 06:54:03
|
[ https://ikasan.atlassian.net/browse/IKASAN-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stewart updated IKASAN-1914: ------------------------------------ Description: Reruns – we may need to rerun on the day, or occasionally historically. There is a business requirement for XXX to be able to correct and rerun the XXXX sensitivities up to 2 weeks (I think) beyond the month end run. Key thing here is that this should be a simple 1 click action. We need to avoid things like manual processes to reset XXX events as this is generally when things fail. > Reruns > ------ > > Key: IKASAN-1914 > URL: https://ikasan.atlassian.net/browse/IKASAN-1914 > Project: Ikasan > Issue Type: Story > Reporter: Michael Stewart > > Reruns – we may need to rerun on the day, or occasionally historically. There is a business requirement for XXX to be able to correct and rerun the XXXX sensitivities up to 2 weeks (I think) beyond the month end run. Key thing here is that this should be a simple 1 click action. We need to avoid things like manual processes to reset XXX events as this is generally when things fail. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175) |
From: Michael S. (JIRA) <ji...@ik...> - 2021-09-01 06:52:59
|
[ https://ikasan.atlassian.net/browse/IKASAN-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stewart updated IKASAN-1913: ------------------------------------ Description: Business day – batches work on a business day. This enables the batch date to be separated from the calendar date as the bulk of batch elements for business day x run on x+1 or beyond (like Product Control runs their Friday batch on Monday Morning) > Business day > ------------ > > Key: IKASAN-1913 > URL: https://ikasan.atlassian.net/browse/IKASAN-1913 > Project: Ikasan > Issue Type: Story > Reporter: Michael Stewart > > Business day – batches work on a business day. This enables the batch date to be separated from the calendar date as the bulk of batch elements for business day x run on x+1 or beyond (like Product Control runs their Friday batch on Monday Morning) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175) |
From: Michael S. (JIRA) <ji...@ik...> - 2021-09-01 06:52:35
|
Michael Stewart created IKASAN-1920: --------------------------------------- Summary: Summary Views Key: IKASAN-1920 URL: https://ikasan.atlassian.net/browse/IKASAN-1920 Project: Ikasan Issue Type: Story Reporter: Michael Stewart -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175) |
From: Michael S. (JIRA) <ji...@ik...> - 2021-09-01 06:52:23
|
Michael Stewart created IKASAN-1919: --------------------------------------- Summary: Easy supportability by non-developers Key: IKASAN-1919 URL: https://ikasan.atlassian.net/browse/IKASAN-1919 Project: Ikasan Issue Type: Story Reporter: Michael Stewart -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175) |
From: Michael S. (JIRA) <ji...@ik...> - 2021-09-01 06:51:52
|
Michael Stewart created IKASAN-1918: --------------------------------------- Summary: Multi-environment Key: IKASAN-1918 URL: https://ikasan.atlassian.net/browse/IKASAN-1918 Project: Ikasan Issue Type: Story Reporter: Michael Stewart -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175) |
From: Michael S. (JIRA) <ji...@ik...> - 2021-09-01 06:51:36
|
Michael Stewart created IKASAN-1917: --------------------------------------- Summary: Multi entity Key: IKASAN-1917 URL: https://ikasan.atlassian.net/browse/IKASAN-1917 Project: Ikasan Issue Type: Story Reporter: Michael Stewart -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175) |
From: Michael S. (JIRA) <ji...@ik...> - 2021-09-01 06:51:20
|
Michael Stewart created IKASAN-1916: --------------------------------------- Summary: Config insertion Key: IKASAN-1916 URL: https://ikasan.atlassian.net/browse/IKASAN-1916 Project: Ikasan Issue Type: Story Reporter: Michael Stewart -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175) |
From: Michael S. (JIRA) <ji...@ik...> - 2021-09-01 06:51:05
|
Michael Stewart created IKASAN-1914: --------------------------------------- Summary: Reruns Key: IKASAN-1914 URL: https://ikasan.atlassian.net/browse/IKASAN-1914 Project: Ikasan Issue Type: Story Reporter: Michael Stewart -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175) |
From: Michael S. (JIRA) <ji...@ik...> - 2021-09-01 06:51:03
|
Michael Stewart created IKASAN-1915: --------------------------------------- Summary: Dependencies Key: IKASAN-1915 URL: https://ikasan.atlassian.net/browse/IKASAN-1915 Project: Ikasan Issue Type: Story Reporter: Michael Stewart -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175) |
From: Michael S. (JIRA) <ji...@ik...> - 2021-09-01 06:50:30
|
Michael Stewart created IKASAN-1913: --------------------------------------- Summary: Business day Key: IKASAN-1913 URL: https://ikasan.atlassian.net/browse/IKASAN-1913 Project: Ikasan Issue Type: Story Reporter: Michael Stewart -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175) |
From: Michael S. (JIRA) <ji...@ik...> - 2021-09-01 06:49:21
|
Michael Stewart created IKASAN-1912: --------------------------------------- Summary: Enhancements to basic scheduler functionality Key: IKASAN-1912 URL: https://ikasan.atlassian.net/browse/IKASAN-1912 Project: Ikasan Issue Type: Epic Components: dashboard Affects Versions: 3.2.0 Reporter: Michael Stewart Fix For: 3.3.0 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175) |
From: Michael S. (JIRA) <ji...@ik...> - 2021-08-31 16:27:21
|
[ https://ikasan.atlassian.net/browse/IKASAN-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stewart resolved IKASAN-1911. ------------------------------------- Resolution: Fixed > Ikasan datasources missing configuration values for pool sizing and connection wait time. > ----------------------------------------------------------------------------------------- > > Key: IKASAN-1911 > URL: https://ikasan.atlassian.net/browse/IKASAN-1911 > Project: Ikasan > Issue Type: Improvement > Components: platform-setup > Affects Versions: 3.1.0, 3.0.1, 3.1.1 > Reporter: Michael Stewart > Assignee: Michael Stewart > Fix For: 3.0.2, 3.2.0, 3.1.2 > > > {code:java}<property name="initialSize" value="${datasource.min.pool.size:0}" /> > <property name="maxTotal" value="${datasource.max.pool.size:8}" /> > <property name="maxWaitMillis" value="${datasource.max.wait.millis:30000}" />{code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175) |
From: Michael S. (JIRA) <ji...@ik...> - 2021-08-31 16:23:53
|
[ https://ikasan.atlassian.net/browse/IKASAN-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stewart updated IKASAN-1911: ------------------------------------ Fix versions: 3.1.2 3.0.2 > Ikasan datasources missing configuration values for pool sizing and connection wait time. > ----------------------------------------------------------------------------------------- > > Key: IKASAN-1911 > URL: https://ikasan.atlassian.net/browse/IKASAN-1911 > Project: Ikasan > Issue Type: Improvement > Components: platform-setup > Affects Versions: 3.1.0, 3.0.1, 3.1.1 > Reporter: Michael Stewart > Assignee: Michael Stewart > Fix For: 3.0.2, 3.2.0, 3.1.2 > > > {code:java}<property name="initialSize" value="${datasource.min.pool.size:0}" /> > <property name="maxTotal" value="${datasource.max.pool.size:8}" /> > <property name="maxWaitMillis" value="${datasource.max.wait.millis:30000}" />{code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175) |
From: Michael S. (JIRA) <ji...@ik...> - 2021-08-31 16:23:45
|
[ https://ikasan.atlassian.net/browse/IKASAN-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stewart updated IKASAN-1911: ------------------------------------ Affects versions: 3.0.1 3.1.0 > Ikasan datasources missing configuration values for pool sizing and connection wait time. > ----------------------------------------------------------------------------------------- > > Key: IKASAN-1911 > URL: https://ikasan.atlassian.net/browse/IKASAN-1911 > Project: Ikasan > Issue Type: Improvement > Components: platform-setup > Affects Versions: 3.1.0, 3.0.1, 3.1.1 > Reporter: Michael Stewart > Assignee: Michael Stewart > Fix For: 3.2.0 > > > {code:java}<property name="initialSize" value="${datasource.min.pool.size:0}" /> > <property name="maxTotal" value="${datasource.max.pool.size:8}" /> > <property name="maxWaitMillis" value="${datasource.max.wait.millis:30000}" />{code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175) |
From: Michael S. (JIRA) <ji...@ik...> - 2021-08-31 16:23:24
|
[ https://ikasan.atlassian.net/browse/IKASAN-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stewart updated IKASAN-1911: ------------------------------------ Summary: Ikasan datasources missing configuration values for pool sizing and connection wait time. (was: Ikasan datasources missing configuration values for pool sizing.) > Ikasan datasources missing configuration values for pool sizing and connection wait time. > ----------------------------------------------------------------------------------------- > > Key: IKASAN-1911 > URL: https://ikasan.atlassian.net/browse/IKASAN-1911 > Project: Ikasan > Issue Type: Improvement > Components: platform-setup > Affects Versions: 3.1.1 > Reporter: Michael Stewart > Assignee: Michael Stewart > Fix For: 3.2.0 > > > {code:java}<property name="initialSize" value="${datasource.min.pool.size:0}" /> > <property name="maxTotal" value="${datasource.max.pool.size:8}" /> > <property name="maxWaitMillis" value="${datasource.max.wait.millis:30000}" />{code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175) |
From: Michael S. (JIRA) <ji...@ik...> - 2021-08-31 12:52:16
|
[ https://ikasan.atlassian.net/browse/IKASAN-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stewart updated IKASAN-1911: ------------------------------------ Description: {code:java}<property name="initialSize" value="${datasource.min.pool.size:0}" /> <property name="maxTotal" value="${datasource.max.pool.size:8}" /> <property name="maxWaitMillis" value="${datasource.max.wait.millis:30000}" />{code} was: {code:java} <property name="initialSize" value="${datasource.min.pool.size}" /> <property name="maxTotal" value="${datasource.max.pool.size}" /> {code} > Ikasan datasources missing configuration values for pool sizing. > ---------------------------------------------------------------- > > Key: IKASAN-1911 > URL: https://ikasan.atlassian.net/browse/IKASAN-1911 > Project: Ikasan > Issue Type: Improvement > Components: platform-setup > Affects Versions: 3.1.1 > Reporter: Michael Stewart > Assignee: Michael Stewart > Fix For: 3.2.0 > > > {code:java}<property name="initialSize" value="${datasource.min.pool.size:0}" /> > <property name="maxTotal" value="${datasource.max.pool.size:8}" /> > <property name="maxWaitMillis" value="${datasource.max.wait.millis:30000}" />{code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175) |
From: Michael S. (JIRA) <ji...@ik...> - 2021-08-31 12:49:29
|
[ https://ikasan.atlassian.net/browse/IKASAN-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stewart reopened IKASAN-1911: ------------------------------------- > Ikasan datasources missing configuration values for pool sizing. > ---------------------------------------------------------------- > > Key: IKASAN-1911 > URL: https://ikasan.atlassian.net/browse/IKASAN-1911 > Project: Ikasan > Issue Type: Improvement > Components: platform-setup > Affects Versions: 3.1.1 > Reporter: Michael Stewart > Assignee: Michael Stewart > Fix For: 3.2.0 > > > {code:java} > <property name="initialSize" value="${datasource.min.pool.size}" /> > <property name="maxTotal" value="${datasource.max.pool.size}" /> > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175) |
From: Michael S. (JIRA) <ji...@ik...> - 2021-08-31 09:36:49
|
[ https://ikasan.atlassian.net/browse/IKASAN-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stewart resolved IKASAN-1911. ------------------------------------- Resolution: Fixed > Ikasan datasources missing configuration values for pool sizing. > ---------------------------------------------------------------- > > Key: IKASAN-1911 > URL: https://ikasan.atlassian.net/browse/IKASAN-1911 > Project: Ikasan > Issue Type: Improvement > Components: platform-setup > Affects Versions: 3.1.1 > Reporter: Michael Stewart > Assignee: Michael Stewart > Fix For: 3.2.0 > > > {code:java} > <property name="initialSize" value="${datasource.min.pool.size}" /> > <property name="maxTotal" value="${datasource.max.pool.size}" /> > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175) |
From: Michael S. (JIRA) <ji...@ik...> - 2021-08-27 14:30:40
|
[ https://ikasan.atlassian.net/browse/IKASAN-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on IKASAN-1911 started by Michael Stewart. ----------------------------------------------- > Ikasan datasources missing configuration values for pool sizing. > ---------------------------------------------------------------- > > Key: IKASAN-1911 > URL: https://ikasan.atlassian.net/browse/IKASAN-1911 > Project: Ikasan > Issue Type: Improvement > Components: platform-setup > Affects Versions: 3.1.1 > Reporter: Michael Stewart > Assignee: Michael Stewart > Fix For: 3.2.0 > > > {code:java} > <property name="initialSize" value="${datasource.min.pool.size}" /> > <property name="maxTotal" value="${datasource.max.pool.size}" /> > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175) |
From: Michael S. (JIRA) <ji...@ik...> - 2021-08-27 14:30:25
|
Michael Stewart created IKASAN-1911: --------------------------------------- Summary: Ikasan datasources missing configuration values for pool sizing. Key: IKASAN-1911 URL: https://ikasan.atlassian.net/browse/IKASAN-1911 Project: Ikasan Issue Type: Improvement Components: platform-setup Affects Versions: 3.1.1 Reporter: Michael Stewart Assignee: Michael Stewart Fix For: 3.2.0 {code:java} <property name="initialSize" value="${datasource.min.pool.size}" /> <property name="maxTotal" value="${datasource.max.pool.size}" /> {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175) |
From: Kieron E. (JIRA) <ji...@ik...> - 2021-08-27 10:40:59
|
[ https://ikasan.atlassian.net/browse/IKASAN-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kieron Edwards updated IKASAN-1910: ----------------------------------- Description: Add main remaining component factories. > Add Scheduler , Sftp and Xml Component Factories > ------------------------------------------------ > > Key: IKASAN-1910 > URL: https://ikasan.atlassian.net/browse/IKASAN-1910 > Project: Ikasan > Issue Type: Story > Components: component > Affects Versions: 3.1.1 > Reporter: Kieron Edwards > Assignee: Kieron Edwards > Fix For: 3.2.0 > > > Add main remaining component factories. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175) |
From: Kieron E. (JIRA) <ji...@ik...> - 2021-08-27 10:40:27
|
Kieron Edwards created IKASAN-1910: -------------------------------------- Summary: Add Scheduler , Sftp and Xml Component Factories Key: IKASAN-1910 URL: https://ikasan.atlassian.net/browse/IKASAN-1910 Project: Ikasan Issue Type: Story Components: component Affects Versions: 3.1.1 Reporter: Kieron Edwards Assignee: Kieron Edwards Fix For: 3.2.0 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175) |
From: Kieron E. (JIRA) <ji...@ik...> - 2021-08-27 10:33:22
|
[ https://ikasan.atlassian.net/browse/IKASAN-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kieron Edwards resolved IKASAN-1894. ------------------------------------ Resolution: Fixed > Add Component Factory Spec, Common and JMS Factories > ---------------------------------------------------- > > Key: IKASAN-1894 > URL: https://ikasan.atlassian.net/browse/IKASAN-1894 > Project: Ikasan > Issue Type: Story > Reporter: Kieron Edwards > > Add component factories as described in [https://ikasan.atlassian.net/browse/IKASAN-1861|https://ikasan.atlassian.net/browse/IKASAN-1861|smart-link] minus the annotations which are no longer needed. > This JIRA adds > * ComponentFactory Spec Interface > * Common Component Factory Code > * Jms Component Factories -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175) |
From: herodotos (JIRA) <ji...@ik...> - 2021-08-27 06:04:43
|
[ https://ikasan.atlassian.net/browse/IKASAN-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] herodotos updated IKASAN-1898: ------------------------------ Description: [~accountid:557058:f1e82d5e-38b0-4849-a42f-4b99eae295b1] Suggests it may be possible to re-order operations so the flow changes state before touching the database. The Ikasan 3 dashboard had no errors for the module, flow state was reflecting as running. Timeline 2021-08-24 05:04:47 - harvesting / housekeeping jobs misfire e.g. {{ 2021-08-24 05:04:58 [DefaultQuartzScheduler_QuartzSchedulerThread] WARN o.i.s.IkasanSchedulerTriggerListener - Ikasan Platform Scheduled Trigger Listener Misfire. Trigger [housekeeping.wiretapHousekeepingJob] misfired at Sun Aug 08 06:23:25 BST 2021 for job [housekeeping.wiretapHousekeepingJob }} They all have misfired at Sun Aug 08 06:23:25 BST 2021 {{ 2021-08-24 05:06:44 - Transaction errors referencing lock problems - java.util.concurrent.locks.LockSupport.park - which originate in the Fix adaptor - This was attempting to persist a FIX message to the replay tables }} {{ 2021-08-24 05:06:54 - RecoveryManager resolves to Retry for FIX Consumer due to session not heartbeating: }} {{ 2021-08-24 05:06:54 [pool-37-thread-1] INFO o.i.r.ScheduledRecoveryManager - RecoveryManager resolving to [Retry (delay=30000, maxRetries=20)] for componentName[ FIX Consumer] exception [Session not heartbeating }} {{ 2021-08-24 05:06:58 - get a http 400 trying to publish to the Ikasan 3 dashboard - solr housekeeping was running at the time }} {{ 2021-08-24 05:06:58 [DefaultQuartzScheduler_Worker-8] WARN o.i.d.DashboardRestServiceImpl - Issue while publishing events to dashboard http://xxx.com:10000//rest/harvest/replay with response [400] [{"errorCode":null,"errorMessage":"An error has occurred attempting to perform a batch insert of }} {{ ReplayEvents!"}] }} 2021-08-24 05:06:58 - Harvesting / housekeeping misfires again {{ 2021-08-24 05:06:58 - RecoveryManager resolves to Stop for FIX Consumer (Again attempting to write FIX message to the replay tables) due to "org.hibernate.exception.GenericJDBCException: Unable to acquire JDBC Connection". }} {{ Caused by: java.sql.SQLException: Unable to enlist connection in the transaction }} {{ at org.apache.commons.dbcp2.managed.TransactionContext.setSharedConnection(TransactionContext.java:113) ~[commons-dbcp2-2.6.0.jar!/:2.6.0] }} {{ at org.apache.commons.dbcp2.managed.ManagedConnection.updateTransactionStatus(ManagedConnection.java:310) ~[commons-dbcp2-2.6.0.jar!/:2.6.0] }} {{ at org.apache.commons.dbcp2.managed.ManagedConnection.<init>(ManagedConnection.java:89) ~[commons-dbcp2-2.6.0.jar!/:2.6.0] }} {{ at org.apache.commons.dbcp2.managed.ManagedDataSource.getConnection(ManagedDataSource.java:64) ~[commons-dbcp2-2.6.0.jar!/:2.6.0] }} {{ at org.apache.commons.dbcp2.BasicDataSource.getConnection(BasicDataSource.java:809) ~[commons-dbcp2-2.6.0.jar!/:2.6.0] }} {{ at org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.getConnection(DatasourceConnectionProviderImpl.java:122) ~[hibernate-core-5.2.17.Final.jar!/:5.2.17.Final] }} {{ at org.hibernate.internal.NonContextualJdbcConnectionAccess.obtainConnection(NonContextualJdbcConnectionAccess.java:35) ~[hibernate-core-5.2.17.Final.jar!/:5.2.17.Final] }} {{ at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.acquireConnectionIfNeeded(LogicalConnectionManagedImpl.java:106) ~[hibernate-core-5.2.17.Final.jar!/:5.2.17.Final] }} {{ ... 57 common frames omitted }} {{ Caused by: java.lang.IllegalStateException: ARJUNA016063: The transaction is not active! }} {{ 2021-08-24 05:07:08 - First instance of "onLogout session no longer online" }} {{ 2021-08-24 05:08:38 - Harvesting / housekeeping misfires again }} {{ 2021-08-24 05:11:54 - Get the transaction errors referencing lock problems again - java.util.concurrent.locks.LockSupport.park - this time attempting to write to error reporting tables. }} This happens repeatedly until: {{ 2021-08-24 05:13:40 [Transaction Reaper Worker 0] WARN com.arjuna.ats.arjuna - ARJUNA012108: CheckedAction::check - atomic action 0:ffff0aa02011:a03f:610f6a48:3204868 aborting with 1 threads active! }} {{ 2021-08-24 05:13:40 [Transaction Reaper Worker 0] WARN o.h.r.t.b.j.i.s.SynchronizationCallbackCoordinatorTrackingImpl - HHH000451: Transaction afterCompletion called by a background thread; delaying afterCompletion processing until the original thread can handle it. [status=4] }} {{ 2021-08-24 05:13:40 [Transaction Reaper Worker 0] WARN com.arjuna.ats.arjuna - ARJUNA012121: TransactionReaper::doCancellations worker Thread[Transaction Reaper Worker 0,5,main] successfully canceled TX 0:ffff0aa02011:a03f:610f6a48:3204868 }} 2021-08-24 05:13:44 - onLogout session no longer online repeats all day, until flows are restarted and everything starts up normally. The module config was updated to seperate the harvesting and housekeeping schedules and also harvesting schedule changed to avoid clashing with solr housekeeping was: [~accountid:557058:f1e82d5e-38b0-4849-a42f-4b99eae295b1] Suggests it may be possible to re-order operations so the flow changes state before touching the database. The Ikasan 3 dashboard had no errors for the module, flow state was reflecting as running. Timeline 2021-08-24 05:04:47 - harvesting / housekeeping jobs misfire e.g. \{code} 2021-08-24 05:04:58 \[DefaultQuartzScheduler_QuartzSchedulerThread] WARN o.i.s.IkasanSchedulerTriggerListener - Ikasan Platform Scheduled Trigger Listener Misfire. Trigger \[housekeeping.wiretapHousekeepingJob] misfired at Sun Aug 08 06:23:25 BST 2021 for job \[housekeeping.wiretapHousekeepingJob They all have misfired at Sun Aug 08 06:23:25 BST 2021 \{code} 2021-08-24 05:06:44 - Transaction errors referencing lock problems - java.util.concurrent.locks.LockSupport.park - which originate in the Fix adaptor - This was attempting to persist a FIX message to the replay tables 2021-08-24 05:06:54 - RecoveryManager resolves to Retry for FIX Consumer due to session not heartbeating: 2021-08-24 05:06:54 \[pool-37-thread-1] INFO o.i.r.ScheduledRecoveryManager - RecoveryManager resolving to \[Retry (delay=30000, maxRetries=20)] for componentName\[ FIX Consumer] exception \[Session not heartbeating 2021-08-24 05:06:58 - get a http 400 trying to publish to the Ikasan 3 dashboard - solr housekeeping was running at the time \{code} 2021-08-24 05:06:58 \[DefaultQuartzScheduler_Worker-8] WARN o.i.d.DashboardRestServiceImpl - Issue while publishing events to dashboard [http://xxx.com:10000//rest/harvest/replay|http://xxx.com:10000//rest/harvest/replay] with response \[400] \[\{"errorCode":null,"errorMessage":"An error has occurred attempting to perform a batch insert of ReplayEvents\!"}] \{code} 2021-08-24 05:06:58 - Harvesting / housekeeping misfires again 2021-08-24 05:06:58 - RecoveryManager resolves to Stop for FIX Consumer (Again attempting to write FIX message to the replay tables) due to "org.hibernate.exception.GenericJDBCException: Unable to acquire JDBC Connection". \{code} Caused by: java.sql.SQLException: Unable to enlist connection in the transaction at org.apache.commons.dbcp2.managed.TransactionContext.setSharedConnection(TransactionContext.java:113) ~\[commons-dbcp2-2.6.0.jar\!/:2.6.0] at org.apache.commons.dbcp2.managed.ManagedConnection.updateTransactionStatus(ManagedConnection.java:310) ~\[commons-dbcp2-2.6.0.jar\!/:2.6.0] at org.apache.commons.dbcp2.managed.ManagedConnection.<init>(ManagedConnection.java:89) ~\[commons-dbcp2-2.6.0.jar\!/:2.6.0] at org.apache.commons.dbcp2.managed.ManagedDataSource.getConnection(ManagedDataSource.java:64) ~\[commons-dbcp2-2.6.0.jar\!/:2.6.0] at org.apache.commons.dbcp2.BasicDataSource.getConnection(BasicDataSource.java:809) ~\[commons-dbcp2-2.6.0.jar\!/:2.6.0] at org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.getConnection(DatasourceConnectionProviderImpl.java:122) ~\[hibernate-core-5.2.17.Final.jar\!/:5.2.17.Final] at org.hibernate.internal.NonContextualJdbcConnectionAccess.obtainConnection(NonContextualJdbcConnectionAccess.java:35) ~\[hibernate-core-5.2.17.Final.jar\!/:5.2.17.Final] at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.acquireConnectionIfNeeded(LogicalConnectionManagedImpl.java:106) ~\[hibernate-core-5.2.17.Final.jar\!/:5.2.17.Final] ... 57 common frames omitted Caused by: java.lang.IllegalStateException: ARJUNA016063: The transaction is not active\! \{code} 2021-08-24 05:07:08 - First instance of "onLogout session no longer online" 2021-08-24 05:08:38 - Harvesting / housekeeping misfires again 2021-08-24 05:11:54 - Get the transaction errors referencing lock problems again - java.util.concurrent.locks.LockSupport.park - this time attempting to write to error reporting tables. This happens repeatedly until: \{code} 2021-08-24 05:13:40 \[Transaction Reaper Worker 0] WARN com.arjuna.ats.arjuna - ARJUNA012108: CheckedAction::check - atomic action 0:ffff0aa02011:a03f:610f6a48:3204868 aborting with 1 threads active\! 2021-08-24 05:13:40 \[Transaction Reaper Worker 0] WARN o.h.r.t.b.j.i.s.SynchronizationCallbackCoordinatorTrackingImpl - HHH000451: Transaction afterCompletion called by a background thread; delaying afterCompletion processing until the original thread can handle it. \[status=4] 2021-08-24 05:13:40 \[Transaction Reaper Worker 0] WARN com.arjuna.ats.arjuna - ARJUNA012121: TransactionReaper::doCancellations worker Thread\[Transaction Reaper Worker 0,5,main] successfully canceled TX 0:ffff0aa02011:a03f:610f6a48:3204868 \{code} 2021-08-24 05:13:44 - onLogout session no longer online repeats all day, until flows are restarted and everything starts up normally. The module config was updated to seperate the harvesting and housekeeping schedules and also harvesting schedule changed to avoid clashing with solr housekeeping > Ikasan flow state not reflected in Dashboard/monitors, observed whilst H2 database had issues > --------------------------------------------------------------------------------------------- > > Key: IKASAN-1898 > URL: https://ikasan.atlassian.net/browse/IKASAN-1898 > Project: Ikasan > Issue Type: Bug > Affects Versions: 3.0.1 > Environment: Production > Reporter: Alwyn Donnell > Assignee: Jeff Mitchell > Priority: Critical > > [~accountid:557058:f1e82d5e-38b0-4849-a42f-4b99eae295b1] Suggests it may be possible to re-order operations so the flow changes state before touching the database. > The Ikasan 3 dashboard had no errors for the module, flow state was reflecting as running. > Timeline > 2021-08-24 05:04:47 - harvesting / housekeeping jobs misfire e.g. > {{ 2021-08-24 05:04:58 [DefaultQuartzScheduler_QuartzSchedulerThread] WARN o.i.s.IkasanSchedulerTriggerListener - Ikasan Platform Scheduled Trigger Listener Misfire. Trigger [housekeeping.wiretapHousekeepingJob] misfired at Sun Aug 08 06:23:25 BST 2021 for job [housekeeping.wiretapHousekeepingJob }} > They all have misfired at Sun Aug 08 06:23:25 BST 2021 > {{ 2021-08-24 05:06:44 - Transaction errors referencing lock problems - java.util.concurrent.locks.LockSupport.park - which originate in the Fix adaptor - This was attempting to persist a FIX message to the replay tables }} > {{ 2021-08-24 05:06:54 - RecoveryManager resolves to Retry for FIX Consumer due to session not heartbeating: }} > {{ 2021-08-24 05:06:54 [pool-37-thread-1] INFO o.i.r.ScheduledRecoveryManager - RecoveryManager resolving to [Retry (delay=30000, maxRetries=20)] for componentName[ FIX Consumer] exception [Session not heartbeating }} > {{ 2021-08-24 05:06:58 - get a http 400 trying to publish to the Ikasan 3 dashboard - solr housekeeping was running at the time }} > {{ 2021-08-24 05:06:58 [DefaultQuartzScheduler_Worker-8] WARN o.i.d.DashboardRestServiceImpl - Issue while publishing events to dashboard http://xxx.com:10000//rest/harvest/replay with response [400] [{"errorCode":null,"errorMessage":"An error has occurred attempting to perform a batch insert of }} > {{ ReplayEvents!"}] }} > 2021-08-24 05:06:58 - Harvesting / housekeeping misfires again > {{ 2021-08-24 05:06:58 - RecoveryManager resolves to Stop for FIX Consumer (Again attempting to write FIX message to the replay tables) due to "org.hibernate.exception.GenericJDBCException: Unable to acquire JDBC Connection". }} > {{ Caused by: java.sql.SQLException: Unable to enlist connection in the transaction }} > {{ at org.apache.commons.dbcp2.managed.TransactionContext.setSharedConnection(TransactionContext.java:113) ~[commons-dbcp2-2.6.0.jar!/:2.6.0] }} > {{ at org.apache.commons.dbcp2.managed.ManagedConnection.updateTransactionStatus(ManagedConnection.java:310) ~[commons-dbcp2-2.6.0.jar!/:2.6.0] }} > {{ at org.apache.commons.dbcp2.managed.ManagedConnection.<init>(ManagedConnection.java:89) ~[commons-dbcp2-2.6.0.jar!/:2.6.0] }} > {{ at org.apache.commons.dbcp2.managed.ManagedDataSource.getConnection(ManagedDataSource.java:64) ~[commons-dbcp2-2.6.0.jar!/:2.6.0] }} > {{ at org.apache.commons.dbcp2.BasicDataSource.getConnection(BasicDataSource.java:809) ~[commons-dbcp2-2.6.0.jar!/:2.6.0] }} > {{ at org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.getConnection(DatasourceConnectionProviderImpl.java:122) ~[hibernate-core-5.2.17.Final.jar!/:5.2.17.Final] }} > {{ at org.hibernate.internal.NonContextualJdbcConnectionAccess.obtainConnection(NonContextualJdbcConnectionAccess.java:35) ~[hibernate-core-5.2.17.Final.jar!/:5.2.17.Final] }} > {{ at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.acquireConnectionIfNeeded(LogicalConnectionManagedImpl.java:106) ~[hibernate-core-5.2.17.Final.jar!/:5.2.17.Final] }} > {{ ... 57 common frames omitted }} > {{ Caused by: java.lang.IllegalStateException: ARJUNA016063: The transaction is not active! }} > {{ 2021-08-24 05:07:08 - First instance of "onLogout session no longer online" }} > {{ 2021-08-24 05:08:38 - Harvesting / housekeeping misfires again }} > {{ 2021-08-24 05:11:54 - Get the transaction errors referencing lock problems again - java.util.concurrent.locks.LockSupport.park - this time attempting to write to error reporting tables. }} > This happens repeatedly until: > {{ 2021-08-24 05:13:40 [Transaction Reaper Worker 0] WARN com.arjuna.ats.arjuna - ARJUNA012108: CheckedAction::check - atomic action 0:ffff0aa02011:a03f:610f6a48:3204868 aborting with 1 threads active! }} > {{ 2021-08-24 05:13:40 [Transaction Reaper Worker 0] WARN o.h.r.t.b.j.i.s.SynchronizationCallbackCoordinatorTrackingImpl - HHH000451: Transaction afterCompletion called by a background thread; delaying afterCompletion processing until the original thread can handle it. [status=4] }} > {{ 2021-08-24 05:13:40 [Transaction Reaper Worker 0] WARN com.arjuna.ats.arjuna - ARJUNA012121: TransactionReaper::doCancellations worker Thread[Transaction Reaper Worker 0,5,main] successfully canceled TX 0:ffff0aa02011:a03f:610f6a48:3204868 }} > 2021-08-24 05:13:44 - onLogout session no longer online repeats all day, until flows are restarted and everything starts up normally. > The module config was updated to seperate the harvesting and housekeeping schedules and also harvesting schedule changed to avoid clashing with solr housekeeping -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175) |
From: Jeff M. (JIRA) <ji...@ik...> - 2021-08-26 16:47:14
|
[ https://ikasan.atlassian.net/browse/IKASAN-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21296#comment-21296 ] Jeff Mitchell commented on IKASAN-1898: --------------------------------------- So this is a casualty of a root cause issue with the database. However, it does highlight that the ScheduledRecoverManager should assume that for any exceptions passed to the recovery manager to deal with it should firstly switch the state of the flow as needed. ie assume that the module is generally toxic and that no interaction has a guaranteed outcome ie to its database, dashboard, etc. So do what can be done within the smallest remit first ie change the state of the flow, before trying to log the error or interact with anything else. Need to have a look at the code to see how easy this would be. > Ikasan flow state not reflected in Dashboard/monitors, observed whilst H2 database had issues > --------------------------------------------------------------------------------------------- > > Key: IKASAN-1898 > URL: https://ikasan.atlassian.net/browse/IKASAN-1898 > Project: Ikasan > Issue Type: Bug > Affects Versions: 3.0.1 > Environment: Production > Reporter: Alwyn Donnell > Assignee: Jeff Mitchell > Priority: Critical > > [~accountid:557058:f1e82d5e-38b0-4849-a42f-4b99eae295b1] Suggests it may be possible to re-order operations so the flow changes state before touching the database. > The Ikasan 3 dashboard had no errors for the module, flow state was reflecting as running. > Timeline > 2021-08-24 05:04:47 - harvesting / housekeeping jobs misfire e.g. > \{code} > 2021-08-24 05:04:58 \[DefaultQuartzScheduler_QuartzSchedulerThread] WARN o.i.s.IkasanSchedulerTriggerListener - Ikasan Platform Scheduled Trigger Listener Misfire. Trigger \[housekeeping.wiretapHousekeepingJob] misfired at Sun Aug 08 06:23:25 BST 2021 for job \[housekeeping.wiretapHousekeepingJob > They all have misfired at Sun Aug 08 06:23:25 BST 2021 > \{code} > 2021-08-24 05:06:44 - Transaction errors referencing lock problems - java.util.concurrent.locks.LockSupport.park - which originate in the Fix adaptor - This was attempting to persist a FIX message to the replay tables > 2021-08-24 05:06:54 - RecoveryManager resolves to Retry for FIX Consumer due to session not heartbeating: > 2021-08-24 05:06:54 \[pool-37-thread-1] INFO o.i.r.ScheduledRecoveryManager - RecoveryManager resolving to \[Retry (delay=30000, maxRetries=20)] for componentName\[ FIX Consumer] exception \[Session not heartbeating > 2021-08-24 05:06:58 - get a http 400 trying to publish to the Ikasan 3 dashboard - solr housekeeping was running at the time > \{code} > 2021-08-24 05:06:58 \[DefaultQuartzScheduler_Worker-8] WARN o.i.d.DashboardRestServiceImpl - Issue while publishing events to dashboard [http://xxx.com:10000//rest/harvest/replay|http://xxx.com:10000//rest/harvest/replay] with response \[400] \[\{"errorCode":null,"errorMessage":"An error has occurred attempting to perform a batch insert of > ReplayEvents\!"}] > \{code} > 2021-08-24 05:06:58 - Harvesting / housekeeping misfires again > 2021-08-24 05:06:58 - RecoveryManager resolves to Stop for FIX Consumer (Again attempting to write FIX message to the replay tables) due to "org.hibernate.exception.GenericJDBCException: Unable to acquire JDBC Connection". > \{code} > Caused by: java.sql.SQLException: Unable to enlist connection in the transaction > at org.apache.commons.dbcp2.managed.TransactionContext.setSharedConnection(TransactionContext.java:113) ~\[commons-dbcp2-2.6.0.jar\!/:2.6.0] > at org.apache.commons.dbcp2.managed.ManagedConnection.updateTransactionStatus(ManagedConnection.java:310) ~\[commons-dbcp2-2.6.0.jar\!/:2.6.0] > at org.apache.commons.dbcp2.managed.ManagedConnection.<init>(ManagedConnection.java:89) ~\[commons-dbcp2-2.6.0.jar\!/:2.6.0] > at org.apache.commons.dbcp2.managed.ManagedDataSource.getConnection(ManagedDataSource.java:64) ~\[commons-dbcp2-2.6.0.jar\!/:2.6.0] > at org.apache.commons.dbcp2.BasicDataSource.getConnection(BasicDataSource.java:809) ~\[commons-dbcp2-2.6.0.jar\!/:2.6.0] > at org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.getConnection(DatasourceConnectionProviderImpl.java:122) ~\[hibernate-core-5.2.17.Final.jar\!/:5.2.17.Final] > at org.hibernate.internal.NonContextualJdbcConnectionAccess.obtainConnection(NonContextualJdbcConnectionAccess.java:35) ~\[hibernate-core-5.2.17.Final.jar\!/:5.2.17.Final] > at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.acquireConnectionIfNeeded(LogicalConnectionManagedImpl.java:106) ~\[hibernate-core-5.2.17.Final.jar\!/:5.2.17.Final] > ... 57 common frames omitted > Caused by: java.lang.IllegalStateException: ARJUNA016063: The transaction is not active\! > \{code} > 2021-08-24 05:07:08 - First instance of "onLogout session no longer online" > 2021-08-24 05:08:38 - Harvesting / housekeeping misfires again > 2021-08-24 05:11:54 - Get the transaction errors referencing lock problems again - java.util.concurrent.locks.LockSupport.park - this time attempting to write to error reporting tables. This happens repeatedly until: > \{code} > 2021-08-24 05:13:40 \[Transaction Reaper Worker 0] WARN com.arjuna.ats.arjuna - ARJUNA012108: CheckedAction::check - atomic action 0:ffff0aa02011:a03f:610f6a48:3204868 aborting with 1 threads active\! > 2021-08-24 05:13:40 \[Transaction Reaper Worker 0] WARN o.h.r.t.b.j.i.s.SynchronizationCallbackCoordinatorTrackingImpl - HHH000451: Transaction afterCompletion called by a background thread; delaying afterCompletion processing until the original thread can handle it. \[status=4] > 2021-08-24 05:13:40 \[Transaction Reaper Worker 0] WARN com.arjuna.ats.arjuna - ARJUNA012121: TransactionReaper::doCancellations worker Thread\[Transaction Reaper Worker 0,5,main] successfully canceled TX 0:ffff0aa02011:a03f:610f6a48:3204868 > \{code} > 2021-08-24 05:13:44 - onLogout session no longer online repeats all day, until flows are restarted and everything starts up normally. > The module config was updated to seperate the harvesting and housekeeping schedules and also harvesting schedule changed to avoid clashing with solr housekeeping -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100175) |