To use persistent messaging add the following STOMP header to all SEND requests: persistent:true. STOMP messages are non-persistent by default. If in Stomp world you use /queue/foo/bar then in a JMS world the queue would be called foo/bar not /foo/bar. Whilst FOO.BAR is the normal syntax to identify a queue type destination the Stomp equivalent is /queue/FOO.BARīe careful about starting destinations with / Also note that the default separator in MOM systems is. Note that the prefix in stomp /queue/ or /topic/ is removed from the string before passing it to ActiveMQ as a JMS destination. The JIRA that implemented this: ActiveMQ 5.x does not support the notion of a grace-period for heart beats as supported by the STOMP protocol Please check the STOMP specification for the details on heart-beating STOMP clients that wish to be tolerant of late arriving heart-beats from the broker must implement their own solution for doing so. Attempts to configure the grace period multiplier to a value less than, or equal to 1.0 will be silently ignored. This resulted in the broker concluding that the client was no longer present causing it to close its side of the client’s connection when the client failed to honor it’s configured heart-beat settings.įrom ActiveMQ 5.9.0: the timeout enforcement for read heart-beats is now configurable via a new transport option transport.hbGracePeriodMultiplier:įor backward compatibility, if the grace period multiplier is not configured the default enforcement mode remains strict, e.g., transport.hbGracePeriodMultiplier=1.0. In other words, the broker was intolerant of late arriving read heart-beats from the client.
ActiveMQ supports STOMP heart beating provided the client is using version 1.1 (or greater) of the protocol.īefore ActiveMQ 5.9.0: enforcement of the ‘read’ heart-beat timeout (that is, a heart-beat sent from the client to the broker) was strict. The STOMP protocol (version 1.1 or greater) defines the concept of heart beats as a method by which a client and broker can determine the health of the underlying TCP connection between them. An example of using Stomp over SSL on the client side can be found in the PHP Stomp client example. To use NIO change the URI scheme of the transport connector to stomp+nio.įor more details on using SSL with ActiveMQ see the following article ( How do I use SSL). This can help when support for a large number of queues is required. The NIO transport will use far fewer threads than the corresponding TCP connector. Enabling Stomp over NIOįrom ActiveMQ 5.3: for better scalability and performance the Stomp protocol can be configured to be run over the NIO transport. This applies to all errors that can occur broker-side.įor additional security, you can use Stomp over SSL as described in the following section. In other case, operations will be discarded but the client will not be informed of errors.
If you use synchronous operations (by using receipts), you can expect an ERROR frame in case of unauthorized access attempt. Also, the authorization policies will be applied when you try to access (read/write) certain destinations. This means that the CONNECT command will return an ERROR STOMP frame on unsuccessful authentication. Securityįrom ActiveMQ 5.1: Stomp fully supports ActiveMQ’s security mechanism. Options missing this prefix will be ignored.
to take effect, e.g., wireFormat.`maxDataLength`=100000.
Wire format options must have the prefix wireFormat.
0 kommentar(er)
