Was system error logs contain a large number of missing identifiers and was

Was system error logs contain a large number of missing identifiers and was

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

 

Recently, when I checked was logs for a resident engineer, I found a large number of missing identifiers.

 

Location of was logs:

Logs	All types of log files, such as SystemOut. log, tranlog, FFDC, and activity. log. The path is under/logs/server.

Was System Log:

The WebSphere Application Server logging infrastructure is based on the standard Java logging infrastructure (java. util. logging. In a typical WebSphere Application Server configuration, the logging is set to write common and severe log messages into two files, namely, SystemOut. log and SystemErr. log.

In addition to system logs, there are also native logs, as shown below:

However, these two logs are different from system logs. These two files are actually processed by the JVM itself. They only contain messages related to the JVM operation, but not messages from the WebSphere Application Server Runtime.

 

A large number of errors of the following types are found in logs:

I asked a developer about the returned XML format and missing the end identifier.

After reading the lengthy log information, we found that a large number of errors are in this category: the end ID is missing.

Feed back the information to the resident staff. We suggest you contact the system development engineer to check whether the code is correct.

 

In addition, after communicating with the resident engineer, we found that the reason for viewing the log WAS that WAS would be stuck in the system for no reason. Later, he reduced the initial stack and the system was running normally.

Finally, we suggest him observe for several days to see if the stack size can meet the requirements. There may be memory overflow, but the log does not capture information such as systemout, so you still need to observe. For incorrect identifiers, contact developers as soon as possible.

 

I suddenly thought of something interesting. Here I want to mention the memory overflow problem, which is common in java development programs. Because of the code quality, some objects are often occupied and not released. Just like in a room, a class is used to put people in the room, and the code mechanism is faulty. new comes out of a dark blue, and then the function repeats new in a dark blue, and then keep new and dark blue. All the time, the whole house was filled with the same dark blue. In fact, we only need a dark blue, and the room is filled with dark blue, and a dark blue is squeezed out of the window. This causes memory overflow.

For classes in the object orientation, it is like a table in the database, and the object is like a piece of data in the table. When we use an object, we pass parameters to the class.

Appendix:

The following sections of was log information:

 

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

FaultSubcode:

FaultString: Error on line 1: The element type "project name category" must be terminated with the matched end tag "& lt;/project name category & gt.

FaultActor:

FaultNode:

FaultDetail:

{Http://xml.apache.org/axis/?stacktrace:error on line 1: The element type "project name category" must be ended with a matched end tag "& lt;/project name category & gt.

 

 

 

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

 

[15-7-8 21: 00: 00: 268 CST] 00000039 SystemErr Error on line 1: the element type "project name category" must be terminated with the matched end tag "</project name Category>.

 

 

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

FaultSubcode:

FaultString: Error on line 1: The element type "project Associated Person" must be followed by the attribute specification "& gt;" or "/& gt ;".

FaultActor:

FaultNode:

FaultDetail:

{Http://xml.apache.org/axis/?stacktrace:error on line 1: The element type "project Associated Person" must be followed by the attribute specification "& gt;" or "/& gt ;".

 

 

**************************************** * ** Blue growth series ********************************* *******************

Original works, from the blog of "Deep Blue". You are welcome to reprint them. Please indicate the source (Http://blog.csdn.net/huangyanlong).

Blue growth note-chasing DBA (1): traveling on the road to Shandong

Blue growth notes-Chase DBA (2): Install! Install! Long-lost memories have aroused my new awareness of DBAs.

Blue growth note-chasing DBA (3): importing and exporting data on antiques becomes a problem

Blue growth note-chasing DBA (4): recalling the sorrow of teenagers, and exploring oracle Installation (10g and 11g in Linux)

Blue growth note-chasing DBA (5): Not talking about technology or business, annoying Application Systems

Blue growth note-chasing DBA (6): doing things and being human: Small technology, great human

Blue growth note-Chase DBA (7): Basic commands, foundation stone

Blue growth notes-chasing DBA (8): repicking SP reports and recalling oracle's STATSPACK Experiment

Blue growth note-chasing DBA (9): Chasing DBA, new planning, new departure

Blue growth note-chasing DBA (10): Flying knife defense, familiarity rather than expertise: Playing with middleware Websphere

Blue growth note-chasing DBA (11): It's easy to go home and wake up.

Blue growth notes-Chase DBA (12): seven days and seven gains of SQL

Blue growth note-chasing DBA (13): Coordinating hardware manufacturers, six stories: what you see as "servers, storage, switches ......"

Blue growth note-chasing DBA (14): An unforgettable "Cloud" end, started hadoop deployment

Blue growth note-chasing DBA (15): Who thinks FTP is "simple" and thinks it is a trigger

Blue growth note-chasing DBA (16): DBA also drank alcohol and was rejected

Blue growth note-Chase DBA (17): whether to share or consume, learn to grow in the Post-IOE Era

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

 

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

Original works, from the blog of "Deep Blue". You are welcome to reprint them. Please indicate the source (Http://blog.csdn.net/huangyanlong).

Football and oracle series (1): 32-way zhoudianbing, overall view of group A Brazil smon process of oracle32 process Alliance

Football and oracle series (2)

Football and oracle series (3): oracle process rankings, the World Cup round is about to fight!

Football and oracle series (4): from Brazil to Germany, think of the different RAC topology comparison! 

Football and oracle series (5): The directX library missing in the voda14 game is similar to the oracle rpm package!

Football and oracle series (6): Asian Cup with database creation-come on, Chinese Team

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

Copyright Disclaimer: This article is an original article by the blogger and cannot be reproduced without the permission of the blogger.