Mediator Messages

0010.0345 AliasesController.updateAliases - Deployment request for runtime alias is null
Class Debug
Explanation

Mediator received an alias deployment request with null values.

Action

Check the deployment request and specify valid information in the request.


0010.0715 Mediator Upgrade, did not complete successfully.
Class E
Explanation

This log message may occur when the Mediator package loads during the Integration Server restart after an overinstall. This message indicates the upgrade was not successful. There should be a previous error message in the server log that indicates the problem.

Action

See actions for message ID '0010.0702'


0010.0753 Successfully migrated Mediator cache configuration file

0010.0786 Error initializing runtime aliases. {0}
Class Error
Explanation

Mediator could not initialize the XML data for the runtime alias.


0010.0811 AliasesController.removeAliases - Cannot delete alias. Null values found in the request field(s).
Class Debug Error
Explanation

Mediator received an alias undeployment request with null values in one or more fields.

Action

Verify the request and resend the request with valid values in the fields.


0010.0814 Error retrieving the secure alias: {0}. {1}
Class Error
Explanation

Error while retrieving the secure string for the alias from the Integration Server password manager.

Action

Check the Integration Server password manager for details on the secure alias string.


0010.0815 Error saving the secure alias: {0}. {1}
Class Error
Explanation

Error while saving the secure string for the alias to the Integration Server password manager.

Action

Check the Integration Server password manager for the secure alias string.


0010.0816 Secure alias does not contain a secure string. Secure alias: {0}
Class Error
Explanation

The secure alias does not have a secure string associated with it.

Action

Enter a valid secure string for the secure alias and try again.


0010.0817 Secure alias has invalid secure string encoding. Secure alias: {0}
Class Error
Explanation

The secure string assigned to the secure alias is not valid.

Action

Check if the secure string is properly encoded.


0010.0852 Mediator could not deploy the service, {0}. {1}
Explanation

An error occurred while parsing the default content type values for the service. Hence, the service could not be deployed.

Action

Check the Integration server logs for more details.


0010.0853 Service failed because of an incorrect value for the default content type. Service: {0}; default content type: {1}
Explanation

The default content type you provided for the service is either not valid or not supported by Mediator.

Action

Check the default content type provided to the service. A list of the content types support by Mediator is available in the product documentation.


0010.0855 Mediator cannot deploy the service because the SOAP action in the REST request received is not suitable.
Explanation

Mediator could not find a suitable SOAP action for the REST request received from the consumer.

Action

Redeploy the service with the correct SOAP action.


0010.0868 Mediator is performing start-up tasks, please wait ...
Explanation

User trying to attempt deployment while loading service(s) from cache/disk at start-up.

Action

Please wait to trigger deployment task until complete the Mediator start-up tasks


0030.0092 PublisherPropsObserver - Unknown sender data type ({0})
Explanation

The properties observer received an invalid sender type.

Action

This indicates a coding error. Non-Mediator code should never call this method.


0030.0094 PublisherPropsObserver - Unknown parameters data type ({0})
Explanation

The properties observer received an invalid update object type.

Action

This indicates a coding error. Non-Mediator code should never call this method.


0030.0099 PublisherPropsObserver - Unknown wrapper factory data type ({0})
Explanation

This message has incorrect text. It should indicate an invalid data type for UDDP publisher bean.

Action

Update the pg configuration file to use a proper UDDI publisher data type.


0030.0100 PublisherPropsObserver - Unable to find wrapper factory
Explanation

There is no UDDI publisher configured, but its properties are being changed.

Action

Update the configuration file. Either configure a UDDI publisher or unregister the UDDI properties observer.


0030.0104 Exception encountered initializing logging resource: {0}
Explanation

A problem was encountered while setting up a logger for Mediator to use. There should be an exception message with more details.

Action

Fix the problem identified by the exception message.


0030.0109 PublisherPropsObserver - Can't convert string ({0}) to integer for publishing interval, ignoring input
Explanation

The value received for performance data reporting interval was not a valid numeric string.

Action

Make sure a numeric value is input.


0030.0113 PublisherPropsObserver - Unknown pg service deployer data type ({0})
Explanation

The data typi of the PG Service Deployer bean is invalid.

Action

Update the pg configuration file to use a proper PG Service Deployer data type.


0030.0301 ConsumerApplicationManager.convert - cannot handle null request
Explanation

Unable to create Consumer deployment object for update.

Action

Probably bad SOAP request to Deployer, fix request.


0030.0302 ConsumerApplicationManager.convert - cannot convert consumer with null {0}
Explanation

Invalid Consumer deployment object was found.

Action

Probably bad SOAP request to Deployer, fix request.


0030.0303 VirtualServiceDeployer.{0} - cannot handle null {1}
Explanation

A null reference was found during a deployment activity. The object and activity are identified in the message.

Action

Probably bad SOAP request for deployment, fix request.


0030.0304 VirtualServiceDeployer.deploy - service ({0}) already deployed, undeploying
Action

Info level message, no action required.


0030.0305 VirtualServiceDeployer.undeploy - cannot undeploy service ({0}), not deployed
Explanation

Attempt to undeploy virtual service failed.

Action

Verify that Mediator and CentraSite agree that the service is no longer deployed. If not, try undeploying this service again, or restarting Mediator/IS.


0030.0306 VirtualServiceDeployer.{0} - caught this: type({1}) message({2})
Explanation

Unable to deploy virtual service. See exception message for more details.

Action

Address the problem indicated by exception and try to deploy again.


0030.0309 ClusteredServiceDeployer{0} - cannot handle null {1}
Explanation

Unable to create VS deployment object for update.

Action

Probably bad SOAP request to Deployer, fix request.


0030.0315 ClusteredConsumerManager.updateConsumer - cannot handle null consumer
Explanation

Unable to create Consumer object for update.

Action

Probably bad SOAP request to Deployer, fix request.


0030.0318 ClusteredServiceDeployer - cannot deploy null info to cache
Explanation

A problem occurred while attempting to convert a PGService for deployment to shared cache. There should be another message describing the conversion or deployment issue.

Action

Fix the conversion or deployment problem.


0030.0319 ClusteredServiceDeployer - cannot undeploy null service name from cache
Explanation

Virtual service undeployment requires a non-empty service name. This is problem with undeployment request payload.

Action

Fix the undeployment request payload.


0030.0328 ConsumerApplicationManager.{0} - cannot handle null update request
Explanation

Invalid Consumer deployment request for update.

Action

Probably bad SOAP request to Deployer, fix request.


0030.0330 ConsumerApplicationManager - not updating consumer ({0}), modification date, ({1}), is no more recent
Action

Info level message, no action required.


0030.0333 ConsumerApplicationManager.{0} - caught this: type({1}) message({2})
Explanation

Unable to create and persist Consumer object for update.

Action

Either bad SOAP request to Deployer, fix Request. Or file system problem, check file system permissions. See logged message text for specific error details.


0030.0336 Consumer Application Update Failed; requested update has invalid {0} field
Explanation

Invalid consumer name or key in remove request.

Action

Probably bad SOAP request to Deployer, fix request.


0030.0337 Consumer Application Remove Failed; consumer ({0}) does not exist
Explanation

Attempt to remove consumer failed.

Action

Reply to CentraSite Deployment attemp should indicate error. Try redeploying this consumer or resynchronizing all consumers.


0030.0343 RegisteredConsumerNamesManager.{0} - cannot handle null update request
Explanation

Invalid RegisteredConsumerNames deployment request for update.

Action

Probably bad SOAP request to Deployer, fix request.


0030.0344 Registered Consumer Names Update Failed; requested update has invalid {0} field
Explanation

Invalid service name or consumer names in registered consumer names update request.

Action

Probably bad SOAP request to Deployer, fix request.


0030.0346 RegisteredConsumerNamesManager - not updating consumer names registered to ({0}), modification date, ({1}), is no more recent
Action

Info level message, no action required.


0030.0347 RegisteredConsumerNamesManager.{0} - cannot handle null update request
Explanation

Invalid RegisteredConsumerNames deployment request for remove.

Action

Probably bad SOAP request to Deployer, fix request.


0030.0348 Registered Consumer Names Remove Failed; requested update has invalid {0} field
Explanation

Invalid service consumer name in remove request.

Action

Probably bad SOAP request to Deployer, fix request.


0030.0350 Registered Consumer Names Remove Failed; service ({0}) has no registered consumers
Explanation

Invalid request to remove RegisteredConsumerNames, must include at least one consumer name.

Action

Probably bad SOAP request to Deployer, fix request.


