Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remove repository log #47

Closed
ThorbenLindhauer opened this issue Sep 2, 2016 · 0 comments
Closed

Remove repository log #47

ThorbenLindhauer opened this issue Sep 2, 2016 · 0 comments
Assignees
@meyerdan

Comments

@ThorbenLindhauer
Copy link
Member

  • From a user's perspective, this removes the delay between deploying a process model and being able to instantiate it on a runtime log
  • When deploying a process model, a target runtime log id must be provided
  • Internally, we no longer have to keep redundant log entries (i.e. workflow definition entries on both, repository and runtime logs)
@ThorbenLindhauer ThorbenLindhauer self-assigned this Sep 2, 2016
@ThorbenLindhauer ThorbenLindhauer changed the title Remove repository logs Remove repository log Sep 2, 2016
ThorbenLindhauer added a commit that referenced this issue Sep 9, 2016
@ThorbenLindhauer
improve(broker): write wf definitions directly to runtime log
d876848 
- removes repository log

related to #47
ThorbenLindhauer added a commit that referenced this issue Sep 9, 2016
@ThorbenLindhauer
fix(broker): recovery should not read past the log's tail
4359b5b 
- fixes the integration test when a process instance is started after
  broker restart

related to #47, #26
ThorbenLindhauer added a commit that referenced this issue Sep 9, 2016
@ThorbenLindhauer
chore(broker): move classes from repository package to runtime
34307ce 
related to #47
meyerdan added a commit that referenced this issue Sep 21, 2016
@meyerdan
fix(broker): disable logging
594fb72 
related to #47
zeebe-bors-heroku bot pushed a commit that referenced this issue May 20, 2019
@zeebe-bors @Zelldon @dependabot-support
Merge #2479 #2493
7809ad1 
2479: Remove atomix dependency from engine module r=menski a=Zelldon

 * atomix dependency was mistakenly added to this module
 * the implementation of the snapshot replication should NOT be part of this module


2493: chore(deps): bump animal-sniffer-annotations from 1.17 to 1.18 r=menski a=dependabot[bot]

