delta/python-packages/qpid-python.git/qpid/cpp/src/tests, branch java-broker-bdb-ha2

QPID-5641: [legacystore] Valgrind reports memory leaks on older store tests

2014-03-21T15:50:56+00:00

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1579963 13f79535-47bb-0310-9956-ffa450edef68

QPID-5362: No store tools exist for examining the journals - Bugfix and reorganization of qls python modules.

2014-03-18T13:54:46+00:00

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1578899 13f79535-47bb-0310-9956-ffa450edef68

QPID-5613: Self test broker start command fails without --interface option.

2014-03-07T22:51:24+00:00

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1575443 13f79535-47bb-0310-9956-ffa450edef68

Revert "NO-JIRA: CMakelists.txt check that ../python exists before building it."

2014-03-05T20:54:27+00:00

This reverts most of commit r1574138. The changes were intended to simplify
handling of setup.py by letting it detect when things were out of date,
but even when there are no changes setup.py does touch some files:

changing mode of /home/andrew/Work/qpid/bld-ninja/src/tests/python/commands/qpid-python-trunning install_egg_info
removing /home/andrew/Work/qpid/bld-ninja/src/tests/python/qpid_python-0.27-py2.7.egg-info
writing /home/andrew/Work/qpid/bld-ninja/src/tests/python/qpid_python-0.27-py2.7.egg-info

This commit restores the previous logic that avoids running setup.py if not needed
but retains the if (EXISTS ${python_src}) check to avoid all this logic if
there is no python source directory available.

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1574656 13f79535-47bb-0310-9956-ffa450edef68

NO-JIRA: CMakelists.txt check that ../python exists before building it.

2014-03-04T17:16:10+00:00

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1574138 13f79535-47bb-0310-9956-ffa450edef68

NO-JIRA: Fix Coverty "Uncaught exception" errors in test clients.

2014-02-26T14:22:27+00:00

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1572061 13f79535-47bb-0310-9956-ffa450edef68

QPID-5561: QPID-5565: Broker->ACL module improvements

2014-02-26T14:12:56+00:00

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1572059 13f79535-47bb-0310-9956-ffa450edef68

NO-JIRA: Fix compile error on RHEL5 in qpid-ping

2014-02-22T01:00:50+00:00

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1570775 13f79535-47bb-0310-9956-ffa450edef68

QPID-5568: HA C++ qpid::messaging AMQP 1.0 client failover logging is not clear

2014-02-20T15:39:43+00:00

The qpid::messaging AMQP 1.0 protocol logging did not give clear information
about reconnection during failover.

This patch simplifies the reconnect logic by collapsing all known addresses from
broker URL and reconnect URLs into a single URL with no duplicates.

It rationalizes the info and notice logging as follows:

# Initial connection with multiple addresses, info logs show the
# full URL, each attempt to connect and the finally connected address.

[Messaging] info Starting connection to amqp:tcp:20.0.10.33:5672,tcp:20.0.10.34:5672,tcp:20.0.10.35:5672
[Messaging] info Connecting to tcp:20.0.10.33:5672
[Messaging] info Failed to connect to tcp:20.0.10.33:5672
[Messaging] info Connecting to tcp:20.0.10.34:5672
[Messaging] info Failed to connect to tcp:20.0.10.34:5672
[Messaging] info Connecting to tcp:20.0.10.35:5672
[Messaging] info Connected to tcp:20.0.10.35:5672

# Re-connection due to a failure. notice logs for the start of reconnection (with full URL)
# and eventual sucess (with individual address). info logs for individual connection attempts.

[Messaging] notice Auto-reconnecting to amqp:tcp:20.0.10.33:5672,tcp:20.0.10.34:5672,tcp:20.0.10.35:5672
[Messaging] info Connecting to tcp:20.0.10.33:5672
[Messaging] info Failed to connect to tcp:20.0.10.33:5672
....
[Messaging] info Connected to tcp:20.0.10.33:5672
[Messaging] notice Auto-reconnected to amqp:tcp:20.0.10.33:5672

The idea here is that there are no logs by default (info is not on by default)
for "normal" behavior, but failover does get a (short) notice log by default.
By turning on info logs you can follow the detailed blow-by-blow of failover
without getting drowned in the detail of debug logs.

Note that final failure to connect is signalled to the application via an exception.
There was not previously any log message for that and I didn't add one.

Additional changes: updated qpid-ping test client to use the messaging library.

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1570231 13f79535-47bb-0310-9956-ffa450edef68

NO-JIRA: Fix build error in ha_test_max_queues for release builds.

2014-02-18T16:09:23+00:00

argc was only being tested in an assert which was compiled out for release builds.

git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1569400 13f79535-47bb-0310-9956-ffa450edef68