0030.0352 RegisteredConsumerNamesManager.{0} - caught this: type({1}) message({2})
Explanation

Unable to create and persist RegisteredConsumerNames object for update.

Action

Either bad SOAP request to Deployer, fix Request. Or file system problem, check file system permissions. See logged message text for specific error details.


0030.0356 VirtualServiceDeployer - unable to get endpoints for {0}, caught this: type({1}), msg({2})
Explanation

Unable to obtain endpoint for deployed service.

Action

Probably bad SOAP request to Deployer or bad VSD, fix one or both.


0030.0357 ClusteredRegisteredConsumerNamesDeployer.updateConsumerNames - cannot handle null reg names object
Explanation

Unable to create RegisteredConsumerNames object for update.

Action

Probably bad SOAP request to Deployer, fix request.


0030.0358 Consumer Application Remove Failed; requested update has invalid name and key fields, both are empty
Explanation

Consumer remove request must have either name or key to identify consumer; both were null or empty.

Action

Probably bad SOAP request to Deployer, fix request.


0030.0359 ConsumerApplicationManager - Consumer update request has invalid IP range; from ({0}) to ({1})
Explanation

Consumer update request had invalid IP address range.

Action

Probably bad SOAP request to Deployer, fix request.


0030.0361 VirtualServiceDeployer - redeploying undeployed service ({0}), deployment failed for newer version
Action

Info level message, no action required.


0030.0362 VirtualServiceDeployer - a problem was encountered during deployment, ({0}) will be undeployed and replaced if necessary
Action

Info level message, no action required.


0030.0363 VirtualServiceDeployer.{0} - service({1}) caught this: type({2}) message({3})
Explanation

Message context encountered an exception while attempting to redeploy or undeploy a virtual service. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0030.0364 Deployment request for service: {0}. Registered consumer name element was processed, but the existing modification date is the same as the request. {1}
Action

Info level message, no action required.


0030.0366 UddiPropertiesObserver - Password lookup failed; type ({0}), message ({1})
Explanation

A problem was encoutnered by attempting to retrieve stored password. There should be an exception with more specific trouble description.

Action

Fix the problem identified by the exception message.


0030.0367 UddiPropertiesObserver - Unable to activate performance date policies; type ({0}), message ({1})
Explanation

The performance data deployer was unable to run. This message should include more details regarding the reason.

Action

Fix the problem identified by the exception message.


0030.0370 Unable to connect to UDDI: ({0}); property updates saved, but data collection is OFF.
Explanation

A problem was encountered during publisher test.

Action

This is probably a bad configuration parameter, fix it.


0030.0371 UddiPropertiesObserver - Unable to convert port string ({0}) to integer, using default port {1}
Explanation

The value input for 'UDDI port' number is non-numeric.

Action

Input an numeric port value.


0030.0396 Exception in AliasesController.{0}. Alias type: {1}, message: {2}
Class Debug
Explanation

Mediator is unable to create and persist an alias during an update.

Action

Verify the access permissions in the file system. See the Mediator error logs for details.


0030.0398 Runtime alias update failed. The update request contains an invalid field: {0}
Class Error
Explanation

The SOAP request sent to the Deployer contains an invalid field.

Action

Resend the request with a valid value for the field.


0030.0399 SimpleAliasDeploymentManager.convert - Cannot deploy simple alias: {0}. Null value in field(s)
Class Debug
Explanation

Mediator found an invalid simple alias during deployment.

Action

Resend the request with a valid value for the field(s).


0030.0410 Error undeploying alias. Alias is associated with services. Alias: {0}, services: {1}
Class Error
Explanation

You are trying to undeploy an alias which is already deployed to a service. If you continue with undeploy, the associated services will not be usable.

Action

Remove the association between the alias and the service that you want to delete, or undeploy the associated services before you undeploy the alias.


0030.0412 EndpointAliasDeploymentManager.convert - Cannot deploy endpoint alias: {0}. Null value in field(s)
Class Debug error
Explanation

Mediator found an invalid endpoint alias during deployment.

Action

Resend the request with a valid value for the field(s)


0030.0419 AliasesDeploymentManager.convert - Cannot deploy alias: {0} of type {1}. Null value in field: {2}
Explanation

Mediator found an invalid alias of type {1} during deployment. Alias Name: {0} Reason - Null value in field: {2}

Action

Resend the request with valid value for the field : {2}


0030.0420 Deployment of webMethods IS Alias {0} failed because no webMethods IS service exists with the given service name {1} in Mediator.
Explanation

Cannot deploy webMethods IS Alias with alias name : {0} and service name : {1}. No webMethods IS Service exists with given service name {1} in Mediator.

Action

Resend the deploy request with valid webMethods IS service name.


0050.0001 Unable to find Policy Element in the VSD:{0}
Explanation

An exception was encountered while attempting to extract a policy element from VSD. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0002 Unable to create Rampart properties:{0}
Explanation

An exception was encountered while attempting to assemble Rampart keystore properties. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0003 Unable to replace static Rampart configuration with configured properties:{0}
Explanation

An exception was encountered while attempting to re-configure Rampart keystore properties. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0004 Unable to create Rampart Configuration Element:{0}
Explanation

An exception was encountered while attempting to convert Rampart configuration string to XML. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0005 Unable to create XPath to select first Policy Alternative:{0}
Explanation

An exception was encountered while attempting to create an Xpath object. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0006 Error while removing existing RampartConfig elements:{0}
Explanation

An exception was encountered while attempting to remove configuration elements. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0007 Required configuration information to enable WS-Security processing is missing. Unable to process service: {0}. Please ensure Keystore/Truststore information is configured
Explanation

Service could not be initialized due to a problem with keystore/trustore configuration.

Action

Fix the security configuration.


0050.0011 Exception while determining hostname or IP address of the server:{0}
Explanation

An exception was encountered while attempting to resolve a host name or IP address. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0013 Mediator needs the repository location of the SOAP Stack
Explanation

Configuration does not include a valid location for Axis2 repositoryconfiguration.

Action

Fix the axis2 configuration.


0050.0016 ServerManager ready for processing
Action

Info level message, no action required.


0050.0017 Mediator encountered exception while starting ServerManager:{0}
Explanation

An exception was encountered during configuration of Axis2 listeners. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0018 Invalid Port specified. Using default configuration: {0}
Explanation

The 'port' property has a non-numeric string value, the value configured in Axis is used.

Action

Make sure the property value to numeric.


0050.0019 Port {0} is already in use. Trying alternate
Explanation

The port indicated in the message is not available to use with a new socket.

Action

Specify another port value in the system 'port' property or Axis configuration.


0050.0020 Exception while creating "id" selection XPath: {0}
Explanation

Message context encountered an exception while attempting to create an XPath object. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0021 Found Element within Resources element with id: {0}
Action

Info level message, no action required.


0050.0022 Exception while selecting element with id:{0} in Resources Element: {1}
Explanation

Message context encountered an exception while attempting to extract the indicated element from XML. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0023 Mediator received a response for the request with message Id :{0} But a callback is not registered (anymore) to process this response
Explanation

No callback was registered at the time this response was processed.

Action

This is probably a VS configuration problem.


0050.0024 Mediator received a response message without a message Id
Explanation

There was a problem relating the native service response to a virtual service request.

Action

Look for previously logged message indicating that message Id was not used.


0050.0025 Mediator encountered an exception: {0}. No error handlers found - [Message Dropped]
Explanation

This could be a configuration problem. An exception was encountered while attempting to handle a fault. The associated exception message should include more details regarding the problem.

Action

Fix the configuration, or other problem identified by the exception message.


0050.0029 VSD with incorrect Namespace:{0}. Unable to create PGService.
Explanation

The namespace found in the VSD is unknown.

Action

This is a virtual service configuration problem.


0050.0031 The {0} element is required for a Mediator Service
Explanation

Some element used during service deployment was found to be null. The specific element should be identified in the message text.

Action

This is a virtual service configuration problem.


0050.0032 The {0} sequence element is required for a Mediator Service
Explanation

The VSD is missing the sequence element identified in the message.

Action

This is a virtual service configuration problem.


0050.0033 The inSequence for VSD:{0} is invalid.
Explanation

The sequence identified in the message failed validation. Look for recent error message with more validation failure details.

Action

This is a virtual service configuration problem.


0050.0034 The outSequence for VSD:{0} is invalid.
Explanation

The sequence identified in the message failed validation. Look for recent error message with more validation failure details.

Action

This is a virtual service configuration problem.


0050.0035 Exception while parsing Virtual Service String Definition:{0}
Explanation

