Process instances do not show in BPEL Console

Hi all,
I have a BPEL, which reads a files from a particular folder if any, Process records in that file and then stores it in database.
I am facing a problem, my records gets processed, this BPEL works fine, as i can see the output in database, however associated instances are not shown in the BPEL Console. But if i restart the process (i.e. Switch OFF the process and Again Switch ON) it shows me all the previous instances and also the current instances. But sometime again this problem occurs.
Has anyone faced the same issue? Please let me know in case anyone has solution.
Thanks in advance.

[http://download.oracle.com/technology/tech/soa/soa_best_practices_1013x_drop3.pdf|http://download.oracle.com/technology/tech/soa/soa_best_practices_1013x_drop3.pdf] I found below in SOA best practices guide:
Why Does the Instance of an Invoked Process Not Display in Oracle BPEL Control?
If the process invoked is asynchronous, the message headers and payload are stored in
the invoke_message table. The invocation message is then processed by a
background thread to create an asynchronous BPEL process instance. If an error is
encountered while processing the invocation message, the transaction is rolled back
and the invoke message remains in its unhandled state in the invoke_message table.
See "How Does an Invoke Message and Activity Display in the Manual Recovery
Page?" on page 1-18 for more details on this scenario.
If the process invoked is synchronous, the cause for the missing instance is likely a
transaction rollback. The reasons for a transaction rollback are as follows:
■ Third party manipulation of the JTA transaction. As described in "How Do I Force
a Rollback in a BPEL Flow?" on page 1-5, a failed database adapter invocation can
cause the TopLink layer to mark the JTA transaction for rollback. Because Oracle
BPEL Server relies on the JTA transaction for persistence (not just as a signaling
mechanism between transaction-aware modules), any changes to the status of the
transaction impact Oracle BPEL Server’s ability to dehydrate the instance.
■ Transaction timeout. The synchronous process may be invoking one or more
backend synchronous services; the total time of all the backend calls may exceed
the timeout value for the transaction. See "How Do I Modify Transaction Timeout
Settings for Oracle BPEL Server?" on page 1-9 for details on how to increase the
transaction timeout value.
■ Failure to dehydrate the synchronous instance to the database. If the
completionPersistPolicy is set to on, the instance attempts to save itself
before returning to the caller. Typically, errors are encountered during this step if
the database connection has been severed or the tablespace is full. Some customers
Transactions
Oracle BPEL Process Manager 1-9
have encountered problems with saving the audit trail of the instance. For
example, there are problems with JDBC batching in 10.1.3.1.0 that the audit trail
persistence code uses. When a synchronous invocation does not result in an
instance visible from Oracle BPEL Control (assuming that
completionPersistPolicy is set to a value of on, deferred, or faulted),
use the following steps to find the underlying error:
– Enable all loggers to debug mode.
– Resubmit the invocation message.
– Check the Oracle Process Manager and Notification Server (OPMN) or
command-line log for the underlying exception stack trace.
Please refer to link below:
http://download.oracle.com/technology/tech/soa/soa_best_practices_1013x_drop3.pdf

Similar Messages

Process Instances do not appear in BPEl console

HI everybody
I have a Asyn BPEL worflow which consists of a receive business event lisening to a change in database which in turn initiates a BPEL flow.The problem i am facing is that when i do make a change in database everything works fine but i am not able to see the process instances generated , in BPEL console instantly. I have to restart the BPEL server one or more time in order to view them on the console. have any body faced a similar prob ??

SOA version ? Able to see the processes in the manual recovery section ? Processes disappear or insatnces ?
Errors in the logs ? What happens if you randomly click on various tabs of the console - still unable to see the previous instances ?

BPEL Processes are not showing in BPEL Console after OPMN restart

Hi All,
BPEL Processes are not showing in BPEL Console after OPMN restart. It was showing earlier before restart.
Can some one help on this?
Thanks

Vikky,
Are you using 10g?
If BPELConsole is up but you don't see any process, you can go to the log files and see what is the problem.
It might relates to permissions, or DB issues etc....
Arik

Deployed processes not showing in BPEL Console

I am working on a processes that uses AQ to interface with a Oracle back end application.
It seemed to work fine, but from a certain moment on it didn't pick up any messages that were qeueued. Except for the first instance of the process. Though the monitor showed it waiting for the response, the process had actually received the response and had proceeded with the next step (in which a file was written to a directory, as I could see). Then it stopped. All subsequent processes stopped after queueing an input message.
After stopping and starting the BPEL Process Manager and OC4J container things went from bad to worse. Now none of the deployed processes are visible in the monitor. However, if I look at a previous instance of a process, it does show up on the dashboard.
I've had a look at the application log of the orabpel OC4J application and it shows a lot of errors (of the same sort) since BEPL Process Manager was stopped. Restarting the Application Server didn't help.
This is the error I'm getting:
05/12/19 14:55:19 MessageDrivenHome::run: dequeue FAILED; attempting to re-acquire JMS session for blocking receive
05/12/19 14:55:19 MessageDrivenHome::run: retry_cnt=0 this.dequeue_retry_cnt=0 this.dequeue_retry_interval=60
Does anybody have a clue about what is wrong?

Some more info on the problem:
I took one of the application servers out of the cluster and began working on it in a standalone state.
The Setup, OracleAS Middle Tier with BPEL:
1. The Application server sits on an internal network that has access to the outside world but restricted incoming access.
2. There is an Apache server running mod_proxy that acts as a reverse proxy for all requests to http://workflow/. http://workflow/ connects the requests to http://servername:7797/, where BPEL is running.
This works to get connectivity to the Application Server. We want the WSDL Location to start with http://workflow/ insead of http://servername:7797/ so we can eventually use a clustered load balancing environment.
I found out that the processes are not showing up in the BPEL Dashboard when I change, soapCallbackUrl and soapServerUrl to http://workflow/. They will not show up until I actually navigate to the WSDL file using teh http://workflow beginning. After which they show up in the BPEL Dashboard. However, on a OC4J_BPEL restart they all disappear again.
Everything works if I use the http://servername:7797/ beginning for WSDLs, but this will not work for the overall implementation.
How can I change soapCallbackUrl and soapServerUrl to http://workflow and still use the BPEL Dashboard?

Instance not found in BPEL Console until Process finished

I have two services on the server, where one (asynchronous) service is calling another (synchronous) service multiple times.
WHen creating an instance in the BPEL Console, this instance is nowhere to be found. When trying to see the flow, an error message occurs in the console and on the BPEL server window:
ORABPEL-02152
Instanz in Datenquelle nicht gefunden.
Die Prozessdomõne konnte die Instanz mit dem Schl³ssel "226865cd4e81777c:1a001ff
:10c814abd65:-7f83" nicht aus der Datenquelle abrufen.
Stellen Sie sicher, dass sich der Schl³ssel "226865cd4e81777c:1a001ff:10c814abd6
5:-7f83" auf eine g³ltige Instanz bezieht, die gestartet und nicht aus der Proze
ssdomõne entfernt wurde.
at com.collaxa.cube.engine.data.AdminFinder.__lookupInstanceMetaData(AdminFinder.java:314)
at com.collaxa.cube.engine.data.AdminFinder.__lookupInstanceMetaData(AdminFinder.java:262)
at com.collaxa.cube.engine.data.AdminFinder.lookupInstanceByConversationId(AdminFinder.java:235)
at com.collaxa.cube.ejb.impl.FinderBean.lookupInstanceByConversationId(FinderBean.java:177)
at IFinderBean_StatelessSessionBeanWrapper42.lookupInstanceByConversationId(IFinderBean_StatelessSessionBeanWrapper42.java:669)
at com.oracle.bpel.client.Locator.lookupInstance(Locator.java:420)
at displayInstance.jspService(_displayInstance.java:111)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:350)
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:824)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:222)
at com.collaxa.cube.fe.DomainFilter.doFilter(DomainFilter.java:152)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:663)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:285)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:126)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:534)
Interestingly, the instances of the (synchronous) service, which are called from the mysterious service, are visible all the time and the flow can be viewed while these services are processed.
Does anybody have an idea why this is happening?
Thank you,
Nina

