Currently RmiTransportWriter opens a connection to the RmiJournalReceiver at startup, and keeps the connection open until shutdown. This means that the receiver must not be shut down, and the network transport must not be interrupted, even if the leading Fedora instance is quiescent.
New behavior would be:
1) RmiTransportWriter opens the connection to RmiJournalReceiver at startup, to test the connection, and then immediately closes the connection.
2) At the beginning of each Journal file, a new connection is established.
3) At the end of each Journal file, the connection is closed.
This would allow system maintenance in quiescent times. It would also allow a non-crucial RMI transport to resume operation after losing one or more files, without restarting the leading Fedora.
Log in to post a comment.