Chapter 3. Using MQTT with IBM WebSphere MQ Telemetry 119
20120322 094145.893 CWNAN0033I Connection attempt to listener 1901 received from client
BridgeDaemon02 on address 9.42.170.179:59802
Example 3-22 shows the output of the running daemon that is connected to the WebSphere
MQ queue manager. When the bridge tries to establish a connection, it checks whether the
connection at the other end is also a WebSphere MQ Telemetry daemon for devices. If not,
the socket error appears. This error does not cause a problem, but it does add the extra line in
the log. This extra line can be avoided by using the tryprivate false parameter in the bridge
configuration. ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month, and much more.
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.
Julian F.
Head of Cybersecurity
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.
Addison B.
Field Engineer
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.
Amir M.
Data Platform Tech Lead
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.