Bumps [animal-sniffer-annotations](https://github.com/mojohaus/animal-sniffer) from 1.17 to 1.18.
<details>
<summary>Commits</summary>

- [`fde3a20`](mojohaus/animal-sniffer@fde3a20) [maven-release-plugin] prepare release animal-sniffer-parent-1.18
- [`6c64478`](mojohaus/animal-sniffer@6c64478) back to 1.18-SNAPSHOT
- [`cf138c9`](mojohaus/animal-sniffer@cf138c9) [maven-release-plugin] prepare release animal-sniffer-parent-1.18
- [`375d1d2`](mojohaus/animal-sniffer@375d1d2) use last mojo parent 50
- [`7ce5177`](mojohaus/animal-sniffer@7ce5177) release upload failed back to 1.18-SNAPSHOT
- [`5b2107b`](mojohaus/animal-sniffer@5b2107b) [maven-release-plugin] prepare for next development iteration
- [`312c17c`](mojohaus/animal-sniffer@312c17c) [maven-release-plugin] prepare release animal-sniffer-parent-1.18
- [`a781fbc`](mojohaus/animal-sniffer@a781fbc) note on release flag in index page
- [`ea98b9e`](mojohaus/animal-sniffer@ea98b9e) add note on javac release flag
- [`fabc20f`](mojohaus/animal-sniffer@fabc20f) [#41](https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/41) - exception type detection ([#47](https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/47))
- Additional commits viewable in [compare view](mojohaus/animal-sniffer@animal-sniffer-parent-1.17...animal-sniffer-parent-1.18)
</details>
<br />

[![Dependabot compatibility score](https://api.dependabot.com/badges/compatibility_score?dependency-name=org.codehaus.mojo:animal-sniffer-annotations&package-manager=maven&previous-version=1.17&new-version=1.18)](https://dependabot.com/compatibility-score.html?dependency-name=org.codehaus.mojo:animal-sniffer-annotations&package-manager=maven&previous-version=1.17&new-version=1.18)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

</details>

Co-authored-by: Christopher Zell <zelldon91@googlemail.com>
Co-authored-by: dependabot[bot] <support@dependabot.com>
zeebe-bors-heroku bot pushed a commit that referenced this issue May 20, 2019
@zeebe-bors @dependabot-support
Merge #2493
018e078 
2493: chore(deps): bump animal-sniffer-annotations from 1.17 to 1.18 r=menski a=dependabot[bot]

Bumps [animal-sniffer-annotations](https://github.com/mojohaus/animal-sniffer) from 1.17 to 1.18.
<details>
<summary>Commits</summary>

- [`fde3a20`](mojohaus/animal-sniffer@fde3a20) [maven-release-plugin] prepare release animal-sniffer-parent-1.18
- [`6c64478`](mojohaus/animal-sniffer@6c64478) back to 1.18-SNAPSHOT
- [`cf138c9`](mojohaus/animal-sniffer@cf138c9) [maven-release-plugin] prepare release animal-sniffer-parent-1.18
- [`375d1d2`](mojohaus/animal-sniffer@375d1d2) use last mojo parent 50
- [`7ce5177`](mojohaus/animal-sniffer@7ce5177) release upload failed back to 1.18-SNAPSHOT
- [`5b2107b`](mojohaus/animal-sniffer@5b2107b) [maven-release-plugin] prepare for next development iteration
- [`312c17c`](mojohaus/animal-sniffer@312c17c) [maven-release-plugin] prepare release animal-sniffer-parent-1.18
- [`a781fbc`](mojohaus/animal-sniffer@a781fbc) note on release flag in index page
- [`ea98b9e`](mojohaus/animal-sniffer@ea98b9e) add note on javac release flag
- [`fabc20f`](mojohaus/animal-sniffer@fabc20f) [#41](https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/41) - exception type detection ([#47](https://github-redirect.dependabot.com/mojohaus/animal-sniffer/issues/47))
- Additional commits viewable in [compare view](mojohaus/animal-sniffer@animal-sniffer-parent-1.17...animal-sniffer-parent-1.18)
</details>
<br />

[![Dependabot compatibility score](https://api.dependabot.com/badges/compatibility_score?dependency-name=org.codehaus.mojo:animal-sniffer-annotations&package-manager=maven&previous-version=1.17&new-version=1.18)](https://dependabot.com/compatibility-score.html?dependency-name=org.codehaus.mojo:animal-sniffer-annotations&package-manager=maven&previous-version=1.17&new-version=1.18)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

</details>

Co-authored-by: dependabot[bot] <support@dependabot.com>
@sdorokhova sdorokhova mentioned this issue Feb 19, 2020
Closed
@Zelldon Zelldon mentioned this issue Mar 25, 2021
Closed
@Zelldon Zelldon mentioned this issue Dec 15, 2021
Closed
@Zelldon Zelldon mentioned this issue Aug 25, 2022
Closed
@megglos megglos mentioned this issue Dec 1, 2022
Closed
@Zelldon Zelldon mentioned this issue Feb 3, 2023
Merged
14 tasks
zeebe-bors-camunda bot added a commit that referenced this issue May 9, 2023
@zeebe-bors-camunda @remcowesterhoud
merge: #12697
0458119 
12697: Fix flaky `EmbeddedSubProcessTest` r=koevskinikola a=remcowesterhoud

## Description

<!-- Please explain the changes you made here. -->
The test was flaky because it could occur that the messages got published before the subscription were opened. As the messages have no TTL this means they were not getting correlated, as expected.

Log of a failing run:
```
C DPLY         CREATE            - #1-> -1  -1 - 
E PROC         CREATED           - #2->#1 K01 - process.xml -> "process..process" (version:1)
E DPLY         CREATED           - #3->#1 K02 - process.xml
E DPLY         FULLY_DISTRIBUTED - #4->#1 K02 - 
C CREA         CREATE            - #5-> -1  -1 - new <process "process..process"> with variables: {correlationKey=correlationKey}
E VAR          CREATED           - #6->#5 K04 - correlationKey->"correlationKey" in <process [K03]>
C PI           ACTIVATE          - #7->#5 K03 - PROCESS "process..process" in <process "process..process"[K03]>
E CREA         CREATED           - #8->#5 K05 - new <process "process..process"> with variables: {correlationKey=correlationKey}
E PI           ACTIVATING        - #9->#7 K03 - PROCESS "process..process" in <process "process..process"[K03]>
E PI           ACTIVATED         - #10->#7 K03 - PROCESS "process..process" in <process "process..process"[K03]>
C PI           ACTIVATE          - #11->#7  -1 - START_EVENT "startEv..8897acc" in <process "process..process"[K03]>
E PI           ACTIVATING        - #12->#11 K06 - START_EVENT "startEv..8897acc" in <process "process..process"[K03]>
E PI           ACTIVATED         - #13->#11 K06 - START_EVENT "startEv..8897acc" in <process "process..process"[K03]>
C PI           COMPLETE          - #14->#11 K06 - START_EVENT "startEv..8897acc" in <process "process..process"[K03]>
E PI           COMPLETING        - #15->#14 K06 - START_EVENT "startEv..8897acc" in <process "process..process"[K03]>
E PROC_MSG_SUB CREATING          - #16->#14 K07 - "eventSubProcess" (inter.) correlationKey: correlationKey `@[K03]` in <process "process..process"[K03]> (no vars)
E PI           COMPLETED         - #17->#14 K06 - START_EVENT "startEv..8897acc" in <process "process..process"[K03]>
E PI           SEQ_FLOW_TAKEN    - #18->#14 K08 - SEQUENCE_FLOW "sequenc..b7cb1a6" in <process "process..process"[K03]>
C PI           ACTIVATE          - #19->#14 K09 - SUB_PROCESS "subProcess" in <process "process..process"[K03]>
E PI           ACTIVATING        - #20->#19 K09 - SUB_PROCESS "subProcess" in <process "process..process"[K03]>
E PI           ACTIVATED         - #21->#19 K09 - SUB_PROCESS "subProcess" in <process "process..process"[K03]>
C PI           ACTIVATE          - #22->#19  -1 - START_EVENT "startEv..8b12a7c" in <process "process..process"[K03]>
E PI           ACTIVATING        - #23->#22 K10 - START_EVENT "startEv..8b12a7c" in <process "process..process"[K03]>
E PI           ACTIVATED         - #24->#22 K10 - START_EVENT "startEv..8b12a7c" in <process "process..process"[K03]>
C PI           COMPLETE          - #25->#22 K10 - START_EVENT "startEv..8b12a7c" in <process "process..process"[K03]>
E PI           COMPLETING        - #26->#25 K10 - START_EVENT "startEv..8b12a7c" in <process "process..process"[K03]>
E PROC_MSG_SUB CREATING          - #27->#25 K11 - "boundary" (inter.) correlationKey: correlationKey `@[K09]` in <process "process..process"[K03]> (no vars)
E PI           COMPLETED         - #28->#25 K10 - START_EVENT "startEv..8b12a7c" in <process "process..process"[K03]>
E PI           SEQ_FLOW_TAKEN    - #29->#25 K12 - SEQUENCE_FLOW "sequenc..8c72ad0" in <process "process..process"[K03]>
C PI           ACTIVATE          - #30->#25 K13 - SERVICE_TASK "task" in <process "process..process"[K03]>
E PI           ACTIVATING        - #31->#30 K13 - SERVICE_TASK "task" in <process "process..process"[K03]>
E JOB          CREATED           - #32->#30 K14 - K14 "task" `@"task"[K13]` 3 retries, in <process "process..process"[K03]> (no vars)
E PI           ACTIVATED         - #33->#30 K13 - SERVICE_TASK "task" in <process "process..process"[K03]>
C MSG          PUBLISH           - #34-> -1 K01 - "boundary" correlationKey: correlationKey (no vars)
C MSG          PUBLISH           - #35-> -1 K01 - "eventSubProcess" correlationKey: correlationKey (no vars)
E MSG          PUBLISHED         - #36->#34 K15 - "boundary" correlationKey: correlationKey (no vars)
E MSG          EXPIRED           - #37->#34 K15 - "boundary" correlationKey: correlationKey (no vars)
E MSG          PUBLISHED         - #38->#35 K16 - "eventSubProcess" correlationKey: correlationKey (no vars)
E MSG          EXPIRED           - #39->#35 K16 - "eventSubProcess" correlationKey: correlationKey (no vars)
C MSG_SUB      CREATE            - #40-> -1  -1 - "eventSubProcess" (inter.) correlationKey: correlationKey `@[K03]` in <process "process..process"[K03]> (no vars)
C MSG_SUB      CREATE            - #41-> -1  -1 - "boundary" (inter.) correlationKey: correlationKey `@[K09]` in <process "process..process"[K03]> (no vars)
E MSG_SUB      CREATED           - #42->#40 K17 - "eventSubProcess" (inter.) correlationKey: correlationKey `@[K03]` in <process "process..process"[K03]> (no vars)
C PROC_MSG_SUB CREATE            - #43-> -1  -1 - "eventSubProcess" (inter.) `@[K03]` in <process ?[K03]> (no vars)
E MSG_SUB      CREATED           - #44->#41 K18 - "boundary" (inter.) correlationKey: correlationKey `@[K09]` in <process "process..process"[K03]> (no vars)
C PROC_MSG_SUB CREATE            - #45-> -1  -1 - "boundary" (inter.) `@[K09]` in <process ?[K03]> (no vars)
E PROC_MSG_SUB CREATED           - #46->#43 K07 - "eventSubProcess" (inter.) correlationKey: correlationKey `@[K03]` in <process "process..process"[K03]> (no vars)
E PROC_MSG_SUB CREATED           - #47->#45 K11 - "boundary" (inter.) correlationKey: correlationKey `@[K09]` in <process "process..process"[K03]> (no vars)
```

The test isn't really flaky on 8.2+ anymore. This is a result of batch processing that was introduced recently. However, I believe it's still good to fix it on all versions and keep the test aligned across versions.

## Related issues

<!-- Which issues are closed by this PR or are related -->

closes #11844 



Co-authored-by: Remco Westerhoud <remco@westerhoud.nl>
@bugbugmaker bugbugmaker mentioned this issue Jun 16, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@meyerdan meyerdan

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@meyerdan @ThorbenLindhauer