Commit 0fcf4c1
committed
Return 0 JMS timestamp if property is null
The property is not supposed to be null in JMS, but it can in AMQP
0.9.1, so JMS messages consumed from AMQP resources can have a null
value. This commit mitigates the issue by returning a timestamp set to 0
in this case, just like the JMS 1.1 specification suggests it when
MessageProducer#setDisableMessageTimestamp(true) is called.
Fixes #1261 parent 828a930 commit 0fcf4c1
File tree
2 files changed
+15
-2
lines changed- src
- main/java/com/rabbitmq/jms/client
- test/java/com/rabbitmq/integration/tests
2 files changed
+15
-2
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
242 | 242 | | |
243 | 243 | | |
244 | 244 | | |
245 | | - | |
| 245 | + | |
| 246 | + | |
| 247 | + | |
| 248 | + | |
| 249 | + | |
| 250 | + | |
246 | 251 | | |
247 | 252 | | |
248 | 253 | | |
| |||
496 | 501 | | |
497 | 502 | | |
498 | 503 | | |
499 | | - | |
| 504 | + | |
| 505 | + | |
| 506 | + | |
| 507 | + | |
500 | 508 | | |
501 | 509 | | |
502 | 510 | | |
| |||
Lines changed: 5 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | 2 | | |
3 | 3 | | |
| 4 | + | |
4 | 5 | | |
5 | 6 | | |
6 | 7 | | |
| |||
22 | 23 | | |
23 | 24 | | |
24 | 25 | | |
| 26 | + | |
25 | 27 | | |
26 | 28 | | |
27 | 29 | | |
| |||
187 | 189 | | |
188 | 190 | | |
189 | 191 | | |
| 192 | + | |
190 | 193 | | |
191 | 194 | | |
192 | 195 | | |
| |||
238 | 241 | | |
239 | 242 | | |
240 | 243 | | |
| 244 | + | |
241 | 245 | | |
242 | 246 | | |
243 | 247 | | |
| |||
274 | 278 | | |
275 | 279 | | |
276 | 280 | | |
| 281 | + | |
277 | 282 | | |
278 | 283 | | |
279 | 284 | | |
0 commit comments