Hi,
I don't understand this behaviour in detail, by now. Could you please state if this is correct?
1. I call an async bpel process A.
2. The message is put in the delivery queue.
3. My client is free again, not blocking.
4. Process A does not show up in Console by now. (If I would call checkpoint(), it would do).
5. A worker takes the message and instantiates the Process A.
6. Process A instance is running now, calling some sync processes.
7. NO dehydration so far.
8. Process A does not show up in Console by now. The called subprocess (sync) do show up, if they are completed.
9. Loop to 6, until Process A ends and makes callback to client.
10. After sending callback, Process A shows up in Console.
11. Now I can monitor, what HAS happened.
I understand, that you can't commit your process data, until a regular dehydration point is reached.
But consequence: I can't even SEE that there exists a process instance from A, until it worked through all the steps above. I just see a swarm of sub processes without an existing parent.
That's the behaviour, you call "intended"?
Workaround would be to do dehydration after each bpel invoke activity. Do you see a problem in doing this?
Thanks in advance!
Torsten

ABAP Work process table is not showing in MMC

HI ,
My ABAP ystem is working fine but in MMC ABAP work process table is not showing.
After rebooting the server in MMC console SID is not appaeraing i have to add the entries eevry time after rebooting.
Please help me any one.
Thanks
Nekkalapu

