-
Notifications
You must be signed in to change notification settings - Fork 383
Description
Describe the bug
A clear and concise description of what the bug is.
com.serotonin.modbus4j.exception.ModbusTransportException: java.net.SocketException: Connection reset by peer: socket write error
at com.serotonin.modbus4j.ip.tcp.TcpMaster.sendImpl(TcpMaster.java:172)
at com.serotonin.modbus4j.ModbusMaster.send(ModbusMaster.java:105)
at com.serotonin.modbus4j.ModbusMaster.sendFunctionGroup(ModbusMaster.java:362)
at com.serotonin.modbus4j.ModbusMaster.send(ModbusMaster.java:305)
at com.sanzhisoft.mybatis.monitor.utils.Modbus4jUtils.batchRead(Modbus4jUtils.java:190)
at com.sanzhisoft.mybatis.monitor.utils.Modbus4jUtils.main(Modbus4jUtils.java:203)
Caused by: java.net.SocketException: Connection reset by peer: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:111)
at java.net.SocketOutputStream.write(SocketOutputStream.java:143)
at com.serotonin.modbus4j.sero.messaging.StreamTransport.write(StreamTransport.java:53)
at com.serotonin.modbus4j.sero.messaging.MessageControl.write(MessageControl.java:213)
at com.serotonin.modbus4j.sero.messaging.MessageControl.send(MessageControl.java:124)
at com.serotonin.modbus4j.sero.messaging.MessageControl.send(MessageControl.java:105)
at com.serotonin.modbus4j.ip.tcp.TcpMaster.sendImpl(TcpMaster.java:133)
... 5 more
To Reproduce
Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Mango Version (please complete the following information):
- Core Version: [e.g. 3.5.6]
- Module Version [e.g. 3.5.10]
Browser (please complete the following information):
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Name [e.g. chrome, safari]
- Version [e.g. 22]
Additional context
Add any other context about the problem here.
ma.log Snippet
- Check your ma.log file (located in ${MA_HOME}/logs) for any errors or warnings
- Do NOT post the entire file, just the relevant lines
Browser console errors
- If the issue is with the web interface then check the development console
Minimal code example to reproduce
- If possible please provide a minimal code example, this will expedite the process of identifying and fixing the problem.