Anyone?
Tim
On Thu, Nov 18, 2010 at 2:10 PM, Tim Chen t...@evri.com wrote:
Hi all,
I wonder what's the best way to handle reconnect to the broker when broker
is unavailable (network is down / broker crashed, etc) using Java JMS client
to C++ broker?
Currently when using the JMS client
It's not too late to add it, but that doesn't necessarily mean it's going to
make it in either.
I'm assuming ./setup.py sdist was to be run in the qpid/tools directory? The
artifact produced by doing that has no LICENCE, NOTICE, or (as ./setup.py
complains about) README files. The first two
Hi Tim,
The Java client uses the connection URL to control failover, but I'm not
sure whether/how that is honoured by the C++ broker. It also defaults on
trunk to use a NoFailover policy.
Rajith - I think you might have the most up-to-date knowledge on the Java
client failover on trunk, do you
Use QPID_TSS consistently and revert uint to the standard unsigned int
--
Key: QPID-2955
URL: https://issues.apache.org/jira/browse/QPID-2955
Project: Qpid
Issue Type:
[
https://issues.apache.org/jira/browse/QPID-2955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorin Suciu updated QPID-2955:
--
Priority: Minor (was: Major)
Summary: Use QPID_TSS consistently (was: Use QPID_TSS consistently
[
https://issues.apache.org/jira/browse/QPID-2955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorin Suciu updated QPID-2955:
--
Attachment: qpid_2955.patch
Use QPID_TSS consistently
-
