WAS _ cluster deployment application encountered ADMA0085E and adma00000w errors, adma0085eadma00000w

WAS _ cluster deployment application encountered ADMA0085E and adma00000w errors, adma0085eadma00000w

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

Recently, a was package deployment error occurs in the production environment.

 

When a normal package is deployed, the following error is reported:

It is easy to note that many configuration items are redundant as follows:

The error message is returned, but no specific solution is displayed.

Two problems are considered:

(1) issues with the package;

(2) WAS faults;

Therefore, in order to eliminate WAS faults, the WAS test package is deployed. The same error was reported during deployment. It is suspected that it is a WAS problem. Check the node service, node synchronization status, and web Service Status. Check that these configurations are correct.

Then the WAS service is restarted, and then the ear package is deployed again. The same error still occurs.

In desperation, I chose to restart the DM management server in the WAS cluster.

After the restart, a pleasant thing happened. The ear package is deployed successfully. A node is not synchronized, as shown below:

Despite this problem, it is much better than before.

So I checked the log and found that node 4 was not synchronized successfully.

Check node 4. Check that node agent is normal, node 4 is normal, and node 4 is normal. Therefore, the node agent of the node is manually disabled and then started manually after the service and synchronization are completed.

Check the startup status of the Deployment package again and find that node 4 has been synchronized and completed.

The task of deploying the package is completed. But why is there such an error? I have some doubts. I don't know what caused it?

After the package is deployed, check the application and find the problem: the application cannot be started and an http500 error is returned.

View the was log and obtain some log information as follows:

It is suspected that the package itself is faulty. Contact the developer. After some coordination and negotiation, it was found that there were some problems with the configuration file. There is a special configuration file for the program under the was cluster, and the newly hired developers are not aware of this, Khan. In the currently deployed package configuration file, I can see the following information in the program: "using the abstract class org. mybatis. spring. support. SqlSessionDaoSupport to provide SqlSession access to the database ". Then I checked the configuration file that should be applicable to the was cluster and found that there was connection configuration information based on the jndi of different users (I finally saw the familiar information ,.

So we re-package the package and deploy it on the was cluster without any problems.

 

Summary:

The essence of the unsuccessful deployment is that the ear package itself is faulty. Therefore, the following was errors cannot be identified by the was itself. This time I learned some experience, that is, the beginning of everything. For was program deployment, we must first confirm whether there is a problem with the package, and then expand, otherwise, it is very dangerous to try without any direction.

 

**************************************** * ** 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.