[
https://issues.apache.org/jira/browse/PLC4X-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Łukasz Dywicki resolved PLC4X-344.
----------------------------------
Fix Version/s: 0.11.0
Assignee: Łukasz Dywicki
Resolution: Fixed
Committed limited fix confirmed earlier by Robin:
https://github.com/apache/plc4x/commit/cd5df7e5b43c6725d4e427181c85bb4b4d68699a
> spi.transaction.RequestTransactionManager is not thread safe
> ------------------------------------------------------------
>
> Key: PLC4X-344
> URL: https://issues.apache.org/jira/browse/PLC4X-344
> Project: Apache PLC4X
> Issue Type: Bug
> Components: Driver-S7, PLC4J
> Environment: Siemens IOT 2050, debian. PLC4J via kotlin
> Reporter: Robin
> Assignee: Łukasz Dywicki
> Priority: Major
> Fix For: 0.11.0
>
> Attachments: PLC4X-344.patch, errorConnect.png
>
>
> When running a s7 connection to an PLC sometimes the connection halts and
> this error is thrown in the log. It seems like the processWorklog function
> uses a thread safe queue but is itself not threadsafe throwing this error.
>
> We're using an single connection to the plc. Reading two datablocks. Each
> datablock is read by a different handler running in a separate thread but
> using the same instance of PLC4J.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
