[jira] [Work logged] (CAMEL-11947) Race condition in iec60870 producer
[ https://issues.apache.org/jira/browse/CAMEL-11947?focusedWorklogId=383384&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-383384 ] ASF GitHub Bot logged work on CAMEL-11947: -- Author: ASF GitHub Bot Created on: 07/Feb/20 04:13 Start Date: 07/Feb/20 04:13 Worklog Time Spent: 10m Work Description: davsclaus commented on pull request #3547: [CAMEL-11947] Race condition in iec60870 producer URL: https://github.com/apache/camel/pull/3547 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 383384) Time Spent: 1h (was: 50m) > Race condition in iec60870 producer > --- > > Key: CAMEL-11947 > URL: https://issues.apache.org/jira/browse/CAMEL-11947 > Project: Camel > Issue Type: Bug > Components: camel-iec60870 >Affects Versions: 2.20.0 >Reporter: James Netherton >Assignee: Thomas Diesler >Priority: Minor > Fix For: 3.1.0 > > Time Spent: 1h > Remaining Estimate: 0h > > I've been working on integrating the iec60870 component with WIldFly. I have > an integration test > [here|https://github.com/wildfly-extras/wildfly-camel/blob/master/itests/standalone/basic/src/test/java/org/wildfly/camel/test/iec60870/Iec60870IntegrationTest.java]. > When it's executed on its own, everything works fine. When it runs with the > entire test suite, I encounter a NullPointerException in the Neoscada > [Client.writeCommand()|https://github.com/eclipse/neoscada/blob/master/protocols/org.eclipse.neoscada.protocol.iec60870.client/src/org/eclipse/neoscada/protocol/iec60870/client/Client.java#L259] > method. > It seems that the Netty channel that it's trying to write to is null and that > initialisation of the channel happens async in > [Client.handleOperationComplete()|https://github.com/eclipse/neoscada/blob/master/protocols/org.eclipse.neoscada.protocol.iec60870.client/src/org/eclipse/neoscada/protocol/iec60870/client/Client.java#L138]. > When I debug, I see the channel gets initialised after the call to > writeCommand(). > Not sure if there's any way to detect whether the client connection has been > established before trying to use it in the > [ClientProducer|https://github.com/apache/camel/blob/master/components/camel-iec60870/src/main/java/org/apache/camel/component/iec60870/client/ClientProducer.java#L49]. > Or maybe this ticket would be better placed with the neoscada project? > > CrossRef > [https://github.com/wildfly-extras/wildfly-camel/issues/2236] > [https://issues.redhat.com/browse/ENTESB-12557] > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-11947) Race condition in iec60870 producer
[ https://issues.apache.org/jira/browse/CAMEL-11947?focusedWorklogId=382202&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-382202 ] ASF GitHub Bot logged work on CAMEL-11947: -- Author: ASF GitHub Bot Created on: 05/Feb/20 11:27 Start Date: 05/Feb/20 11:27 Worklog Time Spent: 10m Work Description: tdiesler commented on pull request #3547: [CAMEL-11947] Race condition in iec60870 producer URL: https://github.com/apache/camel/pull/3547 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 382202) Time Spent: 50m (was: 40m) > Race condition in iec60870 producer > --- > > Key: CAMEL-11947 > URL: https://issues.apache.org/jira/browse/CAMEL-11947 > Project: Camel > Issue Type: Bug > Components: camel-iec60870 >Affects Versions: 2.20.0 >Reporter: James Netherton >Assignee: Thomas Diesler >Priority: Minor > Fix For: 3.1.0 > > Time Spent: 50m > Remaining Estimate: 0h > > I've been working on integrating the iec60870 component with WIldFly. I have > an integration test > [here|https://github.com/wildfly-extras/wildfly-camel/blob/master/itests/standalone/basic/src/test/java/org/wildfly/camel/test/iec60870/Iec60870IntegrationTest.java]. > When it's executed on its own, everything works fine. When it runs with the > entire test suite, I encounter a NullPointerException in the Neoscada > [Client.writeCommand()|https://github.com/eclipse/neoscada/blob/master/protocols/org.eclipse.neoscada.protocol.iec60870.client/src/org/eclipse/neoscada/protocol/iec60870/client/Client.java#L259] > method. > It seems that the Netty channel that it's trying to write to is null and that > initialisation of the channel happens async in > [Client.handleOperationComplete()|https://github.com/eclipse/neoscada/blob/master/protocols/org.eclipse.neoscada.protocol.iec60870.client/src/org/eclipse/neoscada/protocol/iec60870/client/Client.java#L138]. > When I debug, I see the channel gets initialised after the call to > writeCommand(). > Not sure if there's any way to detect whether the client connection has been > established before trying to use it in the > [ClientProducer|https://github.com/apache/camel/blob/master/components/camel-iec60870/src/main/java/org/apache/camel/component/iec60870/client/ClientProducer.java#L49]. > Or maybe this ticket would be better placed with the neoscada project? > > CrossRef > [https://github.com/wildfly-extras/wildfly-camel/issues/2236] > [https://issues.redhat.com/browse/ENTESB-12557] > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-11947) Race condition in iec60870 producer
[ https://issues.apache.org/jira/browse/CAMEL-11947?focusedWorklogId=374944&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-374944 ] ASF GitHub Bot logged work on CAMEL-11947: -- Author: ASF GitHub Bot Created on: 21/Jan/20 12:31 Start Date: 21/Jan/20 12:31 Worklog Time Spent: 10m Work Description: davsclaus commented on pull request #3502: [CAMEL-11947] Possible race condition in iec60870 producer URL: https://github.com/apache/camel/pull/3502 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 374944) Time Spent: 0.5h (was: 20m) > Race condition in iec60870 producer > --- > > Key: CAMEL-11947 > URL: https://issues.apache.org/jira/browse/CAMEL-11947 > Project: Camel > Issue Type: Bug > Components: camel-iec60870 >Affects Versions: 2.20.0 >Reporter: James Netherton >Assignee: Thomas Diesler >Priority: Minor > Time Spent: 0.5h > Remaining Estimate: 0h > > I've been working on integrating the iec60870 component with WIldFly. I have > an integration test > [here|https://github.com/wildfly-extras/wildfly-camel/blob/master/itests/standalone/basic/src/test/java/org/wildfly/camel/test/iec60870/Iec60870IntegrationTest.java]. > When it's executed on its own, everything works fine. When it runs with the > entire test suite, I encounter a NullPointerException in the Neoscada > [Client.writeCommand()|https://github.com/eclipse/neoscada/blob/master/protocols/org.eclipse.neoscada.protocol.iec60870.client/src/org/eclipse/neoscada/protocol/iec60870/client/Client.java#L259] > method. > It seems that the Netty channel that it's trying to write to is null and that > initialisation of the channel happens async in > [Client.handleOperationComplete()|https://github.com/eclipse/neoscada/blob/master/protocols/org.eclipse.neoscada.protocol.iec60870.client/src/org/eclipse/neoscada/protocol/iec60870/client/Client.java#L138]. > When I debug, I see the channel gets initialised after the call to > writeCommand(). > Not sure if there's any way to detect whether the client connection has been > established before trying to use it in the > [ClientProducer|https://github.com/apache/camel/blob/master/components/camel-iec60870/src/main/java/org/apache/camel/component/iec60870/client/ClientProducer.java#L49]. > Or maybe this ticket would be better placed with the neoscada project? > > CrossRef > [https://github.com/wildfly-extras/wildfly-camel/issues/2236] > [https://issues.redhat.com/browse/ENTESB-12557] > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-11947) Race condition in iec60870 producer
[ https://issues.apache.org/jira/browse/CAMEL-11947?focusedWorklogId=374945&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-374945 ] ASF GitHub Bot logged work on CAMEL-11947: -- Author: ASF GitHub Bot Created on: 21/Jan/20 12:31 Start Date: 21/Jan/20 12:31 Worklog Time Spent: 10m Work Description: davsclaus commented on pull request #3503: [CAMEL-11947] Possible race condition in iec60870 producer URL: https://github.com/apache/camel/pull/3503 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 374945) Time Spent: 40m (was: 0.5h) > Race condition in iec60870 producer > --- > > Key: CAMEL-11947 > URL: https://issues.apache.org/jira/browse/CAMEL-11947 > Project: Camel > Issue Type: Bug > Components: camel-iec60870 >Affects Versions: 2.20.0 >Reporter: James Netherton >Assignee: Thomas Diesler >Priority: Minor > Time Spent: 40m > Remaining Estimate: 0h > > I've been working on integrating the iec60870 component with WIldFly. I have > an integration test > [here|https://github.com/wildfly-extras/wildfly-camel/blob/master/itests/standalone/basic/src/test/java/org/wildfly/camel/test/iec60870/Iec60870IntegrationTest.java]. > When it's executed on its own, everything works fine. When it runs with the > entire test suite, I encounter a NullPointerException in the Neoscada > [Client.writeCommand()|https://github.com/eclipse/neoscada/blob/master/protocols/org.eclipse.neoscada.protocol.iec60870.client/src/org/eclipse/neoscada/protocol/iec60870/client/Client.java#L259] > method. > It seems that the Netty channel that it's trying to write to is null and that > initialisation of the channel happens async in > [Client.handleOperationComplete()|https://github.com/eclipse/neoscada/blob/master/protocols/org.eclipse.neoscada.protocol.iec60870.client/src/org/eclipse/neoscada/protocol/iec60870/client/Client.java#L138]. > When I debug, I see the channel gets initialised after the call to > writeCommand(). > Not sure if there's any way to detect whether the client connection has been > established before trying to use it in the > [ClientProducer|https://github.com/apache/camel/blob/master/components/camel-iec60870/src/main/java/org/apache/camel/component/iec60870/client/ClientProducer.java#L49]. > Or maybe this ticket would be better placed with the neoscada project? > > CrossRef > [https://github.com/wildfly-extras/wildfly-camel/issues/2236] > [https://issues.redhat.com/browse/ENTESB-12557] > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
