[
https://issues.apache.org/jira/browse/PLC4X-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17620075#comment-17620075
]
Christofer Dutz commented on PLC4X-344:
---------------------------------------
Oh ... unfortunately it took you quite a while to reply to my question ... so I
stopped following this issue. I just applied the patch (No it wasn't applied
yet). It does look legit and currently running the testsuite with it. Will it
with a few of my PLCs and if that works I'll commit the changes.
Unfortuanteley, we just released 0.10.0 so it will probably take a few months
till the next release.
> 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)
