Resolving problems when using publish/subscribe

Publish/subscribe within WebSphere Message Broker is managed from the workbench, which is used to connect brokers in a topology or hierarchy, and to administer topic-based security (if a User Name Server is in use). Like other workbench changes, you need to deploy any changes that you make so that updates are sent to the broker.

This topic contains advice for dealing with some common problems that can arise when using publish/subscribe:

Your broker is not registering with the User Name Server

Application responses are not received

Your application is not receiving publications

Access control appears not to work

You cannot access the broker topology after you change the access control list (ACL)

Publishing a message causes a filter error

Symbols in subscription filters cause problems

There are problems with multiple brokers and communications

The workbench does not display non-Windows users

There are performance problems on AIX when the JIT compiler is not loaded

Error message BIP2332 is issued with SQLSTATE 57011 when you access the publish/subscribe database on z/OS

Your broker does not have the correct authority to run PGM/IP

Your client does not have the correct authority to run PGM/IP

Your client does not have sufficient memory to run PGM/IP

Related concepts
Publish/Subscribe
Trace