Description of problem:
Summary says it all. If I install mingw32-matahari, install it's iso image on a windows box, configure the broker IP in the registry, and restart the agents, they fail to show up as connected to the broker whether using python or qmf-tool.
I ran a tcpdump session and can see the packets coming across the wire but for what ever reason, it is not connecting (AND doesn't appear to attempt any reconnects).
I tried enabling debug messaging on the windows side but could get it to work.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install/start matahari-broker
2. install mingw32-matahari
3. grab iso from mingw32-matahari
4. copy/install iso on windows box
5. configure broker ip through registry key
6. restart agents
7. on broker, 'qmf-tool localhost:49000'
8. list agents, nothing connected
I have access to windows vm's if you need them...
I was able to enable debug logging using v0.4.0-5 by adding the 'verbose' registry string value. Attempting to run the agents in debug from the windows command line using v0.4.2-9 they all crash with the following error details.
Problem Event Name: APPCRASH
Application Name: matahari-qmf-hostd.exe
Application Version: 0.0.0.0
Application Timestamp: 4e554264
Fault Module Name: libqpidtypes.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4d91ea90
Exception Code: 40000015
Exception Offset: 00022f8f
OS Version: 6.1.7600.2.0.0.272.7
Locale ID: 1033
Additional Information 1: 979f
Additional Information 2: 979fce893fa19c859a9d93203f719072
Additional Information 3: 03d1
Additional Information 4: 03d11bf9ca35c5cee60c0340d35c1c9f
This problem occurs because returning NULL from mh_uuid() is not an acceptable type within qpid.
There is no Windows variant for gathering/creating UUID a patch is in process which the thread can be found :
good 2 go in v0.4.4-2
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
No description required.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.