An exception was encountered while attempting to parse the virtual service description. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0036 Unable to create Virtual Service Definition
Explanation

Unable to create XML object from the VSD string.

Action

This is a virtual service configuration or deployment problem.


0050.0037 PGServiceFactory encountered and exception while creating the PGService: {0}
Explanation

An exception was encountered while attempting to validate input or output sequence or during WSDL URI processing. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0038 Invalid parameter specified for PGService: {0}
Explanation

The attribute named in the message has no value in the VSD.

Action

This is a virtual service configuration problem.


0050.0039 Exception {0} for PGService: {1}
Explanation

An exception was encountered while attempting during service creation. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0040 No PGService found with name: {0}
Explanation

Attempting to undeploy or get endpoints for a service that does not exist.

Action

Make sure the virtual service exists before operating on it.


0050.0041 WSStack exception processing service: {0} Cause: {1}
Explanation

An AxisFault was encountered while attempting to either undeploy or get endpoints for the virtual service named in the message. The associated fault message should include more details regarding the problem.

Action

Fix the problem identified by the fault message.


0050.0042 Unable to locate the WSStack configuration. Can't deploy Virtual Service:{0}
Explanation

The Synapse configuration cannot supply an Axis configuration.

Action

This is an Axis2/Synapse/WS-Stack configuration problem.


0050.0043 A Virtual Service with name:{0} already exists. Unable to deploy.
Explanation

Cannot deploy an Axis service when one already exists with the same name.

Action

Undeploy the existing service before attempting to redeploy or use the same name.


0050.0044 Unable to locate WSStack configuration. Please check if WSStack is enabled/correctly configured.
Explanation

Unable to retrieve the configuration context supplier bean.

Action

This is a Spring bean configuration issue, the pg-config.xml file is missing or corrupted.


0050.0045 Invalid parameter passed for Virtual Service creation:{0}
Explanation

An attempt to persist the VSD for a service found a null element. The VSD is not allowed to be null.

Action

This may be the result of invalid deployment payload; fix the VSD.


0050.0046 Unable to persist VSD:{0} to disk. Encountered error:{1}
Explanation

An exception was encountered while attempting to serialize the VSD for the service identified in the message. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0047 Unable to {0} VSD:{1}. Error:{2}
Explanation

This message is used in several different error conditions, as indicated by the object of 'unable to...'.

Action

Fix the 'unable to...' problem for the service identified by 'VSD:'.


0050.0048 Error getting endpoints for service:{0}, Cause: {1}
Explanation

An exception was encountered while attempting to get endpoints. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0049 Exception while creating PGService: {0}, Cause: {1}
Explanation

An AxisFault was encountered while checking if deploying service already exists or while attempting to register service with Axis2. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0050 Error while engaging module: {0}
Explanation

An AxisFault was encountered while attempting to engage the Axis2 module indicated in the message. The associated fault message should include more details regarding the problem.

Action

Fix the problem identified by the fault message.


0050.0052 Axis was unable to load module {0}
Explanation

An exception was encountered while attempting to load and engage module identified in message. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0053 Loading the WSDL : {0}
Action

Info level message, no action required.


0050.0055 PGService {0} encountered error while converting wsdl element to a StreamSource:{0}
Explanation

An exception was encountered while attempting to read WSDL from manifest. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0057 Unknown WSDL format for PGService:{0}, neither WSDL 1.1 nor WSDL 2.0
Explanation

The current WSDL element has unknown or no namespace associated.

Action

This is a virtual service configuration problem.


0050.0060 Populating SOAP service using WSDL
Action

Info level message, no action required.


0050.0061 Unable to find a WSDL for the PGService:{0}. Assuming a POX or Legacy service
Action

Info level message, no action required.


0050.0062 PGService: {0} is available on transports {1}
Action

Info level message, no action required.


0050.0063 Adding PGService:{0} to the SOAP Stack
Action

Info level message, no action required.


0050.0064 Removing PGService:{0} due to error: axisFault.getMessage()
Action

Info level message, no action required.


0050.0065 Exception while setting policy on PGService:{0}
Explanation

An exception was encountered while attempting to engage WS-Policy module. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0066 Setting Policy with id:{0} on Mediator Service:{1}
Action

Info level message, no action required.


0050.0068 Successfully created service in SOAP Stack for PGService:{0} containing {1} endpoint(s).
Action

Info level message, no action required.


0050.0069 Error{1} on setting parameter :{0} on Mediator Service
Explanation

An exception was encountered while attempting to set a parameter into an Axis service. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0070 creating new Mediator Service: {0}
Action

Info level message, no action required.


0050.0071 Unable to find service directory for service {0}
Explanation

Unable to persist WSDL assets because the virtual service directory does not exist.

Action

Redeploying the virtual service should create the service directory.


0050.0074 Error: {0} while reading from file {1}
Explanation

An exception was encountered while attempting to read the proxy file identified in the message. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0076 Scheduled task[{0}] with startup delay of {1} ms and interval of {2} ms
Action

Info level message, no action required.


0050.0077 Error initializing JMS transport listener. Cause: {0}
Explanation

An exception was encountered while attempting to register JMS listener. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0078 Unable to stop TransportListener called:{0}. Exception:{1}
Explanation

An AxisFault was encountered while attempting to stop the JMS transport listener during bean initialization. The associated fault message should include more details regarding the problem.

Action

Fix the problem identified by the fault message.


0050.0083 Error {0} occurred while updating the load balancer properties
Explanation

An AxisFault was encountered while attempting to add load balancer URL to an Axis transport description. The associated fault message should include more details regarding the problem.

Action

Fix the problem identified by the fault message.


0050.0084 Loadbalanced Endpoint: [{0}] failed!
Explanation

A mediation operation to a load balanced endpoint has failed. The endpoint indicated in the message is not available. This usually indicates a communication problem with the targeted server.

Action

Fix the targeted server.


0050.0086 Unable to get the IS keystore manager - please check your configuration!
Explanation

Unable to retrieve the keystore manager bean.

Action

This is a Spring bean configuration issue, the pg-config.xml file is missing or corrupted.


0050.0087 Keystore initialization failed! Please check the server log for more details
Explanation

Unable to load the keystore file.

Action

This is a Mediator security configuration problem.


0050.0088 Truststore initialization failed! Please check the server log for more details
Explanation

Unable to load the truststore file.

Action

This is a Mediator security configuration problem.


0050.0089 Unable to get the Rampart Configuration Handler - please check your configuration!
Explanation

Unable to retrieve the Rampart creation handler bean.

Action

This is a Spring bean configuration issue, the pg-config.xml file is missing or corrupted.


0050.0099 VSD proxy loader, Unable to delete file: {0}
Explanation

The file or directory indicated in the message could not be deleted.

Action

Determine why the file or directory could not be deleted and make it deletable.


0050.0100 VSD proxy loader, Unable to delete directory: {0}
Explanation

The directory indicated in the message could not be deleted.

Action

Determine why the directory could not be deleted and make it deletable.


0050.0101 VSD proxy loader, Unable to create directory: {0}
Explanation

The file or directory indicated in the message could not be created.

Action

Delete the directory so that Mediator can create it again.


0050.0105 Unable to determine fault cause. Please check the log file for more information!
Explanation

This error indicates that Mediator could not determine the cause for the error when trying to extract the soap fault message from the response. Additional errors if any would be present in the IS log file (server.log)


0050.0208 Error resolving WSDL URI. Cause {0}
Explanation

An exception was encountered while attempting to resolve URI elements into XML source. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0209 Error initializing virtual service factory. Cause: {0}
Explanation

An exception was encountered while attempting to initialize XPath elements. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0210 Error setting location of virtual service proxies directory. Path: {0} Cause: {1}
Explanation

An exception was encountered while attempting to use the directory identified in the message. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0211 Unable to determine service endpoint URI for this service: {0} No transport listener defined for the virtual service's transport protocol.
Explanation

The configuration context's listener manager cannot find an endpoint for the current service. This may indicate that the hosting IS does not have an appropriate listener registered.

Action

This is a configuration problem, either in IS ports or VSD


0050.0212 Unknown exception deploying virtual service: {0} Cause: {1}
Explanation

An exception was encountered while attempting to get an endpoint reference from the context listener manager. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0214 Error {0} manifest from external resources associated with virtual service: {1}. Cause: {2}
Explanation

An exception was encountered while attempting to read WSDL from manifest. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0215 Error initializing virtual service transformation bean with this xslt: {0} Cause: {1}
Explanation

