|
|
|
|---|
JBIFW0003 |
Severe |
Unable to
initialize {0} due to an exception: {1}({2}). Stack trace follows. Cause: A required runtime service
failed to initialize. The service name, exception name, and exception message are provided,
and a stack trace is also logged. Action: Try restarting the runtime. If this
fails to solve the problem, contact Oracle for support. |
JBIFW0004 |
Severe |
JBI framework initialization failed;
one or more services failed to initialize. Cause: Some runtime services failed to
initialize. Action: See the preceding JBIFW0003 message(s) for further details. |
JBIFW0010 |
INFO |
JBI framework ready to
accept requests. Cause: The JBI runtime has initialized and can accept requests
from admin clients. At this point, no components or Service Assemblies have been
started. Action: None required, informational message only. |
JBIFW0012 |
INFO |
JBI framework startup complete. Cause: The
JBI runtime has started and all components and Service Assemblies have been brought to
their previous states. Action: None required, informational message only. |
JBIFW0013 |
SEVERE |
Unable to start {0} due
to an exception: {1} ({2}). Stack trace follows. Cause: A required runtime service
failed to start. The service name, exception class, and exception message are provided,
and a stack trace is also logged. Action: Try restarting the runtime. If
this fails to solve the problem, contact Oracle for support. |
JBIFW0014 |
SEVERE |
JBI framework startup
failed; one or more services failed to start. Cause: Some runtime services failed
to start. Action: See the preceding JBIFW0013 message(s) for further details. |
JBIFW0033 |
SEVERE |
Unable to stop
{0} due to an exception: {1} ({2}). Stack trace follows. Cause: A
runtime service failed to stop. The service name, exception class, and exception message are
provided, and a stack trace is also logged. Action: If this problem
occurs consistently, contact Oracle for support. |
JBIFW0034 |
WARNING |
JBI framework shutdown had errors; one or more
services failed to stop successfully. Cause: Some runtime services failed to stop. Action:
See the preceding JBIFW0033 message(s) for further details. |
JBIFW0042 |
INFO |
JBI framework termination complete. Cause:
The JBI runtime has successfully terminated. Action: None required, informational message only. |
JBIFW0053 |
WARNING |
{0} already initialized.
Cause: An attempt was made to initialize a runtime service that was
already initialized. Action: This is an internal error that should not occur. Report
this error to Oracle. |
JBIFW0054 |
WARNING |
{0} already started. Cause: An attempt was made to
start a runtime service that was already started. Action: This is an
internal error that should not occur. Report this error to Oracle. |
JBIFW0055 |
WARNING |
{0} already stopped.
Cause: An attempt was made to stop a runtime service that was
already stopped. Action: This is an internal error that should not occur. Report
this error to Oracle. |
JBIFW0060 |
SEVERE |
Internal error: Empty list argument received for {0}.
Cause: An List argument to an internal method call was empty when a
non-empty List is required. Action: This is an internal error that should not
occur. Report this error to Oracle. |
JBIFW0061 |
SEVERE |
Internal error: Empty string argument received for
{0}. Cause: A String argument to an internal method call was empty
when a non-empty String is required. Action: This is an internal error that
should not occur. Report this error to Oracle. |
JBIFW0062 |
SEVERE |
Internal error: Invalid argument received
for {0}; the value {1} is unrecognized. Cause: The value of an
argument to an internal method call was invalid. Action: This is an internal error
that should not occur. Report this error to Oracle. |
JBIFW0063 |
SEVERE |
Null argument received for
{0}. Cause: An argument to an internal method call was null when
a non-null value is required. Action: This is an internal error that should
not occur. Report this error to Oracle. |
JBIFW0102 |
WARNING |
Implementation of javax.transaction.TransactionManager not found. Lookup failed
with {0}, stack trace follows. Cause: An exception occurred while the runtime
was looking up the implementation of the Java Transaction Manager. Action: The stack
trace following this message should pinpoint the problem. This is usually an environmental or
configuration problem. |
JBIFW0103 |
WARNING |
Unable to create a LoggerMBean for the framework logger. No JMX control
of the framework logger will be available. Cause: The runtime was
unable to create an MBean for controlling the framework logger. This could be due
to a temporary JMX issue. Action: There should be a message logged before
this message that provides the exact cause of the problem. If you cannot
correct the problem, contact Oracle for support. |
JBIFW0104 |
WARNING |
invalid log level {0} specified. Using default
log level {1}. Cause: The log level specified was not a valid level.
The default value is being used instead. Action: Correct the log level in
your properties settings for the JBI runtime. |
JBIFW0105 |
WARNING |
Unable to create the event notifier
MBean for the framework. No runtime event notifications will be available. Cause:
The runtime was unable to create an MBean for generating event notifications. Without
this MBean, no event notifications can be emitted by the runtime. Action: There
should be a message logged before this message that provides the exact cause
of the problem. If you cannot correct the problem, contact Oracle for support. |
JBIFW0106 |
WARNING |
Cannot obtain
classloader for component {0}, using default classloader for loading resource bundle for package
{1}. The error is: {2} Cause: There was a problem obtaining the
class loader for the named component when attempting to load the resource bundle
for the component. The default runtime class loader will be used to load
the resource bundle. Action: There should be further diagnostic messages logged after this
one that will pinpoint the cause of the problem. |
JBIFW0109 |
WARNING |
Failed to create MBean due
to an exception: {0}. Cause: An MBean could not be created by
the runtime. This message is accompanied by a message that specifies which MBean
was being processed. Action: The exception logged should show exactly what the problem
is. If the problem persists, contact Oracle for support. |
JBIFW0110 |
WARNING |
Failed to create MBean ObjectName
for {0}, {1}. Cause: An MBean name could not be created by
the runtime. This message is accompanied by a message that specifies which MBean
was being processed. Action: The exception logged should show exactly what the problem
is. If the problem persists, contact Oracle for support. |
JBIFW0111 |
WARNING |
Failed to register MBean due
to an exception: {0}. Cause: An MBean could not be registered by
the runtime. This message is accompanied by a message that specifies which MBean
was being processed. Action: The exception logged should show exactly what the problem
is. If the problem persists, contact Oracle for support. |
JBIFW0115 |
WARNING |
Failure unregistering framework MBean: {0},
due to a {1}. Cause: An MBean could not be unregistered by
the runtime. This message is accompanied by a message that specifies which MBean
was being processed. Action: The exception logged should show exactly what the problem
is. If the problem persists, contact Oracle for support. |
JBIFW0116 |
WARNING |
Unable to create a Statistics
MBean for the framework. No JMX access to the framework statistics will be
available. Cause: The statistics MBean for the framework could not be created.
This message is accompanied by a message that provides details about the failure.
Action: The accompanying message should show exactly what the problem is. If the
problem persists, contact Oracle for support. |
JBIFW0117 |
WARNING |
Failed to initialize the jbi registry. {0}.
Cause: The JBI registry failed to initialize properly. The exact cause is provided
in the message. Action: If the cause is an I/O error or a
corrupted file, try restarting. If the problem persists it could be a disk
problem. |
JBIFW0200 |
WARNING |
Could not create bootstrap classloader due to an exception: {0} Cause: The
bootstrap class loader for the component could not be created. The exception in
the message provides the exact reason. Action: Usually this is due to an incorrectly
packaged component. If this is occurring with a user-written component, make sure that
the bootstrap-class-path entries in jbi.xml are correct. Otherwise, contact Oracle for support. |
JBIFW0201 |
WARNING |
Could not
create component classloader due to an exception: {0} Cause: The component/life cycle class
loader for the component could not be created. The exception in the message
provides the exact reason. Action: Usually this is due to an incorrectly packaged
component. If this is occurring with a user-written component, make sure that the
component-class-path entries in jbi.xml are correct. Otherwise, contact Oracle for support. |
JBIFW0202 |
WARNING |
No component classloader
found for {0}. Cause: A request for a component class loader failed
to locate the class loader for the specified component. Action: This is
an internal error that should not occur. contact Oracle for support. |
JBIFW0204 |
WARNING |
No shared classloader
found for {0}. Cause: A request for a shared library class loader
failed to locate the class loader for the specified shared library. Action: This
is an internal error that should not occur. contact Oracle for support. |
JBIFW0205 |
WARNING |
Could not
create shared classloader due to an exception: {0} Cause: An exception occurred while
creating the class loader for a shared library. The exception in the message
provides the exact reason. Action: Usually this is due to an incorrectly packaged
shared library. If this is occurring with a user-written shared library, make sure
that the shared-library-class-path entries in jbi.xml are correct. Otherwise, contact Oracle for support. |
JBIFW1002 |
WARNING |
The
timed wait for components to stop was interrupted. Shutdown continuing without stopping components.
Cause: During a shutdown of the runtime, one or more components failed
to stop before the timeout period specified by the componentTimeout runtime configuration parameter expired.
Action: Try increasing the time interval specified by the componentTimeout runtime configuration parameter, or
specifying a value of 0 for no timeout. The presence of a large
number of deployed Service Assemblies can cause the stopping of a component to
take more time. If the component fails to stop even with the timeout
value set to 0, there may be a problem with the component. |
JBIFW1003 |
WARNING |
The
timed wait for components to start was interrupted. Some components may not be
started. Cause: During a startup of the runtime, one or more components
failed to start before the timeout period specified by the componentTimeout runtime configuration
parameter expired. Action: Try increasing the time interval specified by the componentTimeout runtime configuration parameter,
or specifying a value of 0 for no timeout. The presence of a
large number of deployed Service Assemblies can cause the startup of a component
to take more time. If the component fails to start even with the
timeout value set to 0, there may be a problem with the component. |
JBIFW1011 |
WARNING |
Component
{0} has an unrecognized type {1} and has been ignored. Cause: An
invalid component type was encountered while processing a request. Action: This is an
internal error that should not occur. contact Oracle for support. |
JBIFW1012 |
WARNING |
The requested component {0}
was not found. Cause: A request for an extension MBean name for
the component failed because the component is not registered. Action: This is
an internal error that should not occur. contact Oracle for support. |
JBIFW1106 |
INFO |
{0} {1} has
been installed. Cause: The specified component has been successfully installed into the
runtime. Action: None required, informational message only. |
JBIFW1107 |
WARNING |
Installation of {0} {1} failed. Root Cause:
Installation of the specified component failed. One of the explanations below will be appended
to this message. It has already been installed. Cause: This component is already installed. Action:
If you are trying to update the component, you should use the asadmin
upgrade-jbi-component command, the ant jbi-upgrade-component task, the admin console upgrade component action, or the
NetBeans IDE upgrade component action. |
|
|
A(n) {0} with the same name is already
registered. Cause: Another component with the same name is already installed. For
example, if you are trying to install a binding component by this name,
and there is already a service engine installed by this name, you will
encounter this error. Action: Only one component by any name can be installed.
Change the name of the component so that there are no name conflicts. |
|
|
It
has not yet been loaded. Cause: This error cannot occur with any of
the admin clients (asadmin, ant, admin console, NetBeans IDE). It can occur only
when using the JMX interface directly to install a component, and the loadNewInstaller
operation has not been invoked prior to invoking the install operation. Action: Change
the JMX client to invoke the loadNewInstaller operation first, or use one of
the standard admin clients instead. |
|
|
The bootstrap onInstall() method threw a {0} exception. The exception
message is: {1} Cause: The component's installation processing encountered an error. Action:
The exception class and the exception message should provide information about why the error
occurred. Correct the problem and retry the installation. |
|
|
The bootstrap init() method threw
a {0} exception. The exception message is: {1} Cause: The component's installer bootstrap failed
to initialize during an attempt to install the component. Action: The exception
class and the exception message should provide information about why the error occurred. Correct
the problem and retry the installation. |
|
|
The bootstrap implementation has not been loaded. Cause:
This error cannot occur with any of the admin clients (asadmin, ant, admin
console, NetBeans IDE). It can occur only when using the JMX interface directly to
install a component, and the loadNewInstaller operation has not been invoked prior to
invoking the install operation. Action: Change the JMX client to invoke the loadNewInstaller
operation first, or use one of the standard admin clients instead. |
|
|
The bootstrap getExtensionMBeanName()
method threw a {0} exception. The exception message is: {1} Cause: The component's
installer bootstrap failed on a request for its configuration MBean. Action: The exception
class and the exception message should provide information about why the error occurred. Correct
the problem and retry the installation. |
|
|
The bootstrap cleanUp() method threw a {0}
exception. The exception message is: {1} Cause: After some other failure, the component's
installer bootstrap cleanup failed. Action: Look for previous error messages about the installation failure
and correct those problems before retrying the installation. |
JBIFW1108 |
WARNING |
After installation of {0} {1}, the
bootstrap cleanUp() method threw a {2} exception. The exception message is: {3}
Cause: This is a failure during the cleanup processing in the component's installer
class. Action: The exception class and exception message should provide information about why
the error occurred. The component has already successfully completed its installation processing; this error
is just in the cleanup processing. Manual cleanup of any persistent resources created
by the installer class may be required, depending on the error. There is
no need to install the component again, as it was successfully installed. |
JBIFW1116 |
INFO |
{0} {1}
has been uninstalled. Cause: The named component has been uninstalled from the
system. Action: None required, informational message only. |
JBIFW1117 |
WARNING |
Uninstallation of {0} {1} failed. Root Cause:
Uninstallation of the specified component failed. One of the explanations below will be appended
to this message. It is not installed. Cause: There is no component installed by
this name. Action: Check to make sure that the component name is correct. |
|
|
There
is no {0} installed with this name. Cause: This error cannot occur
with any of the admin clients (asadmin, ant, admin console, NetBeans IDE). It
can occur only when using the JMX interface directly to uninstall a component,
and the loadInstaller operation has not been invoked prior to invoking the uninstall
operation. Action: Change the JMX client to invoke the loadInstaller operation first, or
use one of the standard admin clients instead. |
|
|
The {0} is still running; it
must be shut down before it can be uninstalled. Cause: The component
is still started. Action: Shut down the component before attempting to uninstall. A running
component cannot be uninstalled. |
|
|
The {0} is stopped; it must be shut down
before it can be uninstalled. Cause: The component is stopped, but not shut
down. Action: Shut down the component before attempting to uninstall. A stopped component
cannot be uninstalled, because it is still active. |
|
|
The bootstrap onUninstall() method threw a
{0} exception. The exception message is: {1} Cause: The component's uninstallation processing encountered
an error. Action: The exception class and the exception message should provide information
about why the error occurred. Correct the problem and retry the uninstallation. |
|
|
The bootstrap
init() method threw a {0} exception. The exception message is: {1} Cause:
The component's installer bootstrap failed to initialize during an attempt to uninstall the component.
Action: The exception class and the exception message should provide information about why
the error occurred. Correct the problem and retry the uninstallation. |
|
|
The bootstrap implementation has
not been loaded. Cause: This error cannot occur with any of the
admin clients (asadmin, ant, admin console, NetBeans IDE). It can occur only when
using the JMX interface directly to uninstall a component, and the loadInstaller operation
has not been invoked prior to invoking the uninstall operation. Action: Change the
JMX client to invoke the loadInstaller operation first, or use one of the
standard admin clients instead. |
|
|
The bootstrap getExtensionMBeanName() method threw a {0} exception. The exception message
is: {1} Cause: The component's installer bootstrap failed on a request for
its configuration MBean. Action: The exception class and the exception message should provide
information about why the error occurred. Correct the problem and retry the uninstallation. |
|
|
The
bootstrap cleanUp() method threw a {0} exception. The exception message is: {1}
Cause: After some other failure, the component's installer bootstrap cleanup failed. Action: Look
for previous error messages about the uninstallation failure and correct those problems before retrying
the uninstallation. |
JBIFW1118 |
WARNING |
Uninstallation of {0} {1} cannot proceed because the following Service Units are
still deployed: {2}. Cause: The specified component cannot be uninstalled because there
are still Service Units deployed to it. The names of the Service Units
are listed in the message. Action: Make sure that all Service Assemblies that
have Service Units targeted to this component have been undeployed, then retry the
operation. |
JBIFW1119 |
WARNING |
Required Shared Library {0} is not installed. Cause: This message is
logged during component installation when a Shared Library required by the component is not
installed. Action: Install the required Shared Library before attempting to install the component. |
JBIFW1120 |
WARNING |
The
{0} cannot be installed. The following Shared Libraries must be installed first: {1}.
Cause: The component requires the listed Shared Libraries to be installed before
the component can be installed. Action: Install the required Shared Libraries, then install the
component. |
JBIFW1121 |
WARNING |
After uninstallation of {0} {1}, the bootstrap cleanUp() method threw a {2} exception.
The exception message is: {3} Cause: A failure occurred during the cleanup
processing in the component's installer class. Action: The exception class and exception message
should provide information about why the error occurred. The component has already successfully
completed its uninstallation processing; this error is just in the cleanup processing. Manual
cleanup of any persistent resources created by the installer may be required. There is
no need to uninstall the component again, as it was successfully uninstalled. |
JBIFW1135 |
WARNING |
{0} {1}
cannot be initialized. The LifeCycle init() method threw a {2} exception. The exception
message is: {3} Cause: A failure occurred during the component's initialization. Action:
This is usually indicative of either an environmental issue or a bug in
the component itself . If an exception message is provided, it should provide
further information. If this is not a user-written component, contact Oracle for support. |
JBIFW1136 |
WARNING |
{0}
{1} cannot be initialized. The LifeCycle init() method threw a {2} exception.
Cause: A failure occurred during the component's initialization. Action: This is usually indicative of
either an environmental issue or a bug in the component itself. The component
did not provide an exception message. If this is not a user-written component
and the problem persists, contact Oracle for support. |
JBIFW1137 |
WARNING |
{0} {1} failed to complete its
initialization processing before the timeout interval ({2} milliseconds) expired. Cause: The time
used by the component for initialization exceeded the timeout interval. This can be due
to a hang in the component, or due to a large number
of deployments that may take a long time to initialize. Action: Ensure that
the timeout interval specified by the componentTimeout configuration parameter is sufficient. The value is
specified in milliseconds. |
JBIFW1146 |
INFO |
{0} {1} has been started. Cause: The component has successfully
started. Action: None required, informational message only. |
JBIFW1147 |
WARNING |
{0} {1} cannot be started. The LifeCycle
start() method threw a {2} exception. The exception message is: {3} Cause:
A failure occurred during the component's start processing. Action: This is usually indicative of
either an environmental issue or a bug in the component itself. If an
exception message is provided, it should provide further information. If this is not
a user-written component, contact Oracle for support. |
JBIFW1148 |
WARNING |
{0} {1} cannot be started. It
has been loaded but not installed. Cause: An attempt was made to start
a component that is in the process of being installed but the installation
is not yet complete. Action: Make sure that the component installation has completed
successfully before attempting to start it. |
JBIFW1149 |
WARNING |
{0} {1} cannot be started. The LifeCycle start()
method threw a {2} exception. Cause: A failure occurred during the component's start
processing. Action: This is usually indicative of either an environmental issue or a
bug in the component itself. The component did not provide an exception message.
If this is not a user-written component and the problem persists, contact Oracle for
support. |
JBIFW1150 |
WARNING |
The {0} cannot be started. The following Shared Libraries must be installed first:
{1}. Cause: An attempt was made to start a component that depends
on Shared Libraries that are not installed. Action: Make sure that all of the
required Shared Libraries listed in the error message have been installed before attempting
to start the component. |
JBIFW1151 |
WARNING |
{0} {1} failed to complete its start processing before
the timeout interval ({2} milliseconds) expired. Cause: The time used by the component
for startup exceeded the timeout interval. This can be due to a hang
in the component, or due to a large number of deployments that may
take a long time to start. Action: Ensure that the timeout interval specified
by the componentTimeout configuration parameter is sufficient. The value is specified in milliseconds. |
JBIFW1156 |
INFO |
{0}
{1} has been stopped. Cause: The component has successfully stopped. Action: None
required, informational message only. |
JBIFW1157 |
WARNING |
{0} {1} cannot be stopped. The LifeCycle stop() method threw a
{2} exception. The exception message is: {3} Cause: A failure occurred during
the component's stop processing. Action: This is usually indicative of either an environmental
issue or a bug in the component itself. If an exception message is
provided, it should provide further information. If this is not a user-written component
and the problem persists, contact Oracle for support. |
JBIFW1158 |
WARNING |
{0} {1} cannot be stopped. It
has been loaded but not installed. Cause: An attempt was made to stop
a component that is in the process of being installed but the installation
is not yet complete. Action: Make sure that the component installation has completed
successfully. A component can be stopped only when it is in the STARTED
state. |
JBIFW1159 |
WARNING |
{0} {1} cannot be stopped. The LifeCycle stop() method threw a {2} exception.
Cause: A failure occurred during the component's stop processing. Action: This is
usually indicative of either an environmental issue or a bug in the component
itself. The component did not provide an exception message. If this is not a
user-written component and the problem persists, contact Oracle for support. |
JBIFW1160 |
WARNING |
{0} {1} is not
active. Cause: An attempt was made to stop a component that is
not active. Action: A component can be stopped only when it is in
the STARTED state. |
JBIFW1166 |
INFO |
{0} {1} has been shut down. Cause: The component
has successfully shut down. Action: None required, informational message only. |
JBIFW1167 |
WARNING |
{0} {1} cannot be shut
down. The LifeCycle shutDown() method threw a {2} exception. The exception message is:
{3} Cause: A failure occurred during the component's shutdown processing. Action: This
is usually indicative of either an environmental issue or a bug in the
component itself. The component did not provide an exception message. If this is
not a user-written component and the problem persists, contact Oracle for support. |
JBIFW1168 |
WARNING |
{0} {1} cannot
be shut down. It has been loaded but not installed. Cause: An
attempt was made to shut down a component that is in the process
of being installed but the installation is not yet complete. Action: Make sure
that the component installation has completed successfully. A component can be shut down only
when it is in the STARTED or STOPPED state. |
JBIFW1169 |
WARNING |
{0} {1} cannot be
shut down. The LifeCycle shutDown() method threw a {2} exception. Cause: A
failure occurred during the component's shutdown processing. Action: This is usually indicative of either
an environmental issue or a bug in the component itself. The component did
not provide an exception message. If this is not a user-written component and
the problem persists, contact Oracle for support. |
JBIFW1170 |
WARNING |
{0} {1} failed to complete its shutdown
processing before the timeout interval ({2} milliseconds) expired. Cause: The time used
by the component for shutdown exceeded the timeout interval. This can be due to
a hang in the component, or due to a large number of
deployments that may take a long time to shut down. Action: Ensure that
the timeout interval specified by the componentTimeout configuration parameter is sufficient. The value is
specified in milliseconds. |
JBIFW1171 |
INFO |
{0} {1} forced shutdown complete. Cause: A forced shutdown of
the component has completed. Action: None required, informational message only. |
JBIFW1175 |
WARNING |
During unload of installer
for {0} {1}, the bootstrap cleanUp() method threw a {2} exception. The exception
message is: {3} Cause: After a successful install or uninstall of the
component, a failure occurred in the cleanUp() method in the component's installer. Action:
This is usually indicative of either an environmental issue or a bug in
the component itself. The exception message should provide more information. If this is not
a user-written component and the problem persists, contact Oracle for support. |
JBIFW1185 |
WARNING |
Upgrade requested for
{0} {1}, but this component is not currently installed. Upgrade is valid only
for an existing component. Cause: An attempt was made to upgrade a
component that is not installed. Action: If the component is not installed, it
cannot be upgraded. |
JBIFW1186 |
WARNING |
Upgrade requested for {0} {1}, but this component is currently active.
The component must be shut down before an upgrade is performed. Cause:
An attempt was made to upgrade a component that is still running. Action:
Make sure the component is shut down before attempting to upgrade. |
JBIFW1187 |
WARNING |
Validation for upgrade
of {0} {1} failed. Cause: During preparation for an upgrade of the
component, the validation of the new version of the component failed. Action: This
message will be followed by another message that indicates exactly what problem was encountered
during validation. |
JBIFW1188 |
WARNING |
Upgrade requested for {0} {1}, but the required validation has not been
done. Cause: This is an internal error that should not normally occur.
Action: contact Oracle for support. |
JBIFW1189 |
WARNING |
Cancel upgrade requested for {0}, but there is no
installed component by that name. Cause: This is an internal error that should
not normally occur. Action: contact Oracle for support. |
JBIFW1190 |
INFO |
Update completed successfully for {0} {1}.
This component did not provide full upgrade support. Cause: The component was updated
successfully. In this case, the component performed no special upgrade processing. Only the
components runtime jars were updated. Action: None required, informational message only. |
JBIFW1191 |
INFO |
Upgrade completed successfully
for {0} {1}. Cause: The component was upgraded successfully. In this case,
the component performed special processing to upgrade any artifacts that needed to be
changed to work with the new version of the component. Action: None required,
informational message only. |
JBIFW1192 |
WARNING |
Upgrade failed for {0} {1}: {2} Cause: An upgrade of
the specified component failed to complete. Action: Check the secondary part of this message
for details on the error. |
JBIFW1193 |
WARNING |
Upgrade failed for {0} {1}. The component upgrade
method threw {2} with the message: {3} Cause: The component's upgrade processing failed
with the exception and message shown. Action: This is most likely a problem
in the component. If this is not a user-written component, contact Oracle for
support. |
JBIFW1194 |
WARNING |
Upgrade failed for {0} {1}. An IllegalAccessException was encountered when attempting to invoke
the component upgrade method. Cause: This is an internal error that should
not occur. Action: contact Oracle for support. |
JBIFW1195 |
WARNING |
Upgrade of {0} {1} cannot proceed. The
following Shared Libraries must be installed first: {2}. Cause: The component upgrade cannot
be processed because the component requires Shared Libraries that are not installed. Action:
Make sure that the required Shared Libraries listed in the message are installed
before attempting to upgrade the component. |
JBIFW1201 |
WARNING |
Unable to create MBean due to a {0}
exception. Cause: A failure occurred while attempting to create an MBean in
the runtime. Action: There should be another message preceding this one in the
server log that indicates which MBean was being created. |
JBIFW1202 |
WARNING |
Unable to register MBean due
to a {0} exception. Cause: A failure occurred while attempting to register
an MBean in the runtime. Action: There should be another message preceding this
one in the server log that indicates which MBean was being registered. |
JBIFW1203 |
WARNING |
The InstallerMBean
could not be registered. Cause: The installer MBean for a component could
not be registered. Action: Check the log for further messages that provide detailed
information on the failure. |
JBIFW1204 |
WARNING |
Failure occurred registering logger MBean for {0} {1}: {2}
Cause: The logger MBean for the component could not be registered. Action:
Check the server log for further messages that provide detailed information on the failure.
Note that without the logger MBean, there is no way to change the
logger level settings for the component. Try restarting the runtime to see if
the problem still occurs. If this problem persists, contact Oracle for support. |
JBIFW1205 |
WARNING |
Failure occurred
registering life cycle MBean for {0} {1}: {2} Cause: The life cycle
MBean for the component could not be registered. Action: Check the server log for
further messages that provide detailed information on the failure. Note that without the
life cycle MBean, there is no way to start, stop, or shut down
the component. Try restarting the runtime to see if the problem still occurs.
If this problem persists, contact Oracle for support. |
JBIFW1206 |
WARNING |
Failure occurred registering life cycle MBean.
Cause: During installation of a component, the life cycle MBean for the
component could not be registered. Action: Check the server log for further messages that
provide detailed information on the failure. Note that without the life cycle MBean,
there is no way to start, stop, or shut down the component. If
this problem persists, contact Oracle for support. |
JBIFW1207 |
WARNING |
{0} {1} has been uninstalled but its
LifeCycle MBean could not be unregistered due to a {2} exception. Cause:
During uninstallation of a component, the life cycle MBean for the component could
not be unregistered. Action: Check the server log for further messages that provide detailed
information on the failure. Note that the uninstallation of the component was successful, and
the MBean will not be created on subsequent restarts of the runtime. |
JBIFW1208 |
WARNING |
Unable
to register deployer MBean for {0} {1}: {2} Cause: The deployer
MBean for the component could not be registered. Action: Check the server log for
further messages that provide detailed information on the failure. Note that without the
deployer MBean, there is no way to deploy or undeploy service units to/from
the component. Try restarting the runtime to see if the problem still occurs.
If this problem persists, contact Oracle for support. |
JBIFW1209 |
WARNING |
{0} {1} is being shut down
but its Deployer MBean could not be unregistered due to a {2} exception.
Cause: During shutdown of a component, the deployer MBean for the component
could not be unregistered. Action: Check the server log for further messages that
provide detailed information on the failure. Note that the shutdown of the component
was successful, and the MBean will be recreated on the next start of
the component. |
JBIFW1210 |
WARNING |
{0} {1} has been uninstalled but its Logger MBean for logger {2}
could not be unregistered due to a {3} exception. Cause: During
uninstallation of a component, the logger MBean for the component could not be
unregistered. Action: Check the server log for further messages that provide detailed information
on the failure. Note that the uninstallation of the component was successful, and the
MBean will not be created on subsequent restarts of the runtime. |
JBIFW1211 |
WARNING |
Failure occurred
registering statistics MBean for {0} {1}: {2} Cause: The statistics MBean for the
component could not be registered. Action: Check the server log for further messages
that provide detailed information on the failure. Note that without the statistics MBean,
there is no way to display the statistics for the component. However, the
component itself is still functional. Try restarting the runtime to see if the
problem still occurs. If this problem persists, contact Oracle for support. |
JBIFW1212 |
WARNING |
{0} {1} has
been uninstalled but its Statistics MBean could not be unregistered due to a
{2} exception. Cause: During uninstallation of a component, the statistics MBean for
the component could not be unregistered. Action: Check the server log for further messages
that provide detailed information on the failure. Note that the uninstallation of the
component was successful, and the MBean will not be created on subsequent restarts
of the runtime. |
JBIFW1213 |
WARNING |
Failure occurred registering Configuration MBean for {0} {1}: {2} Cause:
The configuration MBean for the component could not be registered. Action: Check the
server log for further messages that provide detailed information on the failure. Note that
without the configuration MBean, there is no way to display or modify the
configuration properties for the component. However, the component itself is still functional. Try
restarting the runtime to see if the problem still occurs. If this problem
persists, contact Oracle for support. |
JBIFW1214 |
WARNING |
{0} {1} has been uninstalled but its Configuration MBean
could not be unregistered due to a {2} exception. Cause: During uninstallation of
a component, the configuration MBean for the component could not be unregistered. Action:
Check the server log for further messages that provide detailed information on the failure.
Note that the uninstallation of the component was successful, and the MBean will
not be created on subsequent restarts of the runtime. |
JBIFW1300 |
INFO |
Shared Library {0} has
been installed. Cause: The Shared Library has been successfully installed. Action: None
required, informational message only. |
JBIFW1302 |
WARNING |
Installation of Shared Library {0} failed. A Shared Library is already
registered with the same name. Cause: An attempt was made to install
a Shared Library but there is already a Shared Library installed by the
same name. Action: Multiple Shared Libraries with the same name cannot be installed.
One of them must be renamed. |
JBIFW1303 |
WARNING |
Installation of Shared Library {0} failed.
Cause: The installation of a Shared Library failed. Action: Additional messages are logged that
provide detailed information about the failure. Refer to those messages for the appropriate
action. |
JBIFW1304 |
WARNING |
Error creating the shared class loader for Shared Library {0}: {2} Cause:
The runtime was unable to create the class loader for the Shared Library.
Action: Check the message for detailed information about the error. If the cause
of the error cannot be determined, contact Oracle for support. |
JBIFW1320 |
INFO |
Shared Library {0} has
been uninstalled. Cause: The Shared Library has been successfully uninstalled. Action: None
required, informational message only. |
JBIFW1321 |
WARNING |
Uninstallation of Shared Library {0} failed. No Shared Library with the
specified name is installed. Cause: An attempt was made to uninstall a
Shared Library that does not exist. Action: Check to be sure the name
of the Shared Library is correct. |
JBIFW1322 |
WARNING |
Shared Library {0} has been uninstalled, but
the following components cannot be started until this Shared Library is reinstalled: {1}.
Cause: The Shared Library has been successfully uninstalled. The components listed in
the message have dependencies on this Shared Library. Action: If the dependent components are
not also being uninstalled, you must reinstall this Shared Library before those components
can be started. |
JBIFW1324 |
WARNING |
Shared Library {0} is referenced by {1} {2}. Cause:
The named Shared Library is required by the specified component. Action: This message
is issued in the context of other messages. Check the server log for
the other messages to determine the appropriate action. |
JBIFW1325 |
WARNING |
This Shared Library is referenced by:
{0}. These components must be shut down before the Shared Library can be
uninstalled. Cause: An attempt was made to uninstall a Shared Library while
components that depend on it are still active. Action: The listed components must be
shut down before uninstalling the Shared Library. |
JBIFW1326 |
WARNING |
Unable to uninstall Shared Library {0}
due to active dependent components. Cause: An attempt was made to uninstall a
Shared Library while components that depend on it are still active. Action: This
message will be accompanied by other messages that list the dependent components that must
be shut down. |
JBIFW1327 |
INFO |
Class loader removal for Shared Library {0} failed due to
an exception: {1} Cause: During uninstallation of a Shared Library, the class loader
for that library could not be removed. Action: None required, informational message only. |
JBIFW1350 |
WARNING |
DeliveryChannel not
available for {0}. Cause: A component attempted a call to the NMR
when the delivery channel was not available. Action: This is most likely due
to a bug in the component. If the component is a user-written component,
check the component code to make sure that the NMR calls are being
made in the correct place. Otherwise, contact Oracle for support. |
JBIFW1351 |
WARNING |
A logger with name
{0} cannot be created because the resource bundle {1} cannot not be found.
Cause: A component attempted to create a logger with an associated resource
bundle but the resource bundle could not be found. Action: This is most
likely due to a bug in the component. If the component is a
user-written component, check the component packaging to make sure that the resource bundle is
included. Otherwise, contact Oracle for support. |
JBIFW1352 |
WARNING |
A logger with name {0} cannot be
created using resource bundle {1}. A logger with the same name already exists
using resource bundle {2}. Cause: A component attempted to create a logger with
an associated resource bundle but there is already a logger by the same
name using a different resource bundle. Action: This is most likely due to
a bug in the component. If the component is a user-written component, check
the component code to make sure that it is not creating the same
logger with two different resource bundles. Otherwise, contact Oracle for support. |
JBIFW1356 |
WARNING |
Null suffix argument
received. The suffix argument must be non-null. Cause: A component called the javax.jbi.component.ComponentContext.getLogger()
method but provided a null value for the suffix argument. Action: This is
a bug in the component. If the component is a user-written component, check the
component code to make sure that it is not creating the same
logger with two different resource bundles. Otherwise, contact Oracle for support. |
JBIFW2001 |
WARNING |
Component state cannot change
from {0} to {1}. Cause: An invalid component state transition was attempted.
Action: This is an internal error that should not normally occur. If the
problem persists, contact Oracle for support. |
JBIFW2002 |
WARNING |
Bootstrap implementation for {0} could not be loaded.
{1} Cause: A failure occurred while loading the component's installer bootstrap implementation
class. Action: The end of this message contains a more detailed error message
that should indicate the exact problem. Typically this error is due to either
a problem in the packaging of the component or a corrupted filesystem. If
this is a user-written component, check the packaging of the component to make
sure that all of the classes are included and in the correct locations.
Otherwise, contact Oracle for support. |
JBIFW2003 |
WARNING |
LifeCycle implementation for {0} could not be loaded. {1}
Cause: A failure occurred while loading the component's life cycle implementation class.
Action: The end of this message contains a more detailed error message that
should indicate the exact problem. Typically this error is due to a problem
in the packaging of the component or a corrupted filesystem. If this is
a user-written component, check the packaging of the component to make sure that all
of the classes are included and in the correct locations. Otherwise, contact Oracle
for support. |
JBIFW2004 |
WARNING |
Required class {0} was not found. Cause: A class required
by the component was not found in the class path. Action: This is
typically due to either a problem in the packaging of the component or
a corrupted filesystem. If this is a user-written component, check the packaging of the
component to make sure that all of the classes are included and in
the correct locations. Otherwise, contact Oracle for support. |
JBIFW2007 |
WARNING |
The class {0} does not
implement the required interface {1}. Cause: The specified class in the component does
not implement the specified required interface. Action: This is a problem in the
component. If the component is a user-written component, check the code to make
sure that all of the required JSR208 interfaces are implemented. Otherwise, contact Oracle
for support. |
JBIFW2009 |
WARNING |
A {0} exception was encountered. Cause: An unexpected exception occurred while
attempting to load either the life cycle class or the bootstrap class for
the component. Action: This is most likely a problem in the component. If
the component is a user-written component, check the packaging of the component. Otherwise,
contact Oracle for support. |
JBIFW2010 |
WARNING |
The Component.{0} method returned a null value. No implementation of the
{1} interface is available. Cause: The named method in the component's implementation
of the javax.jbi.component.Component interface failed to return a valid implementation of the named
interface. Action: This is a problem in the component. If the component is
a user-written component, check the code to make sure that all of the
required JSR208 interfaces are correctly implemented. Otherwise, contact Oracle for support. |
JBIFW2011 |
WARNING |
Another request is
already in progress for {0}. Cause: An attempt to process a life
cycle or deployment request for the component was denied because another request is
being processed. Action: Retry the request later. This is a transient condition; multiple
concurrent life cycle or deployment requests cannot be allowed without compromising the integrity of
the system. |
JBIFW2012 |
WARNING |
Unable to create directory {0} for storing logger level settings for {1}
{2}. Logger level settings will be lost upon restart of the system.
Cause: An I/O error occurred when creating the directory for storing logger settings
for the component. Action: Check to make sure the disk is accessible and
has available space. Without this directory, logger settings cannot be persisted across restarts
of the runtime. |
JBIFW2013 |
WARNING |
Unable to write logger level settings for {0} {1} to
file {2}. Logger level settings will be lost upon restart of the system.
Cause: An I/O error occurred when writing the logger settings for the
component to the specified file. Action: Check to make sure the disk is accessible
and has available space. Without this file, logger settings cannot be persisted across
restarts of the runtime. |
JBIFW2014 |
WARNING |
Unable to read logger level settings for {0} {1}
from file {2}. Logger level settings will not be restored. Cause: An
I/O error occurred when reading the logger settings for the component from the
specified file. Action: Check to make sure the file is accessible. Without this file,
logger settings cannot be persisted across restarts of the runtime. |
JBIFW2015 |
WARNING |
Unable to close logger
level settings file {0} for {1} {2}. Cause: An I/O error occurred when
creating the directory for storing logger settings for the component. Action: Check
to make sure the disk is accessible and has available space. Without this
directory, logger settings cannot be persisted across restarts of the runtime. |
JBIFW2016 |
WARNING |
Logger {0} is
not registered. Cause: The logger specified is not registered in the component's
logger MBean. Action: This is due to the logger name not being included
in the logger definitions in the jbi.xml for the component. If this is
a user-written component, update the logger definitions in jbi.xml to include this logger
name. Otherwise, contact Oracle for support. |
JBIFW2103 |
WARNING |
A component with name {0} is already registered.
Cause: An attempt was made to install a component but there is
already a component installed with the same name. Action: Make sure you have specified
the correct component archive. |
JBIFW2105 |
WARNING |
Component {0} not found, permanent registration cannot be completed.
Cause: This is an internal error that should not normally occur. Action: contact
Oracle for support. |
JBIFW2108 |
WARNING |
No component with name {0} is registered. Cause: A query
was made for a Service Unit for the named component, but there is
no component registered with the specified name. Action: This could happen if the component
was being uninstalled at the same time a query was made. If this
message continues to be logged, contact Oracle for support. |
JBIFW2152 |
WARNING |
A Shared Library with
name {0} is already registered. Cause: An attempt was made to install
a Shared Library but there is already a Shared Library installed with the
same name. Action: If you intended to replace the existing Shared Library, you
must first uninstall the existing one. |
JBIFW2155 |
WARNING |
No Shared Library with name {0} is registered.
Cause: An attempt was made to uninstall a Shared Library that does
not exist. Action: Make sure the correct Shared Library name is specified. |
JBIFW2204 |
WARNING |
Unrecognized component
type ({0}), component {1} ignored. Cause: This is an internal error that
should not normally occur. Action: contact Oracle for support. |
JBIFW2400 |
WARNING |
Service Unit {0} already exists
for {1} {2}. Cause: A Service Unit by the name displayed has
already been deployed to the component. Action: Change the name of the Service
Unit in your application to avoid the duplicate name, and redeploy the application. |
JBIFW2401 |
WARNING |
Service
Unit {0} not found for {1} {2}. Cause: During an undeploy of
the Service Unit, no Service Unit by this name was found associated with
the component. Action: This is an internal error that should not normally occur.
If the problem persists, contact Oracle for support. |
JBIFW2402 |
WARNING |
Service Unit state cannot change from
{0} to {1}. Cause: An invalid Service Unit state transition was attempted.
Action: This is an internal error that should not normally occur. If the
problem persists, contact Oracle for support. |
JBIFW2450 |
WARNING |
Service Unit {0} not found. Cause: An
operation was attempted on a Service Unit that does not exist in the
runtime. Action: This is an internal error that should not normally occur. If
the problem persists, contact Oracle for support. |
JBIFW2451 |
WARNING |
Service Unit {0} is already deployed.
Cause: An attempt was made to deploy a Service Unit that is already
deployed. Action: This should not normally occur if the supported clients are being
used (NetBeans, asadmin, or admin console). If this message persists, contact Oracle for
support. |
JBIFW2452 |
WARNING |
Service Unit {0} cannot be initialized, it has already been started. Cause:
An attempt was made to initialize a service unit that is already started.
Action: This should not normally occur if the supported clients are being used
(NetBeans, asadmin, ant, or admin console). If this message persists, contact Oracle for support. |
JBIFW2453 |
WARNING |
Service
Unit {0} cannot be started, it has not been initialized. Cause: An
attempt was made to start a Service Unit that is not initialized. Action:
This should not normally occur if the supported clients are being used (NetBeans,
asadmin, ant, or admin console). If this message persists, contact Oracle for support. |
JBIFW2454 |
WARNING |
Service Unit
{0} cannot be stopped, it is shut down. Cause: An attempt
was made to stop a Service Unit that is already shut down. Action:
This should not normally occur if the supported clients are being used (NetBeans,
asadmin, ant, or admin console). If this message persists, contact Oracle for support. |
JBIFW2455 |
WARNING |
Service Unit
{0} cannot be shut down, it has not been stopped. Cause: An
attempt was made to shut down a Service Unit that is not stopped.
Action: This should not normally occur if the supported clients are being used
(NetBeans, asadmin, ant, or admin console). If this message persists, contact Oracle for support. |
JBIFW2456 |
WARNING |
Service
Unit {0} cannot be undeployed because it is in {1} state. It must
be shut down before undeploying. Cause: An attempt was made to undeploy
the Service Unit but it is not in the SHUTDOWN state. Action:
Make sure that the Service Assembly containing this Service Unit has been shut
down before attempting to undeploy. |
JBIFW2457 |
WARNING |
Service Unit {0} state change after {1} could not
be persisted. {2} Cause: The state of the Service Unit was not persisted
after an operation that affected its state. Action: Check the server log for
other messages that precede this message. Those messages will provide more details about
the error. If the problem persists, contact Oracle for support. |
JBIFW2458 |
WARNING |
Interrupt occurred on {0}
for Service Unit {1}. Cause: The operation on the Service Unit was
interrupted, causing a java.lang.InterruptedException. Action: Examine the server log for messages that might
explain why the operation was interrupted. If this problem persists, contact Oracle for
support. |
JBIFW2459 |
WARNING |
Unexpected exception {0} occurred on {1} for Service Unit {2}. Exception message text
is: {3}. Cause: The operation on the Service Unit failed due to
an exception. The message from the exception is included in this message. Action:
The exception message should provide information about what caused the failure. If the
failure is persistent, it could be a problem in the component. If the
component is a user-written component, use the information from the failure to assist in
debugging the problem. Otherwise, contact Oracle for support. |
JBIFW2460 |
WARNING |
Unexpected exception {0} occurred on {1}
for Service Unit {2}. The exception has no message text. Cause: The
operation on the Service Unit failed due to an exception. The exception contained
no message. Action: The exception in this case provided no message. If the failure
is persistent, it could be a problem in the component. If the component
is a user-written component, use the information from the failure to assist in
debugging the problem. Otherwise, contact Oracle for support. |
JBIFW2461 |
WARNING |
Timeout occurred on {0} for Service
Unit {1}. The operation did not complete before the timeout interval of {2}
milliseconds expired. Cause: The operation on the Service Unit failed to complete within
the time interval specified by the serviceUnitTimeout runtime configuration parameter. Action: Depending on
the complexity of the component's processing for a Service Unit, this may or may
not be a problem with the component. Try increasing the value specified by
serviceUnitTimeout in the runtime configuration. If that does not help, there could be
an environmental issue that is affecting the component. If the component is one
of the supported components included in the product, contact Oracle for support. |
JBIFW2462 |
WARNING |
Unable to
perform {0} of Service Unit {1}. The component is not started. Cause:
An attempt was made to perform an operation on a Service Unit, but
the required component was not active. Action: Make sure the component is started before
attempting a Service Unit operation. |
JBIFW2463 |
WARNING |
Unable to perform {0} of Service Unit {1}.
The Service Unit Manager for the component is not available. Cause: A
Service Unit operation was attempted, but the component did not provide a Service
Unit Manager implementation. Action: If this is a user-written component, check to be sure
the javax.jbi.component.Component.getServiceUnitManager() method is correctly implemented. Otherwise, contact Oracle for support. |
JBIFW2500 |
WARNING |
ServiceUnitManager stack trace
follows:\n{0} Cause: The component's ServiceUnitManager implementation encountered an exception and the stack
trace is logged in this message. Action: This is a bug in the component.
If the component is a user-written component, use the information in the stack
trace to help debug the component. Otherwise, contact Oracle for support. |
JBIFW2501 |
WARNING |
Error in ServiceUnitManager
for {0} {1}: {2} Cause: The component's ServiceUnitManager implementation encountered an exception.
Action: This is a bug in the component. This message is normally followed
by message JBIFW2500, which provides the stack trace. If the component is a
user-written component, use the information in the stack trace to help debug the component.
Otherwise, contact Oracle for support. |
JBIFW2502 |
WARNING |
Limit of {0} initialization timeouts reached. Terminating processing for
{1} {2}. Cause: During startup of the component, the runtime encountered multiple
timeouts on initialization of Service Units deployed to the component. The number of
timeouts reached the specified limit and Service Unit initialization processing was terminated. Action: Check
the server log to determine what is causing the service unit initializations to time
out. If the problem persists, contact Oracle for support. |
JBIFW2503 |
WARNING |
Limit of {0} start
timeouts reached. Terminating processing for {1} {2}. Cause: During startup of the component,
the runtime encountered multiple timeouts on starts of Service Units deployed to the
component. The number of timeouts reached the specified limit and Service Unit start
processing was terminated. Action: Check the server log to determine what is causing the
Service Unit starts to time out. If the problem persists, contact Oracle for
support. |
JBIFW2504 |
WARNING |
Limit of {0} stop timeouts reached. Terminating processing for {1} {2}. Cause:
During stop or shutdown of the component, the runtime encountered multiple timeouts on
stops of Service Units deployed to the component. The number of timeouts reached the
specified limit and Service Unit stop processing was terminated. Action: Check the
server log to determine what is causing the Service Unit stops to time
out. If the problem persists, contact Oracle for support. |
JBIFW2505 |
WARNING |
Limit of {0} shutdown timeouts
reached. Terminating processing for {1} {2}. Cause: During shutdown of the component, the
runtime encountered multiple timeouts on shutdowns of Service Units deployed to the component.
The number of timeouts reached the specified limit and Service Unit shutdown processing
was terminated. Action: Check the server log to determine what is causing the Service
Unit shutdowns to time out. If the problem persists, contact Oracle for support. |
JBIFW2507 |
INFO |
Service
Unit {0} for component {1} in Service Assembly {2} has been started.
Cause: The named Service Unit has been successfully started. Action: None required, informational message
only. |
JBIFW2508 |
INFO |
Service Unit {0} for component {1} in Service Assembly {2} has been stopped.
Cause: The named Service Unit has been successfully stopped. Action: None required,
informational message only. |
JBIFW2509 |
INFO |
Service Unit {0} for component {1} in Service Assembly {2} has been
shut down. Cause: The named Service Unit has been successfully shut down.
Action: None required, informational message only. |
JBIFW2550 |
WARNING |
Component {0} has not registered a configuration MBean.
Cause: The named component did not register a configuration MBean. Action: None
required, this means that the component does not provide an MBean for managing
its runtime configuration. |
JBIFW2551 |
WARNING |
Component {0} configuration change {1} could not be persisted. {2} Cause:
An error occurred updating the registry to persist a static configuration attribute for the
component. Action: Look at the error message from the registry operation to determine
whether the problem is a disk issue or an environmental issue. If the
problem persists, contact Oracle for support. |
JBIFW2552 |
WARNING |
Failed to add application variable {0} of component
{1} to the registry. {2} Cause: An error occurred adding the named application
variable to the registry for the component. Action: Look at the error message
from the registry operation to determine whether the problem is a disk issue
or an environmental issue. If the problem persists, contact Oracle for support. |
JBIFW2553 |
WARNING |
Failed to
update application variable {0} of component {1} in the registry. {2} Cause:
An error occurred updating the named application variable in the registry for the
component. Action: Look at the error message from the registry operation to determine
whether the problem is a disk issue or an environmental issue. If the
problem persists, contact Oracle for support. |
JBIFW2554 |
WARNING |
Failed to delete application variable {0} of component
{1} from the registry. {2} Cause: An error occurred removing the named application
variable from the registry for the component. Action: Look at the error message from
the registry operation to determine whether the problem is a disk issue or
an environmental issue. If the problem persists, contact Oracle for support. |
JBIFW2555 |
WARNING |
Operation {0} is
not implemented by MBean {1}. Cause: An operation was invoked on the
configuration MBean but that operation was not supported by the MBean. Action: This
is most likely a bug in the component. If the component is a
user-written component, make sure that the MBean implements all of the required operations. Otherwise,
contact Oracle for support. |
JBIFW2556 |
WARNING |
Failed to add application configuration {0} of component {1} to
the registry. {2} Cause: An error occurred adding the named application configuration
to the registry for the component. Action: Look at the error message from the
registry operation to determine whether the problem is a disk issue or an
environmental issue. If the problem persists, contact Oracle for support. |
JBIFW2557 |
WARNING |
Failed to update application
configuration {0} of component {1} to the registry. {2} Cause: An error
occurred updating the named application configuration in the registry for the component. Action: Look
at the error message from the registry operation to determine whether the problem is
a disk issue or an environmental issue. If the problem persists, contact Oracle
for support. |
JBIFW2558 |
WARNING |
Failed to delete application configuration {0} of component {1} from the registry.
{2} Cause: An error occurred removing the named application configuration from the
registry for the component. Action: Look at the error message from the registry operation
to determine whether the problem is a disk issue or an environmental issue.
If the problem persists, contact Oracle for support. |
JBIFW2600 |
WARNING |
No {0} element was found for
the {1} element. Cause: While processing information from the component descriptor (jbi.xml),
a required element was not found. Action: Check the content of the component descriptor
to make sure that it is complete. If this error occurs for one
of the supported components included with the product, contact Oracle for support. |
JBIFW2601 |
WARNING |
Found {0}
{1} elements, but only one is allowed. Cause: While processing information from
the component descriptor (jbi.xml), more than one element was found where only one
is allowed. Action: Check the content of the component descriptor to make sure
that it is correct. If this error occurs for one of the supported
components included with the product, contact Oracle for support. |
JBIFW2602 |
WARNING |
Empty {0} element not allowed,
must have a single text value. Cause: While processing information from the component
descriptor (jbi.xml), an element that requires a text value had no value specified.
Action: Check the content of the component descriptor to make sure that it
is correct. If this error occurs for one of the supported components included
with the product, contact Oracle for support. |
JBIFW2603 |
WARNING |
Invalid {0} element, found incorrect content. This
element must have a single text value. Cause: While processing information from the
component descriptor (jbi.xml), an element that requires a text value contained an element
that was not expected. Action: Check the content of the component descriptor to
make sure that it is correct. If this error occurs for one of
the supported components included with the product, contact Oracle for support. |
JBIFW2604 |
WARNING |
DOMException: {0}.
Cause: This is an internal error that should not normally occur. Action: contact
Oracle for support. |
JBIFW2650 |
WARNING |
Unable to create user data for notification, {0} exception occurred building CompositeData.
Cause: This is an internal error that should not normally occur. Action:
contact Oracle for support. |
JBIFW2651 |
WARNING |
Unable to send notification for event type {0}, source type {1},
source name {2}; {3} exception occurred. Cause: The runtime attempted to send
a JMX notification for an event, and encountered an exception. Action: This
should not normally occur. If the problem persists, contact Oracle for support. |
JBIFW5000 |
WARNING |
Unable to
query appserver config: {0} Cause: An exception occurred while attempting to query
GlassFish for configuration information while setting up the HTTP binding configuration. The exception
message is included in this message. Action: Check the GlassFish server log for further
information about the error. If the cause is not pinpointed there, contact Oracle
for support. |
JBIFW5002 |
WARNING |
Failed to write httpsoap configuration file {0} : {1} Cause:
An error occurred while writing the configuration file for the HTTP binding component.
Action: This is probably due to either a lack of disk space or
an error on the filesystem. Make sure there is sufficient disk space and
that the filesystem is not corrupted. |
JBIFW5003 |
INFO |
An exception occurred during initialization of system components.
Cause: An error occurred while initializing the system components. Action: This message will be
preceded by more detailed messages that provide further information. |
JBIFW5051 |
WARNING |
Get XA Resources from
JBI components failed with exception: {0} Cause: An error occurred while attempting to
get a list of XA resources requiring synchronization. Action: The exception should contain
detailed information about the error. Correct any problems and try restarting. If this
problem persists, set the level of the com.sun.jbi.framework.sun logger to FINE to obtain
further diagnostics, and contact Oracle for support. |
JBIFW5100 |
SEVERE |
Synchronization failed with the following exception: {0}
Cause: An error occurred during cluster instance synchronization. Action: The exception should contain
detailed information about the error. Check the GlassFish server log for further diagnostics.
If this problem persists, set the level of the com.sun.jbi.framework.sun logger to FINE
to obtain further diagnostics, and contact Oracle for support. |
JBIFW5101 |
WARNING |
Synchronization of file ({0}) from
DAS to local file ({1}) failed with exception: {2}. Cause: During cluster
instance synchronization, a copy operation on a file from the DAS to the
local instance failed. Action: Check the exception to determine why the copy failed. Make
sure there is sufficient space for the local copy of the file and
that the filesystem is accessible. If this problem persists, contact Oracle for support. |
JBIFW5102 |
WARNING |
Synchronization
of config file encountered difference problems. Exception was: {0}. Cause: During cluster
instance synchronization, a problem was encountered when determining the differences between the DAS JBI
configuration and the local JBI configuration. Action: The exception message should contain detailed
information about the error. Check the GlassFish server log for further diagnostics. If
this problem persists, set the level of the com.sun.jbi.framework.sun logger to FINE to
obtain further diagnostics, and contact Oracle for support. |
JBIFW5103 |
WARNING |
Synchronization of archive file failed. Exception
was {0}. Cause: During cluster instance synchronization, a problem was encountered when
downloading a Shared Library, Component, or Service Assembly archive from the DAS. Action:
The exception message should contain detailed information about the error. Check the GlassFish server
log for further diagnostics. If this problem persists, contact Oracle for support. |
JBIFW5104 |
WARNING |
Synchronization failed
to uninstall component ({0}) with exception: {1} Cause: During cluster instance synchronization, a
problem was encountered while uninstalling a component from the local instance. Action: The
exception message should contain detailed information about the error. Check the GlassFish server log
for further diagnostics. If this problem persists, contact Oracle for support. |
JBIFW5105 |
WARNING |
Synchronization failed to
install component ({0}) with exception: {1} Cause: During cluster instance synchronization, a problem
was encountered while installing a component into the local instance. Action: The exception
message should contain detailed information about the error. Check the GlassFish server log for
further diagnostics. If this problem persists, contact Oracle for support. |
JBIFW5106 |
WARNING |
Synchronization cannot get state
for component ({0}) with exception: {1} Cause: During cluster instance synchronization, a problem
was encountered getting the state of a component from the local instance. Action:
The exception message should contain detailed information about the error. Check the GlassFish server
log for further diagnostics. If this problem persists, contact Oracle for support. |
JBIFW5107 |
WARNING |
Synchronization cannot
set state for component ({0}) with exception: {1} Cause: During cluster instance synchronization,
a problem was encountered setting the state of a component in the local
instance. Action: The exception message should contain detailed information about the error. Check
the GlassFish server log for further diagnostics. If this problem persists, contact Oracle for
support. |
JBIFW5108 |
WARNING |
Synchronization failed to uninstall shared library ({0}) with exception: {1} Cause: During
cluster instance synchronization, a problem was encountered while uninstalling a Shared Library from the
local instance. Action: The exception message should contain detailed information about the error.
Check the GlassFish server log for further diagnostics. If this problem persists, contact Oracle
for support. |
JBIFW5109 |
WARNING |
Synchronization failed to install shared library ({0}) with exception: {1} Cause:
During cluster instance synchronization, a problem was encountered while installing a Shared Library into
the local instance. Action: The exception message should contain detailed information about the
error. Check the GlassFish server log for further diagnostics. If this problem persists,
contact Oracle for support. |
JBIFW5110 |
WARNING |
Synchronization failed to undeploy Service Assembly ({0}) with exception: {1}
Cause: During cluster instance synchronization, a problem was encountered while undeploying a Service Assembly
from the local instance. Action: The exception message should contain detailed information about
the error. Check the GlassFish server log for further diagnostics. If this problem
persists, contact Oracle for support. |
JBIFW5111 |
WARNING |
Synchronization failed to deploy Service Assembly ({0}) with exception: {1}
Cause: During cluster instance synchronization, a problem was encountered while deploying a
Service Assembly to the local instance. Action: The exception message should contain detailed information
about the error. Check the GlassFish server log for further diagnostics. If this
problem persists, contact Oracle for support. |
JBIFW5112 |
WARNING |
Synchronization cannot get state for Service Assembly ({0}) with
exception: {1} Cause: During cluster instance synchronization, a problem was encountered getting
the state of a Service Assembly from the local instance. Action: The exception
message should contain detailed information about the error. Check the GlassFish server log for
further diagnostics. If this problem persists, contact Oracle for support. |
JBIFW5113 |
WARNING |
Synchronization cannot set state
for Service Assembly ({0}) with exception: {1} Cause: During cluster instance synchronization, a
problem was encountered setting the state of a Service Assembly in the local
instance. Action: The exception message should contain detailed information about the error. Check
the GlassFish server log for further diagnostics. If this problem persists, contact Oracle for
support. |
JBIFW5115 |
WARNING |
Synchronization failed to set configuration for component ({0}) with exception: {1} Cause:
During cluster instance synchronization, a problem was encountered setting the configuration for a component
in the local instance. Action: The exception message should contain detailed information about
the error. Check the GlassFish server log for further diagnostics. If this problem
persists, contact Oracle for support. |
JBIFW5116 |
INFO |
Synchronization skipped. Unable to connect to the DAS.
Cause: During cluster instance synchronization, the local instance was unable to connect to
the DAS. Action: Messages preceding this one should contain detailed information about the
error. Check the GlassFish server log for further diagnostics. If this problem persists, set
the level of the com.sun.jbi.framework.sun logger to FINE to obtain further diagnostics, and
contact Oracle for support. |
JBIFW5119 |
WARNING |
Synchronization failed to add application variable ({0}) for component ({1})
with exception: {2} Cause: During cluster instance synchronization, a problem was encountered
adding an application variable for a component in the local instance. Action: The
exception message should contain detailed information about the error. Check the GlassFish server log
for further diagnostics. If this problem persists, contact Oracle for support. |
JBIFW5120 |
WARNING |
Synchronization failed to
remove application variable ({0}) for component ({1}) with exception: {2} Cause: During
cluster instance synchronization, a problem was encountered removing an application variable for a component
in the local instance. Action: The exception message should contain detailed information about
the error. Check the GlassFish server log for further diagnostics. If this problem
persists, contact Oracle for support. |
JBIFW5121 |
WARNING |
Synchronization failed to add application config ({0}) for component ({1})
with exception: {2} Cause: During cluster instance synchronization, a problem was encountered
adding an application configuration for a component in the local instance. Action: The
exception message should contain detailed information about the error. Check the GlassFish server log
for further diagnostics. If this problem persists, contact Oracle for support. |
JBIFW5122 |
WARNING |
Synchronization failed to
remove application config ({0}) for component ({1}) with exception: {2} Cause: During
cluster instance synchronization, a problem was encountered removing an application configuration for a component
in the local instance. Action: The exception message should contain detailed information about
the error. Check the GlassFish server log for further diagnostics. If this problem
persists, contact Oracle for support. |
JBIFW5123 |
WARNING |
Synchronization failed to set property ({0}) for component ({1}) with
exception: {2} Cause: During cluster instance synchronization, a problem was encountered setting
a property for a component in the local instance. Action: The exception message should
contain detailed information about the error. Check the GlassFish server log for further
diagnostics. If this problem persists, contact Oracle for support. |
JBIFW5124 |
WARNING |
Synchronization failed to apply configuration
category ({0}) to target ({1}) with exception: {2} Cause: During cluster instance synchronization,
a problem was encountered applying a configuration for a JBI system service in
the local instance. Action: The exception message should contain detailed information about the
error. Check the GlassFish server log for further diagnostics. If this problem persists,
contact Oracle for support. |
JBIFW5190 |
WARNING |
Unable to query appserver config: {0} Cause: An exception
occurred while attempting to query GlassFish for configuration information during cluster instance synchronization. The
exception message is included in this message. Action: Check the GlassFish server log for
further information about the error. If the cause is not pinpointed there, contact
Oracle for support. |
JBIFW5192 |
WARNING |
Failed to write httpsoap configuration file {0} : {1}
Cause: An error occurred while writing the configuration file for the HTTP binding
component during cluster instance synchronization. Action: This is probably due to either a lack
of disk space or an error on the filesystem. Make sure there is
sufficient disk space and that the filesystem is not corrupted. |
JBIFW5199 |
WARNING |
Synchronization currently disabled. Use
com.sun.jbi.synch.enabled property to control. Cause: Cluster instance synchronization is disabled. Action: To enable
synchronization of JBI entities among cluster instances, the com.sun.jbi.synch.enabled property must be set to
TRUE. |
