| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@576853 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@576799 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@576491 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@576396 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@576388 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@576378 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Parser classes.
The Connection Type (0-8 or 0-10) is decided based on the URL scheme if AMQConnection is created by passing a URL.
In other cases it will be based on a jvm switch. Other constructors in AMQConnection internally constructs an 0-8 URL and call the constrcutor with a URL.
In that case it is difficult to figure out the type of connection with out additional information.
The additional information commes in the form of the following jvm arguments
SwitchCon - enables this switch
0-10 - creates an 0-10 connection and the absence of it creates an 0-8 connection
This was done to minimize any impact on the test code.
currently only one code path can be tested at a given time.
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@575789 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
org.apache.qpidity.transport
* factored out the network specific pieces into
org.apache.qpidity.transport
* moved the mina specific code to
org.apache.qpidity.transport.network.mina
* replaced the handler chain with Sender/Receiver chains that can
deal with close request/closed notifications
* moved from an anonymous struct[] to a real Header class
* removed an excess copy from message data transmit
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@575474 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@575289 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
ConcurrentSelectorDeliveryManager that resolves the ordering problem.
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@574982 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The AMQConnection was not made abstract to preserve the widely usd AMQConsutructor in test cases.
Instead 0-8,0-10 specific functionality was delegated to a version specific delegate.
The version is selected via a JVM argument (and based on the URL format)
Currently this mean that we can test only a single code path (o-8 or 0-10) at a time.
Next Step is to refactor the URL stuff.
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@574582 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@574255 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@574227 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@574226 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@574223 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@574222 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
|
|
|
|
| |
provided.
The return message extends unprocessed_msg_0_8 as return message is only a 0-8 feature.
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@573282 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
BasicMessageConsumer and made them abstract
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@573039 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
TransactedTest, also modified TransactedTest to be slightly more robust
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@572751 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@572656 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@571367 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Testing done in Intelij and mvn command line via windows/cygwin.
Python tests removed from auto build pending Jython-siztion. Tested running broker in intelij and python run-tests from cygwin.
All tests pass. (CombinedTest still exhibts a race condition. but that has always been so.)
Additional Race condition identified (around MsgReject/AutoDeleteQueues) during testing patch to follow.
systests are inconsistent Some use TestableMemoryMessageStore some use MemoryMessgaeStore.
Lets not roll back this change if issues are discovered. Lets work together to go forward and address any issues. I have spent a lot of time ensuring the tests work for me so I hope that they work for you.
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@571129 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@569695 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@569691 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Here is the deadlock issue
---------------------------
The internal receive thread acquires the _incomingMessageLock and blocks on sync()
The MINA thread gets on to onMessage() and blocks while trying to acquire the incomingMessageLock
Since the MINA thread doesn't return it can't process the execution.complete() sent by the broker.
Since the execution.complete doesn't get processed, the sync() doesn't return.
Hence the deadlock.
Solution
----------
I rewrote the receive logic using a LinkedBlockingQueue and leveraging the application thread that calls receive methods
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@569688 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@569547 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@569431 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@569414 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) TopicImpl doesn't populate the routing key properly.
The Destination Impl needs to have a routing key field (I added the
field).
For Topic The queue name is generated.
For Queue the routingkey is same as queue name.
2) QpidMessage - Calling flip on messageData resets the limit to zero in
beforeMessageDispatch(). I commented out the flip()
3) QpidMessage - setMessageData
Instead of _messageData = messageBody, I modified it to do
_messageData = messageBody.duplicate();
4) MessageActorId is not set properly - so I modified the code to set
this. This id is used for the destination
5) When creating BytesMessageImpl, in the constructor, it doesn't read from the underlying
message impl. There for the _readIn is null and results in MessageNotReadableException.
I added a temp solution to read and populate _readIn.
However need to revisit it later
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@569238 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@568535 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
after calling flush
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@568321 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@568054 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
| |
added URL support to the client
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@567946 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@567678 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@567674 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@567629 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@567174 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@567048 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@566698 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@566548 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@566538 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
|
|
|
| |
Rearranged package structure for qpid client
Addded javadoc support for qpid client
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@566403 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@566187 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
|
|
| |
Added Java doc
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@566155 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@565727 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
| |
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@565561 13f79535-47bb-0310-9956-ffa450edef68
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Sending Messages
-------------------
ByteBufferMessage for small messages - data will be in memory.
FileMessage and StreamingMessage for sending large messages.
Receiving Messages
-------------------
For small messages u can use MessageListener and receive ByteBufferMessage.
You need to use the MessageListener with the MessagePartListenerAdapter.
For large messages it is recomended to use MessagePartListener.
git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk@565407 13f79535-47bb-0310-9956-ffa450edef68
|