Contents

Versions Compared

Old Version 1

changes.mady.by.user Prathewraj M

Saved on

compared with

New Version 2

changes.mady.by.user Ashish

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

By default, ACLs are checked only at the time of performing an action, such as creating a publisher/subscriber on a topic. If an ACL is modified, clients connected to it are not affected. To get connected clients to check ACL when modified, perform the following steps:

  1. Open the profile for off-line editing through the Profile Manager using Studio, as explained in section 4.8.1 How to Enable Pinging
  2. Go to Fiorano -> etc -> FMQConfigLoader.
  3. Change the value of the AllowOnTheFlyAclCheck property to 'yes' as shown in the figure below:

4. Right-click on the FioranoMQ node and select Save option from the pop-up menu.

Note

The AllowOnFlyAclCheck flag works for all permissions except when:

  1. A publisher is publishing non-persistent messages on a topic.
  2. The permission to create publisher should be revoked for a topic.
  3. No exception is thrown even though the User is not allowed to publish since messages are sent in batch mode.

Work Around 1:

For NP messages, batching is enabled by default which leads to the behavior explained above. To view this Exception at the 'send' API location, set the BatchingEnabled parameter in the ConnectionFactory to 'FALSE'.

Work Around 2:

Add the following line to the client code environment while performing the lookup function:

Code Block
env.put("BatchingEnabled", "false")

Here, env is the environment passed while performing a JNDI lookup. This will disable batching for that particular client.

Adaptavist ThemeBuilder EngineAtlassian Confluence