Hi,
I have checked the note :
Use the SAP tool NTSCMGR. EXE to call up the status of an SAP service and to uninstall or install SAP services. Note with service new installations that, before starting, you must assign a corresponding SAP user for the service with whom the service is started ('Control Panel -> Services -> Startup -> Log on As This Account -> <SID>ADM or SAPService<SID>').
a) Status query:
ntscmgr.exe query <service_name>
b) Removing a service:
ntscmgr.exe remove <service_name>
is that the right way or any other way .
Please suggest my system alaready in running state can we do this things while system up or downtime required.
Is their any impact on exsiting system.

I have added two new extension on CUCM, Directory not showing in attendant console even after resynch on CUCM and attendant cosn

I have added two new extension on CUCM, Directory not showing in attendant console even after resynch on CUCM and attendant cosnole
Any idea?

Hello,
Can you tell us what versions of CUCM and CUxAC you are using? Just extensions alone in CUCM will not sync to the corporate directory within the attendant console application. You will at least have to have user's associated with those extensions and depending on your rule set within the console that should then bring those extensions into the console directory.
Thanks,
Tony

Directory not showing in attendant console

I have added two new extension on CUCM, Directory not showing in attendant console even after resynch on CUCM and attendant cosnole
Any idea?

Under Engineering ----Service Management,can u check LDAP service is running.
Also, under system configuration ---directory synchronisation ----Enable contact synchronisation is enabled.
Also, u are creating this user in AD and then, fetching to CUCM and Attendant Console is finally these users as CCM Source.
regds,
aman

Itouch goes through restore process then will not show home screen

itouch goes through restore process then will not show home screen. Only apple logo shows and flashes periodically.

- Try:
iOS: Not responding or does not turn on
- If not successful and you can't turn the iPod fully off, let the battery fully drain. After charging for at least an hour try the article again.
- If still problem that indicates a hardware problem and an appointment at the genius Bar of an Apple store is in order.

Some failed BPEL processes are not tracked in BPEL Console (not hydrated)

Hi all.
I'm experiencing a problem at a customer which has a standalone BPEL install (they use BPEL 10.1.3.1 only)
The customer is complaing that, due to some process errors, the BPEL process fails but, the process final state is not hydrated to database, so it's not possible to track the process execution.
I built a simple test case and tested against BPEL 10.1.3.1 and 10.1.3.3. The test consists of:
1 - A synchronous BPEL process using an Assign activity.
2 - In the assign, I force an error condition, for example copying the expression parseEscapedXML('some bad xml string') to a variable.
3 - I execute the BPEL process using the console
4 - The process finishes with error, but you don't get any instance in the "Recently Completed BPEL Process Instances"
This is a critical problem as we cannot track both what was successfully executed and what has failed.
Failed instances like this one are obviously logged in appserver files, but this is not an accpectable monitoring alternative.
This is even more critical because the customer does not have Enterprise Service Bus to mediate execution, where I could certainly track those failed ones.
Any ideas?
Is it possible to force hydration of all types of failed processes?
Thanks
Denis
Message was edited by:
[email protected]
Message was edited by:
[email protected]

Additional info: Having the process "In Flight" due to the checkpoint and subsequent "error", if I manually abort the instance and visualize the audit flow, I can see which activity has caused the error.
For example:
1 - I execute the process. It executes the checkpoint() and the ora:parseEscapedXML(), which causes the process to terminate unexpectedly.
2 - The process remains "In-Flight". If I go to the audit flow, it shows that the process has reached the checpoint activity, and nothing further.
3 - I manually abort the instance
4 - I check the audit flow again. This time I can see the flow beyond the checpoint, until the activity that caused the process to terminate (in this case the assign containing the parseScapedXML)
What I conclude is that, when I manually abort the instance, BPEL hydrates the process part that was only "in memory" (the actual point where the process has stoped)
Denis
Message was edited by:
[email protected]

BPEL processes not available on BPEL console when deployed from JDeveloper

