I’m getting similar yet subtly different startup messages:
2016-06-16 22:40:49.301 [DEBUG] [.o.b.tcp.internal.TCPActivator:35 ]- TCP/UDP binding has been started.
2016-06-16 22:40:50.201 [INFO ] [t.AbstractSocketChannelBinding:768 ]- The maximum buffer will be set to the default value of 1024
2016-06-16 22:40:50.205 [INFO ] [t.AbstractSocketChannelBinding:775 ]- The interval to retry connection setups will be set to the default value of 5
2016-06-16 22:40:50.206 [INFO ] [t.AbstractSocketChannelBinding:782 ]- The cron job to reset connections will be set to the default value of 0 0 0 * * ?
2016-06-16 22:40:50.207 [INFO ] [t.AbstractSocketChannelBinding:789 ]- The setting to queue write operation until a channel gets connected will be set to the default value of true
2016-06-16 22:40:50.209 [INFO ] [t.AbstractSocketChannelBinding:796 ]- The port to listen for incoming connections will be set to the default value of 0
2016-06-16 22:40:50.210 [INFO ] [t.AbstractSocketChannelBinding:803 ]- The setting to share channels within an Item will be set to the default value of true
2016-06-16 22:40:50.211 [INFO ] [t.AbstractSocketChannelBinding:810 ]- The setting to share channels between the items with the same direction will be set to the default value of t
rue
2016-06-16 22:40:50.212 [INFO ] [t.AbstractSocketChannelBinding:817 ]- The setting to share channels between directions will be set to the default value of true
2016-06-16 22:40:50.214 [INFO ] [t.AbstractSocketChannelBinding:824 ]- The setting to use address masks for incoming connections will be set to the default value of true
2016-06-16 22:40:50.230 [INFO ] [t.protocol.internal.TCPBinding:173 ]- The maximum time out for blocking write operations will be set to the default vaulue of 3000
2016-06-16 22:40:50.232 [INFO ] [t.protocol.internal.TCPBinding:180 ]- The blocking nature of read/write operations will be set to the default vaulue of false
2016-06-16 22:40:50.233 [INFO ] [t.protocol.internal.TCPBinding:187 ]- The preamble for all write operations will be set to the default vaulue of ""
2016-06-16 22:40:50.234 [INFO ] [t.protocol.internal.TCPBinding:194 ]- The postamble for all write operations will be set to the default vaulue of ""
2016-06-16 22:40:50.236 [INFO ] [t.protocol.internal.TCPBinding:201 ]- Updating states with returned values will be set to the default vaulue of true
2016-06-16 22:41:35.751 [ERROR] [AbstractDatagramChannelBinding:943 ]- there is no channel that services [itemName=MYTHTV, command=testing]
Hrmmm… the reported object names are different between our bindings! (“AbstractDatagramChannelBinding” vs “t.AbstractSocketChannelBinding:768”!)
Here’s the entire option list for tcp-udp from my openhab.cfg:
################################# TCP - UDP Binding ###################################
#
# all parameters can be applied to both the TCP and UDP binding unless
# specified otherwise
# Port to listen for incoming connections
#tcp:port=25001
# Cron-like string to reconnect remote ends, e.g for unstable connection or remote ends
#tcp:reconnectcron=0 0 0 * * ?
# Interval between reconnection attempts when recovering from a communication error,
# in seconds
#tcp:retryinterval=5
# Queue data whilst recovering from a connection problem (TCP only)
#tcp:queue=true
# Maximum buffer size whilst reading incoming data
#tcp:buffersize=1024
# Share connections within the Item binding configurations
#tcp:itemsharedconnections=true
# Share connections between Item binding configurations
#tcp:bindingsharedconnections=true
# Share connections between inbound and outbound connections
#tcp:directionssharedconnections=false
# Allow masks in ip:port addressing, e.g. 192.168.0.1:* etc
#tcp:addressmask=true
# Pre-amble that will be put in front of data being sent
#tcp:preamble=
# Post-amble that will be appended to data being sent
#tcp:postamble=\r\n
# Perform all write/read (send/receive) operations in a blocking mode, e.g. the binding
# will wait for a reply from the remote end after data has been sent
#tcp:blocking=false
# timeout, in milliseconds, to wait for a reply when initiating a blocking write/read
# operation
#tcp:timeout=3000
# Update the status of Items using the response received from the remote end (if the
# remote end sends replies to commands)
#tcp:updatewithresponse=true
# Timeout - or 'refresh interval', in milliseconds, of the worker thread
tcp:refreshinterval=250
# Timeout, in milliseconds, to wait when "Selecting" IO channels ready for communication
#tcp:selecttimeout=1000
# Used character set
tcp:charset=ASCII
udp:charset=ASCII
I have one (apparently default) options in the log that have no mention in your list:
The setting to queue write operation until a channel gets connected will be set to the default value of true
And you have one (looks like a critical one!) that is not mentioned in my list:
UDP Refresh Service has been started
This seems to leave two possibilities… either something in your config is really different than mine, or somehow you have a really different (grumble!workinggrumble!) version of the tcp binding than what shipped with 1.8.1 and also 1.9.x that’s available on cloudbees.
…so what’s the entirety of your tcp/udp config look like in openhab.cfg? 
(Don’t misread my frustration as frustration at you – very happy you’re doing a deep dive trying to help! Just generally frustrated. Thanks in advance!)
Both
)
Seriously, there’s apparently something different between our environments. I didn’t change anything else.