WseePersist Subsystem Messages

The WseePersist1.0 catalog contains messages in the range BEA-221000 - BEA-221099. 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.

BEA-221006

Error: Improper buffering queue type "type" with JNDI name "queueJndiName" configured on logical store "logicalStoreName". You must use Uniform Distributed Queues or simple Queues with web services.

Description	Improper buffering queue type "type" with JNDI name "queueJndiName" configured on logical store "logicalStoreName". You must use Uniform Distributed Queues or simple Queues with web services.
Cause	You configured an invalid type of queue for a logical store (via the RequestBufferingQueueJndiName or ResponseBufferingQueueJndiName properties). You must use Uniform Distributed Queues (recommended) or plain Queues. If you wish to take advantage of migration features of web services in a cluster, you must use Uniform Distributed Queues. Note, when using configuration wizard or WLST to apply the wls_webservice_jaxws.jar extension template, you must explicitly request the creation of Uniform Distributed Queues as described in the web services documentation. By default, the configuration wizard and WLST create Weighted Distributed Queues in a cluster.
Action	Configure a Uniform Distributed Queue (or Queue) and provide this queues JNDI name to the logical store configuration (via the RequestBufferingQueueJndiName or ResponseBufferingQueueJndiName properties). Note, you can do this from the configuration wizard or WLST when applying the wls_webservice_jaxws.jar extension template, and the proper type and number of queues will be created automatically for you. See the web services documentation for more information on requesting Uniform Distributed Queues when using the template.