What is the cause of the following exception: TIBCO.Rendezvous.RendezvousException: Not permitted at TIBCO.Rendezvous.CMListener.ConfirmMessage(Message message)
Article ID: KB0086286
Updated On:
| Products | Versions |
|---|---|
| TIBCO Rendezvous | - |
| Not Applicable | - |
Description
Resolution:
Description:
= = = = = = =
The following are the possible reasons for getting the "Not permitted" exception in a RVCM environment:
1). If a CM listener is not registered for certified delivery with the sender, it presents the sender's name to the callback method but omits the sequence number. In this case, the receiving program cannot confirm delivery. TibrvCmListener.confirmMsg() throws an exception with the status code TibrvStatus.NOT_PERMITTED.
Notice that the first labeled message that a program receives on a subject may not be certified, that is, the sender has not registered a certified delivery agreement with the listener. If appropriate, the certified delivery library automatically requests that the sender register the listener for certified delivery.
2). This error is also seen if the user tries to confirm a certified message which has already been confirmed. Make sure that you are not trying to confirm the same message twice.
3). You do not have the appropriate permissions to create/access the ledger file in the respective directory. Make sure that the user running the cm applications has the permission to create/access the ledger file.
4). This error can arise if more than one CM transports is using this same ledger file. Make sure that no other CM transport is using the same ledger.
Environment:
= = = = = = =
TIBCO Rendezvous (RV) – All versions
All Platforms
Description:
= = = = = = =
The following are the possible reasons for getting the "Not permitted" exception in a RVCM environment:
1). If a CM listener is not registered for certified delivery with the sender, it presents the sender's name to the callback method but omits the sequence number. In this case, the receiving program cannot confirm delivery. TibrvCmListener.confirmMsg() throws an exception with the status code TibrvStatus.NOT_PERMITTED.
Notice that the first labeled message that a program receives on a subject may not be certified, that is, the sender has not registered a certified delivery agreement with the listener. If appropriate, the certified delivery library automatically requests that the sender register the listener for certified delivery.
2). This error is also seen if the user tries to confirm a certified message which has already been confirmed. Make sure that you are not trying to confirm the same message twice.
3). You do not have the appropriate permissions to create/access the ledger file in the respective directory. Make sure that the user running the cm applications has the permission to create/access the ledger file.
4). This error can arise if more than one CM transports is using this same ledger file. Make sure that no other CM transport is using the same ledger.
Environment:
= = = = = = =
TIBCO Rendezvous (RV) – All versions
All Platforms
Issue/Introduction
What is the cause of the following exception:
TIBCO.Rendezvous.RendezvousException: Not permitted at TIBCO.Rendezvous.CMListener.ConfirmMessage(Message message)
Feedback
Yes
No
Powered by
