we are using vcl library to send/receive, if the application aborts or kill
signal is sent to the application, vcl sessions are still in listening mode
even after the thread containing the vcl sessions is closed.
we have a process monitor which monitors our application running/not and
immediately reloads the application
while booting up consecutive time, because the previous session same(IP+port)
will not be closed while trying to open up new session again
I am getting error as connection refused
below is the list of calls made
vppcom_app_create - in main thread
In receiver thread
vppcom_worker_register -> vppcom_session_create ->
vppcom_session_attr(VPPCOM_ATTR_SET_CONNECTED) -> vppcom_session_bind ->
vppcom_session_listen
while exiting thread calling vppcom_session_close -> vppcom_worker_unregister
getting error while calling vppcom_session_listen
vnet[12346]: session_mq_listen_handler:66: listen returned: -16
general protection fault ip:7f351eb202d8 sp:7f33b9ffae20 error:0 in
libvppcom.so.20.05[7f351eb03000+2f000]
general protection fault ip:7f351eb202d8 sp:7f33b97f9e20 error:0
session listen failed errno=-111
Kindly let me know if there's some other configuration that I could use.
vcl.conf
vcl {
rx-fifo-size 4000000
tx-fifo-size 4000000
app-scope-local
app-scope-global
api-socket-name /tmp/vpp-api.sock
app-timeout 2
session-timeout 2
}
regards
Tahir
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17622): https://lists.fd.io/g/vpp-dev/message/17622
Mute This Topic: https://lists.fd.io/mt/77224682/21656
Mute #vppcom:https://lists.fd.io/g/vpp-dev/mutehashtag/vppcom
Mute #vpp-hoststack:https://lists.fd.io/g/vpp-dev/mutehashtag/vpp-hoststack
Group Owner: [email protected]
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
