The WseePersist1.0 catalog contains messages in the range
BEA221000 - BEA221099. Messages in this catalog are part of the
weblogic.wsee
Internationalization package and the weblogic.wsee Localization package.
|
BEA-221000
|
Error: An unexpected error occurred: error
|
Description
| An unexpected error occurred. Please contact Oracle support and provide details of the exception and stack trace. |
|
Cause
| Unknown |
|
Action
| Contact Oracle support |
|
|
BEA-221001
|
Error: No store name provided, and persistence strategy is not LOCAL_ACCESS_ONLY. The SendingService cannot be created.
|
Description
| No store name provided, and persistence strategy is not LOCAL_ACCESS_ONLY. The SendingService cannot be created. |
|
Cause
| When requesting a network-available persistent store, the name of this store must be given when attempting to create a SendingService instance. |
|
Action
| Set up the store, and provide its name when creating the SendingService, or request a store that uses LOCAL_ACCESS_ONLY so the service can create the store for you. |
|
|
BEA-221002
|
Error: The store associated with the given store name (storeName) is slated for use across the network but is not an XA-capable store. Please specify another store name or configure this store to be location independent (e.g. JDBC-based, etc.)
|
Description
| The store associated with the given store name (storeName) is slated for use across the network but is not an XA-capable store. Please specify another store name or configure this store to be location independent (e.g. JDBC-based, etc.) |
|
Cause
| In order to use a store across the network, that store must support the XA transaction protocol. Without this, only local changed can be made. |
|
Action
| Set up the store, and provide its name when creating the SendingService, or request a store that uses LOCAL_ACCESS_ONLY so the service can create the store for you. |
|
|
BEA-221003
|
Error: A store instance with persistent store name storeName and connection name connectionName already exists.
|
Description
| A store instance with persistent store name storeName and connection name connectionName already exists. |
|
Cause
| Some component has attempted to create a store instance without first checking for an existing one. Please contact Oracle Tech Support to file an issue. |
|
Action
| Contact Oracle support. |
|
|
BEA-221004
|
Error: Logical store storeName not defined.
|
Description
| Logical store storeName not defined. |
|
Cause
| You have configured web services to use a named logical store but have not defined that logical store on this server. |
|
Action
| Change the name of the logical store to be used for this web service (or web service client) or define a logical store with the given name (using WLST, WLS console, etc.) |
|
|
BEA-221005
|
Error: You cannot reset the ID on a ClientIdentityFeature. Existing ID oldId attempted new ID newId
|
Description
| You cannot reset the ID on a ClientIdentityFeature. Existing ID oldId attempted new ID newId |
|
Cause
| You called ClientIdentityFeature.setClientId() but thid ID has already been set. You cannot reset the ID. |
|
Action
| Check the ID on the ClientIdentityFeature before trying to set it, or create a new client instance (Port/Dispatch instance) and set a new ClientIdentityFeature on that instance. |
|
