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

On Windows, logging off when WebSphere Business Integration Message Broker components (a broker, the Configuration Manager, or the User Name Server) are active can cause a problem. You might see messages, including 2070, 2642, 1102, and 1103 in the Windows Event log if this is the case.

When you log off, any queue managers that support these WebSphere Business Integration 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 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 that component reestablishes the connection to the queue manager.
  2. To avoid this problem, set the queue managers used by the broker, User Name Server and Configuration Manager to run as Windows services, so that logging off Windows does not cause this problem.

Related tasks
Diagnosing errors
Making initial checks
Windows: Viewing the local error log