| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
QPID-3258
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1103088 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1103083 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1091571 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
detached.
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1091560 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1088776 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1088728 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
|
| |
Porting the fix made in trunk at rev 1087890 into the 0.10 release branch.
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1088643 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
r1088539)
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1088634 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
distribute. Fixes QPID-3176.
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1087729 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1086778 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1086770 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1085355 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
Makefile.am.
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1084172 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
|
|
|
|
|
| |
stack
The hang was caused by re-entrant attempts to initialize the Logger
singleton when an exception was thrown during logger configuration.
The fix is to disable exception logging temporarily while the logger
is constructed.
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1083897 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
Fix name mangling for reserved "type" symbol to work on ruby 1.8 and 1.9.
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1083889 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
|
| |
Warnings for late-and-overrun tasks were not being correctly reported.
Lateness for overrun tasks below the late threshold were not being reported.
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1083082 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
This reverts commit r1082552
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1082962 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
|
| |
Warnings for late-and-overrun tasks were not being correctly reported.
Lateness for overrun tasks below the late threshold were not being reported.
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1082552 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These messages, printed at plugin load time, interfere with qpidd
--check. It is supposed to print the PID of a running qpidd daemon to
stdout, for use in scripts and the like. However with log-to-stdout
enabled these messages obscure the PID.
They are in any case of little value, individual plugins can log their
start-up messages on initialization time which does not cause a
problem
Merged from trunk r1081548.
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1082154 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1081413 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1081339 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1080344 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1080013 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1080009 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1080006 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1080001 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1079953 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1079892 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1079865 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1079864 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
|
| |
Applied patch from Justin Ross <jross@redhat.com>
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1079627 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1079482 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1079321 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1078967 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With the store doing async completions, completion IO callbacks could
be queued differently on different nodes. This led to inconsistent
management changes in a cluster when a connection was modified in an
IO callback.
Fix was to mark IO callback processing as not cluster safe, so
connections don't record management stats during an IO callback.
Test changes:
- enable durable tests in test_management.
- add substitutions to mask known issue of inconsistent "stats changed" messages.
- add transactional client to test_management.
- ignore heartbeat connection close logs in cluster_test_logs.py
- make brokertest.retry more accurate
- fix minor bug in brokertest.log_ready.
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1078965 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1078861 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
3/4/2011
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1078833 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1078823 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1078121 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
|
|
|
| |
align with unquoted names used elsewhere in the console
Merged from trunk r1077869.
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1078061 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.10@1076820 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
|
|
| |
Only UNRELIABLE and AT_LEAST_ONCE is supported.
Currently the reliability mode is used only for determining the accept-mode.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1076800 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
|
|
|
| |
The isQueueExist method is modified to handle the exception when a queue has been deleted.
Both the Message producer and consumer now delete the queue if the delete option is selected and will not check if the queue is empty or if there are any subscribers on it.
Also added test cases.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1076670 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
|
|
|
| |
and the host system timing base yields and elapsed time of zero.
The change is to throw a meaningful error message rather than throwing
an obscure DIV0 error.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1076652 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
|
| |
- Change error checks so that don't throw an incorrect exception in getters
when the queue is null. This should only happen when sending.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1076642 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
|
|
|
| |
- Additional header comments
- Added pendingEvents method to ConsoleSession and AgentSession
- Ensure that nextEvent will not block if timeout is IMMEDIATE (ConsoleSession and AgentSession).
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1076625 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
exchange's alternate-exchange
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1076604 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
|
|
|
|
|
| |
The getPropertyNames method will filter out any property names whose values are not allowed as per the JMS spec.
I could have used the ALLOWED map to check if a value is a valid type.
But unfortunately that map contains byte[] as a valid type, which is not correct as per the JMS spec.
I did not want to modify that map or the behaviour of the setObjectProperty or getObjectProperty methods as there might be applications out there that is depending on it.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1076532 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
|
| |
Instead of checking if it's an instance of AMQQueue, the code the now checks if it's an instance of AMQDestination and javax.jms.Queue to cover the AMQAnyDestination case. The same check is done for topics. Added test cases for QueueReceivers, TopicSubscribers and DurableTopicSubscribers using the new addressing scheme.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1076516 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
qmf2-prototype.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1076376 13f79535-47bb-0310-9956-ffa450edef68
|