BPEL Server Restarts intermittently

Hi All,
I have got a strange problem with my BPEL Server. Every once in a while the BPEL Server restarts on its own. I do not know if it has to do something with memory leaks or performance or some other reason.
I have made my logs to roll at every 2 GB. I also noticed that the BPEL Domains are reloaded everytime the logs are rolled. If during this restart there is some process on the go then i get erroneous results.
I am not able to reproduce the issue but it does happen intermittently. Has anyone else faced this issue?

Also check logs in $OAS_HOME/opmn/logs/ for "Restart" messages, then check the timeouts for the BPEL instance in $OAS_HOME/opmn/config/opmn.xml. These are maybe too low.
--olaf

Similar Messages

BPEL process instance doesn't restart execution after BPEL server restart

I am using Oracle BPEL server 10.1.2 on Windows with the Oracle lite 10G dehydration datastore.
I have a one BPEL process (proc1) that invokes another BPEL process (proc2) synchronously. proc1 also invokes proc3 (also a BPEL process, but probably doesn't matter) synchronoulsy in parallel with proc2.
proc2 has a wait of ~30seconds in it. As soon as proc1 invokes proc2, I shutdown BPEL. Now, when I restart the BPEL server, proc2 instance finishes its execution. But, I don't see instances of proc1 and proc3 in the BPEL console.
Here are my questions:
1. If proc1 invokes proc2 and proc3 in parallel, shouldn't I see instances of proc2 and proc3 at the same time? I only see proc2 not even proc1.
2. Why doesn't proc1 resume its execution after BPEL server is restarted?
Any pointers appreciated.

1. If proc1 invokes proc2 and proc3 in parallel, shouldn't I see instances of proc2 and proc3 at the same time? I only see proc2 not even proc1.
Please read this thread:
ParallelFlows + sync flow

OVM Server restarting intermittently

HI,
One of the customer is facing some issue with the multipath maps because of which some of the paths are failing abruptly. While they fails there is a SCSI reset command issued which actually reset all buses and everything loses connectivity and paths are reregistered again. Because of this the Oracle VM server is reboot intermittently.
I am unable to figure out why this is happening, the customer has tested the setup with Citrix Xenserver and it works fine, even he has check physical connectivity to the LUNs are ok.
The output of multipath -ll also listed below.
[root@prodsrv04 ~]# multipath -ll
36001438009b01b610000800000110000 dm-1 HP,HSV340
size=1.0T features='0' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=1 status=active
| `- 2:0:0:2 sdc 8:32 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 3:0:0:2 sde 8:64 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 3:0:1:2 sdg 8:96 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 2:0:1:2 sdi 8:128 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 2:0:2:2 sdk 8:160 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 2:0:3:2 sdm 8:192 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 3:0:2:2 sdo 8:224 active ready running
`-+- policy='round-robin 0' prio=1 status=enabled
`- 3:0:3:2 sdq 65:0 active ready running
36001438009b01b6100008000002e0000 dm-0 HP,HSV340
size=20G features='0' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=0 status=active
| `- 2:0:0:1 sdb 8:16 active faulty running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 3:0:0:1 sdd 8:48 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 3:0:1:1 sdf 8:80 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 2:0:1:1 sdh 8:112 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 2:0:2:1 sdj 8:144 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 2:0:3:1 sdl 8:176 active ready running
|-+- policy='round-robin 0' prio=1 status=enabled
| `- 3:0:2:1 sdn 8:208 active ready running
`-+- policy='round-robin 0' prio=1 status=enabled
`- 3:0:3:1 sdp 8:240 active ready running
[root@prodsrv04 ~]#
Regards,
Snehangshu Karmakar

same issue here, with this setup : My 8-node pools go regularly into a reboot frenzy.
device {
vendor "HP"
product "HSV340"
path_grouping_policy group_by_prio
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
path_selector "round-robin 0"
path_checker tur
features "0"
hardware_handler "0"
prio alua
failback immediate
rr_weight uniform
no_path_retry 10
rr_min_io 100
The nodes are 3.0.2 and 3.0.3, with the same behaviour.
I also observed that same behaviour on nodes
- with Emulex HBA and others with Qlogic HBA
- with and without VT-d flag
- with nodes behind HP c7000 VirtualConnect and other behind simple FC switches
I also observe frequent multipathd hang stacks in /var/log/messages, occasionally followed by fencing.
I pushed the DEAD_THRESHOLD to 121, but it did not help either.
I currently investigate with the SAN team if LU failover/failback are logged on the array controllers when the cluster nodes reboots.
Is there a known fix/workaround for this ?

How to avoid BPEL process deployment after server restart

Hi,
Message flow in my application is as below
BPEL1 --> ESB --> BPEL2
After every server restart the ESB is failing to invoke a perticular operation of BPEL2 service. All other operations of BPEL2 are working fine.
We are redeploying the BPEL2 proccess everytime the server restart happens to fix this issue. As a temporary fix, we are trying to bypass the ESB and directly invoke BPEL2 from BPEL1, but not sure if this solution works.
Can someone please suggest me as to how to avoid redeployment of the BPEL2 process?
Please let me know incase any additional information is required.
Thanks in advance.
Regards,
Manoj
Edited by: user11290555 on Jun 20, 2010 3:18 PM

Hi,
try the SOA forum. This here is for JDeveloper and ADF related questions
Frank

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/

BPEL Server java.lang.NullPointerException

I have been getting a java.lang.NullPointerException after I try to add a Database adapter to a BPEL process. I get the exception even after I delete everything I added before I got the exception. Here is the text from the screen that the BPEL Console puts up:
Oracle BPEL Process Manager Full Cycle
An unexpected error has occurred while executing your request. This is most likely related to a defect in the Oracle BPEL Process Manager product. We apologize you can post the error to the OTN forum and we will get back to you as soon as possible.
Attachments:
Build Information:
Oracle BPEL Server version 10.1.2.0.0
Build: 1442
Build time: Fri Apr 29 16:59:32 PDT 2005
Build type: release
Source tag: BPELPM_10_1_2_release_branch
Exception Message:
[java.lang.NullPointerException]
null
Exception Trace:
java.lang.NullPointerException
     at com.collaxa.cube.engine.deployment.ProcessRevisionRegistry$RevisionTable.remove(ProcessRevisionRegistry.java:296)
     at com.collaxa.cube.engine.deployment.ProcessRevisionRegistry.delete(ProcessRevisionRegistry.java:112)
     at com.collaxa.cube.engine.deployment.CubeProcessLoader.destroy(CubeProcessLoader.java:596)
     at com.collaxa.cube.engine.deployment.CubeProcessHolder.reload(CubeProcessHolder.java:972)
     at com.collaxa.cube.engine.deployment.CubeProcessHolder.loadAndBind(CubeProcessHolder.java:922)
     at com.collaxa.cube.engine.deployment.CubeProcessHolder.getProcess(CubeProcessHolder.java:787)
     at com.collaxa.cube.engine.deployment.CubeProcessHolder.getProcess(CubeProcessHolder.java:765)
     at com.collaxa.cube.engine.deployment.CubeProcessHolder.getStatus(CubeProcessHolder.java:211)
     at com.collaxa.cube.engine.deployment.DeploymentHelper.lookupProcessStatus(DeploymentHelper.java:301)
     at com.collaxa.cube.ejb.impl.FinderBean.lookupProcess(FinderBean.java:86)
     at IFinderBean_StatelessSessionBeanWrapper42.lookupProcess(IFinderBean_StatelessSessionBeanWrapper42.java:228)
     at com.oracle.bpel.client.Locator.lookupProcess(Locator.java:245)
     at displayProcess.jspService(_displayProcess.java:88)
     at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
     at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347)
     at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
     at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:810)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:322)
     at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:220)
     at com.collaxa.cube.fe.DomainFilter.doFilter(DomainFilter.java:138)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:649)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:322)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:790)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:270)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
     at java.lang.Thread.run(Thread.java:534)
Please let me know if I am doing anything wrong.
Thanks,
Jeff

A follow on to the last post, after I stopped and then restarted the BPEL Server, the process loaded correctly and the error did not reappear.

BPEL Server Connection

Hi All,
Somehow am not able to start my BPEL Server now. It is giving error while coneectiong from JDev.
Also BPEL Console is not accessible.
BPEL startup window shows error like
JSP-0008 Unable to dispatch JSP Page :Exception:java.io.FileNotFoundException: D:\BPEL_Homel\system\appserver\oc4j
\j2ee\home\default-web-app\BPELConsole\default\index.jsp (The system cannot find the path specified)
thanks

Have you performed any upgrade recently?
There has been a problem with the orabpel.ear file in some environments. The issue
can be verified by checking the size of the orabpel.ear files in the the following locations
$ORACLE_HOME/bpel/system/services/lib
and
$ORACLE_HOME/j2ee/oc4j_soa/applications
If only one of them is of size 2530260 bytes, then you have hit upon the cause for this issue in your environment.
Solution
Copy the orabpel.ear from $ORACLE_HOME/bpel/system/services/lib (the one that is of size 2530260 bytes) to the location
$ORACLE_HOME/j2ee/oc4j_soa/applications (to replace the one that is not 2530260 bytes) and restart.
cheers
James

Bpel Server

Hi,
I am getting an error while starting my bpel server, the error is "Clearing WSDL file cache for BPELProcess11.0".
Though I went to the BPEL console and cleared the WSDL cache, the server gives out a message "Purged WSDL cache for domain default and
also in the BPEL designer I am not getting the BPEL deployment option.
Thanks & Regards,
Ramu

wsdl cache claering at restart is perfect and ok, this is no error ..
try to use the deployment tool in jdev, usually it takes some time to load the domains .. - so instead of deploy to domain, you should have a second link in the context menu, ..
hth clemens

I have problem with the BPEL server caching the jar file of Instance

Is there any way to undeploy and redeploy a process where you have changes to the underlying DA, without the BEPL server being restarted. This always works in my Local BPEL server in my Laptop. But when deploying in the hosted BPEL enviroment it becomes a big problem in getting it restarted when ever I MAKE changes.
Is there any other way to disable the Cache of the instance and make it use the newer version uploaded. One more thing if the connection to a database is severed, then the DA will not work until the server is restarted. All the instances using the said connection is failing with either "Invalid Datatype" or "Socket Read exception". Can someone help!!
Thanks,
Prabhakar

Hi,
have you tried to kill the session of the DA in the database?

Composite with dependency not working after soa server restart

Hello,
I have composite application that invokes another composite application. After deploying those work fine. But after restarting soa server the one having dependency does not work any more. To soa server log I get following:
<Jul 1, 2010 11:45:29 AM EEST> <Error> <oracle.integration.platform> <SOA-20003> <Unable to register service.
oracle.fabric.common.FabricException: Error in getting XML input stream: http://Yacico:8001/soa-infra/services/default/validationForCC/getStatusByCC?WSDL: Response: '503: Service Unavailable' for url: 'http://Yacico:8001/soa-infra/services/default/validationForCC/getStatusByCC?WSDL'
at oracle.fabric.common.metadata.MetadataManagerImpl.getInputStreamFromAbsoluteURL(MetadataManagerImpl.java:276)
Caused By: java.io.FileNotFoundException: Response: '503: Service Unavailable' for url: 'http://Yacico:8001/soa-infra/services/default/validationForCC/getStatusByCC?WSDL'
<Jul 1, 2010 11:45:30 AM EEST> <Error> <oracle.integration.platform> <SOA-20020> <Deployment of composite "POProcessing" failed: Unable to find a WSDL that has a definition for service {http://oracle.com/sca/soapservice/POProcessing/POProcessing/receivePO}receivePO and port execute_pt. Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace, service name, and port name. In addition, check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally, validate the HTTP proxy settings for the server..>
So POProcessing does not work any more after server restart. validationForCC works fine also after server restart. Url http://...validationForCC/getStatusByCC?WSDL points to wsdl file and is visible by browser.
I use soa suite 11g patch set 2 (11.1.1.3) running on redhat enterprise linux 5.
Any idea what is the problem?
Is it somehow possible to configure which composites are started first during server startup?
regards, Matti
Edited by: user10197965 on Jul 1, 2010 2:28 AM

Yes, I did that. I'm not all that happy about this as a solution either, but it's better than making multiple copies.
We have since found out that his is a known bug and that it is fixed in some, but not all, deployments.
-------- see below -------------
Composites With WSDL Dependencies Fail To Deploy Following SOA Server Restart [ID 1272070.1]
Modified:Jul 19, 2012 Type:PROBLEM Status:MODERATED Priority:3
In this Document
 Symptoms
 Cause
 Solution
 References
This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
Applies to:
Oracle SOA Platform - Version 11.1.1.3.0 and later
Information in this document applies to any platform.
Symptoms
A SOA Project has an external reference to a Web Service or a reference to another Composite.
When the SOA Server is started, the Composite is trying to access the WSDL of it's referenced Web Service in order to load data structures. If SOA can not find the WSDL then the Composite fails to load/deploy.
Once this happens the Composite can not be started, or shutdown, from Enterprise Manager Fusion Middleware Control Application.
Related Error Messages:
[ERROR] [SOA-20020] ... Unable to find a WSDL that has a definition for service ... Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace, service name, and port name. In addition, check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally, validate the HTTP proxy settings for the server.]
javax.wsdl.WSDLException: WSDLException: faultCode=INVALID_WSDL: Error reading import of oramds
Cause
When SOA Server is restarting the Composite can not access the WSDL of it's referenced Web Service (it is not available).
In the first scenario there are two Composites on the same server: CompositeA and CompositeB.
In SOA Suite 11g there is no possibility to specify the load order for the composites. If CompositeA references CompositeB and if CompositeA is firstly loaded then it can not access the WSDL from CompositeB and the issue occurs.
In the second situation there is one Composite on the server (CompositeA) which references an external WebService (ExternalWS). If the ExternalWS is not available when the SOA Server is starting then this issue occurs.
Solution
Solution 1
Redeploy the affected Composite into the SOA Server.
You can do that but it is not advisable in a production environment and in a development environment it will take a lot of time to redeploy the composite manually
Solution 2
Copy the abstract WSDL locally into the project.
This is documented in these articles in our Knowledge base:
• Document:1155033.1 Node Restart Cause Composites To Become Unavailable. Response: '503: Service Unavailable'
• Document:1151973.1 Boot Order Of The Composites Upon Soa Suite Restart
Steps:
o a. Copy and use the WSDL file in the Project
o b. Edit the WebService Adapter
o c. Change the "WSDL URL" to point to the WSDL copied into the project
o d. Redeploy the Project
o e. Make this configuration with all the Projects that have a references with other Web Services
Solution 3
Use shared artifacts in Metadata Service (MDS). A WSDL used by more than one composite is a shared artifact per definition. If the WSDL structure is changed (that is not happening frequently in a production environment), you will normally deploy a composite with a new version because overwriting it will break your production environment. Moreover, in a development environment you will need a proper process in place where different developers access the same artifacts within MDS. In addition, when you use external WSDLs (owned by third parties), you will have a proper process/agreement in place to be notified about modifications affecting your applications.
1. In order to use shared artifacts a MDS connection must be configured in jDeveloper:
http://download.oracle.com/docs/cd/E14571_01/integration.1111/e10224/sca_lifecycle.htm#SOASE85488
2. Deploy the shared artifacts:
o a. Create a JAR profile and include the artifacts to share
o b. Create a SOA bundle that includes the JAR profile
o c. Deploy the SOA bundle to the application server
http://download.oracle.com/docs/cd/E14571_01/integration.1111/e10224/sca_lifecycle.htm#SOASE85472
If the shared artifacts (WSDLs) needed are from other composites this step can be skipped
3. Create a new WebService
o a. When completing the "WSDL URL" click on "Find existing WSDL's"
o b. Select "Resource Palette"
o c. Go to the SOA-MDS
o d. Select a WSDL from a Composite or the one deployed at step 2.
Known Restriction 1
The port and the location for the WSDL reference is not completed automatically by jDeveloper in the composite.xml file. This information must be inserted manually. In Bug:10287325 is raised this issue and it is available for SOA 11gPS2+.
Known Restriction 2
Another issue regarding MDS caching is raised in Bug:10218147 - the MDS cache is not refreshed when an artifact is deployed or deleted.
In order to refresh this cache the server must be restarted. This Bug resolves the issue but in a production environment the server restart will be the preferred option. The reason for that is because in a production environment you never deploy single composites under the same version after artifacts (WSDLs) have been modified.
The fix for the Bug:10218147 can be an acceptable solution in development environment where redeployment would be quicker than restarting the server.
Bug:10218147 is available for SOA 11gPS2+.
To find out more information about how to use Shared Metadata check the following documentation:
Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite 11g
41 Deploying SOA Composite Applications
41.7.3 Deploying and Using Shared Metadata Across SOA Composite Applications in Oracle JDeveloper
URL:
http://download.oracle.com/docs/cd/E14571_01/integration.1111/e10224/sca_lifecycle.htm#CACFEAJJ
Solution 4
The last solution is to use an UDDI (Universal Description Discovery and Integration).
Oracle recommends Oracle Service Registry 11g (OSR). The advantage is that you can use OSR and SOA Suite in a Shared WebLogic Domain.
http://www.oracle.com/technetwork/middleware/registry/overview/index.html
http://blogs.oracle.com/governance/2010/05/oracle_service_registry_11gr1.html
To find out more information about Oracle Service Registry check the following documentation:
Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite 11g
33 Configuring Service and Reference Binding Components
33.1.3 Changing the Endpoint Reference and Service Key for Oracle Service Registry Integration
http://download.oracle.com/docs/cd/E15523_01/integration.1111/e10226/bc_config.htm#SOAAG37248
Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite 11g
A BPEL Process Activities and Services
A.4 Publishing and Browsing the Oracle Service Registry
http://download.oracle.com/docs/cd/E15523_01/integration.1111/e10224/bp_appx_ref.htm#SOASE85561
Oracle Fusion Middleware Service Registry 11g
http://download.oracle.com/otndocs/tech/soa/OSR11gR1ProductDocumentation.pdf
Solution 5
In case you have BPM Components in the Composites deployed check the following note:
Document 1317803.1 Soa Suite Composite Fails To Deploy Upon Restart Of Managed Server
The issue is caused by the Bug:11822470 SOA SUITE COMPOSITE FAILS TO DEPLOY UPON RESTART OF MANAGED SERVER
References
BUG:10218147 - WSDL CHANGES NEED SOA SUITE SERVER RESTART
BUG:10278478 - WHEN SOA SERVER IS RESTARTED, SOME SOA COMPOSITES COULD NOT LOAD/BE DEPLOYED
BUG:10287325 - ABSTRACT WSDL NOT AVAILABLE WHEN COMPOSITE STARTED
BUG:10311698 - WHEN SOA SERVER IS RESTARTED, SOME SOA COMPOSITES CAN NOT BE STARTUP / SHUTDOWN
BUG:11822470 - SOA SUITE COMPOSITE FAILS TO DEPLOY UPON RESTART OF MANAGED SERVER
@ BUG:9267312 - MDS ARTIFACTS ARE STILL CACHED AFTER DELETING
@ BUG:9708488 - AFTER SOA RESTART, ALL PROCESSES HAVE TO BE REDEPLOYED
@ BUG:9749845 - SCHEMA CACHE STARTS EMPTY AFTER RE-START, BUT NOT AFTER DEPLOYMENT
NOTE:1151973.1 - Boot Order Of The Composites Upon Soa Suite Restart
NOTE:1155033.1 - Node Restart Cause Composites To Become Unavailable. Response: '503: Service Unavailable'
NOTE:1317803.1 - Soa Suite Composite Fails To Deploy Upon Restart Of Managed Server
Bug 11822470 : SOA SUITE COMPOSITE FAILS TO DEPLOY UPON RESTART OF MANAGED SERVER
 Bug Attributes
Type B - Defect Fixed in Product Version 11.1.1.6
Severity 2 - Severe Loss of Service Product Version 11.1.1.4
Status 80 - Development to QA/Fix Delivered Internal Platform 912 - Microsoft Windows (32-bit)
Created Mar 1, 2011 Platform Version 2003
Updated Oct 12, 2012 Base Bug N/A
Database Version N/A Affects Platforms Generic
Product Source Oracle
Abstract: SOA SUITE COMPOSITE FAILS TO DEPLOY UPON RESTART OF MANAGED SERVER
*** 03/01/11 08:07 am ***
Customer has a project consists of two services for interaction with the
process and one reference to an external service.
On deployment of the process to an Enterprise Environment, the process works
as expected. However, upon a restart of the managed server, the process will
then fail to deploy.
Workaround used is to redeploy the project again.
Bug 10278478 : WHEN SOA SERVER IS RESTARTED, SOME SOA COMPOSITES COULD NOT LOAD/BE DEPLOYED
 Bug Attributes
Type B - Defect Fixed in Product Version
Severity 2 - Severe Loss of Service Product Version 11.1.1.3.0
Status 92 - Closed, Not a Bug Platform 226 - Linux x86-64
Created Nov 10, 2010 Platform Version RED HAT ENTERPRISE LINUX 5
Updated Dec 10, 2010 Base Bug N/A
Database Version N/A Affects Platforms Generic
Product Source Oracle
Abstract: WHEN SOA SERVER IS RESTARTED, SOME SOA COMPOSITES COULD NOT LOAD/BE DEPLOYED
Detailed Problem Description
====================
When a SOA composite get dependencies with other SOA composites located on the same server, if the dependency is still not loaded, the SOA composite will not be loaded, and there is no possibilities for Entreprise Manager console to restart it (EM crash). The only way to make it working is to redeployed the SOA composite from jDeveloper that is not acceptable in a production environment.
The composite that has the issue cannot be start-up or shut-down, although the Enterprise Manager do not show any errors with it.

Reload of composite on server restart

Hi,
We have a processes which is invoking some 5 to 6 other bpel processes.On server restart this dependent process is getting loaded first ,i.e prior to the load of other bpel processes.So the reload is failing with :
The composite OrderRespOAppProcessSrvc (1.0) is not available. This could happen because either the composite has been undeployed or soa-infra has not yet loaded this composite.
Error occurred during deployment of component: OrderRespOAppProcessSrvc to service engine: implementation.bpel, for composite: OrderRespOAppProcessSrvc: ORABPEL-05250 Error deploying BPEL suitcase. error while attempting to deploy the BPEL component file "D:\SOA_Middleware\user_projects\domains\dev_domain\servers\soa_server1\dc\soa_4b0a73b3-5a1e-4ab2-b7b7-41bb8f392586"; the exception reported is: java.lang.IllegalStateException: this is only a psuedo object This error contained an exception thrown by the underlying deployment module. Verify the exception trace in the log (with logging level set to debug mode). 
oracle.sysman.emSDK.app.exception.EMSystemException
 at oracle.sysman.emai.model.sca.composite.core.impl.EMCompositeModel.handleErrorDetails(EMCompositeModel.java:83)
 at oracle.sysman.emai.model.sca.share.composite.CompositeCoreModel.initialize(CompositeCoreModel.java:122)
 at oracle.sysman.emai.model.sca.composite.core.impl.CompositeModel.initialize(CompositeModel.java:46)
 at oracle.sysman.emai.model.sca.EMEntityModel._initializeEntityData(EMEntityModel.java:28)
 at oracle.sysman.emai.model.sca.common.SCAEntityObject.initializeSCAData(SCAEntityObject.java:124)
 at oracle.sysman.emai.model.sca.composite.core.impl.EMCompositeModel.initializeSCAData(EMCompositeModel.java:31)
 at oracle.sysman.emai.model.sca.SCAObject.initializeData(SCAObject.java:62)
 at oracle.sysman.emSDK.model.EMObject.reset(EMObject.java:216)
 at oracle.sysman.core.model.util.ModelUtil$EMObjectResetter.initOrResetEMObject(ModelUtil.java:328)
 at oracle.sysman.core.model.util.ModelUtil$EMObjectResetter.access$000(ModelUtil.java:280)
 at oracle.sysman.core.model.util.ModelUtil.initializeMBEMObjects(ModelUtil.java:231)
 at oracle.sysman.core.model.util.ModelUtil.initializeAllEMObjects(ModelUtil.java:128)
 at oracle.sysman.core.model.util.ModelUtil.initializeAllEMObjects(ModelUtil.java:101)
 at oracle.sysman.emSDK.view.util.RefreshBean.refreshPageData(RefreshBean.java:91)
 at oracle.sysman.emSDK.view.util.RefreshBean.refreshPage(RefreshBean.java:73)
 at oracle.sysman.emai.view.sca.common.EMNavigationHandler.refreshPage(EMNavigationHandler.java:677)
 at oracle.sysman.emai.view.sca.composite.core.EMCompositeInstancesView.dataChanged(EMCompositeInstancesView.java:119)
 at oracle.sysman.emai.model.sca.share.composite.CompositeInstances._fireDataChangedEvent(CompositeInstances.java:194)
 at oracle.sysman.emai.model.sca.share.composite.CompositeInstances.getDataModel(CompositeInstances.java:158)
 at sun.reflect.GeneratedMethodAccessor971.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at javax.el.BeanELResolver.getValue(BeanELResolver.java:261)
 at com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:173)
 at com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:200)
 at com.sun.el.parser.AstValue.getValue(Unknown Source)
 at com.sun.el.ValueExpressionImpl.getValue(Unknown Source)
 at org.apache.myfaces.trinidad.bean.FacesBeanImpl.getProperty(FacesBeanImpl.java:68)
 at org.apache.myfaces.trinidad.component.FacesBeanWrapper.getProperty(FacesBeanWrapper.java:58)
 at org.apache.myfaces.trinidad.component.UIXTable$RowKeyFacesBeanWrapper.getProperty(UIXTable.java:594)
 at org.apache.myfaces.trinidad.component.UIXComponentBase.getProperty(UIXComponentBase.java:1194)
 at org.apache.myfaces.trinidad.component.UIXIterator.getValue(UIXIterator.java:706)
 at org.apache.myfaces.trinidad.component.UIXCollection._flushCachedModel(UIXCollection.java:1386)
 at org.apache.myfaces.trinidad.component.UIXCollection.encodeBegin(UIXCollection.java:515)
 at javax.faces.component.UIComponent.encodeAll(UIComponent.java:928)
 at javax.faces.component.UIComponent.encodeAll(UIComponent.java:933)
 at org.apache.myfaces.trinidad.render.CoreRenderer.encodeChild(CoreRenderer.java:399)
 at oracle.adf.view.rich.render.RichRenderer.encodeChild(RichRenderer.java:2633)
 at oracle.adfinternal.view.faces.renderkit.rich.PanelStretchLayoutRenderer.encodeCenterFacet(PanelStretchLayoutRenderer.java:769)
 at oracle.adfinternal.view.faces.renderkit.rich.PanelStretchLayoutRenderer._encodeCenterPane(PanelStretchLayoutRenderer.java:1140)
Is there any way to control the reload of processes when server is restarted.

Hi sab2,
There seems to be no reason for error if you have used correct Abstract WSDLs from the MDS in your composite.xml. The best way to check this is to do a Search for hostname in the entire project and ensure that the host-specific URLs exist only in the composite.xml that too in tags starting with *<binding.ws*. Any other WSDL references e.g. in composite namespaces, in Transformation files Source/target namespaces etc. can be replaced with the abstract WSDLs references.
The task is not done yet. You need to further create the configuration plans corresponding to each server environment where your composite would be deployed e.g. DEV_config_plan.xml, PROD_config_plan.xml. These config plans would replace the concrete locations in your composite.xml at the deployment time.
Also have another issue when we move the jars from dev to prod i see the endpoint on MDS is modified
PROD endpoints but after the process is deployed it still has the Endpoint pointing to Dev URL.
I dont see it any where on the MDS and the Composite WSDL.Are you using proper config plans? If not please use one.
The Process we use to migrate the code from DEV to PROD is by exporting jars from the
DEV instance and deploying them on PRD instance, does this have any effect on the endpoint pointing to the DEV URLI'm not sure about this approach as per the recommended approaches. You can however, use the same deployable JARs and deploy from the FMW console by selecting the appropriate configuration plan.
Regards,
Neeraj Sehgal

Problems in my Local BPEL Server--Urgent!!!!

Hi All,
I have deployed a process in my Local BPEL Server which basically picks a fixed length file from the FTP directory using FTP Adapter, transforms it using a Native Format XSD into an XML file and writes it to a local directory using File Adapter.
I have used the Batching Feature in the FTP Adapter configuration to send messages to BPEL in batches of 1.
Now the problem here is the file is not getting picked up and the server is writing massively into the logs and within a matter of 5-10 mins, the size of the domain.log file reaches around 500 MB. The log file says that, the process endlessly creates batch indexes and also fails in Native Format Translation.
Even i undeployed the process, stopped and restarted the Local BPEL Server but it didn't help. I even restarted my machine.
Whenever i start the BPEL Server, it loads all the processes in the Default Domain and then it starts writing into the logs even though the above process is undeployed. Please find below a portion of the logs that the server writes.
2006-11-10 15:33:57,317> <DEBUG> <default.collaxa.cube.activation> <FTP Adapter::Inbound> Invoking inbound translation for : can_testing.txt
<2006-11-10 15:33:57,317> <DEBUG> <default.collaxa.cube.translation> <NXSDTranslatorImpl::log> Starting translateFromNative
<2006-11-10 15:33:57,317> <DEBUG> <default.collaxa.cube.translation> <NXSDTranslatorImpl::log> Done with translateFromNative
<2006-11-10 15:33:57,317> <DEBUG> <default.collaxa.cube.activation> <FTP Adapter::Inbound> Completed inbound translation for : can_testing.txt
<2006-11-10 15:33:57,317> <DEBUG> <default.collaxa.cube.activation> <FTP Adapter::Inbound> isTextFile : true
<2006-11-10 15:33:57,317> <INFO> <default.collaxa.cube.activation> <FTP Adapter::Inbound> Translated inbound batch index "1831" of file {can_testing.txt} sucessfully.
<2006-11-10 15:33:57,317> <DEBUG> <default.collaxa.cube.activation> <FTP Adapter::Inbound> Translator has failed to translate any message from batch number: 1831
<2006-11-10 15:33:57,317> <INFO> <default.collaxa.cube.activation> <FTP Adapter::Inbound> Message not published as translation failed: {
File=/home0303/sjoseph/Outbound_Testing/\can_testing.txt, batchIndex=1831, PublishSize=1
<2006-11-10 15:33:57,317> <DEBUG> <default.collaxa.cube.activation> <FTP Adapter::Inbound> Invoking inbound translation for : can_testing.txt
<2006-11-10 15:33:57,332> <DEBUG> <default.collaxa.cube.translation> <NXSDTranslatorImpl::log> Starting translateFromNative
<2006-11-10 15:33:57,332> <DEBUG> <default.collaxa.cube.translation> <NXSDTranslatorImpl::log> Done with translateFromNative
<2006-11-10 15:33:57,332> <DEBUG> <default.collaxa.cube.activation> <FTP Adapter::Inbound> Completed inbound translation for : can_testing.txt
<2006-11-10 15:33:57,332> <DEBUG> <default.collaxa.cube.activation> <FTP Adapter::Inbound> isTextFile : true
<2006-11-10 15:33:57,332> <INFO> <default.collaxa.cube.activation> <FTP Adapter::Inbound> Translated inbound batch index "1832" of file {can_testing.txt} sucessfully.
<2006-11-10 15:33:57,332> <DEBUG> <default.collaxa.cube.activation> <FTP Adapter::Inbound> Translator has failed to translate any message from batch number: 1832
<2006-11-10 15:33:57,332> <INFO> <default.collaxa.cube.activation> <FTP Adapter::Inbound> Message not published as translation failed: {
File=/home0303/sjoseph/Outbound_Testing/\can_testing.txt, batchIndex=1832, PublishSize=1
<2006-11-10 15:33:57,332> <DEBUG> <default.collaxa.cube.activation> <FTP Adapter::Inbound> Invoking inbound translation for : can_testing.txt
<2006-11-10 15:33:57,332> <DEBUG> <default.collaxa.cube.translation> <NXSDTranslatorImpl::log> Starting translateFromNative
<2006-11-10 15:33:57,332> <DEBUG> <default.collaxa.cube.translation> <NXSDTranslatorImpl::log> Done with translateFromNative
<2006-11-10 15:33:57,332> <DEBUG> <default.collaxa.cube.activation> <FTP Adapter::Inbound> Completed inbound translation for : can_testing.txt
<2006-11-10 15:33:57,332> <DEBUG> <default.collaxa.cube.activation> <FTP Adapter::Inbound> isTextFile : true
<2006-11-10 15:33:57,332> <INFO> <default.collaxa.cube.activation> <FTP Adapter::Inbound> Translated inbound batch index "1833" of file {can_testing.txt} sucessfully.
<2006-11-10 15:33:57,348> <DEBUG> <default.collaxa.cube.activation> <FTP Adapter::Inbound> Translator has failed to translate any message from batch number: 1833
<2006-11-10 15:33:57,348> <INFO> <default.collaxa.cube.activation> <FTP Adapter::Inbound> Message not published as translation failed: {
File=/home0303/sjoseph/Outbound_Testing/\can_testing.txt, batchIndex=1833, PublishSize=1
<2006-11-10 15:33:57,348> <DEBUG> <default.collaxa.cube.activation> <FTP Adapter::Inbound> Invoking inbound translation for : can_testing.txt
<2006-11-10 15:33:57,348> <DEBUG> <default.collaxa.cube.translation> <NXSDTranslatorImpl::log> Starting translateFromNative
<2006-11-10 15:33:57,348> <DEBUG> <default.collaxa.cube.translation> <NXSDTranslatorImpl::log> Done with translateFromNative
<2006-11-10 15:33:57,348> <DEBUG> <default.collaxa.cube.activation> <FTP Adapter::Inbound> Completed inbound translation for : can_testing.txt
<2006-11-10 15:33:57,348> <DEBUG> <default.collaxa.cube.activation> <FTP Adapter::Inbound> isTextFile : true
<2006-11-10 15:33:57,348> <INFO> <default.collaxa.cube.activation> <FTP Adapter::Inbound> Translated inbound batch index "1834" of file {can_testing.txt} sucessfully.
<2006-11-10 15:33:57,348> <DEBUG> <default.collaxa.cube.activation> <FTP Adapter::Inbound> Translator has failed to translate any message from batch number: 1834
<2006-11-10 15:33:57,348> <INFO> <default.collaxa.cube.activation> <FTP Adapter::Inbound> Message not published as translation failed: {
File=/home0303/sjoseph/Outbound_Testing/\can_testing.txt, batchIndex=1834, PublishSize=1
I am clueless about why the BPEL Server is behaving strangely.
If anybody has faced a similar scenario then please let me know ASAP as i am not able to move forward due to this issue.
Thanks In Advance,
Dibya

Hi,
To get around this problem i uninstalled my Oracle BPEL PM and once again re-installed it. Now it is working fine as i took the back up of all the processes.
But is it a limitation in BPEL wherein the number of processes running on the server cannot exceed a certain value.
Please let me know your inputs on it.
Thanks,
Dibya

Custom Xpath testing : avoid server restart (domain reload) ?

Hi,
We are planning to have a centralized BPEL server for several developers. But apparently, when a developer is working on a custom XPath / XQuery functions, we must retart the server in order to test them ... so the other developers cannot work anymore !
Is there any way to avoid the server restart, and only reload a single domain ?
Thank you.

Absolutely, this is what we will do.
However, we still have an organization problem due to Xquery/Xpath functions, because of the following limitations:
- Xpath functions are per domain as Xquery functions are per server. Can't Xquery functions be per domain ?
- There is no versioning of Xpath/Xquery functions. This is quite annoying especially since Oracle BPEL PM can handle versioning of BPEL Processes.
- Same kind of problem with Jdeveloper : when starting Jdev it would be nice to be able to choose what repository of Xquery functions to use.
- Xpath/Xquery functions need to be deployed manually (XML cut/paste + copy of *.class/*.JAR), there is no standard way to identify a Xpath/Xquery function in a Jdeveloper project so that we can deploy them easily.
We have imagined work-arounds, but they are not fully satisfying:
- Handle Xpath/Xquery versioning in the Java code, by having one parameter as the version number => still a problem for code maintenance, and problem because we need more or less to hard code the version number in our BPEL processes.
- Run multiple instances of BPEL PM on the same application server, so that we can isolate Xquery/Xpath function per version => high server load, expensive.
- Write a Jdeveloper launcher to choose the Xquery functions to use.
- Write a custom deployment tool for Xquery/Xpath => could be quite painful.

Server Restart is resetting the Configuration Properties

Hi,
In SOA Suite 11g, We are using BPEL preferences as an option for some of the confgiurable properties.
Whenever changes have to be made, we are using EM console for this. But whenever the SOA server restarted, these properties are resetting to their previous values.
Am i missing any setting to make it persistent? or what would be the issue?
Thanks & Regards
Siva

Hello,
Even I am facing similar issue with SOA Suite 10.1.3.5.
Did you manage to resolve this issue?
Thanks
Sanjay

Error in starting the BPEL Server

Hi All ,
I am new to the BPEL technology and facing problem when I try to start BPEL Server through the "Start BPEL Server" menu.
This is the error that I get after a few minutes :
OraBPEL "default" BPEL domain loaded.
<2007-12-24 18:13:20,317> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://dwus1b018.msc.com:9700
<2007-12-24 18:13:35,868> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://DWUS1B018:9700/orabpel
<2007-12-24 18:13:51,404> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://10.10.10.10:9700/orabpel
<2007-12-24 18:14:07,205> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://dwus1b018.msc.com:9700/orabpel
<2007-12-24 18:14:22,741> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://localhost:9700/orabpel
<2007-12-24 18:14:22,741> <ERROR> <collaxa> <ProcessJob::execute> Attempt (1/15)
... failed to connect ... retrying in 5 seconds ...
<2007-12-24 18:15:01,415> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://dwus1b018.msc.com:9700
<2007-12-24 18:15:57,390> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://10.10.10.10:9700/orabpel
<2007-12-24 18:16:27,133> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://dwus1b018.msc.com:9700/orabpel
<2007-12-24 18:17:01,908> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://localhost:9700/orabpel
Earlier in the begining it reported that the network name and the localhost name are different so I installed a loopback adapter also. Now this problem is no more there but still the server does not boots and when I click on the BPEL Console then I get this message
"Network Error (dns_unresolved_hostname)
Your requested host "dwus1b018.msc.com" could not be resolved by DNS.
For assistance, contact your network support team."
Please guys help me out , I am badly stuck..........

Hi ,
I am badly stuck now . I have the system RAM now 1 GB and when I start the BPEM server then this is the snapshot of netstat command that I get
H:\>netstat
Active Connections
Proto Local Address Foreign Address State
TCP DWUS1B018:2083 dwus1b018.hsc.com:9700 ESTABLISHED
TCP DWUS1B018:9700 dwus1b018.hsc.com:2083 ESTABLISHED
TCP DWUS1B018:1077 DWUS1B018.hsc.com:2084 ESTABLISHED
TCP DWUS1B018:1531 localhost:2075 ESTABLISHED
TCP DWUS1B018:2072 localhost:2073 ESTABLISHED
TCP DWUS1B018:2073 localhost:2072 ESTABLISHED
TCP DWUS1B018:2075 localhost:1531 ESTABLISHED
TCP DWUS1B018:1353 ggns1wfs01.hsc.com:microsoft-ds ESTABLISHED
TCP DWUS1B018:2060 ggnmail01.hsc.com:https CLOSE_WAIT
TCP DWUS1B018:2062 ggns1wis02.hsc.com:1026 TIME_WAIT
TCP DWUS1B018:2077 ggns1wis02.hsc.com:microsoft-ds TIME_WAIT
TCP DWUS1B018:2084 205.177.95.136:ftp ESTABLISHED
TCP DWUS1B018:2086 205.177.95.136:ftp SYN_SENT
*********************But soon there is error in the BPEL prompt :****************
<2007-12-31 12:11:35,304> <INFO> <default.collaxa.cube.engine> <CubeEngine::init>
OraBPEL "default" BPEL domain loaded.
<2007-12-31 12:11:57,317> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://dwus1b018.hsc.com:9700
2007-12-31 12:12:12.933 WARNING OWS-00102 Mapped {http://xmlns.oracle.com/bpel/services/IdentityService}userObject to javax.xml.soap.SO
APElement userObject. Reason for not creating a custom Java type: use of an unimplemented feature.
2007-12-31 12:12:12.963 WARNING OWS-00102 Mapped {http://xmlns.oracle.com/bpel/services/IdentityService}groupObject to javax.xml.soap.S
OAPElement groupObject. Reason for not creating a custom Java type: use of an unimplemented feature.
2007-12-31 12:12:12.963 WARNING OWS-00102 Mapped {http://xmlns.oracle.com/bpel/services/IdentityService}roleObject to javax.xml.soap.SO
APElement roleObject. Reason for not creating a custom Java type: use of an unimplemented feature.
2007-12-31 12:12:12.979 WARNING OWS-00102 Mapped {http://xmlns.oracle.com/bpel/services/IdentityService}userObjects to javax.xml.soap.S
OAPElement userObjects. Reason for not creating a custom Java type: use of an unimplemented feature.
**************AND then the prompt hangs at this place :****************************
0 processes have been loaded for BPEL domain "default".
<2007-12-31 12:12:34,752> <INFO> <collaxa> <ServerManager::loadProcesses> Done loading processes for all domains
<2007-12-31 12:12:38,021> <INFO> <default.collaxa.cube.compiler> validating "C:\product\10.1.3.1\OraBPEL_1\bpel\domains\default\tmp\.bp
el_TaskManager_1.0_63ee83a3d1166eef2f9e56a17e1de896.tmp\TaskManager.bpel" ...
<2007-12-31 12:12:38,099> <INFO> <default.collaxa.cube.compiler> validating "C:\product\10.1.3.1\OraBPEL_1\bpel\domains\default\tmp\.bp
el_TaskActionHandler_1.0_5edb841c8a9e176e18a0fe3ad7114fb7.tmp\TaskActionHandler.bpel" ...
<2007-12-31 12:12:50,635> <INFO> <default.collaxa.cube.engine.deployment> <CubeProcessFactory::generateProcessClass>
Process "TaskManager" (revision "1.0") successfully compiled.
<2007-12-31 12:12:51,283> <INFO> <default.collaxa.cube.engine.deployment> <CubeProcessFactory::generateProcessClass>
Process "TaskActionHandler" (revision "1.0") successfully compiled.
<2007-12-31 12:12:51,314> <INFO> <default.collaxa.cube.engine.deployment> Process "TaskManager" (revision "1.0") successfully loaded.
07/12/31 12:12:51 @#############@##@ CLOB = oracle.lite.poljdbc.CLOB@8433bb
<2007-12-31 12:12:51,776> <INFO> <default.collaxa.cube.engine.deployment> Process "TaskActionHandler" (revision "1.0") successfully loa
ded.
07/12/31 12:12:51 @#############@##@ CLOB = oracle.lite.poljdbc.CLOB@6fdb4b
************************At this if I run the BPEL Prompt then this message I get at the explorer Window :************************
Network Error (dns_unresolved_hostname)
Your requested host "dwus1b018.msc.com" could not be resolved by DNS. For assistance, contact your network support team.
*********************At this moment the Netstat command gives this output *********
H:\>netstat
Active Connections
Proto Local Address Foreign Address State
TCP DWUS1B018:2083 dwus1b018.hsc.com:9700 CLOSE_WAIT
TCP DWUS1B018:2089 dwus1b018.hsc.com:9700 CLOSE_WAIT
TCP DWUS1B018:9700 dwus1b018.hsc.com:2083 FIN_WAIT_2
TCP DWUS1B018:9700 dwus1b018.hsc.com:2089 FIN_WAIT_2
TCP DWUS1B018:1531 localhost:2075 TIME_WAIT
TCP DWUS1B018:1531 localhost:2095 TIME_WAIT
TCP DWUS1B018:2072 localhost:2073 ESTABLISHED
TCP DWUS1B018:2073 localhost:2072 ESTABLISHED
TCP DWUS1B018:2093 localhost:9700 CLOSE_WAIT
TCP DWUS1B018:2096 localhost:1531 TIME_WAIT
TCP DWUS1B018:9700 localhost:2093 FIN_WAIT_2
*********Please can anybody help me figure out this error****************

BPEL Server Restarts intermittently

Similar Messages

Maybe you are looking for