> > When I changed the code to use the destination values, it successfully > created the producer. I can now send messages. > With respect to the consumer, the ExchangeDeclareBody was successfully > created, but the system hangs on protocolHandler.syncWrite. Digging into > that now. >
The only usual reason for it to wait there is that it didn't get the reply frame it was waiting for, posibly because something on the other end went bang. Did you get any further digging into it? I managed to resolve the hang issue. Did so by diffing communications of a rabbitmq and qpid consumer. The hard-coded nowait is set to true in createExchangeDeclareBody. It appears that it can have either value when creating a producer, but should be false when creating a consumer. Not stating that this is necessarily correct - being knew to AMQP - but that is what makes the code work. These aforementioned discoveries lend themselves to concern. I've now modified the code to accommodate the hard-coded durable and autodelete values, and have changed nowait to false. Are these valid changes? Should the nowait be made variable for producers? Should internal, and for that matter arguements (FieldTable), be made variable? How do we get these changes into the next version? Bug? On the other hand, if these changes are not valid what is the proper usage so that I can communicate with Rabbitmq. Roger -- View this message in context: http://qpid.2158936.n2.nabble.com/Hard-coded-destination-parameters-prevent-creation-of-Producer-and-Consumer-tp7581160p7581249.html Sent from the Apache Qpid users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
