Can an synchronous ESB process initiate an asynchronous BPEL process?

I have a requirement to create a synchronous ESB service that initiates an aysnchronous BPEL process returning a success message to the requesting system.
I can create an esb that receives a paylaod from the requesting system and returns a receipt message, I then created an asynchronous bpel process.
Although I can initiate the asynchronous bpel process from the ESB I cannot work out how to send back the success message? The routing rules do not allow setting of outgoing messages unless you call a synchronous process?

Can you make the BPEL process synchronous. Calling a asynchronous process breaks your synchronous message, because what happens if your asynchronous process takes longer that 1 minute. The synchronous process will timeout but the asynchronous process will complete.
The previous note is correct you can use queues but all this will do is tell you that you posted correctly, you get the same result calling a web service. Asynchronous is fire and forget in a ESB world as it is stateless.
cheers
James

Similar Messages

HowTo get the callback from an asynchronous BPEL process to an ESB?

Hi,
I have deployed an asynchronous BPEL-process which is called from an ESB. So far no problems. But I want to receive the callboack fromt this BPEL process on the ESB, too.
How is this possible?
Note: I have created the BPEL-Process before I created the ESB. So I cannot add the ESB as a partner link in the BPEL Process. Or is this the only way?
Message was edited by:
user636134

Hi,
I have deployed an asynchronous BPEL-process which is called from an ESB. So far no problems. But I want to receive the callboack fromt this BPEL process on the ESB, too.
How is this possible?
Note: I have created the BPEL-Process before I created the ESB. So I cannot add the ESB as a partner link in the BPEL Process. Or is this the only way?
Message was edited by:
user636134

Invoking asynchronous BPEL process from java ui

Hi,
I am invoking an asynchronous BPEL process from java ui.
I read somewhere that i can obtain an instance handler uing the lookupInstance() method of class Locator using the conversation id provided by the class NormalizedMessage.
My code looks like this
// Connect to Oracle BPEL server
Locator locator = new Locator("default","bpel");
IDeliveryService deliveryService = (IDeliveryService)locator.lookupService(IDeliveryService.SERVICE_NAME );
// Construct a normalized message and send to Oracle BPEL Process Manager
NormalizedMessage nm = new NormalizedMessage();
nm.addPart("payload", xml);
// Initiate the BPEL process
deliveryService.post("MyLoanFlow", "initiate", nm);
//Obtain the instance handler
IInstanceHandle handle = locator.lookupInstance(NormalizedMessage.CONVERSATION_ID);
But this is giving the error - can not find any instance with conversation id 'conversationId'.
Also, if i try to obtain a list of instance handles associated with a process , it does not contain the most recently created instance
IBPELProcessHandle ph = locator.lookupProcess("MyLoanFlow");
IInstanceHandle[] iHandler = ph.listInstances();
out.println(iHandler.length + "<br>");
if i invoke the process for the first time the output is 0.
can you please help me. it is urgent.

Hi Sudipto,
Regarding your second question,
deliveryService.post("MyLoanFlow", "initiate", nm);
IBPELProcessHandle ph = locator.lookupProcess("MyLoanFlow");
IInstanceHandle[] iHandler = ph.listInstances();
out.println(iHandler.length + "<br>");
---- returns 0 ---
This is because MyLoanFlow is an asynchronous process in your case. So the control is returned to your java block immediately after the request for a new instance is posted. And your second line of code(querying for the list of instances) is executed even before the instance is created on the server side. You can verify this in two ways:
1. try creating an instance of a synchronous process using IDeliveryService.request - this will always result in the increment since the current thread is blocked till the new instance is created.
2. for your case, you can try
Thread.currentThread().sleep(500); - just allow the server some time for completing the instance before you query it for the list of instances..
and wrt question 1,
//Obtain the instance handler
IInstanceHandle handle = locator.lookupInstance(NormalizedMessage.CONVERSATION_ID);
But this is giving the error - can not find any instance with conversation id 'conversationId'.
For setting the conversationId, you could do so by including the following inside your .bpel file
<bpelx:exec name="test-setConversationId" language="java" version="1.4">
<![CDATA[
setConversationId("conversationId");
]]>
</bpelx:exec>
The code:
IInstanceHandle ins = locator.lookupInstanceByConversationId(NormalizedMessage.CONVERSATION_ID);
should fetch you the required instance in this case.
HTH,
Anuj

