IP2016 Not Starting Tomcat and Javacontainer Automatically in Solaris

(Doc ID 2356793.1)

Last updated on FEBRUARY 02, 2018

Applies to:

Siebel Finance Service - Version 16.18 [IP2016] and later
Information in this document applies to any platform.

Symptoms

On : 16.18 [IP2016] version, Siebel EAI

ACTUAL BEHAVIOR
---------------

When the Siebel server is started, Tomcat and the javacontainer are not starting up automatically even after following the steps at How To Test Siebel IP2016 RESTFul Services API (Doc ID 2193144.2)

and implementing the workaround mentioned at SiebelRestCompIntMgr Component For Java Web Container On Unix OS Causes Many [catalina.sh] <defunct> Processes (Doc ID 2303207.1)


It can be manually started and works fine. just the auto start up script is not working.

EXPECTED BEHAVIOR
-----------------------
Tomcat should start up automatically.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. start the siebel server and confirm SiebelRestCompIntMgr Component is up and running but tomcat is not started at all .

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot auto start tomcat at the development environment.

Changes

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms