Your Configuration Manager Proxy application hangs if
the Configuration Manager is not available
Scenario: When the Configuration Manager is
unavailable, the Configuration Manager Proxy application
hangs.
Explanation: Communication between the Configuration Manager Proxy and
the Configuration Manager is asynchronous, so the Configuration Manager Proxy hangs
because it is waiting for a message from the Configuration Manager.
Solution: Configure the maximum amount of time that the Configuration Manager Proxy waits by using the following method:
// Wait for a maximum of 10 seconds
ConfigManagerProxy.setRetryCharacteristics(10000);
This
represents the time in milliseconds that the Configuration Manager Proxy will
wait for information before throwing the ConfigManagerProxyPropertyNotInitializedException exception.
If
you set this timeout value too low, an exception will be thrown even if the Configuration Manager is available.
You set a property of an object and query its value, but the value
has not changed
Scenario: You have set a property of an object, then queried
its value; the value has not changed.
Explanation: Methods that change properties of domain objects
are not processed immediately. If you call a property change method on a Configuration Manager Proxy object, this causes the Configuration Manager Proxy to
send a message to the Configuration Manager asking it to
make the requested change. The Configuration Manager processes
the request asynchronously and notifies any AdministeredObjectListeners of
the affected object when the change has been attempted.
Solution: Methods that change state usually return as soon
as the request has been put to the Configuration Manager's
queue manager, or following a call to ConfigManagerProxy.beginUpdates(),
as soon as the request has been added to the current batch. If the property
has still not been updated after the action's response to the request has
been returned to the Configuration Manager Proxy, consult the
response message for more details.
You cannot connect to a Configuration Manager using
.CONFIGMGR files
Scenario: You cannot connect to a Configuration Manager using .CONFIGMGR files.
Explanation: The MQPropertyFileConfigManagerConnectionParameters class
allows Configuration Manager Proxy applications to connect to Configuration Managers using files with a .configmgr extension,
although it requires an XML parser in order to do this.
Solution: Ensure that a supported parser is available on
the CLASSPATH. A supported parser is shipped with the product.
Alternatively,
use the MQConfigManagerConnectionParameters class instead
of the MQPropertyFileConfigManagerConnectionParameters class.
This allows you to connect to Configuration Managers by
specifying the host name, queue manager name and port of the target Configuration Manager directly.
This method does not require an XML parser.
You tried to move a broker between Configuration Managers
and now you cannot see the broker's resources
Scenario: You used the BrokerProxy.setUUID() method to attempt
to move a broker from one Configuration Manager to another
and you can no longer see the broker's execution groups, message flows, message sets, and subscriptions.
Explanation: This is a limitation of the setUUID() method.
Solution: Remove all deployed resources and redeploy them
to the broker.