Oracle SOA

bpel_synch

2009-07-08T02:05:00.001-07:00

enqueue dequeue sql script

2009-07-08T01:53:00.000-07:00

Enqueue Message

DECLARE
enqueue_options DBMS_AQ.enqueue_options_t;
message_properties DBMS_AQ.message_properties_t;
msg_handle RAW (16);
ipmsg ip_message_type;
xml_clob CLOB;
msg_id NUMBER (10);
subscribers DBMS_AQ.aq$_recipient_list_t;
BEGIN
xml_clob := '';
subscribers (1) :=
SYS.aq$_agent (''
, NULL
, NULL);
message_properties.recipient_list := subscribers;
DBMS_AQ.enqueue (queue_name => ''
, enqueue_options => enqueue_options
, message_properties => message_properties
, payload => xml_clob
, msgid => msg_handle);
COMMIT;
END;

Dequeue Message

DECLARE
dequeue_options DBMS_AQ.dequeue_options_t;
message_properties DBMS_AQ.message_properties_t;
message_handle RAW (16);
xml_clob CLOB;
BEGIN
dequeue_options.consumer_name := '';
dequeue_options.dequeue_mode := DBMS_AQ.remove;
-- Only if you want to remove message
dequeue_options.navigation := DBMS_AQ.next_message;
dequeue_options.WAIT := DBMS_AQ.forever;
DBMS_AQ.dequeue (queue_name => ''
, dequeue_options => dequeue_options
, message_properties => message_properties
, payload => xml_clob
, msgid => message_handle);
DBMS_OUTPUT.PUT_LINE ('Message ID : ' xml_clob);
COMMIT;
END;

Examples of Date and Time Formatting

2009-07-05T11:38:00.000-07:00

Example: Gregorian Calendar

The following examples show a selection of dates and times and the way they might be formatted. These examples assume the use of the Gregorian calendar as the default calendar.

Required Output	Expression
`2002-12-31`	`format-date($d, "[Y0001]-[M01]-[D01]")`
`12-31-2002`	`format-date($d, "[M]-[D]-[Y]")`
`31-12-2002`	`format-date($d, "[D]-[M]-[Y]")`
`31 XII 2002`	`format-date($d, "[D1] [MI] [Y]")`
`31st December, 2002`	`format-date($d, "[D1o] [MNn], [Y]", "en", (), ())`
`31 DEC 2002`	`format-date($d, "[D01] [MN,*-3] [Y0001]", "en", (), ())`
`December 31, 2002`	`format-date($d, "[MNn] [D], [Y]", "en", (), ())`
`31 Dezember, 2002`	`format-date($d, "[D] [MNn], [Y]", "de", (), ())`
`Tisdag` `31 December 2002`	`format-date($d, "[FNn] [D] [MNn] [Y]", "sv", (), ())`
`[2002-12-31]`	`format-date($d, "[[[Y0001]-[M01]-[D01]]]")`
`Two Thousand and Three`	`format-date($d, "[YWw]", "en", (), ())`
`einunddreißigste` `Dezember`	`format-date($d, "[Dwo] [MNn]", "de", (), ())`
`3:58 PM`	`format-time($t, "[h]:[m01] [PN]", "en", (), ())`
`3:58:45 pm`	`format-time($t, "[h]:[m01]:[s01] [Pn]", "en", (), ())`
`3:58:45 PM PDT`	`format-time($t, "[h]:[m01]:[s01] [PN] [ZN,*-3]", "en", (), ())`
`3:58:45 o'clock PM PDT`	`format-time($t, "[h]:[m01]:[s01] o'clock [PN] [ZN,*-3]", "en")`
`15:58`	`format-time($t,"[H01]:[m01]")`
`15:58:45.762`	`format-time($t,"[H01]:[m01]:[s01].[f001]")`
`15:58:45 GMT+02:00`	`format-time($t,"[H01]:[m01]:[s01] [z]", "en", (), ())`
`15.58 Uhr GMT+02:00`	`format-time($t,"[H01]:[m01] Uhr [z]", "de", (), ())`
`3.58pm on Tuesday, 31st December`	`format-dateTime($dt, "[h].[m01][Pn] on [FNn], [D1o] [MNn]")`
`12/31/2002 at 15:58:45`	`format-dateTime($dt, "[M01]/[D01]/[Y0001] at [H01]:[m01]:[s01]")`

Example: Non-Gregorian Calendars

The following examples use calendars other than the Gregorian calendar.

These examples use non-Latin characters which might not display correctly in all browsers, depending on the system configuration.

Description	Request	Result
Islamic	`format-date($d, "[D١] [Mn] [Y١]", "Islamic", "ar", "AH", ())`	٢٦ ﺸﻭّﺍﻝ ١٤٢٣
Jewish (with Western numbering)	`format-date($d, "[D] [Mn] [Y]", "he", "AM", ())`	‏26 טבת 5763
Jewish (with traditional numbering)	`format-date($d, "[Dאt] [Mn] [Yאt]", "he", "AM", ())`	כ״ו טבת תשס״ג
Julian (Old Style)	`format-date($d, "[D] [MNn] [Y]", "en", "OS", ())`	18 December 2002
Thai	`format-date($d, "[D๑] [Mn] [Y๑]", "th", "BE", ())`	๓๑ ธันวาคม ๒๕๔๕

How to enable debugging in Oracle ESB

2009-07-05T11:34:00.001-07:00

1. Login into the Application Server Control at http://Server.Client.com:7777/em
2. Click on the oc4j_soa instance and Administration tab.
3. Click on Logger Configuration.
4. Now expand Root Logger / oracle to display the logger classes and the Log Level settings.
5. In the Log Level list, select the level FINE for the following classes
. oracle.tip.esb.server.common
. oracle.tip.esb.server.service
6. Restart the SOA suite to apply the changes and the logs can be found at

\\SERVER\\j2ee\oc4j_soa\application-deployments\esb-dt\oc4j_soa_default_group_1\application.log
\\SERVER\\j2ee\oc4j_soa\application-deployments\esb-rt\oc4j_soa_default_group_1\application.log

Oracle BPEL process manager rollback

2009-07-05T11:25:00.000-07:00

Question:
I have a empty BPEL process that polls for AQJMS messages using a JMS adapter and then insert the received messages to the DB. Now the problem is, if there is any error w.r.t the DB insert, then it should rollback the message to the source destination i.e., my AQJMS Queue. But it is not happening. using the bpelx:rollback explicitly doesn't seem to help.

Answer:
You need to make it as one transaction. Use JCA-XA transaction. Just like in PL/SQL to make a transaction block we write it inside BEGIN ... END; in BPEL we create a JNDI of XA type (global-transaction handler) and then configure the property name 'transaction' to 'participate' for all partner links which are part of the transaction.

participate< /property>

However you need to take care of one thing, if the process is syncronous and you call rollback then it will not show up in BPEL console, since it posting to dehydration db will also be rollbacked.

Read the soa_best_practices_1013x
http://download.oracle.com/technology/tech/soa/soa_best_practices_1013x_drop3.pdf

Check the blog below for example on how to do this.
http://soab2bsahil.blogspot.com/2009/04/rollbacking-ebs-apis-using-bpel.html

Tables to be monitered in ORABPEL schema

2009-07-05T10:51:00.000-07:00

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'PC_TASKPAYLOAD';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'WFCOMMENTS';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'DLV_SUBSCRIPTION';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'ATTACHMENT_REF';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'TASK';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'PROCESS_DEFAULT';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'ACTIVITY_SENSOR_VALUES';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'PC_TASK';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'WFMESSAGEATTRIBUTE';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'WFATTACHMENT';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'CUBE_INSTANCE';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'SCOPE_ACTIVATION';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'SYNC_STORE';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'SUITCASE_BIN';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'ATTACHMENT';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'WFTASK';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'PC_TASKATTACHMENT';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'VERSION_SERVER';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'WFROUTINGSLIP';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'WFUSERVACATION';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'WFUSERTASKVIEWGRANT';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'WFUSERPREFERENCE';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'WFTASKTIMER';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'WFNOTIFICATIONMESSAGES';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'DOCUMENT_CI_REF';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'LOAN_CUSTOMER';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'WFNOTIFICATION';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'WI_EXCEPTION';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'NATIVE_CORRELATION';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'FAULT_SENSOR_VALUES';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'PC_OWF';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'PC_TASKASSIGNEE';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'WFATTRIBUTELABELMAP';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'WFUSERTASKVIEW';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'CI_INDEXES';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'SYNC_TRAIL';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'INVOKE_MESSAGE';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'VARIABLE_SENSOR_VALUES';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'BPELPM_ERRORS';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'CUBE_SCOPE';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'XML_DOCUMENT';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'BPELNOTIFICATION';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'ID_RANGE';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'DOMAIN_PROPERTIES';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'PC_TASKHISTORY';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'WFNOTIFICATIONSTATUS';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'WFTASKMETADATA';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'VERSION';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'AUDIT_TRAIL';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'PROCESS';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'TEST_DEFINITIONS';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'DOMAIN';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'PC_TASKASSIGNEEHISTORY';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'WORK_ITEM';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'DLV_MESSAGE';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'DOCUMENT_DLV_MSG_REF';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'PROCESS_DESCRIPTOR';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'PROCESS_LOG';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'SENSOR_SEQUENCE';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'WFTASKHISTORY';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'WFASSIGNEE';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'WFATTRIBUTELABELUSAGE';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'WFTASKDISPLAY';

select sum(bytes) from dba_extents where segment_type = 'TABLE' and segment_name = 'AUDIT_DETAILS';

How to limit the performance of the BPEL File Adapter

2007-08-12T10:33:00.000-07:00

Applies to:
Oracle(R) BPEL Process Manager - Version: 10.1.2 to 10.1.3
Information in this document applies to any platform.
Goal
How can you limit the number of files a file adapter processes at a time?
Can you process one file after another?

Solution

For async processes, the number of BPEL worker threads will limit the number of concurrent
instances. For example, if there are 2000 files in a directory to be processed by the file / ftp adapter then
no more than instances will be executing concurrently.

As you can limit the number of threads available to all processes in a BPEL domain with the
dspMaxThreads parameter, should you wish to therefore only process a low number of files at a time
you can deploy that file adapter process to it's own domain and limit the number of threads within
that domain. By using multiple domains, the sum of the dspMaxThreads settings for all domains
must not exceed the MDB J2EE listener threads setting.

These are further settings are discussed at length within the Performance Tuning chapter of the
Guide below;

Oracle® BPEL Process Manager
Administrator’s Guide
Release 10.1.2
Part No. B25015-01
Chapter 3, Performance Tuning
http://www.oracle.com/technology/products/ias/bpel/documents/bpel_admin_10.1.3.1.0.pdf

How to purge BPEL process instances manually?

2007-08-12T10:00:00.000-07:00

Oracle(R) BPEL Process Manager - Version: 10.1.2.0.2
Information in this document applies to any platform.
Goal
How to purge BPEL process instances manually?

Solution
Please follow the steps below to purge BPEL instances.

1. Make a back up of your dehydration store.

2. Create the script purge_instances.sql :

Create or Replace procedure
purge_instances( p_older_than in timestamp)
as
cursor c_cube_instance(p_date timestamp) is
select cikey
from cube_instance
where state >= 5 and modify_date < p_date;

cursor c_invoke_message(p_date timestamp) is
select message_guid
from invoke_message
where state > 1 and receive_date < p_date;

cursor c_dlv_message(p_date timestamp) is
select message_guid
from dlv_message
where state > 1 and receive_date < p_date;
begin
-- Delete all closed instances older than specified date
--
for r_cube_instance in c_cube_instance(p_older_than)
loop
collaxa.delete_ci( r_cube_instance.cikey );
end loop;

-- Purge all handled invoke_messages older than specified date
--
for r_invoke_message in c_invoke_message(p_older_than)
loop
delete from invoke_message_bin
where message_guid = r_invoke_message.message_guid;

delete from invoke_message
where message_guid = r_invoke_message.message_guid;
end loop;

-- Purge all handled callback messages older than specified date
--
for r_dlv_message in c_dlv_message(p_older_than)
loop
delete from dlv_message_bin
where message_guid = r_dlv_message.message_guid;

delete from dlv_message
where message_guid = r_dlv_message.message_guid;
end loop;

end purge_instances;
/

3. Connect to SQLPlus as user orabpel and run the script.
For Example:
Declare
P_OLDER_THAN Timestamp;
Begin
P_OLDER_THAN := '05/SEP/06 09:05:00 PM';

PURGE_INSTANCES(P_OLDER_THAN => P_OLDER_THAN);
End;

Process Instances Do Not Appear In The BPEL Console - Timeout Errors

2007-08-12T09:45:00.000-07:00

Oracle(R) BPEL Process Manager - Version: 10.1.2 to 10.1.3
This problem can occur on any platform.

Symptoms
New BPEL process instances are not visible in the BPELConsole.
However, Instance activity can be seen in the domain.log.
Additionally you may see transaction timeout errors in the Domain.log

Cause
At the application server J2EE layer, the JTA transaction timeout is less than the time it takes to perform an activity.
The recommended JTA transaction timeout value should be increased to the total time of the sync activity or exec activity, then add 2-3 minutes.

Solution
To implement the solution, please execute the following steps:

1. Within the J2EE application container level, increase the JTA transaction timeout value to the
expected total time of a sync activity or exec activity, then add 2-3 minutes.
2. Restart the container and retest.

If using OAS, this is configured via the iasconsole > midtier:instance > OC4J:instance > config > server.xml > transaction-config timeout parameter that by default is set to 30000.

Info on this parameter:
Oracle® Application Server Containers for J2EE, User’s Guide, 10g Release 2 (10.1.2)
Part No. B14011-01
Page 116/144
http://download-west.oracle.com/docs/cd/B14099_09/web.1012/b14011.pdf

<transaction-config>
Transaction configuration for the server.
Attribute:
¦ timeout="30000" — Specifies the maximum amount of time (in milliseconds) that a transaction can take to finish before it is rolled back due to a timeout. The default value is 30000. This timeout will be a default timeout for all transactions
that are started in OC4J. You can change it by using the dynamic API—UserTransaction.setTransactionTimeout(milliseconds).

In OAS / OC4J / SOA Suite 10.1.3 this parameter is no longer supported. Instead this is defined through the Application Server Control url, and then: oc4j_soa instance > administration > under SERVICES / Transaction Manager (JTA) > administration > under GENERAL, modify 'Transaction Timeout'. Apply and restart the container. For more details see: Oracle® Containers for J2EE Services Guide, 10g (10.1.3.1.0), Part Number B28958-01 - http://download-west.oracle.com/docs/cd/B31017_01/web.1013/b28958/jta.htm

Additionally, Appendix A1.1 of the BPEL Developer Guide goes into detail for each of the timeout settings, at http://download-west.oracle.com/docs/cd/B31017_01/integrate.1013/b28981/app_trblshoot.htm#sthref3957

NOTES: The 'syncMaxWaitTime' parameter in the Manage / BPEL Domain link of the BPELConsole can also be modified to alter the maximum time the process result receiver will wait for a result before returning. Results from asynchronous BPEL processes are retrieved synchronously via a receiver that will wait for a result from the container. This can useful when debugging transaction timeout errors that can sometimes accompany the main subject of this Note.

Additionallty: The level of logging can be modified to improve performance of a system via the 'Manage BPEL Domain' link within the BPEL console. From there you can alter the audit level based on your desired preferences;

auditLevel: Audit trail logging level Controls the amount of audit events logged by a process; currently supported logging levels are:

* off - absolutely no logging performed whatsoever; may result in a slight performance boost for processing instances.
* minimal - all events are logged; however, no audit details are logged.
* production - all events are logged. The audit details for assign activities are not logged; the details for all other nodes are logged.
* development - all events are logged; all audit details for all activities are logged.

The default value is "development".

Database Adapter and Bpel Process Manager run out of Database Connections

2007-08-12T09:42:00.000-07:00

Oracle(R) BPEL Process Manager - Version: 10.1.2.0.2

Symptoms
The problem manifests itself by the database adapter and BPEL running out of database connections. New connections cannot be established.

The following error might occur as a side effect:

Database Adapter::Inbound oracle.tip.adapter.db.InboundWork runOnce Exception during
polling of the database ORABPEL-11624 DBActivationSpec Polling Exception.
Query name: [ClarifyPollingProdService], Descriptor name:
[ServiceRequestAutomation.TableCase].
Polling the database for events failed on this iteration.
If the cause is something like a database being down successful polling will resume once conditions change.
Caused by Exception [TOPLINK-4002]

(OracleAS TopLink - 10g (9.0.4.5) (Build 040930)):
oracle.toplink.exceptions.DatabaseException
Exception Description:
java.sql.SQLException: Io exception: Connection timed out
Internal Exception: java.sql.SQLException: Io exception: Connection timed out
Error Code: 17002.

Cause

Both OC4J running BPEL and the database adapter reached the maximum number of connections and were unable to establish new ones.

The reason for the problem is a database adapter Bug 5595347.

According to Bug 5595347, the database adapter might leave open connections behind.
The fix for Bug 5595347 is included in Patch 5638122.

Solution
To implement the solution, please execute the following steps:

Apply Patch 5638122.

References
Bug 5595347 - ORIONCMTCONNECTION NOT CLOSED IN ORABPEL~OC4J_BPEL~DEFAULT_ISLAND~1
Note 314422.1 - Remote Diagnostic Agent (RDA) 4 - Getting Started
Patch 5638122 - MERGE LABEL REQUEST ON TOP OF 10.1.2.0.2 FOR BUGS 5149866 5595347 5205630

How To Read From A File in Mid-Process

2007-08-12T09:36:00.000-07:00

Oracle(R) BPEL Process Manager - Version: 10.1.2

Goal
How to read from a file in the middle of a process?

Solution
The proper way to read from a file in the middle of a BPEL process is to use the built-in XPath function, ora:readfile. Avoid using the file adapter to read a file. The file adapter (Read) is not designed for reading a file in the middle of a process. It is used to trigger the BPEL process in most cases. So in this scenario, the file adapter is not a good choice. Also it needs to use correlation sets to read files in the middle of a process.

Embedded Java code can solve the problem, but it is hard to maintain, and also not recommended.

How to use the ora:readfile function:

1. Drag an Assign activity and place it in the correct position in the BPEL process
2. Create a new Assign rule using the ora:readfile("file path", "xml schema path") XPath function
3. Assign the result to a variable.

A Code Example:

<assign name="Assign_1">
<copy>
<from expression="ora:readFile("file:///D:\\tmp\\PO.xml",
"file:///D:\\tmp\\OrderBookingPO.xsd")"/>
<to variable="var1" query="/ns1:PurchaseOrder"/>
</copy></assign>

Switching The Process Status From Retired To Active Doesn't Properly Start A Process

2007-08-12T09:31:00.000-07:00

Oracle(R) BPEL Process Manager - Version: 10.1.3.1
This problem can occur on any platform.

Symptoms
A BPEL process containing an AQ adapter which dequeues from a queue is deployed and its process lifecycle status is turned to "Retired". Later, the process lifecycle status is turned to "Active" so that dequeue of messages takes place. No instances of the BPEL process get initiated and messages remain in AQ Queue.

When the same BPEL process is deployed with process state as 'Off', keeping process lifecycle status 'Active' and later turning process state to 'On' the BPEL process is instantiated.

Cause
Bug 5879997 - ACTIVATION AGENT DOES NOT GET ACTIVATED BY MODIFYING THE PROCESS LIFECYCLE
Bug 5567281 - WHEN PROCESS IS RETIRED, CANT CONTINUE DUE TO EP DEACTIVATION

Solution
Apply Patch 6028270 which includes the fix for the above two bugs

References
Bug 5879997 - ACTIVATION AGENT DOES NOT GET ACTIVATED BY MODYFING THE PROCESS LIFECYCLE
Patch 6028270 - MERGE LABEL REQUEST ON TOP OF 10.1.3.1 FOR BUGS 5956917 5964097 5990976 5987760

BPEL Server hangs due to "java.lang.OutOfMemoryError"

2007-08-12T05:58:00.000-07:00

Oracle(R) BPEL Process Manager - Version: 10.1.2.0.2
Linux x86
Symptoms
The BPEL server hangs and a java.lang.OutOfMemoryError is displayed in the domain.log file.

You will see the following stack trace in the domain.log

<ERROR> <default.collaxa.cube.engine.dispatch>
<DispatchHelper::handleMessage> failed to handle message
javax.ejb.EJBException: Transaction was rolled back: java.lang.OutOfMemoryError; nested
exception
is: java.rmi.RemoteException: ; nested exception is:
java.lang.OutOfMemoryError
java.rmi.RemoteException: ; nested exception is:
java.lang.OutOfMemoryError
at com.evermind.server.ejb.EJBUtils.makeException(EJBUtils.java:886)
at

ICubeDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(ICubeDeliveryLocalBean_StatelessSe
ssionBeanWrapper16.java:1846)
at

com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMe
ssageHandler.java:37)
...
.....
Message handle error.
An exception occurred while attempting to process the message
"com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the exception is:
Transaction was rolled back: java.lang.OutOfMemoryError; nested exception is:
java.rmi.RemoteException: ; nested exception is:
java.lang.OutOfMemoryError

ORABPEL-05002

Message handle error.
An exception occurred while attempting to process the message
"com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the exception is:
Transaction was rolled back: java.lang.OutOfMemoryError; nested exception is:
java.rmi.RemoteException: ; nested exception is:
java.lang.OutOfMemoryError
Cause
The BPEL OC4J container uses 512 MB of memory by default 512MB, which is not enough if you are running BPEL in a high load environment.

You need to increase the JVM settings. Here is are some recommendations for a Linux Box with 4GB of memory and 2 CPUs. (If you are using a different platform from Linux, these parameters may not apply.)

-Xmn1228m -XX:+AggressiveHeap -Xms2048m -Xmx2048m

-Xmn1228m
Garbage collector (Oracle recommends sizing the Eden space to be 60 to 70 percent of the total
heap size.)

-XX:+AggressiveHeap
Recommended if you are using two or more CPUs.
The -XX:+AggressiveHeap option inspects the system resources (size of memory and number of processors) and attempts to set variousparameters to be optimal for long-running, memory allocation-intensive jobs.

-Xms2048m
Iniatial heapsize. The heap size controls the amount of memory the JVM uses

-Xmx2048m
Maximum heapsize

It is also neccesary to apply some patches related to the memory usage in BPEL:

5638122 -->MERGE LABEL REQUEST ON TOP OF 10.1.2.0.2 BUGS 5149866 5595347 5205630
5499891 -->CHANGES MADE FOR BETTER MEMORY USE TO AVOID OUTOFMEMORY

Solution
To implement the solution, please execute the following steps:

1. Shut down your application server
2. Backup the <integration_home>\opmn\conf\opmn.xml
3. Increase the BPEL JVM settings. Edit the file <integration_home>\opmn\conf\opmn.xml :

3.1 Look for the OC4J_BPEL process type section

Your original opmn.xml should look like the example below (just the OC4J_BPEL section)

<process-type id="OC4J_BPEL" module-id="OC4J">
<module-data>
<category id="start-parameters">
<data id="java-options" value="-server-Xrs-Djava.security.policy=D:\Oracle\OAS\portal\MT\j2ee\OC4J_BPEL\config\java2.policy-Djava.awt.headless=true
-Xbootclasspath^/p:D:\Oracle\OAS\portal\MT\integration\orabpel/lib/orabpel-boot.jar;D:\Oracle\OAS\portal\MT\integration\orabpel/lib/connector15.jar
-Doc4j.userThreads=true
-Dorabpel.home=D:\Oracle\OAS\portal\MT\integration\orabpel
-Dhttp.proxySet=true
-Dhttp.proxyHost=www-proxy.us.oracle.com -Dhttp.proxyPort=80
-Dhttp.nonProxyHosts=aalvarad-pc.us.oracle.com|localhost|*.us.oracle.com|aalvarad-pc
-Djava.net.preferIPv4Stack=true -server -Xms256M -Xmx512M -Doracle.mdb.fastUndeploy=60 "/>
<data id="oc4j-options" value="-properties"/>
</category>
<category id="stop-parameters">
<data id="java-options" value="-Djava.security.policy=D:\Oracle\OAS\portal\MT\j2ee\OC4J_BPEL\config\java2.policy-Djava.awt.headless=true"/>
<data id="oc4j-options" value="force "/>
</category>
</module-data>
<start timeout="900" retry="2"/>
<stop timeout="120"/>
<restart timeout="720" retry="2"/>
<port id="ajp" range="12501-12600"/>
<port id="rmi" range="12401-12500"/>
<port id="jms" range="12601-12700"/>
<process-set id="default_island" numprocs="1"/>
</process-type>

Look for the entry
-server -Xms256M -Xmx512M
and replace it with
-server -Xmn1228m -XX:+AggressiveHeap -Xms2048m -Xmx2048m

3.2. After the modifications, your opmn.xml file should look like this

New opmn.xml file (just the OC4J_BPEL section):

<process-type id="OC4J_BPEL" module-id="OC4J">
<module-data>

<category id="start-parameters">
<data id="java-options" value="-server
-Xrs -Ddatasource.verbose=true
-Djava.security.policy=D:\Oracle\OAS\portal\MT\j2ee\OC4J_BPEL\config\java2.policy

-Djava.awt.headless=true
-Xbootclasspath^/p:D:\Oracle\OAS\portal\MT\integration\orabpel/lib/orabpel-boot.jar;D:\Oracle\OAS\po

rtal\MT\integration\orabpel/lib/connector15.jar -Doc4j.userThreads=true
-Dorabpel.home=D:\Oracle\OAS\portal\MT\integration\orabpel
-Dhttp.proxySet=true
-Dhttp.proxyHost=www-proxy.us.oracle.com -Dhttp.proxyPort=80
-Dhttp.nonProxyHosts=aalvarad-pc.us.oracle.com|localhost|*.us.oracle.com|aalvarad-pc

-Djava.net.preferIPv4Stack=true -server -Xmn1228m -XX:+AggressiveHeap -Xms2048m -Xmx2048m

-Doracle.mdb.fastUndeploy=60 "/>
<data id="oc4j-options" value="-properties"/>

</category>
<category id="stop-parameters">
<data id="java-options"

value="-Djava.security.policy=D:\Oracle\OAS\portal\MT\j2ee\OC4J_BPEL\config\java2.policy

-Djava.awt.headless=true"/>
<data id="oc4j-options" value="force "/>

</category>
</module-data>
<start timeout="900" retry="2"/>

<stop timeout="120"/>
<restart timeout="720" retry="2"/>

<port id="ajp" range="12501-12600"/>
<port id="rmi" range="12401-12500"/>

<port id="jms" range="12601-12700"/>
<process-set id="default_island" numprocs="1"/>
</process-type>

4. Apply the following patches:

Bug 5638122 MERGE LABEL REQUEST ON TOP OF 10.1.2.0.2 BUGS 5149866 5595347 5205630
Bug 5499891 CHANGES MADE FOR BETTER MEMORY USE TO AVOID OUTOFMEMORY

4) Restart your application server.

References
Patch 5499891 - CHANGES MADE FOR BETTER MEMORY USE TO AVOID OUTOFMEMORY
Patch 5638122 - MERGE LABEL REQUEST ON TOP OF 10.1.2.0.2 FOR BUGS 5149866 5595347 5205630

One Possible Cause For Orabpel-11017

2007-08-12T05:49:00.000-07:00

Oracle(R) BPEL Process Manager - Version: 10.1.3.1

Symptoms
Use of file adapter that references transformation that uses a schema that includes a xsd:date type.

recieving the following error at runtime:

ORABPEL-11017
Translation Error.
Error while translating message to native format.
Cause
Incorrect xml default date format is causing the problem.

The write processThe xsd:date element is expecting
the value for the date type ojbect to be represented in the default
schema date representation format (a text representation like "2000-03-21" or
format "YYYY-MM-DD").

Solution
Change the format date values as follows:

From "MM-DD-YYYY" to "YYYY-MM-DD"

Example:

From sampleoutput.txt:

RH, 1647, 11-07-2006, Test6 Desc DAVE, Test6 Blah DAVE
RL, 1647, 1234, Line Desc, Line Blah, 10, 123.34, 1324.32
RH, 1648, 11-07-2006, Test Desc2, Test Blah
RL, 1648, 1235, Line Desc2, Line Blah , 11, 123.35, 1324.33

to: (From sampleoutput.txt)

RH, 1647,2006-03-21, Test6 Desc DAVE, Test6 Blah DAVE
RL, 1647, 1234, Line Desc, Line Blah, 10, 123.34, 1324.32
RH, 1648,2006-03-21, Test Desc2, Test Blah
RL, 1648, 1235, Line Desc2, Line Blah, 11, 123.35, 1324.33

Here are some options:

1) Change the format of the date values in the source or
db select statement, if applicable.

2) Read/write the values as string types and do any date transformations/arithmetic via other extraneous variables.

3) Research xml schema/transformation functions that could be integrated to
do the string->date conversion for you.

Database Adapter does not recognize Timestamp column

2007-08-12T05:46:00.000-07:00

Oracle(R) BPEL Process Manager - Version: 10.1.2.0.2

Symptoms
BPEL database wizard shows an error at the Select Table view:

Some tables contain columns that are not recognized by the Database Adapter,
so they will be captured as Strings:

My_timestamp (TIMESTAMP(9))

To fix this problem, cancel this wizard, edit the Offline Table definition to
change the type of the above columns to that of the closest supported type, and
run the Database Adapter wizard again. Please consult the Database Adapter
documentation for detailed instructions on how to fix this problem.

Cause
Database adapter does not recognize column of Timestamp type

Solution
In the toplink_mappings.xml manually change attribute-classification

from 'java.lang.String'

to 'java.sql.Timestamp'

Description of Logger Name Parameters in the BPEL Console

2007-08-12T05:45:00.000-07:00

Description of Logger Name Parameters in the BPEL Console

Parameter	Description
default.collaxa.cube	general logger for BPEL platform
default.collaxa.cube.activation	activation agents (i.e. inbound adapters)
default.collaxa.cube.bpeltest	BPEL unit testing
default.collaxa.cube.compiler	BPEL compiler responsible for the server-side compilation of BPEL processes on deployment
default.collaxa.cube.console.reports	-
default.collaxa.cube.engine	general logger for the BPEL engine, mainly for functionality that is cross-module
default.collaxa.cube.engine.agents	internal agent framework, e.g. expiration agents
default.collaxa.cube.engine.archive	archiving in pre-10.1.3 versions (Archiving is not supported in 10.1.3)
default.collaxa.cube.engine.bpel	logging for BPEL processes. If enabled, each executed BPEL activity will log messages
default.collaxa.cube.engine.data	persistence/dehydration layer
default.collaxa.cube.engine.delivery	invocation/callback handling layer
default.collaxa.cube.engine.deployment	deployment of BPEL suitcases
default.collaxa.cube.engine.dispatch	asynchronous message processing
default.collaxa.cube.engine.transaction	not used in 10.1.3
default.collaxa.cube.messaging	mail processing activities
default.collaxa.cube.security	message header authentication layer
default.collaxa.cube.sensor	sensor publishing layer
default.collaxa.cube.services	workflow service component
default.collaxa.cube.translation	adapter translation layer. The transformation between adapter protocol and inbound XML documents
default.collaxa.cube.ws	web-service layer, inbound and outbound
default.collaxa.cube.xml	XML processing, XPath and XML documents (BPEL variables)
default.oracle.bpel.security	-

FILES TO UPLOAD FOR ISSUES RELATED TO BPEL PROCESS DEPLOYMENT

2007-08-12T05:42:00.000-07:00

Oracle(R) BPEL Process Manager - Version: 10.1.2.0.0 to 10.13.1

Goal
This document guides the customer in uploading all the files and information required to troubleshoot an issue related to BPEL Process Deployment.

Solution
1. Turn the log level to debug from BPEL console by referring Note 373930.1
2. Stop the server & clear the directory:
3. BPEL versions 10.1.2.0.2 or 10.1.2.0.0
* ORACLE_HOME/integration/orabpel/domains//logs
4. BPEL version is 10.1.3.x :
* ORACLE_HOME/bpel/domains//logs
5. Restart the server & reproduce the issue.
6. Please run RDA with option (on the instance where the BPEL is running)
1. Is Oracle Web Applications (OAS, WAS, iAS, AS) information requested? Yes
2. Is J2EE/OC4J in use? Yes
7. Upload the RDA outputs to the SR.
8. If Deploying manually using ANT, upload build.xml and build.properties
9. The BPEL Process(JDeveloper Project) which causes this issue.

RDA NOTES
Note 314422.1 - Remote Diagnostic Agent (RDA) 4 - Overview and User Guide
Note 359395.1 - Remote Diagnostic Agent (RDA) 4 - RAC Cluster Guide

BPEL Application Spawns Numerous Database Connections Causing It To Crash

2007-08-12T05:38:00.000-07:00

Oracle(R) BPEL Process Manager - Version: 10.1.2.0.2

Symptoms
You are running Oracle BPEL application connected to Oracle Databases. There is a poller, which poll the DB for requests inserted by your request engine, these pollers then fire the relevant BPEL process for each request.

During runtime, your application started spawning database connections within minutes, causing it to crash. There are no error messages written into any log file.

Cause
All the concurrent active sessions and the sessions being spawned are waiting on the same resource and throwing the same DB error : ORA-04021: Timeout Occurred While Waiting To Lock Object.

This is a known BPEL PM bug

Bug 5001394 - BYTE OFF MAKES BPEL HANG ON AUDIT_TRAIL, AUD TABLE LOCK & CALLBACK MESG LOST
.
Bug 5001394 - BYTE OFF MAKES BPEL HANG ON AUDIT_TRAIL, AUD TABLE LOCK & CALLBACK MESG LOST
.
Solution
To implement the solution, please execute the following steps:

Apply patch for Bug 5001394. Run the test again

References
Bug 5001394 - 1- BYTE OFF MAKES BPEL HANG ON AUDIT_TRAIL, AUD TABLE LOCK & CALLBACK MESG LOST
Errors
ORA-4021 time-out occurred while waiting to lock object

BPEL Process Version 1.0 Is Set As Default Prior To Latest Versions Deployed

2007-08-12T05:36:00.000-07:00

Oracle(R) BPEL Process Manager - Version: 10.1.3.1

Symptoms
You are deploying version 2.0 of a BPEL Process, and marking this version as default in the BPEL Console. When you call the application version 1.0 of the application is called by default despite your default setting. If you put the old version to Retired and Off to make sure it will not be called, then neither version 1.0 nor version 2.0 is called.

Cause
The latest loaded revision of a process was set as default instead of setting the default version, based on the information from the database

Bug 5837566 SUB PROCESS VERSION ONE GETS FAULTED PRIOR TO VERSION TWO

Solution

To implement the solution, please execute the following steps:

1. If no other patch is installed on the system, apply patch for Bug 5837566
2. If there are any other patches applied either
- Apply the fix for Bug 5837566 if it does not conflict with any other patches already applied
OR
- Apply 10.1.3.3 patch when it becomes available

Why BPEL process instances may appear on the Manual Recovery List

2007-08-12T05:32:00.000-07:00

Applies to:
Oracle(R) BPEL Process Manager - Version: 10.1.2 to 10.1.3.1

Solution
Messages appearing on the Recovery Console happen for a number of reasons, namely;

BPEL has a Delivery Service that intercepts the incoming messages. Once it intercepts an incoming message, the delivery service does two things: 1) Put a very short JMS message to the in-memory queue . The small JMS message will trigger work further downstream of the process. 2) Save the BPEL message to tables at the dehydration store.

In the same thread the BPEL engine instantiate or continue the BPEL instance. By the time the engine finishes processing this message (i.e. hits the end of the process, or hits the first dehydration point) the engine will update the message tables to mark the message as "HANDLED".

The Recovery page shows those invoke or callback messages that are NOT in the HANDLED state. If you click fast enough, you will see messages come and go on the Recovery page. So seeing messages at the Recovery page does not necessarily mean there are problems, unless ...

Unless they stay there permanently. They stay there permanently because there are no more JMS messages to trigger the WorkerBean to process those un-handled BPEL messages in invoke_message or dlv_message tables. Derived from this, these are the scenarios that could cause the BPEL messages stay at UNRESOLVED states:

* The server shuts down or crash before it finish processing the BPEL message. When the server re-started again, the in-memory JMS message associated with the invoke or call back message is already is already gone.
* The engine could not finish processing the message before reaching the time-out as dictated by the transaction-time out specified in the server.xml. In such case it rolls back the message to the message table. But the JMS message associated with the invoke messages are already consumed.

In these cases, no more events (i.e. JMS messages) to trigger the engine to process the BPEL messages in invoke_message or dlv_message tables. Therefore a manual recovery is performed.

References
Bug 4859293 - REQUEST AN AUTOMATED RECOVERY ACTIVITY INTO BPEL CODE FOR FAILED PROCESSES

BPEL Workflow:Notification does not send message in e-mail body, instead sends as attachments

2007-08-12T05:31:00.000-07:00

Oracle(R) BPEL Process Manager - Version: 10.1.3.1.0

Symptoms
when configuring the Notification Settings in an Oracle BPEL Workflow to notify participants by email, the message content appears in the email attachment leaving the email body blank. This is in contrary to the expected behavior where the message content will appear in the email body.

Cause
Bug 5898695

When an Oracle Workflow notification email is viewed via Microsoft Outlook, only the email header is seen and not the body. This situation usually occurs when the using Microsoft Exchange as the email server and Microsoft Outlook as the email client.

Solution
1. Download and review the readme and pre-requisites for Patch 5898695

2. Ensure that a backup of the system is made before applying the patch.

3. Apply the patch in a test environment.

4. Retest the issue.

5. Migrate the solution as appropriate to other environments.

BPEL Engine Exceptions ORABPEL 02000 - 02179

2007-08-12T05:29:00.000-07:00

BPEL Engine Exceptions ORABPEL 02000 - 02179
Engine Exceptions 02000 - 02179

ORABPEL-02000
severity: 10
type: error
name: Block element class not valid
description: The class \"{0}\" for the block element \"{1}\" does not implement the ICubeBlock interface. All block elements contained within the process domain must implement this interface.

ORABPEL-02001
severity: 10
type: error
name: Error while creating block element
description: An error has occurred while attempting to instantiate the class \"{1}\" for the block element \"{0}\". The exception reported was: {2}

ORABPEL-02002
severity: 10
type: error
name: Unknown block element classname
description: The block element \"{0}\" is missing its classname; this element cannot be created without its classname.

ORABPEL-02003
severity: 10
type: error
name: Cube element missing id property
description: A Cube element is missing its \"id\" property. Every Cube element in the process domain is uniquely identified by its \"id\" property.

ORABPEL-02004
severity: 10
type: error
name: SOAP router URL not specified
description: The SOAP server URL for the process domain has not been specified. This URL is used to construct the callback URL that remote web-services will use to callback the domain. This property is expected to be specified in the process domain descriptor file.
fix: Please ensure that the \"soap-server-url\" property is specified in the process domain descriptor file.

ORABPEL-02005
severity: 10
type: error
name: Parent block element not found
description: The parent block element \"{0}\" specified by node/block element \"{1}\" has not been defined in the service class map. All nodes/blocks contained in the map must be bound to a valid parent block element.

ORABPEL-02006
severity: 10
type: error
name: Map element missing parent block
description: The node/block element \"{0}\" is missing a parent block identifier. All nodes/blocks contained in the service class map must be bound to a parent block element.

ORABPEL-02007
severity: 10
type: error
name: Multiple method blocks specified
description: Multiple method block elements have been specified in the service class map. A valid map can only contain one method block element.

ORABPEL-02008
severity: 10
type: error
name: No block elements specified in map
description: No block elements have been specified in the service class map. All valid maps must contain at least one block element (the root block).

ORABPEL-02009
severity: 10
type: error
name: No node elements specified in map
description: No node elements have been specified in the service class map. All valid maps must contain at least one node element.
fix: Please add a node element to the map using the studio tool. Once this has been done, please redeploy the service class.

ORABPEL-02010
severity: 10
type: error
name: No method block specified in map
description: No method block element has been specified for the service class map. All valid maps must contain one method block element.

ORABPEL-02011
severity: 10
type: error
name: Node element class not valid
description: The class \"{0}\" for the node element \"{1}\" does not implement the ICubeNode interface. All node elements contained within the process domain must implement this interface.

ORABPEL-02012
severity: 10
type: error
name: Error while creating node element
description: An error has occurred while attempting to instantiate the class \"{1}\" for the node element \"{0}\". The exception reported was: {2}

ORABPEL-02013
severity: 10
type: error
name: Class not found
description: The class \"{0}\" cannot be found in the current classpath.
fix: If \"{0}\" is a business document, please try to recompile the class using the schemac tool and restart the server.

ORABPEL-02014
severity: 10
type: error
name: Unknown node element classname
description: The node element \"{0}\" is missing its classname; this element cannot be created without its classname.

ORABPEL-02015
severity: 10
type: error
name: Incompatible process version
description: The BPEL process \"{0}\" (revision \"{1}\") has been compiled with an older version of BPELC; the BPEL process domain you have deployed the process to cannot execute this process.
fix: Please recompile your BPEL process using the BPELC tool bundled with the current process domain.

ORABPEL-02016
severity: 10
type: error
name: Failed to initialize process
description: The process \"{0}\" has failed to initialize because of the error: \"{1}\".

ORABPEL-02017
severity: 10
type: error
name: Cannot compress data stream
description: Cannot compress data stream with GZIP algorithm; exception is {0}

ORABPEL-02018
severity: 10
type: error
name: Cannot uncompress data stream
description: Cannot uncompress data stream with GZIP algorithm; exception is {0}

ORABPEL-02019
severity: 10
type: error
name: Cannot compute md5 checksum
description: Cannot compute md5 checksum; exception is {0}

ORABPEL-02020
severity: 10
type: error
name: Cannot serialize audit trail
description: An attempt to serialize the audit trail for instance \"{0}\" to its binary representation has failed. The exception reported is: {1}

ORABPEL-02021
severity: 10
type: error
name: Cannot marshall transaction trail
description: An attempt to marshall the audit trail for instance \"{0}\" to its XML representation has failed. The exception reported is: {1}

ORABPEL-02022
severity: 10
type: error
name: Audit trail element format error
description: The value \"{0}\" for the tag \"{1}\" in the XML serialized text for the audit trail for instance \"{2}\" is not a parseable integral value.
fix: Please ensure that the value for tag \"{1}\" conforms to the expected format.

ORABPEL-02023
severity: 10
type: error
name: Cannot activate block
description: An attempt to activate the block \"{0}\" for the instance \"{1}\" has failed. The exception reported is: {2}
fix: If this block has been custom coded for this process, please check the implementation.

ORABPEL-02024
severity: 10
type: error
name: Cannot finalize block
description: An attempt to invoke the method \"until\" on the block \"{0}\" for the instance \"{1}\" has failed. The exception reported is: {2}
fix: If this block has been custom coded for this process, please check the implementation.

ORABPEL-02025
severity: 10
type: error
name: Block cannot handle exception
description: An attempt by the block \"{0}\" to handle a business exception for the instance \"{1}\" has failed. The exception reported is: {2}
fix: If this block has been custom coded for this process, please check the implementation.

ORABPEL-02026
severity: 10
type: error
name: Cannot pre-activate block
description: An attempt to invoke the method \"canActivate\" on the block \"{0}\" for the instance \"{1}\" has failed. The exception reported is: {2}
fix: If this block has been custom coded for this process, please check the implementation.

ORABPEL-02027
severity: 10
type: error
name: Instance binary deserialization failed
description: An attempt to deserialize the instance \"{0}\" from binary format failed. The exception reported is: {1}

ORABPEL-02028
severity: 10
type: error
name: Instance binary serialization failed
description: An attempt to serialize the instance \"{0}\" to binary format failed. The exception reported is: {1}

ORABPEL-02029
severity: 10
type: error
name: Cannot create key generator bean
description: The process domain cannot create the bean \"{0}\"; this bean is responsible for generating a unique key for a new instance. The exception reported is: \"{1}\".
fix: Please check that the instance key generator bean has been properly deployed to the server and can be properly mounted from a java class.

ORABPEL-02030
severity: 10
type: error
name: Cannot marshall instance
description: An attempt to marshall the instance \"{0}\" to XML format has failed. The exception reported is: {1}

ORABPEL-02031
severity: 10
type: error
name: Wrong domain id
description: The instance \"{0}\" was created from the domain \"{1}\"; the current domain is \"{2}\". A process can only be loaded from the domain it was created from.
fix: If you are accessing this instance from the API, please try looking up the instance \"{0}\" from the \"{1}\" domain (change the domain id parameter to the Locator initializer).

ORABPEL-02032
severity: 10
type: error
name: Inconsistent process guid
description: The instance \"{0}\" was created with process guid \"{1}\"; the current guid for the process \"{2}\" (revision \"{3}\") is \"{4}\". Whenever a process is deployed on top of an existing process with the same process id and revision tag, all instances created from the previous process are marked as stale.
fix: If you are accessing this instance from the console, your browser may be referring to an out-of-date page; please click on the Instances tab to get the current list of active instances.

ORABPEL-02033
severity: 10
type: error
name: Invalid instance key format
description: An attempt to construct a valid instance key from the string \"{0}\" has failed. The key consists of a single integer value. The exception reported is: {2}
fix: If the instance key string has not been constructed by the process domain, please ensure that the key format is valid.

ORABPEL-02034
severity: 10
type: error
name: Instance missing XML entry
description: The tag \"{0}\" is missing from the XML serialized text for instance \"{1}\".
fix: Please ensure that the XML document for this instance contains a value for the tag \"{0}\".

ORABPEL-02035
severity: 10
type: error
name: Instance missing process id
description: The instance \"{0}\" is missing its process id; this id specifies the process class that the instance was generated from.

ORABPEL-02036
severity: 10
type: error
name: Instance element format error
description: The value \"{0}\" for the tag \"{1}\" in the XML serialized text for instance \"{2}\" is not a parseable integral value.
fix: Please ensure that the value for tag \"{1}\" conforms to the expected format.

ORABPEL-02037
severity: 10
type: error
name: Cannot create context object
description: An exception occurred while trying to create a context object; the exception reported is: {0}
fix: Please verify that the directory service on the application server has been configured correctly.

ORABPEL-02038
severity: 10
type: error
name: Cannot lookup context object
description: The process domain was unable to lookup the context object using the bind name \"{0}\". The exception reported is: {1}
fix: Please verify the JNDI identifier is valid.

ORABPEL-02039
severity: 10
type: error
name: Cannot delegate lookup to process
description: The process domain was unable to delegate the lookup call for \"{0}\" to the process descriptor. The descriptor cannot be found for this process.

ORABPEL-02040
severity: 10
type: error
name: Cannot destroy context object
description: An exception occurred while trying to destroy a context object; the exception reported is: {0}
fix: Please verify that the directory service on the application server has been configured correctly.

ORABPEL-02041
severity: 5
type: error
name: Cannot access instance
description: The action \"{0}\" cannot be performed on the instance \"{1}\" because of its current state (\"{2}\"). Please consult the documentation for a list of all the permissible actions that can be performed on a instance when it is in the \"{2}\" state.

ORABPEL-02042
severity: 5
type: error
name: Cannot access work item
description: The action \"{0}\" cannot be performed on the work item \"{1}\" because of its current state (\"{2}\"). Please consult the documentation for a list of all the permissible actions that can be performed on a work item when it in the \"{2}\" state.

ORABPEL-02043
severity: 5
type: error
name: Cannot access Scope
description: The action \"{0}\" cannot be performed on the scope \"{1}\" because of its current state (\"{2}\"). Please consult the documentation for a list of all the permissible actions that can be performed on a scope when it in the \"{2}\" state.

ORABPEL-02044
severity: 5
type: error
name: Cannot write audit trail
description: The process domain failed to write the audit trail for instance \"{0}\". The exception reported is: {1}

ORABPEL-02045
severity: 5
type: error
name: Cannot read debug trace
description: The process domain failed to read the debug trace for instance \"{0}\". The exception reported is: {1}

ORABPEL-02046
severity: 5
type: error
name: Cannot write debug trace
description: The process domain failed to write the debug trace for instance \"{0}\". The exception reported is: {1}

ORABPEL-02047
severity: 5
type: error
name: Cannot write instance trace
description: The process domain failed to write the instance trace for instance \"{0}\". The exception reported is: {1}

ORABPEL-02048
severity: 5
type: error
name: Cannot handle work item
description: The process domain was unable to handle the work item \"{0}\". The exception reported is: {1}

ORABPEL-02049
severity: 5
type: error
name: Cannot begin a transaction
description: The OraBPEL system was unable to start a new transaction for method \"{0}\". The exception reported is: {1}

ORABPEL-02050
severity: 10
type: error
name: Request cancelled
description: The invocation for method \"{0}\" on the business transaction \"{1}\", process bean \"{2}\" (revision \"{3}\") has been cancelled. The return value for this method cannot be determined in this case.

ORABPEL-02051
severity: 10
type: error
name: Request not finished
description: The invocation for method \"{0}\" on the business transaction \"{1}\", process bean \"{2}\" (revision \"{3}\") is not complete. The return value for this method cannot be fetched until the method has completed.
fix: Please resubmit this request after several minutes. Please note that the method may contain some asynchronous conversations that could take an indeterminate amount of time to complete.

ORABPEL-02052
severity: 10
type: error
name: Cannot lookup BPEL domain
description: The BPEL domain \"{0}\" cannot be found; the domain may not have initialized properly.
fix: Please verify that the BPEL domain loader has a valid set of initialization properties in the application properties file.

ORABPEL-02053
severity: 10
type: error
name: BPEL domain not initialized
description: The BPEL domain \"{0}\" has not finished initializing yet; the initialization process may be complete in a few moments.

ORABPEL-02054
severity: 10
type: error
name: BPEL domain uninitializing
description: The BPEL domain \"{0}\" is currently uninitializing; the domain may not be accessed anymore.

ORABPEL-02055
severity: 10
type: error
name: Exception not handled
description: An exception thrown from a scope was not handled by any blocks up the scope chain.

ORABPEL-02056
severity: 10
type: error
name: Could not initialize JMS resources
description: An exception thrown while initializing JMS destination \"{0}\", the reason is {1}
fix: Please check your jms server configuration and make sure that you have configured the \"{0}\" destination and make sure that your JMS server is up and running.

ORABPEL-02057
severity: 5
type: error
name: Block element not found in map
description: The block element \"{0}\" has not been defined in the service class map.
fix: If any user specified code is attempting to access the block element \"{0}\", please check the name of the requested element.

ORABPEL-02058
severity: 5
type: error
name: Node element not found in map
description: The node element \"{0}\" has not been defined in the service class map.
fix: If any user specified code is attempting to access the node element \"{0}\", please check the name of the requested element.

ORABPEL-02059
severity: 10
type: error
name: Work item not found in memory repository
description: The process domain was unable to fetch the work item \"{0}\" from the memory repository.
fix: Please check that the work item key \"{0}\" refers to a valid work item that has been started and not removed from the process domain.

ORABPEL-02060
severity: 10
type: error
name: Cannot activate node
description: An attempt to activate the node \"{0}\" for the instance \"{1}\" has failed. The exception reported is: {2}
fix: If this node has been custom coded for this process, please check the implementation.

ORABPEL-02061
severity: 10
type: error
name: Cannot finalize node
description: An attempt to finalize the node \"{0}\" for the work item \"{1}\" has failed. The exception reported is: {2}
fix: If this node has been custom coded for this process, please check the implementation.

ORABPEL-02062
severity: 10
type: error
name: Cannot pre-activate node
description: An attempt to invoke the method \"canActivate\" on the node \"{0}\" for the instance \"{1}\" has failed. The exception reported is: {2}
fix: If this node has been custom coded for this process, please check the implementation.

ORABPEL-02063
severity: 10
type: error
name: Delivery callback message deserialization failed
description: An attempt to deserialize the delivery callback messages for conversation \"{0}\", message \"{1}\" from binary format has failed. The exception reported is: {2}