How to get response from an asynchronous BPEL process in Java

I'm experimenting with BPEL and doesn't seem to be able to get response from an asynchronous BPEL process. Here's the deal:
I have a BPEL process that takes a string as input, and gives another string as output. This is a asyncronous process.
I want to initiate this BPEL process as a web service so I generate a Webservice Proxy in JDeveloper 10g (10.1.3.0.4). The function to call the process is now called "initiate" and takes three arguments: the input string, a "org.xmlsoap.schemas.ws._2003._03.addressing.EndpointReferenceType replyTo" and a
"org.xmlsoap.schemas.ws._2003._03.addressing.AttributedURI messageID".
HTTP-Analyzer shows that invoking the BPEL process with initiate("somestring", null, null) results in sending a SOAP message to the BPEL process, which returns a "202 Accepted". How do I get the response from the process? My intuition tells me that I have to use that second argument, that EnpointReferenceType thing. How do I use that?
Another question: If a asynchronous BPEL process does not exists (so the endpoint does not exist) the Java proxy does not throw an error when runned. It does not even sends a message. It exits with status 0! (This happens for example when deploying a new version of a process and when the "old" version is undeployed). Calling a non-existing synchronous BPEL process, the Java proxy DOES throw an error.

Clemens,
That all sounds logical. But somehow it is still a mystery for me ... Somehow I don't see what should be done.
To call the async BPEL process I have the following procedure:
initiate(String input, org.xmlsoap.schemas.ws._2003._03.addressing.EndpointReferenceType replyTo, org.xmlsoap.schemas.ws._2003._03.addressing.AttributedURI messageID)
The first argument is the input for my BPEL process. The second is the address to a webservice that should handle the callback, right? The third is a messageID (makes sense, but why of the type AttributedURI?).
Here lies my problem. It is not clear to me how these EndpointReferenceType & AttributedURI work. I can't find anything on the net about it. The AXIS examples as where mentioned earlier use other types (namely the "org.xmlsoap.schemas.ws.addressing.MessageID" and "org.xmlsoap.schemas.ws.addressing.ReplyTo") which are completely different.
What I did so far:
- I created an webservice proxy that listens on the onResult endpoint of the BPEL process.
- I created an webservice proxy that calls the BPEL process through the initiate procedure, but it is not completely clear to me how to construct the EndPointreferenceType replyTo, and the MessageID. I did something like this:
EndpointReferenceType replyTo = new EndpointReferenceType();
// callback service running on local machine
// This URI class is the java.net's version
URI replyToURI = new URI("http://vaccinatie:8988/syncro-callback-context-root/stringconcatCallbackBindingPort");
// This AttributedURI is the org.xmlsoap.schemas.ws._2003._03.addressing's version
AttributedURI address = new AttributedURI();
// the only public methos that made sense to me:
address.set_value(replyToURI);
replyTo.setAddress(address);
// call the BPEL process
myPort.initiate("test123", replyTo, address);
But the above doesn't work (largely because I don't know what I'm doing here prob.:-) ) It does send the "test123" message, and the BPEL process does process it, but I don't seem to get the callback right.
I hope this makes my problems somewhat clearer. I hope someone can help me, because I'm just a beginner in this whole "web service area" and seems to do something terribly wrong here, because it should be very simple. Thx.

Error while invoking an asynchronous BPEL process

