WebSphere Channel Framework messages |
CHFW0001E: {0} is missing or is not a directory.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0002E: Channel implementation {0} could not be opened: {1}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0003E: Channel implementation {0} does not have a channel descriptor.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0004E: Errors parsing channel descriptor from {0}: {1}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0005E: Channel implementation {0} does not specify a factory runtime class.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0006E: Channel implementation {0} does not specify a channel configuration class.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0007E: Channel implementation {0} does not specify device- or application-side interfaces.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0008E: Channel implementation {0} specifies an invalid default weight of {1}.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0009E: Chain {0} does not contain any transport channels.
Explanation:
Chains must contain transport channels to function.
User Response:
Add some transport channels to {0}.
CHFW0010E: The transport channels of chain {0} must all flow in the same direction.
Explanation:
Channels can flow into (inbound) or out of (outbound) a server; all transport channels in a chain must flow in the same direction.
User Response:
Ensure that all of the transport channels in chain {0} are either inbound or outbound channels; do not mix inbound and outbound in the same chain.
CHFW0011E: The first transport channel in chain {0} is not a connector channel.
Explanation:
The first transport channel in an in inbound chain must be a connector channel.
User Response:
Ensure that the first transport channel in the inbound chain is a connector channel.
CHFW0012E: The last transport channel in chain {0} is not an acceptor channel.
Explanation:
The last transport channel in an inbound chain must be an acceptor channel.
User Response:
Ensure that the last transport channel in the inbound chain is an acceptor channel.
CHFW0013E: Failed to determine acceptorID for chain {0}.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0014E: Could not find channel descriptor to match channel configuration type {0}.
Explanation:
Channels must provide a descriptor to map configuration types to runtime types; no matching descriptor could be found for configuration type {0}.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0015E: Failed to obtain initial naming context: {0}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0016E: Failed to load transport channel factory: {0}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0017E: Failed to load transport channel: {0}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0018E: Failed to load chain: {0}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0019I: The Transport Channel Service has started chain {0}.
Explanation:
The Transport Channel Service has started the specified chain.
User Response:
none
CHFW0020I: The Transport Channel Service has stopped the Chain labeled {0}.
Explanation:
The Transport Channel Service has stopped the specified chain.
User Response:
none
CHFW0021I: Inbound chain {0} has been marked disabled.
Explanation:
Inbound chains must be explicitly marked as enabled to be eligable for automatic startup. Disabled chains may still be started, but they must be explictly started by name.
User Response:
none
CHFW0022E: The Transport Channel Service could not locate its configuration due to an exception: {0}
Explanation:
The Transport Channel Service encountered an exception whilst attempting to discover and load its configuration; it will be started without configuration.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0023I: The Transport Channel Service could not locate its configuration but will be started without it.
Explanation:
The Transport Channel Service could not locate its configuation. Default configuration for the Transport Channel Service should be added to server.xml.
User Response:
Use the admin console or wsadmin to add default configuration for the Transport Channel Service.
CHFW0024I: The Transport Channel Service has been explicitly disabled.
Explanation:
The Transport Channel Service has been explicitly configured to be disabled and will not be started.
User Response:
none
CHFW0025E: Channel implementation {0} does not specify a factory configuration class.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0026E: Could not find channel factory descriptor to match transport channel configuration type {0}.
Explanation:
Channels must provide a descriptor to map configuration types to runtime types; no matching descriptor could be found for configuration type {0}.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0027I: One or more transport channel implementations failed to load
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0028E: The last transport channel in chain {0} is not a connector channel.
Explanation:
The last transport channel in an outbound chain must be a connector channel.
User Response:
Ensure that the last transport channel in the outbound chain is a connector channel.
CHFW0029E: Error initializing chain {0} because of exception {1}
Explanation:
An exception was caught in either the chain or underlying channels.
User Response:
Ensure the right channels are being used in the chain.
CHFW0030E: Error starting chain {0} because of exception {1}
Explanation:
An exception was caught in either the chain or underlying channels.
User Response:
Ensure the right channels are being used in the chain.
CHFW0031E: Error stopping chain {0} because of exception {1}
Explanation:
An exception was caught in either the chain or underlying channels.
User Response:
Ensure the right channels are being used in the chain.
CHFW0032E: Error destroying chain {0} because of exception {1}
Explanation:
An exception was caught in either the chain or underlying channels.
User Response:
Ensure the right channels are being used in the chain.
CHFW0033E: The Transport Channel Service failed to start transport chain {0} after {1} attempts to start it.
Explanation:
The configured number of retries were not enough to cause the chain to start.
User Response:
Ensure the port used by the chain is not already in use. Correctly set the custom properties for restarting chains.
CHFW0034W: The Transport Channel Service detected transport chain {0} failed. The service will retry to start chain {0} every {1} milliseconds for up to {2} attempts.
Explanation:
The initial attempt to start a chain failed, but future attempts will be made to get it started.
User Response:
Watch for an error or audit message indicating the result of the retry attempts.
CHFW0035E: The Transport Channel Service found and invalid value of {0} for property {1}.
Explanation:
The value of the property was out of the expected bounds.
User Response:
Adjust the configuration to set the property to a valid value.
CHFW0040W: The non-sharable channel, {0}, is being started in both the z/OS control and the z/OS control adjunct region
Explanation:
A channel is defined as non-sharable, but WebSphere Application Server is configured to use this channel in both a z/OS control and a z/OS control adjunct region. This conflict can cause WebSphere Application Server to function improperly.
User Response:
Configure WebSphere Application Server so that the channel is not used in both the z/OS control and the z/OS control adjunct region.
CHFW0600E: Error loading command {0}: {1}
Explanation:
CSMG0001E
User Response:
CSMG0002E
CHFW0600E: Error loading command {0}: {1}
Explanation:
CSMG0001E
User Response:
CSMG0002E
CHFW0801E: More than one factory instance exists for type {0}
Explanation:
There should only be one configured instance of each unique factory type.
User Response:
Please use either the admin application or the command line scripting tool to remove duplicate instances of the same type.
CHFW0802E: More than one channel exists with name {0}
Explanation:
Channels instances must have unique (case-sensitive) names.
User Response:
Please use either the admin application or the command line scripting tool to give channels unique names.
CHFW0803E: More than one chain exists with name {0}
Explanation:
Chain instances must have unique (case-sensitive) names.
User Response:
Please use either the admin application or the command line scripting tool to give chains unique names.
CHFW0804E: Chain {0} currently does not have any member channels
Explanation:
Chains must have at least one member channel.
User Response:
Please use either the admin application or the command line scripting tool to add at least one channel to the chain in question.
CHFW0805E: Chain {0} has incompatible channel types {1} and {2} next to each other
Explanation:
Interfaces emitted/accepted must match the interfaces accepted/emitted by the next channel in the chain.
User Response:
Please use either the admin application or the command line scripting tool to re-order channels or add new channels to the chain in question.
CHFW0806E: Channel {0} does not have a name.
Explanation:
Each channel must a unique name.
User Response:
Please use either the admin application or the command line scripting tool to re-order channels or add new channels to the chain in question.
CHFW0807E: Could not load {0} to validate type {1}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0808E: Class {0} used to validate type {1} is not an extension of {2}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0809E: Could not create an instance of {0} to validate type {1}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0810W: No channel factories present in configuration
Explanation:
There are currently no configured channel factories.
User Response:
None needed
CHFW0811W: No channels present in configuration
Explanation:
There are currently no configured channels.
User Response:
None needed
CHFW0812W: No chains present in configuration
Explanation:
There are currently no configured chains.
User Response:
None needed
CHFW0813E: Caught exception whilst validating ChannelFrameworkService: {0}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0814E: Could not find channel type information for {0}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0815E: Validator for type {0} unspecified
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0816E: Inbound channel {0} does not have a discrimination weight.
Explanation:
tbd
User Response:
Set a disrimination weight on {0}.
CHFW0817E: Inbound channel {0} has an invalid discrimination weight of {1}.
Explanation:
tbd
User Response:
Set a valid discrimination weight on {0}.
CHFW0818E: Chain {0} does not have a name.
Explanation:
Each chain must a unique name.
User Response:
Please use either the admin application or the command line scripting tool to re-order channels or add new channels to the chain in question.
CHFW0819E: Channel {0} in chain {1} does not flow in the same direction as the first channel in the chain.
Explanation:
All channels in a chain must flow in the same direction.
User Response:
Replace {0} with it's corresponding channel type that flows in the opposite direction.
CHFW0820E: Could not determine channel kind information for {0}.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0821E: First channel ({0}) in chain {1} is not a connector channel.
Explanation:
tbd
User Response:
Replace {0} with a connector channel in chain {1}.
CHFW0822E: Last channel ({0}) in inbound chain {1} is not an acceptor channel.
Explanation:
tbd
User Response:
Replace {0} with an acceptor channel in chain {1}.
CHFW0823E: Chain {1} contains channel {0} more than once.
Explanation:
Channels can only occur at one position in a chain.
User Response:
Remove extra occurances of {0} in chain {1}.
CHFW0824E: Could not find channel factory type information for {0}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0825E: Chain {0} failed coherency check because the channel type for one or more channels could not be found.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CHFW0826E: Last channel ({0}) in chain {1} is not a connector channel.
Explanation:
tbd
User Response:
Replace {0} with a connector channel in chain {1}.