ORACLE HTTP SERVER 12.2.1.4 FAILS TO START/SHUTS DOWN IN 2 MINUTES

Recently we built a collocated Oracle http Server (12.2.1.4.0) (OHS) server for POC purposes (This issue occurs in standalone ohs too). After configuring domain, I have started ohs server from em console. I verified that ohs processes were running by using ps -ef | grep ohs command. Satisfied with outcome I called it a day. Next day, I sshed into the machine, to my surprise there was no ohs process running. This time started ohs from command line using startComponent.sh. ohs server started, I was able to open ohs home page but not admin and em consoles. ohs processes were gone again after some time.

I tried to start it from em console and wlst script as well. But end result is same. Meanwhile, I observed a pattern that OHS processes are getting stopped after approximately 2 mins. As this a POC machine, we got single CPU VM. I thought due to limited cpu, startup process is taking time and eventually getting timed out. So I ran below command to find if there is any startup timeout with value of 2 mins/120 seconds.

cd $DOMAIN_HOME/config/fmwconfig/components/OHS
grep -R 120 *

Found start-timeout parameter in $DOMAIN_HOME/config/fmwconfig/components/OHS/ohs1/ohs.plugins.nodemanager.properties. Increased it 600 seconds (10 mins) and started ohs again. It stopped again after 10 mins. So, safely ruled out that it was not hardware capacity issue.

Luckily, quick search in Oracle metalink gave me a pointer about the issue. As per Doc ID 2606314.1, issue is caused due to default wallet configured for localhost. I have followed solution 1 mentioned in the doc and problem resolved. Solution is to change Listen and Virtual hosts to 127.0.0.1 in admin.conf file.

Note: If you are using collocated ohs, don’t forget to stop admin server before making config changes.

Comments

Post a Comment

Popular posts from this blog

HOW WE REDUCED SOA OSB PROVISIONING FROM 4 DAYS TO 4 HOURS

 In our organization, we’ve undertaken the task of upgrading both SOA and OSB from version 12.2.1.3 to 12.2.1.4. This involves an out-of-place migration approach, wherein we create a new environment and switch traffic during the cutover. As you know, this process typically requires several days we opt for manual provisioing. A very significant amount of automation work was previously accomplished for 12.2.1.3 by our predecessors. Despite these efforts, the process still used to take lot of time due to following factors: Bugs in existing automation. For example, SOA composite deployments is not stable which warrants lot of manual work Import of 10s of TLS Certificates into KSS Manual retiring and shutting down of services Monitoring setup Miscellaneous: Increasing Log file count, enabling GC logging, changing heap parameters, bash profile changes While our current automation initiatives have yielded substantial savings, we aimed to capitalize on this upgrade activity to enable end-t...
Read more

NOT ABLE TO START RABBITMQ CLUSTER: CANNOT DECLARE A QUEUE ‘~S’ ON NODE ‘~S’: ~255P

We have 7 node rabbitmq cluster and we are using sharding queues. We have shutdown all non prod rabbitmq nodes as part of VM patching. As it was non prod, we thought of shutting down all together instead of rolling patching. We couldn’t start the any of the rabbitmq post patching. All of nodes were failing to start with the below error: 2022-06-23 05:13:10.104845-07:00 [error] <0.647.0> “Cannot declare a queue ‘~s’ on node ‘~s’: ~255p”, 2022-06-23 05:13:10.104845-07:00 [error] <0.647.0> [“queue ‘sharding: shard.my.queue – rabbit@rabbit1’ in vhost ‘my_vhost'” This is a known issue in some old versions of rabbitmq. rabbitmq node fails to come up with above error. Work around for this is to disable sharding policy for the problematic sharding queue. It can be done either from command line or from rabbitmq admin page. It requires to connect a running node. But as all the nodes were down, we could not disable sharding policy. Luckily, rabbitmq allows disabling sharding pulgi...
Read more

SOA SUITE 12.2.1.4 INSTALLATION: GOT EXCEPTION WHEN AUTO CONFIGURING THE SCHEMA COMPONENT(S) WITH DATA OBTAINED FROM SHADOW TABLE

  We planned to do out of place upgrade from soa suite 12.2.1.3 to 12.2.1.4. As part of this, we planned to automate end to end provisioning. While executing domain configuration using ansible and python scripts, we got following error in domain creation step. Got exception when auto configuring the schema component(s) with data obtained from shadow table. Failed to build JDBC Connection object: com.oracle.cie.domain.script.jython.CommandExceptionHandler. exception. Quick internet search gave few solutions like deleting domain-registry.xml file, verifying dehydration store password supplied to script etc. But none of them helped. After trying several options, I thought I might have done some stupid error prior to domain creation step. To track down the issue, though of checking what getDatabaseDefaults actually doing. I tried to grep for the getDatabaseDefaults function call inside oracle home. But couldn’t find the source code for the python function. As a final resort, thought of...
Read more