Hi ,
I am trying to call an asynchronous BPEL process through java client.
Following is the code which I got from SOA bpel samples present in the following location
<SOA_HOME>\bpel\samples\tutorials\102.InvokingProcesses\rmi\com\otn\samples\async
The code fails while registering the callback
String convId = GUIDGenerator.generateGUID();
nm.setProperty(NormalizedMessage.CONVERSATION_ID, convId);
deliveryService.post("HelloWorld", "initiate", nm);
// register the callback
watchdog.registerAsyncCallback(convId, testAsyncHandler,
locator.getDomainAuth());
The error says java.lang.NoClassDefFoundError: org/collaxa/thirdparty/json/JSONString
I tried to search for this in google. But it seems noone has got this error or maybe noone has used this at all.
Maybe I am missing some jar file, but I am unable locate that.
Can someone help me in this please.

Hi,
These sort of class not found errors come when you are running from a client which does not have all the jar files requried to invoke BPEL using the client API.
org/collaxa/thirdparty/json/JSONString is orabpel-thirdparty.jar.
The complete list of Jar files you would need in the classpath are:
ejb.jar ($ORACLE_HOME/home/lib)
oc4j-internal.jar ($ORACLE_HOME/home/lib)
optic.jar ($ORACLE_HOME/opmn/lib)
orabpel-common.jar ($ORACLE_HOME/bpel/lib)
orabpel-thirdparty.jar ($ORACLE_HOME/bpel/lib)
orabpel.jar ($ORACLE_HOME/bpel/lib)
Hope this helps,
Regards,
Shanmu.
http://www.prshanmu.com/articles/

ESB errors not propagating to BPEL process

I am working in SOA Suite 10.1.3.3. I have an asynchronous BPEL process that is orchestrating a number of ESB services, most of which perform database operations. Occasionally an attempt is made to insert a record into a table which results in an error (e.g., null value inserted into a non-null field, record already exists, non-existent record in parent table upon which current table depends, etc.). This correctly results in an error in the ESB service that shows up in the ESB Control console.
The problem is that the error is NOT propagated upward to the invoking BPEL process (which contains all manner of fault catching branches to process the error, log it, send email notifications, and perform other database operations dependent upon the success or failure of the ESB operations). The BPEL process is therefore left "hanging" and never appears in the BPEL Control console as an instance. It shows up in the Manual Recovery queue as an essentially unrecoverable process.
I am assuming that this change in behavior (such errors formerly propagated to the calling BPEL) is a direct result of the new Fault Handling Framework. My question is: what do I have to do in order to restore the original behavior of the system (ESB service encounters an error and propagates the fault to the async BPEL process, which catches it and does whatever it needs to do to fulfill the requirements of the overall system)? Is this something that can be handled by changes to the BPEL/ESB system configuration, the BPEL process definition, the ESB service definitions, or some combination thereof?
Thanks for your time.
Paul Camann

Hello. We applied 10.1.3.3.1 MLR14 in late October 2008.
We are seeing large numbers of errors like this in the ESB log ($ORACLE_HOME/j2ee/oc4j_soa/log/oc4j_soa_default_group_1/oc4j/log.xml):
<MESSAGE>
<HEADER>
<TSTZ_ORIGINATING>2009-01-26T13:11:15.497-05:00</TSTZ_ORIGINATING>
<COMPONENT_ID>tip</COMPONENT_ID>
<MSG_TYPE TYPE="ERROR"></MSG_TYPE>
<MSG_LEVEL>1</MSG_LEVEL>
<HOST_ID>biwsvlbat027.gdbiw.com</HOST_ID>
<HOST_NWADDR>1.2.3.4</HOST_NWADDR>
<MODULE_ID>esb.server.service.impl.soap</MODULE_ID>
<THREAD_ID>98</THREAD_ID>
<USER_ID>oracle</USER_ID>
<SUPPL_ATTRS>
<ATTR NAME="J2EE_MODULE.name">provider-war</ATTR>
<ATTR NAME="J2EE_APP.name">esb-rt</ATTR>
<ATTR
NAME="WEBSERVICE_PORT.name">__soap_Router_ODS_STAGE_Insert_ODS_STAGE_I_PortType</ATTR>
<ATTR NAME="WEBSERVICE.name">ESB_Router_ODS_STAGE_Insert_Service</ATTR>
</SUPPL_ATTRS>
</HEADER>
<CORRELATION_DATA>
<EXEC_CONTEXT_ID><UNIQUE_ID>1232993475:1.2.3.4:7097:0:307</UNIQUE_ID><SEQ>5</SEQ></EXEC_CONT
EXT_ID>
</CORRELATION_DATA>
<PAYLOAD>
<MSG_TEXT>Exception while print response</MSG_TEXT>
<SUPPL_DETAIL><![CDATA[java.lang.NullPointerException
at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.processMessage
(EventOracleSoapProvider.java:215)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing
(ProviderProcessor.java:956)
at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation
(WebServiceProcessor.java:349)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing
(ProviderProcessor.java:466)
at oracle.j2ee.ws.server.WebServiceProcessor.processRequest
(WebServiceProcessor.java:114)
at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96)
at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:177)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ServletRequestDispatcher.invoke
(ServletRequestDispatcher.java:713)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal
(ServletRequestDispatcher.java:370)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest
(HttpRequestHandler.java:871)
at com.evermind.server.http.HttpRequestHandler.processRequest
(HttpRequestHandler.java:453)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:302)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:190)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run
(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run
(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
]]></SUPPL_DETAIL>
</PAYLOAD>
</MESSAGE>
which is possibly the message that would come back from ESB to BPEL failing?
Thank you.

Implement callback for an asynchronous BPEL process through Java

