NSIS-ka
A free C++ implementation of NSIS protocols

Opened 8 years ago

Last modified 8 years ago

#118 new defect

Catch Exception whenever client is no longer connected to UDS

Reported by: roehricht Owned by: bless
Priority: major Milestone:
Component: QOS-NSLP Version:
Keywords: Cc:

Description

Protlib instance (TPoverUDS) terminates ungracefully if former connection to socket was closed during connection by external client.

2009-06-25 13:14:57.001-28253- DEBUG /4: QoS-NSLP Sock API Received incoming message on Queue
2009-06-25 13:14:57.001-28253- DEBUG /4: QoS-NSLP Sock API Received incoming message from ProcessingModule
2009-06-25 13:14:57.001-28253- EVENT /4: QoS-NSLP Sock API Received a QoS_Appl_Msg to translate and deliver to connected clients
2009-06-25 13:14:57.001-28253- DEBUG /4: QoS-NSLP Sock API generate_netmsg() start
2009-06-25 13:14:57.001-28253- DEBUG /4: QoS-NSLP Sock API length netmsg allocation: 141
2009-06-25 13:14:57.001-28253- EVENT /4: TPoverUDS       Starting new sender thread...
2009-06-25 13:14:57.001-28253- EVENT /4: TPoverUDS       senderthread - starting as thread <2853174160>
2009-06-25 13:14:57.001-28253- DEBUG /4: TimerModule     Stopped timer 3, mid 6 for QNSLP-TimerProc
2009-06-25 13:14:57.001-28253- DEBUG /8: TPoverUDS       No existing connection to [Socketnumber]: 10 found, creating a new one.
2009-06-25 13:14:57.001-28253**ERROR**4: TPoverUDS       Connect to failed: [Connection refused]
terminate called after throwing an instance of 'protlib::TPErrorConnectSetupFail'
  what():  Connection Setup Failure

Change History (1)

comment:1 Changed 8 years ago by roehricht

Can be easily reproduced: Start QoS NSLP on machine A and send a QoS NSLP RESERVE via sudo ./client <IP-of-A> <IP-of-B> towards machine B without starting any QoS NSLP instance on machine B. After the client is shutdown upon a timeout the QoS NSLP instance on A will be terminated ungracefully.

Note: See TracTickets for help on using tickets.