WebSphere Message Brokers
File: au13540_
Writer: Jane Brockbank

Task topic

This build: July 31, 2007 21:39:05

Did you log off Windows while WebSphere Message Broker components were active?

Windows platform On Windows, logging off when WebSphere Message Broker components (a broker, the Configuration Manager, or the User Name Server) are active can cause a problem. You might see messages, including BIP2070, BIP2642, BIP1102, and BIP1103 in the Windows Event log if this is the case.

When you log off, any queue managers that support these WebSphere Message Broker components are stopped unless they are defined to run as Windows services. The components all run as Windows services and remain active, but they find that the queue manager and queue manager objects that are associated with them are no longer available.

  1. If you log off, restart the queue manager that supports the Configuration Manager or the User Name Server, and the component re-establishes the connection to the queue manager.
  2. To avoid this problem, set the queue managers that are used by the broker, Configuration Manager and User Name Server to run as Windows services, so that logging off Windows does not cause this problem.
Related tasks
Troubleshooting and support
Making initial checks
Windows: Viewing the local error log
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:39:05

au13540_ This topic's URL is: