BPEL Messaging Exceptions ORABPEL 08500 - 08512

-
BPEL Messaging Exceptions ORABPEL 08500 - 08512
Messaging Exceptions 08500 - 08512

ORABPEL-08500
severity: 10
type: error
name: Invalid jms message type
description: The JMS message type \"{0}\" is invalid, the BPEL server supports only \"text\" and \"bytes\" message types.
fix: Please verify the OraBPEL JMS Service documentation for valid JMS message types.

ORABPEL-08501
severity: 10
type: error
name: MOM Destination not found.
description: The process domain was unable to lookup the destination \"{0}\". The exception reported is: \"{1}\".
fix: Please ensure that the MOM destination has been registered properly with the JNDI context of the application server.

ORABPEL-08502
severity: 10
type: error
name: MOM Connector not found.
description: The process domain was unable to lookup the messaging connector \"{0}\".
fix: Please check that the messaging connector has been configured properly in the process domain descriptor file.

ORABPEL-08503
severity: 10
type: error
name: MOM Connector shutdown not found.
description: The process domain was unable to close the messaging connector \"{0}\". The exception reported is : \"{1}\".
fix: Please check the MOM Server for the connector has been running properly or not.

ORABPEL-08504
severity: 10
type: error
name: Empty MOM destination
description: The destination configuration \"{0}\" for the MOM connector \"{1}\" has not been specified.

ORABPEL-08505
severity: 10
type: error
name: Cannot create subscriber.
description: The process domain was unable to create a subscriber object for the destination \"{0}\". The exception reported is: {1}.
fix: Please check that the MOM service for the application server has been configured properly - the MOM and EJB connection pools must be the same.

ORABPEL-08506
severity: 10
type: error
name: Cannot create durable subscriber.
description: The process domain was unable to create a durable subscriber for the destination \"{0}\". The exception reported is: \"{1}\".
fix: In order to use durable subscriber, you might need to configure persistence store for the destination. Please check the messaging vendor''s user manual on how to configure persistence store for the destination.

ORABPEL-08507
severity: 10
type: error
name: Failed to convert process domain message to MOM message
description: The process domain is unable to convert the OraBPEL message to the vendor specific MOM Message \"{0}\". The exception reported is: \"{1}\".
fix: Please verify the Process Domain Connector documentation for valid MOM types.

ORABPEL-08508
severity: 10
type: error
name: Failed to convert standard MOM message to process domain message.
description: The process domain is unable to convert the standard MOM Message \"{0}\" to the corresponding process domain message. The reported exception is: \"{1}\".
fix: Please verify the Process domain Connector documentation for valid MOM types.

ORABPEL-08509
severity: 10
type: error
name: MOM connector invalid property.
description: The process domain was unable to interpret value of the MOM connector property \"{0}\". The value of this \"{0}\" property is \"{1}\". The exception reported is \"{2}\".
fix: Please verify the JNDI identfier is valid in the MOM provider''s JNDI registry.

ORABPEL-08510
severity: 10
type: error
name: Cannot send message to message broker
description: The process domain was unable to send a message to the messaging destination \"{0}\". The exception reported is: \"{1}\".
fix: Please check that the messaging service for the application server has been configured properly.

ORABPEL-08511
severity: 10
type: error
name: Empty MOM destination
description: The destination JNDI name or destination type has not been specified for destination \"{0}\", connector \"{1}\".

ORABPEL-08512
severity: 10
type: error
name: Empty MOM connector name
description: The connector name for MOM destination \"{0}\" has not been specified.

Comments

Post a Comment

Popular posts from this blog

ORA-44412: XE edition memory parameter invalid or not specified

-
SQL> connect sys as sysdba Enter password: Connected to an idle instance. SQL> startup ORA-44412: XE edition memory parameter invalid or not specified SQL> startup pfile=C:\oraclexe\app\oracle\product\10.2.0\server\config\scripts\init.ora ORACLE instance started. Total System Global Area 805306368 bytes Fixed Size 1289996 bytes Variable Size 209715444 bytes Database Buffers 591396864 bytes Redo Buffers 2904064 bytes Database mounted. Database opened. SQL> create spfile from pfile='C:\oraclexe\app\oracle\product\10.2.0\server\config\scripts\init.ora'; File created. SQL> shutdown Database closed. Database dismounted. ORACLE instance shut down. SQL> startup ORACLE instance started. Total System Global Area 805306368 bytes Fixed Size 1289996 bytes Variable Size 209715444 bytes Database Buffers 591396864 byt...
Read more

BPEL DOM Exceptions ORABPEL 09200 - 09250

-
BPEL DOM Exceptions ORABPEL 09200 - 09250 DOM Exceptions 09200 - 09250 ORABPEL-09200 severity: 10 type: error name: Invaild to part type. description: The \"\" assign part \"{0}\" is invalid, the part should not be null and it should be an instance of org.w3c.Element. Please verify the BPEL source at line number \"{1}\". ORABPEL-09201 severity: 10 type: error name: The value is invalid. description: Error in expression: value is empty at line \"{1}\". The variable : \"{0}\" is null, when applied to document shown below:\n{2} fix: Please check the BPEL source at line number \"{1}\" and verify the \"from\" variable. ORABPEL-09202 severity: 10 type: error name: The value is invalid. description: Error in expression: value is empty at line \"{1}\". The part : \"{0}\" is null, when applied to document shown below:\n{2} fix: Please check the BPEL source at line number \"{1}\...
Read more

How to mount a WD Book Live as NFS in OEL6U3

-
Scenario : I have a Windows 8 (Host) laptop on which I am running two OEL6U3 (Guest) machines in a Virtual Box. I want to have a shared mount between the two Linux machine which will allow me to read/write from both the machines concurrently. Its a very common scenario for a High Availability Environment. Virtual Box provides a facility of creating sharable VDI disks which can be mounted on multiple machines, but it doesn’t allow concurrent read/write access from multiple machines. If you are installing RAC database then its still achievable, because ASM will provide the feature of concurrent read/writes, but if you want to install a WebLogic cluster with High Availability the recommended approach would be to have a Shared Mount. Step to create a shared nfs mount is fairly simple. I am using a WD My Book Live, and will mount the Public folder as shared mount 1. Get the hostname/ip of the WD device. 2. On the Linux Machine 1 create the folder where you want to mount the nfs ...
Read more