The Curious Case of Missing http Access Log Entries

Few days ago, a person from another team in our project approached us to about intriguing application access issue. They have a java based application deployed in weblogic server front-ended by Oracle http server. She told the application is working fine in production env but not working lower env. They are able to home page in prod and not able to open in lower env. They are getting 404 page not found error. 

She was basically a developer so asked our admin team to check if there is anything wrong with OHS configuration.

She told that she could http get logs in ohs access.log file but not in server access.log file which is present in $DOMAIN_HOME/servers/server1/logs. So she suspected some issue in ohs and ohs was failing to pass request to weblogic server. 
We have followed below steps to troubleshoot issue:
1) I got prod and test urls and tested from my machine. I too got same results. 
2) We have verified OHS configuration and everything looked OK.
3) We went deployments from admin console and verified application status. It is also OK.
4) We have verified OHS access logs and weblogic server logs. We didn’t find any meaningful information.
5) Meanwhile, I got some other task and returned after 30 mins. When I was checking weblogic access.log again, I saw entries related to this application. 
6) I suspected it is due to log http log buffer setting in weblogic. So, to confirm it I have hit this url multiple times. Hurry !!! I could see the log entries immediately.
7) So this what happened is that as the number of requests coming in the test env is less, weblogic bufffered log entries. This is the default behavior and can be modified http log setting present in Environment -> Servers -> ManagedServer -> logs -> http -> Advanced -> Log File Buffer.
It turned out that there was some issue with setting application context in code which caused the issue.

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