DNP3 slave endpoints not coming back up after restart
10 views
Skip to first unread message
Adam Todorski
unread,
Jun 29, 2012, 6:19:56 PM6/29/12
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to reef-...@googlegroups.com
Fellow reef-ers:
I'm having an issue with .48 where dnp3-slave endpoints do not come up after restarting reef. The symptom is that the node simply does not start listening for connections on the specified port, there is nothing obvious in the karaf log or STDOUT. I can clear the issue by issuing a load command on the (unchanged) config; I cannot clear the issue by resetting the processing application ("application:remove node01-Processing"). Endpoints using a different protocol that is not bundled with Reef seem to come back fine. Is this a known issue in .48? Are there any other known issues in .48?
I have not tried this in a multi-node configuration.
Here are the communication portions of my config: ... <cm:protocol name="dnp3-slave"> <common:configFile fileName="slave.xml" /> </cm:protocol> <cm:interface name="DNPIn" ip="10.0.0.2" port="20000" network="any" serverSocket="true"/> ...