An exception was encountered while attempting to read the transformation file. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0216 Error transforming raw virutal service string. Cause: {0} virtual service xml: {1}
Explanation

An exception was encountered while attempting to read the Mediator's transformation file. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0221 Mediator has an internal configuration error. It's deploy-time xslt transformation file path does not exist. Path: {0}
Explanation

An exception was encountered while attempting to read the file identified in the message. The associated exception message should include more details regarding the problem.

Action

This is a configuration problem; make sure the file identified in the message exists and contains the transformation.


0050.0250 Could not find user-specified value for HTTP method! Defaulting to inbound request HTTP method {0}
Explanation

The 'routing method' context variable has an invalid value.

Action

If the value indicated in the message is acceptable, no action is required. Otherwise virtual service configuration must be changed.


0050.0252 Could not set HTTP method for outgoing request for endpoint: {0}
Explanation

The outgoing request's message context is null.

Action

This is a virtual service/policy configuration problem.


0050.0300 Context variable name ''{0}'' is already declared. Multiple declarations in the same context is not allowed.
Explanation

Context variable names must be unique for a service.

Action

This is a service configuration problem.


0050.0303 Attempt to reference context variable without providing a message context. Custom context variables may only be declared with a 'session' scope at this time. Other scopes are not supported.
Explanation

Attempting to get context variable or context variable map, but the message context (or session) is null.

Action

Earlier error messages should provide clues to help determine why a valid message context is null.


0050.0306 Context variable name is required for variable declaration.
Explanation

Variable name validation failed, QName is null or is missing a local part.

Action

This is a context variable configuration problem.


0050.0307 Namespace URI and prefix is required for custom variable declaration. varName: {0}
Explanation

Variable name validation failed, Namespace URI and prefix must both be neither null nor empty.

Action

This is a context variable configuration problem.


0050.0308 Context variable name must be a valid identifer ( alpha-numeric, $, or _ permitted ) Found: {0}
Explanation

Variable name validation failed, name has invalid characters.

Action

This is a context variable configuration problem.


0050.0309 Core Context variables cannot have a namespace or prefix as part of its declaration. varName: {0}
Explanation

Variable name validation failed, prefix for core variables must be empty.

Action

This is a context variable configuration problem.


0050.0310 Either a Message context or axis service name is required when creating a custom context variable. varName: {0}
Explanation

Both service name and Axis2 message context are null, this is not acceptable. This is probably the result of attempting to deploy a service with no service name.

Action

Verify that service configuration is correct.


0050.0311 Attempt to create a custom variable using a message context with no AxisService. varName: {0}
Explanation

The axis2 message context is corrupted, it should identify a service.

Action

Earlier error messages should provide clues to help determine why a valid message context could not be created.


0050.0312 Unexpected error creating custom Mediator context variable. varName: {0} reason: {1}
Explanation

An exception was encountered while attempting to create a custom context variable. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0313 Unexpected error removing custom Mediator context variable for service: {0} reason: {1}
Explanation

An exception was encountered while attempting to remove or inject a custom context variable. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0314 Unexpected error initializing core Mediator context variables. reason: {0}
Explanation

An exception was encountered while attempting to create a context variable. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0316 Unexpected error getting Mediator context variable value. varName: {0} reason: {1}
Explanation

An exception was encountered while attempting to get the valuue of the context variable named in the message. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0317 Unexpected error setting Mediator context variable value. varName: {0}, value:{1}, reason: {2}
Explanation

An exception was encountered while attempting to set the context variable value named in the message. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0318 Expected a virtual service name for this method operation, but none was provided.
Explanation

Attempting to get context variable map for a null service name.

Action

Earlier error messages should provide clues to help determine why a valid service name is null.


0050.0321 Mediator context variable adapter unable to locate this type: {0}
Explanation

The context variable type indicated in the message is unknown.

Action

This is a context variable configuration problem.


0050.0322 Unexpected error getting core Mediator context variable value from adapter. type: {0}
Explanation

An exception was encountered while attempting to get the context variable value named in the message. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0323 Only string and int schema types are supported at this time. Type: {0}, declared with ''{1}'' context variable is not supported.
Explanation

The context variable schema type is not among the accepted types.

Action

This is a service configuration problem.


0050.0324 Context variable name declarations cannot contain $ sign symbols in the name since that is used as a reference operator. varName: {0}
Explanation

Variable name validation failed, name must include substitution character, (dollar sign).

Action

This is a context variable configuration problem.


0050.0325 Unable to return list of context variables declared for this service: {0} Reason: {1}
Explanation

An AxisFault was encountered while attempting to retrieve a list of context variable names. The associated fault message should include more details regarding the problem.

Action

Fix the problem identified by the fault message.


0050.0326 Unable to return list of context variables declared for this message context: {0} Reason: {1}
Explanation

An AxisFault was encountered while attempting to get a list of context variables or list of variable keys. The associated fault message should include more details regarding the problem.

Action

Fix the problem identified by the fault message.


0050.0327 Context variable name deployed with virtual service {0} references an unknown namespace prefix. name attribute: {1}
Explanation

Context variable identified in message has invalid namespace.

Action

This is a context variable configuration problem.


0050.0328 Exception while copying context variables from request to response message context. Reason: {0}
Explanation

An AxisFault was encountered while attempting to copy context variable names between contexts. The associated fault message should include more details regarding the problem.

Action

Fix the problem identified by the fault message.


0050.0329 Could not create backup directory for failed services! Dir tried = {0}
Explanation

An attempt to create the 'failed services' directory has failed.

Action

Determine why the directory could not be created. Either fix the creation problem or specify a different directory.


0050.0331 Error occurred when getting backup directory for path {0}
Explanation

An exception was encountered while attempting to determine directory for backing up failed services. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0333 Error occurred while resolving URI; message = {0}
Explanation

An exception was encountered during URI resolution. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0337 Previously selected {0} port {1} is no longer enabled or available!
Explanation

The message indicates port number and type. The requested port is not available.

Action

Select a new port number for the indicated port type.


0050.0343 Context variable API expected an IData object for ctx variable, {0}, but received this: {1}
Explanation

The data element from which a context variable is to be extracted has an unknown data type.

Action

This is probably a flow configuration problem; where the pipeline was populated with an invalid value.


0050.0344 Attempt to insert {0} core ctx variable with invalid value type: {1}. Expected a collection of this type: {2}
Explanation

.The allowable data type for a core context variable is restricted, depending on variable type.

Action

.This is a context variable configuration problem.


0050.0345 Unable to access array element [{0}] in SOAP_HEADERS core ctx variable. Cause: {1}
Explanation

The index value indicated in the message must be numeric.

Action

This is a context variable configuration problem.


0050.0346 Invalid array or key reference for core ctx variable. This substitution string has mismatched braces: {0}
Explanation

The context variable substitution string is invalid, mismatched brace characters were found.

Action

This is a context variable configuration problem.


0050.0347 Attempt to create an IData value for a ctx variable from an unsupported class type. CtxVar: {0} Bad type: {1}
Explanation

The context variable to be converted to IData has an unknown data type.

Action

This is a context variable configuration problem.


0050.0348 Unable to append header block to the end of the soap header. Cause: {0}, soapHeader element: {1}
Explanation

An exception was encountered while attempting to add append new SOAP header block. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0349 Unable to prepend header block to the beginning of the soap header. Cause: {0}, soapHeader element: {1}
Explanation

An exception was encountered while attempting to add prepend new SOAP header block. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0350 Unable to remove header block from the soap header. Cause: {0}, soapHeader: {1}
Explanation

An exception was encountered while attempting to remove a SOAP header block. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0351 Unable to set header block at position {0} of the soap header. Cause: {1}, soapHeader element: {2}
Explanation

An exception was encountered while attempting to replace a SOAP header block with a new one. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0355 Could not create STS configuration directory! Dir tried = {0}
Explanation

The file or directory indicated in the message could not be created.

Action

Delete the directory so that Mediator can create it next time it is required.


0050.0357 Error occurred when getting STS configurations directory for path {0}
Explanation

An exception was encountered while attempting to create the directory indicated in the message. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0362 Error occurred when creating STS client
Explanation

An exception was encountered while attempting to create an STS client object. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0364 Error occurred when initializing default STS configuration store
Explanation

An exception was encountered while attempting to create JAXB marshaller/unmarshaller pair. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0365 Could not find STS configuration file with path {0}
Explanation

An attempt to delete the file indicated in the message failed because the file does not exist.

Action

Check this directory [IS_INSTALL_DIR\packages\WmMediator\config\resources\security\sts] to make sure there is an xml file with the STS config name being deleted. For e.g. if the STS config being deleted is MySTS, then there should be an XML file called MySTS.xml in the mentioned directory


