BPEL PM 10.1.2 B3 Shutdown

Hi
when i try to shutdown the BPEL PM server 10.1.2 B3 using 'Stop BPEL PM Server' shortcut, it doesn't always shutdown successfully, most of the time it just hangs and i had to kill it.
I tried this in winxp pro with service pack1a and service pack2.
any suggestions?
thanks
Sam

Would like to reopen this for discussion. I have the same problem the majority of the time with 10.1.2.0.2. If I start the server and immediately shut it down, no prob. But if I have run so much as 1 process through the server, it will not shut down on its own. I have to click the red X (windows) to kill the window, and it throws a few exceptions.
I have tried waiting over a half hour, hoping it just needed some time to release connections, but that did no good. Even left it shutting down over a long lunch once (hour+), but it was still in the same state when I returned. The Command window has "Shutting down..." at the bottom and never goes anywhere from there.
I would like to get some ideas for troubleshooting this, so I can get it to shut down more gracefully.
Thx,
Smalls

Similar Messages

How to Shutdown Composite from BPEL

Hi,
I have two composites, one is consuming the messges and routing them to another BPEL,
The second BPEL is invoking a third party system, If suppose that third party system is down, Then
can someone help me in knowing , how to shutdown the first composite from this invoking BPEL? so that i can stop consuming the messages and the messages will pertained in TOPIC.
Thanks,
SV

Hi Albin,,
I have started creating the class with the same code you have shared.
But i am getting null pointer exception when i ran this..
i am seeing the query result as empty,
I am not sure what are you doing here in the below.
Set queryResult = m_connection.queryNames(new ObjectName("*:j2eeType=CompositeLifecycleConfig,*"), null);
Can you please tell me what is ""*:j2eeType=CompositeLifecycleConfig,*"".. may be i need to change this config so that i can avoid null pointer.
Thanks,
SV

BPEL server crashes

Our Bpel server runs fine and then all of a sudden it starts to give errors. Does anyone have any advice about what could be wrong. I pasted the log file info underneath, as you can see its info messages and then just errors and I have to restart the server.
Thanks
Roald
+<2009-02-10 09:07:58,732> <INFO> <default.collaxa.cube.activation> <Database Adapter::Inbound>+
+<oracle.tip.adapter.db.ox.TopLinkXMLProjectInitializer initialize> Initializing an existing toplink project for+
use by the database adapter.
+<2009-02-10 09:13:00,229> <INFO> <default.collaxa.cube.activation> <Database Adapter::Inbound>+
+<oracle.tip.adapter.db.ox.TopLinkXMLProjectInitializer initialize> Initializing an existing toplink project for+
use by the database adapter.
*+<2009-02-10 09:14:00,443> <INFO> <default.collaxa.cube.activation> <Database Adapter::Inbound>+*
+<oracle.tip.adapter.db.ox.TopLinkXMLProjectInitializer initialize> Initializing an existing toplink project for+
use by the database adapter.*
*+<2009-02-10 09:15:00,677> <ERROR> <default.collaxa.cube.activation> <Database Adapter::Inbound>+*
+<oracle.tip.adapter.db.DBManagedConnectionFactory acquireClientSession> unable to build the TopLink Session+
+<2009-02-10 09:15:00,685> <ERROR> <default.collaxa.cube.activation> <Database Adapter::Inbound>+
+<oracle.tip.adapter.db.InboundWork runOnce> Non retriable exception during polling of the database ORABPEL-11624+
DBActivationSpec Polling Exception.
+Query name: [ReadAppointmentData], Descriptor name:+
+[PublishEmployeeAppointmentInformationService.XxnwuHrPeopleV]. 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 ORABPEL-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore.
See root exception for the specific exception. You may need to configure the connection settings in the
deployment descriptor (i.e. $J2EE_HOME/application-deployments/default/DbAdapter/oc4j-ra.xml) and restart the
+server. Caused by Exception [TOPLINK-7099] (OracleAS TopLink - 10g (9.0.4.5) (Build 040930)):+
oracle.toplink.exceptions.ValidationException
Exception Description: Could not find xml project file which is specified in properties file:
xmlProjectFile=file:/u01/app/oracle/product/10.1.2/oas_bpel/integration/orabpel/domains/default/tmp/.bpel_Publish
EmployeeAppointmentInformationService_1.0.jar/toplink_mappings.xml..
+.+
+<2009-02-10 09:15:00,685> <FATAL> <default.collaxa.cube.activation> <AdapterFramework::Inbound>+
+[ReadAppointmentData_ptt::receive(payload)] - Resource Adapter requested Process shutdown!+
+<2009-02-10 09:15:00,685> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework+
instance: OraBPEL - performing endpointDeactivation for portType=ReadAppointmentData_ptt, operation=receive
+<2009-02-10 09:15:00,686> <INFO> <default.collaxa.cube.activation> <Database Adapter::Inbound>+
+<oracle.tip.adapter.db.DBResourceAdapter endpointDeactivation> Deactivating:+
oracle.tip.adapter.db.DBActivationSpec@1cc678a
+<2009-02-10 09:15:00,699> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound>+
JCAActivationAgent::onStateChanged State is changed for process
+'bpel://localhost/default/PublishEmployeeAppointmentInformationService~1.0/', state=OFF+
+<2009-02-10 09:16:05,788> <ERROR> <default.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking+
bean "finder": Cannot fetch a datasource connection.
The process domain was unable to establish a connection with the datasource with the connection URL
+"jdbc/BPELServerDataSourceWorkflow". The exception reported is: Io exception: The Network Adapter could not+
establish the connection
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-04077
Cannot fetch a datasource connection.
The process domain was unable to establish a connection with the datasource with the connection URL
+"jdbc/BPELServerDataSourceWorkflow". The exception reported is: Io exception: The Network Adapter could not+
establish the connection
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.
at
com.collaxa.cube.engine.data.ConnectionFactory$ConnectionFactoryImpl.getConnection(ConnectionFactory.java:347)
at com.collaxa.cube.engine.data.ConnectionFactory.getConnection(ConnectionFactory.java:159)
at com.collaxa.cube.engine.data.ConnectionFactory.getQueryConnection(ConnectionFactory.java:114)
at
com.collaxa.cube.engine.adaptors.common.BaseCubeInstancePersistenceAdaptor.listInstanceMetaData(BaseCubeInstanceP
ersistenceAdaptor.java:1094)
at
com.collaxa.cube.engine.adaptors.oracle.CubeInstancePersistenceAdaptor.listInstanceMetaData(CubeInstancePersisten
ceAdaptor.java:91)
at com.collaxa.cube.engine.data.AdminFinder.__listInstanceMetaData(AdminFinder.java:374)
at com.collaxa.cube.engine.data.AdminFinder.listInstances(AdminFinder.java:190)
at com.collaxa.cube.ejb.impl.FinderBean.listInstances(FinderBean.java:222)
at
IFinderBean_StatelessSessionBeanWrapper42.listInstances(IFinderBean_StatelessSessionBeanWrapper42.java:963)
at com.oracle.bpel.client.Locator.listInstances(Locator.java:521)
at com.oracle.bpel.client.Locator.listInstances(Locator.java:490)
at BusinessProcess.myLocator.getXML(myLocator.java:102)
at bpel.p0.ExecLetBxExe4.execute(ExecLetBxExe4.java:65)
at com.collaxa.cube.engine.ext.wmp.BPELXExecWMP.__executeStatements(BPELXExecWMP.java:52)
at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:188)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3408)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1836)
at
com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75
+)+
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:166)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:252)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5438)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1217)
at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.createAndInvoke(CubeEngineBean.java:120)
at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.syncCreateAndInvoke(CubeEngineBean.java:153)
at
ICubeEngineLocalBean_StatelessSessionBeanWrapper0.syncCreateAndInvoke(ICubeEngineLocalBean_StatelessSessionBeanWr
apper0.java:486)
at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyType(DeliveryHandler.java:520)
at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(DeliveryHandler.java:435)
at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHandler.java:132)
at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:101)
at
IDeliveryBean_StatelessSessionBeanWrapper22.request(IDeliveryBean_StatelessSessionBeanWrapper22.java:479)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:124)
at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:48)
at
com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:174)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:286)
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:327)
at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:433)
at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:150)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:31)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:571)
at com.evermind.sql.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:160)
at
com.collaxa.cube.engine.data.ConnectionFactory$ConnectionFactoryImpl.getConnection(ConnectionFactory.java:336)
+... 37 more+
+<2009-02-10 09:17:03,836> <ERROR> <default.collaxa.cube.services> <PCException::<init>> Internal Error.+
+<2009-02-10 09:17:03,837> <ERROR> <default.collaxa.cube.services> <PCException::<init>> Internal error due to+
+{0}.+
+<2009-02-10 09:17:03,837> <ERROR> <default.collaxa.cube.services> <PCException::<init>> Contact oracle support if+
error is not fixable.
+<2009-02-10 09:17:03,837> <ERROR> <default.collaxa.cube.services> <TaskManager::getPendingTasksOfInstance> Error+
in getting the task of the instance 534412

Looks like the server is unable to connect to the dehydration database.
A standard installation would have this data source setup as part of the installation.
"jdbc/BPELServerDataSourceWorkflow"
This again uses the connection pool "BPELPM_CONNECTION_POOL"
And the name of the data source is "BPELServerDataSourceWorkflow"
There are a few checks that you can perform.
1. Check if the dehydration database is up.
If no then this should be up and running.
2. Go to the EM and use {test connection} for "BPELPM_CONNECTION_POOL"
If comes back with error then check if the dehydration database credentials has changed post installation.
There are a few other datasources that share the same connection pool. Check if these are working too.
Every Little Helps
Kalidass Mookkaiah
http://oraclebpelindepth.blogspot.com/

[Patch 정보] TRACKING BUG FOR CUMULATIVE MLR#6 ON TOP OF BPEL PM 10.1.3.3.1