ORABPEL-02064
severity: 10
type: error
name: Delivery callback message serialization failed
description: An attempt to serialize the delivery callback messages for conversation \"{0}\", message \"{1}\" to binary format has failed. The exception reported is: {2}

ORABPEL-02065
severity: 10
type: error
name: Delivery property serialization failed
description: An attempt to serialize the delivery properties for conversation \"{0}\" to binary format has failed. The exception reported is: {1}

ORABPEL-02066
severity: 10
type: error
name: Delivery property deserialization failed
description: An attempt to deserialize the delivery properties for conversation \"{0}\" to binary format has failed. The exception reported is: {1}

ORABPEL-02067
severity: 10
type: error
name: Delivery callback message XML marshalling failed
description: An attempt to marshall the delivery callback messages for conversation \"{0}\", message \"{1}\" to XML has failed. The exception reported is: {2}

ORABPEL-02068
severity: 10
type: error
name: Operation not supported
description: The method call to \"{0}\" of delivery system persistence service has failed. The object passed in is \"{1}\". This operation is not supported.
fix: Delivery service persistence service does not support advanced persistence features like lazy-loading. The persistence manager should not use those related operations. Check the persistence manager of the object.

ORABPEL-02069
severity: 10
type: error
name: Cannot load message from object store
description: The delivery service can not load the message contents from the datastore. The exception reported is: {0}
fix: If this object type has been imported into the process, please check that the load() method is working properly. The load() call is the object''s opportunity to recreate itself from external storage. Otherwise, the delivery message contents may have been edited manually in the datastore.

ORABPEL-02070
severity: 10
type: error
name: Cannot save message to object store
description: The delivery service cannot store the object \"{0}\" (type \"{1}\") to the datastore. The exception reported is: {2}
fix: If this object type has been imported into the process, please check that the save() method is working properly. The save() call is the object''s opportunity to persist itself in some form of external storage.

ORABPEL-02071
severity: 10
type: error
name: Cannot copy object
description: An attempt to copy the object \"{0}\" (class {1}) has failed. The exception reported is: {2}
fix: If this object type has been imported into the process, please check that the copy() method of this object''s PersistenceManager is working properly.

ORABPEL-02072
severity: 10
type: error
name: Cannot release moniker
description: An attempt to release the moniker \"{0}\" has failed. The exception reported is: {1}
fix: If the last reference to a moniker is being removed, the object referred to by the moniker must be loaded first. Please check that the load() method in the object''s persistence manager is working correctly.

ORABPEL-02073
severity: 10
type: error
name: Cannot delete object
description: An attempt to delete the object \"{0}\" (class {1}) has failed. The exception reported is: {2}
fix: If this object type has been imported into the process, please check that the delete() method is working properly. The delete() call is the object''s opportunity to remove any external persisted version of itself.

ORABPEL-02074
severity: 10
type: error
name: Cannot find target element
description: The target element with id \"{0}\" cannot be located in the current XML document. The node \"{1}\" has a reference link to this element.
fix: The document is corrupt; it may have been edited manually.

ORABPEL-02075
severity: 10
type: error
name: Cannot find element type
description: The element \"{0}\" does not have an \"xsi:type\" attribute specifying schema type of the underlying java object. An XML fragment cannot be properly unmarshalled to its java representation without this information.
fix: The document is corrupt; it may have been edited manually.

ORABPEL-02076
severity: 10
type: error
name: Cannot load object from moniker
description: An attempt to deserialize an object from its moniker format has failed. The exception reported is: {0}
fix: The object moniker is corrupt; the moniker may have been edited manually.

ORABPEL-02077
severity: 10
type: error
name: Negative reference count
description: Assertion failed: object \"{0}\" has negative reference count \"{1}\".

ORABPEL-02078
severity: 10
type: error
name: Cannot marshall object
description: An attempt to marshall the object \"{0}\" (class \"{1}\") to XML has failed. The exception reported is: {2}
fix: If this object type has been imported into the process, please check that the marshall() method is working properly. Otherwise, the document may have been edited manually.

ORABPEL-02079
severity: 10
type: error
name: Cannot prepare to marshall object
description: An attempt to prepare the object \"{0}\" (class \"{1}\") for marshalling has failed. The exception reported is: {2}
fix: If this object type has been imported into the process, please check that the prepareToMarshall() method is working properly. Otherwise, the document may have been edited manually.

ORABPEL-02080
severity: 10
type: error
name: Cannot prepare to save object
description: An attempt to \"prepare to save\" the object \"{0}\" (class {1}) has failed. The exception reported is: {2}
fix: If this object type has been imported into the process, please check that the prepareToSave() method is working properly. The prepareToSave() call is meant for compound objects to prepare their inner objects for saving.

ORABPEL-02081
severity: 10
type: error
name: Cannot read moniker
description: An attempt to read an object''s moniker from the deserializer stream has failed. The exception reported is: {0}
fix: The object moniker is corrupt; the moniker may have been edited manually.

ORABPEL-02082
severity: 10
type: error
name: Cannot save object
description: An attempt to save the object \"{0}\" (class {1}) has failed. The exception reported is: {2}
fix: If this object type has been imported into the process, please check that the save() method is working properly. The save() call is the object''s opportunity to persist itself in some form of external storage.

ORABPEL-02083
severity: 10
type: error
name: Cannot unmarshall object
description: An attempt to unmarshall the object \"{0}\" (element type \"{1}\") from XML has failed. The exception reported is: {2}
fix: If this object type has been imported into the process, please check that the unmarshall() method is working properly. Otherwise, the document may have been edited manually.

ORABPEL-02084
severity: 10
type: error
name: Cannot write moniker
description: An attempt to write an object''s moniker into the serializer stream has failed. The exception reported is: {0}

ORABPEL-02085
severity: 10
type: error
name: Metadata for object not found
description: The metadata for object \"{0}\" has not been registered with the persistence service. Every java object type in the scope must be registered.

ORABPEL-02086
severity: 10
type: error
name: Missing embedded moniker
description: The metadata for object \"{0}\" does not contain an embedded moniker. All linked variants in the scope must contain an embedded moniker that contains the actual bytes defining the object.

ORABPEL-02087
severity: 10
type: error
name: Missing reference identifier
description: The node \"{0}\" is missing its reference identifier. Any element with an \"href\" attribute must contain a non-empty reference id that can be resolved to another element in the document.
fix: The document is corrupt; it may have been edited manually.

ORABPEL-02088
severity: 10
type: error
name: Cannot route root scope
description: A instance''s root scope cannot be routed.

ORABPEL-02089
severity: 10
type: error
name: Invalid scope activation key format
description: An attempt to construct a valid scope activation key from the string \"{0}\" has failed. The expected format is: \"parm1-parm2\", where the parameters are: instance id (integer) and scope id (string) respectively.
fix: If the scope activation key string has not been constructed by the process domain, please ensure that the key format is valid.

ORABPEL-02090
severity: 10
type: error
name: Cannot unmarshall meta data
description: An error occurred while attempting to unmarshall the meta data for the scope tree for instance \"{0}\". The exception reported is: {1}
fix: A variant''s meta data should contain a \"guid\", \"classname\" and \"ref-count\" attributes; the \"ref-count\" attribute should be an integral value.

ORABPEL-02091
severity: 10
type: error
name: Cannot release root scope
description: A instance''s root scope cannot be released from the scope tree.

ORABPEL-02092
severity: 10
type: error
name: Cannot unmarshall scope
description: An attempt to unmarshall a scope for instance \"{0}\" from an XML document has failed. The exception reported is: {1}
fix: The XML document for the scope may have been modified by hand.

ORABPEL-02093
severity: 10
type: error
name: Scope context missing XML entry
description: The tag \"{0}\" is missing from the XML serialized text for the scope data for instance \"{1}\".
fix: Please ensure that the XML document for this instance contains a value for the tag \"{0}\".

ORABPEL-02094
severity: 10
type: error
name: Scope not found
description: The scope \"{0}\" has not been defined in the current instance.

ORABPEL-02095
severity: 10
type: error
name: Cannot resolve scope
description: The scope associated with block element \"{0}\" has not been defined in the current instance.

ORABPEL-02096
severity: 10
type: error
name: Instance element format error
description: The value \"{0}\" for the tag/attribute \"{1}\" in the XML serialized text for instance \"{2}\" is not a parseable integral value.
fix: Please ensure that the value for tag \"{1}\" conforms to the expected format.

ORABPEL-02097
severity: 5
type: error
name: Cannot read process XML model file
description: Cannot read the XML model file for process \"{0}\" (revision \"{1}\"); the exception reported is: {2}
fix: Please check that the BPEL archive for process \"{0}\" (revision \"{1}\") has been deployed correctly.

ORABPEL-02098
severity: 5
type: error
name: Process WSDL not found
description: Cannot find the WSDL file \"{0}\" for process \"{1}\" (revision \"{2}\").
fix: Please check that the BPEL archive for process \"{1}\" (revision \"{2}\") has been deployed correctly.

ORABPEL-02099
severity: 5
type: error
name: Cannot read process WSDL file
description: Cannot read the WSDL file \"{0}\" for process \"{1}\" (revision \"{2}\"); the exception reported is: {3}
fix: Please check that the BPEL archive for process \"{1}\" (revision \"{2}\") has been deployed correctly.

ORABPEL-02100
severity: 5
type: error
name: Cannot find process content file
description: Cannot find the content file \"{0}\" for process \"{1}\" (revision \"{2}\").
fix: Please check that the path \"{0}\" is correct and refers to a file that has been included as a part of the deployment archive.

ORABPEL-02101
severity: 5
type: error
name: Cannot read process content file
description: Cannot read the content file \"{0}\" for process \"{1}\" (revision \"{2}\"); the exception reported is: {3}
fix: Please check that the path \"{0}\" is correct and refers to a file that has been included as a part of the deployment archive.

ORABPEL-02102
severity: 5
type: error
name: Invalid Method Name.
description: Method \"{0}\" not found.

ORABPEL-02103
severity: 10
type: error
name: Process method map not found
description: The map for node element \"{0}\" has not been defined in the process class.

ORABPEL-02104
severity: 5
type: error
name: Process mode closed
description: The process class \"{0}\" (revision \"{1}\") is not in an open mode. New instances may not be created when the process is not open; existing instances are permitted to complete normally.
fix: Only the active revision of a process class (that is, the most recently deployed) may be open; all other revisions are automatically closed.

ORABPEL-02105
severity: 5
type: error
name: No process id found
description: A process class has not been assigned a unique identifier. This situation can occur if the process info class has not been properly bound to the process class.

ORABPEL-02106
severity: 5
type: error
name: Process state off
description: The process class \"{0}\" (revision \"{1}\" ) has not been turned on. No operations on the process or any instances belonging to the process may be performed if the process is off.
fix: Please consult your administrator if this process has been turned off inadvertently.

ORABPEL-02107
severity: 10
type: error
name: Scope activation message not found
description: The process domain was unable to fetch the scope activation message with key \"{0}\" from the datasource.
fix: This row may have been manually removed from the datasource; in which case the instance should be aborted.

ORABPEL-02108
severity: 10
type: error
name: Cannot copy scope
description: An attempt was made to create a copy of the scope \"{0}\". Scopes are not cloneable.

ORABPEL-02109
severity: 10
type: error
name: Cannot deserialize scope data
description: The process domain was unable to deserialize the scope data for instance \"{0}\" from its binary byte representation. The exception reported is: {1}

ORABPEL-02110
severity: 10
type: error
name: Cannot marshall scope data
description: An attempt to marshall the scope data for instance \"{0}\" into XML has failed. The exception reported is: {1}

ORABPEL-02111
severity: 10
type: error
name: Cannot serialize scope data
description: The process domain was unable to serialize the scope data for instance \"{0}\" into a binary byte stream. The exception reported is: {1}

ORABPEL-02112
severity: 5
type: error
name: Invalid absolute scope id
description: The absolute scope id \"{0}\" does not conform to the expected format for a scope identifier (block id + relative scope id).

ORABPEL-02113
severity: 5
type: error
name: Scope not method scope
description: An attempt was made to fetch a return/header value from the root scope.

ORABPEL-02114
severity: 5
type: error
name: Primitive variant cast error
description: The requested variant \"{0}\" is not a primitive variant type. Reference variants cannot be cast to a primitive type.
fix: Please check that the code accessing variant \"{0}\" assumes that \"{0}\" is a reference variant.

ORABPEL-02115
severity: 5
type: error
name: Reference variant cast error
description: The requested variant \"{0}\" is not a reference variant type. Primitive variants cannot be cast to a reference type.
fix: Please check that the code accessing variant \"{0}\" assumes that \"{0}\" is a primitive variant.

ORABPEL-02116
severity: 5
type: error
name: Unknown variant type
description: The variant object associated with key \"{0}\" in the scope tree is neither a primitive nor a reference variant. The only variant types permissible in the scope tree are primitive (all Java primitive types) and reference (java.lang.String, java.util.Date, OraBPEL documents, EJB entity beans and one-dimensional arrays of any primitive or reference type).
fix: Please check that the type for the declared variant \"{0}\" is contained in this list of supported, (de)serializable types.

ORABPEL-02117
severity: 5
type: error
name: Variable already declared
description: A variable with key \"{0}\" has already been declared in the current scope.
fix: Please remove the variable declaration statement from your code.

ORABPEL-02118
severity: 5
type: error
name: Variant not found
description: The variant \"{0}\" has not been declared in the current scope. All variants must be declared in the scope before being accessed.
fix: Please check that the variant \"{0}\" is properly declared; otherwise there may be a misspelling in the name of the variant.

ORABPEL-02119
severity: 10
type: error
name: Transaction view binary deserialization failed
description: An attempt to deserialize the transaction view for instance \"{0}\" from binary format failed. The exception reported is: {1}

ORABPEL-02120
severity: 10
type: error
name: Transaction view binary serialization failed
description: An attempt to serialize the transaction view for instance \"{0}\" to binary format failed. The exception reported is: {1}

ORABPEL-02121
severity: 5
type: error
name: Cannot marshall type to XML
description: An attempt to marshall the object \"{0}\" (class \"{1}\") to XML has failed. The exception reported is: {2}

ORABPEL-02122
severity: 5
type: error
name: Type missing XML element
description: The type class \"{0}\" is missing a \"{1}\" tag.
fix: Please ensure that the XML fragment for this type contains the necessary tag; this type of error usually occurs when the XML document has been edited manually.

ORABPEL-02123
severity: 5
type: error
name: Element contains wrong format
description: The value \"{0}\" for the tag \"{1}\" in the XML serialized text for the type class \"{2}\" is not a parseable integral value.
fix: Please ensure that the value for tag \"{1}\" conforms to the expected format.

ORABPEL-02124
severity: 10
type: error
name: Workitem binary deserialization failed
description: An attempt to deserialize the workitem \"{0}\" from binary format failed. The exception reported is: {1}

ORABPEL-02125
severity: 10
type: error
name: Workitem binary serialization failed
description: An attempt to serialize the workitem \"{0}\" to binary format failed. The exception reported is: {1}

ORABPEL-02126
severity: 10
type: error
name: Workitem binary deserialization failed
description: An attempt to deserialize the workitems for instance \"{0}\" to binary format failed. The exception reported is: {1}

ORABPEL-02127
severity: 10
type: error
name: Workitem binary serialization failed
description: An attempt to serialize the workitems for instance \"{0}\" to binary format failed. The exception reported is: {1}

ORABPEL-02128
severity: 10
type: error
name: Cannot marshall work item
description: An attempt to marshall the work item \"{0}\" to XML format has failed. The exception reported is: {1}

ORABPEL-02129
severity: 10
type: error
name: Invalid work item key format
description: An attempt to construct a valid work item key from the string \"{0}\" has failed. The expected format is: \"parm1-parm2-parm3-parm4\", where the parameters are: instance id (integer), node id (string), scope id (string) and count id (integer) respectively.
fix: If the work item key string has not been constructed by the process domain, please ensure that the key format is valid.

ORABPEL-02130
severity: 10
type: error
name: Work item missing XML entry
description: The tag \"{0}\" is missing from the XML serialized text for work item \"{1} \".
fix: Please ensure that the XML document for this instance contains a value for the tag \"{0}\".

ORABPEL-02131
severity: 10
type: error
name: Null exception thrown
description: A null exception has been thrown from the activity \"{0}\". Exceptions may not be null.

ORABPEL-02132
severity: 10
type: error
name: Work item element format error
description: The value \"{0}\" for the tag \"{1}\" in the XML serialized text for work item \"{2}\" is not a parseable integral value.
fix: Please ensure that the value for tag \"{1}\" conforms to the expected format.

ORABPEL-02133
severity: 5
type: error
name: Error while expiring work item
description: An error has occurred while attempting to expire the work item \"{0}\" (located at node \"{1}\"). The exception reported was: \"{2}\".
fix: Please check the implementation of the work manager class for any errors in the expiration logic. Otherwise, if this is a system or resource problem, please contact your system administrator.

ORABPEL-02134
severity: 5
type: error
name: Error while extending work item
description: An error has occurred while attempting to extend the work item \"{0}\" (located at node \"{1}\"). The exception reported was: \"{2}\".
fix: Please check the implementation of the work manager class for any errors in the extend logic. Otherwise, if this is a system or resource problem, please contact your system administrator.

ORABPEL-02135
severity: 5
type: error
name: Error while executing manage
description: An error has occurred while attempting to execute the method \"manage\" on the work manager for node \"{0}\". The exception reported was: \"{1}\".

ORABPEL-02136
severity: 5
type: error
name: Error while resuming work item
description: An error has occurred while attempting to resume the work item \"{0}\" (located at node \"{1}\"). The exception reported was: \"{2}\".
fix: Please check the implementation of the work manager class for any errors in the resume logic. Otherwise, if this is a system or resource problem, please contact your system administrator.

ORABPEL-02137
severity: 5
type: error
name: Error while suspending work item
description: An error has occurred while attempting to suspend the work item \"{0}\" (located at node \"{1}\"). The exception reported was: \"{2}\".
fix: Please check the implementation of the work manager class for any errors in the suspend logic. Otherwise, if this is a system or resource problem, please contact your system administrator.

ORABPEL-02138
severity: 10
type: error
name: Invalid callback arguments
description: The method invocation \"{0}\" has returned a invalid number of callback arguments. Currently, a maximum of one return value is permitted from a method invocation; the actual number returned for this invocation was \"{1}\".

ORABPEL-02139
severity: 10
type: error
name: Invalid exception object
description: The method invocation \"{0}\" has thrown an invalid exception object. All thrown exceptions must be objects that extend the class \"Throwable\". The object thrown is of class \"{1}\".

ORABPEL-02140
severity: 10
type: error
name: Callback invocation failed
description: An attempt to invoke the method \"{0}\" on the performer \"{1}\" failed. The reported exception is: \"{2}\".
fix: Please ensure that the signature of the method \"{0}\" is: ( IWorkItem, ICubeContext ).

ORABPEL-02141
severity: 5
type: error
name: Error while cancelling perform
description: An error has occurred while attempting to execute the method \"cancelPerform\" on the work performer for node \"{0}\". The exception reported was: \"{1}\".
fix: Please check the implementation of the work performer class for any errors in the performer logic. Otherwise, if this is a system or resource problem, please contact your system administrator.

ORABPEL-02142
severity: 5
type: error
name: Error while executing perform
description: An error has occurred while attempting to execute the method \"perform\" on the work performer for node \"{0}\". The exception reported was: \"{1}\".
fix: Please check the implementation of the work performer class for any errors in the performer logic. Otherwise, if this is a system or resource problem, please contact your system administrator.

ORABPEL-02143
severity: 5
type: error
name: Error while throwing exception
description: An error has occurred while attempting to throw the exception \"{0}\" from the activity \"{1}\". The exception reported was: \"{2}\".
fix: Please check the implementation of the work performer class for any errors in the performer logic. Otherwise, if this is a system or resource problem, please contact your system administrator.

ORABPEL-02144
severity: 5
type: error
name: Cannot unmarshall array
description: An error occurred while attempting to unmarshall the array element \"{0}\"; an invalid array length was found (\"{1}\") when a valid integer was expected.

ORABPEL-02145
severity: 10
type: error
name: Cannot unrecognized date format
description: An attempt to unmarshall a valid java date from the value \"{0}\" has failed. The accepted formats for valid dates are: {1} or {2}.
fix: Dates that are marshalled by the process domain should conform to the expected format; the document may have been edited manually.

ORABPEL-02146
severity: 5
type: error
name: Cannot unmarshall array
description: An error occurred while attempting to unmarshall the array element \"{0}\"; the array type value \"{1}\" was malformed.

ORABPEL-02147
severity: 5
type: error
name: Cannot unmarshall array
description: An error occurred while attempting to unmarshall the array element \"{0}\"; the array length for type \"{1}\" is missing. The expected type format is: type[ length ] (multi- dimensional assymetric arrays can have format type[][][ length ]).

ORABPEL-02148
severity: 5
type: error
name: Cannot unmarshall array
description: An error occurred while attempting to unmarshall the array element \"{0}\"; multi -dimensional symmetric arrays are not supported.

ORABPEL-02149
severity: 10
type: error
name: Instance missing domain id
description: The instance \"{0}\" is missing its domain id; this id specifies the BPEL domain that the instance was generated from.

ORABPEL-02150
severity: 10
type: error
name: Workitem not found in datasource
description: The process domain was unable to fetch the work item \"{0}\" from the datasource.
fix: Please check that the work item key \"{0}\" refers to a valid work item that has been started and not removed from the process domain.

ORABPEL-02151
severity: 10
type: error
name: Multiple activities found
description: Multiple activities were found with the key \"{0}\" from domain \"{1}\". Only one activity should be returned per key.
fix: If the key is a user-specified custom key, please ensure that the key is unique.

ORABPEL-02152
severity: 10
type: error
name: Instance not found in datasource
description: The process domain was unable to fetch the instance with key \"{0}\" from the datasource.
fix: Please check that the instance key \"{0}\" refers to a valid instance that has been started and not removed from the process domain.

ORABPEL-02153
severity: 10
type: error
name: Synchronous work items not found in datastore
description: The process domain was unable to fetch the work items for the synchronous instance with key \"{0}\" from the datasource.
fix: Please check that the instance key \"{0}\" refers to a valid instance that has been started and not removed from the process domain.

ORABPEL-02154
severity: 10
type: error
name: Multiple instances found
description: Multiple instances were found with the key \"{0}\". Only one instance should be returned per key.
fix: If the key is a user-specified custom key, please ensure that the key is unique.

ORABPEL-02155
severity: 10
type: error
name: Document not found in datasource
description: The process domain was unable to fetch the bytes for the business document \"{0}\" from the datasource.
fix: Please check that the business document identifier \"{0}\" refers to a valid entry in the document table; this row may have been manually removed from the table.

ORABPEL-02156
severity: 10
type: error
name: Instance scope not found in datasource
description: The process domain was unable to fetch the scope context data for the instance with key \"{0}\" from the datasource.
fix: Please check that the instance key \"{0}\" refers to a valid instance that has been started and not removed from the process domain.

ORABPEL-02157
severity: 5
type: error
name: Cannot read audit trail
description: The process domain failed to read the audit trail for instance \"{0}\". The exception reported is: {1}

ORABPEL-02158
severity: 5
type: error
name: Cannot create scope deserializer
description: Failed to create the scope deserializer object for instance \"{0}\". The exception reported is: {1}

ORABPEL-02159
severity: 10
type: error
name: Cannot find invoke message
description: The process domain was unable to fetch the invocation content for the message \"{0}\" from the datastore.
fix: Please check that the message key \"{0}\" refers to a valid invocation message that has been delivered to and not removed from the process domain.

ORABPEL-02160
severity: 10
type: error
name: Cannot find callback message
description: The process domain was unable to fetch the callback content for the message \"{0} \" from the datastore.
fix: Please check that the message key \"{0}\" refers to a valid callback message that has been delivered to and not removed from the process domain.

ORABPEL-02161
severity: 10
type: error
name: Audit details not found in datasource
description: The process domain was unable to fetch the audit detail bytes for the instance \"{0}\", detail id \"{1}\" from the datastore.
fix: Please check that the instance identifier \"{0}\" and/or detail identifier \"{1}\" refers to a valid entry in the audit_details table; this row may have been manually removed from the table.

ORABPEL-02162
severity: 10
type: error
name: Instance index out of range
description: The index \"{0}\" for instance \"{1}\" is out of range; please try a value between 1 and \"{2}\" (inclusive).

ORABPEL-02163
severity: 10
type: error
name: Scope released
description: Cannot access scope \"{0}\"; scope has already been released.

ORABPEL-02164
severity: 10
type: error
name: Unknown cache policy
description: Unknown cache policy \"{0}\" specified for property \"{1}\".

ORABPEL-02165
severity: 10
type: error
name: Could not initialize jms connection pool
description: Could not initialize connection pool for connection factory \"{0}\"; the reason is {1}.

ORABPEL-02166
severity: 10
type: error
name: Cannot finalize compensation node
description: Failed when attempt to finalize the compensation node \"{0}\" for the second time. The exception reported is: {1}
fix: If this node has been custom coded for this process, please check the implementation.

