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.

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

Fix potential threadLocalTrxName leakage #5778

metas-ts opened this issue Nov 11, 2019 · 0 comments


Copy link

@metas-ts metas-ts commented Nov 11, 2019

Is this a bug or feature request?


What is the current behavior?

Which are the steps to reproduce?

What is the expected or desired behavior?

@metas-ts metas-ts added the type:bug label Nov 11, 2019
metas-ts added a commit that referenced this issue Nov 11, 2019
* AbstractTrxManager: store threadLocalTrx in a *normal* ThreadLocal; not in `InheritableThreadLocal`, because to inherit this stuff from elsewhere is exactly what we do *not* want
metas-ts added a commit that referenced this issue Nov 18, 2019
  * [#5430](#5430) report server: autodetect and use workspace jasperreports folders
  * [#5637](#5637) Add DPD Shipper and DPD integration
  * [#5755](#5755) Create endpoint to directly insert invoice candidates
  * [#5774](#5774) Invoice candidates sometimes remain "ToUpdate" after the invoice was created
  * [#5776](#5776) Distribution Network from Main-Warehouse to Picking Warehouse
  * [#5782](#5782) Endpoint: Close Invoice Candidates
  * [#5784](#5784) Adjust LU Label
  * [#5789](#5789) Don't log migration scripts for AD_Attachment tables
  * [#5778](#5778) Fix potential threadLocalTrxName leakage
  * [#5787](#5787) BPartner API error if CreatedBy or UpdatedBy == -1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
1 participant
You can’t perform that action at this time.