최근에 출시된 BPEL PM 10.1.3.3.1의 통합패치입니다.
아래는 readme.txt에 포함된 patch list입니다.
# WARNING: Failure to carefully read and understand these requirements may
# result in your applying a patch that can cause your Oracle Server to
# malfunction, including interruption of service and/or loss of data.
# If you do not meet all of the following requirements, please log an
# iTAR, so that an Oracle Support Analyst may review your situation. The
# Oracle analyst will help you determine if this patch is suitable for you
# to apply to your system. We recommend that you avoid applying any
# temporary patch unless directed by an Oracle Support Analyst who has
# reviewed your system and determined that it is applicable.
# Requirements:
# - You must have located this patch via a Bug Database entry
# and have the exact symptoms described in the bug entry.
# - Your system configuration (Oracle Server version and patch
# level, OS Version) must exactly match those in the bug
# database entry - You must have NO OTHER PATCHES installed on
# your Oracle Server since the latest patch set (or base release
# x.y.z if you have no patch sets installed).
# - [Oracle 9.0.4.1 & above] You must have Perl 5.00503 (or later)
# installed under the ORACLE_HOME, or elsewhere within the host
# environment.
# Refer to the following link for details on Perl and OPatch:
# http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=189489.1
# If you do NOT meet these requirements, or are not certain that you meet
# these requirements, please log an iTAR requesting assistance with this
# patch and Support will make a determination about whether you should
# apply this patch.
# 10.1.3.3.1 Bundle Patch 6823628
# DATE: March 14, 2008
# Platform Patch for : Generic
# Product Version # : 10.1.3.3.1
# Product Patched : Oracle(R) SOA
# Bugs Fixed by 10.1.3.3.1 Initial patch 6492514 :
# Bug 5473225 - PATCH01GENESIS HOT UNABLE TO CATCH AN EXCEPTION DURING A
# TRANSFORM
# Bug 5699423 - PARTNERLINK PROPERTY THAT SET BPELXPROPERTY FUNCTION DOESN'T
# WORK
# Bug 5848272 - STATEFUL WEBSERVICES DEMO ON OTN DOES NOT WORK 10.1.3.1
# Bug 5872799 - ANT DEPLOY BPEL TEST FAILS/RUNS ON DEFAULT DOMAIN NOT
# SPECIFIED TARGET DOMAIN
# Bug 5883401 - ALLOW A WAY TO CREATE EMPTY NODES - AND USE FOR REQUIRED
# NODES
# Bug 5919412 - SAMPLE DEMO BPEL PROCESSES MIMESERVICE MIMEREQUESTER AXIS
# JAVA EXAMPLE ERROR
# Bug 5924483 - ESB SHOULD SUPPORT SOAP EDNPOINT LOCATION DYNAMIC UDDI LOOKUP
# Bug 5926809 - ORAPARSEESCAPEDXML XPATH EXPRESSION FAILED TO EXECUTE
# FOTY0001 TYPE ERROR
# Bug 5937320 - STRANGE BEHAVIOUR CALLING FROM BPEL TO BPEL GETTING
# NULLPOINTEREXCEPTION.
# Bug 5944641 - BPA BLUEPRINT NOT AVAIALBLE IN JDEVELOPER
# Bug 5945059 - JAVA.LANG.NULLPOINTEREXCEPTION SENDING EMAILS WITH PAYLOADS
# LARGER THAT 1MB
# Bug 5962677 - WS RESPONSE IS EMPTY SOAP BODY IN ONE-WAY CALL
# Bug 5963425 - WHEN THE OUTCOMES FOR A HT CHANGED & IMPORTED - UPDATE
# CONNECTION ROLES IN BPEL
# Bug 5964097 - AQ ADAPTER DEPLOYMENT CAUSES OPMN TO PERFORM A FORCEFUL
# SHUTDOWN IN SOA
# Bug 5971534 - CANNOT GRANT USER TASK VIEWS TO GROUPS, ONLY TO USERS.
# Bug 5989367 - REFER TO SR 6252219.993 BPEL 10.1.3 ONLY COPIES IN ASSIGN,
# IN 10.1.2 IT CREATES
# Bug 5989527 - ENHANCEMENT WARNING SHOULD BE GIVEN UPON UPLOAD IF BPEL
# PROCESS IS OPEN IN ARIS
# Bug 5997936 - ESB FAULT DOES NOT GET PROPAGATED TO BPEL
# Bug 6000575 - PERF NEED ESB PURGE SCRIPT TO PURGE BY DATE AND PROCESS
# Bug 6001796 - POSTING OF DATE RECEIVED FROM XML GATEWAY TO BPEL FAILED IN
# ESB
# Bug 6005407 - BPEL PROCESS DOESN'T PROPOGATE FAULT THROWN BY BPEL
# SUB-PROCESS
# Bug 6017846 - MIMETYPE OF EMAIL NOTIFICATION IS NOT SET THROUGH HUMAN TASK
# Bug 6027734 - DECISION SERVICE IMPORT - LOCATING DECISION SERVICE IN .DECS
# FILE IMPROPER
# Bug 6028985 - EXCEEDED MAXIMUM NUMBER OF SUBSCRIBERS FOR QUEUE
# ORAESB.ESB_CONTROL
# Bug 6041508 - CREATING/UPDATING DVM CAUSE EXCEPTION
# Bug 6053708 - FTP ADAPTER DOES NOT SUPPORT ENCRYPTED PASSWORD IN
# OC4J-RA.XML
# Bug 6054034 - INDEX4,INDEX5 AND INDEX6 CANNOT BE USED IN BPEL CONSOLE
# Bug 6068801 - BACKPORT OF BPEL ON WEBLOGIC - VERSION 10.1.3.3
# Bug 6070991 - HT EXPORT DOES NOT EXPORT PARAMETERS, ALLOW PARTICIPANTS TO
# INVITE OTHERS
# Bug 6071001 - WSIF HTTP BINDING NOT WORKING FROM ESB
# Bug 6073311 - STRESS SCOPE NOT FOUND ON CALLBACK - WRONG (DUPE)
# SUBSCRIPTION IN TABLE
# Bug 6081070 - JMS ADAPTER REJECTION HANDLER CREATE 0 BYTE FILES
# Bug 6083419 - DECISION SERVICE SCOPE NEED TO HAVE A SPECIAL INDICATOR
# Bug 6085799 - HUMAN TASK ADDED IN SCOPE IN JDEV IS NOT UPDATED TO BPA
# SERVER
# Bug 6085933 - EXPORT AND EXPLORE SHOULD USE USER LANGUAGE AND NOT ENGLISH
# ALWAYS
# Bug 6086281 - STRING INDEX OUT OF RANGE ERROR FOR COBOL COPYBOOK WITH PIC
# CLAUSE HAVING S
# Bug 6086453 - DOMAINS CREATED IN A CLUSTER GETS NOT PROPAGATED TO NEW OR
# EXISTING NODES
# Bug 6087484 - MULTIPLE HEADER SETTING CAUSES ESB EXCEPTION
# Bug 6087645 - ESB SHOULD ALLOW USER PICK RUNTIME PROTOCOL (HTTP/HTTPS)
# Bug 6110231 - TRANSLATION NOT BASED ON MQ CCSID CHARSET
# Bug 6120226 - BPEL IS NOT SETTING THE APPS CONTEXT CORRECTLY
# Bug 6120323 - COMPLETIONPERSISTPOLICY ON DOMAIN LEVEL HAS DISAPPEARED
# Bug 6125184 - ESB JMS SESSION ROLLBACK ORACLE.JMS.AQJMSEXCEPTION
# Bug 6127824 - [AIA2.0] CURRENT XREF IMPLEMENTATION IS MISSING REQUIRED
# INDEXES ON XREF SCHEMA
# Bug 6128247 - HTTPCONNECTOR POST() METHOD SHOULD RAISE EXCEPTION FOR ALL
# STATUS CODES EXCEPT 2
# Bug 6131159 - ENABLE USERS TO CHOOSE XSD WHEN CREATING A BPEL PROCESS FROM
# BLUE PRINT
# Bug 6132141 - PROCESS_DEFAULT TABLE STILL CONTAINS INFORMATION FROM
# UNDEPLOYED PROCESSES
# Bug 6133190 - ENABLING ESB CONSOLE HTTP/S IS MAKING THE CONSOLE TO COME UP
# BLANK.
# Bug 6139681 - BPEL WSDL LINK IN CLUSTERED RUNTIME POINTS TO A SINGLE NODE
# Bug 6141259 - BASICHEADERS NOT PUTTING WWW-AUTHENTICATE HEADERS FOR HTTP
# BINDING IN BPEL
# Bug 6148021 - BPEL NATIVE SCHEMA FOR COBOL COPYBOOK WITH IMPLIED DECIMAL
# LOSES DIGIT IN OUTPUT
# Bug 6149672 - XOR DATA - CONDITION EXPRESSION SPECIFICATION IS NOT
# INTUITIVE IN BPMN MODELS
# Bug 6152830 - LOSING CONDITIONAL EXPRESSIONS CREATED IN JDEV UPON MERGE
# Bug 6158128 - BASICHEADERS NOT PUTTING WWW-AUTHENTICATE HEADERS FOR HTTP
# BINDING
# Bug 6166991 - WHEN STARTING SOA SUITE,, PROCESSES FAIL DUE TO UNDEFINED
# WSDL
# Bug 6168226 - LOCATION-RESOLVER EXCEPTION THROWN IN OPMN LOGS
# Bug 6187883 - CHANGES FOR BPEL RELEASE ON JBOSS- VERSION 10.1.3.3
# Bug 6206148 - [AIA2.0] NEW FUNCTION REQUEST, XREFLOOKUPPOPULATEDCOLUMNS()
# Bug 6210481 - BPEL PROCESS WORKS INCORRECTLY WHEN AN ACTIVITY HAS MULTIPLE
# TRANSITIONCONDITION
# Bug 6240028 - WEBSERVICE THAT DOES NOT CHALLENGE FOR BASIC CREDENTIALS
# CANNOT BE INVOKED
# Bug 6257116 - MULTIPLE HEADER SETTING CAUSES ESB EXCEPTION
# Bug 6258925 - MESSAGE RECEIVED BY THE TARGET ENDPOINT VIA HTTP POST IS
# MISSING THE XML HEADER
# Bug 6259686 - TOO MANY UNNECESSARY WORKFLOW E-MAIL NOTIFICATIONS GENERATED
# Bug 6267726 - 10.1.3.3 ORACLE APPLICATIONS ADAPTER - NOT ABLE TO CAPTURE
# BUSINESS EVENT
# Bug 6272427 - WEBSPHERE BPEL FAILS FOR DATA RETRIEVAL OF SIZE 500+ KB
# Bug 6276995 - MERGE SCOPE NAME IS NOT UPDATED WHEN CHANGED IN THE SERVER
# Bug 6280570 - XPATH EXPRESSION ERROR IN MEDIATOR FOR ASSIGNING USER-DEFINED
# CONTEXT VALUES
# Bug 6282339 - RETRYCOUNT DOES NOT WORK PROPERLY
# Bug 6311039 - ONE RECORD IS INSERTED TO SYNC_STORE IF
# COMPLETIONPERSISTPOLICY SET TO FAULTED
# Bug 6311809 - [AIA2.0] NON-RETRYABLE ERRORS ARE NOT POSTED ON ESB_ERROR
# TOPIC
# Bug 6314784 - THE PRIORITY DEFINED IN THE BPA SUITE IS NOT TRANSFERRED TO
# THE JDEV CORRECTLY
# Bug 6314982 - THREADPOOL RACE CONDITION IN ADAPTER INITIALIZATION MESSAGES
# NOT PROCESSED
# Bug 6315104 - (SET)CLASSNAME MISSING IN TSENSOR JAXB OBJECTS
# Bug 6316554 - CONSUME FUNCTIONALITY OF JMS ADAPTER FOR BEA WEBLOGIC DOES
# NOT WORK
# Bug 6316950 - FILEADAPTER HARPER ENHANCEMENTS SYNC WRITE AND CHUNKED
# INTERACTION SPEC
# Bug 6317398 - THE ICON FOR COMPUTING DIFFERENCE IS MISSING IN JDEV REFRESH
# FROM SERVER DIALOG
# Bug 6320506 - IMPORT FAILS WHEN THERE IS AN UNNAMED CASE
# Bug 6321011 - CANNOT PROCESS 0 BYTE FILE USING FTP ADAPTER
# Bug 6325749 - TRACKING BUG FOR TRACKING ADDITIONAL CHANGES TO BUG #6032044
# Bug 6328584 - NEED A NEW XPATH EXPRESSION TO GET ATTACHMENT CONTENT VIA
# SOAP INVOKATION
# Bug 6333788 - COLLAPSING OF CONSECUTIVE ASSIGN TASKS BREAKS BAM SENSOR
# Bug 6335773 - BUILD.XML CONTAINS DO NOT EDIT .. - WHILE <CUSTOMIZE> TASK
# MUST BE IN <BPELC>
# Bug 6335805 - AQ ADAPTER OUTBOUND DOESN'T RECONNECT AFTER FAILURE
# Bug 6335822 - [AIA2.0] PSRPERFESB - RUNTIME DVM PERFORMANCE OVERHEAD IN ABS
# USE CASE
# Bug 6339126 - CHECKPOINT BPEL JAVA METHOD DOESN'T WORK IN BPEL 10.1.3.3
# Bug 6342899 - OUTLINECHANGE.XML NOT UPDATE WITH ACTIVITY FROM NEW BRANCH
# Bug 6343299 - ESB CONCRETE WSDL NAMESPACE SHOULD BE DIFFERENT FROM IMPORTED
# WSDL NAMESPACE
# Bug 6372741 - DEHYDRATION DATABASE KEEPS GROWING IN 10.1.3.3
# Bug 6401295 - NXSD SHOULD SUPPORT ESCAPING THE TERMINATED/QUOTED/SURROUNDED
# DELIMITERS
# Bug 6458691 - DIST DIRECTORY FOR 10.1.3.3.1 NEEDS UPDATE
# Bug 6461516 - BPEL CONSOLE CHANGES FOR DISPLAYING RELEASE 10.1.3.3.1
# Bug 6470742 - CHANGE THE VERSION NUMBER AND BUILD INFO IN ABOUT DIALOG IN
# ESB
# BUG ADDED IN MLR#1, 6671813 :
# Bug 6494921 - ORABPEL-02154 IF LONG DOMAIN AND SUITECASE NAMES IN USE
# BUGS ADDED IN MLR#2, 6671831 :
# Bug 6456519 - ERROR IN BPEL CONSOLE THREADS TAB:SERVLETEXCEPTION CANNOT GET
# DISPATCHER TRACE
# Bug 6354719 - WHICH JGROUP CONFIGURATION PARAMETER IMPACTS BPEL CLUSTER
# ACTIVITY
# Bug 6216169 - SCOPE NOT FOUND ERROR WHILE DELIVERING EXPIRATION MESSAGE OF
# ONALARM
# Bug 6395060 - ORA-01704 ON INSERTING A FAULTED INVOKE ACTIVITY_SENSOR
# Bug 6501312 - DEHYDRATION DATABASE KEEPS GROWING IN 10.1.3.3 #2
# Bug 6601020 - SEARCHBASE WHICH INCLUDES PARENTHESIS IN THE NAMES DOES NOT
# WORK
# Bug 6182023 - WAIT ACTIVITY FAILS TO CONTINUE IN CLUSTER WHEN PROCESSING
# NODE GOES DOWN
# BUGS ADDED IN MLR#3, 6723162 :
# Bug 6725374 - INSTANCE NOT FOUND IN DATASOURCE
# Bug 4964824 - TIMED OUT IF SET CORRELATIONSET INITIATE YES IN REPLY
# ACTIVITY
# Bug 6443218 - [AIA2.0]BPEL PROCESS THAT REPLIES A CAUGHT FAULT AND THEN
# RETHROWS IT IS STUCK
# Bug 6235180 - BPPEL XPATH FUNCTION XP20 CURRENT-DATETIME() IS RETURNING AN
# INCORRET TIME
# Bug 6011665 - BPEL RESTART CAUSES ORABPEL-08003 FAILED TO READ WSDL
# Bug 6731179 - INCREASED REQUESTS CAUSE OUTOFMEMORY ERRORS IN OC4J_SOA WHICH
# REQUIRES A RESTART
# Bug 6745591 - SYNC PROCESS <REPLY> FOLLOWED BY <THROW> CASE CAUSING
# OUTOFMEMORY ERRORS
# Bug 6396308 - UNABLE TO SEARCH FOR HUMAN TASK THAT INCLUDES TASK HISTORY
# FROM PREVIOUS TASK
# Bug 6455812 - DIRECT INVOCATION FROM ESB ROUTING SERVICE FAILS WHEN CALLED
# BPEL PROCESS
# Bug 6273370 - ESBLISTENERIMPL.ONFATALERROR GENERATING NPE ON CUSTOM ADAPTER
# Bug 6030243 - WORKFLOW NOTIFICATIONS FAILING WITHOUT BPELADMIN USER
# Bug 6473280 - INVOKING A .NET 3.0 SOAP SERVICE EXPOSED BY A ESB ENDPOINT
# GIVES A NPE
# BUGS ADDED IN MLR#4, 6748706 :
# Bug 6336442 - RESETTING ESB REPOSITORY DOES NOT CLEAR DB SLIDE REPOSITORY
# Bug 6316613 - MIDPROCESS ACTIVATION AGENT DOES NOT ACTIVATED FOR RETIRED
# BPEL PROCESS
# Bug 6368420 - SYSTEM IS NOT ASSIGNING TASK FOR REAPPROVAL AFTER REQUEST
# MORE INFO SUBMITTED
# Bug 6133670 - JDEV: UNABLE TO CREATE AN INTEGRATION SERVER CONNETION WHEN
# ESB IS ON HTTPS
# Bug 6681055 - TEXT ATTACHMENT CONTENT IS CORRUPTED
# Bug 6638648 - REQUEST HEADERS ARE NOT PASSED THROUGH TO THE OUTBOUND HEADER
# Bug 5521385 - [HA]PATCH01:ESB WILL LOSE TRACKING DATA WHEN JMS PROVIDER IS
# DOWN
# Bug 6759068 - WORKLIST APPLICATION PERFORMANCE DEGRADATION W/ SSL ENABLED
# FOR BPEL TO OVD
# BUGS ADDED IN MLR#5, 6782254 :
# Bug 6502310 - AUTOMATED RETRY ON FAILED INVOKE WITH CORRELATIONSET INIT
# FAILS
# Bug 6454795 - FAULT POLICY CHANGE NEEDS RESTART OF BPEL SERVER
# Bug 6732064 - FAILED TO READ WSDL ERROR ON THE CALLBACK ON RESTARTING BPEL
# OC4J CONTAINER
# Bug 6694313 - ZERO BYTE FILE WHEN REJECTEDMESSAGEHANDLERS FAILS
# Bug 6686528 - LINK IN APPLICATION.XML FILES CHANGED TO HARD LINKS WHEN MORE
# THAN 1 HT PRESENT
# Bug 6083024 - TEXT AND HTML DOC THAT RECEIVED AS ATTACHMENTS WERE EITHER
# BLANK OR GARBLED
# Bug 6638648 - REQUEST HEADERS ARE NOT PASSED THROUGH TO THE OUTBOUND HEADER
# Bug 6267726 - 10.1.3.3 ORACLE APPLICATIONS ADAPTER - NOT ABLE TO CAPTURE
# BUSINESS EVENT
# Bug 6774981 - NON-RETRYABLE ERRORS ARE NOT POSTED ON ESB_ERROR TOPIC
# Bug 6789177 - SFTP ADAPTER DOES NOT SUPPORT RENAMING FILES
# Bug 6809593 - BPEL UPGRADE TO 10.1.3.3.1 WITH ESB CALLS FAILS DUE TO
# CACHING OF PLNK - SERVICE
# BUGS ADDED IN MLR#6, 6823628 :
# Bug 6412909 - <BPELX:RENAME> DOES NOT ADD XMLNS DECLARATION AUTOMATICALLY
# Bug 6753116 - OUTPUT FROM HUMAN TASK IS NOT IS NOT CONSISTENT WITH
# SCHEMA
# ORDERING
# Bug 6832205 - BAD VERIFICATIONSERVICE PERFORMANCE IF LDAP SERVICE HAS HUGE
# DATA
# Bug 6189268 - CALLING BPEL PROCESS VIA SOAP FROM ESB FAILS WITH
# NAMENOTFOUNDEXCEPTION
# Bug 6834402 - JMS ADAPTER IMPROPERLY CASTS XAQUEUESESSION TO QUEUESESSION
# Bug 6073117 - TASK SERVICE DOESN'T RENDER THE TASK ACTIONS
# Bug 6054263 - REUSING SOAP WSDL IN RS CAUSES SOAP ACTION'S NS TO BE
# STRIPPED
# AWAY
# Bug 6489703 - ESB: NUMBER OF LISTENERS > 1 GIVES JMS EXCEPTION UNDER STRESS
# Bug 5679542 - FTP ADAPTER: COULD NOT PARSE TIME:
# JAVA.LANG.STRINGINDEXOUTOFBOUNDSEXCEPTION
# Bug 6770198 - AQ ACTIVATIONINSTANCES >1 DOESN'T WORK IN ESB
# Bug 6798779 - ESB ROUTING RULES CORRUPTED ON RE-REGISTERING WITH ROUTING
# ORDER
# IN WSDL CHANGED
# Bug 6617974 - BACKPORT REQUEST FOR MOVING FILES FUNCTION OF FTP ADAPTER
# Bug 6705707 - VALIDATION ON ESB CAN'T HANDLE NESTED SCHEMAS
# Bug 6414848 - FTP ADAPTER ARCHIVE FILENAME FOR BPEL IS BEING SCRAMBLED
# AFTER
# THE 10.1.3.3 UPGR
# Bug 5990764 - INFORMATION ARE LOST WHEN BPEL PROCESS IS POLLING FOR MAILS
# WITH
# ATTACHEMENTS
# Bug 6802070 - ORA-12899 SUBSCRIBER_ID/RES_SUBSCRIBER COLUMN SMALL FOR LONG
# DOMAIN AND PROCESS
# Bug 6753524 - WRONG SERVICE ENDPOINT OPEN WHEN TEST WEB SERVICE OF ESB
# Bug 6086434 - PROBLEM IN BPEL FILE ADAPTER WHILE READING A FIXED LENGTH
# FILE
# Bug 6823374 - BPEL 10.1.3.3.1 BAM SENSOR ACTION FAILS WITH BAM 11
# Bug 6819677 - HTTS STATUS 202 RETURNED INSTEAD OF SOAP FAULT
# Bug 6853301 - MQ ADAPTER REJECTED MESSAGES IS NOT REMOVED FROM THE RECOVERY
# QUEUE
# Bug 6847200 - 10.1.3.3.1 PATCH (#6748706) HAS STOPPED FTP ADAPTER POLLING
# IN
# SFTP MODE
# Bug 6895795 - AQ OUTBOUND DOESN'T WORK WITH MLR#6
업무에 참고하시기 바랍니다.

