was system error log large number of occurrences of identifier missing

Original works, from "Deep Blue Blog" blog, dark blue blog:http://blog.csdn.net/huangyanlong/article/ details/46909941

Recently, a large number of missing identifiers were found incorrectly when viewing the was log for a resident engineer.

was log location:

Logs	all types of log files, such as SystemOut.log , Tranlog , FFDC , Activity.log and so on. Path in /logs/server*/ below.

was system log:

The WebSphere application Server logging infrastructure is built on a standard Java -based logging infrastructure (that is, java.util.logging). In a typical WebSphere application Server configuration, logging is set to write normal and critical log messages to two files, namely SystemOut.log and SystemErr.log.

In addition to the system log, there are native logs, as follows:

However, these two logs are different from the system log. These two files are actually handled by the JVM itself and contain only messages related to the operation of the JVM , not from the WebSphere application Server runtime.

A large number of types of errors are found in the log:

With the development of friends around the simple consult, said that this is the return of the XML format is not, the end of the identity is missing.

So after looking through the lengthy log messages, we find that a lot of errors are in this category: Missing end tags.

Feedback to the resident personnel, advise them to contact the system development Engineer to see if there is a problem with the code.

In addition, after communicating with the resident engineer, it was found that the log was viewed due to the fact that was would have been improperly jammed by the previous system. He then changed the initial stack to small, and then the system was temporarily running normally.

Finally, it is recommended that he observe a few more days to see if the stack is small enough to meet demand. There may be a memory overflow phenomenon, but information such as Systemout is not captured in the log, so you still need to observe. For identifiers errors, you need to contact development review as soon as possible.

Suddenly came to the point of interesting, here want to mention a mouth memory overflow problem, common with Java Development program. Due to the quality of the code, it is often not released by object occupancy. It's like a house where a class is put into the house, and the code mechanism is problematic,new comes in a deep blue, and then functionally repeats new to a dark blue, and then keeps new out of the blue. All the way down, the whole house was full of the same dark blue. And in fact we only need a deep blue, and this room is full of deep blue, a deep blue from the window was squeezed out. This is a memory overflow.

For classes in object-oriented, like a table in a database, an object is like a piece of data in a table. When we use objects, we pass the arguments to the class.

Appendix:

The following part was log information:

FaultCode: {http://schemas.xmlsoap.org/soap/envelope/}server

Faultsubcode:

Faultstring:error on line 1: element type "project name category" must be matched with closing tag "</ project name category >" Terminate.

Faultactor:

Faultnode:

Faultdetail:

{http://xml.apache.org/axis/}stacktrace:error on line 1: element type ' project name category ' must be matched with closing tag '</ project name category C2>>" Terminate.

{Http://xml.apache.org/axis/}hostname:localhost.localdomain

[15-7-8 21:00:00:268 CST] 00000039 systemerr R Error on line 1: element type "project name category" must be matched with closing tag "</ project name category >"terminates.

FaultCode: {http://schemas.xmlsoap.org/soap/envelope/}server

Faultsubcode:

Faultstring:error on line 1: the element type "project is associated" must immediately follow the property specification "&gt;" or "/&gt;".

Faultactor:

Faultnode:

Faultdetail:

{http://xml.apache.org/axis/}stacktrace:error on line 1: element type ' project is associated ' must be followed by property specification '&gt;' or "/&gt;".

The Blue Growth Kee series ****************************************************

original works, from the "Blue Blog" blog, Welcome to reprint, please be sure to indicate the source ( Http://blog.csdn.net/huangyanlong ).

The growth of Blue-chase DBA (1): Rushing to the road and into Shandong

Blue Growth Kee-Chase DBA (2): Install! Installation! A long-lost memory that caused me to re-perceive the DBA

The growth of Blue-Chase DBA (3): antique operation, data import and export become a problem

The growth of Blue-Chase DBA (4): Recalling the youth, and then explore Oracle installation (Linux 10g, 11g)

The growth of Blue-Chase DBA (5): No talking about business, annoying application system

The growth of Blue-Chase DBA (6): Work and life: small skills, great people

The growth of Blue-Chase DBA (7): Basic Command, foundation stone

The growth of Blue-chase DBA (8): Regain SP report, recall Oracle's Statspack experiment

The growth of Blue-Chase DBA (9): National Day, chasing DBA, new plan, new departure

The growth of the Blue-Chase DBA (10): flying knives to defend themselves, not expertise: fiddling with middleware WebSphere

The growth of Blue-chase DBA (11): The ease of coming home, the dizzy wake up

The growth of Blue-chase DBA (12): Seven days seven harvested SQL

The growth of blue-chasing DBAs (13): Coordinating hardware vendors, six stories: what you see and feel "servers, storage, switches ..."

The growth of Blue-chase DBA (14): An unforgettable "cloud" side, starting Hadoop deployment

The growth of Blue-Chase DBA (15): Think FTP is very "simple", who chengxiang twists

The growth of Blue-Chase DBA: The DBA also drank and was 捭阖

The growth of blue-chasing DBAs (17): sharing, or spending, learning to grow in the post-IoE era

******************************************************************************************************* ***********

Soccer and Oracle Series *************************************************

original works, from the "Blue Blog" blog, Welcome to reprint, please be sure to indicate the source ( Http://blog.csdn.net/huangyanlong ).

Soccer and Oracle Series (1): 32 Way Princes soldiers of, Oracle32 Process Alliance Group A bigger picture of the Brazilian Smon process

Soccer and Oracle Series (2): Brazil opener Preview, Oracle architecture Talk

Soccer and Oracle Series (3): Oracle process ranking, World Cup round is about to be fought!

Soccer with Oracle Series (4): From Brazil fiasco in Germany, think of the difference in RAC topology comparison!  

Soccer and Oracle Series (5): Fifa14 game The missing DirectX Library is analogous to the RPM package from Oracle!

Soccer and Oracle Series (6): The Asian Cup with the library--Refueling Chinese team

****************************************************************************************************** ************

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

was system error log large number of occurrences of identifier missing