Installation: SOA Suite 10.1.3.4 (Upgraded through patch) (Standalone OC4J)
When I deploy the BPEL processes through JDeveloper, they do not show up in the BPEL console. JDeveloper does not display any error message but in fact displays successful deploy. I am able to manually deploy processes from the BPEL console itself or by dropping in the BPEL suitcase in the deploy directory.
I noticed this issue when I tried installing AIA foundation pack 2.4. The installation showed the message below -
Failed to read wsdl at "http://AMVAIDYA-US:8888/orabpel/default/AIAErrorTaskAdministrationProcess/AIAErrorTaskAdministrationProcess?wsdl", because "Failed to read WSDL from http://AMVAIDYA-US:8888/orabpel/default/AIAErrorTaskAdministrationProcess/AIAErrorTaskAdministrationProcess?wsdl:WSDL not found".
Make sure wsdl is valid. You may need to start the OraBPEL server, or make sure the related bpel process is deployed correctly.
[Potential fix]: If your site has a proxy server, then you may need to configure your BPEL Server, designer and browser with your proxy server configuration settings (see tech note on http://otn.oracle.com/bpel for instructions).
I noticed that issue is independent of AIA since I cannot deploy any BPEL process through JDeveloper (or even through using the ant deploy in JDev)
Please help!
Thanks
Amol

I did try the verbose=true option but there are no errors there. The ant deploy task shows up as successful just like it shows from the right click -> Deploy to domain on the BPEL project. I created a sample async BPEL for this - it has just one assign activity with some dummy values for output. It builds fine. If I deploy the jar file created from this manually in the console it works. But it doesnt work from JDev or Ant. Is there anything I missed during the upgrade patch from 10.1.3.1 to 10.1.3.4? I did execute all the post and pre install tasks (including the orabpel, oraesb schema updates etc)
FYI, I can register an ESB from JDeveloper and it shows up in the ESB console.

BPEL process is not displaying in BPEL Console

Hi
We are deploying the process through jDeveloper to BPEL PM, we have around 100 process are successfully deployed. Once i restart the OPMN by giving OPMNCTL STOPALL and OPMNCTL STARTALL. The process are not displaying. Once restart the whole server means it is coming. what could be the problem
Thanks in Advance
Hamid

After deploying did you try a clear WSDL cache in the BPEL console?
Do you have a look in the log files?
Marc
http://orasoa.blogspot.com

Instance doesn't initiate from BPEL console

BPEL 10.1.2.0.2
Where can I find debug messages to understand why the process doesn't initiate from bpel console? message on console reads:
'Cannot find the specified instance'
Thanks

Check the Domain.log. I suspect you have an invalid XPATH expression before you reach the first hydration point. Take a look on the Manual Recovery Queue and you should see the Invoke message sitting there.
Pete

Task approval not reflected in BPEL Console

Dear Experts,
I am having a human task in my BPEL Process. Using wofk flow apis I am downloading task attachments from BPEL and able to store it in physical location.
Here I am allowing user to upload more attachments. So in BPEL I introduced "while" activity and depends upon the attachment count I am iterating and
storing the file to physical path.
But the issue is, when ever an user upload an attachment to task activity and has approve the task it gets approved.
But task approval is not getting reflected in BPEL console. Here in BPEL console still waiting for task response. I am not able to fix this.
But I think there might be an exception in my code. But it is not reflecting.
Please suggest me.
Thanks,
Rajesh

When the task is approved, is it disappearing from the task list of the worklist application ?
you need to check three log files,1) /<soa_home>/bpel/domains/<domain_name>/logs/domain.log and 2)<soa_home>/j2ee/<instance_name>/logs/<instance_name_directory>/, check .err and .out files.
Let us know if you are getting log entries related to your task.

Debugging mode - sql query not showing up in console

Hi,
I have turned on the debugging mode via Admin->Server Configuration->Debug Level. Set it to debug mode.
I restarted the server. I wanted to test if the query will show up if there was an error in the query.
However I am not seeing any query. It complains that there is some error, but doesn't show what query string it is using.
Anyone got any idea how I can get query to show up on console (BI Publisher web interface) as opposed to
going and seeing the log files on the server.
Please let me know.
Thanks
Girija

Thankyou Vetsrini.
I will try out custom log table approach.
I see that there is a way to test pl/sql scripts via the DBMS output
and for that we need some invoking program like SQL PLUS to get the
log out into a file.
However, we wanted to see if there is a way to set Pl/SQL log files
and get PL/SQL logs when the calling program is BI Publisher.
regards
Girija

Process instances do not show in BPEL Console

Similar Messages

Maybe you are looking for