Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stomp bridge does not support heartbeats #361

Open
glassfishrobot opened this issue Feb 10, 2015 · 6 comments
Open

Stomp bridge does not support heartbeats #361

glassfishrobot opened this issue Feb 10, 2015 · 6 comments

Comments

@glassfishrobot
Copy link

Heartbeats do not appear to be support by the stomp bridge. Attempts to connect with not zero heartbeat values will always have 0,0 returned in the heartbeat header of the connected message.

Example output from telnet is below:

CONNECT
host:localhost
login:admin
passcode:admin
accept-version:1.2
heart-beat:1000,1000

^@
CONNECTED
session:7063978975437788160[null]
version:1.2
heart-beat:0,0
server:Open Message Queue / Oracle GlassFish(tm) Server Message Queue

Affected Versions

[5.1.1]

@glassfishrobot
Copy link
Author

@glassfishrobot Commented
Reported by smithsos

@glassfishrobot
Copy link
Author

@glassfishrobot Commented
@amykang2020 said:
The heart-beat header is optional in STOMP 2.0 specificaiton, and OpenMQ STOMP service currently doesn't support heart-beat.

@glassfishrobot
Copy link
Author

@glassfishrobot Commented
smithsos said:
Thanks, I was unable to find any documentation as to whether this was supported or not. Is it planned to add support for this in any near term releases or is it low priority?

@glassfishrobot
Copy link
Author

@glassfishrobot Commented
@amykang2020 said:
Support for heart-beat header will be added in a future release.

@glassfishrobot
Copy link
Author

@glassfishrobot Commented
This issue was imported from java.net JIRA MQ-361

@glassfishrobot
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant