Problems when using publish/subscribe

Publish/subscribe within WebSphere Business Integration 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 section outlines some common problems that can arise when using publish/subscribe. It contains advice for dealing with the problems:

Broker is not registering with the User Name Server

Application responses are not received

Application is not receiving publications

Access control appears not to work

Message persistence in publish/subscribe is normally preserved. However, a subscriber might not get the expected persistence if ACLs do not allow it.

You cannot access the broker topology after changing the access control list

Publishing a message causes a filter error

Symbols in subscription filters cause problems

Problems with multiple brokers and communications

The workbench doesn't show non-Windows users

Performance problems on AIX when the JIT compiler is not loaded

You get error message BIP2332E with SQLSTATE 57011 when accessing the publish/subscribe database on z/OS.

Related concepts
Publish/Subscribe
Trace

Related tasks
Developing publish/subscribe applications
Viewing broker domain log information
Viewing WebSphere MQ log information
Interpreting trace
Dealing with problems

Related reference
User trace
Publish/subscribe
mqsicreatebroker command
mqsichangebroker command