ORABPEL-02167
severity: 10
type: error
name: Missing process for instance
description: The process (\"{1}\", revision \"{2}\") for instance \"{0}\" was not loaded by the domain; the instance will now be marked as stale.
fix: The archive for process \"{1}\", revision \"{2}\" may have been deleted from the domain manually; in this case the domain would not have been able to mark all instances belonging to the process as stale.

ORABPEL-02168
severity: 5
type: error
name: Cannot read sensor file.
description: A problem occurred while reading the sensor file \"{0}\". The exception reported is: {1}
fix: Please ensure the file exists. If it has been manually deleted, please redeploy the process.

ORABPEL-02169
severity: 5
type: error
name: Cannot read sensor action file.
description: A problem occurred while reading the sensor action file \"{0}\". The exception reported is: {1}
fix: Please ensure the file exists. If it has been manually deleted, please redeploy the process.

ORABPEL-02170
severity: 10
type: error
name: Instance missing test information.
description: The BPELTest instance \"{0}\" is missing test information.
fix: If this instance has been modified manually, it may be corrupt. Please launch a new test run.

ORABPEL-02171
severity: 10
type: error
name: Problem updating label status.
description: A problem occurred while updating the label status \"{0}\" in instance \"{1} \".
fix: This label was not detected during process compilation. Please re-deploy the process and try again.

ORABPEL-02172
severity: 10
type: error
name: Message handler element class not valid
description: The class \"{0}\" for the message handler element \"{1}\" does not implement the IMessageHandler interface. All message handlers contained within the process domain must implement this interface.

ORABPEL-02173
severity: 10
type: error
name: Message handler class not found
description: The class \"{0}\" cannot be found in the current classpath.

ORABPEL-02174
severity: 10
type: error
name: Error while creating message handler element
description: An error has occurred while attempting to instantiate the class \"{1}\" for the message handler \"{0}\". The exception reported was: {2}

ORABPEL-02175
severity: 10
type: error
name: Error while invoking inbound message handler
description: An error has occurred while attempting to invoke the inbound message handler class \"{0}\" for the message \"{1}\". The exception reported was: {2}

ORABPEL-02176
severity: 10
type: error
name: Error while invoking outbound message handler
description: An error has occurred while attempting to invoke the outbound message handler class \"{0}\" for the message \"{1}\". The exception reported was: {2}

ORABPEL-02177
severity: 10
type: error
name: Failed to create datasource
description: Failed to create the datasource \"{0}\". The exception reported was: {1}
fix: Please consult your administrator regarding this error. The application server logs may provide more information regarding this error.

ORABPEL-02178
severity: 5
type: error
name: Process not found
description: The BPEL process \"{0}\", revision \"{1}\" has not been loaded. Either the process was not initialized properly or the process has been disabled.
fix: Please consult your administrator regarding this error. The application server logs may provide more information regarding this error.

ORABPEL-02179
severity: 5
type: error
name: Suitcase not found
description: The process domain was unable to find the BPEL suitcase \"{0}\" in the datasource. Either the suitcase was not saved properly or the suitcase table has been altered manually.

BPEL Data Source Exceptions ORABPEL 04000 - 04142

2007-08-12T05:28:00.002-07:00

BPEL Data Source Exceptions ORABPEL 04000 - 04142
Data Source Exceptions 04000 - 04142

ORABPEL-04000
severity: 10
type: error
name: Cannot count instances
description: The process domain was unable to count the number of instances. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04001
severity: 10
type: error
name: Cannot count instances
description: The process domain was unable to count the number of instances for the process \"{0}\" (revision \"{1}\"). The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04002
severity: 10
type: error
name: Cannot find instances
description: An attempt to fetch the instances using the where condition \"{0}\" from the datastore has failed. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04003
severity: 10
type: error
name: Cannot find work items
description: An attempt to fetch the work items using the where condition \"{0}\" from the datastore has failed. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04004
severity: 10
type: error
name: Cannot insert audit trail
description: The process domain was unable to insert the current log entries for the instance \"{0}\" to the audit trail table. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04005
severity: 10
type: error
name: Cannot insert audit details
description: The process domain was unable to insert the current audit trail detail entries for the instance \"{0}\" to the audit details table. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04006
severity: 10
type: error
name: Cannot insert sync work items
description: The process domain was unable to store the work items for the synchronous instance \"{0}\" to the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04007
severity: 10
type: error
name: Cannot insert sync audit trail
description: The process domain was unable to store the audit trail for the synchronous instance \"{0}\" to the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04008
severity: 10
type: error
name: Cannot set auto commit
description: Unable to set the auto commit level for the current datastore connection. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04009
severity: 10
type: error
name: Cannot commit transaction
description: Unable to commit the current datastore transaction. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04010
severity: 10
type: error
name: Cannot delete instances
description: The process domain was unable to purge the instances from the datastore. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04011
severity: 10
type: error
name: Cannot delete document
description: The process domain was unable to delete the document \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04012
severity: 10
type: error
name: Cannot delete process instances
description: The process domain was unable to delete all the instances for the process \"{0}\" (revision \"{1}\") from the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04013
severity: 10
type: error
name: Cannot find expired work items
description: The process domain was unable to fetch a list of the expired work items in the datastore. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04014
severity: 10
type: error
name: Cannot lookup instance type
description: The process domain was unable to lookup the type for instance \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04015
severity: 10
type: error
name: Cannot find stranded scope activation messages
description: The process domain was unable to fetch a list of the stranded scope activation messages from the datastore. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04016
severity: 10
type: error
name: Cannot find stranded work items
description: The process domain was unable to fetch a list of the stranded work items in the datastore. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04017
severity: 10
type: error
name: Cannot find work items
description: The process domain was unable to find the work items for instance \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04018
severity: 10
type: error
name: Cannot find audit trail
description: The process domain was unable to find the audit trail entry for instance \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04019
severity: 10
type: error
name: Cannot find sync work items
description: The process domain was unable to find the work items for the synchronous instance \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04020
severity: 10
type: error
name: Cannot find sync audit trail
description: The process domain was unable to find the audit trail for the synchronous instance \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04021
severity: 10
type: error
name: Cannot find stranded transaction messages
description: The process domain was unable to fetch a list of stranded transaction messages from the datastore. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04022
severity: 10
type: error
name: Cannot delete transaction data
description: The process domain was unable to delete the data for transaction \"{0}\" from the datasource. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04023
severity: 10
type: error
name: Cannot load transaction data
description: The process domain was unable to load the data for transaction \"{0}\" from the datasource. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04024
severity: 10
type: error
name: Cannot store transaction data
description: The process domain was unable to insert/update the data for transaction \"{0}\" in the datasource. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04025
severity: 10
type: error
name: Cannot decode properties
description: The process domain was unable to decode the properties for message guid {0}, which are stored in column {1}; the exception reported is: {2}

ORABPEL-04026
severity: 10
type: error
name: Cannot find pending callback messages
description: The process domain was unable to find any pending callback messages in the datasource. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04027
severity: 10
type: error
name: Cannot find pending invoke messages
description: The process domain was unable to find any pending invoke messages in the datasource. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04028
severity: 10
type: error
name: Cannot find pending subscriptions
description: The process domain was unable to find any pending subscriptions in the datasource. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04029
severity: 10
type: error
name: Cannot mark process as stale
description: The process domain was unable to mark all instances (and activites) with process GUID \"{0}\" as stale. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04030
severity: 10
type: error
name: Cannot find audit details
description: An attempt to fetch the audit details for instance \"{0}\" (detail id \"{1}\") from datastore has failed. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04031
severity: 10
type: error
name: Cannot find audit details
description: An attempt to fetch the audit details for instance \"{0}\" from datastore has failed. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04032
severity: 10
type: error
name: Cannot read lob column
description: The process domain was unable to read the lob column \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04033
severity: 10
type: error
name: Cannot fetch document
description: The process domain was unable to fetch the document \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04034
severity: 10
type: error
name: Cannot find closed instance
description: The process domain was unable to find the closed instances for the domain \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04035
severity: 10
type: error
name: Cannot fetch instance
description: The process domain was unable to fetch the instance \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04036
severity: 10
type: error
name: Cannot fetch scope activation message
description: The process domain was unable to fetch the scope activation message with key \"{0}\" from the datasource. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04037
severity: 10
type: error
name: Cannot fetch work item
description: The process domain was unable to fetch the work item \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04038
severity: 10
type: error
name: Cannot update document
description: The process domain was unable to update/insert the document \"{0}\" into the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04039
severity: 10
type: error
name: Cannot update key range
description: The process domain was unable to update the key table \"{0}\". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04040
severity: 10
type: error
name: Cannot update lob column
description: The process domain was unable to update the lob column \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04041
severity: 10
type: error
name: Cannot update instance
description: The process domain was unable to update/insert the instance \"{0}\" into the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04042
severity: 10
type: error
name: Cannot update scope
description: The process domain was unable to update/insert the serialized scope for instance \"{0}\" into the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04043
severity: 10
type: error
name: Cannot delete/insert scope activation message
description: The process domain was unable to delete/insert the scope activation message with key \"{0}\" from the datasource. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04044
severity: 10
type: error
name: Cannot update work item
description: The process domain was unable to update/insert the work item \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04045
severity: 10
type: error
name: Cannot batch update work items
description: The process domain was unable to batch update/insert the work items for instance \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04046
severity: 10
type: error
name: Cannot batch insert sync work items
description: The process domain was unable to batch insert a series of synchronous work items in the datastore. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04047
severity: 10
type: error
name: Cannot select delivery subscription
description: The process domain was unable to select the delivery data for processId \"{0}\" and operationName \"{1}\" from the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04048
severity: 10
type: error
name: Cannot insert delivery subscription
description: The process domain was unable to insert the delivery data for conversation \"{0} \", subscriber \"{1}\" in the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04049
severity: 10
type: error
name: Cannot select delivery subscription
description: The process domain was unable to select the delivery data for conversation \"{0}\" (subscriber \"{1}\") from the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04050
severity: 10
type: error
name: Cannot select delivery subscription
description: The process domain was unable to select the delivery data for conversation \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04051
severity: 10
type: error
name: Cannot select delivery subscription
description: The process domain was unable to select the delivery data for conversation type \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04052
severity: 10
type: error
name: Cannot select delivery subscription
description: The process domain was unable to select the delivery data for subscriber \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04053
severity: 10
type: error
name: Cannot update delivery subscription
description: The process domain was unable to update the state of the delivery subscription \"{1}\" for conversation \"{0}\". The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04054
severity: 10
type: error
name: Cannot update delivery subscription
description: The process domain was unable to update the state of the delivery subscription \"{0}\". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04055
severity: 10
type: error
name: Cannot delete handled subscriptions
description: The process domain \"{0}\" was unable to delete handled delivery subscriptions. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04056
severity: 10
type: error
name: Cannot insert delivery message
description: The process domain was unable to insert the delivery data for message \"{0}\", operation \"{1}\" in the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04057
severity: 10
type: error
name: Cannot delete delivery message
description: The process domain was unable to delete the delivery data for message \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04058
severity: 10
type: error
name: Cannot delete handled messages
description: The process domain \"{0}\" was unable to delete the handled delivery data from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04059
severity: 10
type: error
name: Cannot select delivery message
description: The process domain was unable to select the delivery data for message \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04060
severity: 10
type: error
name: Cannot select delivery message
description: The process domain was unable to select the delivery data for message \"{0}\", operation \"{1}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04061
severity: 10
type: error
name: Cannot update delivery message
description: The process domain was unable to update the state of the delivery message \"{0}\". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04062
severity: 10
type: error
name: Cannot delete invoke message
description: The process domain was unable to delete the invocation data for message \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04063
severity: 10
type: error
name: Cannot delete handled messages
description: The process domain \"{0}\" was unable to delete the handled invocation data from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04064
severity: 10
type: error
name: Cannot select invoke message
description: The process domain was unable to select the invocation data for message \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04065
severity: 10
type: error
name: Cannot select invoke message
description: The process domain was unable to select the invocation data for process \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04066
severity: 10
type: error
name: Cannot insert invoke message
description: The process domain was unable to insert the invocation data for message \"{0}\", operation \"{1}\" in the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04067
severity: 10
type: error
name: Cannot update invoke message
description: The process domain was unable to update the state of the invocation message \"{0} \". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04069
severity: 10
type: error
name: Cannot find stale instances
description: The process domain was unable to fetch a list of the stale instances belonging to process \"{0}\" (revision \"{1}\"). The exception reported is: {2}

ORABPEL-04075
severity: 10
type: error
name: Cannot update task
description: The process domain was unable to update the data for task \"{0}\" in the datasource. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04076
severity: 10
type: error
name: Cannot lookup jdbc datasource
description: The process domain was unable to lookup the TX datasource \"{0}\".
fix: Please check that the machine hosting the datasource is physically connected to the network. Additionally check that the connection pool properties as defined in the application server startup properties are valid.

ORABPEL-04077
severity: 10
type: error
name: Cannot fetch a datasource connection
description: The process domain was unable to establish a connection with the datasource with the connection URL \"{0}\". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04078
severity: 10
type: error
name: Cannot close datasource connection
description: The process domain was unable to release its datasource connection. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04079
severity: 10
type: error
name: Cannot read blob stream
description: Cannot read blob stream from datastore with key \"{0}\"; exception is {1}

ORABPEL-04080
severity: 10
type: error
name: Data stream not found
description: The data stream for the instance/activity object \"{0}\" was not found in the datastore.
fix: Please check that the instance/activity key \"{0}\" refers to a valid instance/activity that has been started and not removed from the process domain.

ORABPEL-04081
severity: 10
type: error
name: Cannot write stream length
description: Cannot write binary stream length to serializer for instance \"{0}\"; exception is {1}

ORABPEL-04082
severity: 10
type: error
name: Cannot delete instance
description: The process domain was unable to delete the instance \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04083
severity: 10
type: error
name: Cannot update work item exception
description: The process domain was unable to insert/update the exception entry for the activity \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04084
severity: 10
type: error
name: Cannot delete work item exception
description: The process domain was unable to delete the exception entry for the activity \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04085
severity: 10
type: error
name: Cannot find work item exception
description: The process domain was unable to find the activity in the domain \"{0}\" with custom key \"{1}\"; the exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04087
severity: 10
type: error
name: Cannot find schedulable activities
description: Failed to find schedulable activities for domain \"{0}\"; exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04088
severity: 10
type: error
name: Cannot find tasks
description: Failed to find the tasks for domain \"{0}\" with the where condition \"{1}\"; the exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04089
severity: 10
type: error
name: Cannot update task
description: The process domain was unable to insert the data for task \"{0}\" in the datasource. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04090
severity: 10
type: error
name: Cannot select scope
description: The process domain was unable to read the serialized scope for instance \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04091
severity: 10
type: error
name: Cannot select instance indexes
description: The process domain was unable to read the indexes for instance \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04092
severity: 10
type: error
name: Cannot update instance indexes
description: The process domain was unable to update/insert the indexes for instance \"{0}\" into the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04093
severity: 10
type: error
name: Cannot select process metadata
description: The process domain was unable to select the metadata for process \"{0}\" with revision tag \"{1}\" from the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04095
severity: 10
type: error
name: Cannot delete process metadata
description: The process domain was unable to delete the metadata for process \"{0}\" with revision tag \"{1}\" from the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04096
severity: 10
type: error
name: Cannot update process metadata
description: The process domain was unable to insert/update the process metadata for process \"{0}\" with revision tag \"{1}\" in the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04097
severity: 10
type: error
name: Cannot find process revision
description: The process domain was unable to find the process revision record for process \"{0}\" with revision tag \"{1}\" in the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04098
severity: 10
type: error
name: Cannot flush jboss datasource
description: The process domain was unable to flush the datasource \"{0}\". The exception reported is: {1}
fix: Please try manually flushing the datasource from the jboss jmx-console.

ORABPEL-04099
severity: 10
type: error
name: Cannot find instances
description: The process domain was unable to find instances with root id \"{0}\" in the datasource. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04100
severity: 10
type: error
name: Cannot find invoke metadata
description: The process domain was unable to find any invoke messages with the specified where condition in the datasource. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04101
severity: 10
type: error
name: Cannot find callback metadata
description: The process domain was unable to find any callback messages with the specified where condition in the datasource. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04102
severity: 10
type: error
name: Cannot insert process event
description: The process domain was unable to insert the process event for process \"{0}\" (revision \"{1}\") in the datasource. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04103
severity: 10
type: error
name: Cannot find process events
description: The process domain was unable to find any process events with the specified where condition in the datasource. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04104
severity: 10
type: error
name: Cannot find default revisions
description: The process domain was unable to find the default process revisions in the datasource. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04105
severity: 10
type: error
name: Cannot update default revision
description: The process domain was unable to set the default revision for process \"{0}\", revision tag \"{1}\" in the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04106
severity: 10
type: error
name: Cannot delete default revision
description: The process domain was unable to delete the default revision for process \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04107
severity: 10
type: error
name: Cannot update lob column
description: The process domain was unable to update the lob column \"{0}\" in the datastore, for cube instance \"{1}\". The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04108
severity: 10
type: error
name: Cannot select attachment
description: The process domain was unable to select the attachent by the key \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04109
severity: 10
type: error
name: Cannot delete attachment
description: The process domain was unable to delete the attachent by the key \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04110
severity: 10
type: error
name: Cannot insert attachment
description: The process domain was unable to insert attachent into the datastore. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04111
severity: 10
type: error
name: Cannot fetch attachment reference
description: The process domain was unable to seelct the attachment reference \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04112
severity: 10
type: error
name: Cannot insert attachment reference
description: The process domain was unable to insert attachent reference into the datastore. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04113
severity: 10
type: error
name: Cannot delete attachment reference
description: The process domain was unable to remove attachent reference of instance \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04121
severity: 10
type: error
name: Cannot find test details
description: An attempt to fetch the test details using the where condition \"{0}\" from the datastore has failed. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04122
severity: 10
type: error
name: Cannot update test details
description: The process domain was unable to insert/update test details for instance \"{0}\" in the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04123
severity: 10
type: error
name: Cannot update delivery message batch
description: The process domain was unable to update the state of the following delivery messages \"{0}\". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04124
severity: 10
type: error
name: Cannot update delivery subscription batch
description: The process domain was unable to update the state of the following delivery subscriptions \"{0}\". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04125
severity: 10
type: error
name: Cannot select detail instances
description: The process domain was unable to select the number of detail instances for master instance specified by the conversation id \"{0}\".
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04126
severity: 10
type: error
name: Cannot select document reference key
description: The process domain was unable to select document references for instance id \"{0} \". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04127
severity: 10
type: error
name: Cannot select insert reference key
description: The process domain was unable to insert document references for instance id \"{0} \". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04128
severity: 10
type: error
name: Cannot select document reference key
description: The process domain was unable to select document references for delivery message guid \"{0}\". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04129
severity: 10
type: error
name: Cannot select insert reference key
description: The process domain was unable to insert document references for delivery message guid \"{0}\". The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04130
severity: 10
type: error
name: Cannot select process descriptor
description: The process domain was unable to select the descriptor for process \"{0}\", revision \"{1}\" from the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04131
severity: 10
type: error
name: Cannot insert/update process descriptor
description: The process domain was unable to insert/update the descriptor for process \"{0}\", revision \"{1}\" into the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04132
severity: 10
type: error
name: Cannot read clob stream
description: Cannot read clob stream from datastore with key \"{0}\"; exception is {1}

ORABPEL-04133
severity: 10
type: error
name: Cannot select process suitcase
description: The process domain was unable to select the bytes for suitcase \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04134
severity: 10
type: error
name: Cannot insert/update process suitcase
description: The process domain was unable to insert/update the process suitcase \"{0}\" into the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04135
severity: 10
type: error
name: Cannot delete process suitcase
description: The process domain was unable to delete the process suitcase \"{0}\" from the datastore. The exception reported is: {1}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04136
severity: 10
type: error
name: Cannot count suitcase processes
description: The process domain was unable to count the number of deployed suitcase processes. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04137
severity: 10
type: error
name: Cannot find test definition
description: An attempt to fetch the test definition for process \"{0}\", revision \"{1}\", test suite \"{2}\", location \"{3}\" from the datastore has failed. The exception reported is: {4}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04138
severity: 10
type: error
name: Cannot store test definition
description: The process domain was unable to store the test definition for process \"{0}\", revision \"{1}\", test suite \"{2}\", location \"{3}\" in the datastore. The exception reported is: {4}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04139
severity: 10
type: error
name: Cannot delete test definition
description: The process domain was unable to delete the test definition for process \"{0}\", revision \"{1}\", test suite \"{2}\", location \"{3}\" in the datastore. The exception reported is: {4}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04140
severity: 10
type: error
name: Cannot delete test definitions
description: The process domain was unable to delete test definitions for process \"{0}\", revision \"{1}\" in the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04141
severity: 10
type: error
name: Cannot delete process events
description: The process domain was unable to delete the events logged for process \"{0}\", revision \"{1}\" from the datastore. The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

ORABPEL-04142
severity: 10
type: error
name: Cannot delete process events
description: The process domain was unable to delete the events logged for in the domain. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.

BPEL Generic Exceptions ORABPEL 00000 - 00031

2007-08-12T05:28:00.001-07:00

BPEL Generic Exceptions ORABPEL 00000 - 00031
Generic Exceptions 00000 - 00031

ORABPEL-00000
severity: 10
type: error
name: Exception not handled by the Collaxa Cube system.
description: An unhandled exception has been thrown in the Collaxa Cube system. The exception reported is: \"{0}\".

ORABPEL-00001
severity: 10
type: error
name: Failed to write auth file
description: Failed to write auth property file \"{0}\"; exception reported is: {1}

ORABPEL-00002
severity: 10
type: error
name: Domain authentication change failed
description: Failed to write authentication file \"{1}\" for domain \"{0}\"; exception reported is: {2}

ORABPEL-00003
severity: 10
type: error
name: Failed to read auth file
description: Failed to read auth property file \"{0}\"; exception reported is: {1}

ORABPEL-00004
severity: 10
type: error
name: Authentication failed
description: Failed to authenticate credentials.

ORABPEL-00005
severity: 10
type: error
name: Collaxa lib directory not found
description: The specified BPM library directory \"{0}\" cannot be found.

ORABPEL-00006
severity: 10
type: error
name: Cipher creation error
description: Failed to load the JCE cipher \"{0}\". Your environment may not be set correctly.
fix: You must have the JCE library files installed in your JRE installation as an extension. Copy the jar files from \"{1}\\install\\java\\jce1.2.2\" to the \"(jdk_path) \\jre\\lib\\ext\" directory (where jdk_path is your jdk installation directory).

ORABPEL-00007
severity: 10
type: error
name: Cipher decryption error
description: Failed to decrypt cipher text with transformation \"{0}\"; exception reported is {1}

ORABPEL-00008
severity: 10
type: error
name: Cipher encryption error
description: Failed to encrypt plain text with transformation \"{0}\"; exception reported is {1}

ORABPEL-00009
severity: 10
type: error
name: Data conversion failed
description: Failed to convert \"{0}\" to a \"{1}\".

ORABPEL-00010
severity: 10
type: error
name: Guid generation failed
description: Failed to generate GUID. Please check the domain log whether the GUID generator native library \"cxguid\" was loaded properly.

ORABPEL-00011
severity: 10
type: error
name: Guid Library Load Failed
description: Failed to load the native library \"cxguid\" for the GUID generator. Your environment may not be set correctly. The current PATH is: \"{0}\".
fix: On Windows systems, your PATH must include \"{1}\\bin\".

ORABPEL-00012
severity: 10
type: error
name: Guid Library Load Failed
description: Failed to load the native library \"cxguid\" for the GUID generator. Your environment may not be set correctly. The current java library path is: \"{0}\".
fix: On Linux and Solaris systems, your LD_LIBRARY_PATH must include \"{1}/lib/linux\" and \"{1}/lib/solaris\" respectively.

ORABPEL-00013
severity: 10
type: error
name: Failed to lookup localhost IP
description: Failed to lookup the localhost IP address. Please check that your machine''s network configuration is correct.

ORABPEL-00014
severity: 10
type: error
name: Failed to lookup IP
description: Failed to lookup the IP address for host \"{0}\". Please check that your machine''s network configuration (particularly the DNS settings) is correct.

ORABPEL-00015
severity: 10
type: error
name: Jar Creation Failed
description: Failed to create jar file {0}.
fix: Please verify that jar is installed on this machine and is included in machine system path. Also verify if tools.jar file is included in OBDK_CLASSPATH.

ORABPEL-00016
severity: 10
type: error
name: Javac compiler configuration error
description: Failed to execute javac compiler on file(s) \"{0}\". Exception reported is: {1}
fix: Please verify that javac compiler is installed on this machine and is included in the classpath (check that \"tools.jar\" in particular is in the classpath).

ORABPEL-00017
severity: 10
type: error
name: Java compilation failed
description: Failed to compile file(s) \"{0}\".\nException reported is: {1}
fix: Please verify that file {0} is valid java file or if all required libraries are included in your classpath.

ORABPEL-00018
severity: 10
type: error
name: Java source directory not found
description: Cannot find the java source directory \"{0}\".

ORABPEL-00019
severity: 10
type: error
name: Java destination directory not found
description: Cannot create the java destination directory \"{0}\".
fix: Please check that the directory \"{0}\" exists and is writable.

ORABPEL-00020
severity: 10
type: error
name: JavaDoc Processing Failed
description: Failed to write the JavaDoc argument file \"{0}\". The exception reported is: \"{2}\".
fix: Please check that the directory \"{1}\" is writable.

ORABPEL-00021
severity: 10
type: error
name: JavaDoc Processing Failed
description: Failed to execute JavaDoc with the argument file \"{0}\".
fix: Please verify that JavaDoc is installed on this machine in \\bin directory and this directory is included in machine system path.

ORABPEL-00022
severity: 10
type: error
name: Failed to backup log configuration
description: Failed to backup log configuration file \"{0}\" for domain \"{1}\". The following exception was thrown: {3}
fix: Please ensure that the directory \"{2}\" is writeable by the server.

ORABPEL-00023
severity: 10
type: error
name: Failed to update log configuration
description: Failed to update log configuration file \"{0}\" for domain \"{1}\". The following exception was thrown: {3}
fix: Please ensure that the directory \"{2}\" is writeable by the server.

ORABPEL-00024
severity: 10
type: error
name: Cannot schedule agent
description: An attempt to schedule the \"{0}\" agent with the scheduler has failed. The exception reported is: {1}

ORABPEL-00025
severity: 10
type: error
name: Cannot unschedule agent
description: An attempt to unschedule the \"{0}\" agent with the scheduler has failed. The exception reported is: {1}

ORABPEL-00026
severity: 10
type: error
name: Error while executing agent
description: An error occurred while attempting to execute the job \"{0}\" for agent \"{1}\". The exception reported was : {2}

ORABPEL-00027
severity: 10
type: error
name: Failed to backup log configuration
description: Failed to backup log configuration file \"{0}\" for the Collaxa server. The following exception was thrown: {1}
fix: Please ensure that the directory \"{2}\" is writable by the server.

ORABPEL-00028
severity: 10
type: error
name: Failed to update log configuration
description: Failed to update log configuration file \"{0}\" for the Collaxa server. The following exception was thrown: {2}
fix: Please ensure that the directory \"{1}\" is writable by the server.

ORABPEL-00029
severity: 10
type: error
name: Cannot access log file directory
description: Failed to access log file directory \"{0}\" for the Collaxa server; the server can only access files contained in the logs directory.

ORABPEL-00030
severity: 10
type: error
name: Cannot access log file
description: Failed to access log file \"{0}\" for the Collaxa server; the file cannot be read or is not a plain text file.

ORABPEL-00031
severity: 10
type: error
name: Cannot read log file
description: Failed to read contents for log file \"{0}\" for the Collaxa server; the following exception was thrown: {1}

2007-08-12T05:27:00.000-07:00

BPEL Deployment Exceptions ORABPEL 05200 - 05251
Deployment Exceptions 05200 - 05251

ORABPEL-05200
severity: 10
type: error
name: Cannot read timestamp file
description: An exception occured while attempting to read the timestamp file \"{0}\". The exception reported is: {1}

ORABPEL-05201
severity: 10
type: error
name: Cannot write timestamp file
description: An exception occured while attempting to write the timestamp file \"{0}\". The exception reported is: {1}

ORABPEL-05202
severity: 10
type: error
name: Error opening BPEL archive
description: An exception occured while attempting to open the BPEL archive \"{0}\". The exception reported is: {1}

ORABPEL-05203
severity: 10
type: error
name: Error unpacking BPEL archive
description: An exception occured while attempting to unpack the BPEL archive \"{0}\". The exception reported is: {1}

ORABPEL-05204
severity: 10
type: error
name: Inconsistent process id/revision.
description: The process identifier \"{0}\" and revision tag \"{1}\" do not match the identifier \"{2}\" and revision tag \"{3}\" specified in the process descriptor.
fix: Please generate the BPEL archive again using the \"bpelc\" tool and redeploy the process.

ORABPEL-05205
severity: 10
type: error
name: Missing BPEL archive file
description: The process domain cannot locate the BPEL archive for process \"{0}\", revision \"{1}\".
fix: If you have deployed the process please check that it is located in the directory \"{2}\".

ORABPEL-05206
severity: 10
type: error
name: Missing BPEL archive file name
description: The name for the BPEL archive file is empty.

ORABPEL-05207
severity: 10
type: error
name: Error deploying BPEL archive
description: An error occurred while attempting to deploy the BPEL archive file \"{0}\"; the exception reported is: {1}

ORABPEL-05208
severity: 10
type: error
name: Missing process descriptor file
description: The process deployment descriptor file \"bpel.xml\" has not been packaged in the BPEL archive \"{0}\".
fix: Please generate the BPEL archive again using the \"bpelc\" tool and redeploy the process. The BPEL archive \"{0}\" may have been generated with an older version of \"bpelc\".

ORABPEL-05209
severity: 10
type: error
name: Missing BPEL manifest attribute
description: The manifest for BPEL archive \"{0}\" does not contain the required attribute \"{1}\".
fix: Please generate the BPEL archive again using the \"bpelc\" tool and redeploy the process.

ORABPEL-05210
severity: 10
type: error
name: No BPEL archive files
description: The process domain cannot locate any BPEL archives for process \"{0}\".
fix: If you have deployed a process please check that it is located in the directory \"{1}\".

ORABPEL-05211
severity: 10
type: error
name: Null BPEL manifest
description: The BPEL archive \"{0}\" does not contain a manifest. All deployed BPEL archives must contain a manifest.
fix: Please generate the BPEL archive again using the \"bpelc\" tool and redeploy the process.

ORABPEL-05212
severity: 10
type: error
name: Deployment directory not found
description: The directory \"{0}\" is expected to be present in the domain directory \"{1}\". The deployed processes for this domain are expected to reside in this directory.
fix: Please ensure that the directory \"{0}\" exists under the domain directory \"{1} \".

ORABPEL-05213
severity: 10
type: error
name: Invalid process id
description: The process identifier \"{0}\" for the BPEL Process archive \"{1}\" is not valid. Process identifiers may start with a letter, a \"$\" or \"_\" character; process characters (other than the first character) include a letter, a digit, a \"$\", a \"_\" or \"-\" character.
fix: Please make sure that the deployment descriptor contained in the BPEL Process archive \"{1}\" has a valid process id.

ORABPEL-05214
severity: 10
type: error
name: Invalid process revision tag
description: The process revision tag \"{0}\" for the BPEL Process archive \"{1}\" is not valid. Valid revision tags may contain the following characters: a letter, a digit or any of [\"$\", \"_\", \"-\", \".\"].
fix: Please make sure that the deployment descriptor contained in the BPEL Process archive \"{1}\" has a valid revision tag.

ORABPEL-05215
severity: 5
type: error
name: Error while loading process
description: The process domain encountered the following errors while loading the process \"{0}\" (revision \"{1}\"): {2}.
fix: If you have installed a patch to the server, please check that the bpelcClasspath domain property includes the patch classes.

ORABPEL-05216
severity: 10
type: error
name: Process class not valid
description: The class \"{0}\" for the process \"{1}\" (revision \"{2}\") does not implement the ICubeProcess interface. All process classes contained within the process domain must implement this interface.
fix: Please try recompiling your BPEL process again. The current BPEL process archive \"{1}\" may have been compiled with an older version of \"bpelc\".

ORABPEL-05217
severity: 10
type: error
name: Error while creating process
description: An error has occurred while attempting to instantiate the class \"{0}\" for the process \"{1}\" (revision \"{2}\"). The exception reported was: {3}
fix: Please try recompiling your BPEL process again. The current BPEL process archive \"{1}\" may have been compiled with an older version of \"bpelc\".

ORABPEL-05220
severity: 10
type: error
name: Unknown process classname
description: The process \"{0}\" (revision \"{1}\") is missing its classname; this element cannot be created without its classname.

ORABPEL-05221
severity: 10
type: error
name: Error while updating process
description: An error has occurred while attempting to update the process descriptor for the BPEL process \"{0}\" (revision \"{1}\"). The exception reported was: {2}

ORABPEL-05222
severity: 10
type: error
name: Type class not found
description: Cannot find class for type \"{0}\". Please check that the class is located in the classpath.

ORABPEL-05223
severity: 10
type: error
name: Type excluded
description: Cannot generate type helpers for the class \"{0}\". This class cannot be persisted by the BPEL process domain. Objects which maintain system level handles cannot be persisted and recreated reliably.

ORABPEL-05224
severity: 10
type: error
name: Insufficient security priviledges
description: Failed to generate persistence manager \"{0}\" for class \"{1}\". The application server reflection access check must be disabled in order for the persistence manager to be created. If you cannot disable this check, you must implement your own persistence manager for the class \"{1}\".

ORABPEL-05225
severity: 10
type: error
name: Invalid persistence manager class
description: The persistence manager class \"{0}\" for type \"{1}\" does not implement the IPersistenceManager interface.

ORABPEL-05226
severity: 10
type: error
name: Error while creating persistence manager
description: An error occurred while attempting to instantiate the persistence manager class \"{0}\" for type \"{1}\". The exception reported was: {2}

ORABPEL-05227
severity: 10
type: error
name: Invalid deserializer class
description: The Axis deserializer class \"{0}\" for type \"{1}\" does not implement the Deserializer interface.

ORABPEL-05228
severity: 10
type: error
name: Invalid serializer class
description: The Axis serializer class \"{0}\" for type \"{1}\" does not implement the Serializer interface.

ORABPEL-05229
severity: 10
type: error
name: Error while creating serializers
description: An error occurred while attempting to instantiate the Axis serializer class \"{0} \" for type \"{1}\". The exception reported was: {2}.

ORABPEL-05230
severity: 10
type: error
name: Error accessing working directory
description: Cannot access type working directory \"{0}\". This directory is used by the BPEL process domain to generate helper classes for types used in a process.
fix: Please check that the directory \"{0}\" is readable and writable by the BPEL process domain.

ORABPEL-05231
severity: 10
type: error
name: Error while creating working directory
description: Cannot create type working directory \"{0}\". This directory is used by the BPEL process domain to generate helper classes for types used in a process.
fix: Please check that the directory \"{0}\" exists and is readable and writable by the BPEL process domain.

ORABPEL-05232
severity: 10
type: error
name: Error while creating working directory
description: Cannot create type working directory \"{0}\". This directory is used by the BPEL process domain to generate helper classes for types used in a process. The exception reported is: \"{1}\".
fix: Please check that the directory \"{0}\" exists and is readable and writable by the BPEL process domain.

ORABPEL-05233
severity: 5
type: error
name: Mail account not found
description: The mail account \"{0}\" cannot be found in the metadata directory.

ORABPEL-05234
severity: 10
type: error
name: Error creating mail account
description: An exception occured while attempting to parse the mail account from the XML file \"{0}\". The exception reported is: {1}

ORABPEL-05235
severity: 10
type: error
name: Error unpacking task template archive
description: An exception occured while attempting to unpack the task template archive \"{0}\". The exception reported is: {1}

ORABPEL-05236
severity: 10
type: error
name: Error while creating task template
description: An error has occurred while attempting to instantiate the class \"{0}\" for the task template \"{1}\" (archive \"{2}\"). The exception reported was: {3}

ORABPEL-05237
severity: 5
type: error
name: Task template not found
description: The task template \"{0}\" cannot be found in the metadata directory.

ORABPEL-05238
severity: 10
type: error
name: Tasklet class not valid
description: The class \"{0}\" for the task template \"{1}\" does not implement the ITasklet interface. All tasklet classes contained within the process domain must implement this interface.
fix: Please try regenerating your task template archive again.

ORABPEL-05239
severity: 5
type: error
name: JMS connector not found
description: The jms connector \"{0}\" cannot be found in the metadata directory.

ORABPEL-05240
severity: 10
type: error
name: Error creating jms connector
description: An exception occured while attempting to parse the jms connector from the XML file \"{0}\". The exception reported is: {1}

ORABPEL-05241
severity: 10
type: error
name: Missing task descriptor
description: The task descriptor file \"task.xml\" for the task template \"{0}\" has not been packaged in the task archive file \"{1}\".

ORABPEL-05242
severity: 10
type: error
name: Invalid suitcase deployment descriptor
description: The suitcase descriptor of bpel archive \"{0}\" is not valid.
fix: Rebuild your suitcase and redeploy it using the current BPEL build environment.

ORABPEL-05243
severity: 10
type: error
name: Cannot obtain lock for process
description: Failed to obtain load lock for process \"{0}\"; exception reported is: {1}

ORABPEL-05244
severity: 10
type: error
name: Timed out waiting for process load lock
description: Failed to obtain load lock for process \"{0}\"; timed out after {1} seconds.

ORABPEL-05245
severity: 10
type: error
name: Cannot extract process descriptor
description: Failed to write descriptor file for process \"{0}\", revision \"{1}\"; exception reported is: {2}

ORABPEL-05246
severity: 10
type: error
name: Cannot marshall process descriptor
description: Failed to marshall descriptor for process \"{0}\", revision \"{1}\"; exception reported is: {2}

ORABPEL-05247
severity: 5
type: error
name: Process not found
description: The BPEL process with GUID \"{0}\" has not been loaded. Either the process was not initialized properly or the process has been disabled.
fix: Please consult your administrator regarding this error. The application server logs may provide more information regarding this error.

ORABPEL-05248
severity: 5
type: error
name: Cannot read process bytes
description: An exception occured while attempting to read the bytes from BPEL archive \"{0}\". The exception reported is: {2}

ORABPEL-05249
severity: 10
type: error
name: Cannot compute process guid
description: Failed to compute guid for process \"{0}\", revision \"{1}\"; exception is: {2}

ORABPEL-05250
severity: 10
type: error
name: Error deploying BPEL suitcase
description: An error occurred while attempting to deploy the BPEL suitcase file \"{0}\"; the exception reported is: {1}

ORABPEL-05251
severity: 10
type: error
name: Cannot compute suitcase checksum
description: Failed to compute suitcase id; exception is: {0}

BPEL Activation Agent Exceptions ORABPEL 09900 - 09911

2007-08-11T08:19:00.002-07:00

BPEL Activation Agent Exceptions ORABPEL 09900 - 09911
Activation Agent Exceptions 09900 - 09911

ORABPEL-09900
severity: 10
type: error
name: Error while creating activation job
description: An error occurred while attempting to instantiate the activation agent class \"{0}\". The exception reported was: \"{1}\".
fix: Please fix the error and redeploy the class to the server.

ORABPEL-09901
severity: 10
type: error
name: Unknown activation job classname
description: No activation agent classname has been associated with \"{0}\".
fix: Please check the \"className\" activation agent''s property for your jms process.

ORABPEL-09902
severity: 10
type: error
name: Activation agent class not valid
description: The activation agent class \"{0}\" does not implement the IActivationAgent interface. All activation agents must implement this interface.
fix: Please ensure that the class \"{0}\" implements the IActivationAgent interface.

ORABPEL-09903
severity: 10
type: error
name: Could not initialize activation agent
description: An error occured while initializing an activation agent for process \"{0}\", revision \"{1}\".
fix: Please ensure that the activation agents are configured correctly in the bpel deployment descriptor (bpel.xml).

ORABPEL-09904
severity: 10
type: error
name: Could not uninitialize activation agent
description: An error occured while uninitializing an activation agent for process \"{0}\", revision \"{1}\".

ORABPEL-09905
severity: 10
type: error
name: Error in onStateChanged callback method
description: An error occured while invoking the onStateChanged() method in one of the activation agents for process \"{0}\", revision \"{1}\".

ORABPEL-09906
severity: 10
type: error
name: Error in onLifecycleChanged callback method
description: An error occured while invoking the onLifecycleChanged() method in one of the activation agents for process \"{0}\", revision \"{1}\".

ORABPEL-09907
severity: 10
type: error
name: Error in onUndeploy callback method
description: An error occured while invoking the onUndeploy() method in one of the activation agents for process \"{0}\", revision \"{1}\".

ORABPEL-09908
severity: 10
type: error
name: Error while reading file content from activation agent
description: Activation agent \"{0}\" couldn''t read file content. The reason is {1}.
fix: Please ensure that the file name or path for the file is correct and should be relative path to the BPEL Suite.

ORABPEL-09909
severity: 10
type: error
name: Error in onHeartBeat callback method
description: Error occured while invoking onHeartBeat() method on \"{0}\". The reason is {1}.
fix: Please ensure that the activation class \"{0}\" implements IHeartBeatAware interface and implements onHeartBeat() method correctly.

ORABPEL-09910
severity: 10
type: error
name: Activation agent is not heart beat aware
description: Activation agent \"{0}\" is not heart beat aware. Please implement IHeartBeatAware interface for your activation agent.

ORABPEL-09911
severity: 10
type: error
name: Error getting partner wsdl
description: Error occured while getting partner \"{0}\" wsdl for process \"{1}\". The reason is {2}.
fix: Please ensure that the partner link name is correct.

BPEL XPath Exceptions ORABPEL 09500 - 09504

2007-08-11T08:19:00.001-07:00

BPEL XPath Exceptions ORABPEL 09500 - 09504
XPath Exceptions 09500 - 09504

ORABPEL-09500
severity: 10
type: error
name: XPath expression failed to execute
description: Error while processing xpath expression, the expression is \"{0}\", the reason is {1}.
fix: Please verify the xpath query.

ORABPEL-09501
severity: 10
type: error
name: Failed to register xpath function
description: Error while registering xpath function \"{0}\", the reason is {1}.
fix: Please verify the xpath function \"{0}\" is defined in the domain property file.

ORABPEL-09502
severity: 10
type: error
name: XPath query syntax error
description: Syntax error while parsing xpath expression \"{0}\", at position \"{1}\" the exception is {2}.
fix: Please verify the xpath query \"{0}\" which is defined in BPEL process.

ORABPEL-09503
severity: 10
type: error
name: Invalid xpath expression
description: Error while parsing xpath expression \"{0}\", the reason is {1}.
fix: Please verify the xpath query \"{0}\" which is defined in BPEL process.

ORABPEL-09504
severity: 10
type: error
name: empty variable/expression result
description: xpath variable/expression expression \"{0}\" is empty at line {1}, when attempting reading/copying it.
fix: Please make sure the variable/expression result \"{0}\" is not empty.

BPEL Web Service Exceptions ORABPEL 08000 - 08033

2007-08-11T08:18:00.002-07:00

BPEL Web Service Exceptions ORABPEL 08000 - 08033
Web Service Exceptions 08000 - 08033

<>Parameters: 0: SOAPHeaderElement's QName 1: operation Name 2: SOAPException message
ORABPEL-08000
severity: 10
type: error
name: Failed to set soap header
description: Failed to set SOAPHeaderElement \"{0}\" when invoking operation \"{1}\". Reason is \"{2}\".

ORABPEL-08001
severity: 10
type: error
name: Failed to set soap header
description: Failed to set soap header \"{0}\" for operation \"{1}\", because \"{2}\".

ORABPEL-08002
severity: 10
type: error
name: Failed to read wsdl
description: Error happened when reading wsdl at \"{0}\", because \"{1}\".
fix: Make sure wsdl exists at that URL and is valid.

ORABPEL-08003
severity: 10
type: error
name: Failed to read wsdl
description: Failed to read wsdl at \"{0}\", because \"{1}\".
fix: Make sure wsdl is valid. You may need to start the OraBPEL server, or make sure the related bpel process is deployed correctly.

ORABPEL-08004
severity: 10
type: error
name: WSDL type map not registered
description: Cannot find registered typeMap for WSDL definition \"{0}\".
fix: TypeMapping should be registered before it can be used by the WebService layer. This is a system exception, please report to admin.

ORABPEL-08005
severity: 10
type: error
name: Failed to get type for wrapper
description: Failed to get type for elment \"{1}\" of wrapper type \"{0}\".
fix: Please verify that element \"{1}\" of wrapper type \"{0}\" is defined with the valid XML type.

ORABPEL-08006
severity: 10
type: error
name: Failed to read WSDL
description: Failed to read wsdl at \"{0}\" because \"{1}\".
fix: Please verify that WSDL at location \"{0}\" is valid.

<>{ "exception.08007 .fix", "Please verify that there is a port that implements portType \"{0}\" in the WSDL service \"{1}\"." },
ORABPEL-08007
severity: 10
type: error
name: Failed get wsdl port
description: Failed to get WSDL port that implements portType \"{0}\" from WSDL service \"{1} \".

ORABPEL-08008
severity: 10
type: error
name: Failed get wsdl service definition
description: Failed to get WSDL service \"{0}\" from WSDL definition \"{1}\".
fix: Please verify that WSDL service \"{0}\" is correctly defined in the WSDL file.

ORABPEL-08009
severity: 10
type: error
name: Failed get wsdl service definition
description: Failed to get a WSDL service that support the portType \"{0}\" in WSDL definition \"{1}\".
fix: Please verify that WSDL portType \"{0}\" is supported by a service in WSDL file.

ORABPEL-08010
severity: 10
type: error
name: Failed get operation definition
description: Failed to get the WSDL operation definition of \"{0}\" in portType \"{1}\".
fix: Please verify that operation \"{0}\" is defined in portType \"{1}\".

ORABPEL-08011
severity: 10
type: error
name: Cannot find parterRole
description: Failed to get partnerRole \"{0}\" of partnerLink \"{1}\" in partnerLinkType \"{2} \".
fix: Please verify that partnerRole \"{0}\" is defined in partnerLinkType \"{2}\".

ORABPEL-08012
severity: 10
type: error
name: Cannot find parterRole
description: Failed to resolve the java class for type \"{2}\" of part \"{1}\" of messageType \"{0}\".
fix: Please make sure the XML type \"{2}\" is defined in WSDL or XSD.

ORABPEL-08013
severity: 10
type: error
name: Cannot find partnerLinkType
description: PartnerLinkType \"{1}\" of partnerLink \"{0}\" is not found in either partner WSDL at \"{2}\" and process WSDL at \"{3}\".
fix: Please make sure the partnerLinkType is defined in the WSDL.

ORABPEL-08014
severity: 10
type: error
name: No such operation
description: Cannot find operation.
fix: The WSDL might have been changed and you might need to recompile your process.

ORABPEL-08015
severity: 10
type: error
name: No such operation
description: Cannot find operation \"{0}\" of portType \"{1}\" in WSDL at \"{2}\".
fix: The WSDL at \"{2}\" might have been changed and you might need to recompile and deploy the caller process.

ORABPEL-08016
severity: 10
type: error
name: Cannot find partnerLinkType 2
description: PartnerLinkType \"{0}\" is not found in WSDL at \"{1}\".
fix: Please make sure the partnerLinkType is defined in the WSDL.

ORABPEL-08017
severity: 10
type: error
name: Cannot find partnerLink
description: PartnerLink \"{0}\" has not been defined in the process \"{1}\" (revision \"{2} \").

ORABPEL-08018
severity: 10
type: error
name: Cannot send jms message
description: The process \"{0}\" (revision \"{1}\") was unable to send a message to jms partner \"{2}\"; the exception is: {3}
fix: Please check that the messaging service for the application server has been configured properly.

ORABPEL-08019
severity: 10
type: error
name: Cannot create subscriber
description: The process \"{0}\" (revision \"{1}\") was unable to create a subscriber for jms partner \"{2}\"; the exception is: {3}

ORABPEL-08020
severity: 10
type: error
name: Cannot shutdown subscriber
description: The process \"{0}\" (revision \"{1}\") was unable to close the subscriber for jms partner \"{2}\"; the exception is: {3}
fix: Please check the MOM Server for the connector has been running properly or not.

ORABPEL-08021
severity: 10
type: error
name: Cannot find partner wsdl
description: parnterLink \"{0}\" is not found in process \"{1}\" (revision \"{2}\")
fix: Please check the deployment descriptor of the process to find the correct partnerLink name

ORABPEL-08022
severity: 10
type: error
name: Cannot find binding operation
description: in WSDL located at \"{0}\", cannot find a binding operation of \"{2}\", portType \"{1}\"
fix: Please make sure the WSDL is valid

ORABPEL-08032
severity: 10
type: error
name: Failed get wsdl portType definition
description: Failed to get WSDL portType \"{0}\" from WSDL definition \"{1}\".
fix: Please verify that WSDL portType \"{0}\" is correctly defined in the WSDL file.

ORABPEL-08033
severity: 10
type: error
name: EJB Transaction Error
description: EJB exception happened while invoking the partner
fix: Please verify partner service.

BPEL License Exceptions ORABPEL 00800 - 00824

2007-08-11T08:18:00.001-07:00

BPEL License Exceptions ORABPEL 00800 - 00824
License Exceptions 00800 - 00824

ORABPEL-00800
severity: 10
type: error
name: No license error
description: A valid license for the \"{0}\" component (product \"{1}\", release \"{2}\") has not been found in the license file \"{3}\". This product is unable to continue without a valid license.
fix: If you have not obtained a license for your OraBPEL installation please contact Oracle for assistance.

ORABPEL-00801
severity: 10
type: error
name: No license group error
description: A valid license group for the \"{0}\" product (release \"{1}\") has not been found in the license file \"{2}\". This product is unable to continue without a valid license.
fix: If you have not obtained a license for your OraBPEL installation please contact Oracle for assistance.

ORABPEL-00802
severity: 10
type: error
name: License file not found
description: Could not find licensing file \"{0}\". Your OraBPEL license file, named \"orabpel-license.xml\" must be located in the \"license\" directory in your OraBPEL installation directory.
fix: If this is the first time you are running OraBPEL, please start the server and then the console and a wizard will drive you through the generation of a 30-day evaluation license.\n If you have not obtained a license for your OraBPEL installation please contact Oracle for assistance (support@collaxa.com).

ORABPEL-00803
severity: 10
type: error
name: Cannot create license key
description: Cannot create the license for key for component \"{0}\" due to exception: \"{1} \".

ORABPEL-00804
severity: 10
type: error
name: Cannot read license file
description: Cannot read the license file \"{0}\" due to exception: \"{1}\".
fix: Check that the license file \"{0}\" can be read by the server process.

ORABPEL-00805
severity: 10
type: error
name: Cannot parse license file
description: Cannot parse the license file \"{0}\" due to exception: \"{1}\".
fix: The license file may have been edited manually. Please contact Oracle for licensing assistance.

ORABPEL-00806
severity: 10
type: error
name: Cannot parse license key
description: Cannot parse the license key due to exception: \"{0}\".
fix: The license file may have been edited manually. Please contact Oracle for licensing assistance.

ORABPEL-00807
severity: 10
type: error
name: Cannot write license file
description: Cannot write the licenses to XML due to exception: \"{0}\".

ORABPEL-00808
severity: 10
type: error
name: Invalid component name
description: The component name \"{0}\" cannot be found in the license key. This OraBPEL license has been generated for another component.
fix: The license file may have been edited manually. Please contact Oracle for licensing assistance.

ORABPEL-00809
severity: 10
type: error
name: Invalid product info
description: The product name \"{0}\" or the release \"{1}\" cannot be found in the license key. This OraBPEL license has been generated for another product.
fix: The license file may have been edited manually. Please contact Oracle for licensing assistance.

ORABPEL-00810
severity: 10
type: error
name: Missing product info
description: The product \"{0}\" or the release \"{1}\" cannot be found in the license key.
fix: The license file may have been edited manually. Please contact Oracle for licensing assistance.

ORABPEL-00811
severity: 10
type: error
name: Missing component name
description: The license component name cannot be found in the license key for component \"{0} \".
fix: The license file may have been edited manually. Please contact Oracle for licensing assistance.

ORABPEL-00812
severity: 10
type: error
name: Invalid IP address
description: The localhost IP address \"{0}\" cannot be found in the license key for component \"{1}\". This OraBPEL license has been generated for another IP address.
fix: The license file may have been edited manually. Please contact Oracle for licensing assistance.

ORABPEL-00813
severity: 10
type: error
name: Cannot lookup local IP
description: Cannot lookup the localhost IP address due to exception: \"{0}\".

ORABPEL-00814
severity: 10
type: error
name: Corrupt IP address
description: The license IP address cannot be parsed into the format: \"xxx.xxx.xxx.xxx\".
fix: The license file may have been edited manually. Please contact Oracle for licensing assistance.

ORABPEL-00815
severity: 10
type: error
name: Missing IP address
description: The license IP address cannot be found in the license key for component \"{0} \".
fix: The license file may have been edited manually. Please contact Oracle for licensing assistance.

ORABPEL-00816
severity: 10
type: error
name: Invalid license owner
description: This \"{0}\" license has been issued to \"{1}\"; however, the owner specified in the license file is \"{2}\". This OraBPEL license has been generated for another user.
fix: The license file may have been edited manually. Please contact Oracle for licensing assistance.

ORABPEL-00817
severity: 10
type: error
name: Missing license owner
description: The license owner cannot be found in the license key for component \"{0}\".
fix: The license file may have been edited manually. Please contact Oracle for licensing assistance.

ORABPEL-00818
severity: 10
type: error
name: Invalid start time
description: The OraBPEL license for component \"{0}\" is only valid after \"{1}\".
fix: The date and time settings for this machine have been set to an earlier date than the license creation date.

ORABPEL-00819
severity: 10
type: error
name: Corrupt start time
description: The license creation date cannot be parsed into a java date.
fix: The license file may have been edited manually. Please contact Oracle for licensing assistance.

ORABPEL-00820
severity: 10
type: error
name: Missing start time
description: The license creation date cannot be found in the license key for component \"{0} \".
fix: The license file may have been edited manually. Please contact Oracle for licensing assistance.

ORABPEL-00821
severity: 10
type: error
name: License has expired
description: The OraBPEL license for component \"{0}\" expired on \"{1}\" and is no longer valid.
fix: Please contact Oracle for licensing assistance.

ORABPEL-00822
severity: 10
type: error
name: Corrupt expiration date
description: The license expiration date cannot be parsed into a java date.
fix: The license file may have been edited manually. Please contact Oracle for licensing assistance.

ORABPEL-00823
severity: 10
type: error
name: Corrupt license units
description: The license units value cannot be parsed into an integral value.
fix: The license file may have been edited manually. Please contact Oracle for licensing assistance.

ORABPEL-00824
severity: 10
type: error
name: Missing expiration date
description: The license expiration date cannot be found in the license key for product \"{0} \".
fix: The license file may have been edited manually. Please contact Oracle for licensing assistance.

BPEL Sensor ExceptionsORABPEL 20300 - 20330

2007-08-11T08:17:00.002-07:00

BPEL Sensor ExceptionsORABPEL 20300 - 20330
Sensor Exceptions 20300 - 20330

ORABPEL-20300
severity: 10
type: error
name: Reports Error.
description: A problem occurred while processing reports data. {0}
fix: Please examine the log file to determine the problem.

ORABPEL-20301
severity: 10
type: error
name: Data Publisher failed.
description: The Reporting Data Publisher {0} failed.
fix: Please examine the log file for more details.

ORABPEL-20302
severity: 2
type: warning
name: JMS connection setup failed
description: A problem occurred while setting up a connection to the JMS Destination {0} using the connection factory {1}.
fix: Please verify the JMS configuration as well as the error to determine the problem.

ORABPEL-20303
severity: 8
type: error
name: JMS publish failed
description: An error occurred while publishing reporting data to the JMS destination \"{0} \".
fix: Please verify the JMS destination is valid.

ORABPEL-20304
severity: 8
type: error
name: JMS destination lookup failed
description: The JMS destination lookup failed. The related reporting data will not be published Please ensure the JNDI name {0) is valid.
fix: Please configure the JMS Destination or correct its JNDI name.

ORABPEL-20305
severity: 8
type: error
name: JMS connection factory lookup failed
description: The JMS connection factory lookup failed. The related reporting data will not be published Please ensure the JNDI name {0) is valid.
fix: Please verify the JMS configuration.

ORABPEL-20306
severity: 2
type: warning
name: JMS connection cleanup failed
description: A problem occurred while releasing the JNDI resources used to publish to the destination {0}.
fix: Please verify the JMS configuration as well as the error to determine the problem.

ORABPEL-20307
severity: 10
type: error
name: Custom data publisher could not be located
description: The custom data publisher class {0} could not be loaded.
fix: Please verify the class file and all dependencies can be loaded from the suitcase or the application classpath.

ORABPEL-20308
severity: 10
type: error
name: Custom data publisher initialization error
description: The custom data publisher class {0} could not be initialized properly.
fix: Please examine the log file for details.

ORABPEL-20309
severity: 10
type: error
name: Sensor name not defined
description: The sensor could not be registered because it has no name.
fix: Please specify the sensor name

ORABPEL-20310
severity: 10
type: error
name: Sensor name already in use.
description: The sensor \"{0}\" could not be registered because a sensor with the same name is already registered.
fix: Please specify a unique sensor name.

ORABPEL-20311
severity: 10
type: error
name: Invalid sensor specified in sensor-sensor action association.
description: The sensor-sensor action association for sensor \"{0}\", action \"{1}\" could not be created because no sensor named \"{2}\" exists in the registry.
fix: Please specify a valid sensor name in the association.

ORABPEL-20312
severity: 10
type: error
name: Invalid sensor action specified in sensor-sensor action association.
description: The sensor-sensor action association for sensor \"{0}\", action \"{1}\" could not be created because no sensor action named \"{2}\" exists in the registry.
fix: Please register the sensor action before specifying an assocation.

ORABPEL-20313
severity: 10
type: error
name: Sensor action name not defined
description: The sensor action could not be registered because it has no name.
fix: Please specify the sensor action name.

ORABPEL-20314
severity: 10
type: error
name: Sensor action name already in use.
description: The sensor action \"{0}\" could not be registered because a sensor action with the same name is already registered.
fix: Please specify a unique sensor action name.

ORABPEL-20315
severity: 10
type: error
name: Sensor registry error.
description: An error occurred while loading sensors and sensor actions for process {1), revision {2} in domain {0}.
fix: Please examine the log file for more details.

ORABPEL-20316
severity: 10
type: error
name: Missing sensor target.
description: No target was specified for sensor {0}.
fix: Please specify a target.

ORABPEL-20317
severity: 10
type: error
name: Invalid variable sensor target.
description: The target {1) for sensor {0} is invalid.
fix: Please specify a $ before the variable name and make sure the variable exists.

ORABPEL-20318
severity: 10
type: error
name: Invalid variable sensor.
description: The configuration for sensor {0} is missing.
fix: The element must be specified for variable sensors. Please complete the variable sensor definition.

ORABPEL-20319
severity: 10
type: error
name: Invalid variable sensor configuration.
description: Sensor {0} is a variable sensor but has activity or fault configurations defined.
fix: Please remove the unnecessary configuration elements.

ORABPEL-20320
severity: 10
type: error
name: Invalid fault sensor configuration.
description: Sensor {0} is a fault sensor but has activity or variable configurations defined.
fix: Please remove the unnecessary configuration elements.

ORABPEL-20321
severity: 10
type: error
name: Invalid activity sensor.
description: The configuration for sensor {0} is missing.
fix: The element must be specified for activity sensors. Please complete the activity sensor definition.

ORABPEL-20322
severity: 10
type: error
name: Invalid activity sensor configuration.
description: Sensor {0} is an activity sensor but has variable or fault configurations defined.
fix: Please remove the unnecessary configuration elements.

ORABPEL-20323
severity: 10
type: error
name: Invalid sensor kind.
description: Sensor {0} is invalid because {1} is an unrecognized sensor kind.
fix: Please specify a valid sensor kind.

ORABPEL-20324
severity: 10
type: error
name: Invalid sensor action.
description: Sensor action {0} is invalid because it publishes to a JMS destination but no destination has been specified.
fix: Please specify the JMS destination property in the sensor action.

ORABPEL-20325
severity: 10
type: error
name: Invalid sensor action.
description: Sensor action {0} is invalid because it publishes to a JMS destination but no connection factory has been specified.
fix: Please specify the JMS connection factory.

ORABPEL-20326
severity: 10
type: error
name: Invalid sensor action.
description: Sensor action {0} is invalid because it publishes to a custom publisher but no publisher class has been specified.
fix: Please specify the fully qualified class name of the custom data publisher.

ORABPEL-20327
severity: 10
type: error
name: Invalid publish type.
description: Sensor action {0} is invalid because {1} is an unrecognized publish type.
fix: Please specify a valid publish type.

ORABPEL-20328
severity: 10
type: error
name: Invalid sensor association.
description: Sensor action {0} is invalid because the associated sensor {1} cannot be found.
fix: Please ensure sensor names used in the sensor action file match those defined in the sensor file.

ORABPEL-20329
severity: 10
type: error
name: Invalid sensor action.
description: Sensor action {0} is invalid because the connection name is not specified.
fix: Please specify the connection name property in the sensor action.

ORABPEL-20330
severity: 10
type: error
name: JMS Adapter Sensor Action Publisher error.
description: The Sensor.xsd schema could not be loaded from the classpath.
fix: Please ensure the Sensor.xsd file has not been modified in any way.

ORABPEL-20330
severity: 10
type: error
name: JMS Adapter Sensor Action Publisher error.
description: The JMS Adapter could not be loaded from the classpath.
fix: Please ensure the JMS adapter has been properly deployed in the application server.

BPEL Dispatch Exceptions ORABPEL 05000 - 05006

2007-08-11T08:17:00.001-07:00

BPEL Dispatch Exceptions ORABPEL 05000 - 05006
Dispatch Exceptions 05000 - 05006

ORABPEL-05000
severity: 5
type: error
name: Cannot get dispatcher trace
description: Failed to fetch the dispatcher trace for engine \"{0}\"; the exception reported is: {1}

ORABPEL-05001
severity: 10
type: error
name: Message handler not registered
description: The message handler for class \"{0}\" has not been registered.

ORABPEL-05002
severity: 10
type: error
name: Message handle error
description: An exception occurred while attempting to process the message \"{0}\"; the exception is: {1}

ORABPEL-05003
severity: 10
type: error
name: No message local handler
description: No message local handler has been implemented for the message \"{0}\".

ORABPEL-05004
severity: 10
type: error
name: Dispatcher send error
description: An error occurred while sending a batch message to the dispatch queue. The exception is: {0}

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

ORABPEL-05006
severity: 10
type: error
name: Dispatcher schedule error
description: An error occurred while scheduling a batch message with the dispatcher. The exception is: {0}

BPEL Descriptor Exceptions ORABPEL 00500 - 00534

2007-08-11T08:16:00.002-07:00

BPEL Descriptor Exceptions ORABPEL 00500 - 00534
Descriptor Exceptions 00500 - 00534

ORABPEL-00500
severity: 10
type: error
name: Missing activation attribute
description: Missing activation attribute \"{0}\"; this attribute must contain a value in order for the process to initialize properly.

ORABPEL-00501
severity: 10
type: error
name: Archive descriptor not found
description: The archive descriptor file \"{0}\" was not found in the directory \"{1}\".

ORABPEL-00502
severity: 10
type: error
name: Empty archive property
description: The property \"{0}\" for archive manager \"{1}\" cannot be null or empty.
fix: Please check that all the properties defined for the archive manager \"{0}\" in the \"[CX_HOME]/server-default/system/config_archive.xml\" configuration file have a value.

ORABPEL-00503
severity: 10
type: error
name: Missing xpath function property
description: The property \"{0}\" for xpath function \"{1}\" cannot be null or empty.
fix: Please check that all the properties defined for the function \"{1}\" in the \"xpath-functions.xml\" configuration file have a value.

ORABPEL-00504
severity: 10
type: error
name: Domain descriptor not found
description: The process domain descriptor file \"{0}\" was not found in the directory \"{1} \".

ORABPEL-00505
severity: 10
type: error
name: Missing domain property
description: The property \"{0}\" has not been specified for this process domain.
fix: Please check the \"default.xml\" configuration file for the process domain. The property \"{0}\" should be specified therein.

ORABPEL-00506
severity: 10
type: error
name: Cannot backup domain descriptor
description: An attempt to backup the descriptor for domain \"{0}\" to the file \"{1}\" has failed. The exception reported is: \"{3}\".
fix: Please ensure that the directory \"{2}\" exists and is writable by the server.

ORABPEL-00507
severity: 10
type: error
name: Cannot save domain descriptor
description: An attempt to save the descriptor for domain \"{0}\" to the file \"{1}\" has failed. The exception reported is: \"{3}\".
fix: Please ensure that the directory \"{2}\" exists and is writable by the server.

ORABPEL-00508
severity: 10
type: error
name: Missing server property
description: The property \"{0}\" has not been specified in the server descriptor.
fix: Please check the configuration file \"{1}\" for the property \"{0}\".

ORABPEL-00509
severity: 10
type: error
name: Incompatible archive descriptor version
description: The version of the archive descriptor at \"{0}\" is incompatible with the current version of the process domain; the expected version is \"{1}\".
fix: Your archive descriptor has probably been configured for a previous release.

ORABPEL-00510
severity: 10
type: error
name: Incompatible domain descriptor version
description: The version of the domain descriptor at \"{0}\" is incompatible with the current version of the process domain; the expected version is \"{1}\".
fix: Your domain descriptor has probably been configured for a previous release.

ORABPEL-00511
severity: 10
type: error
name: Incompatible server descriptor version
description: The version of the server descriptor at \"{0}\" is incompatible with the current version of the process server; the expected version is \"{1}\".
fix: Your server descriptor has probably been configured for a previous release.

ORABPEL-00512
severity: 10
type: error
name: Incompatible xpath descriptor version
description: The version of the xpath descriptor at \"{0}\" is incompatible with the current version of the process domain; the expected version is \"{1}\".
fix: Your xpath descriptor has probably been configured for a previous release.

ORABPEL-00513
severity: 10
type: error
name: OraBPEL loader error
description: An error occurred while attempting to initialize the OraBPEL run-time system from file \"{0}\". The exception reported is: \"{1}\".
fix: Please check that the OraBPEL server descriptor file \"{0}\" exists.

ORABPEL-00514
severity: 10
type: error
name: Invalid domain descriptor
description: The file \"{0}\" is not a valid process domain descriptor file. The exception reported is: \"{1}\".
fix: Please make sure that the format of the process domain descriptor file is valid and restart the application server.

ORABPEL-00515
severity: 10
type: error
name: Invalid archive descriptor
description: The file \"{0}\" is not a valid archive descriptor file. The exception reported is: \"{1}\"
fix: Please make sure that the format of the archive descriptor file is valid and restart the application server.

ORABPEL-00516
severity: 10
type: error
name: Invalid xpath descriptor
description: The file \"{0}\" is not a valid xpath function descriptor file. The exception reported is: \"{1}\".
fix: Please make sure that the format of the xpath function descriptor file is valid and restart the application server.

ORABPEL-00517
severity: 10
type: error
name: Invalid Process Descriptor
description: The file \"{0}\" is not a valid process descriptor. The following exception occurred while loading the descriptor: \"{1}\".
fix: Please make sure that the process descriptor has specified all the necessary information in the specified format.

ORABPEL-00518
severity: 10
type: error
name: Error while creating property content handler
description: An error occurred while attempting to instantiate the property content handler class \"{0}\" for property name \"{1}\". The exception reported was: \"{2}\".
fix: Please check the implementation of your property content handler and deploy the class to the server.

ORABPEL-00519
severity: 10
type: error
name: Property content handler class not valid
description: The property content handler class \"{0}\" for property name \"{1}\" does not implement the IPropertyContentHandler interface. All content handlers must implement this interface.
fix: Please ensure that the class \"{0}\" implements the IPropertyContentHandler interface.

ORABPEL-00520
severity: 10
type: error
name: Cannot find property file
description: An error occurred while attempting to find the OraBPEL property file \"{0}\".
fix: Please check that the OraBPEL property file \"{0}\" exists.

ORABPEL-00521
severity: 10
type: error
name: Cannot lookup process object
description: The object bound to the name \"{0}\" has not been defined for the process \"{1} \".
fix: Please ensure that the name \"{0}\" refers to a set of properties in the process descriptor.

ORABPEL-00522
severity: 10
type: error
name: Cannot save suitcase descriptor
description: An attempt to save a suitcase descriptor to the file \"{0}\" has failed. The exception reported is: \"{2}\".
fix: Please ensure that the directory \"{1}\" exists and is writable by the server.

ORABPEL-00523
severity: 10
type: error
name: Missing process attribute
description: The process descriptor file \"{0}\" is missing the attribute \"{1}\". This attribute must contain a value in order for the process to initialize properly.
fix: Please ensure that the process descriptor file \"{0}\" has specified the necessary information in the specified format.

ORABPEL-00524
severity: 10
type: error
name: Process properties not found
description: The process properties \"{0}\" have not been defined for the process \"{1}\".
fix: Please ensure that the process properties \"{0}\" are defined in your process descriptor.

ORABPEL-00525
severity: 10
type: error
name: Missing task template attribute
description: The task template descriptor file \"{0}\" is missing the attribute \"{1}\". This attribute must contain a value in order for the process to initialize properly.
fix: Please ensure that the task template descriptor file \"{0}\" has specified the necessary information in the specified format.

ORABPEL-00526
severity: 10
type: error
name: Task template properties not found
description: The task properties \"{0}\" have not been defined for the task template \"{1} \".

ORABPEL-00527
severity: 5
type: error
name: Invalid task descriptor
description: The descriptor for the task template \"{0}\" is invalid; the exception is {1}

ORABPEL-00528
severity: 10
type: error
name: Cannot backup server descriptor
description: An attempt to backup the descriptor for the OraBPEL server to the file \"{0}\" has failed. The exception reported is: \"{2}\".
fix: Please ensure that the directory \"{1}\" exists and is writable by the server.

ORABPEL-00529
severity: 10
type: error
name: Cannot save server descriptor
description: An attempt to save the descriptor for the OraBPEL server to the file \"{0}\" has failed. The exception reported is: \"{2}\".
fix: Please ensure that the directory \"{1}\" exists and is writable by the server.

ORABPEL-00530
severity: 10
type: error
name: Incompatible message handler descriptor version
description: The version of the message handler descriptor at \"{0}\" is incompatible with the current version of the process domain; the expected version is \"{1}\".
fix: Your message handler descriptor has probably been configured for a previous release.

ORABPEL-00531
severity: 10
type: error
name: Missing message handler property
description: The property \"{0}\" for message handler \"{1}\" cannot be null or empty.
fix: Please check that all the properties defined for the handler \"{1}\" in the \"message-handlers.xml\" configuration file have a value.

ORABPEL-00532
severity: 10
type: error
name: Missing message handler attribute
description: The message handler element \"{0}\" is missing the attribute \"{1}\". This attribute must contain a value in order for the message handler to initialize properly.
fix: Please ensure that the message handler element \"{0}\" has specified the necessary information in the specified format.

ORABPEL-00533
severity: 10
type: error
name: Missing message handler reference
description: The message handler reference \"{1}\" cannot be found in the descriptor file \"{0}\".

ORABPEL-00534
severity: 10
type: error
name: Invalid message handler descriptor
description: The file \"{0}\" does not contain a valid message handler descriptor. The exception reported is: \"{1}\".
fix: Please check the format of the message handler descriptor file and restart the application server.

BPEL Compiler Exceptions ORABPEL 01000 - 01036

2007-08-11T08:16:00.001-07:00

BPEL Compiler Exceptions ORABPEL 01000 - 01036
Compiler Exceptions 01000 - 01036

ORABPEL-01000
severity: 10
type: error
name: Internal compiler error
description: An internal error has occurred while attempting to process the BPEL process file \"{0}\"; the exception is: {1}

ORABPEL-01001
severity: 10
type: error
name: Process descriptor not found
description: The BPEL process descriptor file \"{0}\" cannot be found.

ORABPEL-01002
severity: 10
type: error
name: Domain directory not found
description: The process cannot be deployed to domain \"{0}\" because the domain directory \"{1}\" cannot be found or cannot be written to.
fix: Please check your -deploy option value; \"{0}\" must refer to a domain that has been installed locally on your machine.

ORABPEL-01003
severity: 10
type: error
name: Failed to create build directory
description: Failed to create a build directory for the BPEL archive in \"{0}\"; exception reported is {1}

ORABPEL-01004
severity: 10
type: error
name: Failed to create classes directory
description: Failed to create the classes output directory for the BPEL archive in \"{0}\"; exception reported is {1}

ORABPEL-01005
severity: 10
type: error
name: Failed to compile classes
description: Failed to compile the generated BPEL classes for \"{0}\".

ORABPEL-01006
severity: 10
type: error
name: Missing build directory
description: The build directory for the BPEL process has not been specified.

ORABPEL-01007
severity: 10
type: error
name: Cannot access build directory
description: The build directory \"{0}\" for the BPEL process cannot be found or accessed.

ORABPEL-01008
severity: 10
type: error
name: Failed to include file
description: Failed to include the file \"{0}\" with the BPEL archive due to exception: {1}
fix: Please check that the file \"{0}\" exists and is readable.

<>{ "exception.01009.type", "internal-error" },
ORABPEL-01009
severity: 10
name: Class Not Found
description: Cannot find class {0}

<>{ "exception.01010.type", "internal-error" },
ORABPEL-01010
severity: 10
name: Process Generation Failed
description: {0}

ORABPEL-01011
severity: 10
type: error
name: Invalid Revision Tag
description: The specified revision tag \"{0}\" is invalid. Valid revision tags may contain the following characters: a letter, a digit or any of [\"$\", \"_\", \"-\", \".\"]. And its max length is 50.

ORABPEL-01012
severity: 10
type: error
name: file not found in suitcase
description: File \"{0}\" cannot be found in the current suitcase. File path must to be relative to the project directory.

ORABPEL-01013
severity: 10
type: error
name: BPEL process source not found
description: The \".bpel\" file for BPEL Process \"{0}\" cannot be found in the current directory or the specified sourcepath.

ORABPEL-01014
severity: 10
type: error
name: JBPEL process source not supported
description: JBPEL processes are not supported as of the RC-1 release; JBPEL functionality is now accessible via standard BPEL processes. For more information regarding JBPEL or assistance in porting your JBPEL flows to BPEL, contact \"support@collaxa.com\"

ORABPEL-01015
severity: 10
type: error
name: Multiple operations
description: For synchronous BPEL process, only one operation is supported in this version.

ORABPEL-01016
severity: 10
type: error
name: WSDL source not found
description: The \".wsdl\" file for BPEL Process \"{0}\" cannot be found in the current directory or the specified sourcepath.

ORABPEL-01017
severity: 10
type: error
name: Failed to get WSDL directory
description: Failed to get the directory which contains WSDL file \"{0}\", because \"{1}\". The WSDL file needs to be accessible from the file system.

ORABPEL-01018
severity: 10
type: error
name: Failed to copy file
description: Failed to copy file from \"{0}\" to \"{1}\", because \"{2}\".

ORABPEL-01019
severity: 10
type: error
name: WSDL reference error
description: If not referenced via HTTP, WSDL or XSD can only be referenced in the project directory or the subdirectory of the project directory. The file being imported \"{0}\", is not in project directory \"{1}\" or its subdirectory.

ORABPEL-01020
severity: 10
type: error
name: Failed to parse bpel source
description: Failed to parse bpel source \"{0}\", the error is: {1}

ORABPEL-01021
severity: 10
type: error
name: BPEL validation failed
description: BPEL source validation failed, the errors are: \n {0}.

ORABPEL-01022
severity: 10
type: error
name: BPEL syntax validation failed
description: BPEL syntax validation failed to validate \"{0}\", the error is: {1}

ORABPEL-01023
severity: 0
type: warning
name: BPEL validation has warnings
description: The following warnings were reported during validation: \n {0}

ORABPEL-01024
severity: 10
type: error
name: Cannot find operation in portType
description: The operation \"{0}\" is not found in portType \"{1}\".
fix: Please make sure that operation \"{0}\" exists.

ORABPEL-01025
severity: 10
type: error
name: Cannot find input message
description: The input message of operation \"{0}\" is not found in portType \"{1}\".
fix: Please make sure that \"message=\" is defined for the input of the operation.

ORABPEL-01026
severity: 10
type: error
name: Failed to create bpel validator
description: Failed to create bpel validator using schemas: \"{0}\". Error is \"{1}\".
fix: Please make sure schemas \"{0}\" are valid.

ORABPEL-01027
severity: 10
type: error
name: Cannot find part in message
description: Cannot find part \"{1}\" in messageType \"{0}\". Make sure the assign def is correct.

ORABPEL-01028
severity: 10
type: error
name: Missing propertyAlias
description: Cannot find propertyAlias definition which associates the correlation \"{0}\" of correlationSet \"{1}\" to messageType \"{2}\".
fix: Please define the mentioned propertyAlias in the WSDL file.

ORABPEL-01029
severity: 10
type: error
name: Missing bpel property definition in WSDL
description: Cannot find property definition for \"{0}\" in any of the WSDLs.
fix: Please define the mentioned bpel property in the WSDL file.

ORABPEL-01030
severity: 10
type: error
name: Missing bpel property definition in WSDL
description: Cannot generate debug model file \"{1}\" from input \"{0}\". Because \"{2}\".

ORABPEL-01031
severity: 10
type: error
name: WSDL generator cannot handle the number portTypes
description: WSDLGenerator cannot support \"{0}\"

ORABPEL-01032
severity: 10
type: error
name: Invalid process identifier
description: The specified process id \"{0}\" is invalid. Valid process identifiers may start with a letter, a \"$\" or \"_\" character; process characters (other than the first character) include a letter, a digit, a \"$\", a \"_\" or \"-\" character. And the max length is 100.
fix: Please make sure that the process identifier specified in the deployment descriptor conforms to the specified format.

ORABPEL-01033
severity: 10
type: error
name: deployment descriptor format error
description: Error when parsing the deployment descriptor \"{0}\", because \"{1}\"
fix: Fix the deployment descriptor

ORABPEL-01034
severity: 10
type: error
name: deployment descriptor validation error
description: Deployment descriptor is invalid. The errors are: {0}
fix: Please make the suggested fixes and recompile the BPEL project.

ORABPEL-01035
severity: 10
type: error
name: deployment descriptor validation warning
description: Validation of deployment descriptor genereated warnings: {0}

ORABPEL-01036
severity: 10
type: error
name: Cannot compute process guid
description: Failed to compute process guid using suitcase contents \"{0}\"; exception is: {1}

BPEL Admin Exceptions ORABPEL 00200 - 00234

2007-08-11T08:15:00.001-07:00

BPEL Admin Exceptions ORABPEL 00200 - 00234
Admin Exceptions 00200 - 00234

ORABPEL-00200
severity: 10
type: error
name: SOAP server URL not specified
description: The SOAP server URL for the OraBPEL server has not been specified in the configuration file \"{0}\".

ORABPEL-00201
severity: 10
type: error
name: Caller not permitted
description: Cannot return system authentication token for caller \"{0}\".

ORABPEL-00202
severity: 10
type: error
name: Invalid domain id
description: The domain identifier \"{0}\" is not valid. Domain identifiers may start with a letter, a \"$\" or \"_\" character; domain characters (other than the first character) include a letter, a digit, a \"$\", a \"_\" or \"-\" character. Additionally, the domain identifier \"xmllib\" may not be used; this identifier is reserved.

ORABPEL-00203
severity: 10
type: error
name: Invalid domain directory
description: The domain directory \"{0}\" does not match the domain identifier \"{1}\" retrieved from the configuration files. The domain directory name must match the domain identifier.

ORABPEL-00204
severity: 10
type: error
name: Missing domain id
description: The domain descriptor at \"{0}\" does not contain a domain identifier (attribute \"id\"). The domain derives its id from the descriptor, not the directory name.

ORABPEL-00205
severity: 10
type: error
name: Domain already exists
description: A domain with identifier \"{0}\" already exists at \"{1}\". Please specify another domain identifier.

ORABPEL-00206
severity: 10
type: error
name: Domain creation error
description: An exception occurred while attempting to create the domain \"{0}\" at path \"{1} \". The exception reported is: {2}

ORABPEL-00207
severity: 10
type: error
name: Domain create directory error
description: An exception occurred while attempting to create the domain directory \"{1}\" for domain \"{0}\". Please check that the directory does not already exist.

ORABPEL-00208
severity: 10
type: error
name: Maximum number of domains exceeded
description: Failed to create the domain \"{0}\"; the maximum number of domains ({1}) has been reached.

ORABPEL-00209
severity: 10
type: error
name: Domain id not found
description: The domain identifier \"{0}\" has not been registered with the server.

ORABPEL-00210
severity: 10
type: error
name: Domain ref not found
description: The domain ref \"{0}\" has not been registered with the server.

ORABPEL-00211
severity: 10
type: error
name: Error reading domain index
description: An exception occurred while reading the domain index from the datastore; the exception reported is: {0}
fix: Please check that: the machine hosting the datasource is physically connected to the network, and the connection pool properties as defined in the application server startup properties are valid. and the database schema for the OraBPEL server has been installed in the datasource.

ORABPEL-00212
severity: 10
type: error
name: Error updating domain index
description: An exception occurred while writing the domain index (id\"{0}\", ref \"{1}\") to the datastore; the exception reported is: {2}
fix: Please check that:
+ the machine hosting the datasource is physically connected to the network.
+ the connection pool properties as defined in the application server startup properties are valid.
+ the database schema for the OraBPEL server has been installed in the datasource.

ORABPEL-00213
severity: 10
type: error
name: Error writing domain index
description: An exception occurred while removing the domain index (id \"{0}\", ref \"{1}\") from the datastore; the exception reported is: {2}
fix: Please check that:
+ the machine hosting the datasource is physically connected to the network.
+ the connection pool properties as defined in the application server startup properties are valid.
+ the database schema for the OraBPEL server has been installed in the datasource.

ORABPEL-00214
severity: 10
type: error
name: OraBPEL server not initialized
description: The OraBPEL server has not finished initializing yet; the initialization process may be complete in a few moments.

ORABPEL-00215
severity: 10
type: error
name: Error while creating JDK adaptor
description: An error occurred while attempting to instantiate the JDK adaptor class \"{0}\" for runtime version \"{1}\". The exception reported was: {2}.
fix: Please check the implementation of your JDK adaptor and redeploy the class to the server.

ORABPEL-00216
severity: 10
type: error
name: JDK adaptor class incorrect interface
description: The JDK adaptor class \"{0}\" for runtime version \"{1}\" does not implement the IJDKAdaptor interface. All JDK adaptors must implement this interface.

ORABPEL-00217
severity: 10
type: error
name: JDK version not supported
description: The JDK version \"{0}\" is not supported by the OraBPEL domain runtime. Currently only JDK version 1.4 is supported.

ORABPEL-00218
severity: 10
type: error
name: Wrong Xalan version
description: An unsupported version of the Xalan library was detected in your classpath. The JDK 1.4.1 rt.jar currently bundles the 2.2D11 beta version of Xalan; OraBPEL requires the 2.5.0 release version.
fix: There are several ways to use a later version of Xalan-Java and override the one packaged with the JDK: For the SUN JDK 1.4, use the Endorsed Standards Override Mechanism. Place the xalan.jar, xercesImpl.jar, and xml-apis.jar in the JAVA_HOME/lib/endorsed directory, where JAVA_HOME is where the runtime software is installed. Use the -Xbootclasspath java commandline option to prepend the new xalan.jar, xercesImpl.jar, and xml-apis.jar to the boot class path. When running Xalan-Java: java -Xbootclasspath/p:PATH org.apache.xalan.xslt.Process where PATH is a colon seperated lists of the paths to the files xalan.jar, xercesImpl.jar, and xml-apis.jar (e.g. bin/xalan.jar:bin/xercesImpl.jar:bin/xml-apis.jar) containing the new-version of Xalan- Java.

ORABPEL-00219
severity: 10
type: error
name: Cannot instantiate class
description: Cannot instantiate an instance for the class \"{0}\". Please check that the OraBPEL runtime class \"{1}\" has been granted the necessary security permissions to access the specified class.

ORABPEL-00220
severity: 10
type: error
name: Wrong platform adaptor interface
description: The class \"{0}\" (for the platform adaptor for platform \"{1}\") does not implement the IPlatformAdaptor interface. All platform adaptors used by the OraBPEL server must implement this interface.

ORABPEL-00221
severity: 10
type: error
name: Error while creating platform adaptor
description: An error has occurred while attempting to instantiate the class \"{0}\" as the adaptor for platform \"{1}\". The exception reported is: {2}

ORABPEL-00222
severity: 10
type: error
name: Platform adaptor class not found
description: The class for platform adaptor \"{0}\" (platform \"{1}\") cannot be found.

ORABPEL-00223
severity: 10
type: error
name: Maximum number of namespaces exceeded
description: Failed to create the namespace \"{0}\"; the maximum number of namespaces ({1}) has been reached.

ORABPEL-00224
severity: 10
type: error
name: Could not find namespace index
description: Invalid namespace index \"{0}\".

ORABPEL-00225
severity: 10
type: error
name: Could not read namespace index from db
description: Could not get the namespace index, the reason is {0}

ORABPEL-00226
severity: 10
type: error
name: Could not write namespace index
description: Could not insert the namespace \"{0}\", index \"{1}\", the reason is {2}

ORABPEL-00227
severity: 10
type: error
name: Wrong database adaptor interface
description: The class \"{0}\" (for the database adaptor for \"{1}\", datasource \"{2}\") does not implement the IDatabaseAdaptor interface. All database adaptors used by the OraBPEL server must implement this interface.

ORABPEL-00228
severity: 10
type: error
name: Error while creating database adaptor
description: An error has occurred while attempting to instantiate the class \"{0}\" as the database adaptor for \"{1}\", datasource \"{2}\". The exception reported is: {3}

ORABPEL-00229
severity: 10
type: error
name: Unknown database adaptor classname
description: The database adaptor classname for \"{0}\", datasource \"{1}\" has not been specified.

ORABPEL-00230
severity: 10
type: error
name: Missing adaptor resource configuration
description: The adaptor resource file \"{0}\" for the application server \"{1}\" cannot be found in the current classpath. This resource file contains all the JNDI mappings required for the BPEL process domain to initialize. The application server \"{1}\" may not be currently supported by OraBPEL.

ORABPEL-00231
severity: 10
type: error
name: Error while creating adaptor manifest
description: An error has occurred while attempting to instantiate the class \"{0}\" as the adaptor manifest for \"{1}\", datasource \"{2}\". The exception reported is: {3}

ORABPEL-00232
severity: 10
type: error
name: Wrong adaptor manifest interface
description: The class \"{0}\" (for the adaptor manifest for \"{1}\", datasource \"{2}\") does not implement the IServerAdaptorManifest interface. All adaptor manifests used by the OraBPEL server must implement this interface.

ORABPEL-00233
severity: 10
type: error
name: Unknown adaptor manifest classname
description: The adaptor manifest classname for \"{0}\", datasource \"{1}\" has not been specified.

ORABPEL-00234
severity: 10
type: error
name: Malformed server url
description: The SOAP server url \"{0}\" for the BPEL engine is malformed.

BPEL WSDL Validation Exceptions ORABPEL 01500 - 01507

2007-08-11T08:14:00.002-07:00

BPEL WSDL Validation Exceptions ORABPEL 01500 - 01507
WSDL Validation Exceptions 01500 - 01507

ORABPEL-01500
severity: 10
type: error
name: undefined WSDL message
description: Message \"{1}\" is not defined in WSDL at \"{0}\".
fix: Please make sure the spelling of the message name is correct and the WSDL import is complete.

ORABPEL-01501
severity: 10
type: error
name: undefined part element
description: In WSDL at \"{0}\", message part element \"{1}\" is not defined in any of the schemas.
fix: Please make sure the spelling of the element QName is correct and the WSDL import is complete.

ORABPEL-01502
severity: 10
type: error
name: undefined part type
description: In WSDL at \"{0}\", message part type \"{1}\" is not defined in any of the schemas.
fix: Please make sure the spelling of the type QName is correct and the WSDL import is complete.

ORABPEL-01503
severity: 10
type: error
name: unknown wsdl extension
description: In WSDL at \"{0}\", extension element \"{1}\" is not known. Ignore this element.
fix: Please make sure the spelling of the element is correct and the WSDL import is complete.

ORABPEL-01504
severity: 10
type: error
name: Schema validation error
description: In WSDL at \"{0}\", schema validation error {1}.
fix: Please make sure the defined schemas are correct.

ORABPEL-01505
severity: 10
type: error
name: notification operation not supported
description: In WSDL at \"{0}\", operation \"{2}\" of portType \"{1}\" is a notification operation (The endpoint sends a message), which is not supported in this version. See chapter 2.4 of WSDL spec 1.1.
fix: Make sure the operation is \"one-way\" type or \"request-response\" type.

ORABPEL-01506
severity: 10
type: error
name: solicit-response operation not supported
description: In WSDL at \"{0}\", operation \"{2}\" of portType \"{1}\" is a Solicit-response operation (The endpoint sends a message, and receives a correlated message), which is not supported in this version. See chapter 2.4 of WSDL spec 1.1.
fix: Make sure the operation is \"one-way\" type or \"request-response\" type.

ORABPEL-01507
severity: 10
type: error
name: invalid wsdl root element
description: In WSDL at \"{0}\", the root element is \"{1}\".
fix: Make sure the document is a valid wsdl document.

BPEL Adapter Exceptions ORABPEL 03000 - 03015

2007-08-11T08:14:00.001-07:00

BPEL Adapter Exceptions ORABPEL 03000 - 03015
Adapter Exceptions 03000 - 03015

ORABPEL-03000
severity: 10
type: error
name: Cannot bind adaptors
description: The process domain was unable to bind the connection/database adaptors for \"{0} \", datasource \"{1}\". The exception reported is: {2}
fix: Please check that the machine hosting the datasource is physically connected to the network. Additionally check that the connection pool properties as defined in the application server startup properties are valid.

ORABPEL-03001
severity: 10
type: error
name: Cannot lookup datasource type
description: The process domain was unable to determine the database type. The version table contains the vendor type for the current datasource. The exception reported is: {0}
fix: Please check that:
+ the machine hosting the datasource is physically connected to the network.
+ the connection pool properties as defined in the application server startup properties are valid.
+ the database schema for OraBPEL has been installed in the datasource.

ORABPEL-03002
severity: 10
type: error
name: Cannot lookup db schema version
description: The server was unable to lookup the database schema version. The version table is used to verify that the proper database schema has been installed for use with the server. The exception reported is: {0}
fix: Please check that:
+ the machine hosting the datasource is physically connected to the network.
+ the connection pool properties as defined in the application server startup properties are valid.
+ the database schema for OraBPEL has been installed in the datasource.

ORABPEL-03003
severity: 10
type: error
name: Incorrect db schema version
description: The database schema version \"{0}\" from the database does not match the version \"{1}\" expected by the server.
fix: The database schema currently in place has probably been configured for a previous release; please re-install the database schema and try to start the server again.

ORABPEL-03004
severity: 10
type: error
name: Missing datasource type
description: The database table \"version\" does not contain a datasource vendor type. This value is used by the process domain to initialize resources used to connect to the JDBC datasource.
fix: The database schema may have been modified by hand. Please re-install the database schema and try to start the process domain again.

ORABPEL-03005
severity: 10
type: error
name: Missing db schema version
description: The database table \"version\" does not contain a version guid. This guid is used by the server to verify that the correct database schema is currently installed.
fix: The database schema may have been modified by hand. Please re-install the database schema and try to start the server again.

ORABPEL-03010
severity: 10
type: error
name: Error while creating adaptor manifest
description: An error has occurred while attempting to instantiate the class \"{0}\" as the adaptor manifest for \"{1}\", datasource \"{2}\". The exception reported is: {3}

ORABPEL-03011
severity: 10
type: error
name: Wrong adaptor manifest interface
description: The class \"{0}\" (for the adaptor manifest for \"{1}\", datasource \"{2}\") does not implement the IAdaptorManifest interface. All adaptor manifests used by the OraBPEL server must implement this interface.

ORABPEL-03012
severity: 10
type: error
name: Unknown adaptor manifest classname
description: The adaptor manifest classname for \"{0}\", datasource \"{1}\" has not been specified.

ORABPEL-03013
severity: 10
type: error
name: Cannot instantiate class
description: Cannot instantiate an instance for the class \"{0}\". Java classes that need to be dehydrated/rehydrated within the OraBPEL server must implement the java.io.Serializable interface. These classes must implement a default constructor.

ORABPEL-03014
severity: 10
type: error
name: Cannot install PointBase schema
description: The process domain was unable to create the schema for PointBase. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Additionally check that the connection pool properties as defined in the application server startup properties are valid.

ORABPEL-03015
severity: 10
type: error
name: Cannot install Oracle Lite schema
description: The process domain was unable to create the schema for Oracle Lite. The exception reported is: {0}
fix: Please check that the machine hosting the datasource is physically connected to the network. Additionally check that the connection pool properties as defined in the application server startup properties are valid.

BPEL Test Exceptions ORABPEL 20000 - 20299

2007-08-11T08:13:00.001-07:00

BPEL Test Exceptions ORABPEL 20000 - 20299
Test Exceptions 20000 - 20299

ORABPEL-20000
severity: 10
type: error
name: Assertion execution error.
description: The variable assertion xpath \"{0}\" at activity \"{1}\" failed to execute.
fix: Please ensure the xpath query is valid and namespace qualified.

ORABPEL-20001
severity: 10
type: error
name: Assertion execution error.
description: A problem occurred while converting the assertion value \"{0}\" to a number at activity \"{1}\".
fix: Please change the value to be a number or do a string comparison.

ORABPEL-20002
severity: 10
type: error
name: Assertion execution error.
description: The variable assertion xpath \"{0}\" at activity \"{1}\" failed to select a value.
fix: Please ensure the xpath query is valid and namespace qualified.

ORABPEL-20003
severity: 10
type: error
name: Test results missing.
description: The test results for this process instance could not be located.
fix: Please try to re-run the test case or contact your system administrator.

ORABPEL-20004
severity: 10
type: error
name: Assertion execution error.
description: The specified comparison type \"{0}\" at activity \"{1}\" is not valid.
fix Please specify a valid comparison type

ORABPEL-20005
severity: 10
type: error
name: An external call failed.
description: An error occurred attempting to notify call \"{0}\" at activity \"{1}\".
fix Please examine the log file and make the necessary changes or contact your system administrator.

ORABPEL-20006
severity: 10
type: error
name: The test driver could not be located.
description: An error occurred while reading the test case for suite \"{0}\", test \"{1} \".
fix Please ensure the test was deployed successfully. If the problem persists, please try to re-deploy the test case.

ORABPEL-20007
severity: 10
type: error
name: The test driver could not be parsed.
description: An error occurred while trying to parse the test driver for suite \"{0}\", test \"{1}\". {2}
fix Please ensure the file is valid. Please attempt to redeploy the test case to view any errors.

ORABPEL-20008
severity: 10
type: error
name: An included message could not be parsed.
description: An error occurred while trying create the initiation payload for test \"{0}\" in suite \"{1}\". {2}
fix Please ensure the test is valid and has been deployed correctly.

ORABPEL-20009
severity: 10
type: error
name: An error occurred while generating the initiation message.
description: An error occurred while trying to parse an included message \"{0}\" in suite \"{1}\".
fix Please ensure the test is valid and has been deployed correctly. If you are using message updates, please make sure they have been defined correctly.

ORABPEL-20010
severity: 10
type: error
name: Invalid operation.
description: The operation \"{0}\" is not valid for process \"{1}\", revision \"{2}\".
fix Please ensure the operation exists and corresponds to a createInstance receive activity in the BPEL process.

ORABPEL-20011
severity: 10
type: error
name: Instance initiation error.
description: An error occurred while launching an instance for suite \"{0}\", test \"{1} \".
fix Please examine the log file for details or contact the system administrator.

ORABPEL-20012
severity: 10
type: error
name: Test run data retrieval error.
description: An error occurred while retrieving data for the test run.
fix Please examine the log file for details or contact the system administrator.

ORABPEL-20013
severity: 10
type: error
name: Invalid results document.
description: An error occurred while parsing the results document.
fix Please examine the log file for details or contact the system administrator.

ORABPEL-20014
severity: 10
type: error
name: Partner Emulation Failed.
description: An error occurred while emulating partner \"{0}\", role \"{1}\", operation \"{2} \".
fix Please ensure the partner details are correct in the test driver specified in test suite \"{2}\", location \"{3}\" and examine the log file for details.,

ORABPEL-20015
severity: 10
type: error
name: Partner Emulation Failed.
description: An error occurred while construcing the partner emulation for activity \"{0}\". Message part \"{1}\" could not be created
Fix Please examine the test case driver specified in test suite \"{2} \", location \"{3}\" for errors.

ORABPEL-20016
severity: 10
type: error
name: The test run timed out.
description: This happens when test instances do not complete within the allotted time.
fix Please go to the BPEL Console to determine why some tests have not completed.

ORABPEL-20017
severity: 10
type: error
name: The specified duration is invalid.
description: The duration \"{0}\" is invalid. {1}
fix Please correct the test driver specified in test suite \"{2}\", location \"{3}\" and redeploy the test case,

ORABPEL-20018
severity: 10
type: error
name: The specified message content is invalid.
description: At activity \"{0}\", the emulated message content is invalid.
fix Please redeploy the test case specifid in test suite \"{1}\", location \"{2}\" to view driver errors.

ORABPEL-20019
severity: 10
type: error
name: The expected xml content file was not found.
description: At activity \"{0}\", the expected xml file \"{1}\" could not be found.
fix Please ensure this file has been deployed under the \"messages\" directory.

ORABPEL-20020
severity: 10
type: error
name: XML comparison error.
description: At activity \"{0}\", an unexpected error occurred while executing an XML assertion.
fix Please ensure your test driver file is specified correctly.

ORABPEL-20021
severity: 10
type: error
name: Invalid XPath.
description: At activity \"{0}\", the xpath expression \"{1}\" did not select an element.
fix When doing XML comparsions, please ensure the specified xpath selects an element, or the entire document.

ORABPEL-20022
severity: 10
type: error
name: Driver Generation Error.
description: An unexpected error occurred while generating the test driver.
fix Please ensure the process instance has completed and is valid. Also ensure that the audit trail logging level is set to \"development\".

ORABPEL-20023
severity: 10
type: error
name: Driver Generation Error. Instance still in progress.
description: An error occurred while generating the test driver. Test drivers may only be generated when the instance has completed.
fix Please wait for the instance to complete and then try again.

ORABPEL-20024
severity: 10
type: error
name: Remote deployment failed due to validation errors.
description: Test suite \"{0}\" failed to deploy:\n{1}

ORABPEL-20025
severity: 10
type: error
name: Invalid partner emulation settings.
description Error occurred in test suite \"{0}\", location \"{1}\". While emulating\n" + "activity \"{2}\", the \"testSuite\" or \"testLocation\" parameter was not set.
fix Please set both the testSuite and testLocation attributes of the \"emulate\" element in the test case.

ORABPEL-20026
severity: 10
type: error
name: Test Details not found.
description No test information was found for instance {0}
fix Please ensure the instance is a test case before trying to retrieve test case information.

ORABPEL-20027
severity: 10
type: error
name: Expected XML content not found.
description At activity \"{0}\", no XML content was found while performing an XML assertion.
fix Please ensure that the expected XML content is provided inline or the assertion points to a valid file.

ORABPEL-20028
severity: 10
type: error
name: An error occurred while loading test details.
description An I/O error occurred while loading test details using the where condition {0}. The reported error is {1}.
fix Please examine the error and ensure the data-source is operating properly.

ORABPEL-20029
severity: 10
type: error
name: An error occurred while loading test details.
description An XML parsing error occurred while loading test details for instance {0}. The reported error is {1}.
fix Please do not modify the test_results table manually.

ORABPEL-20030
severity: 10
type: error
name: No initiation operation.
description No initiation section could be found for test defined in suite \"{0}\", file \"{1)\".
fix An initiation section must be provided in a test case or included test driver.

ORABPEL-20200
severity: 10
type: error
name: Deployment failed.
description The attribute \"{0}\" is mandatory.\n Please set this attribute in the task.
fix Please provide this attribute.

ORABPEL-20201
severity: 10
type: error
name: Deployment failed.
description No process deployment could be found for \"{0}\", revision \"{1}\" in domain \"{2}\".
fix Please deploy the process and then try to deploy the tests again. /* { "DEPLOYTEST_suitedir_creation_error", "Deployment failed. The deployment directory \n{0}\n could not be created. { "DEPLOYTEST_suitedir_writable_error", "Deployment failed. The deployment directory \n{0}\n is not a directory or is not writable. */

ORABPEL-20202
severity: 10
type: error
name: Deployment failed.
description Deployment directory \"{0}\" could not be created.
fix Please ensure the parent directory is writable.

ORABPEL-20203
severity: 10
type: error
name: Deployment failed.
description The test files could not be copied to directory \"{0} \".
fix Error message: {1}

ORABPEL-20296
severity: 10
type: error
name: Message update error.
description An error occurred while applying message updates. The XPath \"{0}\" did not select at least one element or attribute.
fix lease check the message namespace and structure to be sure the XPath will select a node.

ORABPEL-20297
severity: 10
type: error
name: An error occurred while deploying the test suite.
description An XML parsing error occurred while storing the test definition for process \"{0}\", revision \"{1}\", test suite \"{2}\". The reported error is {3}.
fix Please ensure the data source is configured correctly. Examine the error message for more details.

ORABPEL-20298
severity: 10
type: error
name: An error occurred while loading test definition.
description An XML parsing error occurred while loading the testdefinition for process \"{0}\", revision \"{1}\", test suite \"{2}\", location \"{3}\". The reported error is {4}."},
Please do not modify the test_results table manually."

ORABPEL-20299
severity: 10
type: error
name: The test suite could not be located.
description: An error occurred while locating the test suite \"{2}\" for process \"{0}\", revision \"{1}\".
fix Please ensure the test suite has been deployed to the server for this process.

BPEL XML Exceptions ORABPEL 09000 - 09021

2007-08-11T08:12:00.001-07:00

BPEL XML Exceptions ORABPEL 09000 - 09021
XML Exceptions 09000 - 09021

ORABPEL-09000
severity: 10
type: error
name: Cannot copy class files
description: Cannot copy generated XML schema classes from \"{0}\" to \"{1}\". The exception reported is: {2}

ORABPEL-09001
severity: 10
type: error
name: Cannot copy source files
description: Cannot copy generated XML schema java source files from \"{0}\" to \"{1}\". The exception reported is: {2}

ORABPEL-09002
severity: 10
type: error
name: File process error
description: Error processing file \"{0}\", because \"{1}\".
fix: Please ensure that the input \"{0}\" is available and valid.

ORABPEL-09003
severity: 10
type: error
name: Failed to normalize name
description: Failed to normalize the name \"{0}\".
fix: Please ensure that the name \"{0}\" is available and valid.

ORABPEL-09004
severity: 10
type: error
name: Failed to marshall object
description: Failed to marshall the class \"{0}\" to XML. The exception reported is: {1}

ORABPEL-09005
severity: 10
type: error
name: Failed to unmarshall object
description: Failed to unmarshall the class \"{0}\" from XML. The exception reported is: {1}

ORABPEL-09006
severity: 10
type: error
name: Incompatible schema object version
description: The XML schema class \"{0}\" has been compiled with an older version of SCHEMAC; the BPEL process domain you have deployed the class to cannot use the helper classes generated for this class.
fix: Please recompile your XML schema using the SCHEMAC tool bundled with the current process domain.

ORABPEL-09007
severity: 10
type: error
name: Error while instantiating marshaller
description: An error has occurred while attempting to instantiate the XML marshaller/unmarshaller class \"{0}\"; the exception reported is: {1}

ORABPEL-09008
severity: 10
type: error
name: Wrong marshaller interface
description: The class \"{0}\" does not implement the com.collaxa.cube.engine.xml.IMarshaller interface. All XML marshallers used in the BPEL domain must implement this interface.

ORABPEL-09009
severity: 10
type: error
name: Wrong schema registry interface
description: The class \"{0}\" (for the runtime schema registry) does not implement the ISchemaRegistry interface. All schema registries used by the runtime must implement this interface.

ORABPEL-09010
severity: 10
type: error
name: Error while creating schema registry
description: An error has occurred while attempting to instantiate the class \"{0}\" as the runtime schema registry. The exception reported is: {1}

ORABPEL-09011
severity: 10
type: error
name: Unknown schema registry classname
description: The classname for the runtime schema registry has not been specified.

ORABPEL-09012
severity: 10
type: error
name: Unmarshaller not found
description: The XML unmarshaller for class \"{0}\" cannot be found. Every scope type used in a process must provide an XML unmarshaller.
fix: Please check that an unmarshaller for the class \"{0}\" has been registered properly with the process domain during process initialization.

ORABPEL-09013
severity: 10
type: error
name: SAX exception
description: SAX exception occurred when parsing \"{0}\", because \"{1}\".
fix: Please ensure that the input \"{0}\" is available and valid.

ORABPEL-09014
severity: 10
type: error
name: Cannot resolve type
description: Type \"{1}\" of \"{0}\" cannot be resolved.
fix: Please ensure that the input XML file is syntactically correct.

ORABPEL-09015
severity: 10
type: error
name: Class to QName mapping failure
description: TypeManager could not map the class name \"{0}\" to QName because \"{1}\"
fix: Please ensure the XML schema type \"{0}\" is valid.

ORABPEL-09016
severity: 10
type: error
name: Class name to QName mapping failure
description: TypeManager could not map the class name \"{0}\" to QName because \"{1}\"
fix: Please ensure the XML schema type \"{0}\" is valid.

ORABPEL-09017
severity: 10
type: error
name: QName to java class mapping failure
description: TypeManager could not map the QName \"{0}\" to java class because \"{1}\"
fix: Please ensure the XML schema type \"{0}\" is valid.

ORABPEL-09018
severity: 10
type: error
name: Failed to create XML parser
description: Failed to create XML parser.
fix: This error might be related to CLASSPATH configuration.

ORABPEL-09019
severity: 10
type: error
name: WSDL or jbpel file not valid
description: Error processing file \"{0}\", because {1}.
fix: Please ensure that the input WSDL or jbpel file \"{0}\" is available and valid.

ORABPEL-09020
severity: 10
type: error
name: Missing argument
description: Missing expected filename/classname argument.
fix: Please type \"{0} -help\" for more information.

ORABPEL-09021
severity: 10
type: error
name: XML Schema \"include\" is not currently supported
description: XSD file \"{0}\" is trying to include XSD file \"{1}\". Schemac does not currently support \"include\".
fix: Schemac does support \"import\". You can change \"{0}\" to use \"import\", or you can physically include \"{1}\" in \"{0}\".

BPEL Messaging Exceptions ORABPEL 08500 - 08512

2007-08-11T08:11:00.000-07:00

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.

BPEL XSD Exceptions ORABPEL 09700 - 09716

2007-08-11T07:57:00.000-07:00

BPEL XSD Exceptions ORABPEL 09700 - 09716
XSD Exceptions 09700 - 09716

ORABPEL-09700
severity: 10
type: error
name: Error loading xsd
description: Error while loading xsd file from location \"{0}\". The reason is {1}.
fix: Please verify the xsd location.

ORABPEL-09701
severity: 10
type: error
name: Error loading schemas from wsdl
description: Error while loading schemas from wsdl file at location \"{0}\". The reason is {1}.
fix: Please verify the schemas defined in wsdl.

ORABPEL-09702
severity: 10
type: error
name: Error creating url for wsdl/xsd
description: Error while creating url for a wsdl/xsd location path, the base url is \"{0}\", the import location URI is \"{1}\". The exception is {2}.
fix: Please verify the base url and the import location URI path.

ORABPEL-09703
severity: 10
type: error
name: Cannot resolve type
description: Cannot resolve type \"{0}:{1}\" from the following schemas {2}
fix: Please make sure that the type \"{0}:{1}\" is correct and defined in one of the schemas.

ORABPEL-09704
severity: 10
type: error
name: Invalid xpath query
description: According to BPEL4WS spec 1.1, section 14.3, the xpath query \"{0}\" is invalid, path expressions must start from the root element prefixed with \"/\".
fix: Please make sure that your xpath query starts with \"/{1}\" which is the root.

ORABPEL-09705
severity: 10
type: error
name: Couldn't initialize variable
description: Error occurred while initializing BPEL variable \"{0}\" the schema processor could not find element \"{1}\", in the following schemas: {2}
fix: Please make sure that the element \"{1}\" is valid in your wsdl.

ORABPEL-09706
severity: 10
type: error
name: Couldn't initialize variable
description: Error occurred while initializing BPEL variable \"{0}\" at line {1}, the schema processor could not find type \"{2}\" for part \"{3}\", in the following schemas: {4}
fix: Please make sure that the type \"{2}\" is valid in your wsdl.

ORABPEL-09707
severity: 10
type: error
name: Failed to initialize bpel variable
description: Could not initialize variable \"{0}\", {1} at line {2}.
fix: Please make sure that the step is valid.

ORABPEL-09708
severity: 10
type: error
name: Invalid schema
description: Schema defined in location \"{0}\" is invalid. The targetNamespace of this schema is {1}, there are some unresolved types/elements in this schema.
fix: Please make sure that these unresolved schema components are defined and imported/included correctly for this schema.

ORABPEL-09709
severity: 10
type: error
name: Error adding schema to the grammar pool
description: Couldn't add schema \"{0}\" to the schema grammar pool. The reason is {1}
fix: Please make sure that this schema is valid.

ORABPEL-09710
severity: 10
type: error
name: Invalid xml document.
description: According to the xml schemas, the xml document is invalid. The reason is: {0}
fix: Please make sure that the xml document is valid against your schemas.

ORABPEL-09711
severity: 10
type: error
name: Error getting xml schemas for a BPEL process
description: Error while loading xml schemas for BPEL process \"{0}\". The reason is {1}.
fix: Please verify the schemas defined for this process.

ORABPEL-09713
severity: 10
type: error
name: IO Error in generating or parsing xml schemas for a BPEL process
description: IO Error in generating or parsing xml schemas for a BPEL process. The reason is {0}.
fix: Please verify the file reading/writing permission.

ORABPEL-09714
severity: 10
type: error
name: Name attribute in XSD is not defined
description: Name attribute of {0} of {1} at {2} is not defined.
fix: Please verify the XSD.

ORABPEL-09715
severity: 10
type: error
name: Global declaration/definition duplicated
description: Global {0} declaration/definition of name {1} are duplicated at the following locations:{2}
fix: Please verify the related XSD and WSDL files.

ORABPEL-09716
severity: 10
type: error
name: Oracle XDK XSD validation error found
description: Oracle XDK XSD validation error found: {0}
fix: "Please verify the related XSD and WSDL files. Users can turn this feature off by adding a System Property of name +"oracle.bpel."+DescriptorDefs.CFG_xdk_xsd_validation + or adding a property entry of name +DescriptorDefs.CFG_xdk_xsd_validation + to 'bpel.xml' file

BPEL Agent Exceptions ORABPEL 03400 - 03411

2007-08-11T07:56:00.002-07:00

BPEL Agent Exceptions ORABPEL 03400 - 03411
Agent Exceptions 03400 - 03411

ORABPEL-03400
severity: 10
type: error
name: Error while creating activation job
description: An error occurred while attempting to instantiate the activation job class \"{0}\" for protocol \"{1}\". The exception reported was: \"{2}\".
fix: Please fix the error and redeploy the class to the server.

ORABPEL-03401
severity: 10
type: error
name: Unknown activation job classname
description: No activation job classname has been associated with protocol \"{0}\".
fix: Please check the \"mail.store.protocol\" property for your mail service.

ORABPEL-03402
severity: 10
type: error
name: Error while creating activation scheduler
description: An error occurred while attempting to instantiate the activation scheduler class \"{0}\" for type \"{1}\". The exception reported was: \"{2}\".
fix: Please fix the error and redeploy the class to the server.

ORABPEL-03403
severity: 10
type: error
name: Unknown activation scheduler classname
description: No activation scheduler classname has been associated with activation type \"{0} \".
fix: Please check the type attribute of the activation property in your process descriptor.

ORABPEL-03404
severity: 10
type: error
name: Activation scheduler filter class not valid
description: The activation scheduler class \"{0}\" for type \"{1}\" does not implement the IActivationScheduler interface. All schedulers must implement this interface.
fix: Please ensure that the class \"{0}\" implements the IActivationScheduler interface.

ORABPEL-03405
severity: 10
type: error
name: Cannot lookup scheduler
description: Cannot lookup the scheduler for agent \"{0}\", group \"{1}\". The exception reported is: \"{2}\".

ORABPEL-03406
severity: 10
type: error
name: Missing mail driven process property
description: The Mail Driven BPEL Process receiver has not been passed all the necessary parameters required for successful initialization. The missing property is \"{0}\".
fix: Please ensure that property values are supplied for the \"mail.user\", \"mail.password\" and \"mail.host\" properties.

ORABPEL-03407
severity: 10
type: error
name: Error while creating mail filter
description: An error occurred while attempting to instantiate the mail filter class \"{0}\". The exception reported was: \"{1}\".
fix: Please fix the error and redeploy the class to the server.

ORABPEL-03408
severity: 10
type: error
name: Mail filter class not valid
description: The mail filter class \"{0}\" does not implement the IMailFilter interface. All mail filter must implement this interface.
fix: Please ensure that the class \"{0}\" implements the IMailFilter interface.

ORABPEL-03409
severity: 10
type: error
name: Engine agent not found
description: The engine agent \"{0}\" has not been registered with the domain.

ORABPEL-03410
severity: 10
type: error
name: Error while creating agent
description: An error occurred while attempting to instantiate the agent class \"{0}\". The exception reported was: \"{1}\".

ORABPEL-03411
severity: 10
type: error
name: Agent class not valid
description: The agent class \"{0}\" does not implement the IAgent interface. All agents managed by the system must implement this interface.

BPEL WSIL Exceptions ORABPEL 13000 - 13008

2007-08-11T07:56:00.001-07:00

BPEL WSIL Exceptions ORABPEL 13000 - 13008
WSIL Exceptions 13000 - 13008

ORABPEL-13000
severity: 10
type: error
name: WSIL Resource bundles not found
description: The resource bundles for WSIL browser cannot be found.

ORABPEL-13001
severity: 10
type: error
name: Directory read failure
description: The directory \"{0}\" cannot be found or is not readable.

ORABPEL-13002
severity: 10
type: error
name: Generic WSIL generation failure
description: WSIL Generation failed. Please make sure that the adapters are correctly deployed. Please also check that the adapter specific jar files are avaialable to runtime (applications.xml). Also pl check the server logs

ORABPEL-13003
severity: 10
type: error
name: Adapter has not been deployed
description: The adapters are not correctly deployed.

ORABPEL-13004
severity: 10
type: error
name: Channel corresponding to event cannot be found.
description: Channel corresponding to event cannot be found. Please make sure that channel has been created using Application Explorer.

ORABPEL-13005
severity: 10
type: error
name: Incorrect WSDL Fiel name specified.
description: The WSDL file name or directory is incorrect. There has been an underlying transformation exception, please check logs.

ORABPEL-13006
severity: 10
type: error
name: WSDL Generation failure.
description: WSDL Generation failure. There has been an underlying error, please check logs.

ORABPEL-13007
severity: 10
type: error
name: Resource exception from legacy adapter.
description: Resource exception from legacy adapter. There has been an underlying error, please check logs.

ORABPEL-13008
severity: 10
type: error
name: Resource exception from applications adapter.
description: Resource exception from applications adapter. There has been an underlying error, please check logs.

BPEL DOM Exceptions ORABPEL 09200 - 09250

2007-08-11T07:54:00.000-07:00

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}\" and verify the \"from\" part.

ORABPEL-09203
severity: 10
type: error
name: The value is invalid.
description: Error in expression: value is empty at line \"{1}\". The XPath expression : \"{0}\" returns zero node, when applied to document shown below:\n{2}
fix: Please check the BPEL source at line number \"{1}\" and verify the \"from\" part xpath query.

ORABPEL-09204
severity: 10
type: error
name: The from value is invalid.
description: According to BPEL4WS spec 1.1 section 14.3, the value should not be empty.
fix: Please check the BPEL source at line number \"{0}\" and verify the .

ORABPEL-09205
severity: 10
type: error
name: XPath query string returns zero node.
description: According to BPEL4WS spec 1.1 section 14.3, The assign activity part query should not return zero node.
fix: Please check the BPEL source at line number \"{1}\" and verify the part xpath query.

ORABPEL-09206
severity: 10
type: error
name: DOM Element creation failed
description: Error occured while creating DOM element, the reason is {0}.

ORABPEL-09207
severity: 10
type: error
name: The XML data is invalid
description: The XML data is invalid; the reason is \"{0}\".
fix: Please verify xml data.

ORABPEL-09208
severity: 10
type: error
name: Cannot copy object
description: An attempt to copy the object \"{0}\" (class {1}) has failed. The exception reported is: {2}
fix: If this object type has been imported into the process, please check that the copy() method of this object''s PersistenceManager is working properly.

ORABPEL-09209
severity: 10
type: error
name: Cannot expand shadow object
description: An attempt to resolve the shadow object \"{0}\" (class {1}) has failed. The exception reported is: {2}
fix: If this object type has been imported into the process, please check that the copy() method of this object''s PersistenceManager is working properly.

ORABPEL-09210
severity: 10
type: error
name: Cannot deep copy object
description: An attempt to deep copy the object \"{0}\" (class {1}) has failed. The exception reported is: {2}
fix: If this object type has been imported into the process, please check that the copy() method of this object''s PersistenceManager is working properly.

ORABPEL-09211
severity: 10
type: error
name: Cannot do binary deep copy element
description: An attempt to binary deep copy the element \"{0}\" has failed. The exception reported is: {2}
fix: If this object type has been imported into the process, please check that the copy() method of this object''s PersistenceManager is working properly.

ORABPEL-09212
severity: 10
type: error
name: Cannot copy object
description: An attempt to copy the moniker \"{0}\" (class {1}) has failed. The exception reported is: {2}
fix: If this object type has been imported into the process, please check that the copy() method of this object''s PersistenceManager is working properly.

ORABPEL-09213
severity: 10
type: error
name: Cannot load object from moniker
description: An attempt to deserialize an object from its moniker format has failed. The exception reported is: {0}
fix: The object moniker is corrupt; the moniker may have been edited manually.

ORABPEL-09214
severity: 10
type: error
name: Cannot marshall object
description: An attempt to marshall the object \"{0}\" (class \"{1}\") to XML has failed. The exception reported is: {2}
fix: If this object type has been imported into the process, please check that the marshall() method is working properly. Otherwise, the document may have been edited manually.

ORABPEL-09215
severity: 10
type: error
name: Cannot read moniker
description: An attempt to read an object''s moniker from the deserializer stream has failed. The exception reported is: {0}
fix: The object moniker is corrupt; the moniker may have been edited manually.

ORABPEL-09216
severity: 10
type: error
name: Cannot save object
description: An attempt to save the object \"{0}\" (class {1}) has failed. The exception reported is: {2}
fix: If this object type has been imported into the process, please check that the save() method is working properly. The save() call is the object''s opportunity to persist itself in some form of external storage.

ORABPEL-09217
severity: 10
type: error
name: Cannot write moniker
description: An attempt to write an object''s moniker into the serializer stream has failed. The exception reported is: {0}

ORABPEL-09218
severity: 10
type: error
name: Couldn''t load the referenced element
description: The shadow node \"{0}\" couldn''t find its referenced read-only element. The XPath to load the referenced element is \"{1}\"
fix: The document is corrupt; it may have been edited manually.

ORABPEL-09219
severity: 10
type: error
name: Cannot save element
description: An attempt to save the element \"{0}\" has failed. Because this element is not a root element and for some reason the scope has reference to this element, scope should have references ONLY to root elements.

ORABPEL-09220
severity: 10
type: error
name: Cannot load element
description: An attempt to load the element \"{0}\" has failed. Because this element is not a root element and for some reason the scope has reference to this element, scope should have references ONLY to root elements.

ORABPEL-09221
severity: 10
type: error
name: Cannot serialize DOM element
description: Failed to serialize the DOM element \"{0}\" to binary format. The exception reported is {1}

ORABPEL-09222
severity: 10
type: error
name: Cannot deserialize DOM element
description: Failed to deserialize the DOM element from binary format, the document id {0}. The exception reported is {1}

ORABPEL-09223
severity: 10
type: error
name: XPath query string returns multiple nodes.
description: According to BPEL4WS spec 1.1 section 14.3, The assign activity part and query {0} should not return multipe nodes.
fix: Please check the BPEL source at line number \"{1}\" and verify the part and xpath query {0}.

ORABPEL-09224
severity: 10
type: error
name: Mismatch Assign
description: Cannot set non-element value to an element based variable
fix: Please check the BPEL source.

ORABPEL-09225
severity: 10
type: error
name: Mismatch Assign
description: Cannot set non-message value to a message based variable
fix: Please check the BPEL source.

<>{ "exception.09226.description", "Cannot use simple-typed variable in "+ "setVariableData(String name, String partOrQuery, Object value) or "+ "setVariableData(String name, String partOrQuery, Object value, boolean clone)" },
ORABPEL-09226
severity: 10
type: error
name: Mismatch Assign
fix: Please check the BPEL source.

ORABPEL-09227
severity: 10
type: error
name: Assign Operation Misuse
description: The from-spec for {2} operation must return either an attribute list or an element list.
fix: Please check the BPEL source at line number \"{1}\" and verify the part and xpath query {0}.

ORABPEL-09228
severity: 10
type: error
name: Assign Operation Misuse
description: The message part \"{2}\" of WSDL variable \"{3}\" is not an XML element; {4} operation cannot be performed.
fix: Please check the BPEL source at line number \"{1}\" and verify the part and xpath query {0}.

<>{ "exception.09229.description", "The to-spec does not yield any data; {1} operation cannot be performed." },
ORABPEL-09229
severity: 10
type: error
name: Assign Operation Misuse
fix: Please check the BPEL source at line number \"{0}\"

<>{ "exception.09230.description", "The parent of the selection result {1} does not exist or is not an XML element; {2} operation cannot be performed." },
ORABPEL-09230
severity: 10
type: error
name: Assign Operation Misuse
fix: Please check the BPEL source at line number \"{0}\"

<>{ "exception.09231.description", "The selection result at list entry # {1} does not have a parent node; {2} operation cannot be performed." },
ORABPEL-09231
severity: 10
type: error
name: Assign Operation Misuse
fix: Please check the BPEL source at line number \"{0}\"

<>{ "exception.09232.description", "The selection result at list entry # {1} is not an XML node; {2} operation cannot be performed." },
ORABPEL-09232
severity: 10
type: error
name: Assign Operation Misuse
fix: Please check the BPEL source at line number \"{0}\"

<>{ "exception.09233.description", "The selection result at list entry # {1} is not an XML element; {2} operation cannot be performed." },
ORABPEL-09233
severity: 10
type: error
name: Assign Operation Misuse
fix: Please check the BPEL source at line number \"{0}\"

<>{ "exception.09234.description", "The selection result of {1} is not an XML element; {2} operation cannot be performed." },
ORABPEL-09234
severity: 10
type: error
name: Assign Operation Misuse
fix: Please check the BPEL source at line number \"{0}\"

<>{ "exception.09240.description", "The element list specified by to-spec used in is NOT contiguous. "},
ORABPEL-09240
severity: 10
type: error
name: Assign Operation Misuse
fix: Please check the BPEL source at line number \"{0}\"

<>{ "exception.09241.description", "The from-list of is element-based, while the to-list is not element-based."},
ORABPEL-09241
severity: 10
type: error
name: Assign Operation Misuse
fix: Please check the BPEL source at line number \"{0}\"

<>{ "exception.09242.description", "The from-list of is attribute-based, while the to-list is not attribute-based."},
ORABPEL-09242
severity: 10
type: error
name: Assign Operation Misuse
fix: Please check the BPEL source at line number \"{0}\"

<>{ "exception.09243.description", "A member of the to-list of does NOT have an element as parent."},
ORABPEL-09243
severity: 10
type: error
name: Assign Operation Misuse
fix: Please check the BPEL source at line number \"{0}\"

<>{ "exception.09244.description", "A member of the to-list of does NOT have a parent node."},
ORABPEL-09244
severity: 10
type: error
name: Assign Operation Misuse
fix: Please check the BPEL source at line number \"{0}\"

<>{ "exception.09245.description", "Members of the to-list of do NOT share the same parent node."},
ORABPEL-09245
severity: 10
type: error
name: Assign Operation Misuse
fix: Please check the BPEL source at line number \"{0}\"

<>{ "exception.09246.description", "Couldn't create the xml stream for document \"{0}\", the reason is: {1}"},
ORABPEL-09246
severity: 10
type: error
name: Failed to create xml stream
fix: Please make sure the document \"{0}\" exists in the document table

<>{ "exception.09247.description", "Couldn't get the blob for document \"{0}\", the reason is: {1}"},
ORABPEL-09247
severity: 10
type: error
name: Failed to get Document Blob
fix: Please make sure the document \"{0}\" exists in the document table

<>{ "exception.09248.description", "Couldn't create document builder \"{0}\", the reason is: {1}"},
ORABPEL-09248
severity: 10
type: error
name: Could not create xdk document builder
fix: Please make sure the document builder \"{0}\" class exists in your classpath

ORABPEL-09249
severity: 10
type: error
name: The XML data is invalid
description: The XML text is invalid {0}, the reason is \"{1}\".
fix: Please verify xml text

ORABPEL-09250
severity: 10
type: error
name: XML Document creation failed
description: Error occured while creating XML Document, the reason is {0}.

BPEL Delivery Exceptions ORABPEL 03800 - 03813

2007-08-11T07:45:00.001-07:00

Delivey Exceptions 03800 - 03813

ORABPEL-03800
severity: 10
type: error
name: Cannot resolve correlation set definition
description: The process domain was not able to resolve which correlation set definition to apply to the received callback message for operation \"{0}\".
fix: Correlation set definitions are registered with the process domain using operation name and process id. The callback message is most likely missing the process id.

ORABPEL-03801
severity: 10
type: error
name: Missing operation name
description: The received callback message is missing the operation name parameter. The process domain cannot resolve which correlation set definition to apply to the message without this parameter.

ORABPEL-03802
severity: 10
type: error
name: Correlation definition not registered
description: The correlation set definition for operation \"{0}\", process \"{1}\", has not been registered with the process domain.
fix: Please try to redeploy your process to the process domain.

ORABPEL-03803
severity: 10
type: error
name: Cannot create engine bean
description: The process domain cannot lookup the engine bean; this bean is responsible for processing the callback of a received message. The exception reported is: {0}
fix: Please check that the engine bean has been properly deployed to the server and can be properly mounted from a java class.

ORABPEL-03804
severity: 10
type: error
name: Synchronous method invocation timeout
description: The synchronous polling thread has timed out waiting for a result from instance \"{0}\".
fix: There may be problem completing instance \"{0}\"; please check the process console for more information.

ORABPEL-03805
severity: 10
type: error
name: Protocol handler not found
description: The process domain was unable to find the protocol handler for the conversation type \"{0}\".
fix: Please check the implementation of the protocol interface for this conversation type.

ORABPEL-03806
severity: 10
type: error
name: Callback on delivery service failed
description: The process domain was unable to process the callback for received message \"{0}\" for conversation \"{1}\", subscriber \"{2}\". The exception reported is: {3}

ORABPEL-03807
severity: 10
type: error
name: Cannot resubscribe MOM conversations
description: An attempt to resubscribe previous MOM conversations has failed. The exception reported is: {0}

ORABPEL-03808
severity: 10
type: error
name: Cannot create listener for MOM conversation
description: An attempt to create MOM listener has failed. The exception reported is: {0}

ORABPEL-03809
severity: 10
type: error
name: Cannot find message part
description: Delivery service cannot find message part \"{0}\" when doing message correlation.
fix: Please check your BPEL source to make sure the correlationSet definition is correct.

ORABPEL-03810
severity: 10
type: error
name: Conflicting receive
description: Another receive activity or equivalent (currently, onMessage branch in a pick activity) has already been enabled with the partnerLink \"{0}\", operation name \"{1}\" and correlation set \"{2}\" (or conversation id). Appendix A - Standard Faults in the BPEL 1.1 specification specifies a fault should be thrown under these conditions.

ORABPEL-03811
severity: 10
type: error
name: No correlation sets defined
description: No correlation sets have been defined for operation \"{0}\" (process \"{1}\"). All receive operations that do not use WS-Addressing to correlate messages must define at least one correlation set.
fix: Please check your BPEL source to make sure at least one correlationSet is defined for the operation \"{0}\".

ORABPEL-03812
severity: 10
type: error
name: Cannot find property alias
description: Cannot find the property alias \"{0}\", message type \"{1}\".
fix: Please check your BPEL/WSDL source to make sure that property alias \"{0}\" has been defined.

ORABPEL-03813
severity: 10
type: error
name: Failed to evaluate correlation query
description: Failed to evaluate the correlationAlias query \"{0}\" on the element \"{1}\".
fix: Please check your BPEL/WSDL source to make sure that proprty alias is defined correctly

How To Get The Instance ID of a BPEL Process at Runtime

2007-08-11T07:32:00.000-07:00

Oracle(R) BPEL Process Manager - Version: 10.1.2
Goal
When an instance of a BPEL process/ suitecase is started the instance ID is added to the field CIKEY of cube_instance table. How is it possible to get the instance ID at runtime?

Solution
To get access to the instance If of a newly started BPEL suitecase/process the build-in method
getInstanceId() has to be used.
This method can be used in the bpel:exec action only.
<bpelx:exec name="Java_Embedding_1" language="java" version="1.3">
<![CDATA[ setVariableData("instance", new Long(getInstanceId())); ]]>
</bpelx:exec>
<bpelx:exec name="Java_Embedding_1" language="java" version="1.3"></bpelx:exec>
In that case the instance ID is stored in the variable 'instance', which is of type 'long' and has been created in the scope in which the bpel:exec action resides.