#13 Incorrect handling of path elements in dropped connections.
From Rainer,
When a BEEP connection is dropped and then can be re-
established, SDSC
does not send a <path> element, however, it still refers to
<path>
elements (via pathid).
Here is a dump of such a session:
####################
testsrvr test server - just a quick debuging aid and
sample....
Compiled with liblogging version 0.6.0.
See http://www.monitorware.com/liblogging/ for updates.
Listening for incoming requests....
KeySZ: 'entry', ValueSZ '[26635]: BEEP Connection to
172.19.1.20
Dropped'
HAS XML Properties:
KeySZ: 'facility', ValueSZ '5'
KeySZ: 'severity', ValueSZ '5'
KeySZ: 'tag', ValueSZ 'syslog-c'
KeySZ: 'hostname', ValueSZ 'localhost.localdomain'
KeySZ: 'timestamp', ValueSZ '2003-09-15T10:43:38+02:00'
Msg from 172.19.1.26, host (non-wellformed msg), facility
1, priority 5:
[26635]: BEEP Connection to 172.19.1.20 Dropped
RAW:[26635]: BEEP Connection to 172.19.1.20 Dropped
- KeySZ: 'path', ValueSZ '(null)'
- HAS XML Properties:
- KeySZ: 'pathID', ValueSZ '1'
- KeySZ: 'fromFQDN', ValueSZ 'localhost.localdomain'
- KeySZ: 'fromIP', ValueSZ '127.0.0.1'
- KeySZ: 'toFQDN', ValueSZ '172.19.1.20'
- KeySZ: 'toIP', ValueSZ '172.19.1.20'
- KeySZ: 'linkprops', ValueSZ ''
- HAS Child:
- Path, Msg: <path pathID='1'
- fromFQDN='localhost.localdomain'
- fromIP='127.0.0.1' toFQDN='172.19.1.20' toIP='172.19.1.20'
- linkprops=''></path>
- KeySZ: 'entry', ValueSZ ': test 3'
- HAS XML Properties:
- KeySZ: 'facility', ValueSZ '1'
- KeySZ: 'severity', ValueSZ '5'
- KeySZ: 'tag', ValueSZ 'rg'
- KeySZ: 'hostname', ValueSZ 'localhost.localdomain'
- KeySZ: 'timestamp', ValueSZ '2003-09-15T10:43:37+02:00'
- KeySZ: 'deviceFQDN', ValueSZ 'localhost.localdomain'
- Msg from 172.19.1.26, host (non-wellformed msg), facility
- 1, priority 5:
- test 3
RAW:: test 3
Logged In: YES
user_id=31465
This will be a bit more difficult than I initially suspected. The
dropped connection means that the message is half sent already
... so it will have to back up in order to send the path.