0050.0366 Could not delete STS configuration file with path {0}
Explanation

An attempt to delete the file indicated in the message returned 'false'. The file was not deleted.

Action

Make sure the STS config file present under [IS_INSTALL_DIR\packages\WmMediator\config\resources\security\sts] is present and not locked by any other application (e.g. opened in an editor like Windows Notepad). Check the log file to see if there is any java IOException related to disk errors.


0050.0367 Error occurred when saving STS configuration to disk
Explanation

An exception was encountered while attempting to marshal configuration object into file. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0368 Error occurred when reading STS configuration from file {0}
Explanation

An exception was encountered while attempting to unmarshal configuration file indicated in the message into JAXB object. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0371 Error getting IS keystore manager instance!
Explanation

An exception was encountered while attempting to get a reference to the keystore manager. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0373 Error occurred when adding rampart configuration to STS policy
Explanation

An exception was encountered while attempting to configure the STS policy. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0379 Error occurred when adding assertion to STS policy
Explanation

An exception was encountered while attempting to add an assertion to a WS-Policy artifact. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0382 Error occurred when adding OnBehalfOf element to WS-Trust request element
Explanation

An exception was encountered while attempting to add the WS-Trust element to a request. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0383 Error occurred when sending WS-Trust request to STS to obtain SAML assertion
Explanation

An exception was encountered while attempting to add SAML assertion to pipeline. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0384 Could not find required property {0} for SAML sender-vouches action!
Explanation

The pub.mediator.security.ws.AddSamlSenderVouchesToken ESB service is missing the required 'ConfigName' input value

Action

Make sure that the 'ConfigName' service input has a valid STS config name (must match one of the configured STS names)


0050.0386 Could not find any STS client configuration with name {0}. Check to see if such an STS configuration exists!
Explanation

This error occurs if the configured ESB service that calls the pub.mediator.security.ws.AddSamlSenderVouchesToken specifies the STS config name incorrectly.

Action

Check if the specified STS config name matches one of the configured STSs in Mediator. The "ConfigName" service input value should be the same name (case-sensitive) as the STS name specified in Mediator Admin configuration page


0050.0388 Could not get SAML assertion from STS!
Explanation

A null assertion element was found in the STS client.

Action

Mediator sent a request to the configured STS to obtain a SAML assertion, but no valid assertion was obtained by the client. Please check the log file for any errors related to sending the WS-Trust request to the STS to obtain the token.


0050.0389 Adding OnBehalfOf element in WS-Trust request for IS user {0}
Action

Info level message, no action required.


0050.0390 Could not find base STS policy file: {0} !
Explanation

An exception was encountered while attempting to load a WS-Policy artifact from the file indicated in the message. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0391 Error occurred when getting STS configurations! Check to see if the ISTSClientConfigManager bean is configured!
Explanation

The STS configuration manager bean could not be found.

Action

This is a Spring bean configuration issue, the pg-config.xml file is missing or corrupted.


0050.0392 Could not find any STS configuration with the name {0}
Explanation

The STS client configuration identified in the message to be loaded or deleted could not be found.

Action

Verify that the STS configuration being loaded or deleted has an equivalent configuration file present under [IS_INSTALL_DIR\packages\WmMediator\config\resources\security\sts] directory. E.g. if the configuration being deleted is called MySTS, then there should be a file with name MySTS.xml in the mentioned directory


0050.0394 Error occurred when getting key aliases for keystore {0}: Error: {1}
Explanation

An exception was encountered while attempting to add a list of certificate aliases to the pipeline. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0395 Error occurred when getting keystore handles {0}
Explanation

An exception was encountered while attempting to add a list of keystore handles to the pipeline. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0396 Error when signing SAML assertion and SOAP request body
Explanation

An exception was encountered while attempting to sign a SAML assertion and request body. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0397 Error occurred when adding ws-addressing headers to outbound soap request; Error: {0}
Explanation

An exception was encountered while attempting to add WS-Addressing headers. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0400 Using default timestamp value of 300s, because input TTL {0} is invalid (-ve or too big)
Explanation

The input value was not valid, a default was used.

Action

If the default is acceptable, no action is required. Otherwise update the configuration.


0050.0507 ScaDeploymentPayload.extractParts found no virtual service requests
Action

Info level message, no action required.


0050.0508 Unexpected exception, attempting to {0}, caught: type({1}), msg({2})
Explanation

An exception was encountered while attempting to process a deployment request. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0509 ScaDeploymentPayload.extractParts - Unable to find consumer file {0}, for component {1})
Explanation

The SCA deployment package was expected to contain a file to define the consumer identified in the message. The file was not found.

Action

This is a deployment payload construction problem.


0050.0510 Unexpected exception, attempting to process {0} request, caught: type({1}), msg({2})
Explanation

An exception was encountered while attempting to process a deployment request. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0515 ScaCompositeConfiguration found component with implementation type ({0})
Action

Info level message, no action required.


0050.0516 {0} - unable to convert string ({1}) to XMLGregorianDate: exception message ({2})
Explanation

The date element from the deployment payload has an unexpected format.

Action

This is problem with the contents of the deployment payload.


0050.0517 DeploymentPayload.{0} - input pipeline does not contain expected key ({1})
Explanation

The deployment payload must include an element with the key indicated in the message.

Action

This is problem with the contents of the deployment payload.


0050.0519 ScaDeploymentPayload - unable to delete temporary zip file: ({0})
Explanation

The file indicated in the message could not be deleted.

Action

Determine why the file could not be deleted and make it deletable.


0050.0520 DeploymentPayload - invalid request type: {0}
Explanation

The deployment payload type is unknown.

Action

This is a deployment payload construction problem.


0050.0528 DeploymentPayload - found null/empty virtual service descriptor for service {0}
Explanation

The deployment payload must contain a VSD. The VSD for the service identified in the message was not found.

Action

This is a deployment payload construction problem.


0050.0603 Error occurred when adding UsernameToken to SOAP Envelope: {0}
Explanation

An exception was encountered while attempting to add username token to the pipeline. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0605 Error occurred when adding X.509 token to SOAP Envelope: {0}
Explanation

An exception was encountered while attempting to add X509 token to the pipeline. The associated exception message should include more details regarding the problem.

Action

Fix the problem identified by the exception message.


0050.0630 DeploymentPayload - No update requests for the runtime aliases being deployed
Class Debug
Explanation

Mediator did not receive any update requests for the runtime aliases being deployed.

Action

Check the update request for runtime aliases.


0050.0632 Mediator does not support the runtime alias. Alias type: {0}
Class Error
Explanation

Mediator was not able to find a runtime alias of the specified type.

Action

Check the alias type assigned to the runtime alias.


0050.0670 Resources for the endpoint URI not found. Endpoint URI: {0}
Class Error
Explanation

Mediator does not have REST resources configured with the specified URI.

Action

Check the configuration of the virtual REST service to ensure that the required resources are configured.


0050.0677 Error while processing the REST to SOAP transformation in Mediator. The JSON string in the request is empty.
Explanation

Mediator expects a non-empty JSON string in the request message.

Action

Check if the JSON request string is valid, and try again. Contact your system administrator for details if the issue persists.


0050.0678 Mediator could not complete the transformation of a REST request received from the consumer to a SOAP request because of an error. JSON string:{0}. {1}
Explanation

Mediator encountered an error while converting the JSON request to a SOAP request as part of the conversion of the REST request to a SOAP request.

Action

Check if the JSON request string is valid and try again. Contact your system administrator for details if the issue persists.


0050.0679 Mediator could not complete the transformation of a REST request received from the consumer to a SOAP request because of an error. {0}
Explanation

Mediator encountered an error while converting the multi-part REST request to SOAP request as part of the conversion of the REST request to SOAP request.

Action

Check if the attachments in the multi-part request are valid.


0050.0680 Mediator could not complete the transformation of a REST request received from the consumer to a SOAP request because of an error. JSON string: {0}. {1}
Explanation

Mediator encountered an error while converting the JSON string sent as an attachment to a SOAP request as part of the conversion of the REST request to a SOAP request.

Action

Check if the JSON string in the attachment to the SOAP request is valid.


0050.0681 Mediator could not complete the transformation of a REST request received from the consumer to a SOAP request because of an error. {0}
Explanation

Mediator encountered an error while parsing the schema in WSDL file, which leads to namespaces not being placed properly in the SOAP request when the REST to SOAP transformations are processed.

Action

Check the schema of the WSDL file provided in the native SOAP service.


0070.0081 [{0}] Removing the Content-Encoding header in response as the Accept-encoding is null

0070.0094 [{0}] --> Incoming Request Header does not contain a valid OAuth token.
Explanation

User has configured OAuth authenticaton scheme but OAuth token is not present in the request.

Action

Ensure that the request has an authorization header with OAuth token in it.


0070.0172 Found duplicate target namespace [{0}], enabling namespace-growth for schema validation
Explanation

This flag will be auto enabled when duplicate target namespaces found in the schema definition otherwise it will be false by default.

Action

User can enable/disable this flag by setting true/false to pg.schema.validation.namespacegrowth property.


010.0787 Could not load information on runtime aliases to Mediator. File not found {0}
Class Error
Explanation

Mediator could not find the file containing information on the runtime aliases.

Action

Check if the file is present in the specified location.


010.0788 Error loading aliases from file store :{0}, {1}
Class Error
Explanation

Mediator encountered an error while loading the aliases from the file store.

Action

Check if the file store exists in Mediator and is valid.


010.0790 Error saving runtime aliases to the file store: {0}. {1}
Explanation

Mediator encountered an error while saving the aliases from the file store.

Action

Check if the file store exists in Mediator and is a valid file store.


010.0792 Runtime alias not added to the file store: {0}
Class Error
Explanation

Mediator is not able to add the runtime alias to the file store.

Action

Check the Integration Server log for more details


0201.0049 No Certificate was sent over HTTPS transport

0203.0323 Error parsing alias service names file. {0}
Class Error
Explanation

Mediator cannot parse the alias service names file.

Action

Check the Integration Server log for details. Redeploy the aliases and the associated services after you have fixed the issues in the alias service names file.


0203.0324 Error loading the service names associated with the alias to memory. {0}
Class Error
Explanation

Mediator cannot parse the alias service names file.

Action

Check the Integration Server log for details.


0203.0325 Error saving the service names associated with the alias to the file store. {0}
Class Error
Explanation

User may not have permission to write to the file, or the file may not be in the disk.

Action

Check the Integration Server log for details.


0203.0326 RuntimeAliasesCache - Null references to aliases found. Could not load the runtime alias cache.
Class Debug error
Explanation

Mediator found null references to aliases.

Action

Check the cluster configuration in Integration Server and also ensure that there are no null elements in the cache.


0010.0062 Unable to get password for callback identifier: {0}
Class E
Explanation

Error while retrieving cleartext password from encrypted passman file store.

Action

Review Mediator STS configuration; otherwise, this is an internal error. Contact webMethods Customer Care. Please produce a diagnostic zip file by running the mediator.util:mediatorDiagnosticZip service from the WmMediator package's list of services in IS Admin's package management menu if available.


0010.0083 Non-fatal Mediator package initialization error. {0}, {1}
Class W
Explanation

Mediator encountered an error during an upgrade processing step after the package initialization completed.

Action

Verify the overinstall upgrade steps were followed as defined in the documentation; otherwise, this is an internal error. Contact webMethods Customer Care. Please produce a diagnostic zip file by running the mediator.util:mediatorDiagnosticZip service from the WmMediator package's list of services in IS Admin's package management menu if available.


0010.0212 Endpoint connection timeout duration expected as a number but was not a number ({0})
Class E
Explanation

A virtual service was deployed with an invalid connection timeout specified for its native provider endpoint.

Action

Review the advanced endpoint configuration in CentraSite and redeploy the service if necessary.


0010.0214 Both keystore and key alias must be specified or none at all for SSL configuration; KeyStore alias = [{0}]; Key alias = [{0}]
Class E
Explanation

A virtual service with a native provider SSL endpoint was deployed with an invalid advanced endpoint configuration. The endpoint must have a valid alias for both the keystore file and the keystore entry aliases as defined in the Integration Server or it can have no aliases defined at all.

Action

Update the advanced endpoint configuration and redeploy the virtual service to Mediator.


0010.0217 Error occurred when getting the password for handle {0} from passman!
Class E
Explanation

An attempt to retrieve a cleartext password from a passman encrypted file store failed.

Action

This is an internal error. Contact webMethods Customer Care. Please produce a diagnostic zip file by running the mediator.util:mediatorDiagnosticZip service from the WmMediator package's list of services in IS Admin's package management menu if available.


0010.0218 Error occurred when storing the password for handle {0} in passman!
Class E
Explanation

An attempt to save a password in a passman encrypted file store failed during Mediator STS configuration.

Action

This is an internal error. Contact webMethods Customer Care. Please produce a diagnostic zip file by running the mediator.util:mediatorDiagnosticZip service from the WmMediator package's list of services in IS Admin's package management menu if available.


0010.0220 Error converting given WS-Policy component to string
Class E
Explanation

Mediator was unable to parse policy elements used in producing request security tokens (RST) to a configured security token service (STS).

Action

This is an internal error. Contact webMethods Customer Care. Please produce a diagnostic zip file by running the mediator.util:mediatorDiagnosticZip service from the WmMediator package's list of services in IS Admin's package management menu if available.


0010.0228 Endpoint read timeout duration expected as a number but was not a number ({0})
Class E
Explanation

A virtual service was deployed with an invalid read timeout specified for its native provider endpoint.

Action

Review the advanced read configuration in CentraSite and redeploy the service if necessary.


0010.0702 Mediator Upgrade, Mediator migration interrupted due to error. Details: {0}
Class E
Explanation

This log message may occur when the Mediator package loads during the Integration Server restart after an overinstall. It indicates the upgrade was not successful and further actions are required.

Action

Depending on the error message, one of the three options are available. 1) Resolve the issue causing the upgrade to fail, and restart the Integration Server again to see if the upgrade completes successfully. 2) Delete the mediatorUpgrade.xml file from installation path: ${IS_HOME}/packages/WmMediator/ directory. This is the file that causes Mediator to perform its upgrade step. If this action is taken, the Mediator configuration will have to be re-entered manually through the IS admin UI. 3) Contact support. Everytime the Integration Server is restarted, Mediator will attempt to perform an upgrade as long as its mediatorUpgrade.xml file is present in the package directory.


0010.0705 Mediator Upgrade, mediatorUpgrade.xml file is corrupted. Expected 'properties' root element but none found.
Class E
Explanation

This message indicates the mediatorUpgrade.xml file included after the installer completes a Mediator overinstall is corrupted. This file is normally installed into the ${IS_HOME}/packages/WmMediator/ directory path when the overinstall completes. Its presence causes Mediator to run its upgrade tasks during the next Integration Server restart. Once the upgrade task has completed, this file is removed ensuring the upgrade is run only once.

Action

Contact customer support or remove the mediatorUpgrade.xml file. The mediator package should load without error during the next Integration Server restart if this file is removed, but Mediator configuration must be set up manually through the IS admin UI.


0010.0706 Mediator Upgrade, unable to read required file. {0}
Class E
Explanation

This log message may occur when the Mediator package loads during the Integration Server restart after an overinstall. This message implies that the OS user running the Integration Server does not have adequate permissions to read the file referenced in the error message.

Action

Review user and file permissions and make necessary adjustments to ensure the file can be read.


0010.0707 Mediator Upgrade, configuration file is missing a required entry element key attribute. {0}, File path: {1}
Class E
Explanation

This log message may occur when the Mediator package loads during the Integration Server restart after an overinstall. The mediatorUpgrade.xml file used to control a Mediator overinstall upgrade is corrupted. It is missing a reference to an attribute containing a path to an archive of the previous Mediator version prior to the overinstall.

Action

Contact support.


0010.0708 Mediator Upgrade, configuration file entry element key attribute: {0}, expected this value: {1}, but found: {2}, File path: {3}
Class E
Explanation

This log message may occur when the Mediator package loads during the Integration Server restart after an overinstall. The mediatorUpgrade.xml file used to control a Mediator overinstall upgrade is corrupted.

Action

Contact support.


0010.0709 Mediator Upgrade, unable to find the required file. Expected location: {0}
Class E
Explanation

This log message may occur when the Mediator package loads during the Integration Server restart after an overinstall. The backup file archive containing the Mediator package prior to the overinstall upgrade cannot be found.

Action

Contact support.


0010.0711 Mediator Upgrade, unable to delete configuration file. Mediator upgrade task will continue to execute after each Integration Server startup until this file is removed. Path: {0}
Class E
Explanation

This log message may occur when the Mediator package loads during the Integration Server restart after an overinstall. Verify that the OS user account running the Integration Server has the necessary permissions to delete the file.

Action

