Skip to main content

Oracle http-web-access.log file is growing in the long run

http-web-access.log file is in the $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_<host>_<sid>/log directory. This log file grows in the long run and can be managed from  $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_<host>_<sid>/config/http-web-site.xml file.


<?xml version = '1.0' standalone = 'yes'?>
<!DOCTYPE web-site PUBLIC "OracleAS XML Web-site" "http://xmlns.oracle.com/ias/dtds/web-site-9_04.dtd">
<web-site port="1158" display-name="OC4J Java HTTP Web Site">
        <!-- The default web-app for this site, bound to the root -->
        <default-web-app application="default" name="defaultWebApp"/>
        <web-app application="default" name="dms0" root="/dms0"/>
        <web-app application="default" name="dms" root="/dmsoc4j"/>
        <web-app application="em" name="em" load-on-startup="true" root="/em"/>


        <!-- Access Log, where requests are logged to -->
        <access-log path="../log/http-web-access.log"/>
        <!-- Uncomment this if you want to use ODL logging capabilities
        <odl-access-log path="../log/http-web-access" max-file-size="1000" max-directory-size="10000"/>
        -->
</web-site>

For changes in order to take effect, oracle dbconsole has to be restarted.

Comments

Popular posts from this blog

Sending Jboss Server Logs to Logstash Using Filebeat with Multiline Support

In addition to sending system logs to logstash, it is possible to add a prospector section to the filebeat.yml for jboss server logs. Sometimes jboss server.log has single events made up from several lines of messages. In such cases Filebeat should be configured for a multiline prospector. Filebeat takes lines do not start with a date pattern (look at pattern in the multiline section "^[[:digit:]]{4}-[[:digit:]]{2}-[[:digit:]]{2}" and negate section is set to true ) and combines them with the previous line that starts with a date pattern. server.log file excerpt where DatePattern: yyyy-MM-dd-HH and ConversionPattern: %d %-5p [%c] %m%n Logstash filter:

Creating Multiple VLANs over Bonding Interfaces with Proper Routing on a Centos Linux Host

In this post, I am going to explain configuring multiple VLANs on a bond interface. First and foremost, I would like to describe the environment and give details of the infrastructure. The server has 4 Ethernet links to a layer 3 switch with names: enp3s0f0, enp3s0f1, enp4s0f0, enp4s0f1 There are two bond interfaces both configured as active-backup bond0, bond1 enp4s0f0 and enp4s0f1 interfaces are bonded as bond0. Bond0 is for making ssh connections and management only so corresponding switch ports are not configured in trunk mode. enp3s0f0 and enp3s0f1 interfaces are bonded as bond1. Bond1 is for data and corresponding switch ports are configured in trunk mode. Bond0 is the default gateway for the server and has IP address 10.1.10.11 Bond1 has three subinterfaces with VLAN 4, 36, 41. IP addresses are 10.1.3.11, 10.1.35.11, 10.1.40.11 respectively. Proper communication with other servers on the network we should use routing tables. There are three