Hi,
I'm using the python-qpid package to do some messaging. Sometime -
especially after some time of inactivity, the exception LinkClosed is
raised when sending a message:
...
File /usr/lib/python2.7/dist-packages/qpid/messaging/endpoints.py,
line 836, in send
self._ecwait(lambda:
Hi Paul,
when I opened the QPID-3175 the SSL support didn't worked for me even
in combination with PLAIN SASL mechanism. But some sort of SSL
implementation was already present for the code. So it is possible
that I just didn't configured it correctly. Also, I believe the SSL
support in Python
Hi Rajith,
I was playing with the JMS selectors last week. While they do work and
really select the messages based on the filter, it seemed to me that
it switched off the acknowledgments completely. The Java application
was getting only the selected messages, but I was unable to
acknowledge them
Hi Paul,
both errors occur under very similar circumstances. I recommend enabling debug
logs of cluster component by adding:
log-enable=debug+:cluster
log-enable=notice+
to qpidd.conf and post the logs to a new JIRA. (you can try enabling trace logs
that might provide more verbose output but
Hello, I have extended the Jakub's patch for file based certificate client
authentication.
It is attached to the same https://issues.apache.org/jira/browse/QPID-3914
JIRA issue .
This patch extends the Jakub's one for the missing client file based
authentication under the Windows. A client may
I compiled the latest version of the c++ qpid client/broker (from the
repository). I compiled it as a release version, not debug. I then compiled
the dotnet binding (org.apache.qpid.messaging.dll) also as release. Everything
works great and my code, using that dll, runs fine on the
Thanks for the direction Pavel!! I've found the problem! :)
In short it was a configuration management service (Puppet this case)
restarting the network subsystem on all three servers in the cluster at
once.
I assume at this stage, that the network restarts are a result of a puppet
