My Oracle Support Banner

start comp Command Does Not Start JMS Receiver When CommType=TLS (Doc ID 2742101.1)

Last updated on JANUARY 06, 2021

Applies to:

Siebel CRM - Version 20.9 and later
Information in this document applies to any platform.

Symptoms

A stopped JMS Receiver that has been TLS enabled does not start running tasks with the server manager command start comp.
A non-TLS enabled JMS Receiver actually starts running tasks as expected.
A restart of the enterprise starts tasks for both.
This poses a maintenance burden as if a TLS-enabled receiver is stopped for any reason, an enterprise restart is required to get the receiver running again.
The detailed steps to confirm are found below.


1. Create a custom JMSReceiver and do the necessary steps to set it to TLS as explained in Siebel Application Is Giving Server Busy Error After Enabling SISNAPI TLS with Siebel 19.x (Doc ID 2556213.1)
which include

Notice it goes online but no actual running tasks are seen in server manager.

6. Repeat steps 2,3,4,5 for the standard JMSReceiver which is NOT TLS enabled and confirm start comp actually starts running tasks.

The conclusion is when TLS enabled, JMS receivers go online but do not start running tasks as they should.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.