If the log messages suggest the upgrade ran successfully, this file can be deleted; otherwise, contact support.


0010.0712 Mediator Upgrade, configuration file is not valid xml. Unable to parse it. {0}, Details: {1}
Class E
Explanation

This log message may occur when the Mediator package loads during the Integration Server restart after an overinstall. The mediatorUpgrade.xml file is corrupted.

Action

Contact support.


0010.0717 Mediator Upgrade, Could not find Default STS configuration file: {0} in archived zip file
Class W
Explanation

The default STS configuration file was not found when performing an overinstall upgrade.

Action

No action is necessary if migrating from Mediator 8.0; otherwise, this is an internal error. Contact webMethods Customer Care. Please produce a diagnostic zip file by running the mediator.util:mediatorDiagnosticZip service from the WmMediator package's list of services in IS Admin's package management menu if available.


0010.0718 Mediator Upgrade, configuration file has unexpected element key attribute, {0}, with value. {1}, and configuration file path: {2}
Class E
Explanation

This log message may occur when the Mediator package loads during the Integration Server restart after an overinstall. The mediatorUpgrade.xml file is corrupted.

Action

Contact support.


0010.0719 Mediator Upgrade, Could not find Default STS configuration file: {0} following upgrade; Skipping migrating configuration data!
Class E
Explanation

Mediator was unable to locate the default STS configuration file during an overinstall upgrade.

Action

This is an internal error. Contact webMethods Customer Care. Please produce a diagnostic zip file by running the mediator.util:mediatorDiagnosticZip service from the WmMediator package's list of services in IS Admin's package management menu if available.


0010.0720 Mediator Upgrade, Could not load Default STS client configuration; Skipping migrating configuration data
Class W
Explanation

The default STS configuration file was not found when performing an overinstall upgrade.

Action

No action is necessary if migrating from Mediator 8.0; otherwise, this is an internal error. Contact webMethods Customer Care. Please produce a diagnostic zip file by running the mediator.util:mediatorDiagnosticZip service from the WmMediator package's list of services in IS Admin's package management menu if available.


0050.0408 Authentication failed for user {0}
Class E
Explanation

Invalid basic authentication credentials were included in the Authorization header sent to a virtual service that has a "Require HTTP Basic Authentication" runtime security policy.

Action

The web service consumer should include proper credentials and resend the service request.


0050.0608 Error occurred when adding Timestamp to SOAP Envelope: {0}
Class E
Explanation

Mediator was unable to insert a WS security timestamp element to the request's security header sent to the native provider.

Action

Review the configured ESB "AddTimestamp" service call for virtual service and redeploy if incorrect. Otherwise, this is an internal error. Contact webMethods Customer Care. Please produce a diagnostic zip file by running the mediator.util:mediatorDiagnosticZip service from the WmMediator package's list of services in IS Admin's package management menu if available.


0070.0010 Incoming request does not contain the 'Authorization' header. This service requires the HTTP Basic Authentication token to be present.
Class E
Explanation

Authorization header was not sent to a virtual service that has a "Require HTTP Basic Authentication" runtime security policy.

Action

The web service consumer must include valid credentials and resend the service request.


0070.0032 Unable to create Schema for this service ''{0}'' Schema validation may not succeed!
Class E
Explanation

Mediator was unable to initialize the schema parser for a virtual service with a "Validate Schema" runtime policy. This error occurs when a consumer sends Mediator a service request.

Action

Review the schemas defined in the virtual service, make corrections, and redeploy the virtual service if necessary; otherwise, this is an internal error. Contact webMethods Customer Care. Please produce a diagnostic zip file by running the mediator.util:mediatorDiagnosticZip service from the WmMediator package's list of services in IS Admin's package management menu if available.


0070.0071 The ESB service name specified for InvokeESB mediator cannot be empty!
Class W
Explanation

A virtual service was deployed containing an ESB service invocation step containing an invalid or missing service name.

Action

Review all service invocations from the "Processing steps" configuration for the virtual service and redeploy if necessary.


0070.0072 The 'service' attribute is required for the InvokeESB mediator definition
Class E
Explanation

The deployed virtual service configuration is corrupted.

Action

This is an internal error. Contact webMethods Customer Care. Please produce a diagnostic zip file by running the mediator.util:mediatorDiagnosticZip service from the WmMediator package's list of services in IS Admin's package management menu if available.


0200.0045 Error saving EhCache configuration file: {0}
Class E
Explanation

Mediator was unable to save its configuration file used for the Terracotta cache component.

Action

This is an internal error. Contact webMethods Customer Care. Please produce a diagnostic zip file by running the mediator.util:mediatorDiagnosticZip service from the WmMediator package's list of services in IS Admin's package management menu if available.


0200.0046 Could not find specified EhCache configuration file: {0}
Class E
Explanation

The Terracotta cache configuration file for Mediator's caches could not be found during package startup.

Action

This is an internal error. Contact webMethods Customer Care. Please produce a diagnostic zip file by running the mediator.util:mediatorDiagnosticZip service from the WmMediator package's list of services in IS Admin's package management menu if available.


0203.0062 ControllingNodeLocker.run, thread id({0}), expected Ehcache, found ({1})
Class E
Explanation

Unexpected content was returned in the Terracotta cluster status cache.

Action

This is an internal error. Contact webMethods Customer Care. Please produce a diagnostic zip file by running the mediator.util:mediatorDiagnosticZip service from the WmMediator package's list of services in IS Admin's package management menu if available.


0203.0065 ControllingNodeLocker.run, thread id({0}), caught ({1}/{2}) attempting to get a lock, thread dies
Class E
Explanation

Mediator encountered an error trying to obtain a lock on the controlling node in a Terracotta cluster.

Action

This is an internal error. Contact webMethods Customer Care. Please produce a diagnostic zip file by running the mediator.util:mediatorDiagnosticZip service from the WmMediator package's list of services in IS Admin's package management menu if available.


0203.0070 ClusterStatusCache - cache manager for {0} returned null CacheCluster reference, not clustered?
Class I
Explanation

Mediator was unable to obtain a reference to the configured Terracotta cluster.

Action

This is an internal error. Contact webMethods Customer Care. Please produce a diagnostic zip file by running the mediator.util:mediatorDiagnosticZip service from the WmMediator package's list of services in IS Admin's package management menu if available.


0203.0071 {0} - getCluster(ClusterScheme.TERRACOTTA) threw exception {1}, using schema NONE
Class I
Explanation

An attempt to get Terracotta cluster configuration details failed.

Action

If Mediator is configured for a Terracotta cluster, this is an internal error. Contact webMethods Customer Care. Please produce a diagnostic zip file by running the mediator.util:mediatorDiagnosticZip service from the WmMediator package's list of services in IS Admin's package management menu if available.


0203.0072 ClusterStatusCache - thread id({0}) attempts to release {1} lock, but does not hold it
Class E
Explanation

An attempt to release the lock on the node controller in a Terracotta cluster failed.

Action

This is an internal error. Contact webMethods Customer Care. Please produce a diagnostic zip file by running the mediator.util:mediatorDiagnosticZip service from the WmMediator package's list of services in IS Admin's package management menu if available.


0203.0073 Error initializating JAXB Context: {0}
Class E
Explanation

Initialization for the cached global or registered consumers deployed to Mediator has failed.

Action

This is an internal error. Contact webMethods Customer Care. Please produce a diagnostic zip file by running the mediator.util:mediatorDiagnosticZip service from the WmMediator package's list of services in IS Admin's package management menu if available.


0203.0075 ControllingNodeLocker.run, thread id({0}), caught {1} attempting to ask about lock status, thread dies
Class E
Explanation

The thread defining the controlling node in a Mediator cluster encountered an error.

Action

This is an internal error. Contact webMethods Customer Care. Please produce a diagnostic zip file by running the mediator.util:mediatorDiagnosticZip service from the WmMediator package's list of services in IS Admin's package management menu if available.


0203.0076 Unable to get cache named {0} from cache manager {1}
Class E
Explanation

Mediator encountered an error accessing one of the Terracotta caches.

Action

This is an internal error. Contact webMethods Customer Care. Please produce a diagnostic zip file by running the mediator.util:mediatorDiagnosticZip service from the WmMediator package's list of services in IS Admin's package management menu if available.


0203.0081 {0}, thread id({1}), caught {2}/{3} attempting to release lock, thread dies
Class E
Explanation

Mediator encountered an error releasing the lock on the controlling node in the Terracotta cluster.

Action

This is an internal error. Contact webMethods Customer Care. Please produce a diagnostic zip file by running the mediator.util:mediatorDiagnosticZip service from the WmMediator package's list of services in IS Admin's package management menu if available.


0203.0082 EhcacheClusterStatusCache, thread id({0}), caught {1}/{2} attempting to update controlling lock in cache
Class E
Explanation

Mediator encountered an error updating the controlling node in a Terracotta cluster.

Action

This is an internal error. Contact webMethods Customer Care. Please produce a diagnostic zip file by running the mediator.util:mediatorDiagnosticZip service from the WmMediator package's list of services in IS Admin's package management menu if available.


0203.0100 Thread interrupted when trying to obtain {0} lock for cache {1}
Class W
Explanation

While Mediator was attempting to obtain a lock on a cache entry key, its thread was interrupted.

Action

No action may be necessary if Mediator is functioning normally.


0203.0101 Unable to {0} lock the {1} cache for key {2} after waiting {3} mSecs
Class E
Explanation

Mediator failed to lock a cache key in the expected period of time.

Action

No action may be necessary if Mediator is functioning normally


0203.0103 {0} task in thread {1} threw this: {2}
Class E
Explanation

An error occurred in the controlling node of a Terracotta cluster during Mediator shutdown.

Action

Contact webMethods Customer Care. Please produce a diagnostic zip file by running the mediator.util:mediatorDiagnosticZip service from the WmMediator package's list of services in IS Admin's package management menu if available.


0205.0062 UddiPerformanceMetricsSender - unable to publish metrics over UDDI for service: {0}, message: {1}
Class E
Explanation

This log message is produced when Mediator is unable to publish performance metrics results to Mediator. When revieiwng the content, please be aware that some exception details may have originated from the CentraSite product hosting the UDDI server. Errors can range from improper Mediator configuration, OS resource issues, network connectivity, or issues with the CentraSite installation.

Action

Depending on the errors logged in the Mediator UI, one of the following actions may prove more relevant. Verify CentraSite configuration information regarding UDDI is correct for the Mediator UI. Verify the hostname or IP address is reachable from the computer running the Mediator instance. Verify the CentraSite instance and its repository is up and accessible.


0205.0063 Unable to initialize UddiClientAdapter due to a missing password for username: {0}.
Class E
Explanation

This log message is produced when Mediator is unable to publish performance metrics results to Mediator. A password was not found in the encrypted store for the user configured in the CentraSite panel of the Mediator UI.

Action

Verify the password is entered and the configuration was successfully saved for the CentraSite configuration screen in the Mediator UI.


0205.0064 Error connecting to CentraSite UDDI registry running on {0}://{1}:{2}. Error: {3}
Class E
Explanation

This log message may be produced under the following situations: During Mediator package startup. CentraSite configuration entered in Mediator UI is saved, but a connection to the UDDI server fails for these settings. Mediator attempts to publish performance metrics but fails during its regularly scheduled interval.

Action

Verify the CentraSite configuration values in the Mediator UI are correct and CentraSite is up and running.


0205.0067 Error disconnecting to CentraSite UDDI registry running on {0}://{1}:{2}. Error: {3}
Class E
Explanation

This log message may be produced during the following situations: During Mediator package shutdown. While Mediator is initializing communications with the CentraSite UDDI server after encountering an error during runtime or saving configuration values in the Mediator UI.

Action

Please see the Action for 0205.0064


0205.0602 Missing ''{0}'' Jdbc destination pool from spring configuration
Class E
Explanation

One of the Mediator configuration files is corrupted and a necessary configuration element is missing.

Action

Contact support.


0205.0603 Jdbc destination sender expected a JdbcEvent object but received: ''{0}''
Class E
Explanation

The JDBC destination sender event component received an unexpected event type.

Action

Contact Support.


0205.0604 Jdbc destination sender encountered a Sql Exception while generating ''{0}'' events. Error Code: {1} Cause: {2}
Class E
Explanation

The Mediator Jdbc destination sender component encountered a SQL exception while sending a runtime event.

Action

Verfiy the database is operational and restart the functional alias pool. Verify the MediatorEvents database component tables installed using the Common Database Component are still defined, and the Jdbc pool credentials defined in Integration Server are correct. If all else fails, please contact Support.


0205.0605 Jdbc destination sender took {0} msecs to get a connection out of data source.
Class D
Explanation

If the '0205 MEN - Events' Mediator logging component is set to 'DEBUG', then Mediator will issue a log message if the time it takes to get a Jdbc connection exceeds a pre-defined threshold as defined in Mediator's pg-jdbc.xml file. The current default is 50 milliseconds.

Action

No action is necessary.


0205.0606 Jdbc destination sender took {0} msecs to get a prepared statement out of connection with this SQL: {1}.
Class D
Explanation

If the '0205 MEN - Events' Mediator logging component is set to 'DEBUG', then Mediator will issue a log message if the time it takes to get a Jdbc prepared statement exceeds a pre-defined threshold as defined in Mediator's pg-jdbc.xml file. The current default is 50 milliseconds.

Action

No action is necessary.


0205.0609 Jdbc destination sender took {0} msecs to close the prepared statement and connection.
Class D
Explanation

If the '0205 MEN - Events' Mediator logging component is set to 'DEBUG', then Mediator will issue a log message if the time it takes to close a Jdbc connection exceeds a pre-defined threshold as defined in Mediator's pg-jdbc.xml file. The current default is 50 milliseconds.

Action

No action is necessary.


0205.0610 Jdbc event requires at least one sql clause to be valid.
Class E
Explanation

The Mediator Jdbc component is in an invalid state.

Action

Contact Support.


0205.0611 Jdbc destination sender took {0} msecs to insert a batch of {1} ''{2}'' events. AutoCommit enabled on driver? {3}, Transaction Isolation level? {4}
Class D
Explanation

If the '0205 MEN - Events' Mediator logging component is set to 'DEBUG', then Mediator will issue a log message if the time it takes to execute a batch of runtime event inserts into the database exceeds a pre-defined threshold as defined in Mediator's pg-jdbc.xml file. The current default is 500 milliseconds.

Action

No action is necessary unless the time is extremely large. In that case, consider reducing the 'pg.jdbc.batchSize' property in Mediator's pg-config.properties file. This will cause the Jdbc destination sender to send updates to the database server in smaller batches.


0205.0613 Jdbc event formatter expected {0} but it received: {1}
Class E
Explanation

The Mediator Jdbc component received an unexpected event type, so it was unable to produce the event.

Action

Contact Support.


0205.0614 Jdbc event sql range should be between 0 and {0}, {1} is out of range.
Class E
Explanation

Mediator Jdbc component is in an invalid state.

Action

Contact Support.


0205.0615 Jdbc performance metrics processor expected only one return key, but ''{0}'' were found.
Class E
Explanation

The Mediator Jdbc component is in an invalid state.

Action

Contact Support.


0205.0616 Jdbc performance metrics processor expected two SQL statements, but ''{0}'' were found.
Class E
Explanation

The Mediator Jdbc component is in an invalid state.

Action

Contact Support.


0205.0617 Jdbc performance metrics processor is missing returned primary key upon SQL insert
Class E
Explanation

Database did not return the 'event_pk' primary key column for the event inserted into the mediator_metrics_event table.

Action

Verify database is functioning properly; otherwise, contact Support.


0205.0618 Jdbc event is in a bad state. Data type count ''{0}'' does not equal column value count ''{1}''
Class E
Explanation

The Jdbc event destination component is in an invalid state.

Action

Contact Support.


0205.0619 Jdbc driver doesn't support returned named SQL columns from Insert statement. Trying ''Statement.RETURN_GENERATED_KEYS'' mode.
Class W
Explanation

The Jdbc event destination component will attempt to use named columns for returning the database-generated primary key after inserting a row. If the database driver does not support this feature, this log message is raised, and the component will use another method to return the inserted primary key.

Action

No action required unless other SQLException errors are raised.


0206.0035 MAC cache update {0} operation took {1} milliseconds to complete for {2} SIEs. This could cause lock attempts for tallying metrics statistics in MAC cache to fail.
Class W
Explanation

An update to the policy engine metrics data took longer than expected. When the duration of this task is longer than the configured lock request timeout, tasks can be lost when they fail to obtain exclusive locks.

Action

Review Integration Server performance and increase the advanced property for lock timeout pg.PgMenSharedCacheManager.lockTimeOut and restart IS. Otherwise, if this happens very frequently, contact webMethods Customer Care. Please produce a diagnostic zip file by running the mediator.util:mediatorDiagnosticZip service from the WmMediator package's list of services in IS Admin's package management menu if available.