Re: Problem with Session.addBroker(), Exchange names beginning with "amq." or "qpid." are reserved.

On 03/15/2010 10:33 PM, Joan Bellver Faus wrote: Exception in thread "Thread-3" org.apache.qpid.console.ConsoleException: org.apache.qpid.transport.SessionException: ch=0 id=0 ExecutionException(errorCode=NOT_ALLOWED, commandId=10, classCode=7, commandCode=1, fieldIndex=0, description=not-allowed

Re: Message replay tracker question

On 03/16/2010 02:54 PM, Wes Parish wrote: I have a question about the qpid::client::MessageReplayTracker C++ class. I am using a MessageReplayTracker to send messages to a broker. Periodically when I close the session and connection object from another thread I receive the following warning

Message replay tracker question

I have a question about the qpid::client::MessageReplayTracker C++ class. I am using a MessageReplayTracker to send messages to a broker. Periodically when I close the session and connection object from another thread I receive the following warning message that is printed to stderr: "Warning

Re: java amqp api vs. jms api

Adam, We only support the JMS API for reasons outlined by William. Those examples are written against a bunch of classes that are subject to change without notice. You could easily cover most use cases with the JMS API + configuration. If you have any concerns about how to support a particular us