Description of problem:
If the message is sent to the qpidd broker with time-to-live property set to some value over AMQP1.0 protocol, this value is ignored and the message stays on the broker forever (more precisely, until it is consumed).
Sending a message to the broker over the old (AMQP-0.10) protocol:

[root@lzhaldyb-rhel64x ~]# qpid-send --ttl 100000 -a test 
[root@lzhaldyb-rhel64x ~]# qpid-receive -a "test; {mode:browse}" --print-headers yes
TTL: 90969
Redelivered: true
Properties: {sn:1, ts:1379578988398828486, x-amqp-0-10.routing-key:test}


[root@lzhaldyb-rhel64x ~]# qpid-receive -a "test; {mode:browse}" --print-headers yes
TTL: 89362
Redelivered: true
Properties: {sn:1, ts:1379578988398828486, x-amqp-0-10.routing-key:test}


[root@lzhaldyb-rhel64x ~]# qpid-receive -a "test; {mode:browse}" --print-headers yes
TTL: 87634
Redelivered: true
Properties: {sn:1, ts:1379578988398828486, x-amqp-0-10.routing-key:test}

So, the message on the broker contains a header named TTL, the value of which decreases over time. If the new (AMQP1.0) protocol version is used:

[root@lzhaldyb-rhel64x ~]# qpid-send --ttl 10000 -a test --connection-options "{ protocol : 'amqp1.0' }"
[root@lzhaldyb-rhel64x ~]# qpid-receive -a "test; {mode:browse}" --print-headers yes
Redelivered: true
Properties: {sn:1, ts:1379579127626723791}


[root@lzhaldyb-rhel64x ~]# qpid-receive -a "test; {mode:browse}" --print-headers yes
Redelivered: true
Properties: {sn:1, ts:1379579127626723791}


[root@lzhaldyb-rhel64x ~]# sleep 20
[root@lzhaldyb-rhel64x ~]# qpid-receive -a "test; {mode:browse}" --print-headers yes
Redelivered: true
Properties: {sn:1, ts:1379579127626723791}

results in no such header and the message not expiring on the broker.

Version-Release number of selected component (if applicable):
qpid-cpp-*-0.22-14.el6

How reproducible:
100%

Steps to Reproduce:
1. Send a message to the broker with time-to-live property set to some value over AMQP 1.0 protocol.
2. Browse the message on the broker and check its headers.
3.

Actual results:
There is no TTL header and the message does not expire.

Expected results:
The message has TTL header, the value of which decreases over time. The message expires (cannot be consumed) when this value reaches 0.

Additional info: