| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Updated ApplicationRegistries to pass the instanceID to the BrokerActor in an attempt to better identify what brokers are shutting down during our test runs.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@819605 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
in the same way as 0-8/9
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@819604 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
that appears during Java broker test runs
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@819594 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@819593 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@819592 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
|
|
| |
deadlock issue with 0-10 rollback method and onMessage usage. Moved 0-10 rollback strategy to the abstract AMQSession and updated 0-8 to use that approach.
0-8 Still excluded from test runs as the race condition is not that the dispatcher would hold a message and reject after the TxRollback. The problem is the Java Broker sends a message out after the FlowOk message so the Dispatcher then sits on it, see QPID-2116. This exact problem was hidden due to the way the Dispatcher is stopped. This problem has not been addressed. The request to stop the dispatcher can only actually stop the dispatcher whilst it is in the middle of processing a message. The stop needs to interrupt the _queue.take() and hold the dispatcher AFTER the processing of any message that it needs to do: see QPID-2117.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@819590 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
execute the 'broker.clean' command after every test method is run
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@818840 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
|
| |
I had missed this bit when I committed last night.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@817867 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
|
|
| |
Added a check in the getNextBrokerDetails method to return null when the current broker equals the only remaining broker in the list
A test case for this will be added once I finalized the test case for the failover exchange method
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@817487 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
|
| |
I have also added a simple check for the default message priority in an existing test in JMSPropertiesTest
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@817478 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
|
|
|
|
|
| |
I didn't meddle with the existing log4j.properties file present in the common module as it maybe used in the broker.
However a cursory glance at the etc directory revealed that the the broker too has a log4j.xml file.
So perhaps the log4j.properties files in the common module is not really needed.
(The settings given i the log4j.xml under the client module could be overriden by explicitly specifying a log4.xml file using -Dlog.configuration property)
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@817457 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
for the failover server. As a result the connection has been failing. Updated to use correct system property and added text to both default.testprofile and test-provider.properties to ensure that the changes are made in both locations, Ideally JNDI connection would use the same system property that is used by QTC for starting the broker. However I don't believe that it is currently doing that.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@817295 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
|
| |
testRuntimeSelectorError
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@816579 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
found the ready line. Added broker.stopped line to cpp.testprofile 'Exception constructed' this identifies port conflict issues. Local testing has shown that this works as expected.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@816150 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@815771 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@815206 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
need to do it aswell.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@814670 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
|
|
|
|
| |
brings it in line with qpid-run.
If QPID_PNAME is not set then it will fall back to QPID_STOP_SERVER so as to main backward compatibility.
If neither are set then it will only use -DPNAME=" as the search. Thus allowing the value to have been changed
and this script still to detect QPID processes.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@814545 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
|
|
| |
property -DPNAME="".
Ensured value is quoted to allow spaces in QPID_PNAME. i.e QPID_PNAME="Production Broker"
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@814544 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
Just check for the file name rather than the path.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@813856 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
|
|
|
|
|
| |
before performing store.deleteQueue().
Created ModelTest to validate the change, (testDeletionDurableViaJMX).
To facility the testing, extracted JMX Operations from ManagementActorLoggingTest to a new JMXTestUtils and updated both ModelTest and MALT to use this interface.
Updated 010(cpp) and 08(Java-InVM) excludes as the CPP does not have JMX and the InVM JMX is unreliable (see QPID-2097)
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@813801 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@813799 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
java.io.tmpdir.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@813798 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
on InVM test cases
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@813797 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
the message store. This will allow current DerbyStores to start up but will mean that the existence of the exchange in the configuration is its durability. Remove it from the config and it is gone. This differs from the way queues work.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@813796 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@813476 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
an more reliable way of adjusting the configuration form the test. In doing this it made sense to udpate the configurations such that they all inherit from the cannonical config.xml from the broker package. Each test now gets its own configuration file that is used to override the defaut values in config.xml.
So the config is now a hierarchy of:
- Test Specific
- Systest adjustments
- stock broker config.xml
I have disabled the DerbyMessageStoreLoggingTest as after making this change it is more reliably throwing a Derby exception on broker startup.
The other changes to the tests were to ensure they correctly save the Test Specific config file before loading. As for some reason, Commons Configuration is not abiding by the optional flag.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@813461 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
ServerConfigurationTest. Merged virtualhost.xml with config.xml
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@813459 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@812825 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@812821 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@812156 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
sync on the failoverMutex in AMQSession that was causing the notification of the close to be blocked until a TimeOutException occured.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@812153 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
control setting from the environment
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@812103 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
error response
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@812083 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
main threads closing. The issue is ok as the main thread will not perform a syncWait, however, the set exception will be rethrown.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@812043 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
be set on a per session basis
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@811748 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@811725 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
fixed the issue with ChannelCloseExceptions by closing the channel and not sending the ChannelClose when the Channel has already been closed by the broker.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@811472 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
|
|
| |
the mina exception notification thread and the clients main thread blocking for a frame. Occasionally, the client will start blocking just after the notification and so will Timeout. This update ensures that blocking does not occur if the connection has been marked closing or is closed. The lastException set on the StateManager is thrown instead.
The connection close also needed to take into consideration this fact. The syncWrite on for ChannelClose and ConnectionClose are now only down if we are not in a closing situation. As the 0-10 code path does not use the StateManager the changes were applied to the 0-8 Session. Further testing may be needed to validate that the 0-10 client code path does not also have this race condition.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@811471 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@811470 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@811469 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@810584 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@810538 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
before delivered messages could be acked. So adjusted test to have the client dispatcher ready to deliver and relax the constraint that we validate which actor is doing the logging. The fact the state has changed correctly is the important factor.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@810441 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
initial receive is to low as there will be no prefetched data to use. Increasing to 1000ms.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@810093 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
SUSPENDING states so that the log can occur. As there are multiple threads editing the state of the subscripition it is possible that the state change does not result in a log message being produced.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@810072 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
|
|
| |
condition when a control thread trys to close the connection at the same time as the exception handling thread is also closing the connection.
Solution here is to wait for the exception handling thread to have done enough to mark the connnection closed so the race condition will not occur.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@809981 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@809957 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
better tested by the _Timeout test. This test verifies that the message is not in the file then waits for it ot occur. The _Found test is failing as we have not waited long enough for the message to be logged.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@809936 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
file 10 times, just in case.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@807983 13f79535-47bb-0310-9956-ffa450edef68
|