Hi ,
I am trying to implement a callback functionality for an asynchronous BPEL process through java.
I found the code in the samples folder of SOA suite installation folder .
<SOA_HOME>\bpel\samples\tutorials\102.InvokingProcesses\rmi\com\otn\samples\async.
There is an AsyncInstanceWatchdog object which registers a callback object(in this case an object of AsyncCallbackImpl class) for a specific CONVERSATION_ID.
String convId = GUIDGenerator.generateGUID();
nm.setProperty(NormalizedMessage.CONVERSATION_ID, convId);
deliveryService.post(proc_name, "initiate", nm);
// register the callback
watchdog.registerAsyncCallback(convId, testAsyncHandler,
locator.getDomainAuth());
// start it
watchdog.start();
There is no problem till the last line. But once the BPEL process returns the control( does a callback), it throws the following error.
May 25, 2010 3:36:06 PM oracle.j2ee.rmi.RMIMessages EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER
WARNING: Exception returned by remote server: {0}
ORABPEL-02118
Variant not found.
The variant "output" has not been declared in the current scope. All variants must be declared in the scope before being accessed.
Please check that the variant "output" is properly declared; otherwise there may be a misspelling in the name of the variant.
at com.collaxa.cube.engine.core.Scope.getVariantRV(Scope.java:535)
at com.collaxa.cube.engine.CubeEngine.getFieldValue(CubeEngine.java:2668)
For your reference the variable output is declared in the definition of AsyncCallbackImpl (which implements the IAsyncInstanceCallback interface).
There are 2 methods defined in the AsyncCallbackImpl class.
public void onResult(Map pResultMessage) {
System.out.println("called back! ");
Iterator iTest = pResultMessage.keySet().iterator();
while (iTest.hasNext()) {
String key = (String)iTest.next();
System.out.println(XMLHelper.elementToString((Element)pResultMessage.get(key)));
public String getVariableName() {
return "output";
The variable name is same given in the sample code. And the BPEL process returns variable named output. So the name should not be a problem.
Is it because of the scope of the variable.. If so, how do I change it.
Any help would be appreciated.
Edited by: saptarishi on May 25, 2010 4:24 PM
Edited by: saptarishi on May 26, 2010 4:45 PM

Solved it by some googling .... :)
Here is the link:-
[http://abhishek-soablog.blogspot.com/2008/09/orabpel-02118.html]
or
[http://beautifulwaste.blogspot.com/2008/04/calling-asynchronous-bpel-process.html]
Both gives the same solution..
In pre 10.1.3.3 release the default behaviour were to keep global variable information along with the instance information for completed BPEL processes.
In 10.1.3.3 or later, this behaviour changed for performance reasons so that the default behaviour is now, not to keep any global variables for a BPEL process once the BPEL process has completed.
You can configure this behaviour on a process level basis by using the parameter keepGlobalVariables in the bpel.xml file for the specific process:
<BPELSuitcase>
<BPELProcess src=".........." id="...........">
<configurations>
<property name="keepGlobalVariables">true</property>
</configurations>
</BPELProcess>
</BPELSuitcase>
Thanks
saptarishi

Throwing a fault from an asynchronous bpel process

Hi,
can anyone please let me know how i can throw a fault to the calling client from an asynchronous bpel process?
(synchronous bpel uses the fault of the reply activity to do the same - i want a similar thing in a callback-invoke of an asynchronous process or any other way to do it if at all)
please let me know if it is possible becoz it was a requirement put forward by a customer and i just want to develop a proof of concept to the same.
regards,
pavan.

Hi,
I'm using BPEL process manager for calling a asynchronous web service,I can invoke the service from BPEL and the service is invoked correctly,but when I view the business process flow in BPEL Console my process is stopped at receive state and doesn't pass it.
Could anybody tell me if any thing should be set to receive a callback from an asynchronous web service to BPEL process?
Is it true that BPEL process receives a callback automatically (using a callback operation which I defined in my web service WSDL) on the same port type that normally receives the requested information, with an invoke activity?
So what could be wrong with my process or invoked web service that the BPEL process doesn't get any reply from my web service and remains in receive activity?
Thnx in advance,
Nasim

DBAdapter polling for new or changed records not issuing callback within an asynchronous BPEL process?

Hi,
I have a requirement to poll a database table withing an asynchronous process. The reason I want to use a receive within an asynchronous BPEL is because the process needs to be notified many times thru polling. So might need many receive activities.
I have developed a process as described below :-
1. Created an asynchronous process.
2. Created a Database adapter for polling a table. Logical delete strategy is being used.
3. Have put a receive activity from the DB Adapter created.
4. Created a correlation set consisting of a single property(String)
5. Created a property alias to refer to
a. the input string of the asynchronous process. (unique for this process)
b. the input from the database adapter (unique for this process)
I initiate this process from the console. Then I inserted a record the table with proper inputs.
But the BPEL waits indefinitely at the receive activity.
When I try to poll the table from an empty BPEL process, it works perfectly fine.
Regards
Kabir

Hi Kabir,
Please refer the following sample for your usecase.
Though Please be aware that one instance of BPEL process will correlate with only one message if you have one receive activity. Not all the messages tht DBAdapter polls.
bpel-305-InboundCorrelationShows how to perform message correlation within BPEL
Also Refer the following in Developer guide.
http://docs.oracle.com/cd/E28280_01/dev.1111/e10224/bp_correlate.htm#CHDFHAAE
If you want to keep polling and receiving the messages in the same BPEL process you might have to put the receive activity in a while loop construct. But as a design this is not a good design.
Can you elaborate your requirement to understand better and suggest better solution.

A Synchronous answer from Asynchronous BPEL (How to?)

Good Afternoon!
A have an asynchronous BPEL with an exposed webservice.
I need BPEL get back a some kind of information at the moment he was called (e.g. a Conversation ID). And then continue his own asynchronous process.
Is it possible?
Tank You!

I have tried:
A Reply. i put a reply exactly after receive input - nothing. BPEL exposed service is defined as asynchronous, so it has not any definition in wsdl for reply answer.
A Callback. i put a callback and return back an assigned Coversation ID. It works good. But it is another callback operation.
May be there is a possibility to return back not in some next activity but exactly in BPEL start moment?
I will describe why i think its possible.
When you call any async webservice you can receive an exception in this moment (if webservice doesnt exist) or you can also receive a "nothing" (if webservice exist and it started to work). In any way you receive in back ground some kind of system information from Application Server that tells you - are you successfull in webservice calling or not.
And this is not a callback. Its something else. Its some kind of server synchronous answer.
And I am thinking, is it possible to use this system answer to send back some technical info about BPEL?

Asynchronous bpel proces seems to reply synchronous

I have made a bpel proces which is triggered by a synchronous webservice. The process is triggered, I fill the reponse and reply to the service to let it know we received the message. After this I process the message which takes some time. The problem is that the reponse is only received when the proces is completely done! When I look at the flow in debug it returns the reply but in SoapUI it times out because the rest of the process takes quite long. Why don't I receive the reponse back immediately when I reply?
Best regards!

4.How to deploy a project using a script?
http://jianmingli.com/wp/?p=2584
1.When we can create synchronous bpel process
Synchronus process need to create in case if you are expecting reply Immediately.
ex. this is usefull in case if you are using Database adapter as partner link in BPEL process. Because database Adapter operation used to give reply immediately.
2. When we can create asynchronous bpel process
Asynchronus process need to create in case if you when reply will come is not having time limit.
Example:- Suppose if you have one loan process in which we are invoking some of the webservices(ex United Star Loan, HDFC loan) which will send the intrest charges in reply but in this case reply can come at any time. Till that time BPEL process need to wait for indefinite amount of time. If Sync BPEL process will be used in the above case then the BPEL process will time out and that will come under faulted state.
3.When we can create empty bpel process
Define Service Later: Select to create an empty BPEL process service component with no activities.

Synchronous/Asynchronous BPEL Correlation

Is this possible?
When a message has to correlate with a BPEL process in a clustered environment of 2 nodes where both of them are active/active and a process instance that is capable of correlating with the message is waiting on one node, where as the message gets routed to the other node and a duplicate copy of the process starts on the other node joins and correlates with the message, and completes the processing on the other node. where as process instance on the first node times out after syncMaxWaitTime.
Server: 10.1.3.4 OC4J

4.How to deploy a project using a script?
http://jianmingli.com/wp/?p=2584
1.When we can create synchronous bpel process
Synchronus process need to create in case if you are expecting reply Immediately.
ex. this is usefull in case if you are using Database adapter as partner link in BPEL process. Because database Adapter operation used to give reply immediately.
2. When we can create asynchronous bpel process
Asynchronus process need to create in case if you when reply will come is not having time limit.
Example:- Suppose if you have one loan process in which we are invoking some of the webservices(ex United Star Loan, HDFC loan) which will send the intrest charges in reply but in this case reply can come at any time. Till that time BPEL process need to wait for indefinite amount of time. If Sync BPEL process will be used in the above case then the BPEL process will time out and that will come under faulted state.
3.When we can create empty bpel process
Define Service Later: Select to create an empty BPEL process service component with no activities.

Error while invoking ESB process from a BPEL process

Hi all
We have a requirement to call an ESB process from a BPEL process. We are using an adapter wth the ESB's WSDL url. After deploying the BPEL process, the registered ESB is getting called for most values while suddenly some values return the followign error
*"exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Connection reset"*
The catch here is, if we re-run the process with the same values again, the ESB is called successfully! How is it possible for a process to error out and run normally for the same inputs ?
What could be the possible fix for this? I am thankful for any inputs on this.
Vijay

Hi Vijay,
This is a bug and you can refer the metalink note:
"Applying Patch 7445876 Results in Error "java.lang.NullPointerException". [ID 942575.1]" for reference.
Also you can refer the following link:
"http://puchaanirudh.blogspot.com/2008/12/exception-on-jaxrpc-invoke-http.html" also.
Thanks,
Vishwanath.

Slave instance can not synchronized with the master for a long time

Hi,
Slave instance can not synchronized with the master for a long time, and the gap of LSNs between slave and master are more and more larger. The transfer bytes per second between master and slave is 118MB/s , upper limit to the ethernet card. Why???
ENVIRONMENT:
1. A network program which we called mcdb is based on BDB 4.8.30. It is used to accept get/set requests and then query data from bdb or save data to bdb.
2. mcdb implements replication with bdb replication manager api. The default start replication policy is DB_REP_ELECTION, rep ack policy is DB_REPMGR_ACKS_ONE_PEER and rep priority is 100.
3. The bdb data files, bdb log files, region files and rep files are all in the same home directory.
4. There are two instances of the mcdb are separately on two standalone servers which has no other programs. These two instances are in one replication group which can elect a master automatically.
5. The master instance is online, which has lots of requests (get, set, delete).
ACTIONS:
1. Start two mcdb instances on two servers and the two instance make a replication group. Slave has already synchronized with the master.
2. Stop the slave for a long time (more than 20 hours).
3. Start the slave instance to synchronize data with master.
RESULT:
1. the gap of LSNs between slave and master are more and more larger.
2. db_stat of master and slave:
master db_stat:
467170     Number of PERM messages not acknowledged
9245     Number of messages queued due to network delay
172415     Number of messages discarded due to queue length
25880     Number of existing connections dropped
3407     Number of failed new connection attempts
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
DB_REPMGR site information:
10.67.15.146 (eid: 0, port: 30011)
Environment configured as a replication master
331726/3574994     Next LSN to be used
0/0     Not waiting for any missed log records
328872/466092     Maximum permanent LSN
0     Next page number expected
0     Not waiting for any missed pages
0     Number of duplicate master conditions originally detected at this site
2147M     Current environment ID (2147483647)
100     Current environment priority
49     Current generation number
50     Election generation number for the current or next election
2323     Number of duplicate log records received
0     Number of log records currently queued
6768     Maximum number of log records ever queued at once
55284     Total number of log records queued
120M     Number of log records received and appended to the log (120475988)
111     Number of log records missed and requested
2147M     Current master ID (2147483647)
2     Number of times the master has changed
0     Number of messages received with a bad generation number
8505306     Number of messages received and processed
12     Number of messages ignored due to pending recovery
471869     Number of failed message sends
12M     Number of messages sent (12959945)
0     Number of new site messages received
1     Number of environments believed to be in the replication group
990543     Transmission limited
0     Number of outdated conditions detected
0     Number of duplicate page records received
0     Number of page records received and added to databases
0     Number of page records missed and requested
Startup complete
6244678     Number of transactions applied
0     Number of startsync messages delayed
1     Number of elections held
1     Number of elections won
No election in progress
0.057097     Duration of last election (seconds)
8944103     Number of bulk buffer sends triggered by full buffer
0     Number of single records exceeding bulk buffer size
5273M     Number of records added to a bulk buffer (5273592170)
10M     Number of bulk buffers sent (10490865)
0     Number of re-request messages received
0     Number of request messages this client failed to process
0     Number of request messages received by this client
slave db_stat:
0     Number of PERM messages not acknowledged
0     Number of messages queued due to network delay
0     Number of messages discarded due to queue length
1454     Number of existing connections dropped
0     Number of failed new connection attempts
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
DB_REPMGR site information:
10.67.15.147 (eid: 0, port: 30011)
Environment configured as a replication client
329544/2916048     Next LSN expected
330433/2013808     LSN of first log record we have after missed log records
329543/5500501     Maximum permanent LSN
0     Next page number expected
0     Not waiting for any missed pages
0     Number of duplicate master conditions originally detected at this site
2147M     Current environment ID (2147483647)
100     Current environment priority
49     Current generation number
50     Election generation number for the current or next election
5256M     Number of duplicate log records received (5256599432)
3925284     Number of log records currently queued
3925285     Maximum number of log records ever queued at once
4880561     Total number of log records queued
3578038     Number of log records received and appended to the log
1912297     Number of log records missed and requested
0     Current master ID
1     Number of times the master has changed
0     Number of messages received with a bad generation number
12M     Number of messages received and processed (12980442)
2     Number of messages ignored due to pending recovery
0     Number of failed message sends
1912307     Number of messages sent
0     Number of new site messages received
0     Number of environments believed to be in the replication group
0     Transmission limited
0     Number of outdated conditions detected
0     Number of duplicate page records received
0     Number of page records received and added to databases
0     Number of page records missed and requested
Startup incomplete
110568     Number of transactions applied
80     Number of startsync messages delayed
0     Number of elections held
0     Number of elections won
No election in progress
0     Number of bulk buffer sends triggered by full buffer
0     Number of single records exceeding bulk buffer size
0     Number of records added to a bulk buffer
0     Number of bulk buffers sent
0     Number of re-request messages received
0     Number of request messages this client failed to process
0     Number of request messages received by this client
Edited by: 899585 on 2013-1-4 下午10:54
Edited by: 899585 on 2013-1-4 下午10:55

Hi,
Unfortunately, this issue is beyond the level of what is supported over the forum. Performance related issues are extremely complex and require an in-depth understanding of your environment and dedicated support. In a generic sense, you can look at this as a basic queueing problem. You have a server that went down and work is still coming in. When the server gets started it is possible that it may never catch up depending on new work coming in and the rate at processing the old work.
So what would you do in this case --- one thing would be to reduce the new work coming in. In HA terms this would be slowing the master down and you can increase DB_REP_ACK_TIMEOUT for this. Another thing you could do is add fresh servers to help reduce the workload. In HA terms, this would be the equivalent of restarting the client and give it a fresh look at everything. Another thing you could do is replan the system and load balance. In HA terms, it would mean something like take a hot backup of the master and reinit a client from scratch.
If you are interested in getting a dedicated support person working on this concern, please let me know and we can move forward down that path. Just respond to the thread with your email address and I will get in contact with you so we can pursue that approach.
thanks
mike

Unable to get callback from Asynchronous BPEL process to work (AXIS Client)

Hello,
I am calling an Asynchronous BPEL process from an AXIS client, and I am unable to get the callback functionality to work. The AXIS client code has been generated from WSDL2Java using the BPEL process' WSDL file.
I CAN insert an invoke node in the BPEL process and invoke my Callback web service using that, but obviously that means the BPEL process is limited to only responding to one pre-determined client, which won't work.
My questions:
- How does the BPEL process know what endpoint to use to make the callback?
- Do I need to modify the generated code to create a SOAP Envelope and invoke the process with the envelope, intead of the invokeOneWay call?
- If I do need to create a SOAP Envelope with a replyto element, what is the structure of a typical BPEL envelope? Is there an example somewhere?
I have looked at the examples in the interop directory, specifically the AXIS calling Async BPEL, but I would like to try to keep the client code as independent as possible (I don't really want to have a dependency on the OTN library).
Any help would be greatly appreciated!!
Thank you.
-Ryan

Please have a look at the Binding in the WSDL. Axis must provide the ReplyTo and
MessageId information there. As far as I see, this must be done by an Axis-Handler,
because the Binding-Part in not generated by WSDL2Java.
I was able to generate the JavaClasses by using the "WSDL2Java -a" option, but
I still do not see how to use them in a handler and how to register the handler.
Maybe someone can give me a hint.

Can an synchronous ESB process initiate an asynchronous BPEL process?

Similar Messages

Maybe you are looking for