Bryan,
The agent should send class-indication messages to the broker 1) at
startup and 2) whenever a new class is dynamically created/registered.
If the broker doesn't have that schema cached, it will send the agent a
schema-request.
If you are talking about new versions of the same classes, the same
rules apply and the class hash had better be different in the new schema.
-Ted
Bryan Kearney wrote:
I am seeing a pattern where I launch an agent, do some debuggin, and
redeploy the agent which contains objects with new schemas. The broker
does not query the agent for new schemas... so.. my consoles get the
old classes. The net net for me now is to restart the broker and agent.
The broker caches the schema. Any way to turn this off, or make it
agressive with refreshes?
-- bk
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
