[Feature Request]: How to handle reconnection after disconnection in a subscription?
- Dominant language
- Java
- Stars
- 1.7k
- Forks
- 504
- Avg merge
- 10h 55m
- Merged PRs (30d)
- 43
Description
### What would you like to happen?
hello,
How to handle reconnection after disconnection in a subscription? I couldn’t find any relevant examples on your official website.
```
connection.addDisconnectListener(event -> {
// Handling logic when the connection is lost
System.out.println("Connection lost. Reconnecting...");
// Perform reconnection operations here, such as reconnecting or restarting the subscription process
});
```
### Programming Languages
- [X] plc4j
- [ ] plc4go
- [ ] plc4c
- [ ] plc4net
### Protocols
- [ ] AB-Ethernet
- [ ] ADS /AMS
- [ ] BACnet/IP
- [ ] CANopen
- [ ] DeltaV
- [ ] DF1
- [ ] EtherNet/IP
- [ ] Firmata
- [ ] KNXnet/IP
- [ ] Modbus
- [X] OPC-UA
- [ ] S7
Contributor guide
Research direction
Start with the plc4j OPC-UA subscription API and the connection.addDisconnectListener entry point shown in the issue. Review the existing official examples and determine the expected reconnection behavior after disconnection. Done means the supported handling is clearly defined and an appropriate example or implementation is provided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100