You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@plc4x.apache.org by "Robin (Jira)" <ji...@apache.org> on 2022/09/27 06:05:00 UTC

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

    [ https://issues.apache.org/jira/browse/PLC4X-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17609829#comment-17609829 ] 

Robin commented on PLC4X-344:
-----------------------------

It doesn't seem like that it is in the latest version as far as I can see.

> 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
>            Priority: Major
>         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)