The JMX1.0 catalog contains messages in the range
BEA149500 - BEA149999. Messages in this catalog are part of the
weblogic.management.jmx
Internationalization package and the weblogic.management.jmx Localization package.
|
BEA-149500
|
Error: An exception occurred while registering the MBean mbean.
|
Description
| An exception occurred while registering the MBean mbean : The error is t. The result is that this specific managed object will not be visible through the MBeanServer |
|
Cause
| Refer to the embedded exception information for more details as to the probable cause of this error. |
|
Action
| This is an internal error and should be reported as a bug to Oracle |
|
|
BEA-149501
|
Error: An exception occurred while registering the MBean mbean at property propertyName.
|
Description
| An exception occurred while registering the MBean mbean at property propertyName: The error is t. The result is that this specific managed object will not be visible through the MBeanServer |
|
Cause
| Refer to the embedded exception information for more details as to the probable cause of this error. |
|
Action
| This is an internal error and should be reported as a bug to Oracle |
|
|
BEA-149502
|
Error: An exception occurred while unregistering the MBean mbean.
|
Description
| An exception occurred while unregistering the MBean mbean : The error is t. The result is that this now invalid managed object will remain visible through the MBeanServer |
|
Cause
| Refer to the embedded exception information for more details as to the probable cause of this error. |
|
Action
| This is an internal error and should be reported as a bug to Oracle |
|
|
BEA-149503
|
Error: An exception occurred while unregistering the MBean mbean at property propertyName.
|
Description
| An exception occurred while unregistering the MBean mbean at property propertyName: The error is t. The result is that this now invalid managed object will remain visible through the MBeanServer |
|
Cause
| Refer to the embedded exception information for more details as to the probable cause of this error. |
|
Action
| This is an internal error and should be reported as a bug to Oracle |
|
|
BEA-149504
|
Warning: The adminstration server was unable to establish JMX Connectivity with the managedServer at the JMX Service URL of serviceURL.
|
Description
| An unexpected exception occurred when contacting the managed server managedServer with the JMX Service URL serviceURL. The exception was t and indicates that the managed server cannot be contacted at host and port for which it is configured. |
|
Cause
| This is likely due to a misconfiguration of the configuration of the managed server. Often this is associated with the use of the Adminstration channel. |
|
Action
| Assure that the managed server adminstration ports are properly configured. It may be helpful to review the documentation on the configuration of the Administration channel. |
|
|
BEA-149505
|
Info: The administration server was unable to establish JMX Connectivity with the managedServer at the JMX Service URL of serviceURL.
|
Description
| An unexpected exception occurred when contacting the managed server managedServer with the JMX Service URL serviceURL. This indicates that the managed server cannot be contacted at host and port for which it is configured. |
|
Cause
| This is likely because the managed server is simply not running . It may indicated that the adminstration channels are not properly configured. |
|
Action
| Assure that the managed server adminstration ports are properly configured. It may be helpful to review the documentation on the configuration of the Administration channel. |
|
|
BEA-149506
|
Info: Established JMX Connectivity with managedServer at the JMX Service URL of serviceURL.
|
Description
| During normal operations the adminstration server made a JMX connection with a newly started managed server. |
|
Cause
| Normal operations. |
|
Action
| None action required |
|
|
BEA-149507
|
Info: JMX Connectivity has been discontinued with the managed server managedServer.
|
Description
| The managed server managedServer is no longer available for JMX connectivity. |
|
Cause
| This message is logged whenever a managed server is shutdown. |
|
Action
| No action required |
|
|
BEA-149508
|
Warning: Unable to establish JMX Connectivity with the Adminstration Server.
|
Description
| This managed server was unable to establish a JMX Connection with the administration server due to the exception t. |
|
Cause
| This may because the adminstration server is not currently available or may indicate a misconfiguration of the configuration of the adminstrative channels. |
|
Action
| If the adminstration sever is currently running the administrator should consult the documentation on the configuration of the Administration channel. |
|
|
BEA-149509
|
Warning: Unable to establish JMX Connectivity with the Adminstration Server adminServer at adminURL.
|
Description
| This managed server was unable to establish a JMX Connection with the administration server adminServer at the JMX Service URL adminURL due to the exception t. |
|
Cause
| This may because the adminstration server is not currently available or may indicate a misconfiguration of the configuration of the adminstrative channels. |
|
Action
| If the adminstration sever is currently running the administrator should consult the documentation on the configuration of the Administration channel. |
|
|
BEA-149510
|
Warning: Unable to establish JMX Connectivity with the Adminstration Server adminServer at adminURL.
|
Description
| This managed server was unable to establish a JMX Connection with the administration server adminServer at the JMX Service URL adminURL. |
|
Cause
| This may because the adminstration server is not currently available or may indicate a misconfiguration of the configuration of the adminstrative channels. |
|
Action
| If the adminstration sever is currently running the administrator should consult the documentation on the configuration of the Administration channel. |
|
|
BEA-149511
|
Info: Established JMX Connectivity with the Adminstration Server adminServer at adminURL.
|
Description
| This managed server established a JMX Connection with the administration server adminServer at the JMX Service URL adminURL. |
|
Cause
| Normal operations. |
|
Action
| No action required. |
|
|
BEA-149512
|
Info: JMX Connector Server started at serviceURL .
|
Description
| The Management Subsystem has made JMX Connectivity available at the URI serviceURL. |
|
Cause
| Normal operations. |
|
Action
| No action required. |
|
|
BEA-149513
|
Info: JMX Connector Server stopped at serviceURL .
|
Description
| The Management Subsystem has discontinued JMX Connectivity at the URI serviceURL. |
|
Cause
| Normal operations. |
|
Action
| No action required. |
|
|
BEA-149514
|
Debug: An error was encountered while attempting to generate an AttributeChangeNotification for MBean objectName on the attribute attributeName
|
Description
| The attribute attributeName was change for the mbean objectName and the JMX subsystem was unable to acquire the information needed to generate an AttributeChangeNotification. |
|
Cause
| This problem is the result of an internal error in the WLS JMX implementation. |
|
Action
| Report this message to Oracle support. |
|
|
BEA-149515
|
Warning: An error was encountered getting the attribute attributeName on the MBean objectName during a call to getAttributes
|
Description
| The JMX specification does not allow for generating an exception during a getAttributes call and requires that all of the available attributes are returned. In this case the attribute attributeName on the MBean objectName could not be acquired. |
|
Cause
| This problem is the result of an internal error in the WLS JMX implementation. |
|
Action
| Report this message to Oracle support. |
|
|
BEA-149516
|
Warning: An error was encountered setting the attribute attributeName on the MBean objectName during a call to setAttributes
|
Description
| The JMX specification does not allow for generating an exception during a setAttributes call and requires that all of the available attributes are returned. In this case the attribute attributeName on the MBean objectName could not be set. |
|
Cause
| This problem is the result of an internal error in the WLS JMX implementation. |
|
Action
| Report this message to Oracle support. |
|
|
BEA-149517
|
Warning: An attempt was made to unregister an mbean that was already unregistered: beanToString
|
Description
| The bean beanToString was not registered yet the WLS JMX implementation attempted to unregister it. |
|
Cause
| This problem is the result of an internal error in the WLS JMX implementation. |
|
Action
| Report this message to Oracle support. |
|
|
BEA-149518
|
Warning: An attempt was made to unregister the objectNameString WLS MBean through JMX.
|
Description
| MBeans that are in the com.bea domain are controlled internally by the WLS implementation and cannot be unregistered through the JMX API directly. |
|
Cause
| Using the JMX API to unregister a WLS MBean. |
|
Action
| Use the WLS APIs to control the configuration of the server environment. |
|
|
BEA-149519
|
Info: The JMX Service URL serviceURL for managed server managedServer was malformed.
|
Description
| An unexpected exception occurred when contacting the managed server managedServer with the JMX Service URL serviceURL. The URL used to contact the managed server was malformed. |
|
Cause
| The URL used to contact a managed server was malformed. |
|
Action
| See the exception included with this message to determine proper action. |
|
|
BEA-149520
|
Error: An attempt was made to Register an MBean with ObjectName objectNameString ObjectName in com.bea domain.
|
Description
| com.bea domain name is reserved for WLS MBeans with WLS Server. |
|
Cause
| Attempt to register an MBean with com.bea domain name |
|
Action
| Register your MBeans with some other domain name. |
|
|
BEA-149521
|
Warning: An exception occurred during the processing of JMX Connectivity with the Adminstration Server: t
|
Description
| During the connect or disconnect of a managed server, an exception t occured in the Administration Server during JMX processing of the connect or disconnect event. |
|
Cause
| Refer to the embedded exception information for more details as to the probable cause of this error. |
|
Action
| Refer to the embedded exception information for more details and troubleshoot based on that information. |
|
