The WliSbTransports catalog contains messages in the range
BEA381500 - BEA381599. Messages in this catalog are part of the
com.bea.wli.sb.transports Internationalization package and the
com.bea.wli.sb.transports Localization package.
|
BEA-381501
|
Warning: JmsAsyncMessageTable timed out message with id messageId
|
Description
| While invoking a JMS business service, a response to a JMS request did not arrive in before specified timeout expired. |
|
Action
| Check that back-end JMS business service is functioning properly and increase the timeout value if necessary |
|
|
BEA-381502
|
Error: Exception in method: e
|
Description
| An unexpected general purpose exception has occurred in OSB JMS transport. There should be an error message that points to cause of the problem |
|
Action
| Contact technical support |
|
|
BEA-381503
|
Warning: method received a message without a JMS Correlation Id; dropping message...
|
Description
| An OSB JMS request/response business service has picked up a message from configured JMS response destination that did not have expected JMSCorrelationID message property. As a result, the response message was dropped. |
|
Action
| Make sure that the back end JMS business service is properly functioning (e.g. that the JMSCorrelationID is being echoed when responding). Also, please make sure that the JMS destination configured for responses is not shared by other unrelated JMS services. |
|
|
BEA-381504
|
Warning: method received a message with an invalid JMS Correlation Id correlationId; dropping message...
|
Description
| An OSB JMS request/response business service has picked up a message from configured JMS response destination whose JMSCorrelationID message property had unexpected data. As a result, the response message was dropped. |
|
Action
| Make sure that the back end JMS business service is properly functioning (e.g. that the JMSCorrelationID is being echoed when responding). Also, please make sure that the JMS destination configured for responses is not shared by other unrelated JMS services. |
|
|
BEA-381505
|
Warning: method received a message with an unknown message Id messageId; dropping message...
|
Description
| An OSB JMS request/response business service has picked up a message from configured JMS response destination that did not correlate to a known JMS request that had been previously sent out. As a result, the response message was dropped. |
|
Action
| Make sure that the back end JMS business service is properly functioning (e.g. that the JMSCorrelationID is being echoed when responding). Also, please make sure that the JMS destination configured for responses is not shared by other unrelated JMS services. |
|
|
BEA-381506
|
Error: Unexpected type of message received: messageType
|
Description
| A non Text or Bytes or Object message was received by JMS proxy service or as a response to JMS business service. OSB JMS transport only supports Text, Bytes and Object messages. |
|
Action
| Make sure only JMS Text or Bytes messages are being sent to OSB JMS proxy or business services. |
|
|
BEA-381507
|
Info: No response payload to send on Inbound JMS Async-Sync endpoint
|
Description
| This is an informational message to alert the user that an empty response payload is being sent as a response to JMS proxy with response |
|
Action
| If this is expected behavior, no action is required. Otherwise one can use various pipeline actions to examine and set the body of the response message to be sent. |
|
|
BEA-381508
|
Warning: Failed to check whether connection factory factory supports XA. Will assume it does not: e
|
Description
| OSB JMS transport failed to determine whether the configured JMS connection factory supports XA transactions. As a result, it will assume that it does not, for the puposes of generation of service-related artifacts. |
|
Action
| Make sure that the JNDI provider referred to by the JMS service URL is up and running and can be properly accessed at service activation time. Also make sure that the JNDI name of the configured connection factory corresponds to an existing connection factory object in JNDI provider. |
|
|
BEA-381509
|
Warning: Cannot set unit of order on non-WLS 9.0 message producer
|
Description
| An attempt was made to set the 'UnitOfOrder' WLS JMS propety on message that corresponds to non-WLS JMS destination. Only WLS 9.0 and higher supports 'UnitOfOrder' feature. |
|
Action
| Check the configuration of JMS service to make sure that if the UnitOfOrder setting is used, then the URL corresponds to WLS 9.0 JMS provider. |
|
|
BEA-381510
|
Error: Error writing jar file: e
|
Description
| There was an unexpected error while generating JMS service-related artifacts. There should be an error message that points to the cause of the problem. |
|
Action
| Contact technical support |
|
|
BEA-381511
|
Error: Unexpected failure while processing an incoming message for endpoint name
|
Description
| There was an unexpected error while processing an inbound message by specified JMS proxy service. This may have happened due mis-configuration of the service |
|
Action
| Contact technical support |
|
|
BEA-381512
|
Error: JMS Endpoint with name ref already registered
|
Description
| There was an unexpected error at session activation time while registering a new JMS service. Two or more JMS services share the same name. |
|
Action
| Contact technical support |
|
|
BEA-381513
|
Error: The URIs for request and response may not be equal
|
Description
| In the configuration for the JMS proxy service the request and response URIs are the same. Such conguration is not legal as it will most likely result in an infinite loop and request/response processing. |
|
Action
| Make sure that request and response URIs have different values in JMS proxy service configuration |
|
|
BEA-381514
|
Error: Service binding(SOAP/XML/WSDL) has request/response operations but JMS transport configuration does not have any response information.
|
Description
| Service binding(SOAP/XML/WSDL) has request/response operations but JMS transport configuration does not have any response information. |
|
Action
| Make sure that the JMS transport configuration of the service is consistent with declared service binding type. |
|
|
BEA-381515
|
Error: Invalid target for JMS proxy: target
|
Description
| The target configured for JMS proxy service is not valid in the current cluster configuration. This may have happened if cluster configuration has recently changed or when this JMS service was moved (exported and imported) from one cluster to another. |
|
Action
| Make sure that the configured target (server or cluster) corresponds to one of the valid target names in the drop-down list of available targets in JMS transport configuration |
|
|
BEA-381516
|
Warning: Failued to modify delivery parameters of a WLS destination: e
|
Description
| There was an error while trying to set the configuration parameters on specified WLS destination. There should be an error message that points to the cause of the error. |
|
Action
| Contact technical support |
|
|
BEA-381517
|
Error: URI uri for this proxy service is already used by another proxy service: other with no message selector
|
Description
| Two or more JMS proxy services are using the same URI. The operation cannot be completed because only a single JMS proxy is allowed to receive messages from a given JMS destination. |
|
Action
| Make sure that the given JMS proxy is the only one that is configured with the URI in question. |
|
|
BEA-381518
|
Error: The generated MDB EAR file name fileName for service thisOne is already used by another service. Please change the name this service to avoid a collision.
|
Description
| There was an unexpected error while OSB was generating JMS service-related artifacts. |
|
Action
| Contact technical support |
|
|
BEA-381519
|
Error: Failure while processing an incoming message for endpoint name due to service configuration in flux
|
Description
| The processing of the message has failed in OSB runtime due to the fact that the configurations for the proxy service is in flux. This proxy is unable to process messages until the configuration stabilizes. |
|
Action
| Wait until the configuration of OSB server stabilizes and retry sending the request. |
|
|
BEA-381520
|
Error: Connection factory name does not exist!
|
Description
| OSB JMS transport failed to look up the configured JMS connection factory for the service with JMSMessageID response pattern in specified JNDI provider at service activation time |
|
Action
| Make sure that the JNDI provider referred to by the JMS service URL is up and running and can be properly accessed at service activation time. Also make sure that the JNDI name of the configured connection factory corresponds to an existing connection factory object in JNDI provider. |
|
|
BEA-381521
|
Error: The response destination is null or is not a queue
|
Description
| The JMS destination configured for response is not a queue. Only JMS queues are supported destinaitons for responses to JMS proxy services. |
|
Action
| Check that the JMS response URI configured in JMS proxy service refers to a JMS queue. |
|
|
BEA-381522
|
Error: The JMS URI uristr is not valid
|
Description
| One or more of the URIs configured for JMS service is not in the format exptected by OSB. The expected format is jms://host:port[,host:port]*/MyFactory/MyQueue where - host is the name of the server that is the JNDI provider - port is the port of the server that is the JNDI provider - MyFactory is the JNDI name of the connection factory - MyQueue is the JNDI name of the JMS destination |
|
Action
| Make sure that the URI string conforms to the expected format |
|
|
BEA-381523
|
Error: The server name serverName is not configured in the table of response JNDI destinations
|
Description
| There was one or more missing target that corresponds to a managed server that is part of OSB cluster domain in the map of destinations JMS service that uses JMSMessageID correlation pattern. Each managed server has to have a corresponding unique destination. This may have happened if cluster configuration has recently changed or when this JMS service was moved (exported and imported) from one cluster to another. |
|
Action
| Make sure that the configured target (server or cluster) corresponds to one of the valid target names in the drop-down list of available targets in JMS transport configuration |
|
|
BEA-381524
|
Error: response destination for serverName not found in table of response JNDI destinations
|
Description
| There was one or more missing destination that corresponds to a managed server that is part of OSB cluster domain in the map of destinations JMS service that uses JMSMessageID correlation pattern. Each managed server has to have a corresponding unique destination. This may have happened if cluster configuration has recently changed or when this JMS service was moved (exported and imported) from one cluster to another. |
|
Action
| Make sure that the configured target (server or cluster) corresponds to one of the valid target names in the drop-down list of available targets in JMS transport configuration |
|
|
BEA-381525
|
Error: Cannot re-use the same destination destination for serverName; use unique response destination for each managed server
|
Description
| There were two or more identical destination names configured for two different managed servers for JMS service with JMSMessageID correlation pattern. Each managed server has to have a corresponding unique destination. This may have happened if cluster configuration has recently changed or when this JMS service was moved (exported and imported) from one cluster to another. |
|
Action
| Make sure that each managed server name corresponds to a unique JMS destination name in JMS transport configuration for the service |
|
|
BEA-381526
|
Error: Response JNDI Names map not found for JMSMessageID response pattern
|
Description
| There was a problem with the configuration of JMS service with JMSMessageID correlation pattern. The configuration is missing a required element that specifies the map of destinations for a set of managed servers. |
|
|
BEA-381527
|
Error: Service Account ref is not static. Only static service accounts are supported with JMS proxies and business services.
|
Description
| The service account used in the configuration of JMS service is not a static account (i.e. either pass-through or mapped). Only static service accounts are supported with JMS proxies and business services |
|
Action
| Check that the type of the service account used in the configuration of the service and make sure only static accounts are used. |
|
|
BEA-381528
|
Error: Attempting an indirect send to a proxy using the JMSMessageID response pattern. Proxy-to-proxy routing not allowed with this pattern.
|
Description
| Sending an outbound message from a JMS proxy pattern to another JMS proxy with JMSMessageID response pattern is not supported |
|
Action
| Check the message flow configuration for the JMS proxy and make sure it does not route to a JMS proxy that uses JMSMessageID response pattern |
|
|
BEA-381529
|
Error: Transaction associated with message id messageId has failed due to status: status
|
Description
| A transaction has failed while waiting for response for JMS request/response service. As a result, any related response message will be ignored. |
|
Action
| Examine the log files to determine that cause of the transaction failure and/or retry sending the request. If the problem persists, contact technical support |
|
|
BEA-381530
|
Error: Failed to lookup connection factory name
|
Description
| OSB JMS transport failed to look up the configured JMS connection factory in specified JNDI provider at service activation time |
|
Action
| Make sure that the JNDI provider referred to by the JMS service URL is up and running and can be properly accessed at service activation time. Also make sure that the JNDI name of the configured connection factory corresponds to an existing connection factory object in JNDI provider. |
|
|
BEA-381531
|
Error: Inbound response will not be sent due to inbound request transaction status: status
|
Description
| A response to JMS proxy service will not be sent due to the fact that the transaction associated with the inbound request has failed due to stated reason. |
|
Action
| Examine the log files to determine that cause of the transaction failure and/or retry sending the request. If the problem persists, contact technical support |
|
|
BEA-381532
|
Info: Warning: configured JMS message expiration value of val milliseconds is very small.
|
Description
| This is a message to warn the user of the fact that the configured message expiration value is relatively small and might lead to lost messages due to their quick expiration. |
|
Action
| Make sure the configured expiration value is properly entered. No further action is necessary if the value is entered as desired. |
|
|
BEA-381533
|
Error: name already exists and is not a Queue
|
Description
| The destination specified in JMS Transport configuration already exists and is not a JMS Queue. |
|
Action
| Make sure the JMS transport configuration is consistent with the existing objects available from specified JNDI provider. That means if one configures a queue in JMS transport page and an object with the specified JNDI name exists, it is expected to be a Queue |
|
|
BEA-381534
|
Error: name already exists and is not a Topic
|
Description
| The destination specified in JMS Transport configuration already exists and is not a JMS Topic. |
|
Action
| Make sure the JMS transport configuration is consistent with the existing objects available from specified JNDI provider. That means if one configures a topic in JMS transport page and an object with the specified JNDI name exists, it is expected to be a Topic |
|
|
BEA-381535
|
Error: name already exists and is not a TopicConnectionFactory
|
Description
| The connection factory specified in JMS Transport configuration already exists and is not an instance of JMS TopicConnectionfactory. Since the configured destination type is a topic, one needs to provide an instance of valid TopicConnectionFactory in the configuration |
|
Action
| Make sure the JMS transport configuration is consistent with the existing objects available from specified JNDI provider. That means if one configures a topic in JMS transport page and an object with the specified JNDI name exists, it is expected to be a TopicConnectionFactory |
|
|
BEA-381536
|
Error: name is not a proxy service"
|
Description
| An unexpected error has occured during UDDI export of JMS services. The JMS service being exported was expected to be a proxy and was not. |
|
Action
| Contact technical support |
|
|
BEA-381537
|
Error: JMS provider-specific configuration was not specified
|
Description
| There was an unexpected error processing the message while parsing the JMS transport-specific configuration of the service endpoint |
|
Action
| Contact technical support |
|
|
BEA-381538
|
Error: Request metadata XML must be an instance of type
|
Description
| There was an unexpected error processing the message while processing request metadata for the inbound or outbound request. |
|
Action
| Check the pipeline actions in your message flow and make sure that you are setting the request metadata in way that is consistent with the transport specified for the service. One can use Log actions to examine the contents of any message context variable. |
|
|
BEA-381539
|
Error: Response metadata XML must be an instance of type
|
Description
| There was an unexpected error processing the message while processing response metadata for the inbound or outbound request. |
|
Action
| Check the pipeline actions in your message flow and make sure that you are setting the response metadata in way that is consistent with the transport specified for the service. One can use Log actions to examine the contents of any message context variable. |
|
|
BEA-381540
|
Warning: method received a message without a JMS Correlation Id; marking TX for rollback...
|
Description
| An OSB JMS request/response business service has picked up a message from configured JMS response destination that did not have expected JMSCorrelationID message property. As a result, the response transaction was marked for rollback |
|
Action
| Make sure that the back end JMS business service is properly functioning (e.g. that the JMSCorrelationID is being echoed when responding). Also, please make sure that the JMS destination configured for responses is not shared by other unrelated JMS services. |
|
|
BEA-381541
|
Warning: method received a message with an invalid JMS Correlation Id correlationId; marking TX for rollback...
|
Description
| An OSB JMS request/response business service has picked up a message from configured JMS response destination whose JMSCorrelationID message property had unexpected data. As a result, the response transaction was marked for rollback |
|
Action
| Make sure that the back end JMS business service is properly functioning (e.g. that the JMSCorrelationID is being echoed when responding). Also, please make sure that the JMS destination configured for responses is not shared by other unrelated JMS services. |
|
|
BEA-381542
|
Warning: method received a message with an unknown message Id messageId; marking TX for rollback...
|
Description
| An OSB JMS request/response business service has picked up a message from configured JMS response destination that did not correlate to a known JMS request that had been previously sent out. As a result, the response transaction was marked for rollback |
|
Action
| Make sure that the back end JMS business service is properly functioning (e.g. that the JMSCorrelationID is being echoed when responding). Also, please make sure that the JMS destination configured for responses is not shared by other unrelated JMS services. |
|
|
BEA-381543
|
Warning: URI: uri, does not have host and port information. Host and port information is configured generally as empty when a foreign JMS provider is used.
|
Description
| JMS proxy service can have empty host and port information in the URI when it is supposed to use foreign JMS provider. The destination is not created if it does not exist. |
|
|
BEA-381544
|
Info: JMS business service is upgraded successfully with the updated JMS configuration schema.
|
Description
| JMS business service is upgraded successfully with the updated JMS configuration schema. |
|
|
BEA-381545
|
Info: "Synchronous-Transactional" property in JMS transport configuration is upgraded to "Same Transaction For Response" in service configuration.
|
Description
| "Synchronous-Transactional" property in JMS transport configuration is upgraded to "Same Transaction For Response" in service configuration. |
|
|
BEA-381546
|
Error: Unexpected JMS Object type of message received for service other than messaging service with sub-type 'Java'
|
Description
| A JMS Object type of message was received by JMS proxy service or as a response to JMS business service for service other than messaging service with sub-type 'Java'. Messages should be of type Text or Bytes. |
|
Action
| Make sure only JMS Text or Bytes messages are being sent to OSB JMS proxy or business services for service other than messaging service with sub-type 'Java'. |
|
|
BEA-381547
|
Error: Unexpected type of message: messageType received for service configured as messaging service with sub-type Java
|
Description
| A Text or Bytes message was received by JMS proxy service or as a response to JMS business service for service configured as messaging service with sub-type Java. Messages should be of type Object. |
|
Action
| Make sure only JMS Object messages are being sent to OSB JMS proxy or business services for service configured as messaging service with sub-type Java. |
|
|
BEA-381548
|
Error: Service binding with response type 'Java' configured with incompatible response message type in the JMS transport configuration
|
Description
| The configuration of the JMS service was not compatible with the declared service binding type. A messaging service with 'Java' response type should not have a response message type configured in the JMS transport configuration. In this case, Object type of messages are sent as the response. |
|
Action
| Make sure that the JMS transport configuration should not have a response message type configured in the JMS transport configuration. |
|
|
BEA-381549
|
Error: Service binding with request type 'Java' configured with incompatible message type in the JMS transport configuration
|
Description
| The configuration of the JMS service was not compatible with the declared service binding type. A messaging service with 'Java' request type should not have a message type configured in the JMS transport configuration. In this case, Object type of messages are sent by the business service. |
|
Action
| Make sure that the JMS transport configuration should not have a message type configured in the JMS transport configuration. |
|
|
BEA-381550
|
Error: Payload from the pipeline not received with one java object
|
Description
| A message with java object should contain one java object. |
|
Action
| Make sure that the message contains only one java object. |
|
|
BEA-381551
|
Error: Response message type is not configured in service binding but JMS transport has response configuration.
|
Description
| The configuration of the JMS service is not compatible with the declared service binding type. JMS transport should not have response configuration as the service messaging type does not have any response. |
|
Action
| Make sure that the JMS transport configuration of the service is consistent with declared service binding type. |
|
|
BEA-381552
|
Error: Response message type is configured in service binding but JMS transport does not have any response configuration.
|
Description
| The configuration of the JMS service is not compatible with the declared service binding type. JMS transport should have response configuration as the service messaging type has response. |
|
Action
| Make sure that the JMS transport configuration of the service is consistent with declared service binding type. |
|