Oracle® Fusion Middleware Messages for Oracle Service Bus
11g Release 1 (11.1.1.7)

E15034-09

Back to Index Page


WliSbTransports Subsystem Messages

The WliSbTransports catalog contains messages in the range BEA381100 - BEA381199. 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-381101

Error: Error encountered while creating the endpoint endpointName: e

Description

An unexpected exception has occurred in OSB FTP transport while creating the endpoint. There should be an error message that points to the cause of the problem.

Action

Check that the endpoint configuration is formed properly.

BEA-381102

Error: Service Account Reference is missing in the FTP service configuration.

Action

Make sure that service account is specified in the FTP service configuration.

BEA-381103

Error: Invalid polling interval interval, it should be greater than zero.

Description

FTP Server is polled for new files by the Ftp proxy service after every poll interval. It should be greater than zero.

Action

Make sure that the polling interval is greater than zero.

BEA-381104

Error: Error while parsing or reading the Ftp Endpoint configuration.

Action

Check that the endpoint configuration is formed properly.

BEA-381105

Error: Error occured for the service endpoint: e

Description

An unexpected general purpose exception has occurred in OSB Ftp transport. There should be an error message that points to the cause of the problem.

Action

Contact technical support.

BEA-381106

Error: Unable to get file filename on attempt number attempt: e

BEA-381107

Error: Credential not found for alias alias: e

Action

Make sure that the credentials with the given name exists in the OSB domain.

BEA-381108

Info: File: filename moved to error directory path: errDirectory

BEA-381109

Error: File: filename was read from the remote FTP server: remotehost but could not be deleted after processing.

Action

Make sure that Ftp proxy service has exclusive access to the remote file. Also the current user should have read, write permission.

BEA-381110

Info: File filename has been put on remote server remotehost

BEA-381111

Error: URI Syntax error for the path path: ex

Description

URI is not formed properly.

Action

Make sure that the URI follows the correct syntax.

BEA-381112

Error: Unable to rename file filename on the remote host remoteHost for the service endpoint endpoint

Action

Make sure that Ftp proxy service has exclusive access to the remote file. Also the current user should have read, write permission.

BEA-381113

Info: File filename renamed to newName on the remote host remoteHost for the service endpoint endpoint

BEA-381114

Error: File filename could not be renamed to newName on the remote host remoteHost for the service endpoint endpoint: e

Description

Exception encountered while executing renaming the file on the remote FTP server.

Action

Make sure that Ftp proxy service has exclusive access to the remote file. Also the current user should have read, write permission.

BEA-381115

Error: File filename could not be deleted on the remote host remoteHost for the Ftp proxy service endpoint

Action

Make sure that Ftp proxy service has exclusive access to the remote file. Also the current user should have read, write permission.

BEA-381116

Error: URI uri for this proxy service is already used by another proxy service: other with same file mask.

Description

An error had occured while registering a new Ftp proxy service: The URI configured for this proxy service is already used by another Ftp proxy service. Each Ftp proxy service has to have a unique URI if the file mask is same.

Action

Check the transport configuration for Ftp proxy service and make sure that the combination of URI and the file mask is unique.

BEA-381117

Error: Exception in method: e

Description

Exception encountered while executing this method. There should be an error message that points to the cause of the problem.

Action

Error message may point to the cause of the problem.

BEA-381118

Error: Invalid pass by reference is set, it can only be true when the message type is of type XML.

Cause

Pass by reference is configured with non-xml message type Ftp proxy service.

Action

If Pass by reference is true, Ftp proxy service should be configured with xml message types.

BEA-381119

Error: Given service account refName is not of static type. Only static service accounts are supported with FTP proxy and business services.

Action

Make sure that the service account configured in FTP proxy or business service is a static service account.

BEA-381120

Error: Service account refName does not exist.

Action

Make sure that service account with the configured name exists in the OSB project.

BEA-381121

Error: Given encoding enc is invalid

Description

Encoding name is incorrect or the particular encoding is not supported by the Java virtual machine.

Action

Make sure that the Ftp proxy service is configured with supported encoding.

BEA-381122

Error: Retry count ct should be greater than zero.

Description

At the time of polling the FTP server for new files, FTP connection failures are tried for the number of times as specified by retry Count. It should be greater than zero.

Action

Make sure that retry count is greater than zero.

BEA-381123

Error: Invalid socket timeout ct, it should be greater than or equal to zero.

Action

Make sure that socket timeout is greater than or equal to zero.

BEA-381124

Error: Invalid read limit limit, it should be greater than or equal to zero.

Description

Read limit is the number of message polled by the Ftp proxy service in a polling cycle. It should always be greater than or equal to zero.

Action

Make sure that read limit is greater than or equal to zero.

BEA-381125

Error: Archive directory should be specified in case Ftp proxy service is configured with Pass by Reference as true.

Action

Make sure that archive directory points to valid file path.

BEA-381126

Error: Invalid transfer mode, it should be either binary or ascii.

Action

Make sure that transfer encoding is either binary or ascii.

 

Back to Index Page

Copyright © 2008, 2013, Oracle. All rights reserved.