8.2: Messages When WebSphere Application Server is running,
InfoCenter Home >
8: Problem determination >
No Heading Found
8.2: Messages When WebSphere Application Server is running,
it might issue messages related to any of the following components:
- Application Assembly Tool
- Administrative GUI
- Administrative repository
- Administrative tasks
- Administrative server
- Alarm
- IBM Validation Tool
- IBM WebSphere validation
- EJB container
- Connection manager
- Database manager
- Data replication service
- Cache management
- Install
- Connector Architecture (J2C)
- IBM Java ORB
- Security Association server
- Java Server Pages (JSP)
- Localizable text
- Messaging
- WebSphere Migration Tool
- JNDI - name services
- Web server plug-ins and native code
- Performance Monitor
- WebSphere security
- Resource Analyzer
- Session and user profiles
- WebSphere systems management utilities
- Servlet engine
- Tracing component
- WebSphere systems management commands
- Request interceptors
- WebSphere object adapter
- WebSphere persistence
- Client
- WSCP command line
- WebSphere server runtime
- WebSphere transactions
- WebSphere systems management task
- EJB workload management
- XML Configurations
- WebSphere Server Validation
Message table To help you diagnose
problems and minimize the need to enable trace in any of the above components,
view the messages table. You can view the messages by prefix or component,
whichever is easiest for you to find in the table. All messages are documented
with user/system action and explanation.
AATL0001: {0} is not a valid
Java archive file Explanation: None. User Response:
None. AATL0002: {0} already
exists. Please input a different file name. Explanation: None.
User Response: None. AATL0003:
{0} already exists. Do you want to overwrite the old one? Explanation:
None. User Response: None.
AATL0004: {0} already exists and can not be overwritten. Do you want to skip
it and continue the operation? Explanation: None. User
Response: None. AATL0005:
A problem occurred while opening file {0} . Possible causes might be incorrect
syntax in the deployment descriptor or missing files. Explanation:
None. User Response: None.
AATL0006: A problem occurred while attempting to add the file(s). Click Details
for more information. Explanation: None. User Response:
None. AATL0007: A problem
occurred while attempting to add the module. Click Details for more information.
Explanation: None. User Response: None.
AATL0008: A problem occurred during
the add or paste operation you are trying to perform. Click Details for more
information. Explanation: None. User Response: None.
AATL0009: Application Assembly Tool
Dialog Explanation: None. User Response: None.
AATL0010: The current property changes
will be lost when you switch to another object. Do you want to apply the changes?
Explanation: None. User Response: None.
AATL0011: Archive is modified. Do you
want to save it before closing the window? Explanation: None.
User Response: None. AATL0012:
Archive was saved successfully. Explanation: None.
User Response: None. AATL0013:
You need to add at least one module to your application. Explanation:
None. User Response: None.
AATL0014: You need to assign container transactions to at least one method.
Explanation: None. User Response: None.
AATL0015: You need to assign method
permissions to at least one method. Explanation: None.
User Response: None. AATL0016:
You need to have at least one enterprise bean. Explanation: None.
User Response: None. AATL0017:
You need to have at least one welcome file. Explanation: None.
User Response: None. AATL0018:
You need to have at least one web resource collection. Explanation:
None. User Response: None. MSGSTART --> AATL0019: This is an EJB 1.0 JAR file. Please specify
the dependent classpath to convert it to a J2EE EJB JAR file.
Explanation: None. User Response: None. AATL0020: Deploy process is cancelled.
Explanation: None. User Response: None. AATL0021: Expanded archive can not be overwritten.
If you want to modify the archive, you can save this archive as another file.
Explanation: None. User Response: None.
AATL0022: Changes have not been applied.
Explanation: None. User Response: None.
AATL0023: Could not save archive file.
Explanation: None. User Response: None.
AATL0024: A problem occurred while attempting
to create the file. Click Details for more information. Explanation:
None. User Response: None.
AATL0025: A problem occurred while attempting to create your Enterprise bean.
Click Details for more information. Explanation: None.
User Response: None. AATL0026:
A problem occurred while attempting to create your Web component. Click Details
for more information. Explanation: None. User Response:
None. AATL0027: A problem
occurred during the create operation. Click Details for more information.
Explanation: None. User Response: None.
AATL0028: A problem occurred while attempting
to create your Bean managed enterprise bean. Click Details for more information.
Explanation: None. User Response: None.
AATL0029: A problem occurred while attempting
to create your Container managed enterprise bean. Click Details for more information.
Explanation: None. User Response: None.
AATL0030: A problem occurred while attempting
to delete the selected object. Click Details for more information.
Explanation: None. User Response: None. AATL0031: A problem occurred while attempting to generate
code for deployment for your archive. Click Details for more information.
Explanation: None. User Response: None.
AATL0032: EJB 1.0 Dependent Classpath
Explanation: None. User Response: None.
AATL0033: Error {0} has occurred. Click
Details for more information. Explanation: None. User
Response: None. AATL0034:
Exception {0} has occurred. Click Details for more information.
Explanation: None. User Response: None. AATL0035: Code generation is in progress. Do you want
to stop the process and exit? Explanation: None. User
Response: None. AATL0036:
Unable to load the alternative deployment descriptor. Click Details for more
information. Explanation: None. User Response: None.
AATL0037: Does the bean implement bean-managed
persistence (BMP)? Explanation: None. User Response:
None. AATL0038: A problem
occurred while attempting to import your Enterprise bean. Click Details for
more information. Explanation: None. User Response:
None. AATL0039: A problem
occurred while attempting to import your Web component. Click Details for
more information. Explanation: None. User Response:
None. AATL0040: loading alternative
deployment descriptor... Explanation: None. User Response:
None. AATL0041: Changes must
be saved before generating code for deployment. Do you want to save and continue?
Explanation: None. User Response: None.
AATL0042: File exists already. Do you
want to overwrite it? Explanation: None. User Response:
None. AATL0043: File {0}
exists already. Do you want to overwrite it? Explanation: None.
User Response: None. AATL0044:
Archive {0} has the following xml syntax error(s): Explanation:
None. User Response: None.
AATL0045: Please choose a security role Explanation: None.
User Response: None. AATL0046:
Please select a file instead of a directory. Explanation: None.
User Response: None. AATL0047:
The following required properties are not set: Explanation: None.
User Response: None. AATL0048:
Archive file can not be saved as following requirements are not met:
Explanation: None. User Response: None. AATL0049: A problem occurred while attempting to remove
the module. Click Details for more information. Explanation:
None. User Response: None.
AATL0050: Archive is modified. Do you want to save the archive before loading
the alternative deployment descriptor? Explanation: None.
User Response: None. AATL0051:
The archive file does not have any security roles. Explanation:
None. User Response: None.
AATL0052: The selected file is not a valid J2EE archive file.
Explanation: None. User Response: None. AATL0053: The selected file does not contain a standard
deployment descriptor. Would you like us to try to repair it and then
open it again? Explanation: None. User Response: None.
AATL0054: Unable to load all elements.
Explanation: None. User Response: None.
AATL0055: A problem occurred while attempting
to get the CMP fields. Click Details for more information. Explanation:
None. User Response: None.
AATL0056: Unable to locate requested help file. Please download the InfoCenter
to enable help. help id: {0} Explanation: None.
User Response: None. AATL0057:
Unable to open file {0}. Click Details for more information. Explanation:
None. User Response: None.
AATL0058: Unable to open parent application {0} Explanation: None.
User Response: None. AATL0059:
The create operation was cancelled by the user before it finished. Click Details
for more information. Explanation: None. User Response:
None. AATL0060: Validating
Application deployment descriptor Explanation: None.
User Response: None. AATL0061:
Validating Application extensions Explanation: None.
User Response: None. AATL0062:
Validating Web module deployment descriptor Explanation: None.
User Response: None. AATL0063:
Validating Web module extensions Explanation: None.
User Response: None. AATL0064:
Validating EJB module deployment descriptor Explanation: None.
User Response: None. AATL0065:
Validating EJB module extensions Explanation: None.
User Response: None. AATL0066:
A problem occurred while attempting to verify your archive. Click Details
for more information. Explanation: None. User Response:
None. AATL0067: Failed to
open archive file {0} Explanation: None. User Response:
None.
ADGU0001W: Unable to obtain Repository types {0} Explanation:
None. User Response: None.
ADGU0002W: Cannot
find an object, TypeObject, for the model Explanation: None.
User Response: None.
ADGU0003W: Cannot narrow a stub
reference {0} Explanation: None. User Response: None.
ADGU0004W: Cannot set cache soft limit size {0} Explanation: None.
User Response: None.
ADGU0005W: {0} {1}
Explanation: None. User Response: None.
ADGU0006W: Encountered an error in getting model attributes for an EJB server
{0} Explanation: None. User Response: None.
ADGU0007W: Cannot generate a byte array from descriptor: {0} {1}
Explanation: None. User Response: None.
ADGU0008W: Skipping property {0}. Encountered an exception: {1}
Explanation: None. User Response: None.
ADGU0009W: Cannot find bar update for command: {0} Explanation:
None. User Response: None.
ADGU0010W: Cannot
obtain an attribute descriptor {0} Explanation: None.
User Response: None.
ADGU0011W: Cannot generate byte
array from descriptor: {0} {1} Explanation: None. User
Response: None.
ADGU0012W: Cannot remove the EPM bean
{0} Explanation: None. User Response: None.
ADGU0013W: Cannot find EJBContainerHome {0} Explanation: None.
User Response: None.
ADGU0014W: Failed to get the root
instances Explanation: None. User Response: None.
ADGU0015W: Cannot obtain a property descriptor {0} Explanation:
None. User Response: None.
ADGU0016W: The
cache method was passed a null array Explanation: None.
User Response: None.
ADGU0017W: Encountered an error
while examining a TypeAttributes object for a UIDescriptor class {0}
Explanation: None. User Response: None.
ADGU0018W: Cannot narrow a home reference {0} Explanation: None.
User Response: None.
ADGU0019W: Failed to get the list
of groups Explanation: None. User Response: None.
ADGU0020W: Property {0} has a non-displayable editor. Skipping.
Explanation: None. User Response: None.
ADGU0021W: Error in getting model servletGroup attributes Explanation:
None. User Response: None.
ADGU0022W: Cannot
add {0} to context sensitive menu. Explanation: None.
User Response: None.
ADGU0023W: The DeployJarCommand
command failed Explanation: None. User Response: None.
ADGU0024W: Failed to get the list of traced components from the administration
server Explanation: None. User Response: None.
ADGU0025W: Failed to get type information from access bean Explanation:
None. User Response: None.
ADGU0026W: Cannot
find VirtualHostHome Explanation: None. User Response:
None.
ADGU0027W: Invalid child request
Explanation: None. User Response: None.
ADGU0028W: Failed to get the type tree Explanation: None.
User Response: None.
ADGU0029W: AccessBean failed to
return root instances Explanation: None. User Response:
None.
ADGU0030E: Could not bind to the Administration
Server on {0} {1} Explanation: None. User Response:
None.
ADGU0031W: Required attribute in the deployment
descriptor is not set {0} Explanation: None. User Response:
None.
ADGU0032W: Invalid event type detected {0}
Explanation: None. User Response: None.
ADGU0033W: Cannot obtain relationship information {0} Explanation:
None. User Response: None.
ADGU0034W: Cannot
process a list entry Explanation: None. User Response:
None.
ADGU0036W: Exception thrown during menu manipulation
{0} Explanation: None. User Response: None.
ADGU0038W: Cannot convert to a valid repository state {0} Explanation:
None. User Response: None.
ADGU0039W: Caught
UnknownHostException exception while getting hostname Explanation:
None. User Response: None.
ADGU0040W: Cannot
get a home for type object {0} Explanation: None. User
Response: None.
ADGU0041W: Error in getting model servlet
attributes Explanation: None. User Response: None.
ADGU0042E: Could not load security configuration from repository!
Explanation: None. User Response: None.
ADGU0044W: Cannot create a file {0} {1} Explanation: None.
User Response: None.
ADGU0045W: Invalid usage.
Explanation: None. User Response: None.
ADGU0046W: Cannot update row {0} Explanation: None.
User Response: None.
ADGU0047W: Cannot set cache sweep
interval {0} Explanation: None. User Response: None.
ADGU0048W: Exception thrown during button manipulation Explanation:
None. User Response: None.
ADGU0049W: The
filter method was passed a null pointer Explanation: None.
User Response: None.
ADGU0050W: Failed to get the list
of components from the administration server Explanation: None.
User Response: None.
ADGU0051W: Cannot find URIHome
Explanation: None. User Response: None.
ADGU0052W: Cannot deserialize a descriptor {0} Explanation: None.
User Response: None.
ADGU0053W: Error in adding servlet
group Explanation: None. User Response: None.
ADGU0054W: Error in getting model URI attrs Explanation: None.
User Response: None.
ADGU0055W: Cannot find ServletHome
Explanation: None. User Response: None.
ADGU0057W: Cannot find instances of type {0} Explanation: None.
User Response: None.
ADGU0058W: Failed to get object
info from ClientAccess bean Explanation: None. User
Response: None.
ADGU0059E: Could not set SecurityConfigAttributes
on session bean Explanation: None. User Response: None.
ADGU0060W: Cannot find the ApplicationHome class {0} Explanation:
None. User Response: None.
ADGU0061W: Could
not narrow home reference Explanation: None. User Response:
None.
ADGU0062W: Cannot find a content pane for object
{0} Explanation: None. User Response: None.
ADGU0063W: Cannot collect attributes: {0} Explanation: None.
User Response: None.
ADGU0065W: Encountered a vector
of bad parameters. Invalid wait time {0} Explanation: None.
User Response: None.
ADGU0066W: Property change was
vetoed: {0} Explanation: None. User Response: None.
ADGU0067W: Property {0} has a null initial value. Explanation:
None. User Response: None.
ADGU0069W: Name
was not set in enterprise bean Explanation: None. User
Response: None.
ADGU0070W: Encountered an invalid state.
No enterprise bean instance for which the home name can be changed
Explanation: None. User Response: None.
ADGU0071W: Cannot obtain the clone interface class {0} Explanation:
None. User Response: None.
ADGU0072W: Cannot
obtain the attribute class: {0} {1} Explanation: None.
User Response: None.
ADGU0073W: Value is not a valid
timestamp {0} Explanation: None. User Response: None.
ADGU0074W: Encountered an unexpected exception during construction of a UIDescriptor
object {0} Explanation: None. User Response: None.
ADGU0075W: RelationInstance object was badly formed. Parent type is neither
source nor target Explanation: None. User Response:
None.
ADGU0076W: Cannot get a remote file browser {}
Explanation: None. User Response: None.
ADGU0077W: Error in getting model EJBDataSource attributes Explanation:
None. User Response: None.
ADGU0078W: Cannot
find the EJBServerHome class {0} Explanation: None.
User Response: None.
ADGU0079E: Unable to set application
on session bean Explanation: None. User Response: None.
ADGU0080W: null pointer exception Explanation: None.
User Response: None.
ADGU0081W: Encountered an error
during JMenuCopy construction {0} Explanation: None.
User Response: None.
ADGU0082W: Skipping property {0}.
Encountered an exception on the target: {1} Explanation: None.
User Response: None.
ADGU0083W: Encountered an error
during the getAttributes method {0} Explanation: None.
User Response: None.
ADGU0084W: Cannot find the EnterpriseBeanHome
class {0} Explanation: None. User Response: None.
ADGU0085W: Failed to get related Ids Explanation: None.
User Response: None.
ADGU0086W: Caught NamingException
exception during lookup or narrow {0} Explanation: None.
User Response: None.
ADGU0087W: Invalid row number
{0} selected in {1} table. Explanation: None. User Response:
None.
ADGU0088W: Encountered an exception in the expandBreakdown
method during retrieval process {0} Explanation: None.
User Response: None.
ADGU0089W: Dynamic invocation
target is not a valid Attributes object Explanation: None.
User Response: None.
ADGU0090W: A Remote class or an
Attribute class was not obtained {0} Explanation: None.
User Response: None.
ADGU0091W: Cannot initialize data
{0} Explanation: None. User Response: None.
ADGU0092W: Cannot find a Node type Explanation: None.
User Response: None.
ADGU0093W: Cannot obtain a task
home {0} Explanation: None. User Response: None.
ADGU0094W: RepositoryOpException when getting JDBC driver name {0}
Explanation: None. User Response: None.
ADGU0095E: FnishTask: Unable to set AMProperties Explanation:
None. User Response: None.
ADGU0096W: Cannot
find ServletRedirectorHome Explanation: None. User Response:
None.
ADGU0097W: Cannot obtain the active error list
{0} Explanation: None. User Response: None.
ADGU0099W: Failed to get the size of ring buffer, using 2000K
Explanation: None. User Response: None.
ADGU0101W: Target is not a NodeFileSystemView object {0} Explanation:
None. User Response: None.
ADGU0102W: Encountered
an error in the getJFCIcon method {0} Explanation: None.
User Response: None.
ADGU0103W: Encountered an invalid
deployment descriptor {0} Explanation: None. User Response:
None.
ADGU0104W: Encountered an unexpected exception
during construction of SIDescriptor object {0} Explanation: None.
User Response: None.
ADGU0105W: Encountered an error
while getting attributes {0} Explanation: None. User
Response: None.
ADGU0106W: Cannot narrow a reference
{0} Explanation: None. User Response: None.
ADGU0107W: Cannot set cache size {0} Explanation: None.
User Response: None.
ADGU0108W: Failed to get related
object Explanation: None. User Response: None.
ADGU0109W: Failed to get a FileBrowserServiceBean session bean {0}
Explanation: None. User Response: None.
ADGU0110W: Encountered an error in getting model attributes for an EJB container
{0} Explanation: None. User Response: None.
ADGU0112W: Cannot set the active repository client to null Explanation:
None. User Response: None.
ADGU0113W: Encountered
a null pointer exception {0} Explanation: None. User
Response: None.
ADGU0114W: Encountered an invalid deployment
descriptor Explanation: None. User Response: None.
ADGU0115W: Failed to remove the FileBrowserService session bean {0}
Explanation: None. User Response: None.
ADGU0116W: Cannot get transaction information {0} Explanation:
None. User Response: None.
ADGU0117W: Caught
NamingException exception while getting initial context Explanation:
None. User Response: None.
ADGU0118W: Cannot
find timer for command: {0} Explanation: None. User
Response: None.
ADGU0119W: The filterTypes method was
passed a null pointer Explanation: None. User Response:
None.
ADGU0120W: Cannot find instances of type: {0}
Explanation: None. User Response: None.
ADGU0121W: Error in getting model servletengine attributes Explanation:
None. User Response: None.
ADGU0123W: RepositoryOpException
when getting data source name {0} Explanation: None.
User Response: None.
ADGU0124W: Cannot set a container
attribute {0} Explanation: None. User Response: None.
ADGU0125W: Caught RemoteException exception while getting hostname
Explanation: None. User Response: None.
ADGU0126W: The getRowForObject method was passed a null pointer
Explanation: None. User Response: None.
ADGU0127W: Cannot find SessionMgrHome Explanation: None.
User Response: None.
ADGU0128W: Encountered an error
while executing the ModifyModelAttributesCommand command: {0}
Explanation: None. User Response: None.
ADGU0129W: Cannot set cache hard limit size {0} Explanation: None.
User Response: None.
ADGU0130W: Cannot get attributes
for all instances: {0} {1} Explanation: None. User Response:
None.
ADGU0131W: Cannot complete the clone check {0}
Explanation: None. User Response: None.
ADGU0132W: RepositoryOpException when setting FullName : {0} Explanation:
None. User Response: None.
ADGU0133E: Could
not create resource tree for task Explanation: None.
User Response: None.
ADGU0134W: Encountered an unexpected
constructor arguments. RelationInstance is unusable {0} Explanation:
None. User Response: None.
ADGU0135W: Encountered
an exception {0} Explanation: None. User Response:
None.
ADGU0137W: Enumeration has more than one element.
Explanation: None. User Response: None.
ADGU0138W: Failed to get the child instances for {0} Explanation:
None. User Response: None.
ADGU0139W: Invalid
table number: {0} Explanation: None. User Response:
None.
ADGU0140W: Cannot find refresh icon name from
resource bundle {0} Explanation: None. User Response:
None.
ADGU0141W: Cannot obtain the InvocationHelper
object {0} Explanation: None. User Response: None.
ADGU0142W: Cannot get choice for node Explanation: None.
User Response: None.
ADGU0144W: Command failed to execute
{0} Explanation: None. User Response: None.
ADGU0146W: Encountered an error in getting model attributes for a Session
Mgr {0} Explanation: None. User Response: None.
ADGU0147W: Cannot create a folder {0} {1} Explanation: None.
User Response: None.
ADGU0148W: Enumeration has no
elements. Explanation: None. User Response: None.
ADGU0149W: Failed to get the components for group {0} Explanation:
None. User Response: None.
ADGU0150W: Null
pointer exception Explanation: None. User Response:
None.
ADGU0151W: Cannot find ServletGroupHome
Explanation: None. User Response: None.
ADGU0152W: Cannot find ServletEngineHome Explanation: None.
User Response: None.
ADGU0153W: Cannot initialize a
table row: {0} {1} Explanation: None. User Response:
None.
ADGU0154W: Cannot cast a UIDescriptor object
to a RelationUIDescriptor object. Using default. {0} Explanation:
None. User Response: None.
ADGU0155W: Cannot
set type default attributes. {0} Explanation: None.
User Response: None.
ADGU0157W: Exception in File chooser
while creating servlet Explanation: None. User Response:
None.
ADGU0158W: Encountered an error during the getAttributes
method on a model object {0} Explanation: None. User
Response: None.
ADGU0159W: Encountered an unexpected
error {0} Explanation: None. User Response: None.
ADGU0160W: Cannot create a trace panel {0} Explanation: None.
User Response: None.
ADGU0161W: Failed to refresh relation
info from clientAccess bean Explanation: None. User
Response: None.
ADGU0164W: Cannot request an attribute{0}
{1} Explanation: None. User Response: None.
ADGU0165W: Error in getting model servletRedirector attributes
Explanation: None. User Response: None.
ADGU0166W: Cannot process a RelationAttributes object: {0} {1}
Explanation: None. User Response: None.
ADGU0168W: Cannot get a containment path Explanation: None.
User Response: None.
ADGU0169W: general exception
Explanation: None. User Response: None.
ADGU0171W: Cannot find the ServerHome class {0} Explanation: None.
User Response: None.
ADGU0173W: No Web Applications
found to create servlet under Explanation: None. User
Response: None.
ADGU0174W: Error in getting model Virtual
Host attributes Explanation: None. User Response: None.
ADGU0175W: Encountered an invalid model proxy {0} Explanation:
None. User Response: None.
ADGU0176W: Cannot
process the bean file {0} Explanation: None. User Response:
None.
ADGU0177W: Cannot obtain related objects {0}
Explanation: None. User Response: None.
ADGU0178W: Cannot get type default attributes. {0} Explanation:
None. User Response: None.
ADGU0179W: Encountered
an error in getting repository object for {0} {1} Explanation:
None. User Response: None.
ADGU0180W: Cannot
obtain the clone attributes {0} Explanation: None.
User Response: None.
ADGU0181W: Cannot cast an enumeration
element to the RepositoryObjectInfo class {0} Explanation: None.
User Response: None.
ADGU0182W: RepositoryOpException
when getting FullName : {0} Explanation: None. User
Response: None.
ADGU0183W: Tree selection does not
contain repository object {0} Explanation: None. User
Response: None.
ADGU0184W: Invalid parameters
Explanation: None. User Response: None.
ADGU0185W: Cannot process an event {0} Explanation: None.
User Response: None.
ADGU0186W: Encountered an error
in getting model attributes for a server {0} Explanation: None.
User Response: None.
ADGU0187W: Encountered an error
in getting model attributes for an application {0} Explanation:
None. User Response: None.
ADGU0188W: Invalid
integer specified. Not setting the ring buffer size Explanation:
None. User Response: None.
ADGU0189W: Exception
Explanation: None. User Response: None.
ADGU0190W: Invalid state detected. Updates will be lost Explanation:
None. User Response: None.
ADGU0191W: Cannot
set the timeout for session {0} Explanation: None.
User Response: None.
ADGU0192W: Encountered an error
while executing the ModifyAttributesCommand command: {0} Explanation:
None. User Response: None.
ADGU0193W: Cannot
find UserProfileHome Explanation: None. User Response:
None.
ADGU0194W: Interface class name not set in attributes
Explanation: None. User Response: None.
ADGU0195W: Cannot get an icon name from the NLS key {0} Explanation:
None. User Response: None.
ADGU0196W: Encountered
an error in getting model attributes for a node node {0} Explanation:
None. User Response: None.
ADGU0197W: Cannot
find animated icon name from resource bundle {0} Explanation:
None. User Response: None.
ADGU0198W: Cannot
find the public property editor for property: {0} Explanation:
None. User Response: None.
ADGU0199W: Cannot
get a remote file browser {0} Explanation: None. User
Response: None.
ADGU0200E: Unable to set resource on
session bean Explanation: None. User Response: None.
ADGU0201W: Encountered an exception while firing the RepositoryModelEvent
event {0} Explanation: None. User Response: None.
ADGU0202W: Unable to determine bean type from the deployment descriptor
Explanation: None. User Response: None.
ADGU0203E: CreateButton shouldn't enabled Explanation: None.
User Response: None.
ADGU1000E: Could not get attributes:
Explanation: None. User Response: None.
ADGU1001E: Cannot get attribute class {0} Explanation: None.
User Response: None.
ADGU1002E: Failed to collect attribute
information about: Explanation: None. User Response:
None.
ADGU1003E: Cannot obtain the attribute class:
{0} {1} Explanation: None. User Response: None.
ADGU1004E: No repository object for specified primary key: Explanation:
None. User Response: None.
ADGU1005E: Attributes
for {0} not found in cache. Explanation: None. User
Response: None.
ADGU1006E: Failed to get attributes
for {0} Explanation: None. User Response: None.
ADGU1007W: Attributes returned NULL for {0}. Can not classify modules.
Explanation: None. User Response: None.
ADGU1008E: Cannot get attr module type in ClientOnlyType {0}.
Explanation: None. User Response: None.
ADGU1009E: Exception occurred Explanation: None. User
Response: None.
ADGU1010E: Operation failure
Explanation: None. User Response: None.
ADGU1011E: Active Object failure Explanation: None.
User Response: None.
ADGU1012E: Failed to get the root
instances Explanation: None. User Response: None.
ADGU1013E: Cannot cast an enumeration element to the RepositoryObjectInfo
class {0} Explanation: None. User Response: None.
ADGU1014E: Failed to get the child instances for {0} Explanation:
None. User Response: None.
ADGU1015E: Failed
to get object info from ClientAccess bean {0} Explanation: None.
User Response: None.
ADGU1016E: Cannot narrow a reference
{0} Explanation: None. User Response: None.
ADGU1017E: Failed to refresh relation info from clientAccess bean for {0}
Explanation: None. User Response: None.
ADGU1018E: Failed to remove {0} from parent's children Explanation:
None. User Response: None.
ADGU1019E: RelationInstance
object was badly formed. Parent type is neither source nor target. {0}
Explanation: None. User Response: None.
ADGU1020E: Encountered an unexpected constructor argument. RelationInstance
is unusable {0}. Explanation: None. User Response:
None.
ADGU1021E: Unable to process the relation attributes.
The RelationInstance object is unusable {0}. Explanation: None.
User Response: None.
ADGU1022E: Cannot obtain relation
size {0} Explanation: None. User Response: None.
ADGU1023E: Failed to get related Ids {0} Explanation: None.
User Response: None.
ADGU1024E: Failed to get related
objects {0} Explanation: None. User Response: None.
ADGU1025E: Error during findElement {0} Explanation: None.
User Response: None.
ADGU1026E: Error during isIdentical
{0} Explanation: None. User Response: None.
ADGU1027E: GetAttribute call threw an exception for {0} Explanation:
None. User Response: None.
ADGU1028E: Failed
to get attributes in getState. Explanation: None. User
Response: None.
ADGU1029E: State is not set
Explanation: None. User Response: None.
ADGU1030E: Unexpected Exception from getState Explanation: None.
User Response: None.
ADGU1031E: Cannot get type tree
from type model root {0} Explanation: None. User Response:
None.
ADGU1032E: Could not find specified properties
file: Explanation: None. User Response: None.
ADGU1033E: Encountered an exception during properties initialization {0}
Explanation: None. User Response: None.
ADGU1034E: Could not narrow home reference {0} Explanation: None.
User Response: None.
ADGU1035E: Can not get home for
type object {0}: {1} Explanation: None. User Response:
None.
ADGU1036E: Error getting default attributes for
type object {0} Explanation: None. User Response: None.
ADGU1037E: Error setting default attributes for type object {0}
Explanation: None. User Response: None.
ADGU1038E: Failed to get the type tree Explanation: None.
User Response: None.
ADGU1039E: Failed to get type
information from access bean Explanation: None. User
Response: None.
ADGU1040E: Interface class name not
set in attributes. Explanation: None. User Response:
None.
ADGU1041E: Unable to obtain Repository types
{0} Explanation: None. User Response: None.
ADGU1042E: {0} is not a type instance. Remove failed. Explanation:
None. User Response: None.
ADGU1043E: Cannot
get attributes for instance: {0} due to {1} Explanation: None.
User Response: None.
ADGU1044E: Caught exception while
getting hostname:" Explanation: None. User Response:
None.
ADGU1045E: Caught exception while getting initial
context:" Explanation: None. User Response: None.
ADGU1046E: Could not bind to the Administration Server on {0} due to {1}
Explanation: None. User Response: None.
ADGU1047E: Cannot initialize the repository client. {0} Explanation:
None. User Response: None.
ADGU1048E: Cannot
fully initialize the RepositoryModel object {0} Explanation: None.
User Response: None.
ADGU1049E: Caught NamingException
exception during lookup or narrow of {0} Explanation: None.
User Response: None.
ADGU1050E: Cannot find all nodes.
{0} Explanation: None. User Response: None.
ADGU1051W: No instances of {0} found to remove. Explanation: None.
User Response: None.
ADGU1052I: Choose a {0} to remove.
Explanation: None. User Response: None.
ADGU1053E: has contained objects. Remove cannot be performed.
Explanation: None. User Response: None.
ADGU1054E: Selected object is unknown. Explanation: None.
User Response: None.
ADGU1055E: Selected object is
not startable. Explanation: None. User Response: None.
ADGU1056E: Selected object is not stoppable. Explanation: None.
User Response: None.
ADGU1057E: Invalid ping choice.
Cannot ping a Type. Explanation: None. User Response:
None.
ADGU1058E: Invalid ping choice. Cannot ping a
relationship. Explanation: None. User Response: None.
ADGU1059E: Invalid ping choice Explanation: None. User
Response: None.
ADGU2000E: Cannot find bar updater
for command: {0} Explanation: None. User Response:
None.
ADGU2001E: Cannot find timer for command: {0}
Explanation: None. User Response: None.
ADGU2002E: The clearSubFrame method was passed a null pointer.
Explanation: None. User Response: None.
ADGU2003E: The forceLayout method was passed a null pointer. Explanation:
None. User Response: None.
ADGU2004E: Action
Event without selection in toolbar. {0} Explanation: None.
User Response: None.
ADGU2005E: Action Event without
action object. {0} Explanation: None. User Response:
None.
ADGU2006E: Table selection does not contain RO
{0} Explanation: None. User Response: None.
ADGU2007E: The Administration Client failed to connect to the Administration
Server. Explanation: None. User Response: None.
ADGU2008E: The Administration Client failed to connect to the Administration
Server. Start the local or remote Administration Server service before launching
the Administration Client. Explanation: None. User Response:
None.
ADGU2009E: The Administration Client failed to
authenticate. Please check the username/password. Explanation:
None. User Response: None.
ADGU2010E: Invalid
port number on command line {0} Explanation: None.
User Response: None.
ADGU2011E: The command line is
not valid. The -rootType argument is not correct. Explanation:
None. User Response: None.
ADGU2012E: The
screen resolution must be set to 800x600 or higher. Explanation:
None. User Response: None.
ADGU2013E: Encountered
an exception during properties initialization {0} Explanation:
None. User Response: None.
ADGU2014E: A
browser could not be launched to display help Explanation: None.
User Response: None.
ADGU2015E: Could not start browser
with command: {0} Explanation: None. User Response:
None.
ADGU2016E: Exception occurred launching AAT:
{0} Explanation: None. User Response: None.
ADGU2017E: Action Event without selection in menu bar. {0}");
Explanation: None. User Response: None.
ADGU2018E: Encountered an error while loading class PropertyResourceBundle
from a JAR file {0} Explanation: None. User Response:
None.
ADGU2019E: Null lookup key passed to NLS
Explanation: None. User Response: None.
ADGU2020E: Unable to parse as integer. Explanation: None.
User Response: None.
ADGU2021E: Failed to get runtime
attributes, server may not be reachable Explanation: None.
User Response: None.
ADGU2022E: Exception event fired
with no exception Explanation: None. User Response:
None.
ADGU2023E: Tree selection does not contain repository
object {0} Explanation: None. User Response: None.
ADGU2024E: MakeIcon parameters are not valid. GIF file name or base class
name is null. Explanation: None. User Response: None.
ADGU2025E: Resource is null Explanation: None. User
Response: None.
ADGU2026E: Resource file has zero length
Explanation: None. User Response: None.
ADGU2027E: Encountered an error during the makeIcon method {0}
Explanation: None. User Response: None.
ADGU2028E: Cannot create an icon Explanation: None.
User Response: None.
ADGU2029E: Cannot convert to a
valid date {0} Explanation: None. User Response: None.
ADGU3000W: Encountered an internal error {0} Explanation: None.
User Response: None.
ADGU3001W: Encountered an error
while getting attributes {0} Explanation: None. User
Response: None.
ADGU3002E: CreateButton shouldn't enabled.
Explanation: None. User Response: None.
ADGU3003E: The required name field in the general tab panel has no value.
Enter a value in the name field. Explanation: None.
User Response: None.
ADGU3004E: The required class
name is not entered. Enter a class name. Explanation: None.
User Response: None.
ADGU3005W: Failed to get a FileBrowserServiceBean
session bean {0} Explanation: None. User Response:
None.
ADGU3006W: Error in getting model EJBDataSource
attributes Explanation: None. User Response: None.
ADGU3007E: A datasource cannot be be created without an existing JDBC provider.
Create a JDBC provider first. Explanation: None. User
Response: None.
ADGU3008E: A JDBC provider is not selected.
Select a provider from the JDBC provider drop down list. Explanation:
None. User Response: None.
ADGU3009E: Your
value for the maximum pool size is invalid. This value must not be less than
the value for the Minimum pool size. Explanation: None.
User Response: None.
ADGU3011W: Cannot set dynamic
cache size {0} Explanation: None. User Response: None.
ADGU3012W: Cannot set dynamic cache default priority {0} Explanation:
None. User Response: None.
ADGU3013E: Edit
cannot be invoked. There is no selection in the External cache group table.
Select a group from the table and then click on the Edit button to bring up
the cache group information. Explanation: None. User
Response: None.
ADGU3014E: Failure retrieving the cache
group information. If the problem persists, contact IBM service.
Explanation: None. User Response: None.
ADGU3015E: Remove cannot be invoked. There is no selection in the External
cache group table. Select a group from the table and then click on the Remove
button to remove the selected cache group. Explanation: None.
User Response: None.
ADGU3016E: Please select a group
from the list. Explanation: None. User Response: None.
ADGU3017E: Cache group was not created. A cache group with the same name already
exists. Create a cache group with an unique name. Explanation:
None. User Response: None.
ADGU3018E: You
have entered an invalid value for Cache size. Valid value for this field must
be a positive number. Explanation: None. User Response:
None.
ADGU3019E: You have entered an invalid value
for Default priority. Valid value for this field must be a positive number.
Explanation: None. User Response: None.
ADGU3020W: Cannot set cache size {0} Explanation: None.
User Response: None.
ADGU3021W: Cannot set cache sweep
interval {0} Explanation: None. User Response: None.
ADGU3022W: Encountered an error in getting model attributes for an EJBModule
Explanation: None. User Response: None.
ADGU3023E: Fail to get file browser service home Explanation:
None. User Response: None.
ADGU3024E: Fail
to get RemoteArchiveInfo Explanation: None. User Response:
None.
ADGU3025E: No {0} instances found to create a
new EJBContainer under. Explanation: None. User Response:
None.
ADGU3026E: You must choose a {0} from the node
drop down list before creating an {1}. Explanation: None.
User Response: None.
ADGU3027W: Encountered an error
in getting model attributes for an EJB server {0} Explanation:
None. User Response: None.
ADGU3028E: No
{0} instances found to create a new EJBContainer under. Explanation:
None. User Response: None.
ADGU3029W: Encountered
an error in getting model attributes for an enterprise application {0}
Explanation: None. User Response: None.
ADGU3030E: A J2C Connection Factory cannot be created without an existing
J2C Resource Adapter. Create a J2C Resource Adapter first. Explanation:
None. User Response: None.
ADGU3031E: A
J2C resource adapter is not selected. Select a resource adapter from the J2C
resource adapter drop down list. Explanation: None.
User Response: None.
ADGU3032E: Invalid value entered
for the Maximum connections field. The maximum connections must be greater
than the minimum connections Explanation: None. User
Response: None.
ADGU3033W: Error in getting model J2CConnectionFactory
attributes {0} Explanation: None. User Response: None.
ADGU3034W: Error in getting model J2CResourceAdapter attributes {0}
Explanation: None. User Response: None.
ADGU3035E: The required archive file name has no value. Click on the ellipses
in the button to bring up a file browser to set your archive file.
Explanation: None. User Response: None.
ADGU3036E: Internal error in creating the installed node list. Restart your
Administrator's Console. If the problem persists, contact IBM service.
Explanation: None. User Response: None.
ADGU3037E: The required implementation class has no value. Enter an implementation
class or click on the ellipses in the button to bring up a selection list.
Explanation: None. User Response: None.
ADGU3038W: Encountered an error in getting model attributes for JDBC provider
{0} Explanation: None. User Response: None.
ADGU3039E: A JMS Connection Factory cannot be created without an existing
JMS Provider. Please create a JMS Provider first. Explanation:
None. User Response: None.
ADGU3040E: The
required external JNDI path has no value. Enter a value in the external JNDI
path field. Explanation: None. User Response: None.
ADGU3041E: The connection type is not selected. Select a connection type.
Explanation: None. User Response: None.
ADGU3042E: The required JMS provider has no value. Select a provider from
the JMS provider drop down list. Explanation: None.
User Response: None.
ADGU3043W: Encountered an error
in getting model attributes for JMS connection factory {0} Explanation:
None. User Response: None.
ADGU3044E: A
JMS Destination cannot be created without an existing JMS Provider. Please
create a JMS Provider first. Explanation: None. User
Response: None.
ADGU3045E: The destination type is
not selected. Select a destination type. Explanation: None.
User Response: None.
ADGU3046W: Error in getting model
attributes for JMS destination {0} Explanation: None.
User Response: None.
ADGU3047E: The required context
factory classname has no value. Enter a value in the context factory clansman
field. Explanation: None. User Response: None.
ADGU3048E: The required provider URL has no value. Enter a value in the provider
URL field. Explanation: None. User Response: None.
ADGU3049W: Error in getting model attributes for JMS provider {0}
Explanation: None. User Response: None.
ADGU3050E: The required server name for outgoing mail has no value. Enter
a value in the server field for outgoing mail. Explanation: None.
User Response: None.
ADGU3051E: Missing protocol value
for mail store access. You have enabled Mail store access. Enter or select
a protocol from the drop down list. Explanation: None.
User Response: None.
ADGU3052E: Missing host value
for mail store access. You have enabled Mail store access. Enter a host value.
Explanation: None. User Response: None.
ADGU3053E: Missing user name value for mail store access. You have enabled
Mail store access. Enter a user name. Explanation: None.
User Response: None.
ADGU3054E: Missing password value
for mail store access. You have enabled Mail store access. Enter a password.
Explanation: None. User Response: None.
ADGU3055W: Error in getting model attributes for JavaMail session {0}
Explanation: None. User Response: None.
ADGU3056W: Encountered an invalid model proxy {0} Explanation:
None. User Response: None.
ADGU3057E: This
node is already installed with this Provider. To change an existing installation,
uninstall the existing node installation first before installing another one.
Explanation: None. User Response: None.
ADGU3058E: You have entered an invalid value for {0}. Valid value for this
input must be between 0 and {1} Explanation: None.
User Response: None.
ADGU3059E: Your value for the
maximum connection cache size is invalid. This value must be bigger than the
value for the Minimum connection cache size. Explanation: None.
User Response: None.
ADGU3060W: Skipping property {0}.
Encountered an exception on the target: {1} Explanation: None.
User Response: None.
ADGU3061W: Skipping property {0}.
Encountered an exception: {1} Explanation: None. User
Response: None.
ADGU3062W: Cannot find the public property
editor for property: {0} Explanation: None. User Response:
None.
ADGU3063W: Property {0} has a null initial value.
Explanation: None. User Response: None.
ADGU3064W: Property {0} has a non-displayable editor. Skipping.
Explanation: None. User Response: None.
ADGU3065W: Cannot obtain an attribute descriptor {0} Explanation:
None. User Response: None.
ADGU3066W: Property
change was vetoed: {0} Explanation: None. User Response:
None.
ADGU3067W: Failed to get a FileBrowserServiceBean
session bean {0} Explanation: None. User Response:
None.
ADGU3068E: Wrong Resource Type Explanation:
None. User Response: None.
ADGU3069E: This
resource driver is already installed in this node. Explanation:
None. User Response: None.
ADGU3070E: The
required executable field has no value. Enter a value in the executable field.
Explanation: None. User Response: None.
ADGU3071W: Encountered an error in getting model attributes for a server {0}
Explanation: None. User Response: None.
ADGU3072E: Session tracking mechanism is not selected. Select at least one
tracking mechanism. Explanation: None. User Response:
None.
ADGU3073E: Cookie maximum age has no value. You
have selected to set maximum cookie age. Enter a valid value in the cookie
age field. Explanation: None. User Response: None.
ADGU3074E: You have entered an invalid value for cookie maximum age. Enter
a positive numeric value for this field. Explanation: None.
User Response: None.
ADGU3075E: Invalidation timeout
has no value. You have selected to set the invalidation timeout. Enter a valid
value in the timeout field. Explanation: None. User
Response: None.
ADGU3076E: You have entered an invalid
value for invalidation timeout. Valid value for this field must be a number
greater than 2. Explanation: None. User Response: None.
ADGU3077E: You have entered an invalid value for the cleanup schedules. Value
for these fields must be between 0 and 23. Explanation: None.
User Response: None.
ADGU3078E: You have entered invalid
values for the cleanup schedules. Schedule one must be earlier or equal to
schedule two. Explanation: None. User Response: None.
ADGU3079E: You have entered an invalid value for time based write frequency.
Valid value for this field must be a positive numeric value. Explanation:
None. User Response: None.
ADGU3080E: You
have entered an invalid value for maximum in memory session count. Valid value
for this field must be a positive numeric value. Explanation:
None. User Response: None.
ADGU3081E: A
URL cannot be be created without an existing URL Provider. Create a URL Provider
first. Explanation: None. User Response: None.
ADGU3082E: The required URL has no value. Enter a value in the URL field.
Explanation: None. User Response: None.
ADGU3083E: The required URL provider has no value. Select a URL Provider from
the drop down list. Explanation: None. User Response:
None.
ADGU3084W: Error in getting model attributes
for URL {0} Explanation: None. User Response: None.
ADGU3085E: The required protocol has no value. Enter a value in the protocol
field. Explanation: None. User Response: None.
ADGU3086E: The required steam handler class has no value. Enter a value in
the stream handler class field. Explanation: None.
User Response: None.
ADGU3087E: Specify a unique MIME
TYPE Explanation: None. User Response: None.
ADGU3088E: Specify at least one EXTENSION Explanation: None.
User Response: None.
ADGU3089W: Error in getting model
Virtual Host attributes Explanation: None. User Response:
None.
ADGU3090W: Encountered an error in getting model
attributes for an WebModule Explanation: None. User
Response: None.
ADGU3091E: You have entered an invalid
value for minimum thread size. Valid value for this field must be a positive
numeric value. Explanation: None. User Response: None.
ADGU3092E: You have entered an invalid value for maximum thread size. Valid
value for this field must be a positive numeric value. Explanation:
None. User Response: None.
ADGU3093E: You
have entered an invalid value for thread inactivity timeout. Valid value for
this field must be a positive numeric value. Explanation: None.
User Response: None.
ADGU3094W: Cannot set thread minimum
size {0} Explanation: None. User Response: None.
ADGU3095W: Cannot set thread maximum size {0} Explanation: None.
User Response: None.
ADGU3096W: Cannot set thread inactivity
timeout {0} Explanation: None. User Response: None.
ADGU3097E: No {0} instance found to create a new Node under. Explanation:
None. User Response: None.
ADGU3098W: Encountered
an error in getting model attributes for a node {0} Explanation:
None. User Response: None.
ADGU3109E: You
have entered an invalid value for {0}. Valid value for this input must be
a positive number. Explanation: None. User Response:
None.
ADGU3170E: You must choose a {0} prior to creating
a {1}. Explanation: None. User Response: None.
ADGU3186W: Error in getting model attributes for URL provider {0}
Explanation: None. User Response: None. ADMR0100E: Attribute does not
exist: {0}. Explanation: None. User Response: None.
ADMR0200W: Unable to get install location on node {0} for ear file
Explanation: None. User Response: None.
ADMR0201W: Module does not have a relative URI. Explanation: None.
User Response: None.
ADMR0202W: Application has no
binding. Explanation: None. User Response: None.
ADMR0203W: Null EJB jar. Explanation: None. User Response:
None.
ADMR0204W: Null web app. Explanation:
None. User Response: None.
ADMR0205W: Unknown
module type - jar or war required. Explanation: None.
User Response: None.
ADMR0206W: Can not find link {0}
for EJB ref. Explanation: None. User Response: None.
ADMR0207W: Can not resolve internal refs. Explanation: None.
User Response: None.
ADMR0208W: Can not change the
original ear file. Explanation: None. User Response:
None.
ADMR0209W: Cannot change the node name for the
original Ear file. Explanation: None. User Response:
None.
ADMR0300E: Failed to deploy J2C resource adapter
archive file: {0}. Explanation: None. User Response:
None.
ADMR0400E: Database select failed to find JDBC
driver instance {0} in table {1}. Explanation: None.
User Response: None.
ADMR0401E: Database select failed
because of {0}. Explanation: None. User Response: None.
ADMR0402E: Database findAll failed due to {0} on table {1}. Explanation:
None. User Response: None.
ADMR0403E: Database
findAll failed due to {0}. Explanation: None. User Response:
None.
ADMR0404E: Database findByName failed due to
{0} on table {1}. Explanation: None. User Response:
None.
ADMR0405E: Database findByName failed due to
{0}. Explanation: None. User Response: None.
ADMR0406E: Database update failed due to {0} for statement with name = {1},
implClass = {2}, urlPrefix = {3}, id = {4}. Explanation: None.
User Response: None.
ADMR0407E: Database update failed
due to {0}. Explanation: None. User Response: None.
ADMR0408E: Database delete failed due to {0} for primary key {1}.
Explanation: None. User Response: None.
ADMR0409E: Database delete failed due to {0}. Explanation: None.
User Response: None.
ADMR0410E: Database insert failed
due to {0} for statement with name = {1}, implClass = {2}, urlPrefix = {3},
id = {4} typeId = {5}. Explanation: None. User Response:
None.
ADMR0411E: Database insert failed due to {0}.
Explanation: None. User Response: None.
ADMR0412E: Database could not create table {0} because of {1}.
Explanation: None. User Response: None.
ADMR0413E: Attribute {0} does not exist. Explanation: None.
User Response: None.
ADMR0414E: Attribute {0} is not
set. Explanation: None. User Response: None.
ADMR0415E: Could not update the instance variables. Explanation:
None. User Response: None.
ADMR0416E: Could
not initialize the instance variables. Explanation: None.
User Response: None.
ADMR0417E: An operation exception
occurred. Explanation: None. User Response: None.
ADMR0418E: Could not change the name of attribute. Explanation:
None. User Response: None.
ADMR0500E: ApplicationBean
select failed to find application instance {0} in table {1}. Explanation:
None. User Response: None.
ADMR0501E: ApplicationBean
select failed because of {0}. Explanation: None. User
Response: None.
a>ADMR0502E: ApplicationBean findAll
failed due to {0} on table {1}. Explanation: None.
User Response: None.
ADMR0503E: ApplicationBean findAll
failed due to {0}. Explanation: None. User Response:
None.
ADMR0504E: ApplicationBean findByName failed
due to {0} on table {1}. Explanation: None. User Response:
None.
ADMR0505E: ApplicationBean findByName failed
due to {0}. Explanation: None. User Response: None.
ADMR0506E: ApplicationBean update failed due to {0} for statement with name
= {1} id = {2}. Explanation: None. User Response: None.
ADMR0507E: ApplicationBean update failed due to {0}. Explanation:
None. User Response: None.
ADMR0508E: ApplicationBean
delete failed due to {0} for primary key {1}. Explanation: None.
User Response: None.
ADMR0509E: ApplicationBean delete
failed due to {0}. Explanation: None. User Response:
None.
ADMR0510E: ApplicationBean insert failed due
to {0} for statement id = {1} typeId = {2}. Explanation: None.
User Response: None.
ADMR0511E: ApplicationBean insert
failed due to {0}. Explanation: None. User Response:
None.
ADMR0512E: ApplicationBean could not create table
{0} because of {1}. Explanation: None. User Response:
None.
ADMR0513E: Attribute {0} does not exist.
Explanation: None. User Response: None.
ADMR0514E: Attribute {0} is not set. Explanation: None.
User Response: None.
ADMR0515E: Attribute could not
be set. Explanation: None. User Response: None.
ADMR0516E: An operation exception occurred. Explanation: None.
User Response: None.
ADMR0517E: Could not update the
instance variables. Explanation: None. User Response:
None.
ADMR0600E: DataSourceBean select failed to find
application instance {0} in table {1}. Explanation: None.
User Response: None.
ADMR0601E: DataSourceBean select
failed because of {0}. Explanation: None. User Response:
None.
ADMR0602E: DataSourceBean findAll failed due
to {0} on table {1}. Explanation: None. User Response:
None.
ADMR0603E: DataSourceBean findAll failed due
to {0}. Explanation: None. User Response: None.
ADMR0604E: DataSourceBean findByName failed due to {0} on table {1}.
Explanation: None. User Response: None.
ADMR0605E: DataSourceBean findByName failed due to {0}. Explanation:
None. User Response: None.
ADMR0606E: DataSourceBean
update failed due to {0} for statement with name = {1} DBName = {2} id = {3}.
Explanation: None. User Response: None.
ADMR0607E: DataSourceBean update failed due to {0}. Explanation:
None. User Response: None.
ADMR0608E: DataSourceBean
delete failed due to {0} for primary key {1}. Explanation: None.
User Response: None.
ADMR0609E: DataSourceBean delete
failed due to {0}. Explanation: None. User Response:
None.
ADMR0610E: DataSourceBean insert failed due to
{0} for statement id = {1} DBName = {2} typeId = {3}. Explanation:
None. User Response: None.
ADMR0611E: DataSourceBean
insert failed due to {0}. Explanation: None. User Response:
None.
ADMR0612E: DataSourceBean could not create table
{0} because of {1}. Explanation: None. User Response:
None.
ADMR0613E: Attribute {0} does not exist.
Explanation: None. User Response: None.
ADMR0614E: Attribute {0} is not set. Explanation: None.
User Response: None.
ADMR0615E: Could not update the
instance variables. Explanation: None. User Response:
None.
ADMR0616E: An operation exception occurred.
Explanation: None. User Response: None.
ADMR0617E: Could not initialize the instance variables. Explanation:
None. User Response: None.
ADMR0618E: Invalid
JDBC driver specified. Explanation: None. User Response:
None.
ADMR0619E: Could not delete from the JNDI namespace.
Explanation: None. User Response: None.
ADMR0620E: Could not insert into the J.NDI namespace. Explanation:
None. User Response: None.
ADMR0621E: Could
not get the JDBC driver. Explanation: None. User Response:
None.
ADMR0622E: Could not change the name of attribute.
Explanation: None. User Response: None.
ADMR1000E: Valid provider must be specified to create this resource.
Explanation: None. User Response: None.
ADMR1001E: Valid name attribute must be specified to create this resource.
Explanation: None. User Response: None.
ADMR1002E: Failed to create relationship between resource and its provider:
{0} Explanation: None. User Response: None.
ADMR1003E: Exception occurred while changing JNDI name from {0} to {1}.
Explanation: None. User Response: None.
ADMR1004E: Exception occurred while updating JNDI binding for {0}.
Explanation: None. User Response: None.
ADMR1005E: Could not get resource provider for {0}. Explanation:
None. User Response: None.
ADMR1500E: Database
insert failed: {0} Explanation: None. User Response:
None.
ADMR1501E: Database query failed: {0}
Explanation: None. User Response: None.
ADMR1502E: Database read failed: {0} Explanation: None.
User Response: None.
ADMR1503E: Database update failed:
{0} Explanation: None. User Response: None.
ADMR1504E: Database delete failed: {0} Explanation: None.
User Response: None.
ADMR1505E: Database table {0}
creation failed: {1} Explanation: None. User Response:
None.
ADMR1506E: Find all in {0} failed: {1}.
Explanation: None. User Response: None.
ADMR1507E: Find by name for {0} failed: {1}. Explanation: None.
User Response: None.
ADMR1508E: Find by JNDI name for
{0} failed: {1}. Explanation: None. User Response:
None.
ADMR1516E: An operation exception occurred.
Explanation: None. User Response: None.
ADMR1517E: Caught attribute not set exception: {0}. Explanation:
None. User Response: None.
ADMR1518E: Could
not initialize attributes: {0}. Explanation: None.
User Response: None.
ADMR1519E: Could not find FileBrowserServiceHome.
Explanation: None. User Response: None.
ADMR1520E: Failed to obtain FileBrowserService. Explanation: None.
User Response: None.
ADMR2000E: getActiveObjectName
not implemented Explanation: None. User Response: None.
ADMR2001E: GetConfiguration not implemented Explanation: None.
User Response: None.
ADMR2100E: Operation not implemented,
but you should not see this exception Explanation: None.
User Response: None.
ADMR2200E: Invalid attributes
class provided: Explanation: None. User Response: None.
ADMR2201E: incrementConfigNo: Clone is not part of model Explanation:
None. User Response: None.
ADMR2202E: Inapplicable
attributes provided for root clone instance Explanation: None.
User Response: None.
ADMR2203E: DesiredState does not
exist for Models Explanation: None. User Response:
None.
ADMR2204E: CurrentState does not exist for Models
Explanation: None. User Response: None.
ADMR2205E: GetNode not implemented for Models Explanation: None.
User Response: None.
ADMR2206E: Inapplicable attributes
provided for model instance Explanation: None. User
Response: None.
ADMR2207E: CloneInterface type does
not exist in the repository Explanation: None. User
Response: None.
ADMR2208E: ListClones of containingModel
failed: Explanation: None. User Response: None.
ADMR2209E: CloneInstance is not of the given clone type specified for this
model instance Explanation: None. User Response: None.
ADMR2210E: Attribute does not exist. Explanation: None.
User Response: None.
ADMR2210E: ListClones of containingModel
failed: Explanation: None. User Response: None.
ADMR2210W: Encountered a bad implementation of a ModelAttributes object in
the setAttributes method: {0} Explanation: None. User
Response: None.
ADMR2211E: Attribute is not set.
Explanation: None. User Response: None.
ADMR2211W: Attribute is set but the get method failed in the setAttributes
method {0} Explanation: None. User Response: None.
ADMR2212W: Unexpected exception in pushModelChangesForWLM Explanation:
None. User Response: None.
ADMR2213W: Model
not found Explanation: None. User Response: None.
ADMR2250E: ModelBean select failed to find model instance {0} in table {1}.
Explanation: None. User Response: None.
ADMR2251E: ModelBean select failed because of {0}. Explanation:
None. User Response: None.
ADMR2252E: ModelBean
findAll failed due to {0} on table {1}. Explanation: None.
User Response: None.
ADMR2253E: ModelBean findAll failed
due to {0}. Explanation: None. User Response: None.
ADMR2254E: ModelBean findByName failed due to {0} on table {1}.
Explanation: None. User Response: None.
ADMR2255E: ModelBean delete failed due to {0} for id = {1}. Explanation:
None. User Response: None.
ADMR2255E: ModelBean
findByName failed due to {0}. Explanation: None. User
Response: None.
ADMR2256E: ModelBean delete failed
due to {0}. Explanation: None. User Response: None.
ADMR2257E: ModelBean insert failed due to {0} for statement id = {1} name
= {2} typeId = {3}. Explanation: None. User Response:
None.
ADMR2258E: ModelBean insert failed due to {0}.
Explanation: None. User Response: None.
ADMR2259E: ModelBean could not create table {0} because of {1}.
Explanation: None. User Response: None.
ADMR2300W: Unexpected WLMBootstrapException in ejbRemove Explanation:
None. User Response: None.
ADMR2310E: NodeBean
select failed to find node instance {0} in table {1}. Explanation:
None. User Response: None.
ADMR2311E: NodeBean
select failed because of {0}. Explanation: None. User
Response: None.
ADMR2312E: NodeBean findAll failed
due to {0} on table {1}. Explanation: None. User Response:
None.
ADMR2313E: NodeBean findAll failed due to {0}.
Explanation: None. User Response: None.
ADMR2314E: NodeBean findByName failed due to {0} on table {1}.
Explanation: None. User Response: None.
ADMR2315E: NodeBean findByName failed due to {0}. Explanation:
None. User Response: None.
ADMR2316E: NodeBean
delete failed due to {0} for id = {1}. Explanation: None.
User Response: None.
ADMR2317E: NodeBean delete failed
due to {0}. Explanation: None. User Response: None.
ADMR2318E: NodeBean insert failed due .to {0} for statement id = {1} name
= {2} typeId = {3}. Explanation: None. User Response:
None.
ADMR2319E: NodeBean insert failed due to {0}.
Explanation: None. User Response: None.
ADMR2320E: NodeBean could not create table {0} because of {1}.
Explanation: None. User Response: None.
ADMR2321E: Attribute {0} does not exist. Explanation: None.
User Response: None.
ADMR2322E: Attribute {0} is not
set. Explanation: None. User Response: None.
ADMR2323E: invalid node name Explanation: None. User
Response: None.
ADMR2324E: unexpected exception when
validating name Explanation: None. User Response: None.
ADMR2400E: Serious Event table corrupted Explanation: None.
User Response: None.
ADMR2401E: Invalid Serious Event
table size Explanation: None. User Response: None.
ADMR2500E: Invalid attributes class provided Explanation: None.
User Response: None.
ADMR2501E: IncrementConfigNo:
Clone is not part of Server Group Explanation: None.
User Response: None.
ADMR2502E: Inapplicable attributes
provided for root clone instance Explanation: None.
User Response: None.
ADMR2503E: Cannot create Server
Clone Explanation: None. User Response: None.
ADMR2504E: Problem in getting ear file location Explanation: None.
User Response: None.
ADMR2505E: Could not get FileBrowserServiceHome
Explanation: None. User Response: None.
ADMR2505E: Error in getting parent EnterpriseApp Explanation:
None. User Response: None.
ADMR2507E: The
.ear file name is empty Explanation: None. User Response:
None.
ADMR2508E: Failed to create FileBrowserService
remote object or call methods on it Explanation: None.
User Response: None.
ADMR2509E: DesiredState does not
exist for Server Groups Explanation: None. User Response:
None.
ADMR2510E: GetNode not implemented for Server
Groups Explanation: None. User Response: None.
ADMR2511E: CurrentState does not exist for Server Groups Explanation:
None. User Response: None.
ADMR2512E: Inapplicable
attributes provided for server group instance Explanation: None.
User Response: None.
ADMR2513E: CloneInterface type
does not exist in the repository Explanation: None.
User Response: None.
ADMR2514E: Problem in ejbPostCreate
while creating clones Explanation: None. User Response:
None.
ADMR2515E: Cannot list clones of ServerGroup
Explanation: None. User Response: None.
ADMR2516E: No ejbServerModuleRel is found Explanation: None.
User Response: None.
ADMR2530W: Encountered a bad implementation
of a ServerGroupAttributes object in the setAttributes method: {0}
Explanation: None. User Response: None.
ADMR2531W: Attribute is set but the get method failed in the setAttributes
method {0} Explanation: None. User Response: None.
ADMR2532W: Unexpected exception in pushServerGroupChangesForWLM
Explanation: None. User Response: None.
ADMR2700E: Cannot find the installed Server Explanation: None.
User Response: None.
ADMR2701E: reinstall - exception
to update ServerModule relation Explanation: None.
User Response: None.
ADMR2702E: Server is initializing
or lost contact Explanation: None. User Response: None.
ADMR2703E: Problem in starting the Module Explanation: None.
User Response: None.
ADMR2704E: Problem in stopping
the Module Explanation: None. User Response: None.
ADMR2705E: Empty ServerGroup with no Servers Explanation: None.
User Response: None.
ADMR2706E: Problem in getting
containment path for Module Explanation: None. User
Response: None.
ADMR2707E: Database create table failed.
Explanation: None. User Response: None.
ADMR2708E: Database update failed to store Module attributes (id={0}).
Explanation: None. User Response: None.
ADMR2709E: Database delete failed to remove Module instance (id={0}).
Explanation: None. User Response: None.
ADMR2710E: Database insert failed to store new Module instance (id={0}).
Explanation: None. User Response: None.
ADMR2711E: Database select failed to find Module instance (id={0}).
Explanation: None. User Response: None.
ADMR2712E: Database select failed. Explanation: None.
User Response: None.
ADMR2713E: Database select failed
to find all instances of Module. Explanation: None.
User Response: None.
ADMR2714E: Exception occurred
initializing default Module attributes. Explanation: None.
User Response: None.
ADMR2715E: Required Module name
attribute was not specified. Explanation: None. User
Response: None.
ADMR2716E: Required attribute for Module
was not input. Explanation: None. User Response: None.
ADMR2717E: Input attribute does not exist for a Module. Explanation:
None. User Response: None.
ADMR2718E: An
error occurred creating the Server --> Module relation : {0}.
Explanation: None. User Response: None.
ADMR2719E: Could not find VirtualHost (name={0}). Explanation:
None. User Response: None.
ADMR2720E: No
web application binding exists for Web Module : {0}. Explanation:
None. User Response: None.
ADMR2721E: No
configured resource was found for the input Module binding : {0}.
Explanation: None. User Response: None.
ADMR2722E: An error occurred creating the {0} to {1} relation.
Explanation: None. User Response: None.
ADMR2723E: No VirtualHost binding exists for Web Module : {0}.
Explanation: None. User Response: None.
ADMR2750W: No name was found for the Enterprise Application that contains
this Module Explanation: None. User Response: None.
ADMR2751W: An Enterprise Application was not found for the Module
Explanation: None. User Response: None.
ADMR2752W: An Enterprise Application was not found for the Module
Explanation: None. User Response: None.
ADMR2753W: Resource reference for JNDI name {0} has no Resource Type value.
A default type of {1} has been assigned Explanation: None.
User Response: None.
ADMR2754W: Server-to-Module Relation
delete failed! Explanation: None. User Response: None.
ADMR2755W: Problem in starting the Module Explanation: None.
User Response: None.
ADMR2756W: Problem in stopping
the Module Explanation: None. User Response: None.
ADMR2800W: Encountered an error during the getROname method Explanation:
None. User Response: None.
ADMR2900E: ServerBean
stop operation exception {0}. Explanation: None. User
Response: None.
ADMR2900W: Failed to reconnect to a
server: {0}. No PID available Explanation: None. User
Response: None.
ADMR2901E: ServerBean select failed
to. find server instance {0} in table {1}. Explanation: None.
User Response: None.
ADMR2901W: Failed to reconnect
to a server: {0} {1} Explanation: None. User Response:
None.
ADMR2902E: ServerBean select failed because of
{0}. Explanation: None. User Response: None.
ADMR2903E: ServerBean update failed due to {0} for statement with id = {1}.
Explanation: None. User Response: None.
ADMR2904E: ServerBean update failed due to {0}. Explanation: None.
User Response: None.
ADMR2905E: SeverBean delete failed
due to {0} for id = {1}. Explanation: None. User Response:
None.
ADMR2906E: SeverBean delete failed due to {0}.
Explanation: None. User Response: None.
ADMR2907E: ServerBean insert failed due to {0} for statement with id = {1}
typeId = {2}. Explanation: None. User Response: None.
ADMR2908E: ServerBean insert failed due to {0}. Explanation: None.
User Response: None.
ADMR2910E: ServerBean findAll
failed due to {0} on table {1}. Explanation: None.
User Response: None.
ADMR2911E: ServerBean findAll
failed due to {0}. Explanation: None. User Response:
None.
ADMR2912E: ServerBean could not create table
{0} because of {1}. Explanation: None. User Response:
None.
ADMR2913E: ServerBean could not initialize because
of {0}. Explanation: None. User Response: None.
ADMR2914E: Attribute does not exist. Explanation: None.
User Response: None.
ADMR2915E: Attribute is not set.
Explanation: None. User Response: None.
ADMR3000E: EJBServerBean select failed to find server instance {0} in table
{1}. Explanation: None. User Response: None.
ADMR3001E: EJBServerBean detected a relation operation exception.
Explanation: None. User Response: None.
ADMR3002E: EJBServerBean detected a missing object exception.
Explanation: None. User Response: None.
ADMR3003E: EJBServerBean select failed because of {0}. Explanation:
None. User Response: None.
ADMR3004E: EJBServerBean
update failed. due to {0} for statement with id = {1}. Explanation:
None. User Response: None.
ADMR3005E: EJBServerBean
update failed due to {0}. Explanation: None. User Response:
None.
ADMR3006E: EJBServerBean delete failed due to
{0} for id = {1}. Explanation: None. User Response:
None.
ADMR3007E: EJBServerBean delete failed due to
{0}. Explanation: None. User Response: None.
ADMR3008E: EJBServerBean insert failed due to {0} for statement with id =
{1} typeId = {2}. Explanation: None. User Response:
None.
ADMR3009E: EJBServerBean insert failed due to
{0}. Explanation: None. User Response: None.
ADMR3010E: EJBServerBean findAll failed due to {0} on table {1}.
Explanation: None. User Response: None.
ADMR3011E: EJBServerBean findAll failed due to {0}. Explanation:
None. User Response: None.
ADMR3012E: EJBServerBean
could not create table {0} because of {1}. Explanation: None.
User Response: None.
ADMR3013E: EJBServerBean could
not initialize because of {0}. Explanation: None. User
Response: None.
ADMR3014E: Attribute does not exist.
Explanation: None. User Response: None.
ADMR3015E: Attribute is not set. Explanation: None.
User Response: None.
ADMR3016E: Failed to get the server
group name Explanation: None. User Response: None.
ADMR3017E: Exception occurred while finding datasource {0}. Explanation:
None. User Response: None.
ADMR3018E: Exception
occurred while finding SecurityConfig bean. Explanation: None.
User Response: None.
ADMR3019W: Failed to reconnect
to EJB server {0}; No IOR is available. Explanation: None.
User Response: None.
ADMR3020W: Failed to reconnect
to EJB server {0}: {1} Explanation: None. User Response:
None.
ADMR3021E: Error removing EJB server's module
relationships. Explanation: None. User Response: None.
ADMR3022E: Problem in module.stoppingContainerObject. Explanation:
None. User Response: None.
ADMR3100E: RelationBean
could not create table {0} because of {1}. Explanation: None.
User Response: None.
ADMR3101E: RelationBean select
failed to find relation instance {0} in table {1}. Explanation:
None. User Response: None.
ADMR3102E: RelationBean
select failed because of {0}. Explanation: None. User
Response: None.
ADMR3103E: RelationBean findAllInstanc.es
failed due to {0} on table for relID = {1}. Explanation: None.
User Response: None.
ADMR3104E: RelationBean findAllInstances
failed due to {0}. Explanation: None. User Response:
None.
>ADMR3105E: RelationBean findAll failed due to
{0} on table {1}. Explanation: None. User Response:
None.
ADMR3106E: RelationBean findAll failed due to
{0}. Explanation: None. User Response: None.
ADMR3107E: RelationBean findByName failed due to {0} on table {1}.
Explanation: None. User Response: None.
ADMR3108E: RelationBean findByName failed due to {0}. Explanation:
None. User Response: None.
ADMR3109E: RelationBean
findBySource failed due to {0} for srcType {1}. Explanation: None.
User Response: None.
ADMR3110E: RelationBean findBySource
failed due to {0}. Explanation: None. User Response:
None.
ADMR3111E: RelationBean findByTarget failed due
to {0} for targetType {1}. Explanation: None. User Response:
None.
ADMR3112E: RelationBean findByTarget .failed
due to {0}. Explanation: None. User Response: None.
ADMR3113E: RelationBean findByEndpoints failed due to {0} for srcType {1}
targetType {2}. Explanation: None. User Response: None.
ADMR3114E: RelationBean findByEndpoints failed due to {0}. Explanation:
None. User Response: None.
ADMR3115E: RelationBean
update failed due to {0} for statement with id = {1} srcID = {2} and targetID
= {3}. Explanation: None. User Response: None.
ADMR3116E: RelationBean update failed due to {0}. Explanation:
None. User Response: None.
ADMR3117E: RelationBean
delete failed due to {0} for id = {1}. Explanation: None.
User Response: None.
ADMR3118E: RelationBean delete
failed due to {0}. Explanation: None. User Response:
None.
ADMR3119E: RelationBean ejbCreate exception because
of non-existent attribute {0}. Explanation: None. User
Response: None.
ADMR3120E: RelationBean insert failed
due to {0} for statement id = {1} name = {2} typeId = {3}. Explanation:
None. User Response: None.
ADMR3121E: RelationBean
insert failed due to {0}. Explanation: None. User Response:
None.
ADMR3122E: ServerBean could not create table
{0} because of {1}. Explanation: None. User Response:
None.
ADMR3123E: RelationBean object traversal failed
due to {0} for srcId {1}. Explanation: None. User Response:
None.
ADMR3124E: RelationBean object traversal failed
due to {0}. Explanation: None. User Response: None.
ADMR3125E: RelationBean object traversal failed due to {0} for srcId {1} and
name {2}. Explanation: None. User Response: None.
ADMR3126E: RelationBean object addition failed due to {0} for id {1} srcId
{2} and targetId {3}. Explanation: None. User Response:
None.
ADMR3127E: RelationBean object addition failed
due to {0}. Explanation: None. User Response: None.
ADMR3128E: RelationBean object check failed due to {0} for id {1} srcId {2}
and targetId {3}. Explanation: None. User Response:
None.
ADMR3129E: RelationBean object check failed due
to {0}. Explanation: None. User Response: None.
ADMR3130E: RelationBean object deletion failed due to {0} for id {1} srcId
{2} and targetId {3}. Explanation: None. User Response:
None.
ADMR3131E: RelationBean object deletion failed
due to {0}. Explanation: None. User Response: None.
ADMR3132E: RelationBean named object deletion failed due to {0} for srcId
{1} and name {2}. Explanation: None. User Response:
None.
ADMR3133E: RelationBean named object deletion
failed due to {0}. Explanation: None. User Response:
None.
ADMR3134E: RelationBean object deletion failed
due to {0} for name {1} srcId {2} and targetId {3}. Explanation:
None. User Response: None.
ADMR3135E: RelationBean
object deletion failed due to {0}. Explanation: None.
User Response: None.
ADMR3136E: RelationBean object
listing failed due to {0} for srcId {1}. Explanation: None.
User Response: None.
ADMR3137E: RelationBean object
listing failed due to {0}. Explanation: None. User Response:
None.
ADMR3138E: RelationBean object listing failed
due to {0} for srcId {1} and name {2}. Explanation: None.
User Response: None.
ADMR3139E: RelationBean object
listing failed due to {0}. Explanation: None. User Response:
None.
ADMR3140E: RelationBean object listing failed
due to no named relation. Explanation: None. User Response:
None.
ADMR3141E: RelationBean object listing by name
failed due to {0} for Id {1} and srcId {2}. Explanation: None.
User Response: None.
ADMR3142E: RelationBean object
listing by name failed due to {0}. Explanation: None.
User Response: None.
ADMR3143E: RelationBean object
listing failed due to {0} for source {1} and target {2}. Explanation:
None. User Response: None.
ADMR3144E: RelationBean
object listing failed due to {0}. Explanation: None.
User Response: None.
ADMR3145E: RelationBean object
listing by name failed due to {0} for name {1}. Explanation: None.
User Response: None.
-->ADMR3146E:
RelationBean setAttributes failed due to {0}. Explanation: None.
User Response: None.
ADMR3200E: RepositoryObjectImpl
could not initialize the instance because of {0}. Explanation:
None. User Response: None.
ADMR3201E: RepositoryObjectImpl
could not insert duplicate key {0} because of {1}. Explanation:
None. User Response: None.
ADMR3202E: RepositoryObjectImpl
could not create table {0} because of {1}. Explanation: None.
User Response: None.
ADMR3203E: RepositoryObjectImpl
could initialize because of {0}. Explanation: None.
User Response: None.
ADMR3204E: RepositoryObjectImpl
findByPrimaryKey failed due to {0} on table {1} for key {2}. Explanation:
None. User Response: None.
ADMR3205E: RepositoryObjectImpl
delete failed due to {0} for id = {1}. Explanation: None.
User Response: None.
ADMR3206E: RepositoryObjectImpl
delete failed due to {0}. Explanation: None. User Response:
None.
ADMR3207E: RepositoryObjectImpl select failed
to find bean instance {0} in table {1}. Explanation: None.
User Response: None.
ADMR3208E: RepositoryObjectImpl
select failed because of {0}. Explanation: None. User
Response: None.
ADMR3209E: RepositoryObjectImpl update
failed due to {0} for statement with id = {1}. Explanation: None.
User Response: None.
ADMR3210E: RepositoryObjectImpl
update failed due to {0}. Explanation: None. User Response:
None.
ADMR3211E: RepositoryObjectImpl could not get
typeId {1} due to {0}. Explanation: None. User Response:
None.
ADMR3212E: RepositoryObjectImpl could not get
typeId due to {0}. Explanation: None. User Response:
None.
ADMR3213E: Attribute does not exist.
Explanation: None. User Response: None.
ADMR3214E: Attribute is not set. Explanation: None.
User Response: None.
ADMR3215E: Operation is not valid.
Explanation: None. User Response: None.
ADMR3216E: RepositoryObjectImpl could not find the home interface for {0}
due to {1}. Explanation: None. User Response: None.
ADMR3217E: RepositoryObjectImpl could not find the naming context due to {0}.
Explanation: None. User Response: None.
ADMR3218E: RepositoryObjectImpl found an invalid relation operation.
Explanation: None. User Response: None.
ADMR3219E: RepositoryObjectImpl could not create model tree because of {0}.
Explanation: None. User Response: None.
ADMR3220E: RepositoryObjectImpl could not get the relationship because of
{0}. Explanation: None. User Response: None.
ADMR3221E: RepositoryObjectImpl could not find an object. Explanation:
None. User Response: None.
ADMR3222E: RepositoryObjectImpl
could not find the primary key {0}. Explanation: None.
User Response: None.
ADMR3223E: RepositoryObjectImpl
could not find the type corresponding to interface {0}. Explanation:
None. User Response: None.
ADMR3224E: RepositoryObjectImpl
could not get the default attributes due to {0} Explanation: None.
User Response: None.
ADMR3225E: RepositoryObjectImpl
could not find the relationship {0}. Explanation: None.
User Response: None.
ADMR3226E: RepositoryObjectImpl
could not get the containment relation due to {0}. Explanation:
None. User Response: None.
ADMR3227E: RepositoryObjectImpl
could not set new name {0} because of {1}. Explanation: None.
User Response: None.
ADMR3228E: RepositoryObjectImpl
could not find the remote interface due to {1}. Explanation: None.
User Response: None.
ADMR3300E: Attribute does not
exist. Explanation: None. User Response: None.
ADMR3301E: Attribute is not set. Explanation: None.
User Response: None.
ADMR3302E: Could not list contained
objects because of {0}. Explanation: None. User Response:
None.
ADMR3303E: Could not lookup contained object
because of {0}. Explanation: None. User Response: None.
ADMR3304E: Could not load class because of {0}. Explanation: None.
User Response: None.
ADMR3305E: Could not find class
for type {0} because of {1}. Explanation: None. User
Response: None.
ADMR3306E: Operation exception encountered.
Explanation: None. User Response: None.
ADMR3307E: TypeBean update failed due to {0} for statement with name = {1}
id = {2}. Explanation: None. User Response: None.
ADMR3308E: TypeBean update failed due to {0}. Explanation: None.
User Response: None.
ADMR3309E: TypeBean could not
find type to delete. Explanation: None. User Response:
None.
ADMR3310E: TypeBean delete failed due to {0}
for id = {1}. Explanation: None. User Response: None.
ADMR3311E: TypeBean delete failed due to {0}. Explanation: None.
User Response: None.
ADMR3312E: TypeBean insert failed
due .to {0} for statement id = {1} class = {2}. Explanation: None.
User Response: None.
ADMR3313E: TypeBean insert failed
due to {0}. Explanation: None. User Response: None.
ADMR3314E: TypeBean findByImplClass failed to find {1} due to {0}.
Explanation: None. User Response: None.
ADMR3315E: TypeBean findByImplClass failed due to {0}. Explanation:
None. User Response: None.
ADMR3316E: TypeBean
findByInterfaceClass failed to find {1} due to {0}. Explanation:
None. User Response: None.
ADMR3317E: TypeBean
findByInterfaceClass failed due to {0}. Explanation: None.
User Response: None.
ADMR3318E: TypeBean findAll failed
due to {0}. Explanation: None. User Response: None.
ADMR3319E: TypeBean findRootTypes failed due to {0}. Explanation:
None. User Response: None.
ADMR3320E: TypeBean
could not create table {0} because of {1}. Explanation: None.
User Response: None.
ADMR3400E: VirtualHost was not
found for Alias (name={0}). Explanation: None. User
Response: None.
ADMR3401E: Exception occurred validating
input VirtualHost (name={0}). Explanation: None. User
Response: None.
ADMR3402E: VirtualHost already exists
(name={0}). Explanation: None. User Response: None.
ADMR3403E: Database create table failed. Explanation: None.
User Response: None.
ADMR3404E: Database update failed
to store VirtualHost attributes (id={0}). Explanation: None.
User Response: None.
ADMR3405E: Database insert failed
to store new VirtualHost instance (id={0}). Explanation: None.
User Response: None.
ADMR3406E: Database delete failed
to remove VirtualHost instance (id={0}). Explanation: None.
User Response: None.
ADMR3407E: Database select failed
to find VirtualHost instance (id={0}). Explanation: None.
User Response: None.
ADMR3408E: Database select failed.
Explanation: None. User Response: None.
ADMR3409E: Database select failed to find all instances of VirtualHost.
Explanation: None. User Response: None.
ADMR3410E: Database select failed to find instance of VirtualHost (name={0}).
Explanation: None. User Response: None.
ADMR3411E: Exception occurred initializing default VirtualHost attributes.
Explanation: None. User Response: None.
ADMR3412E: Required VirtualHost name or AliasList attribute was not specified.
Explanation: None. User Response: None.
ADMR3413E: Required attribute for VirtualHost was not input. Explanation:
None. User Response: None.
ADMR3414E: VirtualHost
AliasList attribute was not set. Explanation: None.
User Response: None.
ADMR3415E: VirtualHost name attribute
was not set. Explanation: None. User Response: None.
ADMR3416E: Input attribute does not exist for a VirtualHost. Explanation:
None. User Response: None.
ADMR3417E: VirtualHost
name attribute does not exist. Explanation: None. User
Response: None.
ADMR3418E: Exception occurred trying
to find VirtualHost for Alias (name={0}). Explanation: None.
User Response: None.
ADMR3419E: Exception occurred
attempting to find VirtualHost by name (name={0}). Explanation:
None. User Response: None.
ADMR4351E: Fail
to request J2CResourceAdapter name Explanation: None.
User Response: None.
ADMR4352E: Fail to request JMSProvider
name Explanation: None. User Response: None.
ADMR4353E: Fail to request JMSProvider name Explanation: None.
User Response: None.
ADMR4354E: Fail to request JMSProvider
name Explanation: None. User Response: None.
ADMR4354E: Fail to request the application server name Explanation:
None. User Response: None.
ADMR4354E: Fail
to request the node name Explanation: None. User Response:
None.
ADMR4355E: Fail to request JDBCDriver name
Explanation: None. User Response: None.
ADMS0001E: Encountered an exception
{0} in the invokeInitializers method on class: {1}
Explanation: None. User Response: None.
ADMS0002I: Initializing WebSphere Administration Server
Explanation: None. User Response:
None. ADMS0003W: Default attribute not set
Explanation: None. User Response:
None. ADMS0004W: Failed to reconnect to
a server: {0} {1} Explanation: None.
User Response: None. ADMS0005W: traceOutputFile
[null] is invalid Only serious event is available in stdout
Explanation: None. User Response: None.
ADMS0006W: Unexpected ServerGroupRefreshException
in setModelChanged Explanation: None.
User Response: None. ADMS0007E: Encountered
an exception in the main method {0} Explanation: None.
User Response: None. ADMS0008I:
Starting server: {0} Explanation: None.
User Response: None. ADMS0009W: Unexpected
exception in pushModelChangesForWLM Explanation: None.
User Response: None.
ADMS0010E: Invalid log file specification {0}
Explanation: None. User Response: None.
ADMS0011W: Encountered an error during the getROName method
{0} Explanation: None. User Response:
None.
ADMS0012W: Unexpected ServerGroupRefreshException
in modelRemoved Explanation: None.
User Response: None.
ADMS0013W: Encountered
a bad implementation of a ModelAttributes object in the setAttributes method:
{0} Explanation: None. User Response:
None.
ADMS0014W: The getEpmName(RepositoryObject)
method must never be called. {0} Explanation: None.
User Response: None. ADMS0015I:
Your temporary product license expired on {0,date}; IBM suggests that you
purchase a production license now to avoid any disruption. Contact your
local IBM representative, or visit www.software.ibm.com to purchase this
product from Shop IBM. Explanation: None.
User Response: None.
ADMS0016W:
Encountered an exception {0} in the invokeUserInitializers method on class:
{1} Explanation: None. User Response:
None.
ADMS0017W: Unexpected ServerGroupRefreshException
in updateWLMInfo Explanation: None.
User Response: None.
ADMS0018W: Failed
to get an EPM name {0} Explanation: None.
User Response: None.
ADMS0019W: Encountered
an error while recording configuration for server: {0} {1}
Explanation: None. User Response: None.
ADMS0020W: Could not create bean table {0} due to {1}
Explanation: None. User Response:
None.
ADMS0021W: Failed to start the server:
{0} {1} Explanation: None. User
Response: None.
ADMS0022E: Error deploying
beans Explanation: None. User
Response: None. ADMS0023W: Orb has not
been initialized: will use IP address of local host
Explanation: None. User Response: None.
ADMS0024I: WebSphere Administration Server open for
e-business Explanation: None.
User Response: None.
ADMS0025W: Failed
to reconnect to an EJB server: {0}. No IOR available
Explanation: None. User Response: None.
ADMS0026W: Security failed to initialize: {0}
Explanation: None. User Response: None.
ADMS0027E: Could not initialize persistent storage for
serious events. Got exception {0} Explanation: None.
User Response: None.
ADMS0028I:
Restarting server: {0} Explanation: None.
User Response: None.
ADMS0029I: Stopped
server: {0} (pid {1}) Explanation: None.
User Response: None.
ADMS0030W: Failed
to reconnect to a server: {0} No PID available Explanation:
None. User Response: None.
ADMS0031W: Failed to register a trace event listener: {0}
Explanation: None. User Response: None.
ADMS0032I: Started server: {0} (pid {1})
Explanation: None. User Response: None.
ADMS0033E: WebSphere Administration Server has been
initialized Explanation: None.
User Response: None.
ADMS0034E: Encountered
an internal error {0} Explanation: None.
User Response: None.
ADMS0035W: Unexpected
WLMBootstrapException Explanation: None.
User Response: None. ADMS0036I: Initialized
server Explanation: None.
User Response: None.
ADMS0037W: Server
agents do not correspond to containment paths Explanation:
None. User Response: None.
ADMS0038W: Failed: Epm setModuleComponents {0}
Explanation: None. User Response: None.
ADMS0039E: Could not load database driver
Explanation: None. User Response: None.
ADMS0040E: Server shutdown Explanation:
None. User Response: None.
ADMS0041I: Force stopped server: {0} (pid {1})
Explanation: None. User Response: None.
ADMS0042W: Failed to stop the server: {0} (pid {1})\\n{2}
Explanation: None. User Response:
None. ADMS0043I: Your temporary product
license expires on {0,date}; IBM suggests that you purchase a production
license now to avoid any disruption. Contact your local IBM representative,
or visit www.software.ibm.com to purchase this product from Shop IBM.
Explanation: None. User Response: None.
ADMS0044W: java net UnknownHostException computing
local host Explanation: None.
User Response: None.
ADMS0045W: Failed
to start the container: {0} {1} Explanation: None.
User Response: None.
ADMS0046W:
Unexpected WLMBootstrapException in ejbRemove Explanation:
None. User Response: None.
ADMS0047W: Encountered an error while resetting create db flag for
bean: {0} {1} Explanation: None.
User Response: None. ADMS0048W: Attribute
is set, but the get method failed in the setAttributes method {0}
Explanation: None. User Response: None.
ADMS0049W: Failed to start the bean {0} {1}
Explanation: None. User Response: None.
ADMS0050W: Encountered an exception when terminating
initializer: {0} {1} Explanation: None.
User Response: None.
ADMS0051I: Error
occurred while validating product license Explanation:
None. User Response: None.
ADMS0052W: Encountered an error while processing the trace specification:
{0} {1} Explanation: None. User
Response: None. ADMS0053W: Unexpected
exception getting orb instance Explanation: None.
User Response: None.
ADMS0054E:
The exportServerUtil method failed {0} Explanation:
None. User Response: None.
ADMS0055W: Unexpected exception encountered in initializeWLMPush
Explanation: None. User Response:
None. ADMS0056E: Agent not properly
initialized; TranLog missed Explanation: None.
User Response: None.
ADMS0057I:
Creating temporary product license Explanation: None.
User Response: None.
ADMS0058W:
Model not found Explanation: None.
User Response: None.
ADMS0059E: Attribute
does not exist: {0} Explanation: None.
User Response: None.
ADMS0060W: Unexpected
ConfigInfoManagerNotInitializedException in updateWLMInfo
Explanation: None. User Response: None.
ADMS0061E: Failed to Create PluginCfgGenerator
Explanation: None. User Response: None.
ADMS0062W: Failed to initialize a server: {0} {1}
Explanation: None. User Response: None.
ALRM0001W: Encountered a failure in the fireAlarm method {0}
Explanation: None. User Response: None.
ADMT0100E: Could not get DataSource Home. Explanation: None.
User Response: None.
ADMT0101W: Cannot get the DataSourceHome interface. Explanation:
None. User Response: None.
ADMT0102E: Could not create data source. Explanation: None.
User Response: None.
ADMT0103W: Cannot get the JDBCDriver interface. Explanation: None.
User Response: None.
ADMT0104E: Could not get JDBCDriver Home. Explanation: None.
User Response: None.
ADMT0106E: Could not create JDBCDriver. Explanation: None.
User Response: None.
ADMT0200E: Could not obtain Initial Context. Explanation: None.
User Response: None.
ADMT0201E: Could not get the ServerHome. Explanation: None.
User Response: None.
ADMT0202E: Could not create Server. Explanation: None.
User Response: None. ADMT0250W:
Cannot get the ServerHome interface. Explanation: None.
User Response: None. ADMT0300E:
Could not find EnterpriseApp name. Explanation: None.
User Response: None. ADMT0301E:
Authorization Table initialization failed. Explanation: None.
User Response: None.
ADMT0302E: Could not get EnterpriseApp attributes. Explanation:
None. User Response: None.
ADMT0303E: Could not bind to application. Explanation: None.
User Response: None.
ADMT0304E: Could not get application DD. Explanation: None.
User Response: None.
ADMT0305E: Could not get application binding. Explanation: None.
User Response: None.
ADMT0306E: Could not update Authorization Table. Explanation:
None. User Response: None.
ADMT0307E: Could not get roleassignment list. Explanation: None.
User Response: None.
ADMT0308E: Could not update RoleAssignment. Explanation: None.
User Response: None.
ADMT0309E: Could not remove security roles from authorization table.
Explanation: None. User Response: None. ADMT0310E: Could not update RunAsRole mapping.
Explanation: None. User Response: None. ADMT0311E: Could not get node home. Explanation:
None. User Response: None. >
ADMT0312E: Could not get FileBrowserServiceHome. Explanation:
None. User Response: None.
ADMT0313E: Could not create FileBrowserService. Explanation: None.
User Response: None.
ADMT0314E: Could not get EnterpriseAppHome. Explanation: None.
User Response: None.
ADMT0315E: Could not get RegistryEntryHome. Explanation: None.
User Response: None.
ADMT0316E: Could not get group Registry Entries. Explanation:
None. User Response: None.
ADMT0317E: Could not get user Registry Entries. Explanation: None.
User Response: None.
ADMT0318E: Could not get Host name. Explanation: None.
User Response: None. ADMT0319E:
Could not validate subjects. Explanation: None. User
Response: None. ADMT0320E:
Could not create Registry. Explanation: None. User
Response: None. ADMT0321E:
Could not fill in subjects access IDs. Explanation: None.
User Response: None.
CHKJ0451E: Unsupported XMI version.
Explanation: None. User Response: None.
CHKJ0452E: No packages have been registered. Explanation: None.
User Response: None.
CHKJ0500I: Parsing document: {0}
Explanation: None. User Response: None.
CHKJ0501I: Finished parsing document, {0}. Explanation: None.
User Response: None.
CHKJ0502I: Warnings occurred during
parse. Explanation: None. User Response: None.
CHKJ0510E: Error occurred during parse: {0} Explanation: None.
User Response: None.
CHKJ0511E: Fatal error occurred
during parse: {0} Explanation: None. User Response:
None.
CHKJ0520W: Invalid value type: {0} expecting
{1} at line number {2}. Explanation: None. User Response:
None.
CHKJ0521W: Invalid value: {0} at line number
{1}. Explanation: None. User Response: None.
CHKJ0522W: Invalid element tag name: {0} at line number {1}. Explanation:
None. User Response: None.
CHKJ0523W: Invalid
attribute: {0} at line number {1}. Explanation: None.
User Response: None.
CHKJ0524W: Invalid namespace:
{0} at line number {1}. Explanation: None. User Response:
None.
CHKJ0525W: Unknown package: {0} at line number
{1}. Explanation: None. User Response: None.
CHKJ0526W: Unable to resolve reference for: {0} at line number {1}.
Explanation: None. User Response: None.
CHKJ0540E: Unsupported encoding: {0} Explanation: None.
User Response: None.
CHKJ1000E: An internal error has
occurred. Please check the log files for more information on the error occurred.
Explanation: None. User Response: None.
CHKJ1001E: The ear file; Explanation: None. User Response:
None.
CHKJ1002E: Duplicate security role named {0}.
Explanation: None. User Response: None.
CHKJ1003E: A module has been defined with no URI. Explanation:
None. User Response: None.
CHKJ1004E: The
URI, {0}, does not match anything within the ear file Explanation:
None. User Response: None.
CHKJ2000W: Home
interface {0} for entity bean {1} contains multiple findByPrimaryKey methods.
Explanation: None. User Response: None.
CHKJ2001W: The primary key class {0} does not implement the {1} method. While
an implementation of this method was not required in the EJB 1.0 specification,
it is required in the EJB 1.1 specification. Read section 9.2.9 of the EJB
1.1 specification for details. Explanation: None. User
Response: None.
CHKJ2002W: {0} implements an ejbCreate
method with signature {1} but does not implement the matching ejbPostCreate
method. While the deployment code can be generated if this method is absent,
the generated code does not invoke ejbPostCreate as it should. The EJB 1.1
specification states that this method must be implemented, and the EJB 1.0
specification intended for this method to be implemented, but did not state
that it was a requirement. Read section 9.2.4 of the EJB 1.1 specification
for details. Explanation: None. User Response: None.
CHKJ2003W: Session bean {0} inherits javax.ejb.SessionSynchronization but,
in its assembly descriptor, method {1} is listed as bean managed (trans-attribute
= Never). The EJB 1.1 specification does not allow use of SessionSynchronization
for bean managed sessions. Read section 11.7.1 of the EJB 1.1 specification
for details. Explanation: None. User Response: None.
CHKJ2004E: CMP bean {0} should not implement the finder method {1}. Read section
9.4.6 of the EJB 1.1 specification for details. Explanation: None.
User Response: None.
CHKJ2005E: Method {0} declared
in home interface for entity bean {1} is not a create or finder method. Read
section 9.2.8 of the EJB 1.1 specification for details. Explanation:
None. User Response: None.
CHKJ2006E: The
{0} bean must have a public constructor that takes no arguments. Read section
6.10.2 (session beans) or 9.2.2 (entity beans) of the EJB 1.1 specification
for details. Explanation: None. User Response: None.
CHKJ2007E: The {0} session bean must not declare the finalize() method. The
EJB 1.1 specification states that this restriction is in place because the
method may not be called by some Container implementations. Read section 6.10.2
(session beans) or 9.2.2 (entity beans) of the EJB 1.1 specification for details.
Explanation: None. User Response: None.
CHKJ2008E: The {0} enterprise bean must contain at least one ejbCreate method.
Read section 6.10.3 of the EJB 1.1 specification for details.
Explanation: None. User Response: None.
CHKJ2009E: The {0} enterprise bean must contain at least one ejbFindByPrimaryKey
method. Read section 9.2.5 of the EJB 1.1 specification for details.
Explanation: None. User Response: None.
CHKJ2010E: The home interface {0} for session bean {1} must contain at least
one create method. Read section 6.10.6 of the EJB 1.1 specification for details.
Explanation: None. User Response: None.
CHKJ2011E: The home interface {0} for entity bean {1} must contain at least
one findByPrimaryKey method. Read section 9.2.8 of the EJB 1.1 specification
for details. Explanation: None. User Response: None.
CHKJ2012E: The interface class {0} for enterprise bean {1} is not a valid
interface. Possible cause: The interface class is not public or is an abstract
class. Explanation: None. User Response: None.
CHKJ2013E: The {0} enterprise bean does not implement the {1} interface. Read
section 6.10.2 (session beans) or 9.2.2 (entity beans) of the EJB 1.1 specification
for details. Explanation: None. User Response: None.
CHKJ2014E: The {0} enterprise bean cannot be declared as abstract. Read section
6.10.2 (session beans) or 9.2.2 (entity beans) of the EJB 1.1 specification
for details. Explanation: None. User Response: None.
CHKJ2015E: The {0} enterprise bean cannot be declared as final. Read section
6.10.2 (session beans) or 9.2.2 (entity beans) of the EJB 1.1 specification
for details. Explanation: None. User Response: None.
CHKJ2016E: The {0} session bean implements javax.ejb.SessionSynchronization,
but the bean is not a stateful session bean. Only stateful session beans are
allowed to implement that interface. Read section 6.10.2 of the EJB 1.1 specification
for details. Explanation: None. User Response: None.
CHKJ2017E: Interface {0} of enterprise bean {1} does not extend the {2} interface.
Read section 6.10.5 (session beans) or 9.2.7 (entity beans) of the EJB 1.1
specification for details. Explanation: None. User Response:
None.
CHKJ2018E: The key class {0} for enterprise bean
{1} does not contain any public fields. Explanation: None.
User Response: None.
CHKJ2019E: The key class {0} for
enterprise bean {1} is not a legal Value Type for RMI-IIOP. Read section 9.4.7.2
of the EJB 1.1 specification for details. Explanation: None.
User Response: None.
CHKJ2020E: The primary key class
{0} for CMP bean {1} is not public. Read section 9.4.7.2 of the EJB 1.1 specification
for details. Explanation: None. User Response: None.
CHKJ2021E: The primary key class {0} for CMP bean {1} has no public default
constructor. Read section 9.4.7.2 of the EJB 1.1 specification for details.
Explanation: None. User Response: None.
CHKJ2022E: The {0} enterprise bean is not defined as public. Read section
6.10.2 (session bean) or 9.2.2 (entity bean) of the EJB 1.1 specification
for details. Explanation: None. User Response: None.
CHKJ2023E: The {0} method declared in {1} has no matching method {2} in enterprise
bean {3}. Explanation: None. User Response: None.
CHKJ2024E: The {0} home interface for stateless session bean {1} should only
have one create() method with no arguments. Read section 6.8 of the EJB 1.1
specification for details. Explanation: None. User Response:
None.
CHKJ2025E: The stateless session bean {0} should
only have one ejbCreate() method with no arguments. Read section 6.8 of the
EJB 1.1 specification for details. Explanation: None.
User Response: None.
CHKJ2200W: Field {0} declared
in enterprise bean {1} is static but not final. Read section 18.1.2 of the
EJB 1.1 specification for details. Explanation: None.
User Response: None.
CHKJ2201E: The field, {0}, in
container managed entity bean {1} is transient. Read section 9.4.1 of the
EJB 1.1 specification for details. Explanation: None.
User Response: None.
CHKJ2202E: The {0} field declared
in {1} is an invalid CMP type. Valid types include Java primitive types, serializable
types, the entity bean's remote interface, or the entity bean's home interface.
Read section 9.4.1 of the EJB 1.1 specification for details. Explanation:
None. User Response: None.
CHKJ2203E: The
field {0}, declared in container managed entity bean {1} is not public. Read
section 9.4.1 of the EJB 1.1 specification for details. Explanation:
None. User Response: None.
CHKJ2204E: Primary
key field {0} in entity bean {1} is illegal because it is not a serializable
type. Read section 9.2.9 of the EJB 1.1 specification for details.
Explanation: None. User Response: None.
CHKJ2205E: The primary key field {0} declared in key class {1} for enterprise
bean {2} is not public. Read section 9.4.7.2 of the EJB 1.1 specification
for details. Explanation: None. User Response: None.
CHKJ2206E: The primary key field {0} declared in primary key class {1} has
not been designated as a CMP field for enterprise bean {2}. Read section 9.4.7.2
of the EJB 1.1 specification for details. Explanation: None.
User Response: None.
CHKJ2400W: {0} throws a java.rmi.RemoteException.
This is permitted in the EJB 1.0 specification, but deprecated in the EJB
1.1 specification. In the EJB 1.1 specification, a javax.ejb.EJBException
(or another java.lang.RuntimeException) should be thrown to indicate non application
exceptions. Explanation: None. User Response: None.
CHKJ2401E: The ejbCreate method {0} declared in enterprise bean {1} should
return void. Read section 6.10.3 of the EJB 1.1 specification for details.
Explanation: None. User Response: None.
CHKJ2402E: The create method {0} declared in {1} for enterprise bean {2} does
not return the remote interface type {3}. Read section 6.10.6 (session beans)
or 9.2.8 (entity beans) of the EJB 1.1 specification for details.
Explanation: None. User Response: None.
CHKJ2403E: The finder method {0} declared in {1} for enterprise bean {2} does
not return the remote interface type {3} or a collection of that type. Read
section 9.2.8 of the EJB 1.1 specification for details. Explanation:
None. User Response: None.
CHKJ2404E: The
finder method {0} declared in home interface {1} for enterprise bean {2} has
multiple signatures. Only one signature is allowed in order to correspond
to one query string in the finder helper interface. Explanation:
None. User Response: None.
CHKJ2405E: The
arguments of the findByPrimaryKey method {0} declared in home interface {1}
for entity bean {2} are invalid. The order and types of the arguments must
match the order and types of the fields in the key class {3}. Possible cause:
The argument type is not the primary key class. Read section 9.2.8 of the
EJB 1.1 specification for details. Explanation: None.
User Response: None.
CHKJ2406E: The method {0} declared
in bean {1} should return the primary key type {2}. Read section 9.2.3 (BMP
beans) or 9.4.2 (CMP beans) of the EJB 1.1 specification for details. The
EJB 1.1 specification has changed the method signature required on CMP beans'
ejbCreate method. Explanation: None. User Response:
None.
CHKJ2407E: The method {0} declared in bean {1}
should return the primary key type {2}, or a collection of that type. Read
section 9.2.5 of the EJB 1.1 specification for details. Explanation:
None. User Response: None.
CHKJ2408E: The
{0} method declared in enterprise bean {1} is not declared as public.
Explanation: None. User Response: None.
CHKJ2409E: The {0} method cannot be declared as final. Explanation:
None. User Response: None.
CHKJ2410E: The
{0} method cannot be declared as static. Explanation: None.
User Response: None.
CHKJ2411E: The name of the {0}
method must not start with ''ejb''. Read section 6.10.4 (session bean) or
9.2.6 (entity bean) of the EJB 1.1 specification for details.
Explanation: None. User Response: None.
CHKJ2412E: The {0} method declared in {1} returns an illegal type {2} for
Java RMI. Possible cause: The type class does not implement the java.io.Serializable
interface. Explanation: None. User Response: None.
CHKJ2413E: The {0} method declared in {1} contains an illegal argument type
{2} for Java RMI. Possible cause: The type class does not implement the java.io.Serializable
interface. Explanation: None. User Response: None.
CHKJ2414E: The {0} method declared in {1} does not throw the {2} exception.
Read section 6.10.6 (session bean) or 9.2.8 (entity bean) of the EJB 1.1 specification
for details. Explanation: None. User Response: None.
CHKJ2415E: The return type of method {0} declared in {1} does not match the
return type {2} of corresponding method in enterprise bean {3}. Read section
6.10.5 (session bean) or 9.2.7 (entity bean) of the EJB 1.1 specification
for details. Explanation: None. User Response: None.
CHKJ2416E: The exception {0} thrown by method {1} in enterprise bean {2} is
not thrown by the corresponding {3} method in {4}. Explanation:
None. User Response: None.
CHKJ2417E: The
{0} method declared in the control descriptor for enterprise bean {1} must
specify the TX_BEAN_MANAGED transaction attribute because the bean level or
another method level descriptor does. Read section 11.7.1 of the EJB 1.1 specification
for details. Explanation: None. User Response: None.
CHKJ2418E: ejbPostCreate method {0} declared in enterprise bean {1} should
return void. Read section 9.2.4 of the EJB 1.1 specification for details.
Explanation: None. User Response: None.
CHKJ2419E: The {0} method declared in home interface for session bean {1}
is not a create method. Read section 6.10.6 of the EJB 1.1 specification for
details. Explanation: None. User Response: None.
CHKJ2800W: The entity bean {0} uses bean managed transaction demarcation.
While permitted in the EJB 1.0 specification, the EJB 1.1 specification explicitly
disallows entity beans from using bean managed transactions. Entity beans
must use container-managed transaction demarcation. Explanation:
None. User Response: None.
CHKJ2801E: Logical
name, as identified by the ''ejb-name'' element in the deployment descriptor,
of the enterprise bean is invalid. Read sections 16.2 and 16.5 of the EJB
1.1 specification for details. Explanation: None. User
Response: None.
CHKJ2802E: Class name, as identified
by the ''ejb-class' element in the deployment descriptor, of the enterprise
bean is invalid. Read sections 16.2 and 16.5 of the EJB 1.1 specification
for details. Explanation: None. User Response: None.
CHKJ2803E: Name of home interface, as identified by the ''home'' element in
the deployment descriptor, for enterprise bean {0} is invalid. Read sections
16.2 and 16.5 of the EJB 1.1 specification for details. Explanation:
None. User Response: None.
CHKJ2804E: Name
of remote interface, as identified by the ''remote'' element in the deployment
descriptor, for enterprise bean {0} is invalid. Read sections 16.2 and 16.5
of the EJB 1.1 specification for details. Explanation: None.
User Response: None.
CHKJ2805E: Enterprise bean, {0},
must be identified as either session or entity. That is, it must use either
the ''entity'' or the ''session'' element in the deployment descriptor. Read
sections 16.2 and 16.5 of the EJB 1.1 specification for details.
Explanation: None. User Response: None.
CHKJ2806E: Entity bean, {0}, must specify whether or not it is re-entrant
through the ''reentrant'' element in the deployment descriptor. Read sections
16.2 and 16.5 of the EJB 1.1 specification for details. Explanation:
None. User Response: None.
CHKJ2807E: Session
bean, {0}, uses an unknown value for the ''session-type'' element. The value
must be either Stateful or Stateless (and the value is case sensitive). Read
sections 16.2 and 16.5 of the EJB 1.1 specification for details.
Explanation: None. User Response: None.
CHKJ2808E: Session bean, {0}, uses an unknown value for the ''transaction-type''
element. The value must be either Container or Bean (and the value is case
sensitive). Read sections 11.3.5, 16.2, and 16.5 of the EJB 1.1 specification
for details. Explanation: None. User Response: None.
CHKJ2809E: Entity bean, {0}, uses an unknown value for the ''persistence-type''
element. The value must be either Container or Bean (and the value is case
sensitive). Read sections 16.2 and 16.5 of the EJB 1.1 specification for details.
Explanation: None. User Response: None.
CHKJ2810E: Bean managed persistence entity bean, {0}, must specify a value
for the ''prim-key-class'' element in the deployment descriptor. Read sections
16.2 and 16.5 of the EJB 1.1 specification for details. Explanation:
None. User Response: None.
CHKJ2811E: One
of the ''cmp-field'' elements in the deployment descriptor is missing a field
name. The name of the container managed persistence enterprise bean is {0}.
Read sections 16.2 and 16.5 of the EJB 1.1 specification for details.
Explanation: None. User Response: None.
CHKJ2812E: Container managed persistence entity bean, {0}, must specify at
least one ''cmp-field'' element in the deployment descriptor. Read section
16.5 of the EJB 1.1 specification for details. Explanation: None.
User Response: None.
CHKJ2813E: This type of enterprise
bean should not specify the ''{0}'' tag. Read sections 16.2 and 16.5 of the
EJB 1.1 specification for details. Explanation: None.
User Response: None.
CHKJ2814E: Method element named
{0}, with description ''{1}'', and trans-attribute ''{2}'', has specified
an enterprise bean which cannot be loaded. This will not cause an error at
compile time, but it will at run-time. Check the syntax in the file''s ''assembly-descriptor''
section. Explanation: None. User Response: None.
CHKJ2815E: The deployment descriptor could not be loaded due to an unknown
syntax error. The start of the bad section is at line {0}, column {1}.
Explanation: None. User Response: None.
CHKJ2816E: The deployment descriptor could not be loaded due to an unknown
syntax error. The start of the bad section is at line {0}. Explanation:
None. User Response: None.
CHKJ2817E: The
deployment descriptor could not be loaded due to an unknown syntax error.
The exception thrown by the parser does not identify a line number, but this
type of exception usually indicates the following type of error: {0}.
Explanation: None. User Response: None.
CHKJ2818E: The deployment descriptor could not be loaded due to an unknown
syntax error. There is no information available to help identify the bad section.
Explanation: None. User Response: None.
CHKJ2819E: The {0} security role ref, defined in the deployment descriptor
of enterprise bean {1}, is not defined in its enclosing EAR file's deployment
descriptor. If one security role ref is defined in the EAR, all security role
refs must be defined in the EAR. Explanation: None.
User Response: None.
CHKJ2820W: The {0} security role
ref, defined in the deployment descriptor of enterprise bean {1}, is defined
more than once. Explanation: None. User Response: None.
CHKJ2821E: Cannot open the deployment descriptor. Validation cannot complete.
Explanation: None. User Response: None.
CHKJ2822E: ''security-role-ref'' element for bean {0} must define the ''role-name''
element. Read section 15.2.5.3 of the EJB 1.1 specification for details.
Explanation: None. User Response: None.
CHKJ2823E: ''security-role-ref'' element {0} must define the ''role-link''
element because the assembly descriptor declares ''security-role'' elements.
Read section 15.3.3 of the EJB 1.1 specification for details.
Explanation: None. User Response: None.
CHKJ2824E: ''security-role-ref'' element {0} refers to unknown role {1}. Any
role referenced in a ''role-link'' element must be one of the defined ''security-role''
elements in the assembly descriptor. Read section 15.3.3 of the EJB 1.1 specification
for details. Explanation: None. User Response: None.
CHKJ2825E: ''security-role'' element in ejb-jar.xml must define the ''role-name''
element. Read section 15.3.1 of the EJB 1.1 specification for details.
Explanation: None. User Response: None.
CHKJ2826W: The {0} ''security-role'', defined in the assembly descriptor,
is defined more than once. Explanation: None. User Response:
None.
CHKJ2827W: ''security-role-ref'' element {0}
defines the ''role-link'' element but there are no ''security-role'' elements
in the application descriptor. Read sections 15.2.5.3, 15.3.1, and 15.3.3
of the EJB 1.1 specification for details. Explanation: None.
User Response: None.
CHKJ3000E: An internal error has
occurred. Please check the log files for more information on the error occurred.
Explanation: None. User Response: None.
CHKJ3001E: The JSP file, {0}, for the servlet \"{1}\" is missing.
Explanation: None. User Response: None.
CHKJ3002E: The <small-icon>file, {0}, is missing. Explanation:
None. User Response: None.
CHKJ3003E: The <large-icon>file,
{0}, is missing. Explanation: None. User Response:
None.
CHKJ3004E: The servlet mapping \"{0}\" refers
to a missing servlet. Explanation: None. User Response:
None.
CHKJ3005E: Empty welcome file list entry.
Explanation: None. User Response: None.
CHKJ3006E: Welcome file {0} is missing. Explanation: None.
User Response: None.
CHKJ3007E: The Tag Library Description
File, {0}, is missing. Explanation: None. User Response:
None.
CHKW0000I: IBM WebSphere Validation Explanation: None.
User Response: None.
CHKW0001I: Common Validation
Explanation: None. User Response: None.
CHKW0002E: An internal error has occurred during validation. Please check
the log files for more information on the error that occurred.
Explanation: None. User Response: None.
CHKW0003E: An object of an unrecognized type was sent for validation. This
is an internal error. Type object type is {0}. Explanation: None.
User Response: None.
CHKW1000I: IBM WebSphere Validation
Explanation: None. User Response: None.
CHKW1001I: Server Configuration Validation Explanation: None.
User Response: None.
CHKW1002E: An internal error has
occurred during server configuration validation. Please check the log files
for more information on the error that occurred. Explanation:
None. User Response: None.
CHKW1003E: An
object of an unrecognized type was sent for server configuration validation.
This is an internal error. The object type is {0}. Explanation:
None. User Response: None.
CHKW1004E: The
name of a domain is required. Explanation: None. User
Response: None.
CHKW1005E: The domain name is invalid
{0}. Explanation: None. User Response: None.
CHKW1006E: A domain must have at least one virtual host. Explanation:
None. User Response: None.
CHKW1007E: Duplicated
virtual host name {0}. Explanation: None. User Response:
None.
CHKW1008E: The name of a virtual host is required.
Explanation: None. User Response: None.
CHKW1009E: The virtual host name is not valid {0}. Explanation:
None. User Response: None.
CHKW1010W: Duplicated
mime entry type {0}. Explanation: None. User Response:
None.
CHKW1011E: Redundant mapping of extension {0}
to mime type {1}. Explanation: None. User Response:
None.
CHKW1012E: Mapping of extension {0} to multiple
mime types {1} and {2}. Explanation: None. User Response:
None.
CHKW1013E: The type of a mime entry is required.
Explanation: None. User Response: None.
CHKW1014E: The mime entry type is not valid {0}. Explanation:
None. User Response: None.
CHKW1015E: No
extension of a mime entry may be null or empty. Explanation: None.
User Response: None.
CHKW1016E: The mime entry extension
is not valid {0}. Explanation: None. User Response:
None.
CHKW1017E: Duplicated host alias with name {0}
and port {1}. Explanation: None. User Response: None.
CHKW1018E: The name of a host alias is required. Explanation:
None. User Response: None.
CHKW1019E: The
host alias name is invalid {0}. Explanation: None.
User Response: None.
CHKW1020E: The port of a host
alias is required. Explanation: None. User Response:
None.
CHKW1021E: The host alias port is not valid {0}.
Explanation: None. User Response: None.
CHKW1022E: The host alias port {0} is less than the minimum {1}.
Explanation: None. User Response: None.
CHKW1023E: A domain must have at least one node. Explanation:
None. User Response: None.
CHKW1024E: Duplicated
node name {0}. Explanation: None. User Response: None.
CHKW1025E: The name of a node is required. Explanation: None.
User Response: None.
CHKW1026E: The node name is not
valid {0}. Explanation: None. User Response: None.
CHKW1027E: The application server id {0} is greater than the minimum {1}.
Explanation: None. User Response: None.
CHKW1028E: The application server module visibility mode {0} is not valid.
Explanation: None. User Response: None.
CHKW1029E: A node must have at least one server. Explanation:
None. User Response: None.
CHKW1030E: Duplicated
server {0}. Explanation: None. User Response: None.
CHKW1031E: The application server id {0} is used by both application servers
{1} and {2}. Explanation: None. User Response: None.
CHKW1032E: The application reference must have at least one module reference.
Explanation: None. User Response: None.
CHKW1033E: The application server must have an ORB configuration.
Explanation: None. User Response: None.
CHKW1034E: The application server must have a transaction service.
Explanation: None. User Response: None.
CHKW1035E: The application server must have a server security configuration.
Explanation: None. User Response: None.
CHKW1036E: The EJB container must have an EJB cache. Explanation:
None. User Response: None.
CHKW1037E: The
module reference must have an application reference. Explanation:
None. User Response: None.
CHKW1038E: The
Node must have a server. Explanation: None. User Response:
None.
CHKW1039E: The ORB configuration must have a
thread pool. Explanation: None. User Response: None.
CHKW1040E: The name of the Cookie is required. Explanation: None.
User Response: None.
CHKW1041E: The session manager
must have a cookie. Explanation: None. User Response:
None.
CHKW1042E: The session manager must have a tuning
parameters. Explanation: None. User Response: None.
CHKW1043E: The transport has a duplicated system property {0}.
Explanation: None. User Response: None.
CHKW1044E: The web container must have a thread pool. Explanation:
None. User Response: None.
CHKW1045E: The
web container must have a session manager. Explanation: None.
User Response: None.
CHKW1046E: The name of the application
reference is required. Explanation: None. User Response:
None.
CHKW1047E: The name {0} of the application reference
is not valid. Explanation: None. User Response: None.
CHKW1048E: The archive URL of the application reference is required.
Explanation: None. User Response: None.
CHKW1049E: The archive URL {0} of the application reference is not valid.
Explanation: None. User Response: None.
CHKW1050E: The cookie domain {0} is not valid. Explanation: None.
User Response: None.
CHKW1051E: The cookie maximum
range {0} is less than the minimum value {1}. Explanation: None.
User Response: None.
CHKW1052E: The cookie path {0}
is not valid. Explanation: None. User Response: None.
CHKW1053E: The provider class of the custom transport is required.
Explanation: None. User Response: None.
CHKW1054E: The provider class {0} of the custom transport is not valid.
Explanation: None. User Response: None.
CHKW1055E: The cache size {0} of the dynamic cache is less than the minimum
value {1}. Explanation: None. User Response: None.
CHKW1056E: The default priority {0} of the dynamic cache is less than the
minimum value {1}. Explanation: None. User Response:
None.
CHKW1057E: The cleanup interval {0} of the EJB
cache is less than the minimum value {1}. Explanation: None.
User Response: None.
CHKW1058E: The cache size {0}
of the EJB cache is less than the minimum value {1}. Explanation:
None. User Response: None.
CHKW1059E: The
passivation directory of the EJB container is required. Explanation:
None. User Response: None.
CHKW1060E: The
passivation directory {0} of the EJB container is not valid. Explanation:
None. User Response: None.
CHKW1061E: The
inactive pool cleanup directory {0} of the EJB container is less than the
minimum value {1}. Explanation: None. User Response:
None.
CHKW1062E: The name of the external cache group
is required. Explanation: None. User Response: None.
CHKW1063E: The name {0} of the external cache group is not valid.
Explanation: None. User Response: None.
CHKW1064E: The type of the external cache group is required. Explanation:
None. User Response: None.
CHKW1065E: The
type {0} of the external cache group is not valid. Explanation:
None. User Response: None.
CHKW1066E: The
address of the external cache group member is required. Explanation:
None. User Response: None.
CHKW1067E: The
address {0} of the external cache group member is not valid. Explanation:
None. User Response: None.
CHKW1068E: The
adapter bean name of the external cache group member is required.
Explanation: None. User Response: None.
CHKW1069E: The adapter bean name {0} of the external cache group member is
not valid. Explanation: None. User Response: None.
CHKW1070E: The first hour {0} of the invalidation schedule must be greater
than or equal to {1} and less than or equal to {2}. Explanation:
None. User Response: None.
CHKW1071E: The
second hour {0} of the invalidation schedule must be greater than or equal
to {1} and less than or equal to {2}. Explanation: None.
User Response: None.
CHKW1072E: The host name of the
location service daemon is required. Explanation: None.
User Response: None.
CHKW1073E: The host name {0} of
the location service daemon is not valid. Explanation: None.
User Response: None.
CHKW1074E: The port {0} of the
location service daemon is less than the minimum value {1}. Explanation:
None. User Response: None.
CHKW1075E: The
mode {0} of the location service daemon is required. Explanation:
None. User Response: None.
CHKW1076E: The
enablement of the management agent is required. Explanation: None.
User Response: None.
CHKW1077E: The primary node name
of the management agent is required. Explanation: None.
User Response: None.
CHKW1078E: The primary node name
{0} of the management agent is not valid. Explanation: None.
User Response: None.
CHKW1079E: The URI of the module
reference is not valid. Explanation: None. User Response:
None.
CHKW1080E: The URI {0} of the module reference
is not valid. Explanation: None. User Response: None.
CHKW1081E: The maximum startup attempts {0} of the monitoring policy is less
than the minimum value {1}. Explanation: None. User
Response: None.
CHKW1082E: The ping interval {0} of
the monitoring policy is less than the minimum value {1}. Explanation:
None. User Response: None.
CHKW1083E: The
ping timeout {0} of the monitoring policy is less than the minimum value {1}.
Explanation: None. User Response: None.
CHKW1084E: The initial ping timeout {0} of the monitoring policy is less than
the minimum value {1}. Explanation: None. User Response:
None.
CHKW1085E: The database URL of the naming repository
is required. Explanation: None. User Response: None.
CHKW1086E: The database URL {0} of the naming repository is not valid.
Explanation: None. User Response: None.
CHKW1087E: The mirror DS XML of the naming repository is required.
Explanation: None. User Response: None.
CHKW1088E: The database schema of the naming repository is required.
Explanation: None. User Response: None.
CHKW1089E: The database user of the naming repository is required.
Explanation: None. User Response: None.
CHKW1090E: The database driver class name of the naming repository is required.
Explanation: None. User Response: None.
CHKW1091E: The database driver class name {0} of the naming repository is
not valid. Explanation: None. User Response: None.
CHKW1092E: The enablement of the naming service provider is required.
Explanation: None. User Response: None.
CHKW1093E: The host of the naming service provider is required.
Explanation: None. User Response: None.
CHKW1094E: The host {0} of the naming service provider is not valid.
Explanation: None. User Response: None.
CHKW1095E: The port {0} of the naming service provider is less than the minimum
value {1}. Explanation: None. User Response: None.
CHKW1096E: The class name of the naming service provider is required.
Explanation: None. User Response: None.
CHKW1097E: The class name {0} of the naming service provider is not valid.
Explanation: None. User Response: None.
CHKW1098E: The in memory session count {0} of the tuning parameters is less
than the minimum value {1}. Explanation: None. User
Response: None.
CHKW1099E: The write frequency of the
tuning parameters is required. Explanation: None. User
Response: None.
CHKW1100E: The write frequency {0}
of the tuning parameters is not valid. Explanation: None.
User Response: None. CHKW1101E: The write interval {0} of the tuning
parameters must be greater than or equal to {1} and less than or equal to
{2}. Explanation: None. User Response: None.
CHKW1102E: The write contents of the tuning parameters is required.
Explanation: None. User Response: None.
CHKW1103E: The write contents {0} of the tuning parameters is not valid.
Explanation: None. User Response: None.
CHKW1104E: The invalidation timeout {0} of the tuning parameters must be greater
than or equal to {1} and may not be {2}. Explanation: None.
User Response: None.
CHKW1105W: When a time based write
frequency is selected the invalidation timeout {0} of the tuning parameters
should be at least twice as large as the write interval {1}. Explanation:
None. User Response: None.
CHKW1106W: The
host name of the transport is blank; use '*' instead. Explanation:
None. User Response: None.
CHKW1107E: The
host name {0} of the transport is not a valid host name. Explanation:
None. User Response: None.
CHKW1108E: The
port {0} of the transport must be greater than or equal to {1} and less than
or equal to {2}. Explanation: None. User Response:
None.
CHKW1109E: The web container has transports for
which the combination of hostname {0} and port {1} are duplicated.
Explanation: None. User Response: None.
CHKW1110E: The transaction service transaction log file {0} is less than the
minimum value {1}. Explanation: None. User Response:
None.
CHKW1111E: The transaction service inactivity
timeout {0} is less than the minimum value {1}. Explanation: None.
User Response: None.
CHKW1112E: The enablement of the
object level trace is required. Explanation: None.
User Response: None.
CHKW1113E: The object level trace
host name is required. Explanation: None. User Response:
None.
CHKW1114E: The host name {0} of the object level
trace is required. Explanation: None. User Response:
None.
CHKW1115E: The port {0} of the object level trace
must be -1, or must be greater than or equal to {1} and less than or equal
to {2}. Explanation: None. User Response: None.
CHKW1116E: The object level trace source path is required. Explanation:
None. User Response: None.
CHKW1117E: The
source path {0} of the object level trace is not valid. Explanation:
None. User Response: None.
CHKW1118E: The
enablement of the trace service configuration is required. Explanation:
None. User Response: None.
CHKW1119E: The
source path {0} of the trace service configuration is not valid.
Explanation: None. User Response: None.
CHKW1120E: The trace service configuration output file name is required.
Explanation: None. User Response: None.
CHKW1121E: The output file name {0} of the trace service configuration is
not valid. Explanation: None. User Response: None.
CHKW1122E: The trace service configuration diagnosis thread host name is required.
Explanation: None. User Response: None.
CHKW1123E: The diagnosis thread host name {0} of the trace service configuration
is not valid. Explanation: None. User Response: None.
CHKW1124E: The port {0} of the trace service configuration must be -1, or
must be greater than or equal to {1} and less than or equal to {2}.
Explanation: None. User Response: None.
CHKW1125E: The minimum size {0} of the thread pool must be greater than or
equal to {1} and less than or equal to {2}. Explanation: None.
User Response: None.
CHKW1126E: The maximum size {0}
of the thread pool must be greater than or equal to {1} and less than or equal
to {2}. Explanation: None. User Response: None.
CHKW1127E: The minimum size {0} of the thread pool must be less than or equal
to the maximum size {2} of the thread pool. Explanation: None.
User Response: None.
CHKW1128E: The inactivity timeout
{0} of the thread pool must be greater than or equal to {1}. Explanation:
None. User Response: None.
CHKW1129E: The
session persistence data source JNDI name is required. Explanation:
None. User Response: None.
CHKW1130E: The
session persistence user ID is required. Explanation: None.
User Response: None.
CHKW1131E: The session persistence
DB2 row size is required. Explanation: None. User Response:
None.
CHKW1132E: The DB2 row size {0} of the session
persistence is not valid. Explanation: None. User Response:
None.
CHKW1133E: The session persistence table space
name is required. Explanation: None. User Response:
None.
CHKW1134E: The enablement of the ORB configuration
is required. Explanation: None. User Response: None.
CHKW1135E: The bootstrap host of the ORB configuration is required.
Explanation: None. User Response: None.
CHKW1136E: The bootstrap host {0} of the ORB configuration is not valid.
Explanation: None. User Response: None.
CHKW1137E: The bootstrap port {0} of the ORB configuration must be greater
than or equal to {1} and less than or equal to {2}. Explanation:
None. User Response: None.
CHKW1138E: The
link type of the OSE transport is required. Explanation: None.
User Response: None.
CHKW1139E: The link type {0} of
the OSE transport is not valid. Explanation: None.
User Response: None.
CHKW1140E: The log file mask of
the OSE transport is required. Explanation: None. User
Response: None.
CHKW1141E: The log file mask {0} of
the OSE transport is not valid. Explanation: None.
User Response: None.
CHKW1142E: The link type of the
OSE transport is required. Explanation: None. User Response:
None.
CHKW1143E: The clone index {0} of the OSE transport
must be greater than or equal to {1}. Explanation: None.
User Response: None.
CHKW1144E: The native log file
of the OSE transport is required. Explanation: None.
User Response: None.
CHKW1145E: The native log file
{0} of the OSE transport is not valid. Explanation: None.
User Response: None.
CHKW1146E: The performance monitor
enablement is required. Explanation: None. User Response:
None.
CHKW1147E: The specification of the performance
monitor is required. Explanation: None. User Response:
None.
CHKW1148E: The specification {0} of the performance
monitor is not valid. Explanation: None. User Response:
None.
CHKW1900I: IBM WebSphere Validation
Explanation: None. User Response: None.
CHKW1901I: Application Server Validation Explanation: None.
User Response: None.
CHKW1902E: An internal error has
occurred during application server validation. Please check the log files
for more information on the error that occurred. Explanation:
None. User Response: None.
CHKW1903E: An
object of an unrecognized type was sent for application server validation.
This is an internal error. The object type is {0}. Explanation:
None. User Response: None.
CHKW2004E: Duplicated
path map entry symbolic name {0}. Explanation: None.
User Response: None.
CHKW2005E: The symbolic name of
a path map entry is required. Explanation: None. User
Response: None.
CHKW2006E: The symbolic name of the
path map entry {0} is not valid. Explanation: None.
User Response: None.
CHKW2007E: The path of the path
map entry is required. Explanation: None. User Response:
None.
CHKW2008E: The path map entry's path is empty.
Explanation: None. User Response: None.
CHKW2009E: The path map entry's path {0} is not valid. Explanation:
None. User Response: None.
CHKW2010E: The
process definition of a server is required. Explanation: None.
User Response: None.
CHKW2011E: The name of a server
is required. Explanation: None. User Response: None.
CHKW2012E: The server name is not valid {0}. Explanation: None.
User Response: None.
CHKW2013E: The executable target
kind of a java process definition is required. Explanation: None.
User Response: None.
CHKW2014E: The executable target
kind {0} is not valid. Explanation: None. User Response:
None.
CHKW2015E: The executable target of a java process
definition is required. Explanation: None. User Response:
None.
CHKW2016E: The executable target {0} is not valid
as a java class name. Explanation: None. User Response:
None.
CHKW2017E: The executable target {0} is not valid
as a JAR file name. Explanation: None. User Response:
None.
CHKW2018E: The java virtual machine initial heap
size {0} cannot be less than {1}. Explanation: None.
User Response: None.
CHKW2019E: The java virtual machine
maximum heap size {0} cannot be less than {1}. Explanation: None.
User Response: None.
CHKW2020E: The java virtual machine
initial heap size {0} cannot be less than the maximum heap size {1}.
Explanation: None. User Response: None.
CHKW2021E: The java virtual machine heap profile arguments {0} are not valid.
Explanation: None. User Response: None.
CHKW2022E: The java virtual machine debug arguments {0} are not valid.
Explanation: None. User Response: None.
CHKW2023E: The java virtual machine executable jar path is required.
Explanation: None. User Response: None.
CHKW2024E: The java virtual machine executable jar path {0} is not valid.
Explanation: None. User Response: None.
CHKW2025E: The process definition executable name is required.
Explanation: None. User Response: None.
CHKW2026E: The process definition working directory is required.
Explanation: None. User Response: None.
CHKW2027E: The process definition working directory {0} is not valid.
Explanation: None. User Response: None.
CHKW2028E: The system property name is required. Explanation:
None. User Response: None.
CHKW2029E: The
standard output file name of the output redirect is required.
Explanation: None. User Response: None.
CHKW2030E: The standard error file name of the output redirect is required.
Explanation: None. User Response: None.
CHKW2031E: The external configuration URL of the custom service is required.
Explanation: None. User Response: None.
CHKW2032E: The external configuration URL {0} of the custom service is not
valid. Explanation: None. User Response: None.
CHKW2033E: The class name of the custom service is required. Explanation:
None. User Response: None.
CHKW2034E: The
class name {0} of the custom service is not valid. Explanation:
None. User Response: None.
CHKW2035E: The
display name of the custom service is required. Explanation: None.
User Response: None.
CHKW2036E: The process priority
of the process execution is required. Explanation: None.
User Response: None.
CHKW2037E: The process priority
{0} of the process process execution must be greater than or equal to {1}.
Explanation: None. User Response: None.
CHKW2038E: The umask of the process execution {0} must have exactly 3 characters.
Explanation: None. User Response: None.
CHKW2039E: The umask of the process execution {0} must have octal ('0' through
'7') characters. Explanation: None. User Response:
None.
CHKW2040E: The run-as-user of the process execution
is required. Explanation: None. User Response: None.
CHKW3000I: IBM WebSphere Validation Explanation: None.
User Response: None.
CHKW3001I: Resources Validation
Explanation: None. User Response: None.
CHKW3002E: An internal error has occurred during resources validation. Please
check the log files for more information on the error that occurred.
Explanation: None. User Response: None.
CHKW3003E: An object of an unrecognized type was sent for resources validation.
This is an internal error. The object type is {0}. Explanation:
None. User Response: None.
CHKW3004E: The
name of the J2EE resource provider is required. Explanation: None.
User Response: None.
CHKW3005E: The URL prefix of the
JDBC driver is required. Explanation: None. User Response:
None. CHKW3006E: The implementation class name of the JDBC driver
is required. Explanation: None. User Response: None.
CHKW3007E: The database name of the data source is required. Explanation:
None. User Response: None.
CHKW3008E: The
minimum pool size of the data source is required. Explanation:
None. User Response: None.
CHKW3009E: Conflicting
minimum pool size of the data source. Explanation: None.
User Response: None.
CHKW3010E: The maximum pool size
of the data source is required. Explanation: None.
User Response: None.
CHKW3011E: Maximum pool size of
the data source must be more than minimum pool size and at least 2.
Explanation: None. User Response: None.
CHKW3012E: The connection timeout of the data source is required.
Explanation: None. User Response: None.
CHKW3013E: Conflicting connection timeout of the data source.
Explanation: None. User Response: None.
CHKW3014E: The idle timeout of the data source is required. Explanation:
None. User Response: None.
CHKW3015E: Conflicting
idle timeout of the data source. Explanation: None.
User Response: None.
CHKW3016E: The orphan timeout
of the data source is required. Explanation: None.
User Response: None.
CHKW3017E: Conflicting orphan
timeout of the data source. Explanation: None. User
Response: None.
CHKW3018E: The statement cache size
of the data source is required. Explanation: None.
User Response: None.
CHKW3019E: Conflicting statement
cache size of the data source is required. Explanation: None.
User Response: None.
CHKW3020E: The External JNDI name
of the JMS destination is required. Explanation: None.
User Response: None.
CHKW3021E: The spec of the URL
is required. Explanation: None. User Response: None.
CHKW3022E: The stream handler class name of the URL provider is required.
Explanation: None. User Response: None.
CHKW3023E: The protocol of the URL provider is required. Explanation:
None. User Response: None.
CHKW3024E: The
display name of the J2C resource adaptor is required. Explanation:
None. User Response: None.
CHKW3025E: The
JNDI name of the J2EE resource factory is required. Explanation:
None. User Response: None.
CHKW3026E: The
name of the J2EE resource factory is required. Explanation: None.
User Response: None.
CHKW3027E: The J2EE resource provider
of J2EE resource factory is absent. Explanation: None.
User Response: None.
CHKW3028E: The type of the resource
property is required. Explanation: None. User Response:
None.
CHKW3029E: The value of the resource property
is required. Explanation: None. User Response: None.
CHKW3030E: The external JNDI name of the JMS connection factory is required.
Explanation: None. User Response: None.
CHKW3031E: The classpath of the resource provider reference is required.
Explanation: None. User Response: None.
CHKW3032E: The J2EE resource provider resource provider reference is absent.
Explanation: None. User Response: None.
CHKW3500E: An internal error has occurred. Please check the log files for
more information on the error occurred. Explanation: None.
User Response: None.
CHKW3550E: An web application
binding with an invalid or null web application reference has been detected
in the bindings. Explanation: None. User Response:
None.
CHKW3551E: An EJB binding with an invalid or
null EJB reference has been detected in the EJB bindings under EJB {0}.
Explanation: None. User Response: None.
CHKW3552W: No JNDI name has been specified for the EJB ref for home {0} under
EJB {1}. JNDI names must be specified for all EJB refs in the EJB jar before
the module may be started in the application server. Explanation:
None. User Response: None.
CHKW3553E: An
EJB binding with an invalid or null resource reference has been detected in
the EJB bindings under EJB {0}. Explanation: None.
User Response: None.
CHKW3554W: No JNDI name has been
specified for the resource ref for resource of name {0} and type {1} under
EJB {2}. JNDI names must be specified for all resource refs in the EJB jar
before the module may be started in the application server. Explanation:
None. User Response: None.
CHKW4002E: An
internal error has occurred during IBM web application extensions validation.
Check the log files for more information on the error that occurred.
Explanation: None. User Response: None.
CHKW4003E: The web application extension has a missing or invalid reference
to the web application. Explanation: None. User Response:
None.
CHKW4004E: Invalid reloadInterval, {0}, specified
for web application {1}. Reload interval must be > 0. Explanation:
None. User Response: None.
CHKW4030E: Missing
default error page URI for web application {0}. Explanation: None.
User Response: None.
CHKW4040E: More than one servlet
extension has been specified for servlet {0} for web application {1}.
Explanation: None. User Response: None.
CHKW4050E: More than one file serving attribute with name {0} has been specified
for web application {1}. Explanation: None. User Response:
None.
CHKW4060E: Missing name on file serving attribute
for web application {0}. Explanation: None. User Response:
None.
CHKW4070E: More than one invoker attribute with
the name {0} have been specified for web application {1}. Explanation:
None. User Response: None.
CHKW4080E: Missing
name on invoker attribute for web application {0). Explanation:
None. User Response: None.
CHKW4095E: Multiple
mime type filters with the same type, {0} for web application {1}.
Explanation: None. User Response: None.
CHKW4096E: One or more mime filters specified for web application {0} have
a missing or invalid type specified. Explanation: None.
User Response: None.
CHKW4097E: The mime filter for
type {0} specified for web application {1} has a missing or invalid target
specified. Explanation: None. User Response: None.
CHKW4098E: One or more markup languages specified for web application {0}
is missing a name. Explanation: None. User Response:
None.
CHKW4101E: Markup language {0} for web application
{1} has a missing or invalid mime type. Explanation: None.
User Response: None.
CHKW4102E: The default page for
markup language {0} for web application {1} is not contained in the web application's
list of pages. Explanation: None. User Response: None.
CHKW4103E: The error page for markup language {0} for web application {1}
is not contained in the web application's list of pages. Explanation:
None. User Response: None.
CHKW4105E: One
or more pages for markup language {0} for web application {1} is missing a
name. Explanation: None. User Response: None.
CHKW4106E: Pages {0} for markup language {1} for web application {2} has a
missing or invalid URI. Explanation: None. User Response:
None.
CHKW4110E: Multiple JSP attributes with name
{0} have been specified for web application {1} Explanation: None.
User Response: None.
CHKW4111E: One or more JSP attributes
specified for web application {0} is missing a name. Explanation:
None. User Response: None.
CHKW4500E: An
internal error has occurred. Please check the log files for more information
on the error occurred. Explanation: None. User Response:
None.
CHKW4510E: Invalid null EJB jar reference in
EJB jar binding. Explanation: None. User Response:
None.
CHKW4511E: An EJB binding with an invalid or
null EJB reference has been detected in the EJB bindings. Explanation:
None. User Response: None.
CHKW4512W: No
binding information has been specified for EJB, {0}. Binding information such
as JNDI names must be specified for all EJB in an EJB jar before the module
may be started in the application server. Explanation: None.
User Response: None.
CHKW4513W: No JNDI name has been
specified for EJB, {0}. JNDI names must be specified for all EJB in an EJB
jar before they can be started in the application server. Explanation:
None. User Response: None.
CHKW4514E: An
EJB binding with an invalid or null EJB reference has been detected in the
EJB bindings under EJB {0}. Explanation: None. User
Response: None.
CHKW4515W: No JNDI name has been specified
for the EJB ref for home {0} under EJB {1}. JNDI names must be specified for
all EJB refs in the EJB jar before the module may be started in the application
server. Explanation: None. User Response: None.
CHKW4516E: An EJB binding with an invalid or null resource reference has been
detected in the EJB bindings under EJB {0}. Explanation: None.
User Response: None.
CHKW4517W: No JNDI name has been
specified for the resource ref for resource of name {0} and type {1} under
EJB {2}. JNDI names must be specified for all resource refs in the EJB jar
before the module may be started in the application server. Explanation:
None. User Response: None.
CHKW4518W: No
datasource has been specified for the container managed entity bean {0}. The
default datasource specified for the EJB jar will be used. Explanation:
None. User Response: None.
CHKW4519W: No
JNDI name for a datasource has been specified for the container managed entity
bean {0}. The default datasource specified for the EJB jar will be used.
Explanation: None. User Response: None.
CHKW4520W: No default CMP datasource has been specified for this EJB jar,
and some container managed entity beans do not have CMP datasource JNDI names
specified. The default CMP datasource of the EJB Container will be used for
all container managed entity beans with no CMP datasource specified.
Explanation: None. User Response: None.
CHKW5000E: An internal error has occurred. Please check the log files for
more information on the error occurred. Explanation: None.
User Response: None.
CHKW5001E: The validation target
is not valid for {1}. Explanation: None. User Response:
None.
CHKW5002E: There is no reference of {0} in {1}.
Explanation: None. User Response: None.
CHKW5003E: The total number of {0} in {1} is not {2} . Explanation:
None. User Response: None.
CHKW5004E: The
reference of {0} in {1} is not defined in {2}. Explanation: None.
User Response: None.
CHKW5005E: The reference of {0}
in {1} is duplicate. Explanation: None. User Response:
None.
CHKW5006E: The value of {0} in {1}, {2}, is not
valid. Explanation: None. User Response: None.
CHKW5007E: The type of {0} in {1} is not {2}. Explanation: None.
User Response: None.
CHKW5101W: The definition of "{0}"
in {1} is overlapping. Explanation: None. User Response:
None.
CHKW5102W: The specified {0} policy in {1} ,{2},
is unsupported in this release of WebSphere. Explanation: None.
User Response: None.
CHKW5201E: The relationship is
{0} , the value of forward in {1}, {2}, is not valid. Explanation:
None. User Response: None.
CHKW5202E: The
relationship is {0}, the value of forward for the two roles must be opposite.
Explanation: None. User Response: None.
CHKW5203E: The total number of {2} in {0} is not {3} in {1}. Explanation:
None. User Response: None.
CHKW5500I: IBM
WebSphere Validation Explanation: None. User Response:
None.
CHKW5501I: Security Validation Explanation:
None. User Response: None.
CHKW5502E: An
internal error has occurred during security validation. Please check the log
files for more information on the error that occurred. Explanation:
None. User Response: None.
CHKW5503E: An
object of an unrecognized type was sent for security validation. This is an
internal error. The object type is {0}. Explanation: None.
User Response: None.
CHKW5504E: The name of the SSL
property is required. Explanation: None. User Response:
None.
CHKW5505E: The LDAP user registry must have an
LDAP search filter. Explanation: None. User Response:
None.
CHKW5506E: Security must have a secure socket
layer. Explanation: None. User Response: None.
CHKW6500E: Invalid null application reference in application binding.
Explanation: None. User Response: None.
CHKW6501E: Could not resolve validation application for application binding.
Explanation: None. User Response: None.
CHKW6502E: No subject (user or group) has been specified for the security
role, {0}. Explanation: None. User Response: None.
CHKW6503E: Could not resolve validation application for application binding.
Explanation: None. User Response: None.
CHKW6504E: More than one role assignment exists for security role, {0}.
Explanation: None. User Response: None.
CHKW6505W: A subject (user or group) has not been assigned for security role,
{0}. The security role assignment should be made prior to running the application.
Explanation: None. User Response: None.
CHKW6507W: A run as role {0} specified for enterprise bean {1} has not been
assigned to an identity. Explanation: None. User Response:
None.
CHKW6508E: An internal error has occurred: {0}.
Please check the log files for more information on the error occurred.
Explanation: None. User Response: None.
CHKW6700E: An internal error has occurred. Please check the log files for
more information on the error occurred. Explanation: None.
User Response: None.
CHKW6701E: The application extension
has a missing or invalid reference to the application. Explanation:
None. User Response: None.
CHKW6702E: The
module extension has a missing or invalid reference to a module for application
{0}. Explanation: None. User Response: None.
CHKW6703E: More than one module extension has been specified for module {0}
in application {1}. Explanation: None. User Response:
None.
CHKW7000I: IBM ThinAdmin Prerequisite Validation
Explanation: None. User Response: None.
CHKW7002E: An internal error has occurred during thin administration prerequisite
validation. Please check the log files for more information on the error that
occurred. Explanation: None. User Response: None.
CHKW7010E: You have disabled cookies in the session manager which is running
the administration application. The administration application relies on cookies
being enabled to operate properly the next time the server is restarted. An
alternative is to run the administration application in a separate process
from your applications. Explanation: None. User Response:
None.
CHKW7011E: You have changed the maximum age for
cookies in the session manager to a value which will cause the administration
application to stop operating, or operate in an indeterminate manner. The
administration application relies on cookies being enabled to operate properly
the next time the server is restarted. An alternative is to run the administration
application in a separate process from your applications. Explanation:
None. User Response: None.
CHKW7012E: When
secure cookies are enabled in the session manager, the administration application
(as well as your own) must be invoked via HTTP rather than http.
Explanation: None. User Response: None.
CHKW7013E: You have changed the path for cookies in the session manager to
a value which will cause the administration application to stop operating,
or operate in an indeterminate manner. The administration application relies
on the cookie path being '/' or '/administration' to operate properly. An
alternative is to run the administratioin application in a separate process
from your applications. Explanation: None. User Response:
None.
CHKW7014E: You have disabled session management
in the web container which is running the administration application. The
administration application relies on session management being enabled to operate
properly the next time the server is restarted. An alternative is to run the
administration application in a separate process from your applications.
Explanation: None. User Response: None.
CHKW7015E: Administration application will not be available because application
server desiredExecutionState is STOP. Explanation: None.
User Response: None.
CNTR0001W: Cannot passivate {0} {1} {2} Explanation: The
container was unable to passivate a stateful session bean User Response:
Check that passivation directory exists, the process has write permissions
in that directory, and that there is enough disk space.
CNTR0002W: Failed to get the wrapper for home: {0} Explanation:
An internal error occurred within the container. User Response:
Contact IBM support.
CNTR0003W: Cannot activate {0}
{1} {2} Explanation: The container failed to activate a stateful
session bean from storage due to exception {2}. User Response: This
condition could occur if either an IOException or ClassNotFoundException occur.
CNTR0004E: Attempt to acquire lock was interrupted {0} Explanation:
A thread attempting to acquire an exclusive lock within the container
was interrupted while waiting for the lock. User Response: Contact
IBM support.
CNTR0005W: Unable to passivate enterprise
bean {0} {1} {2} Explanation: The container was unable to passivate
an enterprise bean due to exception {2}. User Response: None.
CNTR0006W: Failed to connect EJBObject to orb: {0} Explanation:
On an attempt to activate a stateful bean the container failed to connect
a deserialized stub (reference) object. User Response: Contact
IBM support.
CNTR0007W: The resolveObject failed to resolve
Enterprise bean's beanO reference: {0} activatedBeanO: {1} Explanation:
An internal container error has occurred. User Response: Contact
IBM support.
CNTR0008W: Cannot remove {0} {1} {2}
Explanation: The container was unable to remove a passivated stateful
session bean from storage due to exception {2}. User Response: None.
CNTR0009W: Bean has not been installed: {0} Explanation: An
attempt was made to access an enterprise bean which has not been installed
in the container. User Response: None.
CNTR0010W:
NumberFormatException occurred while converting <env-entry> {0} <env-entry>
{1} : {2} Explanation: The container was unable to process
an environment entry due to a NumberFormatException. User Response:
Ensure that the value for the environment entry is a valid string representation
for the specified type.
CNTR0011W: Invalid type encountered
in java:comp/env context <env-entry-name> {0} Explanation:
The container encountered an invalid type for an environment entry.
User Response: Ensure that the environment entry type is one of : String,Integer,Boolean,Double,Byte,Short,Long
or Float.
CNTR0012W: Collaborator {0} threw unexpected
exception - proceeding with remaining collaborators: {1} Explanation:
An internal container error has occurred. User Response: Contact
IBM support.
CNTR0013W: Unable to map exception {0} : {1}
Explanation: The container was unable to map exception {0}
to a valid CORBA exception. User Response: None.
CNTR0014W: StatefulBeanReaper thread was interrupted. Terminating {0}
Explanation: An internal error occurred in the container. User
Response: Contact IBM support.
CNTR0015W: Unexpected
exception during stateful bean cleanup {0} {1} Explanation: None.
User Response: None.
CNTR0016W: Remove from passivation
store failed for bean {0}: {1} Explanation: The container was
unable to remove a passivated stateful session bean from the passivation store.
User Response: None.
CNTR0017W: Security collaborator
threw unexpected exception: {0} Explanation: An internal error
has occurred in the container. User Response: Contact IBM support.
CNTR0018E: Non-application exception occurred: {0} Explanation:
A system exception occurred while invoking a method on an Enterprise Java
Bean. User Response: None.
CNTR0019E: Non-application
exception occurred while processing method {1}: {0} Explanation:
A system exception occurred while invoking a method on an Enterprise Java
Bean. User Response: None.
CNTR0020E: Non-application
exception occurred while processing method {1} on bean {2}: {0}
Explanation: A system exception occurred while invoking a method on an
Enterprise Java Bean. User Response: None.
CNTR0021E: Non-application exception occurred on bean {1}: {0}
Explanation: A system exception occurred while invoking a method on an
Enterprise Java Bean. User Response: None.
CNTR0022E: Transaction coordinator not available: {0} Explanation:
An internal error has occurred in the container. User Response:
Contact IBM support.
CNTR0023W: {0} does not exist.
Container will use current directory for passivating beans Explanation:
The container failed to open the passivation directory. User Response:
Ensure that the passivation directory exists.
CNTR0024W:
Unable to open input stream: {0} {1} {2} Explanation: The container
encountered an IOException while attempting to open a file. User Response:
None.
CNTR0025W: Unable to open output stream: {0}
{1} {2} Explanation: The container encountered an IOException
while attempting to open a file. User Response: None.
CNTR0026W: Datasource name for CMP bean {0} is null. Bean will be unavailable
for use Explanation: No datasource has been specified for the
entity bean {0}. User Response: Specify a datasource for the entity
bean or a default datasource for the module.
CNTR0027W:
Failed to commit connection: {0} Explanation: None.
User Response: None.
CNTR0028W: Failed to close connection:
{0} Explanation: None. User Response: None.
CNTR0029E: Protocol error: multiple suspended transactions Explanation:
An internal error has occurred in the container. User Response:
Contact IBM support.
CNTR0030E: Cannot obtain the
transaction coordinator: {0} Explanation: An internal error
has occurred in the container. User Response: Contact IBM support.
CNTR0031W: Error starting CMP bean: {0} Explanation:
None User Response: None
CNTR0032W:
Error creating CMP persister using datasource: {0} Explanation:
None User Response: None
CNTR0033E:
EJB container ignoring caught unexpected exception: {0} Explanation:
An internal error has occurred in the container. User Response:
Contact IBM support.
CNTR0034I: ContainerEJBException.getExceptionChain
is returning an incomplete list of exceptions. Explanation: Informational
message for IBM support. User Response: Contact IBM support.
CNTR0035E: EJB container caught {0} and is throwing {1}
Explanation: Informational message for IBM support. User Response:
Contact IBM support.
CNTR0036E: EJB container
does not support using the bean instance for finder methods on EJB 1.x container
managed persistence and is throwing {0} Explanation: A bean
configured for EJB 1.x container managed persistence has attempted to invoke
methods on a bean instance for finder method processing. User Response:
Redeploy the bean. If the problem persists, contact IBM support.
CNTR0037E: Prepared statement does not map to connection.
Explanation: An internal error detected by EJB container. User
Response:Contact IBM support.
CNTR0038W: The
TX attribute needs to be changed to eliminate potential lost updates to bean
{0} when used concurrently by multiple transactions. The bean should not
be using the TX_NOT_SUPPORTED, TX_NEVER, or TX_SUPPORTS transaction attribute.
Explanation: A transaction that was started by using either
the TX_NOT_SUPPORTED, TX_NEVER, or the TX_SUPPORTS \ # transaction attribute.
The transaction updated a CMP entity bean and is storing the update to persistent
store. \ # If a concurrent transaction the CMP entity bean with the same primary
key value, the updates of one transaction \ # may overlay the updates of the
other transaction. User Response:The application must ensure that
concurrent transactions never update a CMP entity bean with the same primary
key value. \ # If that can not be done, then which ever bean begins the transaction
must use a transaction attribute other than \ # TX_NEVER, TX_NOT_SUPPORTED,
or TX_SUPPORTS to ensure data consistency is maintained
CNTR0039E: EJB container caught {0} and is rethrowing the caught exception
Explanation: Informational message for IBM support.
User Response:Contact IBM support.
CNTR0040E:
Finder failure as a result of exception {0} Explanation: Informational
message for IBM support. User Response:Contact IBM support.
CNTR0041W: Minimum pool size specified for bean {0} not a valid
integer: {1} Default used instead. Explanation: Only a positive
integer may be specified for the minimum pool size. The default value will
be used instead. User Response:Change the value to a positive
integer.
CNTR0042W: Maximum pool size specified
for bean {0} not a valid integer: {1} Default used instead.
Explanation: Only a positive integer may be specified for the maximum
pool size. The default value will be used instead. User Response:
Change the value to a positive integer.
CNTR0043W:
Minimum pool size specified for bean {0} is greater than maximum pool size
specified: ({1},{2}) Defaults used instead. Explanation: The
maximum pool size must be greater than or equal to the minimum size. Default
values will be used for min and max. User Response:Change the
max size to be greater than or equal to the min size.
CNTR0044I: (Min,Max) pool size is ({0},{1}) for bean {2} Explanation:
These are the minimum and maximum pool size values that will be used for
this bean type. User Response:None.
CNTR0045I: Read-only attribute on findByPrimaryKey method overridden to true
for bean: <All> Explanation: The user has specified that
the findByPrimaryKey read-only attribute be overridden to true on all EntityBeans.
User Response:None.
CNTR0046E: Using
Commit Option A with Optimistic Concurrency is not supported: <All>
Explanation: The user has specified Commit Option A and Optimistic Concurrency
Control on an Enterprise Bean. This combination is not supported.
User Response:Change the enterprise bean to use either Commit Option A
or Optimistic Concurrency Control, but not both.
CONM0000E: The Connection Manager Application Programming Interfaces have
been removed. Use the Connection Pooling Application Programming Interfaces.
Explanation: The methods being called have been removed.
User Response: Use the new Connection Pooling API. <! MSGEND
--> <! MSGSTART --> CONM0006E: Could
not parse {0} setting ({1}) for data source {2} Explanation: None.
User Response: None. <! MSGEND --> <! MSGSTART -->
CONM0007E: Property {0} cannot be null
or blank Explanation: None. User Response: None.
<! MSGEND --> <! MSGSTART -->
CONM0008E: The following exception occurred introspecting class {0}: {1}
Explanation: None. User Response: None. <! MSGEND
--> <! MSGSTART --> CONM0009W: Could
not find the property {0} on class {1} Explanation: None.
User Response: None. <! MSGEND --> <! MSGSTART --> CONM0010W: Could not find method to write property
{0} on class {1} Explanation: None. User Response:
None. <! MSGEND --> <! MSGSTART -->
CONM0011W: An exception occurred setting the property {0} on class {1}: {2}
Explanation: None. User Response: None. <!
MSGEND --> <! MSGSTART --> CONM0012E:
Error encrypting default password: {0} Explanation: None.
User Response: None. <! MSGEND --> <! MSGSTART --> CONM0013E: Error decrypting default password: {0}
Explanation: None. User Response: None. <! MSGEND
--> <! MSGSTART --> CONM1000E: Value
"{0}" is invalid for property ({1}) for data source ({2}). Explanation:
One of the DataSource properties is in an unexpected format.
User Response: Verify all the properties for the data source are correct.
<! MSGEND --> <! MSGSTART -->
CONM1001E: Required property ({0}) is missing for data source ({1}).
Explanation: A required property is missing. User Response: Verify
that all required properties are being configured on the data source. <!
MSGEND --> <! MSGSTART --> CONM1002E:
Error decrypting default password: {0} Explanation: An exception
occurred during the decryption of a password. Either the encrypted password
data is corrupt or was encoded in an unsupported encryption. User
Response: Replace the encrypted password with uncorrupt data or make sure
it is encoded with a supported encryption algorithm. <! MSGEND --> <!
MSGSTART --> CONM1003E: Error encrypting
default password: {0} Explanation: An exception occurred during
the encryption of a password. The password data is corrupt. User
Response: Replace the corrupted password with uncorrupt data. <!
MSGEND --> <! MSGSTART --> CONM1004W:
The user for the supplied password is missing for data source ({0}).
Explanation: The data source password is supplied, but the user is not;
the password is ignored User Response: Supply the user corresponding
to the password or remove the password <! MSGEND --> <! MSGSTART
--> CONM1005W: The password for the
supplied user "{0}", is missing for data source ({1}). Explanation:
The data source user is supplied, but the password is not; the user is
ignored User Response: Supply the password corresponding to the
user or remove the user <! MSGEND --> <! MSGSTART --> CONM1006E: The data source class name "{0}" could not
be found for data source ({1}). Explanation: The data source
class name supplied could not be found User Response: Ensure that
the jar/zip file with the specified class name has been installed <!
MSGEND --> <! MSGSTART --> CONM2000E:
Unable to obtain any portability layer for data source ({0}).
Explanation: Can not map this driver to a portability layer inclding the
generic portability layer. User Response: Ensure 'cm.jar' is in
the classpath and accessable. <! MSGEND --> <! MSGSTART --> CONM6000W: Illegal use of 1PC resource in transaction
Explanation: Trying to call 'prepare' on a one phase resource.
User Response: None. <! MSGEND --> <! MSGSTART -->
CONM6001W: Failed to expand connection
pool; waiting for a free connection instead Explanation: A
connection could not be created. User Response: Make sure the
database can create as many connections as the connection pool. <!
MSGEND --> <! MSGSTART --> CONM6002W:
Failed to get an XA resource {0} Explanation: Failed to get
an XA resource while 'destroying' a connection. Calling destory means to
close the connection and remove it from the free pool. User Response:
None. <! MSGEND --> <! MSGSTART -->
CONM6004E: The required default username for the supplied default password
is missing for data source ({0}). Explanation: A password was
supplied, but no user was supplied. User Response: Supply a valid
username and password, or remove the password. <! MSGEND --> <!
MSGSTART --> CONM6006E: The required
default password for the supplied default username, "{0}", is missing for
data source ({1}). Explanation: The default password is missing.
User Response: Supply a valid password for the default user. <!
MSGEND --> <! MSGSTART --> CONM6007I:
The connection pool was destroyed for data source ({0}). Explanation:
None. User Response: None. <! MSGEND --> <! MSGSTART
--> CONM6008W: Timed out waiting for
a connection from data source ({0}). Explanation: All connections
in the pool were in use for the duration fo the connectionTimeOut period.
User Response: 1) Increase connectionTimeout Value. 2) Increase
maximum number of connections and ensure the database can handle the increased
connection load. <! MSGEND --> <! MSGSTART --> CONM6009E: Failed to get connection to the database
from datasource ({0}). Explanation: Database failed to service
a request for a new connection. User Response: Examine SQL State
code from database to determine exact cause of problem. <! MSGEND
--> <! MSGSTART --> CONM6010W: StaleConnectionException
caught. Purging entire connection pool for data source ({0}).
Explanation: Got a SateConnectionException. User Response: Examine
SQL State code from database to dertermine exact cause of problem. <!
MSGEND --> <! MSGSTART --> CONM6011E:
Connection Pooling Internal Error. Illegal ConnectO state, "{0}", on data
source ({1}). Explanation: Most likely an interanl error.
User Response: Call IBM for service. <! MSGEND --> <! MSGSTART
--> CONM6012E: Database error setting
AutoCommit for data source ({0}). Explanation: Database unable
to service request. User Response: Examine SQL State code from
database to dertermine exact cause of problem. <! MSGEND --> <!
MSGSTART --> CONM6013E: Connection has
outstanding work and can not join a global transaction for data source ({0}).
Explanation: Connection has work that is either uncommitted
or not rolled back. User Response: Commit or roll back the work
on the connection prior to using the connection in a global transaction. <!
MSGEND --> <! MSGSTART --> CONM6014I:
Caught exception ({0}) in method ({1}). Throwing new exception ({2}). The
original exception''s stack trace was: {3} Explanation: Informational
message to note that one type of exception was caught and another type thrown.
User Response: None. <! MSGEND --> <! MSGSTART -->
CONM6015E: Could not load XAResourceFactory
in method ({0}) because the class was not found. Throwing new ({1}).
Explanation: Needed class not found. User Response: Make sure
class exists in classpath and is accessable by the user. <! MSGEND
--> <! MSGSTART --> CONM6016E: Failed
to enlist with transaction. Throwing new ({0}). Explanation:
Enlist returned false for some reason. User Response: None.
<! MSGEND --> <! MSGSTART -->
CONM6017E: In method (enlist) the connection is already associated with another
transaction. Explanation: Trying to enlist this connection
in a different transaction than it is already associated with. User
Response: Don't cache a connection for use by more than one thread in
multiple concurrent transactions. <! MSGEND --> <! MSGSTART -->
CONM6018E: Calling unilateralCommit
in not allowed on a JTAEnabled connection in a global transaction.
Explanation: unilateralCommit was called on a JTAEnabled connection in
a global transaction. User Response: None. <! MSGEND
--> <! MSGSTART --> CONM7000W: Unrecognized
database or driver {0}; using generic settings Explanation: The
database product ID or driver class name was not found in the list of known
databases. User Response: Check to ensure the spelling is correct
and that the database is supported. <! MSGEND --> <! MSGSTART
--> CONM7001E: The following exception
occurred introspecting class {0}: {1} Explanation: An error
occurred during introspection of the data source class. User Response:
Examine the underlying exception for more details. <! MSGEND
--> <! MSGSTART --> CONM7002W: Could
not find the property {0} on class {1} Explanation: The property
to be set does not exist on the class. User Response: Ensure that
the property name specified is correct. <! MSGEND --> <! MSGSTART
--> CONM7003W: Could not find method
to write property {0} on class {1} Explanation: A method to
write the property does not exist on the class. User Response: The
property specified exists, but a write method does not; ensure that the property
specified can be written to the data source. <! MSGEND --> <!
MSGSTART --> CONM7004W: An exception
occurred setting the property {0} on class {1}: {2} Explanation:
An exception occurred setting the property specified to the data source
User Response: Examine the underlying exception for more details <!
MSGEND --> <! MSGSTART --> CONM7005E:
The class ({0}) does not implement javax.sql.ConnectionPoolDataSource or javax.sql.XADataSource
Explanation: None. User Response: None. <!
MSGEND --> <! MSGSTART --> CONM7006E:
An exception occurred instantiating the class ({0}) for data source ({1}):
{2} Explanation: None. User Response: None. <!
MSGEND --> <! MSGSTART --> CONM7007I:
Mapping the following SQLException, with ErrorCode {0} and SQLState {1}, to
a StaleConnectionException: {2} Explanation: None.
User Response: None.
DBMN0001E: Coordinator {0} is not related to current
coordinator {1} Explanation: None.
User Response: None.
DBMN0002W: Error
in property format error. Using defaults {0} Explanation:
None. User Response: None.
DBMN0003E: Connection object is in local transaction context
Explanation: None. User Response: None.
DBMN0004W: Statement was canceled by another
thread Explanation: None.
User Response: None. DBMN0005W: Unable
to find hashed XA resource Explanation: None.
User Response: None.
DBMN0006W:
Transaction inactive {0} Explanation: None.
User Response: None. DBMN0007W:
Connection was pre-empted Explanation: None.
User Response: None.
DBMN0008W:
Local roll back failure {0} Explanation: None.
User Response: None. DBMN0009W:
Failure while creating new connection {0} Explanation:
None. User Response: None.
DBMN0010W: Current coordinator is null Explanation:
None. User Response: None.
DBMN0011E: Failed to get a connection: {0} Explanation:
None. User Response: None.
DBMN0012W: No mapping found in mapTable
Explanation: None. User Response: None.
DBMN0013W: Connection has been returned to the pool: {0}
Explanation: None. User Response:
None.
DBMN0014W: The transaction is
inactive {0} Explanation: None.
User Response: None.
DBMN0015W: Failure
while creating connection {0} Explanation: None.
User Response: None.
DBMN0016W:
Failed to roll back {0} Explanation: None.
User Response: None.
DBMN0017W:
Property object is null Explanation: None.
User Response: None.
DBMN0018W:
Failed to close a connection: {0} Explanation: None.
User Response: None.
DBMN0019W:
New user ID is set for the data source Explanation:
None. User Response: None.
DBMN0020E: Connection is freed Explanation:
None. User Response: None.
DBMN0021E: Failed to get a connection {0}
Explanation: None. User Response: None.
DBMN0022W: Connection object not found in table, mapTable.
Explanation: None. User Response:
None.
DBMN0023W: Failed to close a connection
{0} Explanation: None. User Response:
None.
DBMN0024E: Network protocol is
not set Explanation: None. User
Response: None. DBMN0025E: Registered
event listener object is null Explanation: None.
User Response: None.
DBMN0026W:
Failure while creating XAConnection {0} Explanation:
None. User Response: None.
DBMN0027E: Coordinator is null Explanation:
None. User Response: None.
DBMN0028E: Connection is in use Explanation:
None. User Response: None.
DBMN0029W: Connection object is not in connection table
Explanation: None. User Response: None.
DBMN0030W: New password is set for the data source
Explanation: None. User Response:
None.
DBMN0031W: Failed to unregister
a driver: {0} Explanation: None.
User Response: None.
DBMN0032I: Failed
to load the specified database driver: Explanation:
None. User Response: None.
DBMN0033W: Connection close failure {0}
Explanation: None. User Response: None.
--> DBMN0034E: Registered connection
pool is null Explanation: None.
User Response: None.
-->
DBMN0035W: Method enlist on JTSXA failed Explanation:
None. User Response: None.
--> DBMN0036W: The transaction state is invalid
Explanation: None. User Response:
None.
DRSW0001E: An error occurred communicating over DRS Check for communication
errors on either this machine, or the configured host of the server. Look
for WebSphere exceptions or errors on the server machine. Gather data and
contact service. Explanation: None. User Response:
None.
DRSW0002W: Connection to current host:port DRS
connect point lost. The DRS service will attempt to connect to other host:port
combinations specified in the configuration. Explanation:
None. User Response: None.
DRSW0003E: No
host:port DRS connect points responding - unable to submit or receive messages.
Check all host:port combinations specified in the DRS configuration for
general communication or WebSphere errors. Restart servers as appropriate
and contact service with any available log data. Explanation:
None. User Response: None. DYNA0001E: The priority value was not a valid number
for entry {0}. Use an integer instead of {1}. Explanation: The
user entered a non-integer or non-positive integer for the priority.
User Response: Change the priority value to a positive integer.
DYNA0002E: The timeout value was not a valid number for entry {0}. Use an
integer instead of {1}. Explanation: The user entered a non-integer
for the timeout. User Response: Change the timeout value to a numeral
integer.
DYNA0003E: Not caching {0} due to misconfiguration.
Explanation: The servlet specified was incorrectly configured
for an unknown reason. User Response: Check that legal, non-contradictory
values have been given, and that all required fields are specified.
DYNA0004E: A default cache entry generator was created, but given no configuration
information. This generator will use the URI with no parameters to generate
cache IDs. This information should be set in the servletcache.xml file.
Explanation: A servlet was configured with trivial configuration
information. This is legal, though unlikely correct, except for the simplest
cases. User Response: Verify that the servlet to be cached requires
only the invocation URI to determine uniqueness.
DYNA0005E:
Duplicate ExternalCacheGroup entry for address {0}. Explanation:
None. User Response: None.
DYNA0006E: ExternalCacheGroup
{0} was not found. Explanation: The external cache group
to which this servlet output should be forwarded, was not registered in
the global cache properties . User Response: Check the spelling
of this external cache group. If correct, define this group in the global
cache properties.
DYNA0007E: Error initializing external
cache adapter: {0} Explanation: The specified error was thrown
during external cache adapter initialization. User Response: Identify
the cause of the error from the error specific information provided in the
message
DYNA0008E: CacheUnit no longer exists.
Explanation: A message was either sent or received from a cache unit
that is no longer registered with this cache unit. User Response:
Verify that the specified cache unit should be active; if so, restart
the unit.
DYNA0009E: No element named {0} in document {1}.
Explanation: When parsing the configuration XML files,
an expected XML element was not found. User Response: Check
the XML file format against the documentation, looking for a misconfiguration.
DYNA0010E: No element named {0} in {1}. Explanation: When
parsing the configuration XML files, an expected XML element was not found.
User Response: Check the XML file format against the documentation,
looking for a misconfiguration.
DYNA0011E: Servlet cache
file {0} not found; caching is disabled Explanation: The
specified caching properties were not specified for this application server.
Caching is disabled. User Response: Build a cache configuration
XML file with the specified name. See documentation for instructions on
building this file.
DYNA0012I: Dynamic servlet caching
is enabled Explanation: Dynamic servlet caching is enabled.
User Response: None.
DYNA0013I: Dynamic servlet caching
is disabled Explanation: Dynamic servlet caching is disabled.
User Response: None.
DYNA0014I: {0} is a cacheable
URI Explanation: A servlet or JSP were initialized that
have a cache policy configured. User Response: None.
DYNA0015I: Dynamic Servlet Caching encountered an error: {0}
Explanation: General error message. User Response: Debug
the provided error.
DYNA0016I: Dumped dynamic servlet caching
statistics to: {0} Explanation: Cache statistics were written
to the specified file. User Response: None.
DYNA0017I: Joined group {0} Explanation: This cache unit successfully
joined a group of cooperating caches. User Response: None.
DYNA0018E: Error loading ID Generator {0} Explanation: Error
loading ID Generator. User Response: Debug the provided error.
DYNA0019E: Error loading MetaData Generator {0} Explanation: Error
loading MetaData Generator. User Response: Debug the provided error.
DYNA0020E: Unable to cache {0}, request attributes are not serializable
Explanation: Servlet output was marked as sharable between cache units,
which requires that all request attributes be serializable.
User Response: Modify the cache policy for this servlet so that its output
is not shared, or modify the application so that all request attributes are
serializable.
DYNA0021E: Unable to initialize cache unit
{0}: {1} Explanation: Unanticipated error initializing cache
unit. User Response: Debug the provided error.
DYNA0022E: Error processing dynamic cache configuration: {0} Explanation:
Unanticipated error processing cache configuration. User Response:
Debug the provided error.
INST001E: Insufficient Disk Space Explanation: This message
is issued when the installation image size is greater than the available disk
space. User Response: Free up disk space. INST0002I:
Install Completed Successfully Explanation: The WebSphere installation
is complete. User Response: Proceed with configuration.
INST0003W: Warning no plug-in selected Explanation: A plug-in
must be selected for installation to proceed. User Response: Select
a plug-in that corresponds to the Web Server configured on the system. J2CA0001E: An exception
occurred while trying to read the Resource Adapter Deployment Descriptor for
{0} from the namespace: {1}. Explanation: This message indicates
a problem with the Systems Management configuration of the Resource Adapter. A
Deployment Descriptor does exist for this Resource Adapter, but it is not
in the right format to read in and process. User Response: This
would normally indicate a problem with Systems Management and/or the underlying
data model. Write a defect.
J2CA0002W: There is no
Resource Adapter Deployment Descriptor available for {0}. Explanation:
This message indicates a problem with the Systems Management configuration
for the Resource Adapter. A Deployment Descriptor does not exist for
this Resource Adapter. User Response: This would normally indicate
a problem with Systems Management and/or the underlying data model. Write
a defect.
J2CA0003E: An exception occurred while trying
to read the Connection Factory Properties for {0} from the namespace: {1}.
Explanation: This message indicates a problem with the Systems
Management configuration of the Connection Factory. The Properties do
exist for the Connection Factory, but they are not in the right format to
read in and process. User Response: This would normally indicate
a problem with Systems Management and/or the underlying data model. Write
a defect..
J2CA0004W: There are no Connection Factory Properties
available for {0}. Explanation: This message indicates a problem
with the Systems Management configuration of the Connection Factory. The
Properties do not exist for this Connection Factory. User Response:
This would normally indicate a problem with Systems Management and/or
the underlying data model. Write a defect.
J2CA0005E:
An exception occurred while trying to read the Connection Pooling Properties
for {0} from the namespace: {1}. Explanation: This message
indicates a problem with the Systems Management configuration of the Connection
Factory. The Connection Pooling Properties do exist for the Connection
Factory, but they are not in the right format to read in and process.
User Response: This would normally indicate a problem with Systems Management
and/or the underlying data model. Write a defect.
J2CA0006W: There are no Connection Pooling Properties available for {0}.
Explanation: This message indicates a problem with the Systems Management
configuration of the Connection Factory. The Connection Pooling Properties
do not exist for this Connection Factory. User Response: This would
normally indicate a problem with Systems Management and/or the underlying
data model. Write a defect.
J2CA0007W: An exception
occurred while invoking method set{0} on {1} : {2}. Processing continued.
Explanation: This message indicates a problem with invoking
a method on a ManagedConnectionFactory object. The names of these methods
are determined by the name/value pairs contained in the Connection Factory
Properties. These in turn are based off the contents of the Resource
Adapter's ra.xml file. Processing will continue since the default values
for this particular property may be sufficient to continue execution. Or,
this particular property may not even be required by the ManagedConnectionFactory
object. User Response: This would normally indicate a mismatch
between the Resource Adapter's XML definition and the actual Java class provided
for the Resource Adapter's ManagedConnectionFactory. Write a defect
against the specific Resource Adapter.
J2CA0008W: Class
{0} did not contain method set{1}. Processing continued. Explanation:
This message indicates a missing method on a ManagedConnectionFactory
object. The names of these methods are determined by the name/value
pairs contained in the Connection Factory Properties. These in turn
are based off the contents of the Resource Adapter's ra.xml file. Processing
will continue since the default values for this particular property may be
sufficient to continue execution. Or, this particular property may not
even be required by the ManagedConnectionFactory object. User Response:
This would normally indicate a mismatch between the Resource Adapter's
XML definition and the actual Java class provided for the Resource Adapter's
ManagedConnectionFactory. Write a defect against the specific Resource
Adapter.
J2CA0009E: An exception occurred while trying
to instantiate the ManagedConnectionFactory class {0} : {1}. Explanation:
This message indicates a problem while attempting to create a ManagedConnectionFactory
object. There are several possible reasons for this problem. The
runtime (1) couldn't find the appropriate class for the ManagedConnectionFactory
via the current class loader, (2) couldn't create a TraceWriter object
for the ManagedConnectionFactory, (3) or couldn't create the ConnectionManager
object for the ManagedConnectionFactory. Any of these could also be related
to an invalid XML definition for the Resource Adapter. User Response:
Investigate the complete exception text for clues as to what the real
problem is. In most cases, this exception indicates a problem with the
J2C runtime and a defect should be written. Include the activity.log
with the defect. Include, if possible, a trace of the application server
with the following trace string: com.ibm.ejs.j2c.*=all=enabled
J2CA0010E: Parameter in method {0} is not of type Reference. Explanation:
The getObjectInstance method is invoked by the JNDI lookup processing
of the Resource. The JNDI lookup implementation should be passing in
a valid Reference object for the desired Resource. Either the Name Service
is passing in a bad object or the "Reference" object was created incorrectly
in the first place. User Response: This message is due to an error
in the internal J2C runtime processing and a defect should be written. Include
the activity.log with the defect. Include, if possible, a trace of the
application server with the following trace string: com.ibm.ejs.j2c.*=all=enabled
J2CA0011E: There is no connector name in the Reference object for method {0}.
Explanation: This message indicates a problem with the Reference
object that was initially stored in the JNDI name space. User Response:
This message is due to an error in the internal J2C runtime processing
and a defect should be written. Include the activity.log with the defect. Include,
if possible, a trace of the application server with the following trace string: com.ibm.ejs.j2c.*=all=enabled
J2CA0012E: The connector name is null in the Reference object for method {0}.
Explanation: This message indicates a problem with the Reference
object that was initially stored in the JNDI name space. User Response:
This message is due to an error in the internal J2C runtime processing
and a defect should be written. Include the activity.log with the defect. Include,
if possible, a trace of the application server with the following trace string: com.ibm.ejs.j2c.*=all=enabled
J2CA0013I: An exception occurred while trying to create ManagedConnectionFactory
for {0} : {1}. Explanation: This exception indicates a problem
with creating the ManagedConnectionFactory from the stored Reference in the
JNDI name space. User Response: This informational message provides
additional information for related error messages in the activity.log. Reference
those error messages for additional explanations and user responses.
J2CA0014I: An exception occurred while building the reference for JNDI deployment
of {0} : {1}. This error was absorbed and a null returned from the method.
Explanation: This exception indicates a problem with creating
the Reference object to be stored in the JNDI name space for the named Resource. This
problem will be detected and logged as an error later in the processing.
User Response: This informational message provides additional information
for related error messages in the activity.log. Reference those error
messages for additional explanations and user responses.
J2CA0015E: The Connection Pool Manager could not allocate a Managed Connection.
Explanation: The Pool Manager could not allocate a Managed
Connection. This may be due to properties associated with the Pool Manager
(ie. maximum connections exceeded). A NULL managed connection was returned
by the Pool Manager. User Response: Check for related messages
in the log that might indicate a user controlled source of the problem. If
there are no other indications, the message may be due to an error in the
internal J2C runtime processing and a defect should be written. Include
the activity.log with the defect. Include, if possible, a trace of the
application server with the following trace string: com.ibm.ejs.j2c.*=all=enabled
J2CA0016E: A two phase XA operation, {0}, was invoked within transaction ID
{1}. This resource adapter does not support two phase processing.
Explanation: This message indicates that an attempt was made to use the
connection within the context of an XA transaction along with other XA capable
resources. This is not a valid operation for this resource adapter.
User Response: Modify the logic to separate the resource usage into separate
transactions.
J2CA0017E: A transactional operation, {0},
was invoked within transaction ID {1}. This resource adapter does not support
transactional processing. Explanation: This message indicates
that an attempt was made to use the connection within a transactional context
and this resource adapter does not support transactional processing.
User Response: Modify the logic to remove the transactional context.
J2CA0018E: An exception occurred while trying to create Resource Adapter Connection
Factory {0} : {1}. Explanation: This message indicates a problem
with the Resource Adapter creating the desired Connection Factory. The
exception text should provide additional details on the actual problem.
User Response: If the exception text does not indicate a situation that
is user controlled, then a defect may be in order. Include the activity.log
with the defect. Include, if possible, a trace of the application server
with the following trace string: com.ibm.ejs.j2c.*=all=enabled
J2CA0019W: No Managed Connection Factory Properties data could be assembled
for {0}. Processing continued. Explanation: This message indicates
that due to other logged problems, the properties for the Managed Connection
Factory could not be assembled. This may or may not cause runtime problems
-- it will depend on the default values of the various properties as provided
by the Resource Adapter. User Response: Check for other related
messages that will further explain the specific problems with the property
data. If your connections seem to work okay, you could ignore this message. Otherwise,
attempt to follow the User Response sections as documented by the other messages.
J2CA0020E: The Connection Pool Manager could not allocate a Managed Connection:
{0}. Explanation: This message indicates that an exception
was thrown by the Pool Manager when attempting to allocate a Managed Connection. The
exception text should help with deciphering the problem encountered.
User Response: If there are no user controlled indications, the message
may be due to an error in the internal J2C runtime processing and a defect
should be written. Include the activity.log with the defect. Include,
if possible, a trace of the application server with the following trace string: com.ibm.ejs.j2c.*=all=enabled
J2CA0021E: An exception occurred while trying to get a Connection from the
Managed Connection : {0}. Explanation: This message indicates
that an exception was thrown by the Resource Adapter when attempting to call
getConnection. The exception text should help with deciphering the problem
encountered. User Response: If there are no user controlled indications,
the message may be due to an error in the internal J2C runtime processing
and a defect should be written. Include the activity.log with the defect. Include,
if possible, a trace of the application server with the following trace string: com.ibm.ejs.j2c.*=all=enabled
J2CA0022I: An exception occurred while trying to cleanup and release the Managed
Connection for a failed getConnection from the Managed Connection : {0}. This
second error was absorbed and the original error rethrown. Explanation:
This message indicates that a problem was encountered while attempting
to clean up after a failed getConnection. This message is informational
and should be combined with other related messages for proper problem determination.
User Response: Examine other related messages for Explanation and User
Responses.
J2CA0023E: A two phase XA operation, {0}, was
invoked. This resource adapter does not support two phase processing.
Explanation: This message indicates that an XA operation was attempted
to be invoked on a resource adapter that only supports local transactions. Under
normal conditions, this would indicate that a local transaction resource adapter
was accidentally included within the context of an XA transaction along with
other XA capable resources. User Response: Modify the business
logic to separate the resource usage into separate transactions.
J2CA0024E: Method {0}, within transaction ID {1}, caught {2} and threw a {3}.
Explanation: This message indicates a problem while processing
the given method. Since the interface defines specific exceptions that
can be thrown, the caught exception had to be mapped to the thrown exception. The
processing within the method did not complete successfully. User Response:
The business logic of the bean should properly catch the thrown exception
and process appropriate recovery logic.
J2CA0025E: An exception
occurred within method {0} which invoked a one phase {1} on a resource adapter:
{2}. Explanation: This message indicates a problem while processing
the given method. The processing within the method did not complete
successfully. The resource adapter may not support the given method.
User Response: Verify that the correct resource adapter is being used. Also,
verify that the resource adapter supports the local transaction interface. If
these check out and the given exception text does not provide enough details
to correct the situation, then a defect against the resource adapter may be
in order.
J2CA0026E: Method {0} caught {1} while trying
to register the XA Resource Adapter with the Synchronization Manager for the
current transaction, and threw a {2}. Explanation: This message
indicates a problem while processing the given method. Since the interface
defines specific exceptions that can be thrown, the caught exception had to
be mapped to the thrown exception. The processing within the method
did not complete successfully. User Response: The business logic
of the bean should properly catch the thrown exception and process appropriate
recovery logic.
J2CA0027E: An exception occurred while
invoking {0} on the XA Resource Adapter, within transaction ID {1}: {2}.
Explanation: This message indicates a problem while processing the given
method. The processing within the method did not complete successfully.
User Response: The business logic of the bean should properly catch the
thrown exception and process appropriate recovery logic..
J2CA0028E: An exception occurred while invoking {0} on the XA Resource Adapter:
{1}. Explanation: This message indicates a problem while processing
the given method. The processing within the method did not complete
successfully. User Response: The business logic of the bean should
properly catch the thrown exception and process appropriate recovery logic.
J2CA0029I: An exception occurred during the {0} processing on an XA Resource
Adapter while trying to remove the ConnectionEventLister: {1}. This error
was absorbed and processing continued. Explanation: This message
is for informational purposes. The exception occurred while cleaning
up the managed connection and should not affect normal operation. Processing
will continue. User Response: If this message occurs on a regular
basis, then a defect should be written against the J2C runtime. Include the
activity.log with the defect. Include, if possible, a trace of the application
server with the following trace string: com.ibm.ejs.j2c.*=all=enabled
J2CA0030E: Method {0} caught {1} while trying to enlist the XA Resource Adapter
with the Transaction Manager for the current transaction, and threw a {2}.
Explanation: This message indicates a problem while processing
the given method. Since the interface defines specific exceptions that
can be thrown, the caught exception had to be mapped to the thrown exception. The
processing within the method did not complete successfully. User Response:
The business logic of the bean should properly catch the thrown exception
and process appropriate recovery logic.
J2CA0031I: Method
{0} caught {1} while trying to unlist the XA Resource Adapter from the Transaction
Manager for the current transaction. This error was absorbed and processing
continued. Explanation: This message indicates a problem while
attempting to unlist the resource adapter from the transaction manager. Since
this processing is done during cleanup, the exception will be absorbed and
processing will continue. User Response: If this message occurs
on a regular basis, then a defect should be written against the J2C runtime.
Include the activity.log with the defect. Include, if possible, a trace
of the application server with the following trace string: com.ibm.ejs.j2c.*=all=enabled
J2CA0032I: An exception occurred while trying to {0} from the Pool Manager:
{1}. This error was absorbed and processing continued. Explanation:
This message indicates a problem while performing the given method on
the Pool Manager. Since this processing is performed during cleanup,
the exception will be absorbed and processing will continue. User Response:
If this message occurs on a regular basis, then a defect should be written
against the J2C runtime. Include the activity.log with the defect. Include,
if possible, a trace of the application server with the following trace string: com.ibm.ejs.j2c.*=all=enabled
J2CA0033E: An exception occurred while trying to obtain a Managed Connection
with method {0} from the Pool Manager: {1}. Explanation: This
message indicates a problem with reserving a managed connection from the pool
manager. There are many reasons why this operation may not have exceeded. Please
examine other related messages in the activity.log for more specific problems
to resolve. User Response: If this problem can not be resolved
by the user, then a defect should be written against the J2C runtime. Include
the activity.log with the defect. Include, if possible, a trace of the
application server with the following trace string: com.ibm.ejs.j2c.*=all=enabled.
key=ClientStyleProperties.MalFormedURLException
> JORB0010: Attempted to construct {0} from MalFormedURL. URL={1}.
Processing continues using the default property values. Explanation:
The com.ibm.CORBA.ClientStyleImageURL was not correctly formed.
User Response: Determine which program generated the incorrect URL and
correct the error. key=ClientStyleProperties.IOException >
JORB0011: An I/O error occurred while constructing {0} from the properties
URL. URL={1}. Processing continues using the default property values.
Explanation: An error occurred while reading the file identified by com.ibm.CORBA.ClientStyleImageURL.
User Response: Make sure that the file exists and is readable. key=InvalidValue.useDefault
> JORB0012: Property {0} has invalid value {1}. The default
value, {2}, is used. Explanation: The value specified for one
of the properties in ClientStyleProperties is invalid. User Response:
Find the invalid value and correct it. key=InvalidQOPCombination.useDefault
> JORB0013: An invalid QOP combination was specified. Processing
continues with the default values. The specified invalid combination is {0}.
The default combination is {1}. Explanation: An invalid combination
of Quality Of Protection attributes was specified. . User Response:
Find the invalid value and correct it. key=createKey.unknownType >
JORB0014: createKey received an unknown connection type and
returned a default key. The unknown type is {0}. The returned default key
is {1}. Explanation: com.ibm.CORBA.iiop.ConnectionTable.createKey
received an unknown connectionType. User Response: Contact IBM
Support. key=getConnectionKey.returnedFalse > JORB0015:
getConnectionKey returned a false value and threw a COMM_FAILURE exception.
Explanation: com.ibm.CORBA.iiop.ConnectionTable.get call
of ConnectionInterceptor getConnectionKey method returned a false value.
User Response: Contact IBM Support. key=getConnectionData.returnedNull
> JORB0016: getConnectionData returns a null pointer and throws
a COMM_FAILURE exception. Explanation: The ConnectionInterceptor
returned a ConnectionDataRef object which contains a null pointer to its ConnectionData
object. User Response: Contact IBM Support. key=ConnectionTable.unknownConnectionType
> JORB0017: There is an unknown connection type (value = {0})
and a COMM_FAILURE exception is thrown. Explanation: The
ConnectionInterceptor returned a ConnectionData object with an unknown
connection type. User Response: Contact IBM Support. key=KeyRingFileException.noSSLKeyRingFile
> JORB0018: Cannot find property com.ibm.CORBA.SSLKeyRingFile
in ClientStyleProperties. KeyRingFileException is thrown. Explanation:
TheClientStyleProperties did not include a property named com.ibm.CORBA.SSLKeyRingFile.
User Response: Determine why no value was specified and correct the problem.
JORB0019: "IIOPSSLConnection.coalesceCipherSpecs(...)" returns a null.
An INTERNAL exception is thrown. Suites enabled by the SLLSocket are {0}.
Suites required by ConnectionInterceptor are {1}. Explanation:
The SSLight socket does not support any of the CipherSpecs requested
by IIOPSSLConnection. . User Response: Verify that the correct
version of SSLight is used. key=IIOPSSLConnection.targetSupports >
JORB0020: The SSLServerConnectionData object that was passed
to createSSLServerSocket returns a value for getTargetSupportsQOP() that is
less than 1. Explanation: The ConnectionInterceptor.getServerConnectionData
returns an SSLConnectionData object with an invalid TargetSupports value.
User Response: Contact IBM Support. key=IIOPSSLConnection.targetRequires
> JORB0021: The SSLServerConnectionData object that is passed
to createSSLServerSocket returned a value from getTargetRequiresQOP() that
is less than 1. Explanation: The ConnectionInterceptor.getServerConnectionData
returned an SSLConnectionData object with an invalid TargetRequires value.
User Response: Contact IBM Support. key=IIOPSSLConnection.targetSupports2
> JORB0022: The SSLServerConnectionData object that is passed
to createSSLServerSocket contains a TargetSupportsQOP() value that is less
than its TargetRequiresQOP value. Explanation: The ConnectionInterceptor.getServerConnectionData
returns an SSLConnectionData object where the TargetSupportsQOP value is less
than its TargetRequiresQOP value. User Response: Contact IBM Support. key=IIOPSSLConnection.Class.forName
> JORB0023: {0} throws {1} which is rethrown as an INTERNAL
exception. The KeyRing class name from the ConnectionInterceptor is {2}.
Explanation: Cannot instantiate the SSLightKeyRing class.
User Response: Verify that the class appears in the CLASSPATH. key=IIOPSSLConnection.setEnabledCipherSuites
> JORB0024: {0} throws {1}. The CipherSuites being set are
{2} Explanation: SSLContext.setEnabledCipherSuites fails
and throws an SSLException. User Response: Verify that the correct
version of SSlight is used. key=IIOPSSLConnection.exception >
JORB0025: "{0}" throws {1}. IIOPSSLConnection cannot create a new SSLSocket.
Explanation: User Response: Verify that the
correct version of SSLight is used. key=SSLContext.setTimeout >
JORB0026: "SSLContext.setTimeout(..)" throws {0} when setting the {1} timeout.
The value being set is {2}. Processing continues with default value {3}.
Explanation: User Response: Verify that the
correct version of SSLight is used. key=IIOPSSLConnection.rethrownException
> JORB0027: Method {0} throws {1} which is rethrown as an
INTERNAL exception. Explanation: None. User Response:
Contact IBM Support. key=IIOPSSLConnection.client.importKeyRings.password
> JORB0028: {0} throws {1} which is rethrown as an INTERNAL
exception. The password for the client SSL KeyRing is invalid.
Explanation: None. User Response: Correct the SSL client
KeyRing password and try again. key=IIOPSSLConnection.server.importKeyRings.password
> JORB0029: {0} throws {1} which is rethrown as an INTERNAL
exception. The password for the server SSL KeyRing is invalid.
Explanation: None. User Response: Correct the SSL client
KeyRing password and try again. key=dummySSL.invalidCall >
JORB0030: Attempted to construct the dummy version of {0}, which should
never be constructed. This situation is probably due to a configuration
error. Attempts were made to use SSL on a client that has not installed
an SSL library (for example, somojse.zip). Explanation: A
dummy class which is meant to be used at compile time, was called at run time.
User Response: Verify that there is an SSLight zip file in the CLASSPATH key=clientDelegate.wrongID
> -->JORB0031: The server returns an
InterfaceDef object of the wrong type. Explanation: On a
call to _get_interface_def, the object returned by the server is not an
InterfaceDef object. An Unknown exception is thrown. User Response:
Determine why the server did not return an InterfaceDef object and retry
the call to _get_interface_def. key=clientDelegate.no_InterfaceDefStub
> JORB0032: org.omg.CORBA._InterfaceDefStub class is missing
or not available. Explanation: None. User Response:
Compile ir.idl to generate _InterfaceDefStub and then compile _InterfaceDefStub.
You can also contact IBM Support. key=replyMessage.badCompletion >
JORB0034: Invalid completion status: {0} Explanation:
A SystemException was thrown with a completion status other than Yes,
No, or Maybe (0, 1, 2).. User Response: Determine why the server
threw a SystemException with an invalid completion status and retry. key=iiopTunnelServlet.parsingHost
> JORB0035: service(): An exception occurred while parsing the
host name. Query string={0}. Explanation: The IIOPTunnelServlet
program cannot parse the host name received from the client. The host name
was taken from the IOR of the object that the server is servicing.
User Response: Ensure that the host name is correct for the server. key=iiopTunnelServlet.parsingPort
> JORB0036: service(): An exception occurred while parsing port
number. Query string={0}. Explanation: The IIOPTunnelServlet
program cannot parse the port number received from the client. The port
number was taken from the IOR of the object that the server is servicing.. <
User Response:Ensure that the port number is correct for the server.
key=iiopTunnelServlet.IOException > JORB0037: service(): IOException
occurred while setting up client and server sockets. Exception={0}.
Explanation: An IOException occurred while attempting to connect to
the server from the IIOPTunnelServlet program. User Response: Make
sure the server is active and is accepting requests. key=iiopTunnelServlet.Exception
> JORB0038: {0}: Exception ={1} Explanation: An
exception occurred while attempting to connect to the server from the IIOPTunnelServlet
program. User Response: Make sure the server is active and is accepting
requests. key=iiopTunnelServlet.unsupported > JORB0039:
service(): HTTP method type "{0}" is not supported; only "POST" method type
is supported. Explanation:The IIOPTunnelServer program only
supports the HTTP POST method. < User Response: Make sure
your Web server and servlet engine support the POST method. key=iiopTunnelServlet.servletInfo
> JORB0040: The servlet used to tunnel IIOP packets through
an HTTP Server. Explanation: This is the return value for the
standard servlet method getServletInfo. User Response: No action
is required. key=Redirector.RequestIOException > JORB0041:
handleRequest(): IOException occurred while redirecting the client request
packet to the server. Exception={0}. Explanation: None.
User Response: Make sure the server is active and is accepting requests. key=Redirector.ReplyIOException
> JORB0042: handleReply(): IOException occurred while redirecting
the server reply packet back to the client. Exception={0}. Explanation:
None. User Response: Make sure the client is active and is
accepting replies. key=Redirector.Throwable > JORB0043:
A throwable exception occurred while redirecting the IIOP packets. Exception={0}.
Explanation: . User Response: Make sure the
server and client are active. key=GIOPImpl.locateError >
JORB0044: com.ibm.CORBA.iiop.locate(IOR ior) is called. This situation
should never occur. Explanation: In the IBM ORB, com.ibm.CORBA.iiop.ClientGIOP.locate(IOR
ior, org.omg.CORBA.Object targetObjectProxy) should always be used instead
of com.ibm.rmi.ClientGIOP.locate(IOR ior). Overriding the latter and throwing
an exception implies that there is a coding error in the IBM Java ORB.
User Response: Contact IBM Support. key=GIOPImpl.endPointError
> JORB0045: There is an invalid attempt to use getEndPoint(type,port,addr)
to establish an SSL connection. Explanation: You cannot set
up non-CLEAR_TEXT endpoints this way. User Response: Contact IBM
Support. key=GIOPImpl.badServerConnectionType > JORB0046:
ConnectionInterceptor.getServerConnectionData returns an SSLConnectionData
object with invalid ConnectionType {0}. An INTERNAL exception is thrown.
Explanation: This problem can be due to an IBM Programming
error or a system management configuration error. User Response:
Verify the system management configuration. key=GIOPImpl.badServerSocketQueueDepthValue
> JORB0047: The value {1} specified for the property {0} is
not valid. The default queue depth of {2} will be used Explanation:
The value specified for the ServerSocket Queue depth is not a valid
value. User Response: Check the setting of the ServerSocket
queue depth property and ensure the value is valid (i.e. greater than the
default) key=GIOPImpl.badServerSocketQueueDepthInteger >
JORB0048: The value {1} specified for the property {0} is not a valid integer.
The default queue depth of {2} will be used Explanation: The
value specified for the ServerSocket Queue depth is not a valid value.
User Response: Check the setting of the ServerSocket queue depth property
and ensure the value is valid (i.e. greater than the default) key=ConnectionTable.beforegetConnectionkey
> JORB0049: The parameters passed to ConnectionInterceptor.getConnectionKey
are: host={0}, port={1}, SSLTaggedComponent={2}, method_name={3}, attempts={4},
ConnectionData={5}, targetObjectProxy={6} Explanation: This
message provides configuration information for problem determination and
does not indicate an error. User Response: For information only.
No action is required. key=ConnectionTable.aftergetConnectionKey >
JORB0050: The ConnectionData object returned from getConnectionKey is: {0}
Explanation :These are parameters returned from ConnectionInterceptor.getConnectionKey.
This message provides configuration information for problem determination
and does not indicate an error. User Response :For information
only. No action is required. key=GIOPImpl.aftergetServerConnectionData
> JORB0051: The array of ConnectionData objects returned from
getServerConnectionData is: {0} Explanation: These are parameters
returned from ConnectionInterceptor.getServerconnectionKey. This message
provides configuration information for problem determination and does not
indicate an error. User Response: None. key=GIOPImpl.ServerConnectionDataAfterPortsAreSet
> JORB0052: The array of ConnectionData objects after the listener
ports have been opened is: {0} Explanation: This message
provides configuration information for problem determination and does not
indicate an error.. User Response:For information only. No action
is required. key=ConnectionTable.beforeNotifyBrokenConnection >
JORB0053: The ConnectionData object that is passed to ConnectionInterceptor.notifyBrokenConnection
is: {0} Explanation: This message provides configuration
information for problem determination and does not indicate an error.
User Response: For information only. No action is required. key=GIOPImpl.createListenerException
> JORB0054: The server threw an exception when creating a server
listener socket. The exception is {0}. The ServerConnectionData object that
describes the server port is {1}. Explanation: User
Response: Verify that the port number is valid. key=ServerDelegate.dispatchUnknownException
> JORB0055: The ServerDelegate dispatch method caught an exception
while invoking the operation {0}. The exception is: {1} Explanation:
This message indicates the customer code that the ORB invoked has thrown
an exception. It indicates a problem in the customer's server code (i.e.
the server implementation). The actual exception thrown by the server code
and caught by the ORB is also logged. User Response: The customer
server code should be investigated to determine why the exception was thrown.
key=ServerDelegate.dispatchThrowable > JORB0056: The ServerDelegate
dispatch method caught an exception while invoking the operation {0}. The
exception is: {1} Explanation: This message indicates the the
ORB caught an exception when trying to invoke the server code. It may indicates
a problem in the customer's server code (i.e. the server implementation),
or n some configuration. The actual exception thrown by the server code and
caught by the ORB should is also logged. User Response: The configuration
and customer server code should be investigated as to why the exception was
thrown. key=ServerDelegate._is_a.RepIDs > JORB0057: The
_is_a method was called on a server object with the following RepIDs: {0}.
Explanation: This message provides configuration information
for problem determination and does not indicate an error. User
Response: For information only. No action is required. key=ListnerThread.acceptSocket
> JORB0058: A ListenerThread accepted the following socket:
{0}. Explanation: This message provides configuration information
for problem determination and does not indicate an error.. User
Response: For information only. No action is required. key=ORB.noObjectResolver
> JORB0062: There is no object resolver. Explanation:
Before ORB.register can be called, an ObjectResolver must exist.
User Response: Contact your system support staff to determine why an ObjectResolver
does not exist. key=ServerDelegate.unknownAppException >
JORB0063: Unknown application exception is thrown on the server: {0}.
Explanation: A non-CORBA exception was thrown on the server. User
Response: If the exception is being thrown in the application code, correct
the code and retry. Otherwise, contact IBM Support. key=StandardSyntaxModelImpl.UnMatchedQuote
> JORB0064: There is an unmatched quote exception, {0}.
Explanation: An unmatched quote error occurred while parsing the string
of a naming context path into a CosNaming NameComponent array.
User Response: Make sure the string being passed to the method _StandardSyntaxModelImpl.name_to_string()
has the correct syntax. key=StandardSyntaxModelImpl.IllegalStringSyntax
> JORB0065: There is an IllegalStringSyntax exception, {0}.
Explanation: A syntax error occurred while parsing the string
form of a naming context path into a CosNaming NameComponent array.
User Response: Make sure the string being passed to the method _StandardSyntaxModelImpl.name_to_string()
has the correct syntax. key=StandardSyntaxModelImpl.Exception >
JORB0066: Exception={0} Explanation: An exception
occurred while parsing the string form of a naming context path into a CosNaming
NameComponent array. User Response:Make sure the string being
passed to the method _StandardSyntaxModelImpl.name_to_string() has the
correct syntax. key=ORB.NullgetThreadPool > JORB0067:
There is a null ThreadPool instance in the ORB. Explanation: Called
ORB.getThreadPool, but cannot find the ThreadPool. The ThreadPool has never
been initialized. Because ThreadPool is a plugin, there should be a default
ThreadPool. User Response: Contact IBM Support key=ORB.NullsetThreadPool
> JORB0068: There is a null input parameter in the ORB.setThreadPool()
invocation. Explanation: The ThreadPool must always be set
to a valid instance. User Response: Correct the programming error. key=ThreadPool.IllegalState
> JORB0069: Cannot call ThreadPool.startWorkerThread() after
a ThreadPool.cleanup() request. Explanation: The ORB ThreadPool
was told to stop via the ThreadPool.cleanup() method, and then it was told
to do work via the ThreadPool.startWorkerThread() method. This is an illegal
sequence. User Response: Contact IBM Support. key=ExtendedServerDelegate.UnknownApp
> JORB0070: An unknown application exception was thrown on the
server: {0} Explanation: A non-CORBA exception was thrown on
the server. The name of the exception is given in this string.
User Response: If the exception is being thrown in the application code,
correct the code and retry. If the exception is not being thrown in application
code, contact IBM Support. key=BootstrapServer.notReadable >
JORB0071: BootstrapServer: Cannot read file "{0}". Explanation:
The BootstrapServer cannot read the Initial Services Properties file.
User Response: Ensure that read authority is granted to the administrator
who is starting the BootstrapServer. key=BootstrapServer.settingPort >
JORB0072: BootstrapServer: Setting the port for initial object
references to: {0}. Explanation: The BootstrapServer is listening
on the indicated port. User Response: For information only. No
action is required. key=BootstrapServer.readingServices >
JORB0073: BootstrapServer: Reading initial services from "{0}".
Explanation: User Response: For information only. No action
is required. key=BootstrapServer.couldntWrite > JORB0074:
BootstrapServer: Cannot open "{0}" for writing. Cannot find the file.
Explanation: None. User Response: Ensure that the file exists. key=BootstrapServer.couldntRead
> JORB0075: BootstrapServer: Cannot open "{0}" for reading.
Cannot find the file. Explanation: None. User Response:
Ensure that the file exists. key=BootstrapServer.savingException >
JORB0076: BootstrapServer: Caught an exception while saving
properties to file "{0}": {1}. Explanation: User
Response:Ensure that the file exists and that the administrator has
the correct authority. key=BootstrapServer.loadingException >
JORB0077: BootstrapServer: Caught an exception while loading properties to
file "{0}": {1}. Explanation: None. User Response: Ensure
that the file exists and that the administrator has the correct authority. key=LocationServiceClient.portNotSetException
> JORB0078: Persistent IOR port number is not provided. Object
references will be transient. Explanation: The com.ibm.CORBA.LSDPort
property was not set when the ORB was initialized. This situation results
in transient object references. User Response: If persistent
object references are required, when initializing the ORB, set the com.ibm.CORBA.LSDPort
property to a value that will remain persistent on that host machine. key=LocationServiceClient.UUIDNotSetException
> JORB0079: Unique server ID (UUID) is not set.
Explanation: The com.ibm.CORBA.ServerUUID property was not set when the
ORB was initialized. The Location Service Daemon requires this property to
uniquely identify a server. User Response: When initializing
the ORB, set the com.ibm.CORBA.ServerUUID property to the UUID (Universally
Unique Identifier) assigned to the server. This value is generally assigned
by the system administrator. key=LocationServiceDaemon.waitForRequests
> JORB0080: Location Service Daemon is listening with server
ID = {0} on port = {1} ... Explanation: The Location Service
Daemon is ready to accept requests on the indicated port. User Response:
For information only. No action is required. key=LocationServiceDaemon.failedOnWait
> JORB0081: Location Service Daemon failed on waiting for requests.
Explanation: The Location Service Daemon is not ready to
accept requests and cannot enter into a wait state. User Response:
Restart the Location Service Daemon. key=LocationServiceDaemon.invalidPort
> JORB0082: The port number is invalid. Specify a different
port number. Explanation: User Response: Specify
a valid port number. key=LocationServiceDaemon.exception >
JORB0083: ERROR: {0} Explanation: The Location Service Daemon
received an unexpected exception. User Response: Examine the exception
for possible user error. key=LocationServiceDaemon.portInUse >
JORB0084: Port {0} is in use. Specify a different port number.
Explanation: User Response: Specify a different port number,
or end the process using the port and then restart the Location Service
Daemon. key=LocationServant.SSLEnabled > JORB0085: Location
Service Daemon is SSL enabled. Explanation: The Location Service
Daemon will be listening on an SSL enabled port. User Response: For
information only. No action is required. key=LocationServant.FirewallPlugin
> JORB0086: Location Service Daemon has registered a firewall
plugin. Explanation: The Location Service Daemon will be
interacting with a firewall. The Location Service Daemon will authorize
the server port when the server registers with the Location Service Daemon.
User Response: For information only. No action is required. key=LocationServant.RegisteredServer
> JORB0087: Server registered: ServerUUID={0} HostName={1} Port={2}
Explanation: The indicated server has been registered with
the Location Service Daemon. User Response: For information only.
No action is required. key=LocationServant.UnregisteredServer >
JORB0088: Server unregistered: ServerUUID={0} HostName={1} Port={2}
Explanation: The indicated server has been unregistered with the Location
Service Daemon. User Response: For information only. No action
is required. key=ServerActivator.StartServers > JORB0089:
Location Service Daemon will start the registered servers.
Explanation: A server is considered registered if there is an entry for
the server in the IBMLSDServerRegistry.properties file. The Location Service
Daemon has been configured to start a registered server if a request comes
in for that server and the server is not registered with the Location Service
Daemon as an active server. User Response: For information
only. No action is required. key=ServerActivator.SSLEnabled >
JORB0090: Registered servers started by the Location Service Daemon will need
to be SSL enabled. Explanation: The Location Service has
been configured to listen on an SSL enabled port. Servers that are started
by the Location Service Daemon are notified that they need to listen on
an SSL enabled port. User Response: For information only. No
action is required. key=ServerActivator.ServerTimeOut >
JORB0091: Registered Servers will have {0} milliseconds to start.
Explanation: The Location Service Daemon has been configured to start
servers. When a server is started, the Location Service Daemon uses the
indicated timeout value when waiting for a server to start.
User Response:For information only. No action is required. key=ServerActivator.StoreServerList
> JORB0092: Location Service Daemon will persistently store
the list of active servers to {0}. Explanation: The Location
Service Daemon has been configured to persistently store the list of active
registered servers. User Response: For information only. No
action is required. key=ServerActivator.RestoreServerList >
JORB0093: Location Service Daemon is initializing the list of active servers
from {0}. Explanation: The Location Service Daemon has been
configured to persistently store the list of active registered servers.
Upon startup, the Location Service Daemon uses the stored file to restore
the list of active servers. User Response: For information only.
No action is required. key=ServerActivator.StartServer >
JORB0094: Location Service Daemon is starting server {0}. Explanation:
A server is considered registered if there is an entry for the server
in the IBMLSDServerRegistry.properties file. The Location Service Daemon
has been configured to start a registered server if a request comes in
for that server and the server is not registered with the Location Service
Daemon as an active server. User Response: For information
only. No action is required. key=ServerActivator.StoringActiveServerList
> JORB0095: Location Service Daemon is storing the active server
list to {0}. Explanation: None. User Response: For
information only. No action is required. key=IIOPConnection.CouldNotInstantiateReaderManager
> JORB0096: Could not instantiate {0}, caught "{1}". Using com.ibm.CORBA.iiop.ThreadPerConnectionManager
instead Explanation: This message provides configuration
information for problem determination and does not indicate an error.
User Response: For information only. No action is required. key=ThreadPerConnectionReaderManager.CouldNotInstantiateReader
> JORB0097: Could not instantiate a StandardReaderThread
Explanation: This message provides configuration information for problem
determination and does not indicate an error. User Response:
For information only. No action is required. key=JNIReaderManager.invalidNumberOfReaders
> JORB0098: The property {0} has a value of {1}. This is not
a valid value. The number of JNIReaderThreads is set to the default value
of {2} Explanation: This message provides configuration
information for problem determination and does not indicate an error.
User Response: For information only. No action is required. key=JNIReaderThread.getSSLSocketFD0Resuts
> JORB0099: Native method getSSLSockedFD0 was called. The Socket
passed in was {0}, and the FileDescriptor returned was {1}
Explanation: This message provides configuration information for problem
determination and does not indicate an error. User Response:
For information only. No action is required. key=JNIReaderThread.showfdConnectionMap
> JORB0100: Before calling the native method addConnection0,
the contents of the fdConnectionMap are {0}, and the fileDescriptor for the
connection being added is {1} Explanation: This message
provides configuration information for problem determination and does not
indicate an error.. User Response: For information only. No
action is required. key=JNIReaderThread.fdConnectionMap.getFailed >
JORB0101: fdConnectionMap.get( theFileDescriptor ) returned null. theFileDescriptor={0},
the map is {1} Explanation: This message provides configuration
information for problem determination and does not indicate an error.
User Response: For information only. No action is required. key=JNIReaderThread.fdConnectionMap.get
> JORB0102: after calling fdConnectionMap.get() with Filedescriptor
{0} the returned IIOPConnection was {1}. The fdConnectionMap contains{2}
Explanation: This message provides configuration information for problem
determination and does not indicate an error. User Response:
For information only. No action is required. key=JNIReaderManager.noNonFullNativeReaders
> JORB0103: None of the native code reader threads has room
in its queue for a new Socket to watch, a COMM_FAILURE was thrown
Explanation: None of the native code reader threads has room in its
queue for a new Socket to watch. User Response: Add more
ReaderThreads, via ORB property com.ibm.CORBA.numJNIReaders key=Profile.getHostIPAddress
> JORB0104: In Profile.getIPAddress(), InetAddress.getByName(
{0} ) threw an UnknownHostException Explanation: A Profile
has a host name that cannot be found by the domain name server User
Response: Check the host name and the name server key=IIOPSSLConnectionClient.coalesceCipherSpecs
> JORB0105: "IIOPSSLConnectionClient.coalesceCipherSpecs(...)"
returns a null. An INTERNAL exception is thrown. Suites enabled by the JSSESocket
are {0}. Suites required by ConnectionInterceptor are {1}.
Explanation: The JSSE socket does not support any of the CipherSpecs
requested by IIOPSSLConnection. User Response: The JSSE socket
does not support any of the CipherSpecs requested by IIOPSSLConnection.
key=IIOPSSLConnectionClient.createSSLSocket > JORB0106: "IIOPSSLConnectionClient.createSSLSocket(...)"
returns a null. An INTERNAL exception is thrown. Additional information
{0}. Explanation: This message results from a JSSE client
socket creation error. User Response: Message contains more
details.
JSAS0010E: Null reference to Vault. The problem may be an out of memory error.
Restart the server machine and try again. If the problem persists, contact
support for assistance. Explanation: This message indicates
that an error occurred while creating a vault instance during initialization
of the server. User Response: The problem may be an out of memory
error. Restart the server machine and try again. If the problem persists,
contact support for assistance.
JSAS0020E: Null reference
to LoginHelper. The problem may be an out of memory error. Restart the server
machine and try again. If the problem persists, contact support for assistance.
Explanation: This message indicates an internal error occurred
while trying to create an instance of LoginHelperImpl. User Response:
The problem may be an out of memory error. Restart the server machine
and try again. If the problem persists, contact support for assistance.
JSAS0025E: Null reference to ORB. The problem may be an out of memory error.
Restart the server machine and try again. If the problem persists, contact
support for assistance. Explanation: This message indicates
that a reference to the ORB was null. User Response: The
problem may be an out of memory error. Restart the server machine and try
again. If the problem persists, contact support for assistance.
JSAS0026E: Exception connecting object to the ORB. Check the sas.server.props
file to ensure that the SSLKeyRing and SSLKeyRingPassword are set properly.
If the problem persists, contact support for assistance.
Explanation: An internal exception occurred. In all likelihood your server
key ring is invalid, does not contain a server certificate, or cannot be
found. User Response: Check the sas.server.props file to
ensure that the SSLKeyRing and SSLKeyRingPassword are set properly. If the
problem persists, contact support for assistance.
JSAS0030E:
Unable to get Current. Check to ensure the correct Java class files are in
the program classpath. Make sure you are not using the wrong version of UJC.JAR.
If you still have problems after reviewing your setup, contact support for
assistance. Explanation: This message indicates an internal
error occurred while trying to access Current via resolve_initial_references.
User Response: Check to ensure the correct Java class files are in
the program classpath. Make sure you are not using the wrong version of UJC.JAR.
If you still have problems after reviewing your setup, contact support for
assistance.
JSAS0040E: Unable to initialize security context.
Check to ensure the userid and password is valid. Restart the client and retry
the operation. If the problem persists, contact support for assistance.
Explanation: The outcome of init_security_context is failure. Any
reason for a secure association failure with the target server could cause
this error. There are times when this is benign, such as for method invocations
that do not require security. User Response: Check to ensure
the userid and password is valid. Restart the client and retry the operation.
If the problem persists, contact support for assistance.
JSAS0050E: Attempt to establish secure connection failed. Explanation:
None. User Response: None.
JSAS0051E: Invalid
authentication target. Verify that the com.ibm.CORBA.authenticationTarget
property in the sas.server.props or sas.client.props is set to a valid type.
Explanation: The authentication target is not of the type
BasicAuth, LocalOS or LTPA. Sometimes only LocalOS or LTPA are valid authentication
targets for certain methods. User Response: Verify that the
com.ibm.CORBA.authenticationTarget property in the sas.server.props or sas.client.props
is set to a valid type.
JSAS0052E: Invalid credential token.
Retry the operation after a few minutes. If using request_login for Domino,
ensure that Domino/WebSphere SSO is set up correctly. If the problem persists,
contact support for assistance. Explanation: The credential
token is null, expired, or has been tampered with. Since the token is digitally
signed, any modification of the bytes in the token will not verify. Typically
this error is due to a null token. User Response: Retry the
operation after a few minutes. If using request_login for Domino, ensure
that Domino/WebSphere SSO is set up correctly. If the problem persists,
contact support for assistance.
JSAS0053E: Unable to validate
credential token. Retry the operation after a few minutes. If using request_login
for Domino, ensure that Domino/WebSphere SSO is set up correctly. If the
problem persists, contact support for assistance. Explanation:
The credential token is null, expired, or has been tampered with. Since
the token is digitally signed, any modification of the bytes in the token
will not verify. Typically this error is due to a null token. User
Response: Retry the operation after a few minutes. If using request_login
for Domino, ensure that Domino/WebSphere SSO is set up correctly. If the
problem persists, contact support for assistance.
JSAS0054E:
Unable to set invocation credentials. Retry the operation. Ensure the program
is creating the credential properly before setting it as the invocation credential.
You may need to restart the client or server which has the invalid credential.
If the problem persists, contact support for assistance. Explanation:
The credential is null, or the credential is not a subtype of org.omg.SecurityLevel2.Credentials,
or the credential has been marked invalid during a failed login attempt,
or while the security server was unavailable. User Response:
Retry the operation. Ensure the program is creating the credential properly
before setting it as the invocation credential. You may need to restart the
client or server which has the invalid credential. If the problem persists,
contact support for assistance.
JSAS0060E: Unable to build
security context. Often problems with client and server configuration is
to blame for these errors. Frequently these problems relate to SSL connections
not being created. This situation could result from invalid settings in
the sas.client.props or the sas.server.props. Maybe the UJC.JAR is not
specified in the classpath or is not the same version as the server. The
JDK you are using must also have the JSSE extension classes in /java/jre/lib/ext
directory. The java.security file must include the IBMJCE provider. If the
problem persists, contact support for assistance. Explanation:
This message indicates that the building of the security context failed.
Typical reasons for this failure are: cannot find the session in the session
table, a TCP/IP connection is made instead of an SSL connection, or a Java
runtime exception occurred. User Response: Many times problems
with the client and server configuration are to blame for these errors.
Frequently these problems relate to SSL connections not being created.
This situation could result from invalid settings in the sas.client.props
or the sas.server.props. Maybe the UJC.JAR is not specified in the classpath
or is not the same version as the server. The JDK you are using must also
have the JSSE extension classes in /Java/jre/lib/ext directory. The java.security
file must include the IBMJCE provider. If the problem persists, contact support
for assistance.
JSAS0070E: Unable to complete secure association
at the client. Retry the client program after a few minutes. If the problem
still persists, contact support for assistance. Explanation:
An attempt to communicate with the server failed. The server may be
down, or the host and port are incorrect. User Response: Retry
the client program after a few minutes. If the problem still persists,
contact support for assistance.
JSAS0071E: NO_PERMISSION
caught, unable to complete secure association at the client. Retry the client
program after a few minutes wait. Ensure that the client program is using
the correct version of UJC.JAR in the classpath. If the problem still persists,
contact support for assistance. Explanation: An attempt
to establish a secure association with the server failed with a NO_PERMISSION.
User Response: Retry the client program after a few minutes wait.
Ensure that the client program is using the correct version of UJC.JAR in
the classpath. If the problem still persists, contact support for assistance.
JSAS0080E: Unable to reclaim message. Message was out-of-sequence or not
recoverable. Retry the operation after a few minutes. If this problem persists,
contact support for assistance. Explanation: This error
indicates the message was corrupted either during packaging, or while sending
across the wire. User Response: Retry the operation after a
few minutes. If this problem persists, contact support for assistance.
JSAS0090E: Unable to protect message. Explanation: None.
User Response: None.
JSAS0100E: Null target security
name. Verify that the principalName specified in the sas.server.props of the
server is valid. If the problem persists, contact support for assistance.
Explanation: The target security retrieved from a security
tagged component in the IOR is null. User Response: Verify that
the principalName specified in the sas.server.props of the server is valid.
If the problem persists, contact support for assistance.
JSAS0110E: Client credentials were not the correct type. Ensure that the client
program is correctly following the CORBA programming model. Also, verify that
the correct version of UJC.JAR is in the client classpath.
Explanation: This message indicates that the credentials object being
passed are either not SAS credentials, or no type was specified.
User Response: Ensure that the client program is correctly following
the CORBA programming model. Also, verify that the correct version of UJC.JAR
is in the client classpath.
JSAS0120E: Unable to create
SecurityContext object. Try to review the client security configuration file
(sas.client.props). If recent changes have been made you may want to undo
these changes. If you do not see any problems with the configuration and you
still get this error, contact support for assistance. Explanation:
A problem occurred while obtaining the security context object while
adding a new security session. This situation typically occurs while the
client is trying to log in. User Response: Review the client
security configuration file (sas.client.props). If recent changes have
been made, you may want to undo these changes. If you do not see any problems
with the configuration and you still get this error, contact support for
assistance.
JSAS0130E: Client credentials were not valid.
Restart the client so that it logs in with new credentials. Once client credentials
are marked invalid, they must be thrown away and news ones created.
Explanation: This message indicates that the client credentials were
marked invalid at some point. Some reasons for this invalid marking are:
expiration of a credential token, invalid userid and password, unavailable
security server to verify the user information. User Response:
Restart the client so that it logs in with new credentials. Once client
credentials are marked invalid, they must be thrown away and news ones created.
JSAS0140E: Unable to delete credentials from default credentials list.
Explanation: None. User Response: None.
JSAS0150E: Unable to find session in session table. Retry the operation.
If the error repeats, restart the client program. Check the client properties
to ensure the login information is correct. After restarting the client
and server programs, if you still are unable to eliminate the error, contact
support for assistance. Explanation: This error indicates
that the session key used to lookup the session in the session table has
not been found in the session table. This situation is typically a side
effect of another problem, such as an invalid credential or an unavailable
security service. User Response: Retry the operation. If the
error repeats, restart the client program. Check the client properties
to ensure the login information is correct. If after restarting the client
and server programs, you still are unable to eliminate the error, contact
support for assistance.
JSAS0160E: Null session entry in
session table. Check to see if a server process has terminated just prior
to receiving these errors. If a process has terminated, restart the process
and retry the operation. Verify that the client userid and password are
valid. If the login fails, the session is deleted on the client side and
the credentials are marked invalid. If a retry occurs, you will likely
see this error. Restart the client program after verifying the login information.
If the errors persist, contact support for assistance. Explanation:
An attempt to access a security session from the session tables on either
the client or the server has failed. This error is typically a side effect
of another problem. The session probably has already been deleted or has never
been added. User Response: Check to see if a server process
has terminated just prior to receiving these errors. If a process has terminated,
restart the process and retry the operation. Verify that the client userid
and password are valid. If the login fails, the session is deleted on the
client side and the credentials are marked invalid. If a retry occurs,
you will likely see this error. Restart the client program after verifying
the login information. If the errors persist, contact support for assistance.
JSAS0170E: Null session handle in session table. Check to see if a server
process has terminated just prior to receiving these errors. If a process
has terminated, restart the process and retry the operation. Verify that
the client userid and password are valid. If the login fails, the session
is deleted on the client side and the credentials are marked invalid. If
a retry occurs, you will likely see this error. Restart the client program
after verifying the login information. If the errors persist, contact support
for assistance. Explanation: An attempt to access a security
session from the session tables on either the client or the server has failed.
This error is typically a side effect of another problem. The session probably
has already been deleted or has never been added. User Response:
Check to see if a server process has terminated just prior to receiving
these errors. If a process has terminated, restart the process and retry
the operation. Verify that the client userid and password are valid. If
the login fails, the session is deleted on the client side and the credentials
are marked invalid. If a retry occurs, you will likely see this error.
Restart the client program after verifying the login information. If the
errors persist, contact support for assistance.
JSAS0171E:
No class definition found error for Class.forName.newInstance(). Verify that
IBMWEBAS.JAR is in the classpath on the server. Restart the server and retry
the operation. If the problem persists, contact support for assistance.
Explanation: Could not find the class com.ibm.LocalOSImpl.LocalOSServerImpl.
User Response: Verify that IBMWEBAS.JAR is in the classpath on the server.
Restart the server and retry the operation. If the problem persists, contact
support for assistance.
JSAS0172E: Java language error
for Class.forName.newInstance(). Verify that IBMWEBAS.JAR is in the classpath
on the server. Restart the server and retry the operation. If the problem
persists, contact support for assistance. Explanation: Could
not find the class com.ibm.LocalOSImpl.LocalOSServerImpl. User Response:
Verify that IBMWEBAS.JAR is in the classpath on the server. Restart the
server and retry the operation. If the problem persists, contact support for
assistance.
JSAS0173E: Java language exception for Class.forName.newInstance().
Verify that IBMWEBAS.JAR is in the classpath on the server. Restart the server
and retry the operation. If the problem persists, contact support for assistance.
Explanation: Could not find the class com.ibm.LocalOSImpl.LocalOSServerImpl.
User Response: Verify that IBMWEBAS.JAR is in the classpath on the server.
Restart the server and retry the operation. If the problem persists, contact
support for assistance.
JSAS0174E: Illegal access exception
for Class.forName.newInstance(). Verify that IBMWEBAS.JAR is in the classpath
on the server. Restart the server and retry the operation. If the problem
persists, contact support for assistance. Explanation: Could
not find the class com.ibm.LocalOSImpl.LocalOSServerImpl. User Response:
Verify that IBMWEBAS.JAR is in the classpath on the server. Restart the
server and retry the operation. If the problem persists, contact support for
assistance.
JSAS0175E: Instantiation exception for Class.forName.newInstance().
Verify that IBMWEBAS.JAR is in the classpath on the server. Restart the server
and retry the operation. If the problem persists, contact support for assistance.
Explanation: Could not find the class com.ibm.LocalOSImpl.LocalOSServerImpl.
User Response: Verify that IBMWEBAS.JAR is in the classpath on the server.
Restart the server and retry the operation. If the problem persists, contact
support for assistance.
JSAS0176E: Class not found exception
for Class.forName.newInstance(). Verify that IBMWEBAS.JAR is in the classpath
on the server. Restart the server and retry the operation. If the problem
persists, contact support for assistance. Explanation: Could
not find the class com.ibm.LocalOSImpl.LocalOSServerImpl. User Response:
Verify that IBMWEBAS.JAR is in the classpath on the server. Restart the
server and retry the operation. If the problem persists, contact support for
assistance.
JSAS0180E: Unable to get PrincipalAuthenticator
from Current. Check sas.server.props and sas.client.props to ensure that
the authenticationTarget is set properly. If the problem persists, contact
support for assistance. Explanation: The problem is typically
related to the configuration. User Response: Check sas.server.props
and sas.client.props to ensure that the authenticationTarget is set properly.
If the problem persists, contact support for assistance.
JSAS0185E: Validation of BasicAuth Token not supported. Check the client
code to ensure it is not calling validate incorrectly. Resubmit the request
after waiting a few minutes. If the problem persists, contact support for
assistance. Explanation: Trying to validate a BasicAuth
token which consists of a userid and password. This token should be authenticated,
not validated. User Response: Check the client code to ensure
it is not calling validate incorrectly. Resubmit the request after waiting
a few minutes. If the problem persists, contact support for assistance.
JSAS0186E: Authentication with BasicAuth Token not supported. Check the
client code to ensure it is not calling the wrong principal authenticator.
Resubmit the request after waiting a few minutes. If the problem persists,
contact support for assistance. Explanation: Trying to authenticate
a BasicAuth token which consists of a userid and password in either the
LTPA or LocalOS PrincipalAuthenticator. User Response: Check
the client code to ensure it is not calling the wrong principal authenticator.
Resubmit the request after waiting a few minutes. If the problem persists,
contact support for assistance.
JSAS0190E: Invalid or null
client security name, unable to authenticate. Verify the information used
to login. Retry the operation with a valid userid. If a properties login is
performed, check the properties file to ensure a userid has been set.
Explanation: The userid passed into authenticate was null or invalid.
User Response: Verify the information used to login. Retry the operation
with a valid userid. If a properties login is performed, check the properties
file to ensure a userid has been set.
JSAS0191E: Null or
empty BasicAuth Token, unable to authenticate. Verify the information used
to log in. Retry the operation with a valid userid and password. If a properties
login is performed, check the properties file to ensure a userid and password
has been set. Explanation: The userid and password passed
into authenticate was null. User Response: Verify the information
used to login. Retry the operation with a valid userid and password. If a
properties login is performed, check the properties file to ensure a userid
and password has been set.
JSAS0192E: Java exception for
com.ibm.NamingStringSyntax._StandardSyntaxModelImpl(). Either the class
was not found or the JVM is running out of memory. Ensure that the classpath
has a valid version of UJC.JAR. Retry the operation after stopping and
restarting the server. If the problem persists, contact support for assistance.
Explanation: A Java runtime exception occurred while
creating a new object for _StandardSyntaxModelImpl. User Response:
Either the class was not found or the JVM is running out of memory.
Ensure that the classpath has a valid version of UJC.JAR. Retry the operation
after stopping and restarting the server. If the problem persists, contact
support for assistance.
JSAS0193E: Invalid name exception
for com.ibm.CORBA.iiop.ORB.resolve_initial_references(). Verify that security
is enabled in the client and server configuration (com.ibm.CORBA.securityEnabled=true).
Check the client program to ensure that a valid name is passed into "resolve_initial_references".
Explanation: This message indicates that the name passed
into "resolve_initial_references" in the program is invalid or has not
yet been registered. User Response: Verify that security is
enabled in the client and server configuration (com.ibm.CORBA.securityEnabled=true).
Check the client program to ensure that a valid name is passed into "resolve_initial_references".
JSAS0194E: Java exception for com.ibm.CORBA.iiop.ORB.resolve_initial_references().
Either the class was not found or the JVM is running out of memory. Ensure
that the classpath has a valid version of UJC.JAR. Retry the operation
after stopping and restarting the server. If the problem persists, contact
support for assistance. Explanation: A Java runtime exception
occurred while looking up an object in Current. User Response:
Either the class was not found or the JVM is running out of memory.
Ensure that the classpath has a valid version of UJC.JAR. Retry the operation
after stopping and restarting the server. If the problem persists, contact
support for assistance.
JSAS0195E: Java exception for org.omg.CosNaming.NamingContextHelper.narrow().
Either a class was not found or the JVM is running out of memory. Ensure
that the classpath has a valid version of UJC.JAR. Retry the operation
after stopping and restarting the server. If the problem persists, contact
support for assistance. Explanation: A Java runtime exception
occurred while getting the root naming context. User Response:
Either a class was not found or the JVM is running out of memory. Ensure
that the classpath has a valid version of UJC.JAR. Retry the operation
after stopping and restarting the server. If the problem persists, contact
support for assistance.
JSAS0196E: Java exception for org.omg.CORBA.Object.resolve().
Check to see if other errors occurred on the AdminServer console. This
error typically points to a problem with the SecurityServer. If a validate
exception is occuring and you are using the LDAP admin ID, try changing
the Security name of the server to a valid LDAP user, instead of the LDAP
admin ID. If the problem persists, contact support for assistance.
Explanation: An exception occurred while trying to access the SecurityServer
object. If the error is a CORBA_ROLLBACK, an exception occurred while executing
a method in the SecurityServer. User Response: Check to see
if other errors occurred on the AdminServer console. This error typically
points to a problem with the SecurityServer. If a validate exception is
occurring and you are using the DAP Adm. ID, try changing the Security
name of the server to a valid DAP user, instead of the DAP Adm. ID. If
the problem persists, contact support for assistance.
JSAS0197E: Java exception for com.ibm.WebSphereSecurity.SecurityServerHelper.narrow().
Check to see if other errors occurred on the AdminServer console. This
error typically points to a problem with the SecurityServer. If a validate
exception is occurring and you are using the LDAP admin ID, try changing
the Security name of the server to a valid LDAP user, instead of the LDAP
admin ID. If the problem persists, contact support for assistance.
Explanation: An exception occurred while trying to access the SecurityServer
object. If the error is a CORBA_ROLLBACK, an exception occurred while executing
a method in the SecurityServer. User Response: Check to see
if other errors occurred on the AdminServer console. This error typically
points to a problem with the SecurityServer. If a validate exception is
occurring and you are using the LDAP admin ID, try changing the Security
name of the server to a valid LDAP user, instead of the LDAP admin ID.
If the problem persists, contact support for assistance.
JSAS0198E: Java language error for com.ibm.WebSphereSecurity.SecurityServerHelper.narrow().
Check to see if other errors occurred on the AdminServer console. This
error typically points to a problem with the SecurityServer. If a validate
exception is occurring and you are using the LDAP admin ID, try changing
the Security name of the server to a valid LDAP user, instead of the LDAP
admin ID. If the problem persists, contact support for assistance.
Explanation: An exception occurred while trying to access the SecurityServer
object. If the error is a CORBA_ROLLBACK, an exception occurred while executing
a method in the SecurityServer. User Response: Check to see
if other errors occurred on the AdminServer console. This typically points
to a problem with the SecurityServer. If a validate exception is occurring
and you are using the LDAP admin ID, try changing the Security name of
the server to a valid LDAP user, instead of the LDAP admin ID. If the problem
persists, contact support for assistance.
JSAS0199E: Security
server could not be initialized; reason is unknown. Check to see if other
errors occurred on the AdminServer console. This error typically points
to a problem with the SecurityServer. If a validate exception is occurring
and you are using the LDAP admin ID, try changing the Security name of
the server to a valid LDAP user, instead of the LDAP admin ID. If the problem
persists, contact support for assistance. Explanation: An
exception occurred while trying to access the SecurityServer object. If
the error is a CORBA_ROLLBACK, an exception occurred while executing a
method in the SecurityServer. User Response: Check to see if
other errors occurred on the AdminServer console. This error typically
points to a problem with the SecurityServer. If a validate exception is
occurring and you are using the LDAP admin ID, try changing the Security
name of the server to a valid LDAP user, instead of the LDAP admin ID.
If the problem persists, contact support for assistance.
JSAS0200E: Attempt to establish a secure association at the target server
failed. Check and verify your userid and password. Retry the operation
after a few minutes. If the problem persists, contact support for assistance.
Explanation: The attempt to authenticate the client has
been rejected. Most of the time this rejection is due to an invalid userid
and password. Sometimes this error is due to an unavailable security server.
User Response: Check and verify your userid and password. Retry
the operation after a few minutes. If the problem persists, contact support
for assistance. JSAS0201E: Authentication failed. Check
the userid and password entered and retry the operation. Check to loginSource
property to verify you are logging in with the proper credentials. Make sure
the userid and password exist in the user registry. Explanation:
The userid and password specified during login were not valid.
User Response: Check the userid and password entered and retry the
operation. Check to loginSource property to verify you are logging in with
the proper credentials. Make sure the userid and password exist in the user
registry.
JSAS0202E: Credential token expired. Close the
client and log in again. Explanation: The credential
token associated with the user credential has expired. This situation typically
occurs with LTPA. User Response: Close the client and log in
again.
JSAS0205E: Userid or password were invalid. Check
the userid and password entered and retry the operation. Check to loginSource
property to verify you are logging in with the proper credentials. Make
sure the userid and password exist in the user registry.
Explanation: The userid and password specified during login were not
valid. User Response: Check the userid and password entered
and retry the operation. Check to loginSource property to verify you are logging
in with the proper credentials. Make sure the userid and password exist in
the user registry.
JSAS0206E: Unsupported realm. Verify
that the global security configuration is valid. The realm determines which
user registry to use for authenticating users. Check the principalName
property in sas.server.props to ensure it is set correctly.
Explanation: The realm selected is not supported. User Response:
Verify that the global security configuration is valid. The realm determines
which user registry to use for authenticating users. Check the principalName
property in sas.server.props to ensure it is set correctly.
JSAS0207E: Internal error: method not implemented. This error typically indicates
that the function has not yet been implemented. If the problem persists, contact
support for assistance. Explanation: The method to be invoked
was not yet implemented. User Response: This error typically
indicates that the function has not yet been implemented. If the problem persists,
contact support for assistance.
JSAS0208E: Internal error:
system exception. Write down all the error information and contact support
for assistance. Explanation: A system exception occurred
in the security code. User Response: Write down all the error
information and contact support for assistance.
JSAS0209E:
Internal error: Java exception. Write down all the error information and
notify support of the problem. Explanation: A Java runtime
exception occurred. User Response: Write down all the error
information and notify support of the problem.
JSAS0210E:
Password expired. Notify the administrator of your user registry to reset
your password. Explanation: The password has expired in
the user registry. User Response: Notify the administrator of
your user registry to reset your password.
JSAS0215E:
Account locked. Notify the administrator of your user registry to get your
account reset. Explanation: The account associated with your
userid has been locked. User Response: Notify the administrator
of your user registry to get your account reset.
JSAS0220E:
Service unavailable. Please retry the operation in a few minutes. If the problem
persists, notify your system administrator. Explanation: The
security server which authenticates your userid and password is temporarily
unavailable. User Response: Please retry the operation in a
few minutes. If the problem persists, notify your system administrator.
JSAS0221E: Validation not supported. Check the client code to ensure it
is not calling validate incorrectly. Resubmit the request after waiting
a few minutes. If the problem persists, contact support for assistance.
Explanation: Validation is not supported given the current
security configuration. User Response: Check the client code
to ensure it is not calling validate incorrectly. Resubmit the request
after waiting a few minutes. If the problem persists, contact support for
assistance.
JSAS0225E: Internal error. Please retry the
operation in a few minutes. If the problem persists, notify your system administrator.
Explanation: An internal system error occurred while trying
to authenticate your userid and password. User Response: Please
retry the operation in a few minutes. If the problem persists, notify your
system administrator.
JSAS0230E: Reason unknown. Please
retry the operation in a few minutes. If the problem persists, notify your
system administrator. Explanation: The authentication failed
for an unknown reason. User Response: Please retry the operation
in a few minutes. If the problem persists, notify your system administrator.
JSAS0235E: Client authentication required. The client configuration may have
client authentication disabled. Ensure that SSLTypeIServerAssociationEnabled=true.
Explanation: The target server requires that the user authenticate
before trying to issue a method request. User Response: The client
configuration may have client authentication disabled. Ensure that SSLTypeIServerAssociationEnabled=true.
JSAS0240E: Login failed. Verify the userid and password is correct. Check
the properties file to ensure the login source is valid. If this error occurs
on the server, check the server properties to ensure the principalName has
a valid realm and userid. Explanation: This message indicates
that the attempt at authenticating failed. User Response: Verify
the userid and password is correct. Check the properties file to ensure the
login source is valid. If this error occurs on the server, check the server
properties to ensure the principalName has a valid realm and userid.
JSAS0250E: Secure association compromised. Retry the operation. Might want
to contact your network administrator to see if any network problems occurred
during the time of the errors. If the problem persists, contact support for
assistance. Explanation: The message from the server has
been corrupted. This situation could result from message tampering or just
a power spike causing bytes to get jumbled. User Response: Retry
the operation. Might want to contact your network administrator to see if
any network problems occurred during the time of the errors. If the problem
persists, contact support for assistance.
JSAS0300E: Invalid
message type returned from target. Retry the operation after a few minutes.
If the problem persists, messages on the server system should give a better
indication of what the problem is. Further tracing on the server may be
necessary. Contact support for assistance. Explanation:
A message type sent from the server to the client is not a valid message
type. Typically this situation occurs when the server throws an exception
during the processing of a request. Typically, the request has not completed.
User Response: Retry the operation after a few minutes. If the problem
persists, there should be messages on the server system which may give a better
indication of what the problem is. Further tracing on the server may be necessary.
Contact support for assistance.
JSAS0310E: Invalid security
attribute type, unable to authenticate. Verify the program to ensure that
the attribute being accessed is a valid credential attribute. You may need
to contact your system administrator to verify that all of the attributes
you need have been set in the user registry. Explanation: A
security attribute is a value stored in the credential object such as userid
or groupid. Either the type trying to be accessed is not a valid credential
attribute type, or the attribute being accessed is null. User
Response: Verify the program to ensure that the attribute being accessed
is a valid credential attribute. You may need to contact your system administrator
to verify that all of the attributes you need have been set in the user registry.
JSAS0320E: Connection type found in session entry was not valid for this security
context. Ensure that the security configuration has the SSLKeyring, SSLKeyringPassword,
SSLClientKeyring, SSLClientKeyringPassword, SSLServerKeyring (clientside),
SSLServerKeyringPassword, and that the keyring file has valid, non-expired
certificates. Also, ensure that SSLTypeIClientAssociationEnabled=true in the
sas.server.props. If problem persists, contact support for assistance.
Explanation: The connection type was not SSL, but rather some other type
of connection, likely TCPIP. User Response: Ensure that the security
configuration has the SSLKeyring, SSLKeyringPassword, SSLClientKeyring, SSLClientKeyringPassword,
SSLServerKeyring (clientside), SSLServerKeyringPassword, and that the keyring
file has valid, non-expired certificates. Also, ensure that SSLTypeIClientAssociationEnabled=true
in the sas.server.props. If problem persists, contact support for assistance.
JSAS0330E: Target sequence number in received message out of sync with session
entry. Explanation: None. User Response: None.
JSAS0340E: Invalid communication direction for security feature. Ensure the
call to get_security_features passes in org.omg.Security.CommunicationDirection._SecDirectionBoth.
Explanation: The communication direction passed into get_security_features
currently only supports org.omg.Security.CommunicationDirection._SecDirectionBoth.
User Response: Ensure the call to get_security_features passes in org.omg.Security.CommunicationDirection._SecDirectionBoth.
JSAS0350E: Security attribute type is null or invalid. Verify the program
to ensure that the attribute being accessed is a valid credential attribute.
You may need to contact your system administrator to verify that all of the
attributes you need have been set in the user registry. Explanation:
A security attribute is a value stored in the credential object such as
userid or groupid. Either the type trying to be accessed is not a valid credential
attribute type or the attribute being accessed is null. User Response:
Verify the program to ensure that the attribute being accessed is a valid
credential attribute. You may need to contact your system administrator to
verify that all of the attributes you need have been set in the user registry.
JSAS0355E: Duplicate security attribute type specified. Verify the program
to ensure that the same attribute is not trying to be retrieved more than
once at the same time. Explanation: This error indicates that
the same attribute in the credential object is being accessed more than once
for a single get_attributes call. User Response: Verify the program
to ensure that the same attribute is not trying to be retrieved more than
once at the same time.
JSAS0360E: Security attribute list
is null. Verify that the list of attributes that is trying to be set is not
null. Retry the operation. If the problem persists, contact support for assistance.
Explanation: While calling set_attributes on the credential,
the attribute list is null. User Response: Verify that the list
of attributes that is trying to be set is not null. Retry the operation. If
the problem persists, contact support for assistance.
JSAS0370E: Security attribute list contains null attribute type or attribute
family. Verify that the list of attributes that is trying to be set does not
contain a null attribute. Retry the operation. If the problem persists, contact
support for assistance. Explanation: While calling set_attributes
on the credential, the attribute list contains a type which is null.
User Response: Verify that the list of attributes that is trying to be
set does not contain a null attribute. Retry the operation. If the problem
persists, contact support for assistance.
JSAS0380E: Security
attribute list contains null member. Verify that the list of attributes that
is trying to be set does not contain a null attribute. Retry the operation.
If the problem persists, contact support for assistance. Explanation:
While calling set_attributes on the credential, the attribute list contains
a type which is null. User Response: Verify that the list of attributes
that is trying to be set does not contain a null attribute. Retry the operation.
If the problem persists, contact support for assistance.
JSAS0400E: Could not close the key file; processing will continue. Processing
should continue. If problem persists, contact support for assistance.
Explanation: A Java I/O Exception occurred while trying to close the
keyfile. User Response: Processing should continue. If problem
persists, contact support for assistance.
JSAS0401E: Vault
handed in is not an ISecurityLocalObjectBaseL13Impl.Vault. Verify that the
correct version of UJC.JAR is loaded in the classpath. If the problem persists,
contact support for assistance. Explanation: The class package
is not valid. User Response: Verify that the correct version of
UJC.JAR is loaded in the classpath. If the problem persists, contact support
for assistance.
JSAS0402E: The standardClaimQOPModels attribute
contains an invalid option; using Authenticity. Correct the value specified
on the standardClaimQOPModels property if you do not want to use Authenticity.
Explanation: The option specified in standardClaimQOPModels
is not valid. Valid options include Authenticity, Integrity, Confidentiality,
and Advanced. User Response: Correct the value specified on the
standardClaimQOPModels property if you do not want to use Authenticity.
JSAS0403E: The delegateCredentials property contains an illegal delegation
mode. Correct the value specified on the delegateCredentials property. The
default is None. Explanation: Valid delegateCredentials property
values include None, Simple, Scoped, Traced, and MethodDefined. User
Response: Correct the value specified on the delegateCredentials property.
The default is None.
JSAS0404E: The loginTimeout property
is out of range. Correct the value so that it falls between 0 and 600,
specified in seconds. Explanation: The valid range is
0 - 600. User Response: Correct the value so that it falls between
0 and 600, specified in seconds.
JSAS0405E: The property
contains a non-integer string value. Correct the value specified in the property
so that it is an integer number. Explanation: The value entered
could not be represented as an integer number. User Response: Correct
the value specified in the property so that it is an integer number.
JSAS0406E: The standardPerformQOPModels attribute contains an invalid option.
Correct the value specified on the standardPerformQOPModels property if you
do not want to use Authenticity. Explanation: The option specified
in standardPerformQOPModels is not valid. Valid options include Authenticity,
Integrity, Confidentiality, and Advanced. User Response: Correct
the value specified on the standardPerformQOPModels property if you do not
want to use Authenticity.
JSAS0407E: The securityBootStrapRepositoryPort
property contains a non-integer string value. Correct the value specified
in the property so that it is an integer number. Explanation:
The value entered could not be represented as an integer number.
User Response: Correct the value specified in the property so that it
is an integer number.
JSAS0408E: The SSLCredentialsTimeout
property is out of range. Correct the value specified in the property so that
it is in the valid range. Explanation: The valid range for
SSLCredentialsTimeout property is 0 through 364 days, specified in seconds.
User Response: Correct the value specified in the property so that
it is in the valid range.
JSAS0409E: The SSLCredentialsTimeout
property contains a non-integer string value. Correct the value specified
in the property so that it is an integer number. Explanation:
The value entered could not be represented as an integer number.
User Response: Correct the value specified in the property so that it
is an integer number.
JSAS0410E: The SSLPort property contains
a non-integer string value. Correct the value specified in the property so
that it is an integer number. Explanation: The value entered
could not be represented as an integer number. User Response: Correct
the value specified in the property so that it is an integer number.
JSAS0411E: The SSLV3SessionTimeout property is out of range. Correct the value
specified so that it is within the valid range. Explanation: The
valid range for SSLV3SessionTimeout is 0 through 1 day specified in seconds.
User Response: Correct the value specified so that it is within the valid
range.
JSAS0412E: The SSLV3SessionTimeout property contains
a non-integer string value. Correct the value specified in the property so
that it is an integer number. Explanation: The value entered
could not be represented as an integer number. User Response: Correct
the value specified in the property so that it is an integer number.
JSAS0413E: A problem occurred while processing the security configuration.
Verify the data entered in the security configuration is valid. If the
problem persists, contact support for assistance. Explanation:
A Java runtime exception occurred while processing the sas.server.props
or sas.client.props. User Response: Verify the data entered
in the security configuration is valid. If the problem persists, contact support
for assistance.
JSAS0414E: The configuration is incorrect;
security will be disabled. If you get this error, other errors will have proceeded
it which describe the problems with the configuration. Explanation:
Based on the verification level which determines how tightly to verify
the configuration, it has been determined that the configuration is not consistent.
The verification levels are Completeness, Consistency, PassivelyCorrect and
ActivelyCorrect. The default for com.ibm.CORBA.verificationLevel is Consistency.
User Response: If you get this error, other errors will have proceeded
it which describe the problems with the configuration.
JSAS0415E: The configuration is incorrect. If you get this error, other errors
will have proceeded it which describe the problems with the configuration.
Explanation: Based on the verification level which determines
how tightly to verify the configuration, it has been determined that the configuration
is not consistent. The verification levels are Completeness, Consistency,
PassivelyCorrect and ActivelyCorrect. The default for com.ibm.CORBA.verificationLevel
is Consistency. User Response: If you get this error, other errors
will have proceeded it which describe the problems with the configuration.
JSAS0416E: The configuration is in an unknown state. If you get this error,
other errors will have proceeded it which describe the problems with the configuration.
Explanation: Based on the verification level which determines
how tightly to verify the configuration, it has been determined that the configuration
is not consistent. The verification levels are Completeness, Consistency,
PassivelyCorrect and ActivelyCorrect. The default for com.ibm.CORBA.verificationLevel
is Consistency. User Response: If you get this error, other errors
will have proceeded it which describe the problems with the configuration.
JSAS0417E: The active correctness verification produced a verification
result. If you get anything other than 0, you will have preceeding messages
which describe the specific problem. Explanation: The verification
results are: Unknown (-1), Success (0), ConfigIncomplete (1), ConfigInconsistent
(2), and ConfigWrong (3). User Response: If you get anything other
than 0, you will have preceeding messages which describe the specific problem.
JSAS0418E: The configuration has not been initialized. Ensure that the sas.server.props
or sas.client.props file is complete and in the location specified by the
com.ibm.CORBA.ConfigURL. This location is typically WASROOT/properties.
Explanation: This message indicates that the sas.server.props or sas.client.props
file has not been processed. User Response: Ensure that the
sas.server.props or sas.client.props file is complete and in the location
specified by the com.ibm.CORBA.ConfigURL. This location is typically WASROOT/properties.
JSAS0419E: The bootstrap repository file name has not been set. Verify that
the com.ibm.CORBA.bootstrapRepositoryLocation property has been set in the
sas.server.props. Explanation: The bootstrap repository name
is specified on the com.ibm.CORBA.bootstrapRepositoryLocation property in
the sas.server.props file. User Response: Verify that the com.ibm.CORBA.bootstrapRepositoryLocation
property has been set in the sas.server.props.
JSAS0420E:
None of the association options have been set. Ensure that at least one of
these association options are set. Explanation: At least one
of the following association options must be set: DCEClientAssociationEnabled,
DCEServerAssociationEnabled, SSLTypeIClientAssociationEnabled, SSLTypeIServerAssociationEnabled,
LTPAClientAssociationEnabled, LTPAServerAssociationEnabled, LocalOSClientAssociationEnabled,
LocalOSServerAssociationEnabled. User Response: Ensure that at
least one of these association options are set.
JSAS0421E:
The SSL client keyring has not been set. Ensure that this property has been
set with a valid keyring file. Explanation: This message
indicates that the com.ibm.CORBA.SSLClientKeyRing property has not be set
in either the sas.server.props or the sas.client.props. User
Response: Ensure that this property has been set with a valid keyring
file.
JSAS0422E: The configuration is incomplete. A preceeding
message will likely tell you the exact reason why it is incomplete. The likely
reasons are no Bootstrap Repository location, no association options selected,
or the configuration has not been initialized. Explanation: A
verification result of ConfigIncomplete (1) has been returned. User
Response: A preceeding message will likely tell you the exact reason why
it is incomplete. The likely reasons are no Bootstrap Repository location,
no association options selected, or the configuration has not been initialized.
JSAS0423E: The completeness verification produced a verification result.
If you get anything other than 0, you will have preceeding messages which
describe the specific problem. Explanation: The verification
results are: Unknown (-1), Success (0), ConfigIncomplete (1), ConfigInconsistent
(2), and ConfigWrong (3). User Response: If you get anything other
than 0, you will have preceeding messages which describe the specific problem.
JSAS0424E: The login source is Properties, however either the userid or password
were not specified. Specify a userid on com.ibm.CORBA.loginUserid and password
on com.ibm.CORBA.loginPassword if you intend to use the login source of properties.
Explanation: This message indicates an inconsistency in
the configuration because a login source of properties needs to have a
userid and password specified. User Response: Specify a userid
on com.ibm.CORBA.loginUserid and password on com.ibm.CORBA.loginPassword if
you intend to use the login source of properties.
JSAS0425E:
The login source is KeyTable, however the KeyTable file was not specified.
Specify a KeyTable file on com.ibm.CORBA.keytabFileName if you intend to use
the login source of KeyTable. Explanation: This message
indicates an inconsistency in the configuration because a login source
of KeyTable needs to have a KeyTable file specified. User Response:
Specify a KeyTable file on com.ibm.CORBA.keytabFileName if you intend
to use the login source of KeyTable.
JSAS0426E: The secure
association options require the use of SSL, however either the keyring
or the keyring password were not specified. Ensure one of these properties
is set in the sas.client.props and sas.server.props. Explanation:
One of the following keyring properties is not set: SSLClientKeyRing,
SSLServerKeyRing, SSLClientKeyRingPassword, or SSLServerKeyRingPassword.
User Response: Ensure one of these properties is set in the sas.client.props
and sas.server.props.
JSAS0427E: The specified perform-QOP
options are not valid. Verify that the above properties are consistent.
Explanation: The property com.ibm.CORBA.standardPerformQOPModels is
set to advanced, however, the way that the following properties are set
is inconsistent: performClientAuthentication, performServerAuthentication,
performMessageReplayDetection, performMessageOutOfSequenceDetection, performMessageIntegrity,
and performMessageConfidentiality. User Response: Verify
that the above properties are consistent.
JSAS0428E: The
specified claim-QOP options are not valid. Verify that the above properties
are consistent. Explanation: The property com.ibm.CORBA.standardClaimQOPModels
is set to advanced, however, the way that the following properties are
set is inconsistent: performClientAuthentication, performServerAuthentication,
performMessageReplayDetection, performMessageOutOfSequenceDetection, performMessageIntegrity,
and performMessageConfidentiality. User Response: Verify
that the above properties are consistent.
JSAS0429E: The
configuration is inconsistent. The reason for this inconsistency will be
printed out in a preceeding message. Explanation: This
message is printed when there are dependencies between two configuration
options and one of the dependencies is not met. For example, if SSL is
configured but the KeyRing file is not. User Response: The exact
reason of the inconsistency will be printed out in a preceeding message.
JSAS0430E: The consistency verification produced a verification result.
If you get anything other than 0, you will have preceeding messages which
describe the specific problem. Explanation: The verification
results are: Unknown (-1), Success (0), ConfigIncomplete (1), ConfigInconsistent
(2), and ConfigWrong (3). User Response: If you get anything other
than 0, you will have preceeding messages which describe the specific problem.
JSAS0431E: The passive correctness verification produced a verification
result. If you get anything other than 0, you will have preceeding messages
which describe the specific problem. Explanation: The verification
results are: Unknown (-1), Success (0), ConfigIncomplete (1), ConfigInconsistent
(2), and ConfigWrong (3). User Response: If you get anything other
than 0, you will have preceeding messages which describe the specific problem.
JSAS0432E: The SSL server keyring has not been set. Ensure that this property
has been set with a valid keyring file. Explanation: This
message indicates that the com.ibm.CORBA.SSLServerKeyRing property has
not be set in either the sas.server.props or the sas.client.props.
User Response: Ensure that this property has been set with a valid
keyring file.
JSAS0433E: The performClientAuthentication
is set, but none of the server association options are set. Ensure that at
least one of the server association properties are set to true.
Explanation: The property com.ibm.CORBA.performClientAuthentication is
set, however, one of the following is not set: SSLTypeIServerAssociationEnabled,
SSLTypeIIServerAssociationEnabled, LTPAServerAssociationEnabled, or LocalOSServerAssociationEnabled.
User Response: Ensure that at least one of the server association
properties is set to true.
JSAS0434E: The Key File contains
an entry containing the wrong number of values: Explanation: None.
User Response: None.
JSAS0435E: Credentials are invalid.
Log in again to get new credentials. Sometimes it is necessary to restart
the client and server to ensure that you are using new credentials. Once
credentials are marked invalid, they cannot become valid again.
Explanation: The invalid flag on the credential object has been set
to true. Typically this situation results from the credential being rejected
by the server when trying to authenticate. A NO_PERMISSION exception has
likely been thrown by the server. User Response: Log in again
to get new credentials. Sometimes it is necessary to restart the client
and server to ensure that you are using new credentials. Once credentials
are marked invalid, they cannot become valid again.
JSAS0436E:
The configuration is ambiguous about which security mechanism to use. Try
to review the client or server security configuration files (sas.client.props
or sas.server.props). If recent changes have been made you may want to undo
these changes. If you do not see any problems with the configuration and you
still get this error, contact support for assistance. Explanation:
This error indicates that the client or server configuration properties
are not valid, or are conflicting. Some properties cannot be set together
and still be valid. User Response: Try to review the client
or server security configuration files (sas.client.props or sas.server.props).
If recent changes have been made you may want to undo these changes. If you
do not see any problems with the configuration and you still get this error,
contact support for assistance.
JSAS0437E: The DCE tagged
component was mal-formed and cannot be parsed. Ensure that the server version
to which you are trying to connect is supported. Make sure the UJC.JAR
you are using on the client side is compatible with that of the server.
Explanation: While parsing the tagged component, a SystemException
occurred. User Response: Ensure that the server version to which
you are trying to connect is supported. Make sure the UJC.JAR you are using
on the client side is compatible with that of the server.
JSAS0438E: Invalid initial reference name. Verify that security is enabled
in the client and server configuration (com.ibm.CORBA.securityEnabled=true).
Check the client program to ensure that a valid name is passed into "resolve_initial_references".
Explanation: This message indicates that the name passed
into "resolve_initial_references" in the program is invalid or has not
yet been registered. User Response: Verify that security is
enabled in the client and server configuration (com.ibm.CORBA.securityEnabled=true).
Check the client program to ensure that a valid name is passed into "resolve_initial_references".
JSAS0439E: Unable to get Credentials. Verify that the client set the credentials
properly before invoking the request. Ensure that the correct userid and
password were specified when logging in. If the problem persists, contact
support for assistance. Explanation: On the server side,
there must be a set of received credentials when communicating over SSL and
Mutual Authentication is enabled. Without the received credentials the server
will throw a NO_PERMISSION exception. User Response: Verify
that the client set the credentials properly before invoking the request.
Ensure that the correct userid and password were specified when logging
in. If the problem persists, contact support for assistance.
JSAS0441E: ASSOC_ACCEPT message is illegal at the target. Retry the operation
after a few minutes. Check the client configuration to ensure there is
nothing out of the ordinary that might be causing an exception to occur.
If the problem persists, contact support for assistance. Explanation:
The message type ASSOC_ACCEPT should not be received at the target
server. This situation might result from an exception on the client which
caused a mixup. User Response: Retry the operation after a few
minutes. Check the client configuration to ensure there is nothing out
of the ordinary that might be causing an exception to occur. If the problem
persists, contact support for assistance.
JSAS0442E:
ASSOC_REJECT message is illegal at the target. Retry the operation after
a few minutes. Check the client configuration to ensure there is nothing
out of the ordinary that might be causing an exception. If the problem
persists, contact support for assistance. Explanation: The
message type ASSOC_REJECT should not be received at the target server.
This message might result from an exception on the client which caused
a mixup. User Response: Retry the operation after a few minutes.
Check the client configuration to ensure there is nothing out of the ordinary
that might be causing an exception. If the problem persists, contact support
for assistance.
JSAS0443E: Request holder service data
key for Security Context invalid. Ensure that the correct UJC.JAR is in the
server and client classpath. There might be a mismatch between these files
on the client and the server. If the problem persists, contact support for
assistance. Explanation: The key used to find the security
context is invalid. User Response: Ensure that the correct UJC.JAR
is in the server and client classpath. There might be a mismatch between these
files on the client and the server. If the problem persists, contact support
for assistance.
JSAS0444E: Security bootstrap repository
contains an invalid reference. Stop the adminserver, rename this file,
restart your adminserver and the file should get recreated from scratch.
Try running "Java com.ibm.ISecurityUtilityImpl.BootstrapRepository %WAS_ROOT%/etc/secbootstrap"
to see if it can be read. Make sure %WAS_ROOT% points to /WebSphere/AppServer.
If the problem persists, contact support for assistance.
Explanation: An object reference retrieved from the Bootstrap Repository
file (found at BootstrapRepositoryLocation property in the sas.server.props)
was null. This situation could indicate that the repository is corrupted.
User Response: Stop the adminserver, rename this file, restart your
adminserver and the file should get recreated from scratch. Try running
"Java com.ibm.ISecurityUtilityImpl.BootstrapRepository %WAS_ROOT%/etc/secbootstrap"
to see if it can be read. Make sure %WAS_ROOT% points to /WebSphere/AppServer.
If the problem persists, contact support for assistance.
JSAS0445E: Unknown host. An attempt will be made to use the host name,
however, if this fails you will need to take action. Contact your network
administrator to ensure that the hostname and IP address which you have
configured on the server is valid. Explanation: Could not
convert to the dotted IP address from the host name. User Response:
An attempt will be made to use the host name, however, if this fails
you will need to take action. Contact your network administrator to ensure
that the hostname and IP address which you have configured on the server
are valid.
JSAS0446E: The listening port has not yet been
initialized. Check the configuration to ensure there is not a property
which inadvertently sets the port to something already being used. Stop
the server and wait for about 2 minutes before restarting the server so
that all ports in use will be released. Explanation: This
message indicates that the port specified in the server connection data
is 0. User Response: Check the configuration to ensure there
is not a property which inadvertently sets the port to something already
being used. Stop the server and wait for about 2 minutes before restarting
the server so that all ports in use will be released.
JSAS0447E: The security tagged component assistor is not an ObjectImpl
and therefore cannot be registered with the ORB. Check to ensure you have
the same version of UJC.JAR as the server. Check the dates of the file
on the server to ensure they match the dates of other JAR files on the
server in case a mismatch has occurred. Explanation: The
SecurityTaggedComponentAssistorImpl.class file in the UJC.JAR is not valid.
User Response: Check to ensure you have the same version of UJC.JAR as
the server. Check the dates of the file on the server to ensure they match
the dates of other JAR files on the server in case a mismatch has occurred.
JSAS0448E: The security bootstrap repository is inconsistent. Stop the
adminserver, rename this file to anything else, restart your adminserver
and the file should get recreated from scratch. Try running "java com.ibm.ISecurityUtilityImpl.BootstrapRepository
%WAS_ROOT%/etc/secbootstrap" to see if it can be read. Make sure %WAS_ROOT%
points to /WebSphere/AppServer. If the problem persists, contact support
for assistance. Explanation: The file pointed to by BootstrapRepositoryLocation
in the sas.server.props has been corrupted. User Response: Stop
the adminserver, rename this file to anything else, restart your adminserver
and the file should get recreated from scratch. Try running "Java com.ibm.ISecurityUtilityImpl.BootstrapRepository
%WAS_ROOT%/etc/secbootstrap" to see if it can be read. Make sure %WAS_ROOT%
points to /WebSphere/AppServer. If the problem persists, contact support
for assistance.
JSAS0449E: The SSL tagged component was
mal-formed and cannot be parsed. Ensure that the server version you are
trying to connect to is supported. Make sure the UJC.JAR you are using
on the client side is compatible with that of the server.
Explanation: While parsing the tagged component, a SystemException occurred.
User Response: Ensure that the server version you are trying to connect
to is supported. Make sure the UJC.JAR you are using on the client side is
compatible with that of the server.
JSAS0450E: Failed to
initialize security context. Have the client verify that the userid and
password specified during login are valid. Explanation:
This indicates that a client is trying to establish a secure association
with the server, but failed to authenticate. User Response: Have
the client verify that the userid and password specified during login are
valid.
JSAS0451E: Credentials do not contain a Public security
name. The client should specify a userid and password to get authenticated.
Explanation: The public security name is the client
userid. In this case, a userid was not specified. User Response:
The client should specify a userid and password to get authenticated.
JSAS0452E: The security context is no longer valid. Try to review the client
or server security configuration files (sas.client.props or sas.server.props).
If recent changes have been made you may want to undo these changes. If you
do not see any problems with the configuration and you still get this error,
contact support for assistance. Explanation: This error typically
occurs when adding a security session on the client or server. User
Response: Try to review the client or server security configuration files
(sas.client.props or sas.server.props). If recent changes have been made you
may want to undo these changes. If you do not see any problems with the configuration
and you still get this error, contact support for assistance.
JSAS0453E: No credentials could be found identifying the local target. Check
the sas.server.props com.ibm.CORBA.PrincipalName, com.ibm.CORBA.UserID, and
com.ibm.CORBA.Password properties to ensure they are valid. For the com.ibm.CORBA.PrincipalName,
ensure the correct realm is specified in front of the userid (realm/userid).
If you do not see any problems with these properties, contact support for
assistance. Explanation: The server credentials could not be
found. User Response: Check the sas.server.props com.ibm.CORBA.PrincipalName,
com.ibm.CORBA.UserID, and com.ibm.CORBA.Password properties to ensure they
are valid. For the com.ibm.CORBA.PrincipalName, ensure the correct realm is
specified in front of the userid (realm/userid). If you do not see any problems
with these properties, contact support for assistance.
JSAS0454E: Could not create local credentials. Check the sas.server.props
com.ibm.CORBA.PrincipalName, com.ibm.CORBA.UserID, and com.ibm.CORBA.Password
properties to ensure they are valid. For the com.ibm.CORBA.PrincipalName,
ensure the correct realm is specified in front of the userid (realm and
userid). If you do not see any problems with these properties, contact
support for assistance. Explanation: This message indicates
that a login failed on the server. User Response: Check the
sas.server.props com.ibm.CORBA.PrincipalName, com.ibm.CORBA.UserID, and
com.ibm.CORBA.Password properties to ensure they are valid. For the com.ibm.CORBA.PrincipalName,
ensure the correct realm is specified in front of the userid (realm and
userid). If you do not see any problems with these properties, contact
support for assistance.
JSAS0455E: Attempting to acquire
a security server of an unknown type. Explanation: None.
User Response: None.
JSAS0456E: Attempting to set a
security server of an unknown type. Explanation: None.
User Response: None.
JSAS0457E: LocalOSServerImpl no
class definition found error. Verify that IBMWEBAS.JAR is in the classpath
on the server. Restart the server and retry the operation. If the problem
persists, contact support for assistance. Explanation: Could
not find the class com.ibm.LocalOSImpl.LocalOSServerImpl. User Response:
Verify that IBMWEBAS.JAR is in the classpath on the server. Restart the
server and retry the operation. If the problem persists, contact support for
assistance.
JSAS0458E: LocalOSServerImpl unsatisfied link
error. Verify that IBMWEBAS.JAR is in the classpath on the server. Restart
the server and retry the operation. If the problem persists, contact support
for assistance. Explanation: Could not find the class com.ibm.LocalOSImpl.LocalOSServerImpl.
User Response: Verify that IBMWEBAS.JAR is in the classpath on the server.
Restart the server and retry the operation. If the problem persists, contact
support for assistance.
JSAS0459E: LTPAServerImpl CosNaming.NamingContextHelper.narrow
general exception. Explanation: None. User Response:
None.
JSAS0460E: LTPAServerImpl WebSphereSecurity.SecurityServerHelper.narrow
general exception Explanation: None. User Response:
None.
JSAS0461E: Invalid credential token, unable to
validate. Retry the operation after a few minutes. If using request_login
for Domino, ensure that Domino/WebSphere SSO is set up correctly. If the
problem persists, contact support for assistance. Explanation:
The credential token is null, expired, or has been tampered with. Since
the token is digitally signed, any modification of the bytes in the token
will not verify. Typically this error is due to a null token. User
Response: Retry the operation after a few minutes. If using request_login
for Domino, ensure that Domino/WebSphere SSO is setup correctly. If the problem
persists, contact support for assistance.
JSAS0462E: I/O
Error trying to open the security bootstrap repository. Check the property
bootstrapRepositoryLocation in the sas.server.props to be sure it points to
a valid filename and location. If the path is correct, rename the file to
allow it to recreate a new file. If the problem still persists, contact support
for assistance. Explanation: An error occurred while opening
the file pointed to by the bootstrapRepositoryLocation property. User
Response: Check the property bootstrapRepositoryLocation in the sas.server.props
to be sure it points to a valid filename and location. If the path is correct,
rename the file to allow it to recreate a new file. If the problem still persists,
contact support for assistance.
JSAS0463E: I/O Error while
processing the security bootstrap repository. Stop the adminserver, rename
this file, restart your adminserver and the file should get recreated.
Try running "Java com.ibm.ISecurityUtilityImpl.BootstrapRepository %WAS_ROOT%/etc/secbootstrap"
to see if the file can be read. Make sure %WAS_ROOT% points to /WebSphere/AppServer.
If the problem persists, contact support for assistance.
Explanation: The file pointed to by BootstrapRepositoryLocation in the
sas.server.props has been corrupted. User Response: Stop the
adminserver, rename this file, restart your adminserver and the file should
get recreated. Try running "Java com.ibm.ISecurityUtilityImpl.BootstrapRepository
%WAS_ROOT%/etc/secbootstrap" to see if the file can be read. Make sure
%WAS_ROOT% points to /WebSphere/AppServer. If the problem persists, contact
support for assistance.
JSAS0464E: I/O Error while writing
the security bootstrap repository. Stop the adminserver, rename this file,
restart your adminserver and the file should get recreated. Try running
"Java com.ibm.ISecurityUtilityImpl.BootstrapRepository %WAS_ROOT%/etc/secbootstrap"
to see if the file can be read. Make sure %WAS_ROOT% points to /WebSphere/AppServer.
If the problem persists, contact support for assistance.
Explanation: The file pointed to by BootstrapRepositoryLocation in the
sas.server.props has been corrupted. User Response: Stop the
adminserver, rename this file, restart your adminserver and the file should
get recreated. Try running "Java com.ibm.ISecurityUtilityImpl.BootstrapRepository
%WAS_ROOT%/etc/secbootstrap" to see if it can be read. Make sure %WAS_ROOT%
points to /WebSphere/AppServer. If the problem persists, contact support
for assistance.
JSAS0465E: THE SECURITY SERVICE HAS
ALREADY BEEN INITIALIZED WITH THIS ORB. The ServiceInit (the call that
enables security) will return immediately without reinitializing the security.
The error should be reported to support. A trace will probably be requested
to determine what called ServiceInit a second time. Explanation:
This message indicates that security for this ORB has already been
initialized and an attempt to initialize it again is occurring.
User Response: The ServiceInit (the call that enables security) will
return immediately without reinitializing the security. The error should
be reported to support. A trace will probably be requested to determine
what called ServiceInit a second time.
JSAS0466E: An
I/O error occurred while processing the message buffer. Retry the operation.
If the problem persists, contact support for assistance.
Explanation: A Java InputStream read error occurred. User Response:
Retry the operation. If the problem persists, contact support for assistance.
JSAS0467E: The host address in the IOR is null or blank. Make sure the version
of UJC.JAR is valid for the WebSphere release you are running. Restart the
server and try the operation again. If the problem persists, contact support
for assistance. Explanation: The server host address is
null as read from the IOR which the server exported. User Response:
Make sure the version of UJC.JAR is valid for the WebSphere release you
are running. Restart the server and try the operation again. If the problem
persists, contact support for assistance.
JSAS0468E: The
port in the IOR is zero. Review the logs on the server to ensure the server
started successfully. Check to ensure that you have the correct version
of UJC.JAR. Stop the server, wait 2 minutes, then restart the server and
retry the client operation. If the problem persists, contact support for
assistance. Explanation: The server port is null as read
from the IOR which the server exported. User Response: Review
the logs on the server to ensure the server started successfully. Check
to ensure that you have the correct version of UJC.JAR. Stop the server,
wait 2 minutes, then restart the server and retry the client operation.
If the problem persists, contact support for assistance.
JSAS0469E: The IOR is mal-formed -- the connection will be refused. Ensure
that the client version you are using is supported by the server. Check the
UJC.JAR date and size and verify it is the same as that of the server. Check
the classpath to ensure it includes the correct version of UJC.JAR. If the
problem persists, contact support for assistance. Explanation:
Specific values in the IOR that should exist were null. This usually
indicates that an exception occurred while trying to read them or there
is an interoperability problem with another version of the server.
User Response: Ensure that the client version you are using is supported
by the server. Check the UJC.JAR date and size and verify it is the same as
that of the server. Check the classpath to ensure it includes the correct
version of UJC.JAR. If the problem persists, contact support for assistance.
JSAS0470E: Multiple occurrences of the same credentials were found in the
established credentials list. Potentially the same user is accessing the
target server at identical times. While this should not be a problem, it
could contribute to the error. If the problem persists, contact support for
assistance. Explanation: The same credentials have been
found in the established credentials list. The credentials key used to identify
credentials in the established credentials list are the userid, realm, and
credential type. User Response: Potentially the same user is accessing
the target server at identical times. While this should not be a problem,
it could contribute to the error. If the problem persists, contact support
for assistance.
JSAS0471E: The requestCredsExpiration property
is out of range. Correct the value specified in the requestCredsExpiration
property so that it is within the valid range. Explanation: The
valid range for the requestCredsExpiration property is 10 minutes through
364 days. User Response: Correct the value specified in the requestCredsExpiration
property so that it is within the valid range.
JSAS0472E:
The BasicAuth expiration time is smaller than the ORB request timeout; A method
request could take longer than the period over which the requesting credentials
will remain valid. If you are setting these properties explicitly, ensure
that requestTimeout is smaller than requestCredsExpiration. Explanation:
The property com.ibm.CORBA.requestCredsExpiration is smaller than the
property com.ibm.CORBA.requestTimeout. The default for com.ibm.CORBA.requestCredsExpiration
is infinite (this has no bearing on the LTPA token timeout). The default for
com.ibm.CORBA.requestTimeout is 180 seconds. User Response: If
you are setting these properties explicitly, ensure that requestTimeout is
smaller than requestCredsExpiration.
JSAS0473E: Invalid
mechanism type. Check the security configuration to ensure the properties
are set correctly. Retry the operation. If the problem still persists, contact
support for assistance. Explanation: The security mechanism
is not a valid mechanism as defined in the mechanism factory. User
Response: Check the security configuration to ensure the properties are
set correctly. Retry the operation. If the problem still persists, contact
support for assistance.
JSAS0474E: Unable to refresh server
credentials, reset to minimum expiration time. Restart the server. If the
problem persists, contact support for assistance. Explanation:
The server credential needs to be refreshed so that the token does
not expire. This message indicates that the refresh failed. This failure
could result from a problem logging into the server to get a new credential
token or that the credential has been marked invalid. The expiration time
will be set explicitly to correct the problem temporarily. User
Response: Restart the server. If the problem persists, contact support
for assistance.
JSAS0475E: Invalid expiry time. Check to
ensure the value passed into is_valid is not negative. Explanation:
The value passed into the is_valid method is negative. User Response:
Check to ensure the value passed into is_valid is not negative.
JSAS0476E: Invalid credential type. Ensure that the client authentication
target in the client properties is set to a value that the server supports.
Explanation: The credential object passed to the server is
not a type which the server supports. User Response: Ensure that
the client authentication target in the client properties is set to a value
that the server supports.
JSAS0477E: Invalid credential.
Retry the operation. Ensure the program is creating the credential properly
before setting it as the invocation credential. You may need to restart the
client or server which has the invalid credential. If the problem persists,
contact support for assistance. Explanation: This message
results from a null credential, or the credential not being a subtype of
org.omg.SecurityLevel2.Credentials, or the credential being marked invalid
during a failed login attempt, or an unavailable security server.
User Response: Retry the operation. Ensure the program is creating
the credential properly before setting it as the invocation credential. You
may need to restart the client or server which has the invalid credential.
If the problem persists, contact support for assistance.
JSAS0478E: Failed to set invocation credentials. Explanation:
None. User Response: None.
JSAS0479E: Unable
to sleep. Restart the server. If the problem persists, contact support for
assistance. Explanation: A Java runtime exception occurred
while a thread was trying to sleep for a specified number of seconds.
User Response: Restart the server. If the problem persists, contact support
for assistance.
JSAS0480E: Failed to find the correct entry
in key file. Ensure that the property com.ibm.CORBA.keyFileName is pointing
to a keyfile which contains the realm and security name which you are looking
for. Explanation: The keyfile entry to the specified realm
and security name was not found in the keyfile. User Response: Ensure
that the property com.ibm.CORBA.keyFileName is pointing to a keyfile which
contains the realm and security name which you are looking for.
JSAS0481E: Unable to map server credential because key file is not defined.
Ensure that the property com.ibm.CORBA.keyFileName in sas.server.props and
sas.client.props is pointing to a valid keyfile. Explanation:
The keyfile specified in the property com.ibm.CORBA.keyFileName is not
pointing to a valid keyfile. User Response: Ensure that the property
com.ibm.CORBA.keyFileName in sas.server.props and sas.client.props is pointing
to a valid keyfile.
JSAS0482E: Failed to load configured
key file. Verify the keyfile path in the security configuration.
Explanation: The key file reference is null after trying to open key file.
User Response: Verify the keyfile path in the security configuration.
JSAS0483E: The security session at the target is in the wrong state for this
security message. Retry the operation after a few minutes. Verify that the
UJC.JAR used by the client is the same version as that used by the server.
If the problem persists, contact support for assistance. Explanation:
A problem occurred with the message sequencing. This situation may
be a temporary problem, due to a server restart. User Response:
Retry the operation after a few minutes. Verify that the UJC.JAR used
by the client is the same version as that used by the server. If the problem
persists, contact support for assistance.
JSAS0484E: A
problem occurred while decoding the loginPassword property. Retype the
password on the loginPassword property and restart the program.
Explanation: A java runtime exception occurred while decoding the
loginPassword property. User Response: Retype the password on the
loginPassword property and restart the program.
JSAS0485E:
A problem occurred while decoding the SSLClientKeyRingPassword property.
Retype the password on the SSLClientKeyRingPassword property and restart
the program. Explanation: A java runtime exception occurred
while decoding the SSLClientKeyRingPassword property. User Response:
Retype the password on the SSLClientKeyRingPassword property and restart
the program.
JSAS0486E: A problem occurred while decoding
the SSLServerKeyRingPassword property. Retype the password on the SSLServerKeyRingPassword
property and restart the program. Explanation: A java
runtime exception occurred while decoding the SSLServerKeyRingPassword property.
User Response: Retype the password on the SSLServerKeyRingPassword property
and restart the program.
JSAS0487E: A problem occurred
while decoding the keyRingPassword argument. Retype the keyring passwords
in the sas.client.props and sas.server.props and retry the operation. If
the problem persists, contact support for assistance. Explanation:
A java runtime exception occurred while decoding the keyRingPassword argument.
User Response: Retype the keyring passwords in the sas.client.props and
sas.server.props and retry the operation. If the problem persists, contact
support for assistance.
JSAS0010I: Credentials found, but
SecurityName & CredentialToken not set. Explanation: None.
User Response: None.
JSAS0020I: Credentials are not
the correct type for this security context. Explanation: None.
User Response: None.
JSAS0030I: No credentials found
on default credentials list. Explanation: None. User
Response: None.
JSAS0040I: Could not form valid connection
key. Explanation: None. User Response: None.
JSAS0050I: SSL Tag present in IOR, but not Security Tag. Explanation:
None. User Response: None.
JSAS0400I: The
configuration appears to be actively correct. Explanation: None.
User Response: None.
JSAS0401I: The configuration has
been initialized. Explanation: None. User Response:
None.
JSAS0402I: Security has been enabled.
Explanation: None. User Response: None.
JSAS0403I: The bootstrap repository file name has been set: Explanation:
None. User Response: None.
JSAS0404I: The
login source has been set: Explanation: None. User Response:
None.
JSAS0405I: The login userid has been set:
Explanation: None. User Response: None.
JSAS0406I: The login password has been set: Explanation: None.
User Response: None.
JSAS0407I: The keytab file name
has been set: Explanation: None. User Response: None.
JSAS0408I: The key file name has been set: Explanation: None.
User Response: None.
JSAS0409I: The principal has been
set: Explanation: None. User Response: None.
JSAS0410I: The principal was not set: Explanation: None.
User Response: None.
JSAS0411I: DCE client-association
has been enabled. Explanation: None. User Response:
None.
JSAS0412I: DCE server-association has been enabled.
Explanation: None. User Response: None.
JSAS0413I: SSL Type-I client-association has been enabled. Explanation:
None. User Response: None.
JSAS0414I: SSL
Type-I server-association has been enabled. Explanation: None.
User Response: None.
JSAS0415I: LTPA client-association
has been enabled. Explanation: None. User Response:
None.
JSAS0416I: LTPA server-association has been enabled.
Explanation: None. User Response: None.
JSAS0417I: Local operating system client-association has been enabled.
Explanation: None. User Response: None.
JSAS0418I: Local operating system server-association has been enabled.
Explanation: None. User Response: None.
JSAS0419I: The authentication target has been set: Explanation:
None. User Response: None.
JSAS0420I: The
SSL client keyring has been set: Explanation: None.
User Response: None.
JSAS0421I: The SSL client keyring
password has been set: Explanation: None. User Response:
None.
JSAS0422I: The SSL session timeout has been set:
Explanation: None. User Response: None.
JSAS0423I: The SSL credentials timeout has been set: Explanation:
None. User Response: None.
JSAS0425I: The
SSL port has been set: Explanation: None. User Response:
None.
JSAS0426I: The standard perform-QOP model has
been set: Explanation: None. User Response: None.
JSAS0427I: The perform client-authentication has been set: Explanation:
None. User Response: None.
JSAS0428I: The
perform server-authentication has been set: Explanation: None.
User Response: None.
JSAS0429I: The perform message
replay detection has been set: Explanation: None. User
Response: None.
JSAS0430I: The perform message out-of-sequence
detection has been set: Explanation: None. User Response:
None.
JSAS0431I: The perform message integrity has
been set: Explanation: None. User Response: None.
JSAS0432I: The perform message confidentiality has been set: Explanation:
None. User Response: None.
JSAS0433I: The
standard claim-QOP model has been set: Explanation: None.
User Response: None.
JSAS0434I: The claim client-authentication
required has been set: Explanation: None. User Response:
None.
JSAS0435I: The claim server-authentication required
has been set: Explanation: None. User Response: None.
JSAS0436I: The claim message replay detection required has been set:
Explanation: None. User Response: None.
JSAS0437I: The claim message out-of-sequence detection required has been set:
Explanation: None. User Response: None.
JSAS0438I: The claim message integrity required has been set:
Explanation: None. User Response: None.
JSAS0439I: The claim message confidentiality required has been set:
Explanation: None. User Response: None.
JSAS0440I: The claim client-authentication supported has been set:
Explanation: None. User Response: None.
JSAS0441I: The claim server-authentication supported has been set:
Explanation: None. User Response: None.
JSAS0442I: The claim message replay detection supported has been set:
Explanation: None. User Response: None.
JSAS0443I: The claim message out-of-sequence supported required has been set:
Explanation: None. User Response: None.
JSAS0444I: The claim message integrity supported has been set:
Explanation: None. User Response: None.
JSAS0445I: The claim message confidentiality supported has been set:
Explanation: None. User Response: None.
JSAS0446I: The delegation mode has been set: Explanation: None.
User Response: None.
JSAS0447I: The security service
will not be disabled during bootstrap activation. Explanation:
None. User Response: None.
JSAS0448I: The
security bootstrap repository port has been set: Explanation:
None. User Response: None.
JSAS0449I: The
configuration appears to be complete. Explanation: None.
User Response: None.
JSAS0450I: The configuration appears
to be consistent. Explanation: None. User Response:
None.
JSAS0451I: The configuration appears to be passively
correct. Explanation: None. User Response: None.
JSAS0452I: The SSL server keyring has been set: Explanation: None.
User Response: None.
JSAS0453I: The SSL server keyring
password has been set: Explanation: None. User Response:
None.
JSAS0454I: The indicated entry was not found
in the key file. Explanation: None. User Response:
None.
JSAS0455I: Unable to login principal: null authentication
information. Explanation: None. User Response: None.
JSAS0456I: Trying again to form a secure association with the target.
Explanation: None. User Response: None.
JSAS0457I: Could not close the security bootstrap repository.
Explanation: None. User Response: None.
JSAS0458I: BasicAuth credentials will not expire. Explanation:
None. User Response: None.
JSAS0459I: The
BasicAuth credentials expiration has been set: Explanation: None.
User Response: None.
JSAS0460I: Successfully loaded
configured key file: Explanation: None. User Response:
None.
JSAS0010W: Secure server association options
not enabled. Explanation: None. User Response: None.
JSAS0020W: Unable to get credentials. Verify the userid and password supplied
are correct. Try restarting the client program to resolve the problem.
Increasing the credential timeout value could reduce the likelihood of
this error occurring. If the problem persists, contact support for assistance.
Explanation: The credentials supplied are either invalid
or null. An attempt is made to login as unauthenticated. If the resource is
unprotected, the invocation should succeed. User Response: Verify
the userid and password supplied are correct. Try restarting the client
program to resolve the problem. Increasing the credential timeout value
could reduce the likelihood of this error occurring If the problem persists,
contact support for assistance.
JSAS0030W: Trying unauthenticated
login. Verify the userid and password supplied is correct. Try restarting
the client program to resolve the problem. Increasing the credential timeout
value could reduce the likelihood of this error occurring If the problem
persists, contact support for assistance. Explanation: The
credentials supplied are either invalid or null. An attempt is made to login
as unauthenticated. If the resource is unprotected, the invocation should
succeed. User Response: Verify the userid and password supplied
is correct. Try restarting the client program to resolve the problem. Increasing
the credential timeout value could reduce the likelihood of this error
occurring If the problem persists, contact support for assistance.
JSAS0040W: No ConnectionData object attached to RequestHolder. Verify the
classpath on the client and server both contain the same UJC.JAR and the same
SAS e-fixes. If the problem persists, contact support for assistance.
Explanation: The type of connection data object is not valid. There may
be a problem with the classes which loaded from the classpath. User
Response: Verify the classpath on the client and server both contain the
same UJC.JAR and the same SAS e-fixes. If the problem persists, contact support
for assistance.
JSAS0050W: No security service context
found on RequestHolder service context list. Typically no action required.
Explanation: The service context list did not have a security
context. Typically this situation results because the transport was TCP/IP
instead of SSL. User Response: Typically no action required.
JSAS0060W: No security service context found in message. Typically no action
is required. Explanation: This indicates that a security
context was not sent from the client along with the message. Typically
this situation occurs when a TCPIP connection was made. User
Response: Typically no action is required.
JSAS0070W:
Session entry already exists. Try to login again. If the error persists, contact
support for assistance. Explanation: This message indicates
that an added session is trying to be added again. User Response:
Try to login again. If the error persists, contact support for assistance.
JSAS0080W: Security Tag not found in IOR. Explanation: None.
User Response: None.
JSAS0090W: SSL Tag not found in
IOR. Explanation: None. User Response: None.
JSAS0100W: Null Credentials list. If an unauthenticated request is not desired,
check the client login userid and password to verify correctness. Review the
login source property in the sas.client.props. If the problem persists, contact
support for assistance. Explanation: The credentials list passed
into init_security_context are null. An unauthenticated request will be attempted.
User Response: If an unauthenticated request is not desired, check the
client login userid and password to verify correctness. Review the login source
property in the sas.client.props. If the problem persists, contact support
for assistance.
JSAS0110W: No service context list found
on RequestHolder. Typically no action required. Explanation:
The service context list did not have a security context. Typically
this situation results because the transport was TCP/IP instead of SSL.
User Response: Typically no action required.
JSAS0120W:
Security enabled, but EstablishTrustInClient is not set in IOR. If mutual
authentication is desired, check the standardPerformQOPModels property so
that it is set to authenticity, integrity, or confidentiality.
Explanation: The standardPerformQOPModels property in the sas.client.props
may not be set for mutual authentication. User Response: If mutual
authentication is desired, check the standardPerformQOPModels property so
that it is set to authenticity, integrity, or confidentiality.
JSAS0401W: Unable to get Current. Check to ensure the correct Java class files
are in the program classpath. Make sure you are not using the wrong version
of UJC.JAR. If you still have problems after reviewing your setup, contact
support for assistance. Explanation: This message indicates
an internal error occurred while trying to access Current via resolve_initial_references.
User Response: Check to ensure the correct Java class files are in
the program classpath. Make sure you are not using the wrong version of UJC.JAR.
If you still have problems after reviewing your setup, contact support for
assistance.
JSAS0402W: No security context associated with
request. Typically no action required. Explanation: The
request did not have an associated security context. Typically this situation
results because the transport was TCP/IP instead of SSL. User
Response: Typically no action required.
JSAS0403W:
DCE Security Tag not found in IOR. Verify that the client program is attempting
the access the correct object. This message could be benign if the object
method does not require security to be invoked. Explanation: The
IOR does not contain a DCE security tag. This tag contains the target security
name, mechanism and required quality of protection (QOP). User Response:
Verify that the client program is attempting to access the correct
object. This message could be benign if the object method does not require
security to be invoked.
JSAS0404W: SSL Security Tag not
found in IOR. Verify that the client program is attempting the access the
correct object. This message could be benign if the object method does not
require security to be invoked. Explanation: The IOR does not
contain an SSL security tag. This tag contains the port, required quality
of protection (QOP) and supported QOP. User Response: Verify that
the client program is attempting the access the correct object. This message
could be benign if the object method does not require security to be invoked.
JSAS0405W: Unable to get client security name from credentials. Restart the
client so that new credentials will be created. Check with your user registry
administrator to ensure the user data is valid. If the problem persists, contact
support for assistance. Explanation: This message indicates
that the attributes stored in the credential cannot be retrieved due to
a java runtime exception. User Response: Restart the client
so that new credentials will be created. Check with your user registry administrator
to ensure the user data is valid. If the problem persists, contact support
for assistance.
JSPG0002E: The JSP engine is not configured with a scratch directory
Explanation: The JSP engine must have a scratch directory in which it
can compile the generated servlets. User Response: The scratch
directory is not user-definable. It is defined by the servlet engine.
Contact service. JSPG0003E: The scratch directory you
specified: {0} is unusable. Explanation: The specified scratch
directory must be read/write, and must be a directory, not a file.
User Response: Verify that the specified scratch directory meets these
criteria.
JSPG0004I: The scratch directory for the JSP
engine is: {0}. Explanation: The scratch directory is displayed
for informational purposes. User Response: No user response required.
JSPG0005I: Parent class loader is: {0}. Explanation: The parent
class loader is displayed for informational purposes. User Response:
No user response required.
JSPG0006I: IMPORTANT: Do
not modify the generated servlets. Explanation: The servlet
class files that are compiled from the JSP files should not be modified.
User Response: No user response required.
JSPG0007E:
Internal error: Comments were not implemented Explanation: The
JSP engine does not handle comments. User Response: Implement handleComment().
JSPG0008E: Internal error: Directives were not implemented Explanation:
The JSP engine does not handle directives. User Response: Implement
handleDirective().
JSPG0009E: Internal error: Declarations
were not implemented Explanation: The JSP engine does not handle
declarations. User Response: Implement handleDeclaration().
JSPG0010E: Internal error: Expressions were not implemented Explanation:
The JSP engine does not handle expressions. User Response: Implement
handleExpression().
JSPG0011E: Internal error: Scriptlets
were not implemented Explanation: The JSP engine does not handle
scriptlets. User Response: Implement handleScriptlet().
JSPG0012E: Internal error: useBean was not implemented Explanation:
The JSP engine does not handle the <jsp:useBean> tag. User Response:
Implement handleBean() and handleBeanEnd().
JSPG0013E:
Internal error: getProperty was not implemented Explanation: The
JSP engine does not handle the <jsp:getProperty> tag. User Response:
Implement handleGetProperty().
JSPG0014E: Internal
error: setProperty was not implemented Explanation: The JSP
engine does not handle the <jsp:setProperty> tag. User Response:
Implement handleSetProperty().
JSPG0015E: Internal
error: Plug-in was not implemented Explanation: The JSP engine
does not handle the <jsp:plugin> tag. User Response: Implement
handlePlug-in().
JSPG0016E: Internal error: Forward was
not implemented Explanation: The JSP engine does not handle
the <jsp:forward> tag. User Response: Implement handleForward().
JSPG0017E: Internal error: Include was not implemented Explanation:
The JSP engine does not handle the <jsp:include> tag. User Response:
Implement handleInclude().
JSPG0018E: useBean: ID attribute
is missing Explanation: In the <jsp:useBean> tag, the "id="
attribute could not be found. User Response: Add the "id=" attribute
to the <jsp:useBean> tag, to specify a name for the bean.
JSPG0019E: useBean ({0}): Either class or type attribute must be specified
Explanation: In the <jsp:useBean> tag, either the "class="
or "type=" attribute must be specified. User Response: Add the
"class=" or "type=" attribute to the <jsp:useBean> tag, to identify the
class or package of the bean.
JSPG0020E: useBean: Duplicate
bean name: {0}. Explanation: A bean of this name already exists
on the JSP page. User Response: Give this bean a unique name, using
the "id=" attribute of the <jsp:useBean> tag.
JSPG0021E:
Can't use as session bean {0} since it is prohibited by the JSP directive
defined earlier. Explanation: In the page directive for the
JSP page, the session attribute is "false" indicating no session support is
required. User Response: Change the session attribute of the page
directive to "true", or change the scope of the bean to "page", "request",
or "application".
JSPG0022E: useBean: Can't specify both the
class and beanName attribute Explanation: In the <jsp:useBean>
tag, either the "class" or "beanName" attribute can be used, but not both.
User Response: Use one or the other attribute.
JSPG0024E:
Invalid scope ({1}) in useBean: ({0}). Explanation: In the <jsp:useBean>
tag, the scope attribute must have one of the following values: "page", "request",
"session", or "application". User Response: Set the scope attribute
to one of the valid values.
JSPG0025E: Can't determine
the classname from the .class file Explanation: Expecting
to be able to get the class name from the class file. The class file might
be corrupt. User Response: Delete the scratch directory and try
the request again. If error persists, contact service.
JSPG0026W: Warning: Bad type in .class file Explanation: The
12 valid types are: Class, Field Reference, Method Reference, Interface Method
Reference, Name and Type, String, Integer, Float, Long, Double, ASCIZ, and
Unicode. User Response: No user response required.
JSPG0027E: Error while writing data file Explanation: The JSP
engine was unable to write the data file (.DAT) to the scratch directory.
User Response: Make sure the scratch directory is valid and the disk is
not full. If error persists, contact service.
JSPG0028E:
Page directive: Can't have multiple occurrences of contentType
Explanation: In the Page directive, only one contentType attribute is
allowed. User Response: Edit the Page directive so that there is
only one contentType attribute.
JSPG0029E: Page directive:
Invalid value for contentType Explanation: In the Page directive,
there is no value given for the contentType attribute. User Response:
Be sure a valid MIME type is given for the contentType attribute. The
most common values are "text/html" (which is the default), "text/xml" and
"text/plain".
JSPG0030E: Page directive: Can't have multiple
occurrences of a session Explanation: In the Page directive,
only one session attribute is allowed. User Response: Edit the
Page directive so that there is only one session attribute.
JSPG0031E: Page directive: Invalid value for a session Explanation:
In the Page directive, an invalid value was found for the session attribute.
User Response: Make sure the value of the session attribute is either
"true" or "false".
JSPG0032E: Page directive: Can't have
multiple occurrences of a buffer. Explanation: In the Page
directive, only one buffer attribute is allowed. User Response: Edit
the Page directive so that there is only one buffer attribute.
JSPG0033E: Page directive: Invalid value for a buffer Explanation:
In the Page directive, an invalid value is given for the buffer attribute.
User Response: Make sure the value of the buffer attribute is either "none",
or "sizekb" where size is an integer indicating the buffer size
in kilobytes. JSPG0034E: Page directive: Can't have multiple
occurrences of autoFlush. Explanation: In the Page directive,
only one autoFlush attribute is allowed. User Response: Edit the
Page directive so that there is only one autoFlush attribute.
JSPG0035E: Page directive: Invalid value for autoFlush Explanation:
In the Page directive, an invalid value was found for the autoFlush attribute.
User Response: Make sure the value of the autoFlush attribute is either
"true" or "false".
JSPG0036E: Page directive: Can't have
multiple occurrences of isThreadSafe. Explanation: In the Page
directive, only one isThreadSafe attribute is allowed. User Response:
Edit the Page directive so that there is only one isThreadSafe attribute.
JSPG0037E: Page directive: Invalid value for isThreadSafe Explanation:
In the Page directive, an invalid value was found for the isThreadSafe
attribute. User Response: Make sure the value of the isThreadSafe
attribute is either "true" or "false".
JSPG0038E: Page
directive: Can't have multiple occurrences of information Explanation:
In the Page directive, only one information attribute is allowed.
User Response: Edit the Page directive so that there is only one information
attribute.
JSPG0039E: Page directive: Invalid value for
information Explanation: In the Page directive, there is no
value given for the information attribute. User Response: Make
sure a text string value is given for the information attribute.
JSPG0040E: Page directive: Can't have multiple occurrences the of isErrorPage
Explanation: In the Page directive, only one isErrorPage attribute
is allowed. User Response: Edit the Page directive so that there
is only one isErrorPage attribute.
JSPG0041E: Page directive:
Invalid value for the isErrorPage Explanation: In the Page
directive, an invalid value was found for the isErrorPage attribute.
User Response: Make sure the value of the isErrorPage attribute is either
"true" or "false".
JSPG0042E: Page directive: Can't have
multiple occurrences of the errorPage Explanation: In the Page
directive, only one errorPage attribute is allowed. User Response:
Edit the Page directive so that there is only one errorPage attribute.
JSPG0043E: Page directive: Can't have multiple occurrences of a language
Explanation: In the Page directive, only one language attribute is allowed.
User Response: Edit the Page directive so that there is only one language
attribute.
JSPG0046E: Page directive: Can't have multiple
occurrences of an extends attribute Explanation: In the Page
directive, only one extends attribute is allowed. User Response: Edit
the Page directive so that there is only one extends attribute.
JSPG0047E: Page directive: Illegal combination of buffer="none" && autoFlush="false"
Explanation: In the Page directive, it is illegal to set the
autoFlush attribute to "false" when the buffer attribute is set to "none"
or "0". User Response: Edit the Page directive to correct this
situation.
JSPG0048E: Internal error: Tag extensions were
not implemented Explanation: The JSP engine does not handle
tag extensions. User Response: Implement handleTagBegin() and handleTagEnd().
JSPG0049E: Missing file argument to include Explanation: In
the <%@ include ... %> directive, there is no pathname given for the file
attribute. User Response: Edit the file attribute and add a valid
path name to the file to be included: <%@ include file="
relativeURL" %>
JSPG0050E: Bad file argument
to include Explanation: None. User Response: None.
JSPG0051I: Jasper JSP 1.1 Engine Explanation: The JSP Engine
level is displayed for informational purposes. User Response: No
user action is required.
JSPG0052E: Stream closed
Explanation: The output stream was unexpectedly closed. User Response:
Restart server, if problem persists then contact service
JSPG0053E: Invalid forward tag Explanation: In the <jsp:forward
> tag, the required page attribute is missing. User Response: Edit
the <jsp:forward> tag and add the page attribute pointing to a string or
an expression representing the relative URL of the file to which you are forwarding
the request.
JSPG0054E: Unhandled error! You might want
to consider having an error page to report such errors more gracefully.
Explanation: An unknown exception was thrown. User Response: None.
JSPG0055E: Invalid directive Explanation: An invalid directive
was found while parsing the JSP page. The valid directives are "page",
"include" and "taglib". User Response: Correct or remove the directive.
JSPG0056E: Unterminated {0} tag Explanation: The open tag,
displayed above, is not closed. User Response: Close the tag with
the appropriate closing tag.
JSPG0057E: useBean tag must
begin and end in the same physical file Explanation: The useBean
tag must begin and end in the same physical file. User Response: Close
the useBean tag in the physical file in which the tag was opened.
JSPG0058E: Unable to load class {0} Explanation: The class
named above could not be loaded. User Response: Restart server,
if problem persists, contact service.
JSPG0059E: Unable
to compile class for JSP Explanation: None. User Response:
None.
JSPG0060E: Unable to compile class for JSP
Explanation: None. User Response: None.
JSPG0061E: Unable to rename class file {0} to {1} Explanation:
None. User Response: None.
JSPG0062E: {0}:
Mandatory attribute {1} missing Explanation: The attribute
is required for this tag. User Response: Add this attribute to
the tag.
JSPG0063E: {0}: Invalid attribute, {1}
Explanation: The attribute is not valid for this tag. User Response:
Remove the attribute or correct the attribute name.
JSPG0065E: Cannot read file: {0} Explanation: The file exists
but cannot be read. The reason is unknown. User Response: Restart
server, if problem persists, contact service.
JSPG0066E:
Have seen file {0} already, maybe this is a recursive include?!
Explanation: None. User Response: None.
JSPG0067E: Unterminated quotes Explanation: None. User
Response: None.
JSPG0068E: Attribute value should be
quoted Explanation: None. User Response: None.
JSPG0069E: Attribute {0} has no value Explanation: None.
User Response: None.
JSPG0070E: Unterminated tag attribute
list Explanation: None. User Response: None.
JSPG0071E: No name in the Param tag Explanation: None.
User Response: None.
JSPG0072E: No value in the Param
tag Explanation: None. User Response: None.
JSPG0073E: Attempted a bean operation on a null object Explanation:
None. User Response: None.
JSPG0074E: No
BeanInfo for the bean of type ''{0}'' could be found, the class likely does
not exist. Explanation: None. User Response: None.
JSPG0075E: An exception occurred while introspecting the read method of the
property ''{0}'' in a bean of type ''{1}'': {2} Explanation: None.
User Response: None.
JSPG0076E: Cannot find a method
to read the property ''{0}'' in a bean of type ''{1}'' Explanation:
None. User Response: None.
JSPG0077E: Cannot
find a method to write the property ''{0}'' in a bean of type ''{1}''
Explanation: None. User Response: None.
JSPG0078E: Cannot find any information on the property ''{0}'' in a bean of
type ''{1}'' Explanation: None. User Response: None.
JSPG0079E: Cannot set indexed property Explanation: None.
User Response: None.
JSPG0080E: Invalid JSP: Include
tag Explanation: None. User Response: None.
JSPG0081E:JSP: Include needs to have "flush=true" Explanation:
None. User Response: None.
JSPG0082E: JSP:
Include page="..." flush="true" is the only valid combination in JSP 1.1
Explanation: None. User Response: None.
JSPG0083E: Error: Attempt to clear a buffer that's already been flushed
Explanation: None. User Response: None.
JSPG0084E: Error: JSP buffer overflow Explanation: None.
User Response: None.
JSPG0085E: Expected "param" tag
with "name" and "value" attributes after the "params" tag. Explanation:
None. User Response: None.
JSPG0086E: Param
tag needs to be closed with "/>" Explanation: None.
User Response: None.
JSPG0087E: Param tag needs to
be closed with /params Explanation: None. User Response:
None.
JSPG0088E: Type not declared in JSP: Plug-in
Explanation: None. User Response: None.
JSPG0089E: Code not declared in JSP: Plug-in Explanation: None.
User Response: None.
JSPG0090E: JSP: Plug-in not closed
Explanation: None. User Response: None.
JSPG0091E: Illegal to clear() when the buffer size = 0 Explanation:
None. User Response: None.
JSPG0092E: setProperty:
Bean {0} not found Explanation: None. User Response:
None.
JSPG0093E: getProperty: Bean {0} not found
Explanation: None. User Response: None.
JSPG0094E: setProperty: Class {0} not found Explanation: None.
User Response: None.
JSPG0095E: setProperty: Can't
have a non-null value when property=* Explanation: None.
User Response: None.
JSPG0096E: setproperty: BeanInformation
for bean {0} was not found Explanation: None. User Response:
None.
JSPG0097E: setProperty: Either the param or value
can be present Explanation: None. User Response: None.
JSPG0098E: setProperty: Can't set array property {0} through a string constant
value Explanation: None. User Response: None.
JSPG0099W: Warning: Invalid value for the initParam keep generated. Will
use the default value of "false" Explanation: None.
User Response: None.
JSPG0100W: Warning: Invalid value
for the initParam largeFile. Will use the default value of "true"
Explanation: None. User Response: None.
JSPG0101W: Warning: Invalid value for the initParam mappedFile. Will use the
default value of "false" Explanation: None. User Response:
None.
JSPG0102W: Warning: Invalid value for the initParam
sendErrorToClient. Will use the default value of "false" Explanation:
None. User Response: None.
JSPG0103E: Unable
to open tag library {0} : {1} Explanation: None. User
Response: None.
JSPG0104E: Cannot create a reader when
the stream is not buffered Explanation: None. User Response:
None.
JSPG0105W: Warning: Unknown element {0} in TLD
Explanation: None. User Response: None.
JSPG0106W: Warning: Unknown element {0} in the tag Explanation:
None. User Response: None.
JSPG0107W: Warning:
Unknown element {0} in the attribute Explanation: None.
User Response: None.
JSPG0108E: More than one tag library
is in the TLD Explanation: None. User Response: None.
JSPG0109W: Could not load TagExtraInformation class {0}: {1} Explanation:
None. User Response: None.
JSPG0110E: Parse
Error in the tag library descriptor: {0} Explanation: None.
User Response: None.
JSPG0111E: Unable to open the
tag library descriptor: {0} Explanation: None. User
Response: None.
JSPG0112E: Buffer size <= 0
Explanation: None. User Response: None.
JSPG0113E: JSP file "{0}" not found Explanation: None.
User Response: None.
JSPG0114I: Copying {0} into {1}
Explanation: None. User Response: No user response
required.
JSPG0115I: Stripping comment: {0}
Explanation: None. User Response: No user response required.
JSPG0116I: Handling directive: {0} {1} Explanation: None.
User Response: No user response required.
JSPG0117I:
Plug-in: {0} Explanation: None. User Response: No
user response required.
JSPG0118I: Package name is: {0}
Explanation: The package name is displayed for informational
purposes. User Response: No user response required.
JSPG0119I: Class name is: {0} Explanation: The class name is
displayed for informational purposes. User Response: No user response
required.
JSPG0120I: Java file name is: {0}
Explanation: The java file name is displayed for informational purposes.
User Response: No user response required.
JSPG0121I:
Class file name is: {0} Explanation: The class file name is
displayed for informational purposes. User Response: No user response
required.
JSPG0122I: Accepted {0} at {1} Explanation:
None. User Response: No user response required.
JSPG0123I: Adding jar {0} to my classpath Explanation: None.
User Response: No user response required.
JSPG0124I:
Compiling with: {0} Explanation: None. User Response:
No user response required.
JSPG0125E: According to
the TLD attribute {0} is mandatory for the tag {1} Explanation:
None. User Response: None.
JSPG0126E: Attribute
{0} invalid according to the specified TLD Explanation: None.
User Response: None.
JSPG0127E: Could not locate TLD
{0} Explanation: None. User Response: None.
JSPG0128E: Could not locate web.xml Explanation: None.
User Response: None.
JSPG0129E: Usage: jsptoservlet
[-o <path/to/outputDirectory>] [-keepgenerated] <.jsp files>.
Explanation: None. User Response: None.
JSPG0130I: Classpath {0} is: {1} Explanation: The classpath
is displayed for informational purposes. User Response: No user
response required.
JSPG0131E: Unable to load tag handler
class {0} because of {1} Explanation: None. User Response:
None.
JSPG0132E: Unable to find setter method for
attribute: {0} Explanation: None. User Response: None.
JSPG0133E: Unable to introspect on tag handler class: {0} because of {1}
Explanation: None. User Response: None.
JSPG0134E: Attributes are invalid according to tag information
Explanation: None. User Response: None.
JSPG0135E: No such tag {0} in the tag library imported with prefix {1}.
Explanation: None. User Response: None.
JSPG0136W: Can't create an instance of specified compiler plug-in class {0}
due to {1}. Will default to Sun Java Compiler Explanation: None.
User Response: None.
JSPG0137W: Specified compiler
plug-in class {0} not found. Will default to Sun Java Compiler
Explanation: None. User Response: None.
JSPG0138W: Specified compiler path {0} not found. Will default to system path
Explanation: None. User Response: None.
JSPG0139E: The -uriroot option must specify a pre-existing directory
Explanation: None. User Response: None.
JSPG0140I: uriRoot implicitly set to "{0}" Explanation: None.
User Response: No user response required.
JSPG0141E:
Usage: jspc <options> [--] <jsp files> where JSP files is
any number of: <file> A
file to be parsed as a JSP page -webapp <dir> A
directory containing a web application, all JSP pages will
recursivly be parsed where options include: -q Quiet
mode (same as -v0) -v[#] Verbose
mode (optional number is level, default is 2) -d <dir> Output
Directory -dd <dir> Literal
Output Directory. (package directories will not be made)
-p <name> Name of target package
-c <name> Name of target class name
(only
applies to first JSP page) -mapped Generate
separate write() calls for each HTML line in the JSP -die[#] Generate
an error return code (#) on fatal errors If
the number is absent or unparsable it defaults to 1. -uribase <dir> The
uri directory compilations should be relative to (Default
is "/") -uriroot <dir> The root directory
that the uri files should be resolved against,
(Default is the directory jspc is invoked from) -webinc <file> Creates
partial servlet mappings for the -webapp option -webxml <file> Creates
a complete web.xml when using the -webapp option -ieplugin <clsid> Java
Plug-in class ID for Internet Explorer Explanation: This
is the correct usage for JSPC. User Response:
<! MSGSTART --> LTXT0001I: Extracting files from: Explanation:
None. User Response: None. <! MSGEND --> <! MSGSTART
--> LTXT0002I: Parsing ejb-jar.xml file.
Explanation: None. User Response: None. <!
MSGEND --> <! MSGSTART --> LTXT0003I:
Parsing ibm-ejb-jar-bnd.xmi file. Explanation: None.
User Response: None. <! MSGEND --> <! MSGSTART --> LTXT0004I: Preparing jar for deployment.
Explanation: None. User Response: None. <! MSGEND
--> <! MSGSTART --> LTXT0005I: Executing
command: Explanation: None. User Response: None.
<! MSGEND --> <! MSGSTART -->
LTXT0006I: Final prep of jar file. Explanation: None.
User Response: None. <! MSGEND --> <! MSGSTART --> LTXT0007I: Creating jar file: Explanation:
None. User Response: None. <! MSGEND --> <! MSGSTART
--> LTXT0015E: Input jar file does not
exist. Explanation: None. User Response: None.
<! MSGEND --> <! MSGSTART -->
LTXT0016E: Output jar file already exists, recreating. Explanation:
None. User Response: None. <! MSGEND --> <! MSGSTART
--> LTXT0017E: Unable to remove existing
file: Explanation: None. User Response: None. <!
MSGEND --> <! MSGSTART --> LTXT0018E:
LocalizableText jar file 'ltext.jar' does not exist. Explanation:
None. User Response: None. <! MSGEND --> <! MSGSTART
--> LTXT0019E: All three files were
not extracted from the ltext.jar. Explanation: None.
User Response: None. <! MSGEND --> <! MSGSTART --> LTXT0025E: [ {0} ] ! Serializable Explanation:
None. User Response: None. <! MSGEND --> <! MSGSTART
--> LTXT0101E: LocalizableText.properties
An IOException was thrown while writing the Object[] to the byte[].
Explanation: None. User Response: None. <! MSGEND
--> <! MSGSTART --> LTXT0102E: LocalizableText.properties
Unable to perform the format method on the LocalizableTextFormatter because
of a remote exception. Explanation: None. User Response:
None. <! MSGEND --> <! MSGSTART -->
LTXT0103E: LocalizableText.properties LocalizableTextFormatter.toString error.
Unable to load the arguments from the argument array. Explanation:
None. User Response: None. <! MSGEND --> <! MSGSTART
--> LTXT0104E: LocalizableText.properties
Either the pattern key or the resource bundle name is not set in the LocalizableTextFormatter
object before formatting. Explanation: None. User Response:
None.
MIGR0001I: java com.ibm.websphere.migration.WASPreUpgrade
<backupDirectoryName> <currentWebSphereDirectory> <administrationNodeName> [-nameServiceHost <host
name> [ -nameServicePort <port number> ]] [-traceString <trace spec>
[-traceFile <file name>]]} Explanation: This describes the syntax
of the WASPreUpgrade command. This command is used to save the environment
and the necessary files of an existing Release 3.02 or 3.5 WebSphere environment.
The results of this command are stored in a backup directory. This backup
directory can be used with the WASPostUpgrade command to restore the previously
saved environment into a Release 4.0 WebSphere configuration. The first three
parameters of the command are required positioned parameters. The others are
optional.
- <backupDirectoryName> - This is the name of the directory to store
the saved configuration and files. The directory will be created if it does
not already exist. This is a required parameter.
- <currentWebSphereDirectory> - This is the directory name of the currently
installed Release 3.02 or 3.5 WebSphere product. This directory can be either
a Standard or Advanced Edition WebSphere installation. This is a required
parameter.
- <administrationNodeName> - This is the administration node name of
the currently installed WebSphere product. XMLConfig will be called using
this parameter. The WebSphere Administration server will need to be running
for this command to execute successfully. This is a required parameter.
- [-nameServiceHost <host name> [ -nameServicePort <port number> ]]
- These are optional parameters and will be passed to the call to XMLConfig
if it is specified. They can be used to override the default host name and
port number used by XMLConfig.
- [-traceString <trace spec> [-traceFile <file name>]]}- These are
optional parameters and are used to gather trace information for use by IBM
Service personnel. The -traceString parameter value is "*=all=enabled" and
must be specified with quotes to be processed correctly.
User Response: None. MIGR0002I: java com.ibm.websphere.migration.WASPostUpgrade
<backupDirectoryName> [-import <xml data file>]
[-adminNodeName <primary node name>] [-nameServiceHost <host
name> [ -nameServicePort <port number>]] [-traceString <trace
spec> [-traceFile <file name>]] [-substitute <"key1=value1[;key2=value2;[...]]">]}
Explanation: This describes the syntax of the WASPostUpgrade
command. This command is used to restore the environment and necessary files
from an existing Release 3.02 or 3.5 WebSphere environment that was previously
created using the WASPreUpgrade command. The results of this command is an
updated WebSphere Release 4.0 configuration. The first parameter of the command
is required. The others are optional.
- <backupDirectoryName> - This is the name of the directory that has
the saved configuration and files that was created by the WASPreUpgrade command.
This is a required parameter.
- [-import <xml data file>] - This is an optional parameter that
can be used to specify an xml data file that was created using either a Release
3.02 or 3.5 version of XMLConfig. The default xml configuration file (websphere_3x_backup.xml)
in the backupDirectoryName will be used if this parameter is not specified.
- [-adminNodeName <primary node name>] - This is the administration node
name of the currently installed WebSphere product. This parameter is required
if the configuration will be restored on a WebSphere Application Server Advanced
Edition, Version 4.0.x environment. XMLConfig will be called using this parameter.
The WebSphere Administration server will need to be running for this command
to execute successfully.
- [-nameServiceHost <host name> [ -nameServicePort <port number> ]]
- These are optional parameters and will be passed to the call to XMLConfig
if it is specified. They can be used to override the default host name and
port number used by XMLConfig. These parameters will only be used if
the configuration will be restored on a WebSphere Application Server, Advanced
Edtion, Version 4.0.x.
- [-traceString <trace spec> [-traceFile <file name>]]}- These are
optional parameters and are used to gather trace information for use by IBM
Service personnel. The -traceString parameter value is "*=all=enabled" and
must be specified with quotes to be processed correctly.
- [-substitute <"key1=value1[;key2=value2;[...]]">]} - These are optional
parameters and will be passed to the call to XMLConfig if it is specified. They
are used for substitution of security values in the xml data file. In input
xml file, the key(s) should appear as $key$ for substitution.
User Response: None. MIGR0101W: Unable to create
trace log using file {0}. Explanation: The command that was
executed was passed -traceString and -traceFile parameters for tracing the
command's execution. The parameter specified for the -traceFile parameter
was used to try and create a file to store the resulting trace data. That
file could not be created, trace will not be gathered during execution of
the command. User Response: Specify a different value for the -traceFile
parameter that can be successfully created and used to store trace data and
try the command again.
MIGR0102E: Invalid Command Line.
Explanation: An invalid command line was specified when one
of the migration commands as specified. This message will be accompanied by
a more specific message that describes the specific problem. User Response:
Correct the error and execute the command again using the correct parameters.
MIGR0103E: You must specify the backup directory name. Explanation:
The required parameter for the backup directory was not specified. See
the command syntax for more information on the correct command line parameters.
User Response: Correct the error and execute the command again using the
correct parameters.
MIGR0104E: You must specify the currently
installed WebSphere directory name. Explanation: The required
parameter for the currently installed WebSphere directory name was not specified.
See the WASPreUpgrade command syntax for more information on the correct command
line parameters. User Response: Correct the error and execute the
command again using the correct parameters.
MIGR0105E:
You must specify the primary node name. Explanation: The required
parameter for the administration node name was not specified. See the WASPreUpgrade
command syntax for more information on the correct command line parameters.
User Response: Correct the error and execute the command again using the
correct parameters.
MIGR0106E: Illegal argument {0} specified.
Explanation: An argument was specified on a command lime invocation
that is not supported. See the command syntax for more information on the
correct command line parameters User Response: Correct the error
and execute the command again using the correct parameters.
MIGR0107E: There must be an even number of optional parameters.
Explanation: An odd number of optional parameters were specified when
executing one of the migration commands. Since optional parameters specify
a 'name' and 'value' combination this is an illegal command line. See the
command syntax for more information on the correct command line parameters.
User Response: Correct the error and execute the command again using the
correct parameters.
MIGR0108E: The specified WebSphere
directory does not contain WebSphere version that can be upgraded.
Explanation: The value specified as the currentWASDirectory on the WASPreUpgrade
command does not point to a directory that contains a WebSphere release that
can be migrated. This could occur for several reasons. One of the reasons
might be that the specified directory does not contain a valid WebSphere installed
directory. Another reason can be that the specified directory does contain
a valid WebSphere installed directory but it is not a supported release. Any
release and fix level from Release 3.02 through 3.5 is supported.
User Response: Correct the error and execute the command again using the
correct parameters.
MIGR0110E: The currently installed
version of WebSphere is not supported by this command. Explanation:
The value specified as the currentWASDirectory on the WASPreUpgrade command
does not point to a directory that contains a WebSphere release that can be
migrated. The reason is that the specified directory does contain a
valid WebSphere installed directory but it is not a supported release. Any
release and fix level from Release 3.02 through 3.5 is supported.
User Response: Correct the error and execute the command again using the
correct parameters.
MIGR0111E: The specified backup directory
cannot be used because it is a file. Explanation: The required
parameter for the backup directory specified an existing file instead of a
directory name. See the command syntax for more information on the correct
command line parameters. User Response: Correct the error and execute
the command again using the correct parameters.
MIGR0112E:
The specified backup directory cannot be used because it is not write able.
Explanation: The required parameter for the backup directory
specified a directory that is read-only. See the command syntax for more information
on the correct command line parameters. User Response: Correct
the error and execute the command again using the correct parameters.
MIGR0113E: The specified backup directory cannot be used because it cannot
be created. Explanation: The required parameter for the backup
directory specified a directory name that could not be used to create a directory.
See the command syntax for more information on the correct command line parameters.
User Response: Correct the error and execute the command again using the
correct parameters.
MIGR0114E: The setupCmdLine setting
{0} cannot be found. Explanation: The migration commands need
to read the setupCmdLine command file in the installed WebSphere environment
in order to execute. The required settings could not be found in the command
file. User Response: If the WASPreUpgrade command was specified
than the directory specified for the current WebSphere directory may be incorrect.
If a valid directory name has been specified or the WASPostUpgrade was specified
then the contents of the setupCmdLine file is not valid. Correct the error
and execute the command again. Contact IBM Service Personnel if the problem
cannot be resolved.
MIGR0115E: Unable to execute: {0}.
Explanation: The migration command unsuccessfully called another
program to perform a task. This call could not be completed. User Response:
This is an error, contact IBM Service personnel for further information.
MIGR0116E: The backup directory does not contain the required xml data file
{0}. Explanation: When executing the WASPostUpgrade command,
if the -import parameter was not specified, the default xml data file that
was created when the WASPreUpgrade command was executed cannot be found. This
may be due to an incorrect value for the backup directory name. If the -import
parameter was specified then an invalid value may have been specified.
User Response: Correct the error and execute the command again using the
correct parameters.
MIGR0117E: The specified WebSphere
directory does not contain a valid product file {0}. Explanation:
When executing the WASPreUpgrade command a valid product definition file
could not be found in the properties/com/ibm/websphere directory. This may
be due to an incorrect value specified for the current WebSphere directory
name. User Response: Correct the error and execute the command
again. Contact IBM Service Personnel if the problem cannot be resolved.
MIGR0118E: The WebSphere directory does not contain a readable product file
{0}. Explanation: When executing the WASPreUpgrade command
a valid product definition file could not be found in the properties/com/ibm/websphere
directory. This may be due to an incorrect value specified for the current
WebSphere directory name. User Response: Correct the error and
execute the command again. Contact IBM Service Personnel if the problem cannot
be resolved.
MIGR0119E: The XML file {0} used for import
is not valid. Explanation: When executing the WASPostUpgrade
command, if the -import parameter as not specified, the xml data file that
was created when the WASPreUpgrade command was executed cannot be used. This
may be due to an incorrect value for the backup directory name. If the -import
parameter was specified then an invalid value may have been specified. The
xml data file does not contain data in the format that was generated by an
invocation of Release 3.02 or 3.5 version of XMLConfig. User Response:
Correct the error and execute the command again using the correct parameters.
MIGR0120E: The DTD file {0} does not exist. Explanation: When
executing the WASPostUpgrade command a DTD file is required to read an xml
data file that was created on a Release 3.02 or 3.5 system. This file cannot
be found. User Response: This is an error, contact IBM Service
personnel for further information.
MIGR0121E: Unable to
read import XML document {0}. Explanation: When executing the
WASPostUpgrade command, if the -import parameter as not specified, the xml
data file that was created when the WASPreUpgrade command was executed cannot
be used. This may be due to an incorrect value for the backup directory name.
If the -import parameter was specified then an invalid value may have been
specified. User Response: Correct the error and execute the command
again using the correct parameters.
MIGR0122E: Unable to
read configuration file {0}. Explanation: When executing the
WASPostUpgrade command the specified configuration file could not be read.
This is a required configuration file in order for the WebSphere Application
Server, Advanced Edition, Version 4.0.x environment. User Response:
This is an error, contact IBM Service personnel for further information.
MIGR0123E: Failure while importing object {0} of type {1}, exception {2}.
Explanation: When executing the WASPostUpgrade command an
error occurred while trying to map the specified object into the WebSphere
Application Server, Advanced Edition, Version 4.0.x environment. The specific
reason can be determined by the exception information. Failure of this object
will prevent the this object and any of the objects it contains from being
imported into the WebSphere Application Server, Advanced Edition, Version
4.0.x environment. User Response: Use the information specified
by the exception information to correct the error and execute the WASPostUpgrade
command again if this object is required in the WebSphere Application Server,
Advanced Edition, Version 4.0.x environment.
MIGR0124E:
Unable to import XML data file {0}. Explanation: When executing
the WASPostUpgrade command, if the -import parameter as not specified, the
xml data file that was created when the WASPreUpgrade command was executed
cannot be used. This may be due to an incorrect value for the backup directory
name. If the -import parameter was specified then an invalid value may have
been specified. User Response: Correct the error and execute the
command again using the correct parameters.
MIGR0125E:
The call to XMLConfig was not successful {0}. Check the log for details, fix
the problem and try again. Explanation: When executing one
of the migration command, a call to XMLConfig was not successful. The log
associated with the migration command can be found in the directory specified
by the backup directory name. See this log for more information on this error.
Also ensure that the WebSphere Administration Server is running and the parameters
that are passed to XMLConfig are correct before the migration command is executed
again. User Response: Correct the error and execute the command.
MIGR0126E: The call to XMLConfig was not successful. Caught exception {0}.
Explanation: When executing one of the migration command,
a call to XMLConfig was not successful. The log associated with the migration
command can be found in the directory specified by the backup directory name.
See this log for more information on this error. Also ensure that the WebSphere
Administration Server is running and the parameters that are passed to XMLConfig
are correct before the migration command is executed again. User Response:
Correct the error and execute the command.
MIGR0127E:
Unable to load the XMLConfig class. Caught exception {0}. Explanation:
When executing the WASPreUpgrade command a specific jar file containing
XMLConfig is required to create an xml data file that was created. This file
cannot be found or loaded. User Response: This is an error, contact
IBM Service personnel for further information.
MIGR0128E:
Unable to read XMLConfig data tag definition file. Explanation:
When executing the WASPostUpgrade command a DTD file is required to read
an xml data file that was created on a Release 3.02 or 3.5 system. This file
cannot be loaded. User Response: This is an error, contact IBM
Service personnel for further information.
MIGR0129E: Unable
to save exported data to file {0}, caught exception {1}. Explanation:
An error while executing the WASPostUpgrade command while trying to save
the data in the configuration files. User Response: This is an
error, contact IBM Service personnel for further information.
MIGR0201I: Initialized Log File {0}. Explanation: This is an
informational message in the log file associated with a migration command
that the log file has been successfully created and can be used to log data.
User Response: None.
MIGR0202W: Failure to initialize
log file {0}. Explanation: This is an informational message
that can occur when trying to create the log file associated with a migration
command. The output of the log file will be routed to the screen instead of
the log file. User Response: None.
MIGR0203I:
Working with configuration from release {0}. Explanation: This
is an informational message that indicates the release that the WASPostUpgrade
command is currently using to import data from. This data is retrieved from
the backup directory specified on the WASPostUpgrade command line.
User Response: None.
MIGR0204I: Calling XMLConfig {0}.
Explanation: This is an informational message that the migration
command is calling XMLConfig. The following data in the log that is captured
is associated with this call to XMLConfig. User Response: None.
MIGR0206E: Unable to copy directory. The source {0} does not exist.
Explanation: An error occurred while executing the WASPreUpgrade command.
This error occurred because the source directory does not exist. This may
affect the success of a following WASPostUpgrade command. One error that may
occur is when a user directory cannot be copied and it contains the
data required to create a new application in the the WebSphere Application
Server, Advanced Edition, Version 4.0.x environment. User Response:
If possible, determine the reason for the failure, correct the problem
and try the command again.
MIGR0207E: Unable to copy directory
{0}. Explanation: An error occurred while executing the WASPreUpgrade
command. This error occurred because the source directory could not be copied.
This may affect the success of a following WASPostUpgrade command. One error
that may occur is when a user directory cannot be copied and it contains the
data required to create a new application in the the WebSphere Application
Server, Advanced Edition, Version 4.0.x environment. User Response:
If possible, determine the reason for the failure, correct the problem
and try the command again.
MIGR0208W: Unable to install
datasource {0} into JDBC driver name {1}. Explanation: An error
occurred while processing the WASPostUpgrade command. The error occurred while
installing a datasource into a JDBC driver. User Response: This
is an error, contact IBM Service personnel for further information.
MIGR0209I: Source directory {0} is verified. Explanation: This
is an informational message while executing the WASPreUpgrade command. It
indicates the source directory was found. User Response: None.
MIGR0210I: Creating directory {0}. Explanation: This is an
informational message while executing the WASPreUpgrade command. It indicates
the destination directory did not already exist and was created. User
Response: None.
MIGR0211I: Copying directory {0}.
Explanation: This is an informational message while executing the WASPreUpgrade
command. It indicates the directory was copied from the source to the destination
directory. User Response: None.
MIGR0212E: Unable
to create directory {0}. It already exists as a file. Explanation:
An error occurred while executing the WASPreUpgrade command. This error
occurred because the source directory could not be copied. This may affect
the success of a following WASPostUpgrade command. The destination directory
could not be created because it already exists in the backup directory as
a file. User Response: Correct the problem and try the command
again.
MIGR0213E: Unable to create directory {0}.
Explanation: An error occurred while executing the WASPreUpgrade command.
This error occurred because the source directory could not be copied. This
may affect the success of a following WASPostUpgrade command. The destination
directory could not be created. User Response: Correct the
problem and try the command again.
MIGR0214E: Unable to
copy file. Source {0} does not exist. Explanation: An error
occurred while executing the WASPreUpgrade command. This error occurred because
the source file could not be found. This may affect the success of a following
WASPostUpgrade command. The destination directory could not be created.
User Response: Correct the problem and try the command again.
MIGR0215E: Unable to copy file. Could not open destination file {0}.
Explanation: An error occurred while executing the WASPreUpgrade command.
This error occurred because the source file could not be found. This may affect
the success of a following WASPostUpgrade command. The destination file could
not be created. User Response: Correct the problem and try
the command again.
MIGR0216E: Unable to copy file. Could
not transfer from source {0} to destination {1}. Explanation:
An error occurred while executing the WASPreUpgrade command. This error
occurred because the source file could not be copied. This may affect the
success of a following WASPostUpgrade command. The destination file could
not be created. User Response: Correct the problem and try
the command again.
MIGR0217W: Could not close file {0}.
Explanation: An error occurred while executing the WASPreUpgrade
command. This error occurred because the destination file could not be closed.
This may affect the success of a following WASPostUpgrade command. The destination
file could not be created. User Response: Correct the problem
and try the command again.
MIGR0218I: Starting to import
{0}, action {1}. Explanation: This is an informational message
issued while executing the WASPostUpgrade command. It indicates that objects
of the specified type are being imported. User Response: None.
MIGR0219I: Starting to import {0}. Explanation: This is an
informational message issued while executing the WASPostUpgrade command. It
indicates that objects of the specified type are being imported. User
Response: None.
MIGR0220W: Ignoring object {0} of type
{1} because action was not create, update or locate. Explanation:
This is an informational message issued while executing the WASPostUpgrade
command. This command does not process all of the actions that can be specified
in an xml data file created by XMLConfig. Only the actions 'create', 'update
and 'locate' are supported. User Response: None.
MIGR0221I: Reading the previously saved configuration file {0}.
Explanation: This is an informational message issued while executing the
WASPostUpgrade command. It displays the configuration file that will be used
to restore the configuration.. User Response: None.
MIGR0222W: Unable to locate object while importing object {0} of type {1}.
Explanation: This is an informational message issued while
executing the WASPostUpgrade command. The specified object could not be found
in the existing configuration. This means that the objects owned by the this
object will not be processed as part of this configuration. User Response:
None.
MIGR0223I: Adding {0} entry {1} to the model.
Explanation: This is an informational message issued while
executing the WASPostUpgrade command. The specified object is being added
to the configuration. User Response: None.
MIGR0224W: Ignoring Node entry {0}, only one node is allowed on editions other
than Advanced.. Explanation: This is an informational message
issued while executing the WASPostUpgrade command. There is more than one
node specified in the xml data file. This node will not be processed as part
of the update of the configuration. User Response: None.
MIGR0225I: Unable to get cookie data. Caught exception {0}. Explanation:
This is an informational message issued while executing the WASPostUpgrade
command. The specified cookie data cannot be found and cannot be loaded into
the configuration. User Response: None.
MIGR0227W:
Unable to make a backup of configuration file {0}, caught exception {1}.
Explanation: This is a message issued while executing the WASPostUpgrade
command. A backup of the existing configuration files are made before attempting
to update the configuration. A backup file could not be create for the specified
file due to the displayed exception. This may cause problems in an error occurs
while trying to save the new configuration which would normally cause the
backup file to be restored as the configuration that will be used.
User Response: None.
MIGR0228E: Unable to save configuration
files. Caught exception {0}. Explanation: This is a message
issued while executing the WASPostUpgrade command. A backup of the existing
configuration files are made before attempting to update the configuration.
Problems occurred while trying to save the new configuration and it cannot
be used. The backup file for the configuration files are restored as the configuration
that will be used. User Response: None.
MIGR0229I:
Updating attributes of {0} entry {1}, it is already defined in the existing
model. Explanation: This is an informational message
issued while executing the WASPostUpgrade command. The specified object already
exists in the WebSphere Application Server, Advanced Edition, Version 4.0.x
configuration. The attributes of this object will be updated to match the
attributes of the Release 3.02 or 3.5 configuration. User Response:
None.
MIGR0230I: Ignoring attributes of {0} entry {1}.
Objects owned by this object will be mapped to the one object allowed by this
product. Explanation: This is an informational message issued
while executing the WASPostUpgrade command. The specified object will not
be mapped to the WebSphere Application Server, Advanced Edition, Version 4.0.x
configuration because it is not valid to map in the destination WebSphere
Application Server, Advanced Edition, Version 4.0.x configuration. The attributes
of this object will not be updated to match the attributes of the Websphere
Application Server, Version 3.02 or 3.5 configuration. All of the objects
owned by the specified object will be processed during the rest of the migration process.
User Response: None.
MIGR0231E: Failure while deploying
object {0} of type {1}. Explanation: This is an informational
message issued while executing the WASPostUpgrade command. The specified EJB
object could not be deployed into the WebSphere Application Server, Advanced
Edition, Version 4.0.x configuration. See following messages in the log for
more information on this failure. User Response: The log will contain
more information on the specific error, this may be due to incompatibilities
between EJB 1.0 and EJB 1.1 implementations. If this is the case then the
application that contains the EJB will have to be modified and deployed using
the development and deployment tools.
MIGR0232I: No object
of type {0} to import. Explanation: This is an informational
message issued while executing the WASPostUpgrade command. This happens during
the processing of security information of the specified object. User
Response: Review and modify the security information of the specified
object as required after the migration has been completed.
MIGR0233W: Failure while importing object {0} of type {1}, JSP level 0.91
is not supported. Explanation: This is an informational message
issued while executing the WASPostUpgrade command. This happens during the
processing of ServletEngine configurations. The specified ServletEngine is
configured to support JSP 0.91 level of servlets. This support has been removed
in this release, so the servlets owned by this ServletEngine will not be migrated
to the WebSphere Application Server, Advanced Edition, Version 4.0.x environment
User Response: If the servlets owned by this ServletEngine are required
then they will need to be modified to use JSP 1.1 interfaces and then redeploy
into the WebSphere Application Server, Advanced Edition, Version 4.0.x environment.
MIGR0234W: Unable to locate object {0} of type {1}. Explanation:
This is an informational message issued while executing the WASPostUpgrade
command. The specified object could not be found in the existing configuration.
This means that the objects owned by the this object will not be processed
as part of this configuration. User Response: None.
MIGR0235I: Completing import. Explanation: This is an informational
message. User Response: None.
MIGR0236W: Ignoring
GenericServer entry {0}, only one application server is allowed on editions
other than Advanced. Explanation: This is an informational
message issued while executing the WASPostUpgrade command. A GenericServer
entry was processed. There is a limit on the number of application servers
that can be created in the edition this migration is executing against. This
entry will be ignored. User Response: None.
MIGR0237I: Read configuration file {0} successfully. Explanation:
This is an informational message while executing the WASPostUpgrade command.
The specified xml data file has been read successfully. User Response:
None.
MIGR0238W: Ignoring object {0} of type {1} because
action was not create, update or locate. Explanation: This
is an informational message issued while executing the WASPostUpgrade command.
This command does not process all of the actions that can be specified in
an xml data file created by XMLConfig. Only the actions 'create', 'update'
and 'locate' are supported. User Response: None.
MIGR0239I: Creating XML data file {0} before calling XMLConfig.
Explanation: This is an informational message while executing the WASPostUpgrade
command. The specified xml data file is being created as input to an XMLConfig
command. User Response: None.
MIGR0240E: Error
while creating DOM entries for input xml data file, caught exception {0}.
Explanation: This is an error message issued while executing
the WASPostUpgrade command. Some data could not be mapped properly from the
previous configuration files to the WebSphere Application Server, Advanced
Edition, Version 4.0.x configuration. User Response: This is an
error, contact IBM Service personnel for further information.
MIGR0241I: Standard output of {0}. Explanation: This is an
informational message. The following data is the output of one of the commands
being executed by the migration command. This data can be used for further
problem determination if required. User Response: None.
MIGR0242I: Standard error of {0}. Explanation: This is an informational
message. The following data is the output of one of the commands being executed
by the migration command. This data can be used for further problem determination
if required. User Response: None.
MIGR0243I:
Datasource {0} already installed in JDBC driver name {1}. Explanation:
An error occurred while processing the WASPostUpgrade command. The error
occurred while installing a datasource into a JDBC driver because a datasource
is already installed in the JDBC Driver. This configuration will use the existing
datasource and JDBC Driver combination. User Response: None
MIGR0300I: Starting to save existing WebSphere environment. Explanation:
This is an informational message. User Response: None.
MIGR0301I: Exporting existing configuration. Explanation: This
is an informational message. User Response: None.
MIGR0302I: Saving existing files. Explanation: This is an informational
message. User Response: None.
MIGR0303I: Completed
saving of the existing WebSphere environment. Explanation: This
is an informational message. User Response: None.
MIGR0304I: Starting to restore previous WebSphere environment.
Explanation: This is an informational message. User Response:
None.
MIGR0305I: Importing previous configuration.
Explanation: This is an informational message. User
Response: None.
MIGR0306I: Restoring previously saved
files. Explanation: This is an informational message.
User Response: None.
MIGR0307I: Completed restoring
of the previous WebSphere environment. Explanation: This is
an informational message. User Response: None.
MIGR0308I: Successfully restored {0} {1} objects. Explanation:
This is an informational message. User Response: None.
MIGR0309I: Failed to restore {0} {1} objects. Explanation: This
is an informational message. User Response: None. NMSV0001W: NameServer already
initialized, ignoring this request to initialize again. Explanation:
The name server should be initialized only once, but there was an attempt
to initialize it a second time. User Response: This message is
to aid in problem diagnosis and can be ignored if no external symptoms are
experienced. If this message accompanies name server startup problems, please
report this problem to IBM support.
NMSV0002W: WsnNameService
bootstrap object created with no properties. Explanation: No
properties were supplied to the name server to create a bootstrap object.
User Response: This message is to aid in problem diagnosis and can be
ignored if no external symptoms are experienced. If there is a problem starting
the name server, please report this event to IBM support.
NMSV0003E: Name server initialization failed. Cannot obtain host name for
this host. Explanation: The name server could not be initialized.
An error occurred while attempting to obtain the host name for the name server's
local host. User Response: This error is an internal error. Please
contact IBM support. NMSV0004E: Name server initialization
failed. Cannot initialize database tables. Explanation: The
name server could not be initialized. The database tables, used to store persistent
name server data, could not be initialized. User Response: Make
sure that the database server is running and that the WAS database exists.
Confirm that a connection can be made to the database using the user id and
password that WebSphere is configured to use. NMSV0005E:
Name server initialization failed. Cannot create the LDAP name tree.
Explanation: The name server could not be initialized. The LDAP directory
space, used to store persistent name server data, could not be initialized.
User Response: This error is an internal error. Please contact IBM support.
NMSV0006E: Name server initialization failed. Name server implementation
type of "{0}" is not supported in this release. Explanation: The
name server could not be initialized. WebSphere is configured to use a name
server implementation that is not supported in this release. User Response:
This error is an internal error. Please contact IBM support.
NMSV0007E: Name server initialization failed. Name server implementation type
of "{0}" is not recognized as a valid type. Explanation: The
name server could not be initialized. WebSphere is configured to use a name
server implementation that is not recognized. User Response: This
error is an internal error. Please contact IBM support.
NMSV0008E: Name server initialization failed. Could not create a root context
IOR. The name server implementation type is "{0}". Explanation:
The name server could not be initialized. The root context object could
not be converted to an IOR. User Response: This error is an internal
error. Please contact IBM support. NMSV0009E: Name server
initialization failed. Unable to create name server bootstrap object.
Explanation: The name server could not be initialized. The name server
bootstrap object could not be created. User Response: This error
is an internal error. Please contact IBM support. NMSV0010E:
Name server initialization failed. Initialization of the WLM Bootstrap Service
failed. Explanation: The name server could not be initialized.
An error occurred while attempting to initialize the WLM Bootstrap Service.
User Response: This error is an internal error. Please contact IBM support.
NMSV0011E: Unable to start Bootstrap Server. The most likely
cause is that the bootstrap port is already in use. Please ensure that no
servers or other processes are already using the bootstrap server port.
Explanation: Make sure the bootstrap port is not already in use by any
other server processes. This error can occur when WebSphere's name server
has already been started. Otherwise, this error is an internal error. Please
contact IBM support if the above actions do not correct the problem.
User Response: This error is an internal error. Please contact IBM support.
NMSV0012E: Name server initialization failed. Cannot create
the CosNaming name tree. Explanation: The name server could
not be initialized. The CosNaming name tree structure could not be initialized.
User Response: This error is an internal error. Please contact IBM support.
NMSV0013E: Name server initialization failed. Method getInitialContextRdbBootstrap
failed or called in error. Explanation: The name server could
not be initialized. The getInitialContextRdbBootstrap method was either called
when not in RDB Name Server Bootstrap mode or it was unable to create the
InitialContext. User Response: This error is an internal error.
Please contact IBM support. NMSV0014E: Name server initialization
failed. Attempt to bind an object prior to initialization completing.
Explanation: The name server could not be initialized. The RDB Name Server
has not yet been fully initialized, but was called to bind an object that
was not one of the Name Service EJBs. User Response: This error
is an internal error. Please contact IBM support. NMS0015E:
Name server initialization failed. Could not build the System Name Space.
Explanation: The name server could not be initialized. There
was an unrecoverable NamingException when building the System Name Space.
User Response: This error is an internal error. Please contact IBM support.
NMSV0016E: Internal implementation error. Unexpected InvalidNameException
thrown by WsnName while converting an internally generated name string "{0}"
to a CosName. Throwing a CosNaming InvalidName exception. Explanation:
The CosNaming name server initialization process cannot convert a name
that was internally generated to the CosNaming name format. User Response:
This error is an internal error. Please contact IBM support.
NMSV0100E: new_context: Unbound context instances not allowed. Throwing NO_IMPLEMENT
exception. Explanation: The method, new_context, part of the
CosNaming::NamingContext interface, is not supported. User Response:
A client program invoked the new_context method, which is not supported.
Clients should use the bind_new_context method.
NMSV0101E:
The name syntax property "{0}" is set to an unrecognized value of "{1}".
Explanation: An invalid name syntax was specified. User Response:
This error is an internal error. Please contact IBM support.
NMSV0102E: Internal implementation error. Unexpected InvalidNameException
thrown by WsnName while converting the internally stored INS name string "{0}"
to a CosName. Ignoring the exception and setting the name to an empty name.
Explanation: The CosNaming name server cannot convert a name
stored in an internal format to the CosNaming name format. User Response:
This error is an internal error. Please contact IBM support.
NMSV0103E: A zero-length CosNaming::NameComponent array was specified. Throwing
InvalidName exception. Explanation: An empty name (zero name
components) was passed to the CosNaming server. Empty names are not valid.
User Response: If the CosNaming client is a customer-provided application,
this is a user error. If the CosNaming client is WebSphere's CosNaming JNDI
plug-in (i.e., a WebSphere context factory was used to create an initial context),
this is an internal error and should be reported to IBM support.
NMSV0104E: CosNaming::NameComponent[{0}] contains a null id or kind field.
Throwing InvalidName exception. Explanation: A component in
a name passed to a method in WebSphere's name server implementation of CosNaming::NamingContext
contained a null id or kind field. A null value for an id or kind field is
invalid. User Response: If the CosNaming client is a customer-provided
application, this is a user error. If the CosNaming client is WebSphere's
CosNaming JNDI plug-in (i.e., a WebSphere context factory was used to create
an initial context), this is an internal error and should be reported to IBM
support.
NMSV0105E: Cannot convert a CosName to a valid
INS name. Explanation: The CosNaming name server could not
convert a CosNaming name to its internal form. User Response: This
error is an internal error. Please contact IBM support.
NMSV0106E: Target context type of "{0}" is not the expected type.
Explanation: The CosNaming name server encountered an unknown implementation
of CosNaming::NamingContext. User Response: This error is an internal
error. Please contact IBM support.
NMSV0107E: An unexpected
error occurred. Mapping to CORBA UNKNOWN. Explanation: Some
unexpected error occurring which processing a CosNaming name server request.
User Response: See the trace output for more details about the origin
of the problem.
NMSV0108E: An error occurred attempting
to create database tables. Explanation: The database tables
used by the name server to store name space data could not be created. The
cause is probably specific to the relational database manager being used.
User Response: See the trace output for more details about the origin
of the problem.
NMSV0109E: CosNaming server caught exception:
AdapterAlreadyExistsException. Explanation: The CosNaming name
server encountered a fatal error during startup. User Response: This
error is an internal error. Please contact IBM support.
NMSV0110E: CosNaming server caught exception: InvalidServantException.
Explanation: The CosNaming name server encountered a fatal error during
startup. User Response: This error is an internal error. Please
contact IBM support.
NMSV0301E: A lookup of "{0}" failed.
Explanation: An error occurred during deserialization of a
JNDI context for a local name space, such as a java: URL name space. This
error is most likely to occur during reactivation of an Enterprise JavaBean
deployed on an application server. User Response: This error is
an internal error. Please contact IBM support.
NMSV0302E:
NamingManager.getURLContext returned a null Context for the scheme "{0}".
Explanation: A URL was passed to a JNDI Context method, which
then invoked the JNDI Naming Manager to return the Context identified by the
URL. The Naming Manager method which was invoked returned a null value.
User Response: This problem is probably the result of an incorrect configuration.
Make sure that the factory for the scheme of the specified URL can be located
from the value of the property, java.naming.factory.url.pkgs, found in the
Context's environment.
NMSV0303E: Exception occurred in
NamingManager.getURLContext for the scheme "{0}". Explanation:
A URL was passed to a JNDI Context method, which then invoked the JNDI
Naming Manager to return the Context identified by the URL. The Naming Manager
invocation failed. User Response: This problem is probably the
result of an incorrect configuration. Make sure that the factory for the scheme
of the specified URL can be located from the value of the property, java.naming.factory.url.pkgs,
found in the Context's environment. The trace output may contain additional
diagnostic information.
NMSV0304W: There was an attempt
to set the java URL name space accessor more than once. Explanation:
This is an internal error. The java URL name space accessor should be
initialized only once, but there was an attempt to initialize it a second
time. User Response: This message is to aid in problem diagnosis
and can be ignored if no external symptoms are experienced. If this message
accompanies problems using java: URL names in java.naming.Context method calls,
please report this problem to IBM support.
NMSV0305E: A
NamingException occurred while getting the next object in the UrlBindingEnumeration
Explanation: Some error occurred while processing the method,
next, in the NamingEnumeration returned from a URL context. User Response:
This error is an internal error. Please contact IBM support.
NMSV0306E: The scheme or package name was not set. Explanation:
An error occurred while processing a URL-based name space. User
Response: This error is an internal error. Please contact IBM support.
NMSV0401W: The name "{0}" is invalid. Explanation: The LDAP
plug-in for JNDI could not perform an internal name conversion. This is an
internal error. User Response: If incorrect results are accompanied
by this message, please contact IBM support.
NMSV0402E:
Cannot convert the JNDI name "{0}" to an LDAP name string. Explanation:
A JNDI name passed to the LDAP plug-in for JNDI could not be converted
to an LDAP name. This is probably an internal error. User Response:
This error is an internal error. Please contact IBM support. As a work-around,
use a different name if possible.
NMSV0403E: Error occurred
while serializing context object. Explanation: An error occurred
during serialization of a JNDI context for an LDAP-based name space.
User Response: This error is an internal error. Please contact IBM support.
NMSV0404E: Error occurred while deserializing context object.
Explanation: An error occurred during deserialization of a JNDI context
for an LDAP-based name space. User Response: This error is an internal
error. Please contact IBM support.
NMSV0501W: Ignored an
InvalidPropertyName exception from the CosNaming name server.
Explanation: An internal error occurred during a JNDI lookup.
User Response: If this warning message is accompanied by incorrect JNDI
lookup results, please context IBM support to report this problem.
NMSV0502W: The class "com.ibm.ejs.ns.jndi.CNInitialContextFactory" has been
deprecated. It has been replaced with "com.ibm.websphere.naming.WsnInitialContextFactory".
Explanation: The initial context factory for WebSphere has
changed. The old one will work, but some time in the future it will no longer
be available. User Response: Begin using the new initial context
factory as soon as possible. NMSV0601E: Naming Service
unavailable. Null initial context returned from ORB. Explanation:
The initial context returned from the ORB was null. User Response:
This error is an internal error. Please contact IBM support.
NMSV0602E: Naming Service unavailable. A communications error occurred.
Explanation: A connection to the name server could not be made when attempting
create an initial context. User Response: The most like causes
are that the provider URL is incorrect or that the name server identified
by the provider URL is not running. Make sure that the name server is running
and that the host and port in the provider URL are correct. Also, make sure
that the host identified in the provider URL can be accessed from the machine
on which the JNDI client is running. Refer to the trace output accompanying
this message for more information about the root cause.
NMSV0603E: Naming Service unavailable. Could not get the root context.
Explanation: An unknown error occurred while attempting to obtain the
initial context from the ORB. User Response: For more information
about the root cause, refer to any additional trace output accompanying this
message.
NMSV0604E: Exception thrown in Referenceable.getReference().
Explanation: While processing a JNDI bind or rebind operation
on a javax.naming.Referenceable object, a call to the method, getReference(),
on the object resulted in an exception. User Response: The Referenceable
object could not be processed for some unknown reason. Check the trace output
accompanying this message for more details on the root cause.
NMSV0605E: Exception thrown in NamingManager.getObjectInstance().
Explanation: While processing a JNDI lookup or listBindings operation
on a javax.naming.Reference object, a call to the JNDI Naming Manager to process
the object failed. It is possible that some class file required to process
the Reference object cannot be found in the classpath. It is also possible
that a factory for the Reference object could not be found, based on the value
for the property java.naming.factory.object found in the JNDI context's environment.
User Response: Make sure that the classpath and java.naming.factory.object
property setting are correct. Check the trace output accompanying this message
for more details on the root cause.
NMSV0606E: Object is
not of any type which can be bound. Explanation: The JNDI bind
or rebind method was passed an object which is of a type that cannot be bound.
Allowed object types include CORBA objects (which includes EJBs deployed to
WebSphere), JNDI contexts of the same type as the context object being invoked,
javax.naming.Referenceable, javax.naming.Reference, and java.io.Serializable.
User Response: Attempt to bind or rebind only objects of the above types.
NMSV0607E: The Context at name path "{0}" was passed a null name to the method
"{1}". Explanation: A JNDI context method was passed a null
name. Null names are not valid. User Response: Use an appropriate
name for the desired JNDI operation.
NMSV0608E: The Context
at name path "{0}" was passed an empty name to the method "{1}".
Explanation: A JNDI context method was passed an empty name. JNDI context
methods except for lookup, list, and listBindings, do not accept empty names.
User Response: Use an appropriate name for the desired JNDI operation.
NMSV0901E: An unexpected error occurred. Explanation: Some
unexpected error occurred. User Response: Check any trace output
accompanying this message for additional information. This is very possibly
an internal error. If the problem cannot be resolved from the trace output,
please contact IBM support.
NMSV0902E: An error occurred
while serializing an object. Explanation: An error occurred
while attempting to serialize an object. This error probably occurred during
a JNDI bind or rebind operation. User Response: One possible cause
is that some object encountered during the serialization process is not serializable.
For more information about the root cause, see the trace output which accompanies
this message.
NMSV0903E: An error occurred while deserializing
an object. Explanation: An error occurred while attempting
to deserialize an object. This error probably occurred during a JNDI lookup
or listBindings operation. User Response: The most likely cause
for this problem is not having the required class or classes in the JNDI client
classpath. The trace output should contain more details, such as the class
name that could not be found.
NMSV0904W: Ignored InvalidNameException
while converting a CosName to a String. Explanation: A name
conversion performed for internal processing failed. User Response:
This is an internal error. This message is to aid in problem diagnosis
and can be ignored if no external symptoms are experienced. If this message
accompanies problems occurring with JNDI method calls, please report this
problem to IBM support.
NMSV0905E: Failed to create Class
object for the class "{0}". Explanation: An error occurred
during internal processing. User Response: This error is an internal
error. Please contact IBM support.
NMSV0906E: Could not
create an instance of the class "{0}". Explanation: An error
occurred during internal processing. User Response: This error
is an internal error. Please contact IBM support.
NMSV0907E:
Could not invoke method "{0}" on object of type "{0}". Explanation:
An error occurred during internal processing. User Response: This
error is an internal error. Please contact IBM support. PLGN0001E: Prepare for write
Explanation: None. User Response: None.
PLGN0002E: OSE Listener Explanation: None. User Response:
None.
PLGN0003E: Null listener Explanation:
None. User Response: None.
PLGN0004E: Engine
exception Explanation: None. User Response: None.
PLGN0005E: Cred buffer error Explanation: None. User
Response: None.
PLGN0006E: Illegal use of OSEListenerDispatcher
by plug-in Explanation: None. User Response: None.
PLGN0007E: Engine Throwable Explanation: None. User
Response: None.
PLGN0008E: Translate a message
Explanation: None. User Response: None.
PLGN0009E: init message instead of service Explanation: None.
User Response: None.
PLGN0010E: Can not create SQEventImp
Explanation: None. User Response: None.
PLGN0011E: Can't find class com.ibm.servlet.debug.OOPDebugEngine: all WebSphere
Application Server jars must be in the classpath Explanation:
None. User Response: None.
PLGN0012E: Getting
init data Explanation: None. User Response: None.
PLGN0013E: Null native queue Explanation: None. User
Response: None.
PLGN0014E: Unable to load bootstrap.properties
Explanation: None. User Response: None.
PLGN0015E: Bootstrap file does not exist Explanation: None.
User Response: None.
PLGN0016E: Can not create queue
Explanation: None. User Response: None.
PLGN0017E: Return code is -1 Explanation: None. User
Response: None.
PLGN0018E: Accept new socket
Explanation: None. User Response: None.
PLGN0019E: Sending message Explanation: None. User Response:
None.
PLGN0020E: Closing.queue Explanation:
None. User Response: None.
PLGN0021E: Servlet
request processor exception: Virtual Host/WebGroup not found Explanation:
None. User Response: None.
PLGN0022E: SSL
information error Explanation: None. User Response:
None.
PLGN0023E: Invalid argument : null queue name
Explanation: None. User Response: None.
PLGN0024E: No certificates Explanation: None. User Response:
None.
PLGN0025E: Illegal Access Exception
Explanation: None. User Response: None.
PLGN0026E: Stopping threads Explanation: None. User
Response: None.
PLGN0027E: Initializing message
Explanation: None. User Response: None.
PLGN0028E: Service requests Explanation: None. User
Response: None.
PLGN0029W: Failed to redirect system
output Explanation: None. User Response: None.
PLGN0030E: Interrupted wait Explanation: None. User
Response: None.
PLGN0031E: Closing new socket
Explanation: None. User Response: None.
PLGN0032E: Interrupted Event notification. Explanation: None.
User Response: None.
PLGN0033E: Null server root
Explanation: None. User Response: None.
PLGN0034E: Interrupted wait/Event generation. Explanation: None.
User Response: None.
PLGN0035E: Send error
Explanation: None. User Response: None.
PLGN0036E: Failure to service Explanation: None. User
Response: None.
PLGN0037E: Unable to load bootstrap.properties,
server.root not defined Explanation: None. User Response:
None.
PLGN0038E: Instantiation Exception
Explanation: None. User Response: None.
PLGN0039E: Failure to marshal threads Explanation: None.
User Response: None.
PLGN0040E: Interrupted wait
Explanation: None. User Response: None.
PLGN0041E: IllegalStateException: Illegal AppServerEntry classname: {0}
Explanation: None. User Response: None.
PLGN0042E: Pre-invoke Security Exception Explanation: None.
User Response: None.
PLGN0043E: Get a service ID.
Explanation: None. User Response: None.
PLGN0044E: Error releasing the message Explanation: None.
User Response: None.
PLGN0045E: Free disposed object
Explanation: None. User Response: None.
PLGN0046E: Error while parsing a service message Explanation:
None. User Response: None.
PLGN0047E: Open
new server socket Explanation: None. User Response:
None.
PLGN0048E: Get message/service portion
Explanation: None. User Response: None.
PLGN0049E: -1 return code Explanation: None. User Response:
None.
PLGN0050E: Releasing message Explanation:
None. User Response: None.
PLGN0051E: Null
input Explanation: None. User Response: None.
PLGN0052E: Getting new socket Explanation: None. User
Response: None.
PLGN0053E: Interrupted notify
Explanation: None. User Response: None.
PLGN0054E: Null buffer Explanation: None. User Response:
None.
PLGN0055E: Unable to load bootstrap.properties
from server.root Explanation: None. User Response: None.
<!
MSGSTART --> PMON3002W: The WebSphere admin
server is not running. Please start the admin server if you want to use
Resource Analyzer to display current data. The server is not required
for replaying log files. Explanation: Resource Analyzer is
not able to connect to the WebSphere administrative server, as it might not
be running or wrong host or port# is specified. Resource Analyzer will not
be able to collect real-time performance data. User Response: To
get real-time data make sure the administrative server is running. To play
log files administrative server is not required <! MSGEND --> <!
MSGSTART --> PMON3003W: Reached end
of log file. Please rewind file to play from the beginning.
Explanation: Resource Analyzer reached end of the log file that is being
played. User Response: To start playing again click rewind and
play <! MSGEND --> <! MSGSTART -->
PMON3005W: Performance data monitoring is not enabled for this selection. Set
the monitoring level in WebSphere Administrative Console and refresh Resource
Analyzer. Explanation: None. User Response: None.
<! MSGEND --> <! MSGSTART -->
PMON3006W: Performance data monitoring is not enabled for this selection. Would
you like to set the monitoring level now? Explanation: None.
User Response: None. <! MSGEND --> <! MSGSTART -->
PMON3007W: Save the Monitoring setting
changes in WebSphere Admin Server? Explanation: None.
User Response: None. <! MSGEND --> <! MSGSTART --> PMON7001E: Error opening log file or unknown file format.
Explanation: Resource Analyzer is not able to open the specified
log file for re-playing User Response: Log file format might not
be compatible with the expected format (Resource Analyzer Version 4.0) or
log file might be corrupted <! MSGEND --> <! MSGSTART --> PMON7002E: Invalid input - Please select a number between
0 and 501. Explanation: Expected value is a number greater
than zero and less than 501 User Response: Use a number greater
than 0 and less than 500 <! MSGEND --> <! MSGSTART --> PMON7003E: Error in getting data. Make sure the server
has not been stopped or removed by refreshing the server node.
Explanation: Resource Analyzer is not able to connect to application server
as it might be stopped or removed. User Response: Check in the
admin console if the application server for which the data is requested is
running. <! MSGEND --> <! MSGSTART -->
PMON7004E: Invalid input - Please select a number greater than 0.
Explanation: None. User Response: None. <! MSGEND
--> <! MSGSTART --> PMON7005E: Help
file not found. Explanation: None. User Response:
None. <! MSGEND --> <! MSGSTART -->
PMON7006E: A browser could not be launched to display help. Explanation:
None. User Response: None. <! MSGEND --> <! MSGSTART
--> PMON7007E: Error connecting to Admin
Server. Explanation: None. User Response: None.
<! MSGEND --> <! MSGSTART -->
PMON9000E: Error - Invalid port# Usage: java com.ibm.websphere.pmi.ra.view.RAGui <host
name> <port#> Explanation: Command line error. Describes
command line usage and required parameters User Response: Make
sure the port# after the host name is an integer. By default, 900 is assumed.
Alarm
ALRM0001W: Encountered
a failure in the fireAlarm method {0} Explanation:
None. User Response: None. SECJ0007E: Error during security initialization
Explanation: An unexpected error occurred during security
initialization. User Response: This is a general error. Look
for previous messages that may be related to the failure or a configuration
problem. Enabling security debug trace for components com.ibm.ws.security.*
and com.ibm.ejs.security.* may yield additional information.
SECJ0045E: Error initializing security/SAS Explanation: An
error occurred initializing the Secure Association Service which is part of
the ORB security. User Response: Verify the property file, usually
sas.server.props, is present and has read permission.
SECJ0046E: SAS Property:{0} has been updated Explanation: Informational
User Response: A security configuration change has caused a SAS Property
to be updated.
SECJ0047E: Missing or malformed security
configuration URL specified by property {0} Explanation: The
URL used to specify Secure Association Service properties is missing or malformed.
User Response: The URL is usually specified as a propertyname when starting
WebSphere from the command line with the -D argument. For example: \-Dcoom.ibm.CORBA.ConfigURL=file\:/C\:/wastd/AppServer/properties/sas.server.props. Verify
that the property and URL is specified and refers to a valid file and the
file has the read permission.
SECJ0048E: Error updating
or loading future security configuration URL specified by property {0}
Explanation: The path or file specified in the property may be invalid
or there could be a file permission problem. User Response: Verify
the path and file specified by the property is valid and the file has read
permission.
SECJ0049E: Configuration error encountered
while starting the server Explanation: An unexpected
RemoteException, OpException or IOException occurred during server startup.
There could be problems with loading or writing of security configured URL
property files. User Response: Verify the file permissions associated
with security configured URL property file (typically sas.server.props) are
read and writable.
SECJ0050E: Error encountered while shutting
down the server Explanation: An unexpected RemoteException,
OpException or IOException occurred during server shutdown. There could be
problems with loading or writing of security configured URL property files.
User Response: Verify the file permissions associated with security configured
URL property file (typically sas.server.props) are read and write.
SECJ0051E: IOException when determining whether configuration is current with
property file {0} or {1} Explanation: A loadProperties() operation
probably failed. User Response: Verify the file permissions associated
with security configured URL property file (typically sas.server.props) are
read and write.
SECJ0052E: Authorization failed while invoking
({0}){1} {2} - invalid credentials Explanation: This
is an internal error. The credential used during the authorization check is
corrupt, missing attributes, or not recognized. User Response:
Contact your service representative if the problem persist.
SECJ0053E: Authorization failed for {0} while invoking ({1}){2} {3}
Explanation: The user does not have the necessary permission to
access the resource. User Response: Contact your WebSphere
security administrator if this is unexpected. The user must be mapped to one
the roles protecting the resource if the user requires access to the protected
resource.
SECJ0055E: Authentication failed for {0}
Explanation: The user could not be authenticated. The user
id or password may have been entered incorrectly. The user may not exist
in the user registry that WebSphere is configured to authenticate to.
User Response: Verify that the user id and password are entered
correctly. Consult with the administrator of the user registry that WebSphere
is configured to use if the problem persist.
SECJ0056E:
Authentication failed for reason {0} Explanation: Authentication
failed with the specified reason. User Response: Verify that
the user id and password are entered correctly. Consult with the administrator
of the user registry if the problem persist.
SECJ0058E:
LTPAServer does not exist Explanation: This is an internal
error probably due to LTPAServer initialization problems. User Response:
Contact your service representative if the problem persist. Enabling
security debug trace for components com.ibm.ws.security.* and com.ibm.ejs.security.*
may yield additional information.
SECJ0059E: Cannot create
LTPAServer without a password Explanation: The wrong
constructor was used when trying to create an instance of LTPAServerBean
User Response: This is an internal error. Contact your service
representative
SECJ0060E: LTPA configuration not found
Explanation: This is an internal error. User Response:
Contact your service representative if the problem persist.
SECJ0061E: LTPAConfig creation exception Explanation: This
is an internal error. A problem occurred during the LTPAConfig creation
or initialization. User Response: There may be a problem
with the datasource for the LTPAConfigBean.
SECJ0062E:
LTPAConfig remove exception Explanation: This is an internal
error. The ejbRemove() operation failed on the LTPAConfigBean User
Response: There may be a problem with the datasource for the LTPAConfigBean. Contact
your service representative if the problem persist.
SECJ0063E:
Credential mapping failed due to invalid access ID Explanation:
This is an internal error due to a null access ID in the credential.
User Response: Contact your service representative if the problem
persist.
SECJ0064E: Credential mapping failed
Explanation: The credential mapping can fail for a number of reasons:
The credential token is not an instance of a supported CredentialToken type
for a mapping. The principal identified in the credential cannot be
mapped to an entry or found in the user registry. A user registry exception
occurs or if the user registry has been stopped. User Response:
Verify the user registry is operational. Verify the principal exist
in the target user registry if appropriate. The exception reported
with this error message may help diagnose the problem.
SECJ0065E: Unsupported encoding Explanation: This is an internal
error. An UnsupportedEncodingException occurred when the LTPAServer tried
to encode the token value. User Response: Contact your service
representative if the problem persist.
SECJ0067E: Cannot
credential map given credential token into LDAP Explanation:
The credential mapping can fail for a number of reasons: The credential
token is not an instance of a supported CredentialToken type for a mapping. The
principal identified in the credential cannot be mapped to an entry or found
in the user registry. A user registry exception occurs or if the user
registry has been stopped. User Response: Verify the user
registry is operational. Verify the principal exist in the target user
registry if appropriate. The exception reported with this error message
may help diagnose the problem.
SECJ0068E: LDAP initialization
error Explanation: An unexpected exception occurred when configuring
for LDAP. User Response: Verify the WeSphere LDAP configured settings
such as the provider URL are correct in the Security Center GUI.
SECJ0069E: No Security Name configured for privilege id: {0}.
Explanation: Cannot find a name for the specified SID in the Windows
user registry. This can occur if a network timeout prevents the function from
finding the name. It also occurs for SIDs that have no corresponding account
name, such as a logon SID that identifies a logon session User Response:
WebSphere may still have a reference to the user in the authorization
table but, that user may have been removed from the Windows user registry. If
you know the user, remove it from any resource protection permissions in WebSphere. If
the user is still valid, then it needs to be recreated in the Windows user
registry and then reassigned to proper resource permissions in WebSphere.
SECJ0070E: No privilege id configured for: {0} Explanation:
Unable to find a SID for the specified user in the Windows user registry. The
user may not exist in the user registry. User Response: If
appropriate create the user in the user registry.
SECJ0071E:
Error retrieving registry entries for the given pattern {0} Explanation:
None. User Response: Verify the pattern is correct and
not malformed.
SECJ0072E: Error finding registry for type
{0} Explanation: This is an internal error. The
key may not represent a valid type or a common name may be invalid.
User Response: If the problem persist, contact your service representative.
SECJ0073E: Error finding registry entry for privilege id {0} Explanation:
This is an internal error. User Response: If the problem
persist, contact your service representative.
SECJ0074E:
Error creation user registry Explanation: An InstantiationException,
IllegalAccessException, ClassNotFoundException exception occurred when trying
to load or create the user registry. User Response: Verify
the classpath used to start WebSphere is correct and that the jar files have
at least the read permission and exist.
SECJ0075E: Unsupported
entry type {0} Explanation: This is an internal error. A
registry of the specified type could not be looked up. User Response:
If the problem persist, contact your service representative.
SECJ0076E: Error creating registry entry home Explanation:
This is an internal error. Unable to create the home for the registry.
User Response: If the problem persist, contact your service representative.
SECJ0077E: Registry impl instance not found for type {0} Explanation:
This is an internal error. User Response: If the problem
persist, contact your service representative.
SECJ0078E:
User registry does not exist Explanation: Unable
to lookup RegistryHome in name space or narrow failed. The class for the
user registry was not registered in the name space correctly or the class
file for the user registry cannot be found. User Response: Verify
the classpath is correct and that the required classes exist.
SECJ0079E: User type not supported in the user registry Explanation:
This is an internal error. User Response: If the problem
persist, contact your service representative.
SECJ0082E:
Error during web security initialization Explanation: This
is an internal error. An unexpected exception occurred when initializing the
WebCollaborator User Response: If the problem persist, contact
your service representative. Enabling security debug trace for components
com.ibm.ws.security.* and com.ibm.ejs.security.* may yield more information.
SECJ0084E: Error while initializing security web configuration
Explanation: An error internal occurred while initializing the security
attributes of a Web Application. User Response: If the problem
persist, contact your service representative.
SECJ0087E:
Internal Server Error Explanation: The HttpServletResponse
indicates an Internal Server Error has occurred. User Response: If
the problem persist, contact your service representative.
SECJ0105E: An unexpected exception occurred when decoding the value [{0}]
for password [{1}] in the security configured URL Explanation:
The encoded password cannot be decoded because it is missing or malformed.
User Response: Verify the passwords in the security configured URL are
not corrupt or missing. Reset the affected password through the WebSphere
Administrative console if possible. If all else fails, reset the password
to its plain text value in the security configured URL (which is usually sas.server.props).
SECJ0106E: An unexpected exception occurred when encoding the value [{0}]
for password [{1}] in the security configured URL Explanation:
The password cannot be encoded because it is missing or malformed.
User Response: Verify the passwords in the security configured URL are
not corrupt or missing. Reset the affected password through the WebSphere
Administrative console if possible. If all else fails, reset the
password to its plain text value in the security configured URL (which is
usually sas.server.props).
SECJ0107W: The {0}
file does not exist Explanation: User Response: If
this message is from a warning, then it is a temporary problem with is usually
recovered from automatically. If it is not a warning, then check the file
permissions for the file to ensure they are readable. If the file
is missing, restore it. SECJ0108E: Unexpected exception
occurred when getting user registry or registry attributes. Explanation:
User Response: Verify that the user registry has been configured
in WebSphere properly. SECJ0109W: Recovering ({0}) from ({1})
Explanation: The security configured URL is being recovered
from the future version. This may happen if the security configured URL is
missing or has been deleted. User Response: None
SECJ0110E: I/O Error occurred when loading property URL {0} Explanation:
A loadProperties() operation probably failed. User Response: Verify
the file permissions associated with security configured URL property file
(typically sas.server.props) are read and write.
SECJ0111W: RunAsMap Not defined properly for Application {0} Explanation:
The run-as-bindings size is zero for this application. User Response:
Verify that the run-as bindings are specified for the application if necessary.
SECJ0112W: Authorization Table Not defined for Application {0}
Explanation: No security constraints or roles have been defined for this
application. User Response: If no security is necessary for this
application then ignore this message. Otherwise, review the security
requirements of this application. SEJ0113E: An unexpected
exception occurred in getRequiredRoles for method {0} and resource {1}
Explanation: An internal error occurred. User Response: Review
the roles associated with the method and resource. Contact your service
representative if the problem persist. SECJ0114W: Unable
to extract the security attributes from the credential Explanation:
The credential may be malformed or corrupt. User Response: This
is an internal error. Contact your service representative if the problem
persist. SECJ0115W: The credential has a null value for
the public name Explanation: The credential is possibly malformed
or corrupt. User Response: This is an internal error. Contact
your service representative if the problem persist. SECJ0116W:
Unable to extract the credential token from the credential Explanation:
The credential is possibly malformed or corrupt. User Response:
This is an internal error. Contact your service representative if
the problem persist. SECJ0117A: Form login failed for user
{0} Explanation: The user could not be authenticated by the
FormLogin Servlet. The user id or password may have been entered
incorrectly. The user may not exist in the user registry that
WebSphere is configured to authenticate to. User Response: Verify
that the user id and password are entered correctly. Consult with the
administrator of the user registry if the problem persist.
SECJ0118E: Authentication error during authentication for user {0}
Explanation: An unexpected error occurred during authentication.
User Response: This is an internal error. Look for previous messages
that may be related to the failure. SEJ0119E: Error getting
the web app information for form login Explanation: This
is an internal error. User Response: Verify the web application
is properly configured. Contact your service representative if the problem
persist. SECJ0120A: Trust Association Init loaded {0} interceptor(s)
Explanation: Reports the number of Trust Association interceptors
that have been added. User Response: None, informational only. SECJ0121A:
Trust Association Init class {0} loaded successfully Explanation:
User Response: None, informational only.
SECJ0122A: Trust Association Init Interceptor signature: {0} Explanation:
Reports the signature of the Trust Association interceptor. User
Response: None, informational only. SECJ0123E: Trust
Association Init Error retrieving class loader. TrustAssociation cannot be
enabled. Explanation: getClassLoader() operation returned null.
User Response: Verify the appropriate Trust Association classes are installed
and the classpath is correct. SECJ0124E: Trust Association
Init No interceptor class {0} found Explanation: The interceptor
class file specified in trustedservers.properties cannot be found.
User Response: Verify the appropriate Trust Association classes are installed
and the classpath is correct. Also verify the class specified in the trustedservers.properties
file and that the file has at least the read permission.
SECJ0125E: Trust Association Init Unable to load Trust Association class {0}
Explanation: A ClassNotFoundException occurred when trying
to load the subject class. User Response: Verify the appropriate
Trust Association classes are installed and the classpath is correct.
SECJ0126E: TrustAssociation failed during validation. Explanation:
When the appropriate interceptor is found for a given request, that interceptor
then validates its trust with the reverse proxy server. This error message suggests
that the validation has failed and therefore the reverse proxy cannot
be trusted. For example, an incorrect password may have been provided.
User Response: In a production environment, the user may be alerted to
check if there is an intruder in the system. In a development environment in
which testing is underway, verify if the expected inputs from the reverse
proxy server is in fact being passed to the interceptor correctly. The
nature of these inputs really depends on how trust association is being established.
For example, the simplest method would be to pass a username/password through
the Basic Authority header. SECJ0128E: An unexpected exception
occurred during TrustAssociation Explanation: This refers to
all other exceptions that can be possibly thrown by an interceptor, when validating trust
with the reverse proxy server and when getting the authenticated username, aside
from WebTrustAssociationFailedException and WebTrustAssociationUserException.
User Response: Debug the problem from the stack trace that is printed
together with this error message. You can also turn on the debug trace to
get more information about the nature of the exception.
SECJ0129A: Authorization failed for {0} while invoking {1} on {2}
Explanation: The user does not have the necessary permission to access
the resource. User Response: Contact your WebSphere security administrator
if this is unexpected. The user must be mapped to one the roles protecting
the resource if the user requires access to the protected resource. SECJ0130E:
Unable to get source path from request header 'via' Explanation: When
using WebSealTrustAssociationInterceptor, the "via" HTTP header in the
HTTP Request object will be examined. This message appears when the value
for this header is invalid or corrupted. User Response: Make sure
that WebSeal and/or the HTTP Server is properly working.
SECJ0131E: Authentication failed. Unable to get the mapped credential for
SecOwnCredentials. Explanation: This is an internal error.
User Response: Contact your service representative if the problem persist.
SECJ0132A: Java 2 Security Manager is installed and enabled Explanation:
User Response: None, informational only.
SECJ0133A: Illegal {0} \: {1} Explanation: An illegal Permission
was attempted. Only the main thread can set the security manager.
User Response: Verify the code that is trying to set the security manager
is not trying to subvert the Websphere security manager.
SECJ0134A: Permission {0} denied with exception message {1} Explanation:
The Java Security Manager checkPermission() threw a SecurityException
on the subject Permission. User Response: Verify the attempted
operation is permitted. SECJ0135A: Illegal System.exit()
attempted Explanation: Only the main thread is allowed to exit
the Java VM User Response: Verify the code attempting the system
exit is not trying to subvert the WebSphere security manager. SESN0001E: SessionContext:
Couldn't stop invalidation thread Explanation: Failed to stop
session invalidation thread when reading updated configuration values.
User Response: Latest configuration values involving invalidation may
not be in use. Restart the server in order to pick up the latest values.
SESN0002E: SessionContext: Unknown host exception occurred Explanation:
Failed to determine the host internet address. User Response:
Restart server, if problem persists then contact service.
SESN0003E: SessionContext: The invalidation thread was interrupted by the
JVM Explanation: The Java Virtual Machine interrupted the invalidation
thread. User Response: Restart the server.
SESN0004E: SessionContext: An exception occurred while running the invalidation
thread Explanation: The session invalidation thread encountered
an exception. User Response: Restart server, if problem persists
then contact service.
SESN0005E: SessionContext: An error
occurred with configuration parameters Explanation: An error
was encountered while processing Session Manager configuration values.
User Response: Check/correct Session Manager configuration values and
restart the server.
SESN0006E: SessionContext: Attempted
to create a session while Session Manager was stopped. Explanation:
This could occur when a session request is received while Session Manager
is stopped or reading new configuration values. User Response: Start
the Session Manager.
SESN0007E: SessionContext: Attempted
to access a session while Session Manager was stopped Explanation:
This could occur when a session request is received while Session Manager
is stopped or reading new configuration values. User Response: Start
the Session Manager.
SESN0008E: SessionContext: A user
authenticated as {0} has attempted to access a session owned by {1}
Explanation: An attempt was made to access a session by an unauthenticated
user or a different authenticated name. User Response: If Integrate
WebSphere Security is enabled in the Session Manager then all requests that
are part of the same session must share a common authentication identity.
SESN0009E: SessionContext: Unable to load IBM JCE, will use default ID generator
Explanation: The IBM JCE random session ID generator encountered
an error. Therefore, the default IBM session ID generator will be used.
User Response: Check to see if {WAS_ROOT}/java/jre/lib/security/java.security
has com.ibm.crypto.provider.IBMJCE is a security provider. If not, add the
entry security.provider.2=com.ibm.crypto.provider.IBMJCE
SESN0010E: BackedHashtableMR: Exception getting properties of the session
Explanation: None. User Response: If a SQLException
has occurred then refer to the appropriate database documentation for your
environment. For example, if the Session Manager is configured for a DB2 datasource
then refer to the DB2 documentation. Also, ensure that you have properly configured
a datasource and have configured the Session Manager to use that datasource.
Ensure that the datasource pools and timeouts are appropriate for your environment.
After fixing the database problem, restart the server. If it is not
an SQLException, contact service.
SESN0011E: SessionContext:
setSessionTimeoutInfo error Explanation: An exception was encountered
while processing the session invalidation timeout values. User Response:
Assure that the invalidation time specified in the Session Manager configuration
and the session timeout value configured in the web application are correct
and restart the server.
SESN0012E: SessionData: putValue
- null key entered Explanation: The HttpSession.putValue or
HttpSession.setAttribute method was called from a servlet/JSP with a null
key. User Response: Fix the servlet/JSP.
SESN0013E:
SessionData: putValue - null value entered Explanation: The
HttpSession.putValue or HttpSession.setAttribute method was called from a
servlet/JSP with a null value. User Response: Fix the servlet/JSP.
SESN0014E: DatabaseSessionContext:initalizeParameters - problem accessing
configuration parameters Explanation: Error processing Session
Manager configuration values. User Response: Check/correct Session
Manager configuration values relating to database and restart the server.
SESN0015E: DatabaseSessionContext:processInvalidList - problem invalidating
session Explanation: The database invalidation of timed out
sessions has encountered an error. User Response: If an SQLException
has occurred, refer to the appropriate database documentation for your
environment. For example, if the Session Manager is configured for a DB2 datasource
then refer to the DB2 documentation. Also, assure that you have properly configured
a datasource and have configured the Session Manager to use that datasource.
Ensure that the datasource pools and timeouts are appropriate for your environment.
After fixing the database problem restart the server. If it is not an SQLException,
contact service.
SESN0016E: DatabaseSessionContext:performInvalidation
detected an error Explanation: The database invalidation of
timed out sessions has encountered an error. User Response: If
an SQLException has occurred, refer to the appropriate database documentation
for your environment. For example, if the Session Manager is configured for
a DB2 datasource then refer to the DB2 documentation. Also, ensure that you
have properly configured a datasource and have configured the Session Manager
to use that datasource. Ensure that the datasource pools and timeouts are
appropriate for your environment. After fixing the database problem restart
the server. If it is not a SQLException, contact service.
SESN0017E: DatabaseSessionContext: Couldn't stop PropertyWriter thread
Explanation: Failed to stop TimeBasedWriter thread when reading updated
configuration values. User Response: Latest configuration values
may not be in use. Restart the server in order to pick up the latest values.
SESN0018E: DatabaseSessionContext: The PropertyWriter thread was interrupted
by the JVM Explanation: The Java Virtual Machine interrupted
the TimeBasedWriter thread. User Response: Restart the server.
SESN0019E: checkMinimumInvalidationError detected that TimeBaseWrite invalidation
time was not at least three times the Write Interval. This has been corrected
Explanation: When TimeBasedWrite is used, the invalidation
time must be at least three times the TimeBasedWrite Interval to assure that
a session is not prematurely timed out. This condition was automatically corrected.
User Response: Update the Session Manager configuration so that Invalidation
time is at least three times the TimeBasedWrite Interval. Note that the invalidation
time is also configured as session timeout in the Web application definition.
SESN0020E: checkMinimumInvalidationError encountered a problem checking minimum
Invalidation time Explanation: None. User Response:
Restart server, if problem persists then contact service.
SESN0021E: DatabaseSessionContext: An exception occurred while running the
PropertyWriter thread Explanation: The TimeBasedWriter thread
has encountered an exception. User Response: Restart server, if
problem persists then contact service.
SESN0022E: DatabaseSessionData:
A problem occurred reading the creation time field from the database
Explanation: None. User Response: If a SQLException has occurred
then refer to the appropriate database documentation for your environment.
For example, if the Session Manager is configured for a DB2 datasource then
refer to the DB2 documentation. Also, ensure that you have properly
configured a datasource and have configured the Session Manager to use that
datasource. Ensure that the datasource pools and timeouts are appropriate
for your environment. After fixing the database problem restart the server.
If it is not a SQLException then contact service.
SESN0023E:
DatabaseSessionData: A problem occurred reading the maximum inactive interval
field from the database Explanation: None. User Response:
If a SQLException has occurred, refer to the appropriate database documentation
for your environment. For example, if the Session Manager is configured for
a DB2 datasource, refer to the DB2 documentation. Also, ensure you have properly
configured a datasource and have configured the Session Manager to use that
datasource. Ensure that the datasource pools and timeouts are appropriate
for your environment. After fixing the database problem restart the server.
If it is not a SQLException then contact service.
SESN0024E:
DatabaseSessionData: A problem occurred reading the application name field
from the database Explanation: None. User Response:
If an SQLException has occurred, refer to the appropriate database documentation
for your environment. For example, if the Session Manager is configured for
a DB2 datasource, refer to the DB2 documentation. Also, ensure that you have
properly configured a datasource and have configured the Session Manager to
use that datasource. Ensure that the datasource pools and timeouts are appropriate
for your environment. After fixing the database problem, restart the
server. If it is not an SQLException then contact service.
SESN0025E: DatabaseSessionData: A problem occurred reading the user name field
from the database Explanation: None. User Response:
If an SQLException has occurred, refer to the appropriate database
documentation for your environment. For example, if the Session Manager is
configured for a DB2 datasource then refer to the DB2 documentation. Also,
ensure that you have properly configured a datasource and have configured
the Session Manager to use that datasource. Ensure that the datasource pools
and timeouts are appropriate for your environment. After fixing the database
problem, restart the server. If it is not an SQLException, contact service.
SESN0026E: DatabaseSessionData: A problem occurred processing HttpSessionBindingListeners
stored in the database Explanation: None. User Response:
If an SQLException has occurred, refer to the appropriate database documentation
for your environment. For example, if the Session Manager is configured for
a DB2 datasource, refer to the DB2 documentation. Also, ensure that
you have properly configured a datasource and have configured the Session
Manager to use that datasource. Ensure that the datasource pools and timeouts
are appropriate for your environment. After fixing the database problem, restart
the server. If it is not an SQLException then contact service.
SESN0027E: DatabaseSessionData: A problem occurred reading the listener count
field from the database Explanation: None. User Response:
If an SQLException has occurred, refer to the appropriate database documentation
for your environment. For example, if the Session Manager is configured for
a DB2 datasource, refer to the DB2 documentation. Also, ensure that you have
properly configured a datasource and have configured the Session Manager to
use that datasource. Ensure that the datasource pools and timeouts are appropriate
for your environment. After fixing the database problem restart the server.
If it is not an SQLException, contact service.
SESN0028E:
DatabaseSessionData.convertObject: Encountered an exception getting an EJB
Object using the EJB Handle. Explanation: The EJBObject was
previously put to the session. A RemoteException was encountered while issuing
getEJBObject() from Handle. User Response: Refer to EJB documentation.
SESN0029E: DatabaseSessionData.convertObject: Encountered an exception getting
an EJB Home using the EJB Home Handle. Explanation: The EJBHome
was previously put to the session. A RemoteException was encountered while
issuing getEJBHome() from Handle. User Response: Refer to EJB documentation.
SESN0030E: DatabaseSessionData.convertObject: Encountered an exception getting
at Initial Context. Explanation: An InitialContext was previously
put to the session. A NamingException was encountered while reconstructing
javax.naming.InitialContext(). User Response: Refer to naming server
documentation for the error message.
SESN0031E: DatabaseSessionData.putValueGuts:
Encountered an exception getting EJB Home Explanation: An EJBHome
was put to the session. A RemoteException occurred while issuing getHomeHandle().
User Response: Refer to EJB documentation.
SESN0032E:
DatabaseSessionData.putValueGuts: Encountered an exception getting EJB Handle
Explanation: An EJBObject was put to the session. A RemoteException
occurred while issuing getHandle(). User Response: Refer to EJB
documentation.
SESN0033E: DatabaseSessionData.putValueGuts:
A javax.naming.Context was put to the session. A RemoteException occurred
while issuing getEnvironment()on javax.naming.Context. Explanation:
A javax.naming.Context was put into the session. Exception occurred while
getting at the environment from the javax.naming.Context object. User
Response: Refer to naming server documentation for the error message.
SESN0034E: DatabaseSessionData.getSwappableListeners: class not found
Explanation: An attempt to deserialize a session object from the database
has resulted in a ClassNotFoundException. The object to be deserialized must
be contained in the classpath for all JVMs that can access the session. Another
possibility is that the serialized object definition has been changed after
the object was serialized. User Response: Assure that all JVMs
that can access this session have the classpath set appropriately.
SESN0035E: BackedHashtable:removeSessions - database error Explanation:
An exception was encountered while attempting to remove a session from
the database. User Response: If an SQLException has occurred, refer
to the appropriate database documentation for your environment. For example,
if the Session Manager is configured for a DB2 datasource, refer to the DB2
documentation. Also, ensure that you have properly configured a datasource
and have configured the Session Manager to use that datasource. Ensure that
the datasource pools and timeouts are appropriate for your environment. After
fixing the database problem, restart the server. If it is not a SQLException
then contact service.
SESN0036E: BackedHashtable:doInvalidations
- database error Explanation: An exception was encountered
while attempting to remove a session from the database. User Response:
If a SQLException has occurred then refer to the appropriate database
documentation for your environment. For example, if the Session Manager is
configured for a DB2 datasource then refer to the DB2 documentation. Also,
assure that you have properly configured a datasource and have configured
the Session Manager to use that datasource. Assure that the datasource pools
and time-outs are appropriate for your environment. After fixing the database
problem restart the server. If it is not a SQLException then contact service.
SESN0037E: BackedHashtable:pollForInvalids - database error Explanation:
An exception was encountered while attempting to search for expired sessions
that contain listener objects. User Response: If a SQLException
has occurred then refer to the appropriate database documentation for your
environment. For example, if the Session Manager is configured for a DB2 datasource
then refer to the DB2 documentation. Also, assure that you have properly configured
a datasource and have configured the Session Manager to use that datasource.
Assure that the datasource pools and time-outs are appropriate for your environment.
After fixing the database problem restart the server. If it is not a SQLException
then contact service.
SESN0038E: BackedHashtable: getConnection
- database error Explanation: An exception was encountered
while attempting to get a database connection User Response: If
an SQLException has occurred, refer to the appropriate database documentation
for your environment. For example, if the Session Manager is configured for
a DB2 datasource, refer to the DB2 documentation. Also, ensure that you have
properly configured a datasource and have configured the Session Manager to
use that datasource. Assure that the datasource pools and timeouts are appropriate
for your environment. After fixing the database problem restart the server.
If it is not an SQLException then contact service.
SESN0039E:
BackedHashtable:selectAndLock - database error Explanation: None.
User Response: If a SQLException has occurred then refer to the appropriate
database documentation for your environment. For example, if the Session Manager
is configured for a DB2 datasource then refer to the DB2 documentation. Also,
assure that you have properly configured a datasource and have configured
the Session Manager to use that datasource. Assure that the datasource pools
and timeouts are appropriate for your environment. After fixing the database
problem restart the server. If it is not a SQLException then contact service.
SESN0040E: BackedHashtable: commonSetup - problem streaming object
Explanation: Exception caught while trying to serialize session data for
subsequent database write. User Response: The session data may
be too large to serialize. Either put less data in the session or consider
configuring Session Manager for multirow database mode.
SESN0041E: BackedHashtable: ejbStore - database error for session
Explanation: An exception was encountered when attempting to store a session
to database. User Response: If an SQLException has occurred, refer
to the appropriate database documentation for your environment. For example,
if the Session Manager is configured for a DB2 datasource, refer to the DB2
documentation. Also, ensure that you have properly configured a datasource
and have configured the Session Manager to use that datasource. ensure that
the datasource pools and timeouts are appropriate for your environment. After
fixing the database problem, restart the server. If it is not an SQLException
then contact service.
SESN0042E: BackedHashtable: ejbCreate
- database error Explanation: An exception was encountered
when attempting to store a session to database. User Response: If
an SQLException has occurred, refer to the appropriate database documentation
for your environment. For example, if the Session Manager is configured for
a DB2 datasource, refer to the DB2 documentation. Also, ensure that you have
properly configured a datasource and have configured the Session Manager to
use that datasource. Ensure that the datasource pools and timeouts are appropriate
for your environment. After fixing the database problem, restart the server.
If it is not an SQLException then contact service.
SESN0043E:
BackedHashtable: Problem obtaining the configured datasource Explanation:
The Session Manager cannot find the configured datasource. User
Response: Ensure that you have properly configured a datasource. When
Session Manager persistence is enabled the Session Manager configuration must
contain a valid datasource.
SESN0044E: BackedHashtable:
problem occurred reading in a single object of the application data for a
session from the database Explanation: An exception was encountered
when the getValue()/getAttribute() method was called to read the value from
the database. User Response: If a SQLException has occurred, refer
to the appropriate database documentation for your environment. For example,
if the Session Manager is configured for a DB2 datasource, refer to the DB2
documentation. Also, ensure that you have properly configured a datasource
and have configured the Session Manager to use that datasource. Ensure that
the datasource pools and timeouts are appropriate for your environment. After
fixing the database problem, restart the server. If it is not an SQLException,
contact service.
SESN0045E: BackedHashtable: Problem sending
asynchronous last access updates to the database Explanation:
None. User Response: If an SQLException has occurred refer
to the appropriate database documentation for your environment. For example,
if the Session Manager is configured for a DB2 datasource, refer to the DB2
documentation. Also, ensure that you have properly configured a datasource
and have configured the Session Manager to use that datasource. Ensure that
the datasource pools and timeouts are appropriate for your environment. After
fixing the database problem, restart the server. If it is not a SQLException,
contact service.
SESN0046E: BackedHashtable: A database
error occurred while organizing sessions after a web application reload
Explanation: None. User Response: If an SQLException has occurred, refer
to the appropriate database documentation for your environment. For example,
if the Session Manager is configured for a DB2 datasource, refer to the DB2
documentation. Also, ensure that you have properly configured a datasource
and have configured the Session Manager to use that datasource. Ensure that
the datasource pools and timeouts are appropriate for your environment. After
fixing the database problem, restart the server. If it is not an SQLException
then contact service.
SESN0047E: BackedHashtable:initConnPool
- problem creating a table for sessions Explanation: None.
User Response: If an SQLException has occurred, refer to the appropriate
database documentation for your environment. For example, if the Session Manager
is configured for a DB2 datasource, refer to the DB2 documentation. Also,
ensure that you have properly configured a datasource and have configured
the Session Manager to use that datasource. Ensure that the datasource pools
and timeouts are appropriate for your environment. After fixing the database
problem, restart the server. If it is not an SQLException, contact service.
SESN0048E: BackedHashtable:createTable - SQL Exception during CreateTable
Explanation: None. User Response: If an SQLException
has occurred, refer to the appropriate database documentation for your environment.
For example, if the Session Manager is configured for a DB2 datasource, refer
to the DB2 documentation. Also, ensure that you have properly configured a
datasource and have configured the Session Manager to use that datasource.
Ensure that the datasource pools and timeouts are appropriate for your environment.
After fixing the database problem, restart the server. If it is not an SQLException,
contact service.
SESN0049E: BackedHashtable: dropTable
- Dropping old sessions table Explanation: The Session Manager
has detected that the Sessions table was in an out-of-date format. The old
table has been dropped and a new table will be created. User Response:
None.
SESN0050E: BackedHashtable:dropTable: Exception
dropping sessions table - You should drop the sessions table manually
Explanation: The Session Manager has detected that the Sessions table
was in an out-of-date format. The old table could not be dropped automatically.
User Response: The user should manually drop the sessions table and restart
the server.
SESN0051E: BackedHashtable: getValue - class
not found Explanation: An attempt to deserialize a session
object from the database has resulted in a ClassNotFoundException. The object
to be deserialized must be contained in the classpath for all JVMs that can
access the session. Another possibility is that the serialized object definition
has been changed after the object was serialized. User Response: Ensure
that all JVMs accessing this session have the classpath set appropriately.
SESN0052E: BackedHashtable.getSession - error updating last acc time
Explanation: None. User Response: If an SQLException has occurred,
refer to the appropriate database documentation for your environment. For
example, if the Session Manager is configured for a DB2 datasource, refer
to the DB2 documentation. Also, ensure that you have properly configured a
datasource and have configured the Session Manager to use that datasource.
Assure that the datasource pools and timeouts are appropriate for your environment.
After fixing the database problem, restart the server. If it is not
an SQLException, contact service.
SESN0053E: BackedHashtable.checkValidity
- error checking session validity Explanation: None.
User Response: If an SQLException has occurred, refer to the appropriate
database documentation for your environment. For example, if the Session Manager
is configured for a DB2 datasource, refer to the DB2 documentation. Also,
ensure that you have properly configured a datasource and have configured
the Session Manager to use that datasource. Ensure that the datasource pools
and timeouts are appropriate for your environment. After fixing the database
problem, restart the server. If it is not an SQLException, contact service.
SESN0054E: BackedHashtable.removeNonCachedSessionError - error removing Cached
session Explanation: An exception was encountered while attempting
to remove a session from the database. User Response: If an SQLException
has occurred, refer to the appropriate database documentation for your environment.
For example, if the Session Manager is configured for a DB2 datasource, refer
to the DB2 documentation. Also, ensure that you have properly configured a
datasource and have configured the Session Manager to use that datasource.
Ensure that the datasource pools and timeouts are appropriate for your environment.
After fixing the database problem, restart the server. If it is not
an SQLException, contact service.
SESN0055E: BackedHashtable:handlePropertyHits
- An attempt was made to write more than 2M to large column Explanation:
None. User Response: The session data may be too large for
the database column. Either place less data in the session or consider configuring
Session Manager for multi-row database mode.
SESN0056E:
BackedHashtable.oracleGetValue - error encountered Explanation:
An exception was encountered when the getValue()/getAttribute() method
was called to read the value from the database. User Response: If
an SQLException has occurred, refer to the appropriate database documentation
for your environment. For example, if the Session Manager is configured for
an Oracle datasource, refer to the Oracle documentation. Also, ensure that
you have properly configured a datasource and have configured the Session
Manager to use that datasource. Ensure that the datasource pools and timeouts
are appropriate for your environment. After fixing the database problem, restart
the server. If it is not an SQLException, contact service.
SESN0057E: BackedHashtableMR: A problem storing application data changes to
the database Explanation: None. User Response: If
an SQLException has occurred, refer to the appropriate database documentation
for your environment. For example, if the Session Manager is configured for
a DB2 datasource, refer to the DB2 documentation. Also, ensure that you have
properly configured a datasource and have configured the Session Manager to
use that datasource. Ensure that the datasource pools and timeouts are appropriate
for your environment. After fixing the database problem, restart the
server. If it is not an SQLException, contact service.
SESN0058E: BackedHashtableMR: A problem occurred inserting a new session into
the database Explanation: None. User Response: If
an SQLException has occurred, refer to the appropriate database documentation
for your environment. For example, if the Session Manager is configured for
a DB2 datasource, refer to the DB2 documentation. Also, ensure that
you have properly configured a datasource and have configured the Session
Manager to use that datasource. Ensure that the datasource pools and timeouts
are appropriate for your environment. After fixing the database problem, restart
the server. If it is not an SQLException, contact service.
SESN0059E: SessionContextRegistry: A problem occurred processing a configuration
from the session active object Explanation: None. User
Response: Check/correct Session Manager configuration values and restart
the server. If problem persists, contact service.
SESN0060E:
SessionContextRegistry: A problem occurred creating a session context
Explanation: None. User Response: Check/correct Session Manager
configuration values and restart the server. If problem persists, contact
service.
SESN0061E: SessionContextRegistry: A problem occurred
creating the session PMI instrumentation Explanation: None.
User Response: Check/correct PMI configuration values and restart the
server. If problem persists, contact service.
SESN0062E:
BackedHashtable.handleAsyncUpdates detected an exception Explanation:
An exception has been detected while attempting to update the database
with the session last access times. User Response: If an SQLException
has occurred, refer to the appropriate database documentation for your environment.
For example, if the Session Manager is configured for a DB2 datasource, refer
to the DB2 documentation. Also, assure that you have properly configured a
datasource and have configured the Session Manager to use that datasource.
Assure that the datasource pools and timeouts are appropriate for your environment.
After fixing the database problem, restart the server. If it is not an SQLException,
contact service.
SESN0063E: BackedHashtable.selectNoUpdateError
- Exception in selectNoUpdate Explanation: None. User
Response: If an SQLException has occurred, refer to the appropriate database
documentation for your environment. For example, if the Session Manager is
configured for a DB2 datasource, refer to the DB2 documentation. Also, ensure
that you have properly configured a datasource and have configured the Session
Manager to use that datasource. Ensure that the datasource pools and timeouts
are appropriate for your environment. After fixing the database problem, restart
the server. If it is not an SQLException, contact service.
SESN0100E: UPManagerBean - Error in finding by {0} Explanation:
Error finding the user profile with given identity. User Response:
The user profile you are querying may not have been created.
SESN0101E: UPManagerBean - Error in getting Read Only Bean Home
Explanation: Error getting at read only enterprise bean home from naming
server. User Response: Check whether read only enterprise bean
is deployed correctly with the jndi name specified in xml file.
SESN0102E: UPManagerBean - Error in getting Read Write Bean Home
Explanation: Error getting at read write enterprise bean home from naming
server. User Response: Check whether read write enterprise bean
is deployed correctly with the jndi name specified in xml file.
SESN0103E: UPManagerBean - error accessing IntialContext Explanation:
Unable to get at InitialContext. User Response: Refer to naming
server documentation for the error message. Correct and restart server. If
problem persists, contact service.
SESN0104E: UserProfileManager
- UserProfile not Enabled Explanation: Userprofile is accessed
while userprofile is turned off. User Response: Enable the userprofile
in userprofile.xml located in properties folder.
SESN0105E:
UserProfileManager - Error initializing specified classes Explanation:
Server was unable to load the specified classes in xml file. User
Response: Check whether classes specified in xml files are in application
classpath.
SESN0106E: UserProfileManager - Error while
initializing from Active Object Explanation: Error initializing
the userprofile manager. User Response: Check userprofile.xml in
properties folder for any missing elements.
SESN0107E:
UserProfileManager - Error while getting properties from XML Explanation:
Error initializing the userprofile manager from xml file. User
Response: Check userprofile.xml in properties folder for any missing elements.
SESN0108E: UserProfileManager - user {0} already exists Explanation:
Unable to add userprofile with given identity. User Response:
Userprofile with given identity already exists.
SESN0109E:
UserProfileManager - error initializing DataWrapper class Explanation:
Error initializing the datawrapper class specified in userprofile.xml
file. User Response: Datawrapper class specified in xml file should
be present in classpath.
SESN0110E: UserProfileManager
- error while accessing Manager Bean Explanation: Error accessing
userprofile manager enterprise bean. User Response: Check whether
userprofile beans were properly deployed and started.
SESN0111E: UserProfileManager - unable to find {0} Explanation:
Error finding the userprofile with given identity. User Response:
The userprofile you are querying may not have been created.
SESN0112E: UserProfileManager - unable to find userprofiles by {0}
Explanation: Error accessing userprofiles by given property. User
Response: Check whether userprofile beans were properly deployed and started.
SESN0113E: UserProfileManager - error removing user {0} Explanation:
Error removing the specified userprofile. User Response: The
userprofile you are trying to remove may not be present.
SESN0114E: UserProfileManager - error while getting new columns from extended
class {0} Explanation: Unable to get at new columns from the
extended datawrapper class. User Response: Datawrapper class specified
in xml file should be present in classpath.
SESN0115E:
UserProfile - error in userprofile Explanation: Error occurred
in userprofile management. User Response: Check the logs for userprofile
exceptions. If problem persists, contact service. SMTL0001I: Cannot
load a manifest file: {0} {1} Explanation: None. User
Response: None.
SMTL0002E: Encountered an invalid transaction
attribute: {0} Explanation: None. User Response: None.
SMTL0003W: There are no public fields in the class: {0} Explanation:
None. User Response: None.
SMTL0004E: Encountered
an invalid public bean method: {0} Explanation: None.
User Response: None.
SMTL0005W: Exception thrown by
discard strategy {0} {1} Explanation: None. User Response:
None.
SMTL0006E: Encountered the IOException exception
in the getBinaryStream method {0} Explanation: None.
User Response: None.
SMTL0007W: Failure to register
trace event listener: {0} Explanation: None. User Response:
None.
SMTL0008W: TraceSpec processing error: {0} {1}
Explanation: None. User Response: None.
SMTL0009W: Failure to recognize key(s) in a descriptor file: {0}
Explanation: None. User Response: None.
SMTL0010W: Exception on database query (read by primary key):
Explanation: None. User Response: None.
SMTL0011W: Trying to get administrative node reference: administrative server
startup slow : could be a network/configuration issue Explanation:
None. User Response: None.
SMTL0012W: Waiting
for initial context {0} Explanation: None. User Response:
None.
SMTL0013E: Unable to access the bean's fields
Explanation: None. User Response: None.
SMTL0014W: TraceSpec processing error: Explanation: None.
User Response: None.
SMTL0015W: An error occurred while
stopping the administrative server {0} Explanation: None.
User Response: None.
SMTL0016E: Failure to open a deployment
descriptor file Explanation: None. User Response: None.
SMTL0017E: Encountered an invalid isolation level: {0} Explanation:
None. User Response: None.
SMTL0018I: DrAdmin
available on port {0} Explanation: None. User Response:
None.
SMTL0019E: Failure to get a class object: {0}
Explanation: None. User Response: None.
SMTL0020W: An exception occurred during database query (find all):
Explanation: None. User Response: None.
SMTL0021E: Failure to load a bean class Explanation: None.
User Response: None.
SMTL0022E: Encountered an invalid
container managed field: {0} Explanation: None. User
Response: None.
SMTL0023W: No value is specified for
the key: {0} Explanation: None. User Response: None.
SMTL0024E: Unable to get the bean's methods Explanation: None.
User Response: None.
SMTL0025E: Exception caught :
{0} Explanation: None. User Response: None.
SMTL0026E: Failure to create a data source: {0} Explanation: None.
User Response: None.
SMTL0027W: An exception occurred
during database update: {0} {1} Explanation: None.
User Response: None.
SMTL0028W: An exception occurred
during database query (read for update by primary key): Explanation:
None. User Response: None.
SMTL0029W: LRU
thread was interrupted. Terminating. {0} Explanation: None.
User Response: None.
SMTL0030E: Failure to open an
environment properties file Explanation: None. User
Response: None.
SMTL0031E: Unable to get the bean's
home name Explanation: None. User Response: None.
SMTL0032E: Exception caught: {0} Explanation: None.
User Response: None.
SMTL0033W: Stopping node: {0}
Explanation: None. User Response: None.
SMTL0034E: Encountered an invalid RunAs mode: {0} Explanation:
None. User Response: None.
SMTL0035W: Caught
Exception: {0} Explanation: None. User Response: None.
SMTL0036W: An exception occurred during LRU sweep {0} {1} Explanation:
None. User Response: None.
SMTL0037E: Unable
to access a bean class: {0} Explanation: None. User
Response: None.
SMTL0038I: Connection attempt has exceeded
the threshold DrAdmin exits Explanation: None. User
Response: None.
SMTL0039W: An exception occurred during
database query: {0} {1} Explanation: None. User Response:
None.
SMTL0040W: Failure to register trace event listener:
Explanation: None. User Response: None. SRVE0001E: Failure to create
shared servlet context Explanation: None. User Response:
None.
SRVE0002E: Illegal Argument Exception: Error
reading bootstrap file Explanation: None. User Response:
None.
SRVE0003I: Using /default servlet_engine for
configuration data Explanation: None. User Response:
None.
SRVE0004W: Illegal Argument Exception: Invalid
transport name: {0} Explanation: None. User Response:
None.
SRVE0005E: Failure to add WebGroup {0}
Explanation: None. User Response: None.
SRVE0006E: JNDI Error Explanation: None. User Response:
None.
SRVE0007E: Internal Error: Connection queue
overflow Explanation: None. User Response: None.
SRVE0008E: iiopredirector XML contains invalid XML syntax Explanation:
None. User Response: None.
SRVE0009W: Invalidation
Exception: JarFileClassProvider is invalid. File has been deleted
Explanation: None. User Response: None.
SRVE0010E: Illegal State Exception: JSPSupport is already owned by another
Web application Explanation: None. User Response: None.
SRVE0011E: Illegal Argument Exception: Trying to write < 0 chars
Explanation: None. User Response: None.
SRVE0012E: Error creating Initial Systems Management Configuration
Explanation: None. User Response: None.
SRVE0013E: MalformedXMLInfoException: Missing name in init-parameter
Explanation: None. User Response: None.
SRVE0014E: Uncaught service() exception root cause {0}: {1} Explanation:
None. User Response: None.
SRVE0015E: Failure
to initialize Web application {0} Explanation: None.
User Response: None.
SRVE0016E: Illegal Argument Exception:
Invalid header format Explanation: None. User Response:
None.
SRVE0017W: Web Group not found: {0}
Explanation: None. User Response: None.
SRVE0018E: Error occurred while reloading servlet group: {0} Explanation:
None. User Response: None.
SRVE0019E: Place
your servlet's class on classpath of the application server {0}: {1}
Explanation: None. User Response: None.
SRVE0020E: [Servlet Error]-[{0}]: {1}: {2} Explanation: None.
User Response: None.
SRVE0021I: Servlet unloaded: {0}
Explanation: None. User Response: None.
SRVE0022E: Unable to locate a matching Virtual Host: {0} Explanation:
None. User Response: None.
SRVE0023E: Web
Group not found Explanation: None. User Response: None.
SRVE0024E: Failure to set attribute Explanation: None.
User Response: None.
SRVE0025E: Error creating queue.properties/rules.properties
Explanation: None. User Response: None.
SRVE0026E: [Servlet Error]-[{0}]: {1} Explanation: None.
User Response: None.
SRVE0027E: Object Pool Exception:
Class not accessible to instantiate. Explanation: None.
User Response: None.
SRVE0028E: An error occured in
plug-in configuration Explanation: None. User Response:
None.
SRVE0029E: Unable to shutdown host
Explanation: None. User Response: None.
SRVE0030E: Root Cause Explanation: None. User Response:
None.
SRVE0031E: Illegal Argument Exception: {0} is
not a directory. Explanation: None. User Response: None.
SRVE0032I: [Servlet Message]-[{0}]: {1} Explanation: None.
User Response: None.
SRVE0033E: Unable to cleanly stop
the transport Explanation: None. User Response: None.
SRVE0034I: Servlet redirector is running Explanation: None.
User Response: None.
SRVE0035E: WebAppSecurityCollaborator
Explanation: None. User Response: None.
SRVE0036E: Remote Exception Explanation: None. User
Response: None.
SRVE0037E: Object is not serializable
Explanation: None. User Response: None.
SRVE0038E: Unable to initialize IIOPRedirector Transport Explanation:
None. User Response: None.
SRVE0039E: Error
Invoking Servlet {0} Explanation: None. User Response:
None.
SRVE0040W: Total read equals zero
Explanation: None. User Response: None.
SRVE0041E: Illegal Argument Exception: Bootstrap file not found
Explanation: None. User Response: None.
SRVE0042E: Illegal Argument Exception: Invalid content length
Explanation: None. User Response: None.
SRVE0043E: Internal Error Explanation: None. User Response:
None.
SRVE0044E: Servlet Exception: Missing resource:
{0} Explanation: None. User Response: None.
SRVE0045W: Invalidation Exception: JarFileClassProvider is invalid. File has
been updated Explanation: None. User Response: None.
SRVE0046E: An error occurred while creating an instance of the input class
Explanation: None. User Response: None.
SRVE0047E: An error occurred during destroy Explanation: None.
User Response: None.
SRVE0048I: Loading servlet: {0}
Explanation: None. User Response: None.
SRVE0049E: An error occurred during plug-in configuration notification
Explanation: None. User Response: None.
SRVE0050E: Illegal Argument Exception: JSPSupport can only be registered with
the name: {0} Explanation: None. User Response: None.
SRVE0051E: An internal engine error occurred while processing request
Explanation: None. User Response: None.
SRVE0052E: Unable to load specified configuration file Explanation:
None. User Response: None.
SRVE0053E: Illegal
Argument Exception: Invalid date format Explanation: None.
User Response: None.
SRVE0054E: An error occurred while
loading session context and Web application Explanation: None.
User Response: None.
SRVE0055I: Servlet wait for destroy
time-out has expired, destroy will be forced: {0} Explanation:
None. User Response: None.
SRVE0056E: Illegal
Argument Exception: Unsupported flag Explanation: None.
User Response: None.
SRVE0057E: Class Cast Exception:
Input class does not implement IPoolable Explanation: None.
User Response: None.
SRVE0058E: Did not realize destroy()
exception thrown by servlet {0}: {1} Explanation: None.
User Response: None.
SRVE0059E: Error handling invocation
Explanation: None. User Response: None.
SRVE0060E: Unable to bind host name [{0}] to servletHost [{1}]
Explanation: None. User Response: None.
SRVE0061E: Illegal Argument Exception: Invalid directory specified: {0}
Explanation: None. User Response: None.
SRVE0062I: Server name not specified. Using first servlet engine in configuration
file Explanation: None. User Response: None.
SRVE0063E: An internal engine error occurred while sending error to client:
{0} Explanation: None. User Response: None.
SRVE0064E: An error occurred while restarting Web application
Explanation: None. User Response: None.
SRVE0065E: AdminListener Explanation: None. User Response:
None.
SRVE0066I: Waiting for servlet to finish servicing
requests: {0} Explanation: None. User Response: None.
SRVE0067E: IllegalStateException: No Target Set Explanation: None.
User Response: None.
SRVE0068E: Did not realize service()
exception thrown by servlet {0}: {1} Explanation: None.
User Response: None.
SRVE0069I: Initializing Default
Server Explanation: None. User Response: None.
SRVE0070E: Error initializing for next request Explanation: None.
User Response: None.
SRVE0071E: Failed to retrieve
attribute names Explanation: None. User Response: None.
SRVE0072E: Transport Exception Explanation: None. User
Response: None.
SRVE0073E: Servlet Exception: Error
while finishing response Explanation: None. User Response:
None.
SRVE0074E: MalformedXMLInfoException: Unsupported
attribute type: {0} Explanation: None. User Response:
None.
SRVE0075E: Error reloading session context
Explanation: None. User Response: None.
SRVE0076E: IO Exception: Tried to write more than the content length
Explanation: None. User Response: None.
SRVE0077E: Servlet Exception: Could not load Web application {0}
Explanation: None. User Response: None.
SRVE0078E: Servlet Exception: non-HTTP request or response Explanation:
None. User Response: None.
SRVE0079E: Servlet
host not found Explanation: None. User Response: None.
SRVE0080E: Invalid content length Explanation: None.
User Response: None.
SRVE0081I: Started Default Server
Explanation: None. User Response: None.
SRVE0082E: Could not find resource /iiopredirector.xml Explanation:
None. User Response: None.
SRVE0083E: Failure
to restart WebGroup {0} Explanation: None. User Response:
None.
SRVE0084E: Class name malformed
Explanation: None. User Response: None.
SRVE0085E: Error initializing Default Server Explanation: None.
User Response: None.
SRVE0086E: Illegal Argument Exception:
Missing resource bootstrap properties Explanation: None.
User Response: None.
SRVE0087E: Failed to remove attribute
Explanation: None. User Response: None.
SRVE0088I: Creating Sample Server Configuration Explanation: None.
User Response: None.
SRVE0089E: Error getting remote
attribute: {0} Explanation: None. User Response: None.
SRVE0090E: Servlet Not Found Exception: {0} Explanation: None.
User Response: None.
SRVE0091I: [Servlet LOG]: {0}
Explanation: None. User Response: None.
SRVE0092I: [Servlet LOG]: {0}: {1} Explanation: None.
User Response: None.
SRVE0093E: Unable to create RemoteSRP
Bean Explanation: None. User Response: None.
SRVE0094E: Error loading ServletEngineInfo: {0} Explanation: None.
User Response: None.
SRVE0095I: Servlet has become
temporarily unavailable for service: {0} Explanation: None.
User Response: None.
SRVE0096E: Failed to start administrative
transport Explanation: None. User Response: None.
SRVE0097I: Servlet unload initiated: {0} Explanation: None.
User Response: None.
SRVE0098I: Generating plug-in
configuration for this node Explanation: None. User
Response: None.
SRVE0099E: Object Pool Exception: Class
could not be instantiated. Explanation: None. User Response:
None.
SRVE0100E: Did not realize init() exception
thrown by servlet {0}: {1} Explanation: None. User Response:
None.
SRVE0101E: Error Initializing IIOPRedirector
Explanation: None. User Response: None.
SRVE0102E: MalformedXMLInfoException: Duplicate init-parameter detected [{0}]
Explanation: None. User Response: None.
SRVE0103E: Illegal Argument Exception: ScriptName must be the first part of
the URI Explanation: None. User Response: None.
SRVE0104E: Unable to load administrative configuration. The initial configuration
will not be created Explanation: None. User Response:
None.
SRVE0105E: An exception occurred in Session.releaseSession()
Explanation: None. User Response: None.
SRVE0106E: Unable to remove remote attribute named: {0} Explanation:
None. User Response: None.
SRVE0107I: Servlet
has become permanently unavailable for service: {0} Explanation:
None. User Response: None.
SRVE0108E: Illegal
Argument Exception: Missing flag value Explanation: None.
User Response: None.
SRVE0109E: Illegal Argument Exception:
Invalid ObjectPool instantiated. Explanation: None.
User Response: None.
SRVE0110E: Failure to create distributed
attribute list. Attributes will not be shared across clones Explanation:
None. User Response: None.
SRVE0111E: Unable
to load administrative configuration. The default server will not be started
Explanation: None. User Response: None.
SRVE0112E: Error locating a matching Virtual Host Explanation:
None. User Response: None.
SRVE0113E: Failure
to set the Dirty bit on all active nodes Explanation: None.
User Response: None.
SRVE0114E: Unable to export RemoteSRP
Connection Object Explanation: None. User Response:
None.
SRVE0115E: Error occurred while invoking error
reporter Explanation: None. User Response: None.
SRVE0116E: Could not find resource iiopredirector.xml on the classpath
Explanation: None. User Response: None.
SRVE0117E: Unable to get remote attribute names Explanation: None.
User Response: None.
SRVE0118E: Could not find resource
/default.servlet_engine Explanation: None. User Response:
None.
SRVE0119E: Number Format Exception: Invalid
Integer Format Explanation: None. User Response: None.
SRVE0120E: IO Error Explanation: None. User Response:
None.
SRVE0121E: Illegal Argument Exception: Trying
to write < 0 bytes Explanation: None. User Response:
None.
SRVE0122W: No such servlet host: [{0}]
Explanation: None. User Response: None.
SRVE0123E: Servlet error: {0} Explanation: None. User
Response: None.
SRVE0124E: Error while shutting down
the application server Explanation: None. User Response:
None.
SRVE0125E: MalformedXMLInfoException: Missing
value in init-parameter [{0}] Explanation: None. User
Response: None.
SRVE0126E: Invalidation Exception:
{0} was created Explanation: None. User Response: None.
SRVE0127E: Unable to obtain Object from object pool {0} Explanation:
None. User Response: None.
SRVE0128E: Error
invoking servlet Explanation: None. User Response: None.
SRVE0129W: IO Exception: Connection reset Explanation: None.
User Response: None.
SRVE0130I: Servlet available for
service: {0} Explanation: None. User Response: None.
SRVE0131I: Servlet redirector starting Explanation: None.
User Response: None.
SRVE0132E: IO Error: Invalid content
length Explanation: None. User Response: None.
SRVE0133E: An error occurred while parsing parameters Explanation:
None. User Response: None.
SRVE0134E: Failed
to retrieve attribute Explanation: None. User Response:
None.
SRVE0135E: Pool Session Exception: Error creating
an instance of the input class Explanation: None. User
Response: None.
SRVE0136I: HTTP transport started on
Port {0} Explanation: None. User Response: None.
SRVE0137E: An error occurred while disabling servlet {0} Explanation:
None. User Response: None.
SRVE0138E: postInvoke
Security Exception Explanation: None. User Response:
None.
TRAS0001W: Encountered an internal error. No valid bundles.
Explanation: None. User Response: None.
TRAS0002W: Null lookup key passed to TraceNLS
Explanation: None. User Response: None.
TRAS0003W: Encountered an error while loading class PropertyResourceBundle
from a JAR file {0} Explanation: None.
User Response: None. WCMD0001W: {0} cannot be set
Explanation: None. User Response: None.
WCMD0002W: Ignoring attribute {0} Explanation: None.
User Response: None.
WCMD0003W: Attribute does not
exist: {0} Explanation: None. User Response: None.
WINT0001W:
Unable to open input stream: {1} {2} {3} Explanation: None.
User Response: None.
WINT0002E: Protocol error occurred
in container transaction Explanation: None. User Response:
None.
WINT0003W: Coordinator was not available {0}
Explanation: None. User Response: None.
WINT0004E: Protocol error: multiple suspended transactions Explanation:
None. User Response: None.
WINT0005W: Unable
to open output stream: {1} {2} {3} Explanation: None.
User Response: None.
WINT0006E: Cannot obtain the transaction
coordinator {0} Explanation: None. User Response: None.
WOBA0001W:
An exception occurred while unregistering from LSD {0} Explanation:
None. User Response: None.
WOBA0002E: An
exception occurred with the stringifyRemote method: {0} Explanation:
None. User Response: None.
WOBA0003W: orb
has not been initialized: registerManagedServer will use IP address to register
with LSD Explanation: None. User Response: None.
WOBA0004W: The objectToKey method of EJSRootOAImpl object received an unexpected
callback {0} Explanation: None. User Response: None.
WOBA0005E: Cannot obtain IP address for local host Explanation:
None. User Response: None.
WPRS0001W: Failed to commit: {0}
Explanation: None. User Response: None.
0001I: Command line, property file, and system property arguments resolved
to: Explanation: The parameter values listed were retrieved
from three places:
- the command line (for example,-CCverbose=true)
- a properties file (for example,-CCpropfile=myapp.properties)
- system properties (for example,java -Dcom.ibm.CORBA.BootstrapHost=myserver.a.b.com
...)
The parameters are resolved in the order listed above, with command line
values having the highest priority and system properties the lowest.
User Response: No action is required. The -CCverbose flag was specified
on the launchClient command, and this message is a result of setting that
flag. It is for information only.
WSCL0002I: Setting DataSource Property {0} to value {1} on DataSource {2}.
Explanation: The application client runtime set the stated
property to the stated value on the JDBC Datasource. DataSource properties
are configured using the Application Client Resource Configuration
Tool . User Response: No action is required. This is for information
only. WSCL0003I: Establish a
method on the DataSource {0} for the Property {1}. Explanation:
The application client runtime has established that a method for setting
the stated JDBC DataSource property exists. User Response: No action
is required. This is for information only.
WSCL0004I: Setting resource property {0} to value {1}. Explanation:
The application client runtime set the stated property to the stated value
for the resource. User Response: No action is required. This is
for information only. WSCL0005I:
JMS resource using supplied JNDI binding mechanism: {0}. Explanation:
The application client runtime is using the stated JNDI binding mechanism
for the JMS resource. The binding mechanism specifies a JMS class that provides
JMS services to the client and resides on the locally configured client system.
The JNDI binding mechanism class can be configured using the
Application Client Resource Configuration Tool . User Response:
No action is required. This is for information only. WSCL0006I: JMS resource using an indirectly supplied
JNDI binding mechanism: {0}. Explanation: The application client
runtime is using the stated JNDI binding mechanism for the JMS resource. This
binding mechanism was configured as a link to a JNDI reference located in
a remote JNDI namespace and allows the client application to use JMS services.
The JNDI binding mechanism can be configured using the Application
Client Resource Configuration Tool . User Response: No action
is required. This is for information only.
WSCL0007I: Loading the default resource binders. Explanation:
The application client runtime is loading the default resource binders.
The resource binders allow the application client runtime to load and configure
resources used by the client application. User Response: No action
is required. This is for information only.
WSCL0008I: Adding binder {0} from the properties file. Explanation:
The application client runtime has added the resource binders defined
in the properties file. Resource binders defined in the properties file are
optional and are used to extend or override the default behavior of the application
client runtime. User Response: No action is required. This is for
information only. WSCL0009I:
No binders were found in the properties file. Explanation: The
properties file contains no resource binders. Resource binders defined in
the properties file are optional and are used to extend or override the default
behavior of the application client runtime. User Response: No action
is required. This is for information only.
WSCL0010I: Resource binders loaded successfully. Explanation:
The application client runtime has successfully loaded the resource binders.
User Response: No action is required. This is for information only.
WSCL0011I: Stack trace: {0}
Explanation: An exception was received by the application client runtime.
The stack trace was made available to assist in the problem determination.
User Response: Analyze the exception and stack trace and correct the problem.
For additional help, enable debug by specifying the -CCtrace flag on the launchClient
command. WSCL0012I: Processing
command line arguments Explanation: This is a status message.
User Response: No action is required. This is for information only.
WSCL0013I: Initializing the J2EE Application
Client Environment Explanation: This is a status message.
User Response: No action is required. This is for information only.
WSCL0014I: Invoking the application
client {0} Explanation: This is a status message that indicates
which class is being started by the launchClient command. User Response:
No action is required. This is for information only. WSCL0015I: Processing the application client archive
file: {0} Explanation: The application client runtime is reading
and loading the stated application client archive file. User Response:
No action is required. This is for information only. WSCL0016I: Using temporary directory {0}.
Explanation: The application client runtime has created the stated temporary
directory for use in storing temporary files. User Response: No
action is required. This is for information only.
WSCL0017I: Loading the main class {0} for the application client jar file
{1} Explanation: The application client runtime is using a
class loader to load the stated main class from the stated application client
archive file. User Response: No action is required. This is for
information only. WSCL0018I:
Processing resource provider factory: {0} Explanation: The Application Client Resource Configuration Tool is filtering
the stated resource provider factories to obtain the pertinent resource providers.
User Response: No action is required. This is for information only.
WSCL0019I: Found resource provider
factory of type: {0} Explanation: The Application
Client Resource Configuration Tool has encountered a resource provider
factory of the stated type. User Response: No action is required.
This is for information only.
WSCL0020I: Processed resource provider of type: {0} Explanation:
The Application Client Resource Configuration Tool has
processed a resource provider factory of the stated type. User Response:
No action is required. This is for information only. WSCL0021I: Opening archive file: {0} Explanation:
The Application Client Resource Configuration Tool is
opening the stated archive file to obtain the client resource configuration
file. User Response: No action is required. This is for information
only. WSCL0022I: Searching for
the resource repository Explanation: The
Application Client Resource Configuration Tool is searching for an existing
resource repository. User Response: No action is required. This
is for information only. WSCL0023I:
The resource repository was not found. Creating a new repository: {0}
Explanation: The Application Client Resource Configuration
Tool was unable to locate an existing resource repository. A new resource
repository is being created with the stated name. User Response: No
action is required. This is for information only.
WSCL0024I: Adding {0} {1} to the JNDI table Explanation: The Application Client Resource Configuration Tool has added
the stated entry to the JNDI resource table. User Response: No
action is required. This is for information only.
WSCL0025I: Binding EJB reference object: Explanation: The application
client runtime is binding the EJB to the local namespace using the stated
JNDI name. EJB references are configured using the Application Assembly Tool.
User Response: No action is required. The -CCverbose flag was specified
on the launchClient command, and this message is a result of setting that
flag. This is for information only.
WSCL0026I: Adding EJB references defined in the properties file
Explanation: The application client runtime has added the EJB references
defined in the properties file. EJB references specified in a properties file
are optional. User Response: No action is required. This is for
information only. WSCL0027I:
No EJB references defined in the properties file Explanation:
The properties file contains no EJB references. User Response:
No action is required. This is for information only. WSCL0028I: Binding environment entry: Explanation:
The application client runtime is binding the object for the environment
entry to the local namespace using the stated JNDI name. Environment entries
are configured using the Application Assembly Tool. User Response:
No action is required. The -CCverbose flag was specified on the launchClient
command, and this message is a result of setting that flag. This is for information
only. WSCL0029I: Binding resource
reference object: Explanation: The application client runtime
is binding the object for the resource reference entry to the local namespace
using the stated JNDI name. Resource references are configured using the Application
Assembly Tool. User Response: No action is required. The -CCverbose
flag was specified on the launchClient command, and this message is a result
of setting that flag. This is for information only. WSCL0030I: No resource provider refs configured for
this provider Explanation: No resource provider references
were configured for this provider. User Response: No action is
required. This is for information only.
WSCL0031I: The object was bound successfully Explanation: The
object was bound into the local namespace successfully. User Response:
No action is required. The -CCverbose flag was specified on the launchClient
command, and this message is a result of setting that flag. This is for information
only. WSCL0032I: Loading the
following URLs with the class loader: Explanation: The application
client runtime is loading the stated URLs. This list is a superset of the
resource references that have been configured for this client application
with the Application Client Resource Configuration Tool .
This helps to determine why a resource reference is not being found.
User Response: No action is required. This is for information only.
WSCL0033I: The main class was loaded
with: {0} Explanation: The stated class loader was used to
load the main class. This is intended to help determine why a different
class may fail to load later. User Response: No action is required.
This is for information only.
WSCL0034I: Binding enterprise extension resource {0} Explanation:
The application client runtime is binding the stated enterprise extension
resource into the local namespace. User Response: No action is
required. The -CCverbose flag was specified on the launchClient command, and
this message is a result of setting that flag. This is for information only.
WSCL0035I: Initialization of the J2EE
Application Client Environment has completed Explanation: This
is a status message. User Response: No action is required. This
is for information only. WSCL0036I:
Parsing classpath: {0} Explanation: The Application Client
runtime is parsing the stated classpath string into separate classpath entries.
User Response: No action is required. This is for information only.
WSCL0100E: Exception received: {0}
Explanation: An exception was received by the application
client runtime. User Response: Analyze the exception and correct
the problem. For additional help enable debug by specifying the -CCtrace
flag on the launchClient command.
WSCL0101E: An invalid or missing parameter on launchClient. See help message
on launchClient. Explanation: An invalid or missing parameter
was specified on the launchClient command. User Response: Determine
which parameters were incorrect or missing and correct the error. Specify
the -help or -? flag on the launchClient command for additional help.
WSCL0102E: Missing property value for
-CC parameter: {0} Explanation: The stated -CC parameter was
specified without a value on the launchClient command. For example, you may
have specified-CCverbose. All -CC parameters require
a value to be specified. For example,-CCverbose=true.
User Response: Specify the property value on the -CC parameter and try
again. Specify the -help or -? flag on the launchClient command for additional
help. WSCL0103E: An invalid -CC
property value was specified: {0} Explanation: A -CC property
was specified with an invalid value on the launchClient command. User
Response: Specify a valid property value for the -CC parameter and try
again. Specify the -help or -? flag on the launchClient command for additional
help. WSCL0104E: The required
parameter specifying the EAR file for the client application was null
Explanation: A null or empty string was passed for the Enterprise Archive
File (EAR) parameter to the launchClient API. This parameter is required and
must point to a valid EAR file. User Response: Ensure that you
specify the name of a valid EAR file that contains the client application
you are attempting to run. You may have to fully qualify the file name. Refer
to the launchClient Javadoc for more information.
WSCL0105E: Cannot launch more than one J2EE application per Java Virtual Machine.
Explanation: You tried to launch two different J2EE applications
within the same Java Virtual Machine (JVM). The Application Client runtime
only allows one application, represented by an Enterprise Archive File (EAR),
to be launched within the same JVM. That EAR file can be launched multiple
times with different parameters, but it must be the same EAR file. This is
because you can only have one JNDI name space active at a time. If you were
to launch two applications, they would both use the last JNDI name space to be
in initialized. Since this would cause confusion in the programming model,
the Application Client runtime only allows one application to be launched
per JVM. User Response: This is a programming error. The application
you are running must be changed to only launch one J2EE application.
WSCL0120E: The JDBC property {0} is
required Explanation: A required JDBC property was not specified.
User Response: Analyze the message data to identify the missing JDBC required
property. For additional help enable debug by specifying the -CCtrace flag
on the launchClient command.
WSCL0121E: The Class for DataSource {0} was not found: {1} Explanation:
The JDBC DataSource class was not found. User Response: Ensure
that the DataSource class exists and place it in the classpath so that it
may be located by the application client runtime. For additional help enable
debug by specifying the -CCtrace flag on the launchClient command.
WSCL0122E: Received an IllegalAccessException
while attempting to access or create DataSource {0}: {1} Explanation:
The application client runtime received an IllegalAccessException when
attempting to access the JDBC DataSource. The JDBC DataSource class is protected
and cannot be accessed by the application client runtime. User Response:
Change the JDBC DataSource to be publicly available. For additional help
enable debug by specifying the -CCtrace flag on the launchClient command.
WSCL0123E: Received an IllegalAccessException
while attempting to access Property {0} on DataSource {1}: {2}
Explanation: The application client runtime received an IllegalAccessException
when attempting to access the JDBC DataSource access or method to obtain the
DataSource property. User Response: Change the JDBC DataSource
access or method to be publicly available. For additional help enable debug
by specifying the -CCtrace flag on the launchClient command. WSCL0124E: Received an InstantiationException while
attempting to create DataSource {0}: {1} Explanation: The application
client runtime received an InstantiationException when attempting to instantiate
the JDBC DataSource. The JDBC Datasource is defined as either abstract or
an interface. User Response: Change the JDBC Datasource to be a
concrete class. WSCL0125E: Received
an IllegalArgumentException while attempting to set the value for DataSource
Property {0} on DataSource {1}. Unknown parameters are required : {2}
Explanation: The application client runtime received an IllegalArgumentException
when attempting to set a property on the JDBC Datasource. Each JDBC Datasource
property requires a method to enable setting the property with the only parameter
being the property value. User Response: Ensure that the JDBC Datasource
property set method exists and only expects one parameter containing the property
value. WSCL0126E: Received an
InvocationTargetException while attempting to set the value for DataSource
Property {0} on DataSource {1}: {2} Explanation: The application
client runtime received an InvocationTargetException when attempting to set
a property on the JDBC Datasource. Each JDBC Datasource property requires
a method to enable setting the property with the only parameter being the
property value. User Response: Ensure that the JDBC Datasource
property set method exists and only expects one parameter containing the property
value. Analyze the message data for the InvocationTargetException to determine
the cause of the problem. For additional help enable debug by specifying the
-CCtrace flag on the launchClient command.
WSCL0127W: Encountered an unsupported DataSource Property {0}: {1}
Explanation: The defined JDBC Datasource property is not supported. The
application client runtime has ignored this property and continued processing.
User Response: No action is required. Warning message only. To prevent
this warning message in the future, remove the defined property from the JDBC
Datasource. Use the Application Client Resource Configuration
Toolt o make the necessary modifications to the JDBC Datasource.
WSCL0128E: Unable to establish a set
method for Property {0} on DataSource {1}. Explanation: The
application client runtime was unable to establish a method for setting a
property on the JDBC DataSource. Each JDBC DataSource property requires a
method to enable setting the property with the only parameter being the property
value. User Response: Ensure that the JDBC DataSource property
set method exists and only expects one parameter containing the property value.
For additional help enable debug by specifying the -CCtrace flag on the launchClient
command. WSCL0129E: The DataSource
classname {0} is not of the required type javax.sql.DataSource.
Explanation: The JDBC Datasource is required to be of type javax.sql.DataSource.
User Response: Change the JDBC Datasource to be of type javax.sql.DataSource.
WSCL0130E: The specified object reference
for creating of the DataSource is not of the required type javax.naming.Reference
Explanation: The object reference for the JDBC Datasource
is required to be of type javax.naming.Reference. User Response: Change
the object reference for the JDBC Datasource to be of type javax.naming.Reference.
WSCL0131E: Received an IntrospectionException
while attempting to introspect DataSource {1}: {2} Explanation:
The application client runtime received an IntrospectionException when
attempting to process the JDBC Datasource. User Response: Analyze
the exception message data and correct the problem. For additional help enable
debug by specifying the -CCtrace flag on the launchClient command.
WSCL0150W: Unknown JMS resource type:
{0} Explanation: The stated JMS Resource is of an unknown type.
The JMS Resource is required to be of type Destination or Connection.
User Response: Ensure that the JMS Resource is of type Destination or
Connection. Use the Application Client Resource Configuration
Toolt o make the necessary modifications to the JMS Resource. For additional
help enable debug by specifying the -CCtrace flag on the launchClient command.
WSCL0151W: The property value for Property
{0} for the {1} Resource was set to an invalid value of {2}. Explanation:
The stated property for the stated resource was either not a valid type
or was not set. The property must be of type java.lang.String, java.lang.Boolean
or java.lang.Integer. Properties for resources are configured using the Application Client Resource Configuration Tool . This property
was ignored. User Response: Ensure the property value is set to
a valid type. WSCL0152W: The
Class for the JNDI binding mechanism {0} was not found Explanation:
The application client runtime was unable to find the class for instantiating
the stated JMS binding mechanism. The JNDI binding mechanism is configured
using the Application Client Resource Configuration Tool
. User Response: Ensure that the JMS binding mechanism class
exists and is available in the classpath.
WSCL0153W: The required constructor for the JNDI binding mechanism {0}(java.util.Properties)
was not found: {1} Explanation: The application client runtime
was unable to instantiate an instance of the stated JMS binding mechanism.
The JMS binding mechanism is required to have a class constructor that has
one parameter of type java.util.Properties. This binding mechanism class is
a user written class and is not supplied by WebSphere. User Response:
Ensure that the JMS binding mechanism has a constructor with one parameter
of type java.util.Properties.
WSCL0154W: Unable to construct an instance of JNDI binding mechanism {0}(java.util.Properties)
Explanation: The application client runtime failed to execute
the stated class constructor due to an unexpected error. User Response:
A programming error exists in the constructor. Analyze the exception
received and correct the problem.
WSCL0155W: The URL specification {0} is not valid Explanation:
The application client runtime was unable to create a URL for the stated
URL specification. The URL specified in the client resource configuration
file is not properly formed. User Response: Correct the URL specification
by using the Application Client Resource Configuration Tool
. WSCL0156W: Unable to create
a URL resource because: Explanation: The application client
runtime received an unexpected exception while creating the URL resource.
User Response: Analyze the stated exception received and correct the problem.
WSCL0157W: Unable to decode the password
for resource {0} when attempting to set property {1} Explanation:
The application client runtime was unable to decode the password for the
stated resource. The encoding scheme used when the password was encoded is
not valid. User Response: Correct the password in the client resource
configuration file by using the Application Client Resource
Configuration Tool. WSCL0158W:
Unable to create a mail resource with properties: {0} because:
Explanation: The application client runtime received an unexpected exception
while creating the stated mail resource. User Response: Analyze
the stated exception received and correct the problem. WSCL0159W: Unable to create a data source resource
with properties: {0} because: Explanation: The application
client runtime received an unexpected exception while creating the stated
Datasource resource. User Response: Analyze the stated exception
received and correct the problem.
WSCL0160W: An unexpected classloader {0} was used to load class {1} for resource
{2}. Explanation: A classpath was specified in the resource
configuration file for the stated resource, however the Application Client
runtime loaded the stated class using a different classloader than the one
created by the Application Client runtime. In most cases, this indicates the
stated class was found in the system classpath. This may later cause exceptions
such asjava.lang.ClassNotFoundExceptionandjava.lang.NoClassDefFoundError
when the stated class attempts to load other classes. This is a warning
only and the stated class was successfully loaded, but the classpath specified
in the resource configuration file will not be used. User Response:
Search through the classpath specified with the<nobr>-CCclasspath
<nobr>option and locate the .class file or the jar file that contains
the stated class. If you are not using the launchClient command file, you
will have to search the system classpath as well. Once you locate the class,
remove it and rerun launchClient. You can use the Application
Client Resource Configuration Toolt o configure classpath information
for this resource. WSCL0161E:
The resource configuration information is not compatible with the resource
type {1}. The object was not bound into the namespace. Explanation:
This resource was configured as the stated type when assembling the Application
Client using the Application Assembly Tool. The Application Client runtime
found a resource with the same name in the client resource configuration file,
however, the client resource configuration information is not compatible with
the stated resource type. User Response:
- If the stated type is correct, then use the Application
Client Resource Configuration Toolt o find the resource with the matching
name and delete it, then configure the resource for the appropriate type.
- If the stated type is incorrect, then use the Application Assembly Tool
to configure the correct type.
WSCL0200E: The Enterprise
Archive file {0} does not contain an application client jar file.
Explanation: The application client runtime was unable to locate the client
application jar file in the stated client application Enterprise Archive File
(EAR). This may happen for several reasons:
- The specified file is not an EAR file.
- The specified file is a valid EAR file but does not contain an application
client.
- The specified EAR file does not match the J2EE version of the application
client runtime.
- The specified EAR file was not built by the WebSphere Application Assembly
Tool.
User Response: Use the Application Assembly Tool to reassemble
the EAR file and be sure to include the application client. WSCL0201E: No manifest entry found in application client
jar file {0} Explanation: The application client runtime was
unable to locate a manifest file in the stated application client jar file.
The manifest contains meta data for the J2EE application client and is required.
User Response: Use the Application Assembly Tool to reassemble the application
client jar file. This will add the manifest to the proper path in the application
client jar file. Then use the Application Assembly Tool to reassemble the
Enterprise Archive file. WSCL0202E:
The manifest file for the application client jar file {0} located in the Enterprise
Archive file {1} does not contain a main class entry for the client application
main class Explanation: The application client runtime was
unable to locate a manifest entry identifying the main class for the stated
application client in the stated Enterprise Archive file. User Response:
Use the Application Assembly Tool to modify the application client jar
file. In the main class field specify the fully-qualified name of the class
that you wish to start with the launchClient command. For example, 'com.myCompany.myApp.myClass'.
WSCL0203E: Unable to locate the application
client jar file {0} in the Enterprise Archive file {1} Explanation:
The application client runtime was unable to locate the stated application
client jar file in the stated Enterprise Archive file. This error occurs when
the-CCjarfilenameparameter is used, and the specified
jar file does not exist in the Enterprise Archive file. User Response:
Change the value for the-CCjarfilenameparameter
to a jar file that exists in the Enterprise Archive file. If the jar file
you need is not in the Enterprise Archive file, use the Application Assembly
Tool to add the application client jar file to the Enterprise Archive file.
WSCL0204W: Failed to start the process
to remove the temporary directory {1} Explanation: The application
client runtime was unable to start the process used to remove the stated temporary
directory that the runtime created. User Response: Locate the stated
temporary directory and manually remove the directory and files. They are
no longer needed and are wasting space on the hard drive. This error generally
occurs whenjava.exeis not in your system path. To prevent this error
in the future, locatejava.exeand add its path to your system path.
WSCL0205W: The incorrect class loader
was used to load {0} Explanation: The Application Client runtime
attempted to load the stated main class from the Enterprise Archive (EAR)
file, but another version of the main class was found in one of the application
classpath's first. This resulted in the main class being loaded from the hard
drive instead of the EAR file. In most cases, this is a severe error that
will cause the user program to fail later with exceptions such asjava.lang.ClassNotFoundException
andjava.lang.NoClassDefFoundErrorwhen attempting to load EJB's
or other classes from the EAR file. User Response: Search through
the classpath's specified with the<nobr>-CCclasspath<nobr>option
and the classpath's configured with the Application Client
Resource Configuration Toolt o locate the .class file or the jar file
that contains the main class. If you are not using the launchClient command
file, you will have to search the system classpath as well. Once you locate
the class, remove it and rerun launchClient.
WSCL0206E: File {0} is not a valid Enterprise Archive file. Explanation:
The stated file was passed to the Application Client runtime, but it does
not conform to the Enterprise Archive (EAR) file format. User Response:
This may happen for one of the following reasons:
- The file does not exist. Specify a different file on the launchClient
command
- The file you specified is not an Enterprise Archive (EAR) file. Your application
must be packaged within an Application Client jar file, and this jar file
must be packaged within an EAR file. Use the Application Assembly Tool to
add your application to an Application Client jar file. Then add your Application
Client jar file to an EAR file and rerun launchClient with the EAR file
- Your EAR file may be corrupted or built incorrectly. Use the Application
Assembly Tool to resave the EAR file. This may correct the error.
WSCL0207E: Jar file {0} in
Enterprise Archive file {1} is not an Application Client jar file.
Explanation: The stated jar file name was passed to launchClient with
the -CCjar parameter. The jar file exists in the stated Enterprise Archive
(EAR) file, but it is not an Application Client jar file. User Response:
If you remove the -CCjar parameter from the launchClient invocation, the
Application Client runtime will automatically locate the Application Client
jar file in your EAR file. If you have more than one Application Client jar
file in your EAR file, however, you will need to use the -CCjar parameter.
If you would like the stated jar file to be an Application Client jar
file, perform the following steps in the Application Assembly Tool:
- Create an Application Client module and add your jar file's contents
- Delete the existing jar file from your EAR and add the new Application
Client module.
WSCL0208E: System property
com.ibm.websphere.client.applicationclient.archivedir cannot be set to a file.
Explanation: The stated system property was set to a filename,
but it User Response: Change the value of the stated system property
to a directory. If your ear file has already been extracted to the hard drive,
you can change the value of the system property to the root directory where
it was extracted. If you would like the launchClient command to extract the
ear file, specify the desired target directory.
WSCL0209E: Failed to create archive directory {0}. Explanation:
The Application Client system property User Response: This
is usually caused by specifying a directory value that has multiple subdirectories
that don't exist. The Application Client runtime will only create the last
subdirectory specified. For example, if you specify "/A/B/C" and subdirectories
A or B do not exist, you will receive this failure. With this example, the
Application Client runtime will only create the subdirectory C. The
other possible failure is you don't have authority to write to the specified
directory. If this is the case, you need to specify a different directory
or change the directory permissions.
WSCL0220E: An unsuccessful attempt was made to find the resource configuration
information for {0} Explanation: The application client runtime
was unable to locate the resource configuration information for the stated
resource because the name of the resource does not match the JNDI name used
when the resource was configured using the Application Client
Resource Configuration Tool . User Response: Use the
Application Client Resource Configuration Toolt o change the JNDI name
to equal the resource name value that was stated in the message. The resource
name value was configured using the Application Assembly Tool. WSCL0280W: An EJB object could not be created because
the name is null Explanation: The application client runtime
was unable to create a reference to an EJB because the value specified on
the <ejb-ref-name> entry in the application client deployment descriptor
contains an invalid name. This can happen if the deployment descriptor was
created without using the Application Assembly tool. User Response:
Verify the value specified on the <ejb-ref-name> entry in the application
client deployment descriptor contains a valid name or use the Application
Assembly tool to configure this EJB resource. WSCL0300W:
An environment object could not be created for {0} because the value of {1}
is not valid for type {2} Explanation: The application client
runtime was unable to create an environment object because the value specified
on the <env-entry-value> entry in the application client deployment
descriptor does not contain a valid value for the type specified on the <env-entry-type> entry.
This can occur if the deployment descriptor was created without using the
Application Assembly Tool. User Response: Change the value specified
on the <env-entry-value> entry in the application client deployment
descriptor to a valid value for the type specified on the <env-entry-type> entry.
Or use the Application Assembly Tool to configure a value that is valid for
the type specified. WSCL0301W: An environment object
could not be created for {0} because the type {1} is not supported
Explanation: The application client runtime was unable to create an object
defined by the <env-entry> in the application client deployment descriptor
because the type specified for the <env-entry-type> is not valid. This
can occur if the deployment descriptor was created without using the Application
Assembly Tool. User Response: Change the type specified on the <env-entry-type> in
the application client deployment descriptor to a valid type or use the Application
Assembly Tool to modify the type. The valid types are: java.lang.Boolean,
java.lang.String, java.lang.Integer, java.lang.Double, java.lang.Byte, java.lang.Short,
java.lang.Long, and java.lang.Float. WSCL0330W: Unable
to update the classpath for resource {0} because the classpath {1} specified
in the client resource configuration file is not in the correct format
Explanation: The application client runtime was unable to update the classpath
for the stated resource because the classpath is not in the correct format.
User Response: Use the Application Client Resource Configuration
Toolt o change the stated classpath. WSCL0331E:
An unexpected error occurred while trying to create URL stream handler class
{0} for protocol {1}. Explanation: The Application Client runtime
was unable to create the stated URL stream handler class for the stated protocol.
This is most likely because the stream handler class was specified incorrectly
when the URL provider was configured or the stated stream handler class could
not be found in the classpath. User Response: Use the
Application Client Resource Configuration Toolt o find the URL provider
for the stated protocol and verify the stream handler class field value and
the classpath field value are correct. WSCL0350W: Unable
to create a resource for {0} because the following error occurred:
Explanation: The application client runtime encountered an unexpected
exception while creating the stated resource. User Response: Analyze
the stated exception received and correct the problem.
WSCL0351W: Unable to create a resource for {0} because the resource type {1}
specified in the application client deployment descriptor is not supported.
Verify the type specified on the <res-type> entry is one of the following:
{2} Explanation: The application client runtime was unable
to create the stated resource because the resource type specified by the <res-type> element
in the application client deployment descriptor was not supported. This can
occur if the deployment descriptor was created without using the Application
Assembly Tool. User Response: Change the type specified on the <res-type> entry
to one of the stated supported types or use the Application Assembly Tool
to configure the resource. WSCL0370W: An error occurred
while trying to bind an Enterprise Extension resource Explanation:
The application client runtime encountered an unexpected exception while
binding an Enterprise Extension resource. The message that follows provides
detailed information about the exception. User Response: Analyze
the exception and correct the problem.
Application Client Resource Configuration ToolThe Application Client
Resource Configuration Tool is used to configure local resource references
for an Application Client. Issue 'clientConfig' from the command line to start
the tool.
WSCP0001E: The following options are available for {0} Explanation:
None. User Response: None.
WSCP0002E: Binding
{0} to {1} is not supported Explanation: None. User
Response: None.
WSCP0003E: Contexts do not have knowledge
of their parent Explanation: None. User Response: None.
WSCP0004E: {0} cannot be destroyed because it is not empty Explanation:
None. User Response: None.
WSCP0005E: Failed
to find {0} Explanation: None. User Response: None.
WSCP0006E: You do not have permission to create {0} Explanation:
None. User Response: None.
WSCP0007E: Editor
not defined for this property Explanation: None. User
Response: None.
WSCP0008E: An exception occurred. The
stack trace was: Explanation: None. User Response:
None.
WSCP0009E: Failed to attach to server using
{0} : {1} Explanation: None. User Response: None.
WSCP0010E: Binding {0} to {1} failed : {2} Explanation: None.
User Response: None.
WSCP0011E: Failed to cd to {0}
: {1} Explanation: None. User Response: None.
WSCP0012E: Failed to create {0} : {1} Explanation: None.
User Response: None.
WSCP0013E: Failed to destroy {0}
: {1} Explanation: None. User Response: None.
WSCP0014E: Failed to perform remote evaluation Explanation: None.
User Response: None.
WSCP0015E: Failed to export configuration
to file {0} : {1} Explanation: None. User Response:
None.
WSCP0016E: Failed to generate the fully qualified
name for {0} Explanation: None. User Response: None.
WSCP0017E: Failed to get defaults : {0} Explanation: None.
User Response: None.
WSCP0018E: Failed to get environment
of {0} : {1} Explanation: None. User Response: None.
WSCP0019E: Failed to import configuration from file {0} : {1}
Explanation: None. User Response: None.
WSCP0020E: Failed to list attributes of {0} Explanation: None.
User Response: None.
WSCP0021E: Failed to list {0}
: {1} Explanation: None. User Response: None.
WSCP0022E: Failed to load extension : {0} Explanation: None.
User Response: None.
WSCP0023E: Failed to rename {0}
to {1} : {2} Explanation: None. User Response: None.
WSCP0024E: The search for {0} failed : {1} Explanation: None.
User Response: None.
WSCP0025E: Failed to set defaults
: {0} Explanation: None. User Response: None.
WSCP0026E: Unbinding {0} failed : {1} Explanation: None.
User Response: None.
WSCP0027E: Internal error : {0}
Explanation: None. User Response: None.
WSCP0028E: Internal error : Invalid wscp option type : {0} Explanation:
None. User Response: None.
WSCP0029E: Internal
error : Method not found : {0} Explanation: None. User
Response: None.
WSCP0030E: Internal error : Could not
get parent name for {0} Explanation: None. User Response:
None.
WSCP0031E: Internal error : Could not get short
name for {0} Explanation: None. User Response: None.
WSCP0032E: Internal error : Could not get type name for {0} Explanation:
None. User Response: None.
WSCP0033E: Invalid
action : {0} Explanation: None. User Response: None.
WSCP0034E: Invalid attribute : {0} Explanation: None.
User Response: None.
WSCP0035E: Invalid attribute format
: {0} Explanation: None. User Response: None.
WSCP0036E: Invalid context : {0} Explanation: None.
User Response: None.
WSCP0037E: Invalid filter : {0}
: {1} Explanation: None. User Response: None.
WSCP0038E: Invalid key Explanation: None. User Response:
None.
WSCP0039E: Invalid {0} name : {1}
Explanation: None. User Response: None.
WSCP0040E: Invalid object type : {0} is a {1} but must be a {2}
Explanation: None. User Response: None.
WSCP0041E: Invalid object name : {0} Explanation: None.
User Response: None.
WSCP0042E: Invalid option : {0}
Explanation: None. User Response: None.
WSCP0043E: Invalid option argument : {0} Explanation: None.
User Response: None.
WSCP0044E: Invalid combination
of options. The valid combinations are: -baseInstance -recursive
[-makeClone] -baseInstance -parentModel [-modelAttrs]
(-baseInstance [-makeClone] | -parentModel) [-modelAttrs] Explanation:
None. User Response: None.
WSCP0045E: Invalid
options. The -makeClone option cannot be specified without the -baseInstance
option Explanation: None. User Response: None.
WSCP0046E: Invalid combination of options. Only one search method can be specified.
Explanation: None. User Response: None.
WSCP0047E: Invalid port : {0} Explanation: None. User
Response: None.
WSCP0048E: Invalid properties format
: {0} Explanation: None. User Response: None.
WSCP0049E: An action to perform on {0} must be specified Explanation:
None. User Response: None.
WSCP0050E: Missing
option argument for {0} Explanation: None. User Response:
None.
WSCP0051E: A required argument was not specified
: {0} Explanation: None. User Response: None.
WSCP0052E: A required option was not specified : {0} Explanation:
None. User Response: None.
WSCP0053E: Name
is already bound : {0} Explanation: None. User Response:
None.
WSCP0054E: No attached server Explanation:
None. User Response: None.
WSCP0055E: No
current context Explanation: None. User Response: None.
WSCP0056E: No options are available for {0} Explanation: None.
User Response: None.
WSCP0057E: {0} cannot be removed
because it is not empty Explanation: None. User Response:
None.
WSCP0058E: Object not found : {0}
Explanation: None. User Response: None.
WSCP0059E: Required attribute cannot be defaulted : {0} Explanation:
None. User Response: None.
WSCP0060E: Server
listening at {0} Explanation: None. User Response: None.
WSCP0061E: Socket error : {0} Explanation: None. User
Response: None.
WSCP0062E: Timeout occurred before
task completed Explanation: None. User Response: None.
WSCP0063E: Server baseInstName + {0} is already a member of a server group;
it cannot be made part of {1}. Explanation: None. User
Response: None.
WSCP0064E: Server group {0} already
exists. Explanation: None. User Response: None.
WSCP0065E: The following actions are available for {0} Explanation:
None. User Response: None.
WSCP0066E: Action
{0} not valid for type {1} Explanation: None. User Response:
None.
WSCP0067E: Act exception : {0} Explanation:
None. User Response: None.
WSCP0068E: Application
relation not found : {0} Explanation: None. User Response:
None.
WSVR0001E: More than one node defined. -nodeName must be specified.
Explanation: None. User Response: None.
WSVR0002E: Node {0} not found in {1}. Explanation: None.
User Response: None.
WSVR0003E: More than one server
defined. -serverName must be specified. Explanation: None.
User Response: None.
WSVR0004E: Server {0} on Node
{2} defined in {1} is not an application server. Explanation:
None. User Response: None.
WSVR0005E: Server
{0} on Node {2} not found in {1}. Explanation: None.
User Response: None.
WSVR0006E: Server {0} failed during
initialization : {1} Explanation: None. User Response:
None.
WSVR0007E: Could not find the Domain object in
{0} Explanation: None. User Response: None.
WSVR0008E: Error encountered reading {0} {1} Explanation:
None. User Response: None.
WSVR0009E: Error
occurred during startup {0} Explanation: None.
User Response: None.
WSVR0010E: EJB engine failed to
stop. {0} Explanation: None. User Response:
None.
WSVR0011W: {0} has an invalid archiveURL: {1}
Explanation: None. User Response: None.
WSVR0012W: Application, {0}, failed to start {1} Explanation:
None. User Response: None.
WSVR0013W: Module,
{0}, failed to start {1} Explanation: None.
User Response: None.
WSVR0014E: Error removing WAR:
{0} {1} Explanation: None. User Response:
None.
WSVR0015E: Error removing EJB jar: {0}
{1} Explanation: None. User Response: None.
WSVR0016W: Resource provider {0} has an invalid classpath, {1}
{2} Explanation: None. User Response: None.
WSVR0017E: Error encountered binding J2EE resource, {0}, as {1}
{2} Explanation: None. User Response: None.
WSVR0018W: Failureto create CustomService, {0} {1}
Explanation: None. User Response: None.
WSVR0019W: CustomService, {0}, failed to initialize. {1}
Explanation: None. User Response: None.
WSVR0020W: CustomService, {0}, failed to shutdown. {1}
Explanation: None. User Response: None.
WSVR0021W: Invalid trace file specified: {0} Explanation: None.
User Response: None.
WSVR0022E: Invalid Transaction
Log File specification: {0} Explanation: None. User
Response: None.
WSVR0023I: Server {0} open for ebusiness
Explanation: None. User Response: None.
WSVR0024I: Server {0} stopped Explanation: None. User
Response: None.
WSVR0025I: Creating temporary product
license Explanation: None. User Response: None.
WSVR0026I: Error occurred while validating product license Explanation:
None. User Response: None.
WSVR0027I: Temporary
product license expires on {0,date} Explanation: None.
User Response: None.
WSVR0028I: Temporary product license
expired on {0,date} Explanation: None. User Response:
None.
WSVR0029W: Listener {0} threw an exception
{1} Explanation: None. User Response: None.
WSVR0030E: ORB not initialized Explanation: None. User
Response: None.
WSVR0031E: Failure to load container
{0} Explanation: None. User Response: None.
WSVR0032E: Object Adapter created already Explanation: None.
User Response: None.
WSVR0033E: Failure to load security
collaborator, {0} {1} Explanation: None.
User Response: None.
WSVR0034W: Invalid passivation
directory specified: {0} Explanation: None. User Response:
None.
WSVR0035E: Failure to initialized the container:
{0} Explanation: None. User Response: None.
WSVR0036E: Failure to obtain initial naming context: {0} Explanation:
None. User Response: None.
WSVR0037I: Starting
EJB jar: {0} Explanation: None. User Response: None.
WSVR0038I: No JNDI name found for {0}, binding home name as {1}
Explanation: None. User Response: None.
WSVR0039E: Failed to start EJB jar, {0}: {1} Explanation: None.
User Response: None.
WSVR0040E: addEjbModule failed
for {0} {1} Explanation: None. User Response:
None.
WSVR0041I: Stopping EJB jar: {0}
Explanation: None. User Response: None.
WSVR0042E: Failed to stop {0}: {1} Explanation: None.
User Response: None.
WSVR0043E: Unbind failed for {0}:
{1} Explanation: None. User Response: None.
WSVR0044E: Failed to stop EJB jar, {0}: {1} Explanation: None.
User Response: None.
WSVR0045E: Failed to create sub-context
{0}: {1} Explanation: None. User Response: None.
WSVR0046E: Failed to bind, {0}: {1} Explanation: None.
User Response: None.
WSVR0047E: Batch naming operation
failed : {0} Explanation: None. User Response: None.
WSVR0048W: Binding {0} failed, no JNDI name found Explanation:
None. User Response: None.
WSVR0049I: Binding
{0} as {1} Explanation: None. User Response: None.
WSVR0050W: setProperty -- unsupported object type: {0} Explanation:
None. User Response: None.
WSVR0051W: Attempted
to register URLProvider with null protocol, {0} or streamHandlerClassName
{1} Explanation: None. User Response: None.
WSVR0052W: Attempted to unregister URLProvider with null protocol
Explanation: None. User Response: None.
WSVR0053I: DrAdmin available on port {0} Explanation: None.
User Response: None.
WSVR0054E: Failed to create a
server socket, the port {0} maybe in use: {1} Explanation: None.
User Response: None.
WSVR0055E: Configuration dump
for module, {0}, failed. {1} Explanation: None.
User Response: None.
WSVR0056E: Configuration dump
for application, {0}, failed. {1} Explanation: None.
User Response: None.
WSVR0057E: Stop node failed
{0} Explanation: None. User Response: None.
WSVR0058E: Could not process trace specification {0} {1}
Explanation: None. User Response: None.
WSVR0059E: Failure to open trace log file {0} {1} Explanation:
None. User Response: None.
WSVR0060I: Defaulting
trace output to System.out Explanation: None. User Response:
None.
WSVR0061W: Failure to create trace event listener
{0} {1} Explanation: None. User Response:
None.
WSVR0062W: WLMBootstrapException occurred
{0} Explanation: None. User Response: None.
WSVR0063I: Agent has the same name as PrimaryNode. Change it to {0}
Explanation: None. User Response: None.
WSVR0064W: Failed to update {0} {1} Explanation: None.
User Response: None.
WSVR0065W: Could not find {0}
{1} Explanation: None. User Response: None.
WSVR0066W: {0} not updated, could not create {1} Explanation:
None. User Response: None.
WSVR0067I: WebSphere
Administration Server has been initialized Explanation: None.
User Response: None.
WSVR0068E: Could not load database
driver {0} Explanation: None. User Response: None.
WSVR0069I: Initializing WebSphere Administration Server Explanation:
None. User Response: None.
WSVR0070W: Exception
encountered in initializeWLMPush {0} Explanation: None.
User Response: None.
WSVR0071E: Invalid EJB jar bindings
for {0} {1} Explanation: None. User Response:
None.
WSVR0072E: Invalid ejbjar.xml for {0}
{1} Explanation: None. User Response: None.
WSVR0073E: PrimaryNode {0} is not found! Administrative agent did not start.
Explanation: None. User Response: None.
WSVR0074E: Administrative agent not properly initialized. Transaction log
missing. Explanation: None. User Response: None.
WTRN0001W:
Exception occurred when obtaining an otid_t object from JTS Explanation:
None. User Response: None.
WTRN0002E: Register
resource failed: Explanation: None. User Response: None.
WTRN0003W: Unable to deserialize an object from the byte stream {0}
Explanation: None. User Response: None.
WTRN0004W: Encountered an error when destroying XA resource:
Explanation: None. User Response: None.
WTRN0005W: Encountered an error while creating XAConnection and XAResource
{0} Explanation: None. User Response: None.
WTRN0006W: Encountered an error while closing XAConnection: {0} {1}
Explanation: None. User Response: None.
WTRN0007W: SQLException occurred because of a connection commit error: {0}
Explanation: None. User Response: None.
WTRN0008W: Object cannot be deserialized. Explanation: None.
User Response: None.
WTRN0009W:
XAER_RMFAIL on: Explanation: None. User Response: None.
WTRN0010E: Encountered an error while building a JTAXAResource object {0}
Explanation: None. User Response: None.
WTRN0011W: One-phase resource does not support commit Explanation:
None. User Response: None.
WTRN0012E: Register
XAResource failed: Explanation: None. User Response:
None.
WTRN0013E: XA rollback operation failed: global
transaction: {0} Exception: {1} Explanation: None.
User Response: None.
WTRN0014W: XAER_RMERR happens
on: Explanation: None. User Response: None.
WTRN0015W: SQLException occurred because of connection rollback error: {0}
Explanation: None. User Response: None.
WTRN0016W: Nested transactions are not supported Explanation:
None. User Response: None.
WTRN0017W: Encountered
an error in XA recover operation: {0} Explanation: None.
User Response: None.
WTRN0018W: Unknown XAResource
state Explanation: None. User Response: None.
WTRN0019W: Can not create XAResourceFactory: {0} {1} Explanation:
None. User Response: None.
WTRN0020W: Encountered
an XA forget error: {0} {1} Explanation: None. User
Response: None.
WTRN0021W: Unknown JTA Driver
Explanation: None. User Response: None.
WTRN0022W: The JTAXAResource object is null Explanation: None.
User Response: None.
WTRN0023W: No transaction is associated
with current thread Explanation: None. User Response:
None.
WTRN0024W: Invalid XA end flag: {0}
Explanation: None. User Response: None.
WTRN0025W: Can not create XAResource object Explanation: None.
User Response: None.
WTRN0026W: The registerServant
method failed: Explanation: None. User Response: None.
WTRN0027W: XAResource is not known to this transaction Explanation:
None. User Response: None.
WTRN0028W: Exception
occurred in the current get_control method Explanation: None.
User Response: None.
WTRN0029W: bqual_length of otid
is greater than 60 Explanation: None. User Response:
None.
WTRN0030W: TMRESUME is not supported
Explanation: None. User Response: None.
WTRN0031E: Error to recover XAResource: Explanation: None.
User Response: None.
WTRN0032W: This should not happen
Explanation: None. User Response: None.
WTRN0033W: Encountered an exception during initialization of XARecoveryManager
{0} Explanation: None. User Response: None.
WTRN0034W: Encountered an error building JTAXAResource Explanation:
None. User Response: None.
WTRN0035W: Encountered
an exception in current get_coordinator method Explanation: None.
User Response: None.
WTRN0036I: Unable to establish
adapters Explanation: None. User Response: None.
WTRN0037E: Unable to defer commitment of restart-data helper transaction.
tid: {0}, result: {1} Explanation: None. User Response:
None.
WTRN0038E: Encountered an error while loading
restart data: {0} Explanation: None. User Response:
None.
WTRN0039E: Incorrect number of old helper transactions.
expected: {0}, found: {1} Explanation: None. User Response:
None.
WTRN0040I: Expected log file specification to
be a comma-delimited list of file names, device names, or both optionally
followed by the size separated by ; Explanation: None.
User Response: None.
WTRN0041E: Encountered exception
while initializing log file {0} {1} Explanation: None.
User Response: None.
WTRN0042W: Giving up on outcome
delivery Explanation: None. User Response: None.
WTRN0043E: Encountered an invalid number of restart data tables: {0}, tid:
{1} Explanation: None. User Response: None.
WTRN0044I: Prepare phase operating on subtransaction Explanation:
None. User Response: None.
WTRN0045E: Failure
to prepare restart data helper transaction: tid: {0}, result: {1}
Explanation: None. User Response: None.
WTRN0046E: Unable to finish old helper transaction: {0}, status: {1}
Explanation: None. User Response: None.
WTRN0047E: {0} Explanation: None. User Response: None.
WTRN0048E: Current helper transaction (for restart data) was not prepared,
tid: {0}, status: {1} Explanation: None. User Response:
None.
WTRN0049I: Default and minimum log file size
is 1M Explanation: None. User Response: None.
WTRN0050E: {0} corrupted Explanation: None. User Response:
None.
WTRN0051W: Cannot recover a resource {0} {1}
Explanation: None. User Response: None.
WTRN0057I: At least two file/device names are required Explanation:
None. User Response: None.
WTRN0058I: Sample
specification for using two log files of 2 MB each, logFile1, logFile2;2M
Explanation: None. User Response: None.
WTRN0059W: rollback_only failed for transaction: {0} {1} Explanation:
None. User Response: None. WTSK0001W: Encountered an internal
error. Invalid attributes: {0} Explanation: None. User
Response: None.
WTSK0002W: Cannot edit relationships
Explanation: None. User Response: None.
WTSK0003W: Cannot access the ApplicationHome interface Explanation:
None. User Response: None.
WTSK0004W: Internal
error. Invalid attributes Explanation: None. User Response:
None.
WTSK0005W: Cannot access the EJBServerHome interface
Explanation: None. User Response: None.
WTSK0006W: Cannot access the EJBContainerHome interface Explanation:
None. User Response: None.
WTSK0007W: Encountered
an error accessing bean attributes {0} Explanation: None.
User Response: None.
WTSK0008W: Internal error
Explanation: None. User Response: None.
WTSK0009W: Attribute not set Explanation: None. User
Response: None.
WTSK0010W: Cannot access the DataSourceHome
interface Explanation: None. User Response: None.
WTSK0011W: Encountered an exception: {0} Explanation: None.
User Response: None.
WTSK0012W: Could not access Home
Explanation: None. User Response: None.
WTSK0013W: Cannot access the EnterpriseBeanHome interface Explanation:
None. User Response: None.
WTSK0014W: Could
not obtain Initialcontext Explanation: None. User Response:
None.
WTSK0015W: General Error Explanation:
None. User Response: None.
WTSK0016W: Cannot
access the JDBCDriverHome interface Explanation: None.
User Response: None.
WTSK0017E: findLTPAConfig
Explanation: None. User Response: None.
WTSK0018W: Cannot access the ServerHome interface Explanation:
None. User Response: None. WWLM0001: Could not notify {0} in the
{1} method because the server was not found in the server group. {2}
Explanation: An internal recoverable error occurred. User Response:
If this problem persists, contact your service representative.
WWLM0002: An exception occurred while setting Workload Management properties.
{0} Explanation: One of the Workload Management properties
was invalid. User Response: Make sure that the Workload Management
properties are set correctly. In particular com.ibm.ejs.wlm.RefreshInterval,
com.ibm.ejs.wlm.MaxCommFailures and com.ibm.ejs.wlm.UnusableInterval must
be valid numbers.
WWLM0003: Method {0} was called more
than once with different host names. {1} {2} Explanation: An
unexpected internal error occurred. User Response: If this problem
persists, contact your service representative.
WWLM0004:
{0} cannot be initialized more than once. Explanation: Multiple
requests were made to initialize an object instance that should only be initialized
one time. User Response: If this problem persists, contact your
service representative.
WWLM0005: Unable to access home
for model bean. {0} Explanation: An attempt to access the home
for the model bean was not successful. User Response: Ensure that
the administrative repository database and name server are up and running.
WWLM0006: Unable to set the thread properties for {0}. {1} Explanation:
Workload Management was unable to construct the named thread because an
unexpected exception occurred when setting the thread properties.
User Response: Correct the problem based on information from the exception
and restart the Administrative Server. If this problem persists, contact your
service representative.
WWLM0007: An unexpected exception
occurred while getting the current state of a clone. {0} Explanation:
An unexpected exception occurred when getting the current state of a clone.
User Response: Check the state of the clones. If this problem persists,
contact your service representative.
WWLM0008: Unexpected
exception when updating clone {0} with model information. {1}
Explanation: An error occurred when trying to push model information to
a clone. User Response: Check the state of the clones. If the problem
persists, contact your service representative.
WWLM0009:
Unable to access model bean for model {0}. {1} Explanation: An
unexpected exception occurred when refreshing clones. User Response:
Contact your service representative.
WWLM0010: An
unexpected exception occurred writing server group information. {0}
Explanation: An unexpected exception occurred when writing server group
information to a byte stream. User Response: If the problem persists,
contact your service representative.
WWLM0011: An exception
occurred while creating table {0}. {1} Explanation: Workload
Management was unable to create the specified table. User Response:
If the table is a bootstrap table, restart the Administrative Server.
If the problem persists, contact your service representative.
WWLM0012: Method {0} encountered an exception while inserting into table {1}.
{2} Explanation: Workload Management was unable to insert into
the specified table. User Response: If the problem persists, contact
your service representative.
WWLM0013: Method {0} encountered
an unexpected exception while updating table {1}. {2} Explanation:
Workload Management was unable to update the specified table.
User Response: If the problem persists, contact your service representative.
WWLM0014: Could not update Administrative Server information. {0}
Explanation: Workload Management was unable to update one or more of the
Administrative Servers with Workload Management information. User Response:
If the problem persists, contact your service representative.
WWLM0015: Method {0} encountered an unexpected exception while getting Server
Group information from table {1}. {2} Explanation: An unexpected
exception occurred. User Response: If the problem persists, contact
your service representative.
WWLM0016: Method {0} encountered
an exception while querying table {1}. {2} Explanation: Workload
Management was unable to query the specified table. User Response:
If the problem persists, contact your service representative.
WWLM0017: Method {0} encountered an exception while deleting server entry
from table {1}. {2} Explanation: Workload Management was unable
to delete the server entry from the specified table. User Response:
If the problem persists, contact your service representative.
WWLM0018: Entry {0} in table {1} was not found. Explanation: Workload
Management was unable to find the entry from the specified table.
User Response: If the problem persists, contact your service representative.
WWLM0019: Method {0} found no usable proxies in the list. {1}
Explanation: Workload Management was unable to find a server in the proxy
list. User Response: Workload Management resumes when servers become
available again.
WWLM0020: Could not resolve to an Administrative
Server to get server group information. {0} Explanation: Workload
Management was unable to get Administrative Server information. User
Response: Workload Management resumes when servers become available again.
WWLM0021: Server entry {0} differs from server {1} in method {2}.
Explanation: An internal recoverable error occurred which was unexpected.
The server entry differs from the one used to make an invocation within the
specified method. User Response: Contact your service representative.
WWLM0022: Cannot find an affinity object with ID {0} in the {1} method.
Explanation: Affinity was unexpectedly removed. User Response:
None
WWLM0023: No transaction available getting {0}
from {1}. {2} Explanation: Workload Management was unable to
get the transactional coordinator from the controller. User Response:
If this problem persists, contact your service representative.
WWLM0024: Could not retry call to retrieve server group information. {0}
Explanation: Workload Management was unable to retry getting the server
group information. User Response: If this problem persists, contact
your service representative.
WWLM0025: Unable to resume
transaction. {0} Explanation: Workload Management runtime suspended
the user transaction and was unable to resume it. User Response: Rollback
and retry the transaction. If this problem persists, contact your service
representative.
WWLM0026: Server group is already set in
{0) method. {1} Explanation: An internal error occurred which
was unexpected. The original server group was used. User Response:
Contact your service representative.
WWLM0027: Model
names are not the same in the {0} method. {1} {2} Explanation:
An internal error occurred which was unexpected. User Response:
Contact your service representative.
WWLM0028: Method
{0} encountered an unexpected exception. {1} Explanation: An
internal error occurred which was unexpected. User Response: If
this problem persists, contact your service representative.
WWLM0029: Method {0} encountered an unexpected exception getting {1} instance.
{2} Explanation: An internal error occurred which was unexpected.
The specified instance was not initialized. User Response: If this
problem persists, contact your service representative.
WWLM0030: Invalid server selection policy {0} in method {1}. {2}
Explanation: An internal error occurred which was unexpected.
User Response: Contact your service representative.
WWLM0031: Unable to create server selection policy class {0}. {1}
Explanation: An internal error occurred which was unexpected.
User Response: Contact your service representative.
WWLM0032: Server group name was not specified in {0}. Explanation:
An inappropriate use of a constructor occurred. User Response:
If this problem persists, contact your service representative.
WWLM0033: Service context list is null in method {0}. Explanation:
An internal error occurred which was unexpected. User Response:
If this problem persists, contact your service representative.
WWLM0034: Encountered an unexpected exception creating {0} instance. {1}
Explanation: An internal error occurred which was unexpected. The specified
instance was not created. User Response: If this problem persists,
contact your service representative.
WWLM0035: Could not
find any server entries in table {0}. Explanation: No servers
were found in specified table. User Response: Contact your service
representative.
WWLM0036: An unexpected exception occurred
when updating server group {0} with new server group information. {1}
Explanation: Unable to update server group information because of malformed
server group byte array parameter. User Response: If the problem
persists, contact your service representative.
WWLM0037:
Unable to find clone for IOR, {0}. Explanation: Workload Management
is unable to find the clone for the specified IOR. User Response: None
WWLM0038: During update of the {0} table a transaction already exits.
Explanation: Workload Management determined a transaction already exits.
User Response: None
WWLM0039: During update of the
{0} table the commit of the transaction failed with an exception. {1}
Explanation: Commit of the transaction failed. User Response: If
the problem persists, contact your service representative.
WWLM0040: The domain, {0}, could not be located because the property was not
set in the admin.config file. Explanation: WLM needs host and
port information to lookup foreign domain information. The host and port are
set in the admin.config file. User Response: Set the domain information
in the admin.config file as follows: com.ibm.websphere.adminDomain.bootstrap.<foreign_domain_name>=host:port
WWLM0041: Workload management support is limited to one domain.
Explanation: Workload balancing and failover are not available across
domains. User Response: The client should bootstrap into the domain
where workload management is required. XMLC0000I: Node {0} XML string: {1} Explanation:
None. User Response: None. XMLC0001W: Failure
to load information : {0}. Explanation: None. User Response:
None. XMLC0002E: Failed to map methods to method
groups. Explanation: None. User Response: None.
XMLC0003E: Failure to initialize {0} configuration.
Explanation: None. User Response: None.
XMLC0004E: Failure to find all({0}) Explanation: None.
User Response: None. XMLC0005E: Failure to find {0}
: {1} Explanation: None. User Response: None.
XMLC0006E: Failure to find Parent's Name. Exception {0}
Explanation: None. User Response: None.
XMLC0007E: Failure to create {0} : {1} Explanation: None.
User Response: None. XMLC0008E: Failure to update
{0} : {1} Explanation: None. User Response: None.
XMLC0009E: Failure to delete {0} : {1} Explanation:
None. User Response: None. XMLC0010E: Failure
to locate {0} : {1} Explanation: None. User Response:
None. XMLC0011E: Failure to start {0} : {1}
Explanation: None. User Response: None.
XMLC0012E: Failure to restart {0} : {1} Explanation: None.
User Response: None. XMLC0013E: Failure to stop {0}
: {1} Explanation: None. User Response: None.
XMLC0014E: Failure to enable {0} : {1} Explanation:
None. User Response: None. XMLC0015E: Failure
to disable {0} : {1} Explanation: None. User Response:
None. XMLC0016E: Failed to process children for Full
Export. Explanation: None. User Response: None.
XMLC0017E: Failure to install JDBC Driver {0} on node {1}.
Explanation: None. User Response: None.
XMLC0018E: Failure to uninstall JDBC Driver {0} on node {1}. Explanation:
None. User Response: None. XMLC0019E: Failure
to set attributes : {0}. Explanation: None. User Response:
None. XMLC0020E: Failure to export {0} : {1}
Explanation: None. User Response: None.
XMLC0021E: Failure to import {0} : {1} Explanation: None.
User Response: None. XMLC0022E: Failure to get name
of {0} : {1} Explanation: None. User Response: None.
XMLC0023E: Failure to get list of {0} : {1} Explanation:
None. User Response: None. XMLC0024E: Failure
to determine associated {0} : {1} Explanation: None.
User Response: None. XMLC0025E: Unable to populate
attributes from element : {0} Explanation: None. User
Response: None. XMLC0026E: Unable to populate element
from attributes {0} Explanation: None. User Response:
None. XMLC0027E: Unable to get cached configuration
: {0} Explanation: None. User Response: None.
XMLC0028W: Unable to get command line arguments : {0}
Explanation: None. User Response: None.
XMLC0029W: Unable to get environment : {0} Explanation: None.
User Response: None. XMLC0030E: Unable to export :
{0} Explanation: None. User Response: None.
XMLC0031I: Unable to import : {0} Explanation:
None. User Response: None. XMLC0032I: Unable
to create : {0} Explanation: None. User Response: None.
XMLC0033I: Unable to locate file : {0} Explanation:
None. User Response: None. XMLC0034W: Unable
to get cookie data : {0} Explanation: None. User Response:
None. XMLC0035W: Unable to get database data : {0}
Explanation: None. User Response: None.
XMLC0036E: Unable to get web application attributes in order to calculate
root URI. Root URI will be set to null Explanation: None.
User Response: None. XMLC0037E: Unable to save exported
data to file : {0}:{1} Explanation: None. User Response:
None. XMLC0038I: Unable to read import document :
{0} Explanation: None. User Response: None.
XMLC0039I: Unable to create trace log to file: : {0}
Explanation: None. User Response: None.
XMLC0040E: Could not access the node at which this bean will reside.
Explanation: None. User Response: None.
XMLC0041E: Repository Exception {0} Explanation: None.
User Response: None. XMLC0042E: Naming Exception {0}
Explanation: None. User Response: None.
XMLC0043E: Remote Exception {0} Explanation: None.
User Response: None. XMLC0044E: Finder Exception {0}
Explanation: None. User Response: None.
XMLC0045E: Remove Exception {0} Explanation: None.
User Response: None. XMLC0046E: Exception {0}
Explanation: None. User Response: None.
XMLC0047E: OpException {0} Explanation: None. User Response:
None. XMLC0048E: Class Cast Exception: {0}
Explanation: None. User Response: None.
XMLC0049E: Create Exception : {0} Explanation: None.
User Response: None. XMLC0050I: Finished deploying
EJB and renamed jar file to {0}. Explanation: None.
User Response: None. XMLC0051I: Deploying {0} : {1}
Explanation: None. User Response: None.
XMLC0052I: Exporting {0} : {1} Explanation: None. User
Response: None. XMLC0053I: Importing {0} : {1}
Explanation: None. User Response: None.
XMLC0054W: Creating {0} : {1}, since it was not found for update.
Explanation: None. User Response: None.
XMLC0055W: Updating {0} : {1}, since it was already created Explanation:
None. User Response: None. XMLC0056I: Installing
{0} : {1} Explanation: None. User Response: None.
XMLC0057I: Uninstalling {0} : {1} Explanation:
None. User Response: None. XMLC0058I: Uninstalling
JDBC Driver {0} from Node {1}. Explanation: None. User
Response: None. XMLC0059I: Installing JDBC Driver:
{0} on node {1} Explanation: None. User Response: None.
XMLC0060E: Processing partial export for {0} : {1}
Explanation: None. User Response: None.
XMLC0061I: {0} Attribute will not be set : {1} Explanation: None.
User Response: None. XMLC0062I: JDBC Driver attribute
will not be set Explanation: None. User Response: None.
XMLC0063I: Install will not be performed Explanation:
None. User Response: None. XMLC0064I: Uninstall
will not be performed Explanation: None. User Response:
None. XMLC0065I: Since it was not found for update
Explanation: None. User Response: None.
XMLC0066I: Since it was already created Explanation: None.
User Response: None. XMLC0067I: {0} Does not exist.
Explanation: None. User Response: None.
XMLC0068I: {0} Does not exist, will create new one. Explanation:
None. User Response: None. XMLC0069I: {0}
Already exists. Explanation: None. User Response: None.
XMLC0070I: Exception when creating or deploying a jar file.
Explanation: None. User Response: None.
XMLC0071I: Exception in getHome, will retry with unqualified home name {0}.
Explanation: None. User Response: None.
XMLC0072I: Exception in getHome using unqualified home name {0}.
Explanation: None. User Response: None.
XMLC0073I: Continuing Child Processing.Exception: {0} Explanation:
None. User Response: None. XMLC0074I: Ending
Child Processing. Exception : {0} Explanation: None.
User Response: None. XMLC0075E: Missing required attribute,{0}
must be specified! Create operation has been terminated. Explanation:
None. User Response: None. XMLC0076I: Following
operation has been terminated: {0} Explanation: None.
User Response: None. XMLC0077E: Missing required element
: {0} Explanation: None. User Response: None.
XMLC0078I: Missing required attribute : {0} Explanation:
None. User Response: None. XMLC0079I: At
least one URI path must be specified. Explanation: None.
User Response: None. XMLC0080I: Following must be
specified : {0} Explanation: None. User Response: None.
XMLC0081E: Missing required attribute, jar file not set, create
cannot continue. Explanation: None. User Response: None.
XMLC0082I: Empty deployment descriptor, create or update will
fail. Explanation: None. User Response: None.
XMLC0083E: Failed to update {0}: {1} does not exist. Please
use the create action. Explanation: None. User Response:
None. XMLC0084E: Failed to create {0}. {1} already
exists. Please use the update action. Explanation: None.
User Response: None. XMLC0085W: The locate action
has been ignored for URI {0}. URIs do not contain any children.
Explanation: None. User Response: None.
XMLC0086I: Root URI will be set to null. Explanation: None.
User Response: None. XMLC0087I: Unable to create initial
context. Please check name service settings: {0} Explanation:
None. User Response: None. XMLC0088W: Make
sure the Websphere <root>/properties directory is in the classpath.
Explanation: None. User Response: None.
XMLC0089W: server.root cannot be set and will remain null. Explanation:
None. User Response: None. XMLC0090I: Cannot
determine proper node name. Explanation: None. User
Response: None. XMLC0091E: No {0} specified for {0}
security Explanation: None. User Response: None.
XMLC0092E: Empty deployment descriptor, HomeName {0} was probably
specified incorrectly, create or update will fail. Explanation:
None. User Response: None. XMLC0093I: Create
action is not supported on this type of object. Explanation: None.
User Response: None. XMLC0094E: Delete action is not
supported on this type of object. Explanation: None.
User Response: None. XMLC0095E: Restart action is
not supported on this type of object. Explanation: None.
User Response: None. XMLC0096E: Enable action is not
supported on this type of object. Explanation: None.
User Response: None. XMLC0097E: Disable action is
not supported on this type of object. Explanation: None.
User Response: None. XMLC0098E: Start action is not
supported on this type of object. Explanation: None.
User Response: None. XMLC0099E: Stop action is not
supported on this type of object. Explanation: None.
User Response: None. XMLC0100E: Update action is not
supported on this type of object. Explanation: None.
User Response: None. XMLC0101I: Locate action is not
supported on this type of object. Explanation: None.
User Response: None. XMLC0102I: The locate action
has been ignored for Explanation: None. User Response:
None. XMLC0103I: Invalid Command Line!
Explanation: None. User Response: None.
XMLC0104I: !Odd number of arguments specified. Explanation: None.
User Response: None. XMLC0105I: !You must specify
either -import or -export. Explanation: None. User Response:
None. XMLC0106I: !You cannot specify both -import
and -export Explanation: None. User Response: None.
XMLC0107I: ! You must specify the primary node name.
Explanation: None. User Response: None.
XMLC0108I: !Illegal argument specified: Explanation: None.
User Response: None. XMLC0109I: !Illegal input file:
{0} Explanation: None. User Response: None.
XMLC0110E: !HomeName {0} was specified incorrectly.
Explanation: None. User Response: None.
XMLC0111I: Substitute can not be used with export option! Explanation:
None. User Response: None. XMLC0112I: Malformed
substitute string ! Explanation: None. User Response:
None. XMLC0113W: No authentication mechanism defined.
Explanation: None. User Response: None.
XMLC0114E: No authentication mechanism properties defined. Exception {0}
Explanation: None. User Response: None.
XMLC0115I: You must restart the administrative server for security changes
to take effect! Explanation: None. User Response: None.
XMLC0116W: LTPA is set but no LTPAConfig object exists.
Explanation: None. User Response: None.
XMLC0117W: No authentication mechanism is configured Explanation:
None. User Response: None. XMLC0118W: Unknown
user registry is configured. Cannot export. Explanation: None.
User Response: None. XMLC0119I: java com.ibm.websphere.xmlconfig.XMLConfig
{ ( -import<xml data file>) || { ( -import<xml data file>) || [ ( -export<xml
output file>[-partial<xml data file>] ) }[ ( -export<xml output file>[-partial<xml
data file>] ) } -adminNodeName<primary node name>-adminNodeName<primary
node name>[ -nameServiceHost<host name>[ -nameServicePort<port number>]][
-nameServiceHost<host name>[ -nameServicePort<port number>]] [-trace
string<trace spec>[-trace file<file name>]][-trace string<trace spec>[-trace
file<file name>]] value2;[...]]\">]}value2;[...]]\">]} In input xml file,
the key(s) should appear as $key$ for substitution. Explanation:
None. User Response: None.
|