Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test case indicates that relp connection is opened twice but closed only once #39

Closed
kortemik opened this issue Nov 26, 2024 · 1 comment · Fixed by #42
Closed

test case indicates that relp connection is opened twice but closed only once #39

kortemik opened this issue Nov 26, 2024 · 1 comment · Fixed by #42

Comments

@kortemik
Copy link
Member

Description
from #38 (comment)

tcpdump indicates that relp connection is opened twice:

1 open 53 
relp_version=0
relp_software=RLP-01
commands=syslog

1 rsp 86 200 OK
relp_version=0
relp_software=rlp_03,9.0.0,https://teragrep.com
commands=syslog

1 open 53 
relp_version=0
relp_software=RLP-01
commands=syslog

1 rsp 86 200 OK
relp_version=0
relp_software=rlp_03,9.0.0,https://teragrep.com
commands=syslog

2 syslog 75 <12>1 2024-11-26T10:00:12.366Z localhost appName - - - DEBUG logger - none

2 rsp 6 200 OK

3 close 0

3 rsp 0 
0 serverclose 0 
@kortemik kortemik mentioned this issue Nov 26, 2024
@kortemik
Copy link
Member Author

this is a bug in the reconnectIfNoMessagesInterval handling. this triggers on the first run:
https://github.com/teragrep/jla_01/blob/master/src/main/java/com/teragrep/jla_01/RlpLogbackAppender.java#L300-L306

@kortemik kortemik linked a pull request Nov 29, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant