메시지 순서는 보장되지 않으며 사양에 따라 필수 사항이 아니며 Total JMS Message ordering에 이유에 대한 설명이 나와 있습니다. 스택 오버 플로우 게시 How to handle order of messages in JMS?도 참조하십시오. 또한
Although clients loosely view the messages they produce within a session
as forming a serial stream of sent messages, the total ordering of this stream
is not significant. The only ordering that is visible to receiving clients is
the order of messages a session sends to a particular destination.
Several things can affect this order like message priority,
persistent/non persistent etc.
그래서 귀하의 질문에 메시지를 대답
들이 위의 정보와 함께 전송 된 동일한 순서로 수신 될 JMS2 사양
JMS defines that messages sent by a session to a destination must be received
in the order in which they were sent. This defines a partial ordering
constraint on a session’s input message stream.
JMS does not define order of message receipt across destinations or across
a destination’s messages sent from multiple sessions. This aspect of a
session’s input message stream order is timing-dependent. It is not under
application control.
당으로