[jira] [Updated] (PLC4X-344) spi.transaction.RequestTransactionManager is not thread safe

["Łukasz Dywicki (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/PLC4X-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Łukasz Dywicki updated PLC4X-344:
---------------------------------
    Affects Version/s: 0.9.1
                       0.10.0
                       0.9.0
                       0.8.0

> 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
>    Affects Versions: 0.8.0, 0.9.0, 0.10.0, 0.9.1
>         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)