Вы находитесь на странице: 1из 3

===================================

WLS Basic Feature Usage Measurement


===================================
9/7/18 6:07 PM
===========
Domain Info
===========
Checking for administration port enabled:
Checking for service migration:
No errors detected
============
Cluster Info
============
Checking cluster type and overload actions:
Feature usage measurement error: Cluster cluster_reports has an incorrect overload
protection panic action: system-exit
Feature usage measurement error: Cluster cluster_forms has an incorrect overload
protection panic action: system-exit
WebLogic Server has features for detecting, avoiding, and recovering from overload
conditions. WebLogic Server's overload protection features help prevent the
negative consequences - degraded application performance and stability - that can
result from continuing to accept requests when the system capacity is reached.
In the license for WebLogic Server Basic, the configuration of any overload
protection scheme at either a cluster or server level is not permitted.
See the documentation:
http://download.oracle.com/docs/cd/E12839_01/web.1111/e13701/overload.htm
2 error(s) detected
===========
Server Info
===========
Checking server mode and overload actions:
Feature usage measurement error: Server TEST_FORMS1 has an incorrect overload
protection panic action: system-exit
Feature usage measurement error: Server TEST_REPORTS1 has an incorrect overload
protection panic action: system-exit
Feature usage measurement error: Server TEST_REPORTS2 has an incorrect overload
protection panic action: system-exit
Feature usage measurement error: Server TEST_FORMS2 has an incorrect overload
protection panic action: system-exit
Feature usage measurement error: Server TEST_FORMS3 has an incorrect overload
protection panic action: system-exit
Feature usage measurement error: Server TEST_REPORTS3 has an incorrect overload
protection panic action: system-exit
Feature usage measurement error: Server AdminServer has an incorrect overload
protection panic action: system-exit
WebLogic Server has features for detecting, avoiding, and recovering from overload
conditions. WebLogic Server's overload protection features help prevent the
negative consequences - degraded application performance and stability - that can
result from continuing to accept requests when the system capacity is reached.
In the license for WebLogic Server Basic, the configuration of any overload
protection scheme at either a cluster or server level is not permitted.
See the documentation:
http://download.oracle.com/docs/cd/E12839_01/web.1111/e13701/overload.htm
7 error(s) detected
======================
Singleton Service Info
======================
Checking for singleton services:
No errors detected
======================
Service Migration Info
======================
Checking for service migration:
No errors detected
========================
Global Work Manager Info
========================
Checking for global Work Managers:
No errors detected
=============================
Application Work Manager Info
=============================
Checking for application-scoped Work Managers:
No errors detected
===============
Deployment Info
===============
Checking for application versioning and ordering:
Feature usage measurement error: Application fads version 1.0 uses version 1.0
Feature usage measurement error: Application fads-ui version 1.0 uses version 1.0
Production redeployment strategy involves deploying a new version of an updated
application alongside an older version of the same application. WebLogic Server
automatically manages client connections so that only new client requests are
directed to the new version. Clients already connected to the application during
the redeployment continue to use the older version of the application until they
complete their work, at which point WebLogic Server automatically retires the older
application. This capability is supported by deploying the application in
Administration mode, which makes it available only via a configured Administration
channel.
In the license for WebLogic Server Basic, deploying any application that uses a
version identifier is not permitted.
See the documentation:
http://download.oracle.com/docs/cd/E12839_01/web.1111/e13702/redeploy.htm#DEPGD281
2 error(s) detected
=========================
Application FastSwap Info
=========================
Checking whether FastSwap is enabled in an application:
No errors detected
========
JMS Info
========
Checking for non-default Unit-of-Work Message Handling Policy:
Checking for non-default Message Unit-of-Order:
Checking for Message Store-and-Forward agents:
No errors detected
=====================
Tuxedo Connector Info
=====================
Checking for WebLogic Tuxedo Connectors:
No errors detected
=========
SNMP Info
=========
Checking for SNMP agents:
No errors detected
=====================
Application Mode Info
=====================
Checking for application in Administration mode:
No errors detected
======================
Module Deployment Info
======================
Checking for deployment of standalone JMS, JDBC, or WLDF modules:
No errors detected
===========================
HTTP Publish-Subscribe Info
===========================
Checking for HTTP Publish-Subscribe Server usage:
No errors detected
==========================
Diagnostics Framework Info
==========================
Checking for WebLogic Diagnostics Framework usage:
No errors detected
===============================
Active GridLink DataSource Info
===============================
Checking for Active GridLink DataSource usage:
No errors detected
=======
Summary
=======
11 error(s) detected

Вам также может понравиться