One of the learning processes = about the second log4j log management view = log4j background printing log view solve the problem

<! --
/* Font Definitions */
@ Font-face
{Font-family:;
Panose-1: 2 1 6 0 3 1 1 1 1 1;
MSO-font-alt: simsun;
MSO-font-charset: 134;
MSO-generic-font-family: auto;
MSO-font-pitch: variable;
MSO-font-Signature: 3 135135232 16 0 262145 0 ;}
@ Font-face
{Font-family: "/@ ";
Panose-1: 2 1 6 0 3 1 1 1 1 1;
MSO-font-charset: 134;
MSO-generic-font-family: auto;
MSO-font-pitch: variable;
MSO-font-Signature: 3 135135232 16 0 262145 0 ;}
/* Style definitions */
P. msonormal, Li. msonormal, Div. msonormal
{MSO-style-parent :"";
Margin: 0 cm;
Margin-bottom:. 0001pt;
Text-align: justify;
Text-justify: Inter-ideograph;
MSO-pagination: none;
Font-size: 10.5pt;
MSO-bidi-font-size: 12.0pt;
Font-family: "Times New Roman ";
MSO-Fareast-font-family:;
MSO-font-kerning: 1.0pt ;}
/* Page Definitions */
@ Page
{MSO-page-border-Surround-header: No;
MSO-page-border-Surround-footer: No ;}
@ Page Section1
{Size: 612.0pt 792.0pt;
Margin: 72.0pt 90.0pt 72.0pt 90.0pt;
MSO-header-margin: 361_pt;
MSO-footer-margin: 36366pt;
MSO-paper-Source: 0 ;}
Div. Section1
{Page: Section1 ;}
-->

Initializing

Composable

Request

Processor

For

Module

Prefix

''

Initialize

Action

Of

Type:

**. *. * Action

 

Exec

:

**.**()

Method.

In fact, it has nothing to do with it. Here I am not adding log processing. So all the data in the background is printed,

 

I checked the network for a while. However, I am confused about my own situation. I can't help it, but I only need to troubleshoot it myself. What to say

DWR

Question: What package is not introduced? These are all correct.

Web. xml

No log processing is added.

 

Because this project was redone after the last problem, it was not long for me to come here, so I did not participate in it, but many people have gone through it. Of course, I only need to make modifications. This is the problem of the data connection pool. This is really difficult to grasp, so let's talk about it. "As long as money can solve the problem, it is not a problem. As long as there is an "Explicit problem, it is not a problem", a lot of errors are reported in the background, and you know how to solve them. If everything is good, the program runs abnormally, the database cannot be seen, and no error is reported in the background, but there is a problem accessing the page. What should I do? I think it is really hard for everyone to solve this problem.

 

But the final self-check

Web. xml

Why is there no log management component during configuration? I think so. Add

<! -- Log4j -->

<

Listener

>

<

Listener-class

>

Org

. Springframework

. Web. util

. Log4jconfiglistener

</

Listener-class

>

</

Listener

>

<

Context-Param

>

<

Param-name

>

Log4jconfiglocation

</

Param-name

>

<

Param-Value

>

// WEB-INF/log4j. Properties

</

Param-Value

>

</

Context-Param

>

The problem is fixed. Directly speechless.

 

This problem occurs for a long time to deal with a lot of problems printed in the background, because there is a timely alarm information that requires constant access to the background page, so there will be such a problem. As long as the interaction with the background occurs, the print will appear. Why? Think about it now, that is, there is no filtering. What is used for filtering? You can write or use others. There is always something to block, so ah ,...