David,
You are right, theer are some changes incorporated in the latest MLR # 16 on the configurations files and on the dehydration store metrics(such as performance, fields,..).
However, I would not suggest to continue working on olite, even for Development/Test purposes as you might get stuck with strange errors...and the only solution would be to re-install SOA Suite if your olite gets corrupted. There might be ways to gets your olite back to position, but trust me..its not so simple.
Also, when you develop and stress test all your testcase scenarios in an TEST Adv installation, its simple to mimic the same in actual production box, as you exactly know its behavior.
So, go for a brand new SOA 10.1.3.4 MLR # 5 (or) 10.1.3.3.1 MLR # 16 SOA Suite Advanced installation with Oracle DB 10.2.0.3 as its dehydration store.
Hope this helps!
Cheers
Anirudh Pucha

BPEL process state "Off"

Hi,
I had created one BPEL process which reads from FTP Remote server and writes to local file directory.
After reading from Remote FTP server I am deleting file from the server. In the remote server I had created on user to interact with FTP server with all permissions. When the BPEL process executed FTP Adapter is deleting the File successfully from remote location but BPEL state is changed to “Off”.
When I checked the logs, I found there is problem with Delete permission. Actually as mentioned above file is deleted successfully in the remote location.
OPMN logs:
<File Adapter::Outbound> Processing file : /click/xelusparts/feeds/jabilparts/outbound/process/\po_28.txt
<File Adapter::Outbound> Sending message to Adapter Framework for posting to BPEL engine: {
file=/click/xelusparts/feeds/jabilparts/outbound/process/\po_28.txt
<2007-06-11 19:00:42,677> <DEBUG> <default.collaxa.cube.engine.deployment> <CubeProcessHolder::loadAndBind> Check if process FTPRetrieveTOFileWriteProcess, revision 1.0 needs to be reloaded
<2007-06-11 19:00:42,709> <DEBUG> <default.collaxa.cube.ws> <WSDLManager::getWSDL> registered wsdl at http://dt1521-localhost.com:80/orabpel/default/FTPRetrieveTOFileWriteProcess/1.0/_FTPRetrieveTOFileWriteProcess.wsdl
<2007-06-11 19:00:42,709> <DEBUG> <default.collaxa.cube.ws> <WSDLManager::getWSDL> got wsdl at: http://dt1521-localhost.com:80/orabpel/default/FTPRetrieveTOFileWriteProcess/1.0/_FTPRetrieveTOFileWriteProcess.wsdl
<2007-06-11 19:00:42,724> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Sucessfully sent message : /click/xelusparts/feeds/jabilparts/outbound/process/\po_28.txt to Adapter Framework.
<2007-06-11 19:00:42,724> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> Deleting file : /click/xelusparts/feeds/jabilparts/outbound/process/\po_28.txt after processing.
<2007-06-11 19:00:42,724> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Host name is 'DT1521-localhost.com'.
<2007-06-11 19:00:42,724> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Reading reply from DT1521-localhost.com
<2007-06-11 19:00:42,818> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> operation: Write, partnerLink: <partnerLink name="FileWriter" partnerLinkType="{http://xmlns.oracle.com/pcbpel/adapter/file/Write/}Write_plt">
<myRole name="null">
<ServiceName>null</ServiceName>
<PortType>null</PortType>
<Address>null</Address>
</myRole>
<partnerRole name="Write_role">
<ServiceName>null</ServiceName>
<PortType>{http://xmlns.oracle.com/pcbpel/adapter/file/Write/}Write_ptt</PortType>
<Address>null</Address>
</partnerRole>
<conversationId>bpel://localhost/default/FTPRetrieveTOFileWriteProcess~1.0/10610-BpInv1-BpSeq1.3-3</conversationId>
<properties>{}</properties>
</partnerLink>
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <WSDLManager::getWSDL> registered wsdl at D:\OraHome_1\integration\orabpel\domains\default\tmp\.bpel_FTPRetrieveTOFileWriteProcess_1.0.jar\Write.wsdl
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <WSDLManager::getWSDL> got wsdl at: D:\OraHome_1\integration\orabpel\domains\default\tmp\.bpel_FTPRetrieveTOFileWriteProcess_1.0.jar\Write.wsdl
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> def is file:/D:/OraHome_1/integration/orabpel/domains/default/tmp/.bpel_FTPRetrieveTOFileWriteProcess_1.0.jar/Write.wsdl
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::invoke> opName=Write, parnterLink=<partnerLink name="FileWriter" partnerLinkType="{http://xmlns.oracle.com/pcbpel/adapter/file/Write/}Write_plt">
<myRole name="null">
<ServiceName>null</ServiceName>
<PortType>null</PortType>
<Address>null</Address>
</myRole>
<partnerRole name="Write_role">
<ServiceName>{http://xmlns.oracle.com/pcbpel/adapter/file/Write/}Write</ServiceName>
<PortType>{http://xmlns.oracle.com/pcbpel/adapter/file/Write/}Write_ptt</PortType>
<Address>null</Address>
</partnerRole>
<conversationId>bpel://localhost/default/FTPRetrieveTOFileWriteProcess~1.0/10610-BpInv1-BpSeq1.3-3</conversationId>
<properties>{}</properties>
</partnerLink>
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::doShortCut> Parner Property optShortCut
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> ResourceAdapterMetaData Connection Created
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> file:/D:/OraHome_1/integration/orabpel/domains/default/tmp/.bpel_FTPRetrieveTOFileWriteProcess_1.0.jar/Write.wsdl [ Write_ptt::Write(opaque) ] - Looking up Resource Adapter JDNI location 'eis/FileAdapter'
<2007-06-11 19:00:42,834> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> Managed Connection Created
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Creating Connection
<2007-06-11 19:00:42,834> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> Connection Created
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Creating FileInteraction
<2007-06-11 19:00:42,834> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> FileInteraction Created
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Instantiating outbound JCA interactionSpec oracle.tip.adapter.file.outbound.FileInteractionSpec
<2007-06-11 19:00:42,834> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Populating outbound JCA interactionSpec oracle.tip.adapter.file.outbound.FileInteractionSpec with properties: {FileNamingConvention=spob230_%SEQ%.txt, OpaqueSchema=true, ElapsedTime=60, NumberMessages=1, PhysicalDirectory=c:\inbound_dir, FileSize=1024000}
07/06/11 19:00:42 file:/D:/OraHome_1/integration/orabpel/domains/default/tmp/.bpel_FTPRetrieveTOFileWriteProcess_1.0.jar/fileAdapterOutboundHeader.wsdl
07/06/11 19:00:42 file:/D:/OraHome_1/integration/orabpel/domains/default/tmp/.bpel_FTPRetrieveTOFileWriteProcess_1.0.jar/fileAdapterOutboundHeader.wsdl
07/06/11 19:00:42 file:/D:/OraHome_1/integration/orabpel/domains/default/tmp/.bpel_FTPRetrieveTOFileWriteProcess_1.0.jar/Write.wsdl
<2007-06-11 19:00:42,849> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> file:/D:/OraHome_1/integration/orabpel/domains/default/tmp/.bpel_FTPRetrieveTOFileWriteProcess_1.0.jar/Write.wsdl [ Write_ptt::Write(opaque) ] - Invoking JCA outbound Interaction
<2007-06-11 19:00:42,849> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> File Adapter received an input Record
<2007-06-11 19:00:42,849> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Waiting outside sync object.....
<2007-06-11 19:00:42,849> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Batcher created using staging : true with number of messages : 1
<2007-06-11 19:00:42,849> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Input Record: javax.xml.transform.dom.DOMSource@e5394c
<2007-06-11 19:00:42,849> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Translating....
<2007-06-11 19:00:42,849> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> Outbound Translation done.
<2007-06-11 19:00:42,865> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Refreshed (staging/num Messages) file count : 1
<2007-06-11 19:00:42,865> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Host DT1521-localhost.com FTP command: USER orabpel
<2007-06-11 19:00:42,865> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Wrote to Control File
<2007-06-11 19:00:42,865> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Batching staging File: staging0
<2007-06-11 19:00:42,865> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Batcher sending to sender for output file writing
<2007-06-11 19:00:42,865> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Sending File to output Dir
<2007-06-11 19:00:42,865> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> FileAgent.putFile() puts spob230_17.txt in c:\inbound_dir begins ...
<2007-06-11 19:00:42,865> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> Done Writing to output file spob230_17.txt in dir c:\inbound_dir !!
<2007-06-11 19:00:42,881> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> End clearing Control File
<2007-06-11 19:00:42,881> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Deleting staging File: staging0
<2007-06-11 19:00:42,881> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> End clearing Control File
<2007-06-11 19:00:42,881> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> Interaction gets a ok response
<2007-06-11 19:00:42,881> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> Done with Input Record
<2007-06-11 19:00:43,256> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> FTP Command: USER, reply:
331 Password required for orabpel
<2007-06-11 19:00:43,256> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Host DT1521-localhost.com FTP command: PASS
<2007-06-11 19:00:43,506> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> FTP Command: PASS, reply:
230 Login OK
<2007-06-11 19:00:43,506> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Host DT1521-localhost.com FTP command: CWD /click/xelusparts/feeds/jabilparts/outbound/process/
<2007-06-11 19:00:43,615> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> FTP Command: CWD, reply:
250 Directory successfully changed
<2007-06-11 19:00:43,615> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Host DT1521-localhost.com FTP command: DELE po_28.txt
<2007-06-11 19:00:43,709> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> FTP Command: DELE, reply:
200 Deleted file "po_28.txt".
<2007-06-11 19:00:43,709> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> FTPClient.deleteFile(): 200 Deleted file "po_28.txt".
<2007-06-11 19:00:43,709> <ERROR> <default.collaxa.cube.ws> <File Adapter::Outbound> FTPClient.deleteFile(): Unable to delete file po_28.txt', reply code = 200
<2007-06-11 19:00:43,709> <DEBUG> <default.collaxa.cube.ws> <File Adapter::Outbound> Processer thread calling onFatalError with exception Error deleting file from FTP Server.
Unable to delete file from server.
Please ensure whether the remote file has delete permission.
<2007-06-11 19:00:43,709> <FATAL> <default.collaxa.cube.activation> <AdapterFramework::Inbound> [Get_ptt::Get(opaque)] - Resource Adapter requested Process shutdown!
<2007-06-11 19:00:43,709> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework instance: OraBPEL - performing endpointDeactivation for portType=Get_ptt, operation=Get
<2007-06-11 19:00:43,709> <INFO> <default.collaxa.cube.ws> <File Adapter::Outbound> Endpoint De-activation called in adapter for endpoint : /click/xelusparts/feeds/jabilparts/outbound/process/
<2007-06-11 19:00:43,725> <DEBUG> <default.collaxa.cube.engine.deployment> <CubeProcessHolder::loadAndBind> Check if process FTPRetrieveTOFileWriteProcess, revision 1.0 needs to be reloaded
<2007-06-11 19:00:44,037> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> JCAActivationAgent::onStateChanged State is changed for process 'bpel://localhost/default/FTPRetrieveTOFileWriteProcess~1.0/', state=OFF
<2007-06-11 19:00:44,037> <DEBUG> <default.collaxa.cube.engine.deployment> <CubeProcessHolder::updateRevision> Updated state for process FTPRetrieveTOFileWriteProcess (revision 1.0) to 1
Thanks,
Vidya

Hi SR,
You can do this by having a BPEL process with a java embedding containing below code.
* Input Variables
String processName   = (String)getVariableData("processName");
String revision      = (String)getVariableData("revision");
* Declare variables.
IBPELProcessHandle procHandle = null;
Locator loc = null;
BPELProcessMetaData bpelProcessMetadata = null;
try{
     * get Locator Instance
    loc = getLocator();
     * Lookup Process. Revision optional.
    if(revision == null || revision.trim().equals(""))
      procHandle = loc.lookupProcess( processName );
    else
      procHandle = loc.lookupProcess(processName, revision);
    if(procHandle == null)
      throw new Exception("Unable to find process: " + processName);
     * Get Metadata of the process.
    bpelProcessMetadata = procHandle.getMetaData();
     * Set Lifecycle to Retired.
     * Use setState(IBPELProcessConstants.STATE_OFF) to change process state to off.
    bpelProcessMetadata.setLifecycle(IBPELProcessConstants.LIFECYCLE_RETIRED);
     * Finally update the process with the modified metadata.
    procHandle.updateMetaData(bpelProcessMetadata);
}catch (Exception e)
addAuditTrailEntry(e);
}If you want you can schedule this process.
Regards
PavanKumar.M

File Adapter BPEL Process getting switched off

The file adapter BPEL process reads a csv file which has a series of records in itfrom /xfer/chroot/data/aramex/accountUpdate/files. In between reading the files, the BPEL process gets switched off. The below snippet is the error we found in the domain.log. Anybody can you please suggest what to do?
<2010-11-25 16:22:28,025> <WARN> <PreActivation.collaxa.cube.ws> <File Adapter::Outbound>
java.io.FileNotFoundException: /xfer/chroot/data/aramex/accountUpdate/files/VFQ-251120101_1000.csv (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at oracle.tip.adapter.file.FileUtil.copyFile(FileUtil.java:947)
at oracle.tip.adapter.file.inbound.ProcessWork.defaultArchive(ProcessWork.java:2341)
at oracle.tip.adapter.file.inbound.ProcessWork.doneProcessing(ProcessWork.java:614)
at oracle.tip.adapter.file.inbound.ProcessWork.processMessages(ProcessWork.java:445)
at oracle.tip.adapter.file.inbound.ProcessWork.run(ProcessWork.java:227)
at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:280)
at java.lang.Thread.run(Thread.java:619)
<2010-11-25 16:22:28,025> <INFO> <PreActivation.collaxa.cube.ws> <File Adapter::Outbound> Processer thread calling onFatalError with exception /xfer/chroot/data/aramex/accountUpdate/files/VFQ-251120101_1000.csv (No such file or directory)
<2010-11-25 16:22:28,025> <FATAL> <PreActivation.collaxa.cube.activation> <AdapterFramework::Inbound> [Read_ptt::Read(root)]Resource Adapter requested Process shutdown!
<2010-11-25 16:22:28,025> <INFO> <PreActivation.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework instance: OraBPEL - performing endpointDeactivation for portType=Read_ptt, operation=Read
<2010-11-25 16:22:28,025> <INFO> <PreActivation.collaxa.cube.ws> <File Adapter::Outbound> Endpoint De-activation called in adapter for endpoint : /xfer/chroot/data/aramex/accountUpdate/files/
<2010-11-25 16:22:28,095> <WARN> <PreActivation.collaxa.cube.ws> <File Adapter::Outbound> ProcessWork::Delete failed, the operation will be retried for max of [2] times
<2010-11-25 16:22:28,095> <WARN> <PreActivation.collaxa.cube.ws> <File Adapter::Outbound>
ORABPEL-11042
File deletion failed.
File : /xfer/chroot/data/aramex/accountUpdate/files/VFQ-251120101_1000.csv as it does not exist. could not be deleted.
Delete the file and restart server. Contact oracle support if error is not fixable.
at oracle.tip.adapter.file.FileUtil.deleteFile(FileUtil.java:279)
at oracle.tip.adapter.file.FileUtil.deleteFile(FileUtil.java:177)
at oracle.tip.adapter.file.FileAgent.deleteFile(FileAgent.java:223)
at oracle.tip.adapter.file.inbound.FileSource.deleteFile(FileSource.java:245)
at oracle.tip.adapter.file.inbound.ProcessWork.doneProcessing(ProcessWork.java:655)
at oracle.tip.adapter.file.inbound.ProcessWork.processMessages(ProcessWork.java:445)
at oracle.tip.adapter.file.inbound.ProcessWork.run(ProcessWork.java:227)
at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:280)
at java.lang.Thread.run(Thread.java:619)
<2010-11-25 16:22:28,315> <ERROR> <PreActivation.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "cube delivery": Process state off.
The process class "BulkAccountUpdateFileConsumer" (revision "1.0" ) 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.
Please consult your administrator if this process has been turned off inadvertently.

This patch is not for 10.1.3.1.
I have provided a response to on the following post
BPEL Process Going into Dead State Automatically.
cheers
James

How to use xPath to extract a element from a xml stringin BPEL workflow?

I have a xml string passed into the BPEL workflow, and I need to extract the value of "serviceOrderGuid" (see the xml string below), how I can use BPEL mapper to do this? I am using NetBeans 6.0/M10.
Thanks
Kebin
<Parameters xmlns="http://www.sunmicrosoft.com/TrueOMF/WorkflowInformation.xsd">
<Parameter isIn="false" isOut="true" name="serviceOrderGuid">
<Value>5e8c9de9-f9b9-4815-bc06-e1572ff122f2</Value>
</Parameter>
<Parameter isIn="false" isOut="true" name="elementOfferGuid">
<Value>4f7c9de2-f9b9-4815-bc06-e1572ee122e2</Value>
</Parameter>
</Parameters>

Thank you for your help so far, but I still have issues to be resolved.
I developed couple of workflows, in assign activity, I used query to retrieve some value from xml string, e.g.
<copy>
<from variable="OriginalEventMessage">
<query>/node()/*[ ( local-name() = 'Request' ) ]/*[ ( local-name() = 'Parameters' ) ]/*[ ( ( local-name() = 'Parameter' ) and ( @name = 'serviceOrderGuid' ) ) ]/*[ ( local-name() = 'Value' ) ]</query>
</from>
<to variable="CallMefIn" part="EventMessage">
<query>//*[local-name()='Request']/*[local-name()='Parameters']/*[local-name()='Parameter' and @name='serviceOrderGuid']/*[local-name()='Value']</query>
</to>
</copy>
at deployment, I got messages like "Starting BPELSE deploy process
FromXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
ToXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
ToXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
What is the problem?
I attach the whole deployment log for your review.
Thanks
Kebin
Stopping service assembly MefWorkflowCompositeApp on target server.
Stopping suId : MefWorkflowCompositeApp-sun-http-binding
Stopped suId : MefWorkflowCompositeApp-sun-http-binding
Shutting down service assembly MefWorkflowCompositeApp on target server.
Shutdown : MefWorkflowCompositeApp-sun-http-binding
Shutdown : MefWorkflowCompositeApp-sun-http-binding completed
Undeploying service assembly MefWorkflowCompositeApp from target server.
Shutdown : MefWorkflowCompositeApp-sun-http-binding
Shutdown : MefWorkflowCompositeApp-sun-http-binding completed
JBIMA0412: Service Assembly with ID : MefWorkflowCompositeApp has been undeployed.
Deploying service assembly MefWorkflowCompositeApp to target server.
Deploying service unit : MefWorkflowCompositeApp-sun-http-binding from C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\AlertMefBpel.wsdl'.
Retrieving document at 'MEFWEBService.wsdl', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/AlertMefBpel.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\AlertMefWeb.wsdl'.
Retrieving document at 'MEFWEBService.wsdl', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/AlertMefWeb.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\ArchitectMefBpel.wsdl'.
Retrieving document at 'MEFWEBService.wsdl', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/ArchitectMefBpel.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\ArchitectMefWeb.wsdl'.
Retrieving document at 'MEFWEBService.wsdl', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/ArchitectMefWeb.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\CallMef.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/CallMef.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\CallSD.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/CallSD.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\FeatureBuilderMefBpel.wsdl'.
Retrieving document at 'MEFWEBService.wsdl', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/FeatureBuilderMefBpel.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\FeatureBuilderMefWeb.wsdl'.
Retrieving document at 'MEFWEBService.wsdl', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/FeatureBuilderMefWeb.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\GlobalStoreMefBpel.wsdl'.
Retrieving document at 'MEFWEBService.wsdl', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/GlobalStoreMefBpel.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\GlobalStoreMefWeb.wsdl'.
Retrieving document at 'MEFWEBService.wsdl', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/GlobalStoreMefWeb.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\LocalStoreMefBpel.wsdl'.
Retrieving document at 'MEFWEBService.wsdl', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/LocalStoreMefBpel.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\LocalStoreMefWeb.wsdl'.
Retrieving document at 'MEFWEBService.wsdl', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/LocalStoreMefWeb.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\LogCurrentState.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/LogCurrentState.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\MEFWEBService.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\OperatorInputMefBpel.wsdl'.
Retrieving document at 'MEFWEBService.wsdl', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/OperatorInputMefBpel.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\OperatorInputMefWeb.wsdl'.
Retrieving document at 'MEFWEBService.wsdl', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/OperatorInputMefWeb.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\OrderManagementMefBpel.wsdl'.
Retrieving document at 'MEFWEBService.wsdl', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/OrderManagementMefBpel.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\OrderManagementMefWeb.wsdl'.
Retrieving document at 'MEFWEBService.wsdl', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/OrderManagementMefWeb.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\RBLocalStoreMefBpel.wsdl'.
Retrieving document at 'MEFWEBService.wsdl', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/RBLocalStoreMefBpel.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\RBLocalStoreMefWeb.wsdl'.
Retrieving document at 'MEFWEBService.wsdl', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/RBLocalStoreMefWeb.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\SecurityMefBpel.wsdl'.
Retrieving document at 'MEFWEBService.wsdl', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/SecurityMefBpel.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\SecurityMefWeb.wsdl'.
Retrieving document at 'MEFWEBService.wsdl', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/SecurityMefWeb.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\SmsAdministratorMefBpel.wsdl'.
Retrieving document at 'MEFWEBService.wsdl', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/SmsAdministratorMefBpel.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\SmsAdministratorMefWeb.wsdl'.
Retrieving document at 'MEFWEBService.wsdl', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/SmsAdministratorMefWeb.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\SmsParentMefBpel.wsdl'.
Retrieving document at 'MEFWEBService.wsdl', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/SmsParentMefBpel.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/SmsParentMefBpel.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\SmsParentMefWeb.wsdl'.
Retrieving document at 'MEFWEBService.wsdl', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/SmsParentMefWeb.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\SolutionDomainBpel.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/SolutionDomainBpel.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\SssMefBpel.wsdl'.
Retrieving document at 'MEFWEBService.wsdl', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/SssMefBpel.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\SssMefWeb.wsdl'.
Retrieving document at 'MEFWEBService.wsdl', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/SssMefWeb.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\SSSTalkerMefBpel.wsdl'.
Retrieving document at 'MEFWEBService.wsdl', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/SSSTalkerMefBpel.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\SSSTalkerMefWeb.wsdl'.
Retrieving document at 'MEFWEBService.wsdl', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/SSSTalkerMefWeb.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/MEFWEBService.wsdl'.
Retrieving document at 'C:\Program Files\glassfish-v2-b53\domains\domain1\jbi\service-assemblies\MefWorkflowCompositeApp\MefWorkflowCompositeApp-sun-http-binding\sun-http-binding\MefWorkflow\UtilityServiceBpel.wsdl'.
Retrieving schema at 'WorkflowInformation.xsd', relative to 'file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/service-assemblies/MefWorkflowCompositeApp/MefWorkflowCompositeApp-sun-http-binding/sun-http-binding/MefWorkflow/UtilityServiceBpel.wsdl'.
JBIMA0402: Service Assembly file:/C:/Program Files/glassfish-v2-b53/domains/domain1/jbi/tmp/28345a2b1143bbd25887fe9/MefWorkflowCompositeApp.zip has been deployed.
Starting service assembly MefWorkflowCompositeApp on target server.
Starting BPELSE deploy process
FromXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
ToXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
ToXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
FromXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
ToXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
FromXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
ToXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
FromXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
ToXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
FromXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
ToXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
FromXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
ToXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
FromXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
ToXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
ToXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
FromXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
FromXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
ToXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
FromXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
ToXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
FromXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
FromXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
ToXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
ToXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
FromXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
ToXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
FromXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
ToXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
FromXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
FromXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
ToXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
ToXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
FromXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
ToXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
FromXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
ToXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
ToXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
FromXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oasis-open.org/wsbpel/2.0/process/executable
FromXmlParser.endElement(): Found unrecognized end element </query>, namespace=http://docs.oa

RAC node outage causes SOA Suite 10.1.3.4 BPEL failure

Using weblogic 9.2 and the SOA Suite 10.1.3.4. We use a 10g Oracle RAC ( 2 nodes ); the WL cluster has a multi data source of 2 pools, each pool pointing to a single node in the rac, each pool deployed to the cluster, and the multi data source in load-balancing mode.
So the other night, one of the db nodes had a hardware failure ( ironically, with a remote monitoring / management card ). Annoying, but it should not have caused the BPEL servers to be in "FAILED NOT RESTARTABLE" status the next morning.
Jun 9, 2009 12:10:07 AM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "esbaqds2": Io exception: The Network Adapter could not establish the connection>
SEVERE: Destroying JMSDequeuer failed
oracle.jms.AQjmsException: Connection has been administratively destroyed. Reconnect.
at oracle.jms.AQjmsSession.preClose(AQjmsSession.java:980)
at oracle.jms.AQjmsObject.close(AQjmsObject.java:409)
at oracle.jms.AQjmsSession.close(AQjmsSession.java:1020)
at oracle.tip.esb.server.dispatch.JMSDequeuer.destroy(JMSDequeuer.java:419)
at oracle.tip.esb.server.dispatch.JMSDequeuer.destroyWithoutUnsubscribing(JMSDequeuer.java:395)
at oracle.tip.esb.server.dispatch.JMSDequeuer.dequeue(JMSDequeuer.java:175)
at oracle.tip.esb.server.dispatch.agent.ESBWork.process(ESBWork.java:174)
at oracle.tip.esb.server.dispatch.agent.ESBWork.run(ESBWork.java:132)
at weblogic.connector.security.layer.WorkImpl.runIt(WorkImpl.java:108)
at weblogic.connector.security.layer.WorkImpl.run(WorkImpl.java:44)
at weblogic.connector.work.WorkRequest.run(WorkRequest.java:93)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
followed by a 2 GB log file containing 1.3 million iterations of the following within the next 10 minutes before the managed servers failed.
java.lang.NullPointerException
at java.lang.String.<init>(String.java:144)
at oracle.tip.esb.server.dispatch.JMSDequeuer.dequeue(JMSDequeuer.java:168)
at oracle.tip.esb.server.dispatch.agent.ESBWork.process(ESBWork.java:174)
at oracle.tip.esb.server.dispatch.agent.ESBWork.run(ESBWork.java:132)
at weblogic.connector.security.layer.WorkImpl.runIt(WorkImpl.java:108)
at weblogic.connector.security.layer.WorkImpl.run(WorkImpl.java:44)
at weblogic.connector.work.WorkRequest.run(WorkRequest.java:93)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Both managed instances of the BPEL cluster failed, even though the 1st node of the Oracle RAC was still available.
Our 10.3 cluster, also using multi data sources to the same RAC for the OSB components, simply went on about its business using the remaining rac node pool.
Seems to be a single point of failure...

We haven't changed the JDBC connection string yet, but we did run a test in the same environment while Oracle support considers the situation.
For the test, we simply shutdown one node of the RAC and watched to see what happens. Within the space of a minute, the JDBC "Failed Reserve Request Count" was increasing by thousands on every refresh of the screen. We restarted the RAC node after 5 minutes, by which time the "Failed Reserve Request Count" was over 190,000
The 2 BPEL managed servers remained in Running status and each created a 660 MB log file within that 5 minutes. In the original outage, the nodes were down for about 15 minutes. Most of the logging is being generated from within the oracle.tip.esb classes, not by the weblogic classes. It looks like that once the pool pointing to the downed RAC node becomes disabled, the Oracle BPEL code is still trying to use it even though the multi-source JNDI is the published lookup:
INFO: JMSDequeuer::createConnection - AQ Topics
java.sql.SQLException: weblogic.common.ResourceException:
esbaqds(esbaqds2): Pool esbaqds2 is disabled, cannot allocate resources to applications..
esbaqds(esbaqds1): Pool esbaqds1 is disabled, cannot allocate resources to applications..
at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(JDBCUtil.java:250)
at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:348)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:364)
at oracle.tip.esb.server.dispatch.JMSDequeuer.createAQConnection(JMSDequeuer.java:559)
at oracle.tip.esb.server.dispatch.JMSDequeuer.dequeue(JMSDequeuer.java:159)
at oracle.tip.esb.server.dispatch.agent.ESBWork.process(ESBWork.java:174)
at oracle.tip.esb.server.dispatch.agent.ESBWork.run(ESBWork.java:132)
at weblogic.connector.security.layer.WorkImpl.runIt(WorkImpl.java:108)
at weblogic.connector.security.layer.WorkImpl.run(WorkImpl.java:44)
at weblogic.connector.work.WorkRequest.run(WorkRequest.java:93)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Caused by: weblogic.common.ResourceException:
esbaqds(esbaqds2): Pool esbaqds2 is disabled, cannot allocate resources to applications..
esbaqds(esbaqds1): Pool esbaqds1 is disabled, cannot allocate resources to applications..
at weblogic.jdbc.common.internal.MultiPool.searchLoadBalance(MultiPool.java:331)
at weblogic.jdbc.common.internal.MultiPool.findPool(MultiPool.java:202)
at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:77)
at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:346)
... 11 more
SEVERE: Failed to process deferred message
oracle.tip.esb.server.dispatch.QueueHandlerException: Error creating "weblogic.common.ResourceException: No good connections available."
at oracle.tip.esb.server.dispatch.JMSDequeuer.createAQConnection(JMSDequeuer.java:661)
at oracle.tip.esb.server.dispatch.JMSDequeuer.dequeue(JMSDequeuer.java:159)
at oracle.tip.esb.server.dispatch.agent.ESBWork.process(ESBWork.java:174)
at oracle.tip.esb.server.dispatch.agent.ESBWork.run(ESBWork.java:132)
at weblogic.connector.security.layer.WorkImpl.runIt(WorkImpl.java:108)
at weblogic.connector.security.layer.WorkImpl.run(WorkImpl.java:44)
at weblogic.connector.work.WorkRequest.run(WorkRequest.java:93)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

Java.lang.OutOfMemoryError -- Is there a way to limit BPEL instances number

Hi All,
My BPEL process is using JMS adapter to read the JMS queue. Whenever a new message arrives, a new BPEL instance is created. However, when the message gets bigger and multiple messages arrive at queue at the same time, the OC4J gets java OutOfMemory (heap space) error and was forced shutdown. I'm wondering if there's any way to limit the BPEL instance created, say, only one at a time, and the messages would be processed in sequence. Would this be a good way to not use so much heap at one time? Is there a way to limit the BPEL instance created?
Thanks for your help!
Michelle

Take a look at how to configure Jms polling interval (talks about a property that you can set to introduce a delay in between dequeues). That might be of some help to start with.
It is supposed to work exactly the way you want it i.e the activation agent does a dequeue and hand off to bpel engine (which creates an instance and uses the same thread to run as much of that instance as possible i.e till the first dehydration point). So, if your process has a dehydration point right at the beginning (which could be due to invocation of another async process, or wait or ...), you could very well see this thread go right back and process the next available message.
I believe this is a generic problem that is not necessarily jms adapter specific. One way would be to split up your process into three processes:
1. "Kickoff" process which contains just a "receive" associated with the activation agent followed by an invocation of a "Controller" process
2. "Controller" process which checks for the provided input as to which process it needs to invoke, and then goes on to check how many instances of that process are currently running; if this number is below a certain threshold, kick off the main process providing it the necessary payload gotten from the "KickOff" process
3. "Main" process which is same as your current process except that it is a typical async process without the adapter "receive" partner link
So, the idea being that for any process where you want to introduce a control-flow mechanism, you would split it into #1 and #3 above. Have one generic Controller process, which caters to all of the processes.
Would be interested in learning if others have solved this in a generic way.

BPEL Process getting halted even after expired.

I have a BPEL process which call a certain human task. human task expires in some x amount of time. so after expiry the Escalation & Renew Policy should kick in. but the task is still visible to the same user and the process is still waiting for the response from the task.
server shutdown can be a problem. because i restarted the server about the same time as the expiration time.
Thanks

This patch is not for 10.1.3.1.
I have provided a response to on the following post
BPEL Process Going into Dead State Automatically.
cheers
James

Query regarding cron expression in BPEL

Hi,
I am using the quartz scheduler in BPEL and using the cron expression in bpel.xml
but the problem I am facing is it is running for only one day it is not running for the next day
the expression I am writting in bpel.xml is
<activationAgents>
<activationAgent className="oracle.tip.adapter.fw.agent.jca.JCAActivationAgent" partnerLink="FileScBpel4" heartBeatInterval="10">
<property name="schedulerCallout">DefaultSchedulerCalloutImpl</property>
<property name="endpointScheduleOn">0 30 19 * * ?</property>
<property name="endpointScheduleOff">0 31 19 * * ?</property>
</activationAgent>
</activationAgents>
so if I deploy it in BPEL PM it will run for today at 19:30
but when I am changing the system date to the next day and changing the time to 19:30 it is not running again
can anybody plz help me out how can I schedule it for everyday 19:30

Hi Sailo,
If you use quartz as a servlet, you'll have to add the entry to you're web.xml, in addition to other servlets you create :
<servlet>
<servlet-name>QuartzInitializer</servlet-name>
<servlet-class>org.quartz.ee.servlet.QuartzInitializerServlet</servlet-class>
<load-on-startup>1</load-on-startup>
<init-param>
<param-name>config-file</param-name>
<param-value>quartz.properties</param-value>
</init-param>
<init-param>
<param-name>shutdown-on-unload</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>start-scheduler-on-load</param-name>
<param-value>true</param-value>
</init-param>
</servlet>
Cheers
Pucha Anirudh

Deployment of BPEL (and ESB) into Clustered Environment

Hi All,
I was after any view points / pointers into peoples experiences into deployment of BPEL and ESB into a clustered Oracle iAS SOA suite environment, where there are two or more nodes running BPEL, ESB etc with a corresponding OHS Loan Balancers. I have been unable to find any specific information with regards to recommendations into the best ways to deploy into a clustered environment.
My viewpoints are there are two alternative approaches that could be used, both of which use ANT deployment scripts to register / deploy the various services.
(1) Leaving all nodes up in the cluster and using a properties file to specify the relevant details, deploy to one environment allowing the load balancer to distribute the software to the respective nodes in the cluster
(2) Deploy to each of the nodes in turn ensuring all other nodes in the cluster are taken down during each separate deployment
What are other peoples thoughts / experiences / recommendations?
Thanks in Advance
Dave

I don't believe there is any real information on deployments in a cluster in those documents.
There is a note on metalink 457654.1 which says to apply to each node, while doing this shut down the other servers. From experience this worked for some configuration and not others.
Can you say what cluster deployment you used, e.g. 10.1.3.1 or 10.1.3.3 with BPEL and ESB-RT in the same oc4j?
Also what version are you on. If you are on 10.1.3.4 using the 10.1.3.3 deployment configuration you don't need to shutdown the nodes. And you can get away with just deploying to one node but make sure your <ORACLE_HOME>/bpel/system/config/collaxa-config.xml file has been set to cluster = true. Look at metalink note 746251.1.
You can experience the notorious Process Lock Timeout Error when not shutdown cleanly but this is resolved using the best practice guide http://www.oracle.com/technology/tech/soa/soa-suite-best-practices/soa_best_practices_1013x_drop1.pdf
ESB can be applied to just one node.
Make sure that all your endpoints are pointing to the load balancer and not the actual node themselves.
Also you connect string is different in your build.properties make sure of the following
cluster = true
oc4jinstancename = default_group
local.oc4jinstancename = oc4j_soa (or the oc4j container with BPEL)
esb
deployer.uri=deployer:cluster:opmn://hostname:opmn port/default_group
cheers
James

DB Adapter call when DB is Down -- No BPEL Instance created

I have a simple DB Adapter BPEL Process. Works well. Now I shutdown then database. Problem is when I initiate BPEL Process via the BPEL Dashboard, I get the following message:
Cannot find the specified instance
If the instance has recently been initiated, the invocation data may not have been delivered to the engine yet. Refresh your browser window or try again in a few seconds.
I find no trace of this BPEL process, “Flow, Audit and Debug” all show the same message for ever!!!
Any comments would be appreciated.
Thanks.

Hi
When you initiate the process, the DB Adapter looks for the relevant dehydration store which logs the deployed bpel processes.
So, you need to have your db up, and also, mention the exact error messages being logged after turning the debug on for activation, messaging loggers in BPEL Admin.
Cheers
Anirudh Pucha

Configuring BPEL PM with Oracle XE database

Hi,
I have been using my BPEL PM with default olite db quite a days ago and it was running fine. Now I have changed the dehydration to Oracle XE database and chnaged the corresponding data-source.xml files.
I can access the default domain from BPEL console and I can see the processes.
But I am getting the error when am creating an instance of the process and also I am not able to login to the worklist application.
The error I got is shown below.
<2005-12-26 12:38:57,375> <ERROR> <default.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "cu
be delivery": Cannot fetch a datasource connection.
The process domain was unable to establish a connection with the datasource with the connection URL "loc/BPELServerDat
aSource". The exception reported is: Cannot fetch a datasource connection.
The process domain was unable to establish a connection with the datasource with the connection URL "loc/BPELServerDat
aSource". The exception reported is: Listener refused the connection with the following error:
ORA-12519, TNS:no appropriate service handler found
The Connection descriptor used by the client was:
152.69.213.27:1521:xe
Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that th
e datasource connection parameters (user/password) is currently valid.
Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that th
e datasource connection parameters (user/password) is currently valid.
<2005-12-26 12:38:57,515> <ERROR> <default.collaxa.cube.engine.dispatch> <BaseScheduledWorker::process> Failed to hand
le dispatch message ... exception ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeI
nstanceMessage"; the exception is: Cannot fetch a datasource connection.
The process domain was unable to establish a connection with the datasource with the connection URL "loc/BPELServerDataSource". The exception reported is: Cannot fetch a datasource connection.
The process domain was unable to establish a connection with the datasource with the connection URL "loc/BPELServerDataSource". The exception reported is: Listener refused the connection with the following error:
ORA-12519, TNS:no appropriate service handler found
The Connection descriptor used by the client was:
152.69.213.27:1521:xe
Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that th
e datasource connection parameters (user/password) is currently valid.
Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that th
e datasource connection parameters (user/password) is currently valid.
Waiting for any idea to solve this issue.
Thanks in advance
Aki

Similar problems, in my case I was trying out the DatabaseServer on an Oracle XE database using the Embedded OC4J A/S bundled with RC3; this combination turns out explosive :)
The service was simply doing a select statement and the number of connections kept growing and growing during my tests; you can see them from the command line when typing `netstat -t` - eventually it just stopped working while I was testing; in the web service it reported:
ORA-12519, TNS:no appropriate service handler found
But my listner was running !!! I tried the connection from JDS and it complained about the same thing - then eventually I tried it from sqlplus and it showed:
ORA-00020: maximum number of processes (%s) exceeded
So now finally we're getting somewhere - after googling I found this web site; a good laugh:
http://it.newinstance.it/2007/06/01/ora-12519-tnsno-appropriate-service-handler-found/
So basically I did from the command line the following:
lsnrctl stop;
sqlplus "/as sysdba"
shutdown immediate;
startup;
alter system set processes=150 scope=spfile;
shutdown immediate;
startup;
lsnrctl start;
Now hopefully this will solve it; I'd still like to know how to change the OC4J connection pool settings for the SOA stuff - is this possible at all or does it have some kind of minimum requirement ?
After restarting and testing a few times; my service is actually working so I'm very pleased :)
Regards

BPEL startup error (Linux)

Hi,
I've sucessfully installed BPEL PM on Linux AS 2.1. In addition, I set up Oracle 9i for use with BPEL according "BPEL Process Manager Oracle 9i Configuration Guide".
I'm able to login on database:
[oracle@ofswas bin]$ sqlplus orabpel/[email protected]
SQL*Plus: Release 9.0.1.4.0 - Production on Tue Nov 9 15:35:48 2004
(c) Copyright 2001 Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.0.1.5.0 - Production
With the Partitioning option
JServer Release 9.0.1.4.0 - Production
SQL>
Here is my data-source.xml:

<data-source class="com.evermind.sql.DriverManagerDataSource"
name="BPELServerDataSource"
location="jdbc/BPELServerDataSource"
xa-location="BPELServerDataSource"
ejb-location="jdbc/BPELServerDataSource"
connection-driver="oracle.jdbc.OracleDriver"
max-connections="50"
min-connections="10"
username="orabpel"
password="orabpel"
url="jdbc:oracle:thin:@ofswas.compasso.com.br:1521:asdb"/>
<data-source class="com.evermind.sql.DriverManagerDataSource"
name="BPELSamplesDataSource"
location="jdbc/BPELSamplesDataSource"
xa-location="BPELSamplesDataSource"
ejb-location="jdbc/BPELSamplesDataSource"
connection-driver="oracle.jdbc.OracleDriver"
max-connections="50"
min-connections="10"
username="orabpel"
password="orabpel" url="jdbc:oracle:thin:@ofswas.compasso.com.br:1521:asdb"/>
When starting BPel, I got the following error:
<PlatformAdaptor_oc4j_10g::registerShutdownHook> Registered shutdown hook for platform OC4J
<ConnectionFactoryImpl::init> Initialized connection factory jdbc/BPELServerDataSource
<ConnectionFactoryImpl::init> Initialized connection factory jdbc/BPELServerDataSource
04/11/09 15:39:32 ORABPEL-03002
Cannot lookup db schema version.
The process domain 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: Internal Error:Invalid Connect String
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.
sql statement: SELECT table_name FROM all_tables WHERE LOWER( table_name ) = ?
04/11/09 15:39:32 at com.collaxa.cube.engine.adaptors.olite.util.SchemaUtils.isSchemaInstalled(SchemaUtils.java:165)
04/11/09 15:39:32 at com.collaxa.cube.engine.adaptors.olite.util.SchemaUtils.installSchema(SchemaUtils.java:70)
04/11/09 15:39:32 at com.collaxa.cube.engine.adaptors.olite.util.SchemaUtils.installServerSchema(SchemaUtils.java:52)
04/11/09 15:39:32 at com.collaxa.cube.engine.adaptors.util.DataSourceSchemaUtils$1.installSchema(DataSourceSchemaUtils.java:58)
04/11/09 15:39:32 at com.collaxa.cube.engine.adaptors.util.DataSourceSchemaUtils.getDataSourceType(DataSourceSchemaUtils.java:134)
04/11/09 15:39:32 at com.collaxa.cube.engine.adaptors.util.DataSourceSchemaUtils.getServerDataSourceType(DataSourceSchemaUtils.java:101)
04/11/09 15:39:32 at com.collaxa.cube.admin.adaptors.ServerAdaptorManager.init(ServerAdaptorManager.java:73)
04/11/09 15:39:32 at com.collaxa.cube.admin.ServerManager.__init(ServerManager.java:175)
04/11/09 15:39:32 at com.collaxa.cube.admin.ServerManager.init(ServerManager.java:94)
04/11/09 15:39:32 at com.collaxa.cube.beans.ServerBean.init(ServerBean.java:203)
04/11/09 15:39:32 at IServerBean_StatelessSessionBeanWrapper14.init(IServerBean_StatelessSessionBeanWrapper14.java:79)
04/11/09 15:39:32 at com.collaxa.cube.admin.CXLoaderServlet.init(CXLoaderServlet.java:59)
04/11/09 15:39:32 at javax.servlet.GenericServlet.init(GenericServlet.java:258)
04/11/09 15:39:32 at com.evermind.server.http.HttpApplication.loadServlet(HttpApplication.java:2132)
04/11/09 15:39:32 at com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4573)
04/11/09 15:39:32 at com.evermind.server.http.HttpApplication.initPreloadServlets(HttpApplication.java:4667)
04/11/09 15:39:32 at com.evermind.server.http.HttpApplication.initDynamic(HttpApplication.java:811)
04/11/09 15:39:32 at com.evermind.server.http.HttpApplication.<init>(HttpApplication.java:533)
04/11/09 15:39:32 at com.evermind.server.Application.getHttpApplication(Application.java:889)
04/11/09 15:39:32 at com.evermind.server.http.HttpServer.getHttpApplication(HttpServer.java:688)
04/11/09 15:39:32 at com.evermind.server.http.HttpSite.initApplications(HttpSite.java:587)
04/11/09 15:39:32 at com.evermind.server.http.HttpSite.setConfig(HttpSite.java:263)
04/11/09 15:39:32 at com.evermind.server.http.HttpServer.setSites(HttpServer.java:259)
04/11/09 15:39:32 at com.evermind.server.http.HttpServer.setConfig(HttpServer.java:160)
04/11/09 15:39:32 at com.evermind.server.ApplicationServer.initializeHttp(ApplicationServer.java:2385)
04/11/09 15:39:32 at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:1542)
04/11/09 15:39:32 at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:92)
04/11/09 15:39:32 at java.lang.Thread.run(Thread.java:534)
<CXLoaderServlet::init>
ORABPEL START-UP ERROR!!!!!!!!
OraBPEL run-time system failed to start due to exception:
Cannot lookup db schema version.
The process domain 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: Internal Error:Invalid Connect String
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.
sql statement: SELECT table_name FROM all_tables WHERE LOWER( table_name ) = ?
04/11/09 15:39:32 Web-App orabpel:httpbinding (0.0.0.0/0.0.0.0:9700/httpbinding) started...
04/11/09 15:39:32 Building Application TagLibrary Persistent Cache for httpbinding
04/11/09 15:39:32 Done getting application current resources
04/11/09 15:39:32 Done initializing cache
04/11/09 15:39:32 Refreshing application cache - from existing cache ...
04/11/09 15:39:32 Found 0 listeners
04/11/09 15:39:32 Oracle Application Server Containers for J2EE 10g (10.1.2.0.0) initialized
04/11/09 15:39:32
04/11/09 15:39:33 java.io.IOException: java.io.IOException: cmd: not found
at java.lang.UNIXProcess.<init>(UNIXProcess.java:143)
at java.lang.Runtime.execInternal(Native Method)
at java.lang.Runtime.exec(Runtime.java:566)
at java.lang.Runtime.exec(Runtime.java:491)
at java.lang.Runtime.exec(Runtime.java:457)
at com.collaxa.cube.util.CommandExecute.execute(CommandExecute.java:49)
at com.collaxa.cube.admin.adaptors.platform.PlatformAdaptor_oc4j_10g$ShutdownHook.doKillOlite(PlatformAdaptor_oc4j_10g.java:127)
at com.collaxa.cube.admin.adaptors.platform.PlatformAdaptor_oc4j_10g$ShutdownHook.run(PlatformAdaptor_oc4j_10g.java:96)
Can someone help me?
thanks
Alisson

Hello,
I think you have omitted the username and password in connection string for your jdbc.
In fact when you test the connection your string is:
[oracle@ofswas bin]$ sqlplus orabpel/[email protected]
username/password@domain
and with it you can connect
but your data-sources.xml is:
<data-source class="com.evermind.sql.DriverManagerDataSource"
name="BPELServerDataSource"
location="jdbc/BPELServerDataSource"
xa-location="BPELServerDataSource"
ejb-location="jdbc/BPELServerDataSource"
connection-driver="oracle.jdbc.OracleDriver"
max-connections="50"
min-connections="10"
username="orabpel"
password="orabpel"
url="jdbc:oracle:thin:@ofswas.compasso.com.br:1521:asdb"/>
As you see in the url lack username and password to acces to your database
So try to use correct string:
url="jdbc:oracle:thin:[username/password]@host:port:sid"/>
I hope this help you...
ByeBye
Andrea

BPEL PM 10.1.2 B3 Shutdown

Similar Messages

Maybe you are looking for