Description:
When there is an OnStartup process deployed in the same engine of the JMS Starter that connects to the Weblogic JMS server, the JMS Starter is not able to start. If the OnStartup process is not present, the JMS Starter starts successfully, even if others starters are running at the same time. Additionally, the Weblogic server access policy is limited to a group, in which the Tibco user is included. If the Weblogic access policy is changed to everyone, Tibco is able to connect successfully even with the OnStartup starter deployed.


Symptoms:
BW.Example-Example Error [BW-Plugin] BW-JMS-100015 Activation error with process starter [Domains/OrderManagement/BusinessResources/Processes/OrderComponent/Starters/Weblogic Starter.process]
Activation error with process starter [Domains/OrderManagement/BusinessResources/Processes/OrderComponent/Starters/Weblogic Starter.process]
    at com.tibco.pe.core.ProcessStarter.setState(Unknown Source)
    .......
    .......
    .......
    .......

Caused by: weblogic.jms.common.JMSSecurityException: Access denied to resource: type=<jms>, application=oms_jms_module, destinationType=queue, resource=external_osm_request, action=receive
    at weblogic.jms.common.JMSSecurityHelper.checkPermission(JMSSecurityHelper.java:162)
    .......
    .......
    .......

Cause:
When the JNDI resource are defined outside the JMS connection, the error will be thrown.