Temporary queues not being cleaned by ActiveMatrix Administrator."javax.jms.JMSSecurityException: Not permitted".
Article ID: KB0089885
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix Service Grid | - |
| TIBCO ActiveMatrix BusinessWorks Service Engine | - |
| Not Applicable | - |
Description
Description:
Symptoms:
Cause:
Connections with temporary queues are not being closed when the EMS user has no publish permission on the topic or queue and is throwing the error "javax.jms.JMSSecurityException: Not permitted" exception at the BWSE (Business Works Service Engine) Invoke partner activity.
Steps to reproduce this issue follows.
1). Create composite application with BWSE component.
2). In the BWSE implementation, use the Invoke Partner activity to call a third-party service with SOAP over JMS binding. Set the AMX endpoint type.
3). Configure the AMX reference to use temporary queues for a reply message.
4). Enable authorization in EMS and mark the request queue as secure. Do not grant send permission on the request queue to the AMX user.
5). Deploy the application and invoke the exposed service several times.
6). Examine the temporary queues. You will notice temporary destinations with no messages and receivers.
While processing the service which is making use of temporary queues, temporary queues are being created in the EMS (Enterprise Messaging Service) server and are not being automatically cleaned up.
Symptoms:
Temporary queues being created with no receivers and no pending messages while invoking the service.
Cause:
Connections with temporary queues are not being closed when the EMS user has no publish permission on the topic or queue and is throwing the error "javax.jms.JMSSecurityException: Not permitted" exception at the BWSE (Business Works Service Engine) Invoke partner activity.
Steps to reproduce this issue follows.
1). Create composite application with BWSE component.
2). In the BWSE implementation, use the Invoke Partner activity to call a third-party service with SOAP over JMS binding. Set the AMX endpoint type.
3). Configure the AMX reference to use temporary queues for a reply message.
4). Enable authorization in EMS and mark the request queue as secure. Do not grant send permission on the request queue to the AMX user.
5). Deploy the application and invoke the exposed service several times.
6). Examine the temporary queues. You will notice temporary destinations with no messages and receivers.
Issue/Introduction
Temporary queues not being cleaned by ActiveMatrix Administrator."javax.jms.JMSSecurityException: Not permitted".
Resolution
Grant send, receive and browse permissions for the EMS user on the request queue.
Feedback
Yes
No
Powered by
