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.

Similar Messages

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

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

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 ?

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

Not able find BPEL console link in 11g

Hi,
I have installed SOA suite11g, Oracle Xpress Edition 11.0.0.28844, Weblogic server 10.3, Jdeveloper 11g. But I am not able to see my BPEL Console when I use the link http://localhost:8001/BpelConsole.
All the above mentioned components have been installed in my machine only so there is no connectivity issue.
Please let me know if I am missing something or what are the steps to get to the BPEL Console. I am able to login to my weblogic admin console.
Any kind of help is appreciated.
Thanks,
Abhay

I am in the same boat please let me know if you find any solution.
--Hi Gurus help please!

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

Prestage Package status not reflecting on the console

Hello,
I have extracted some prestage packages successfully on the new DP but for some reasons, it doesn’t reflect the status on the primary server. After troubleshooting, I found
this article which describes my issue similarly.
http://eskonr.com/tag/sccm-2012/page/2/
Where it says, “Will reject this STA for DP”, that similarly matches with my concern.
I have followed the article regarding the script for compare the version difference but what I am not sure is, I believe it ultimately says to redistribute the content to
the DP once more ?
Let me know if I am wrong or if there is any other way as this is happening for many prestage packages.
Not sure how it started all of a sudden when it working since a day before.

Hello,
I have created a new prestage package and it extracted successfully as per the below message in Distmgr.log but for some reasons the status doesnt reflect on the console.
Please help as this is really urgent
Processing status update for package AAA SMS_DISTRIBUTION_MANAGER
11/12/2014 9:25:21 AM 11344 (0x2C50)
Successfully updated the package server status for ["Display=\\<DP server>\"]MSWNET:["SMS_SITE=SiteID"]\\<DP server>\ for package AAA, Status 3
SMS_DISTRIBUTION_MANAGER 11/12/2014 9:25:21 AM
11344 (0x2C50)
STATMSG: ID=2330 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=<primaryserver>SITE=<SiteID> PID=19600 TID=11344 GMTDATE=Wed Nov 12 03:55:21.886 2014 ISTR0="AAA" ISTR1="["Display=\\<DP
server>\"]MSWNET:["SMS_SITE=<SiteID>"]\\<DP server>\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400
AVAL0="AAA" AID1=404 AVAL1="["Display=\\<DP server>\"]MSWNET:["SMS_SITE=<SiteID>"]\\<DP server>\"
SMS_DISTRIBUTION_MANAGER 11/12/2014 9:25:21 AM
11344 (0x2C50)
Successfully delete package status file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\BKP96Y8Q.STA
SMS_DISTRIBUTION_MANAGER 11/12/2014 9:25:21 AM
11344 (0x2C50)

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]

Process not available in bpel console after deploying it

Hi All,
I am following note 459640.1. In step 5-j It asks to deploy the bpel processes using the following command line:
obant -buildfile WshJarBuild.xml
-DnewOtmURL=<OTM SERVER URL>
-DbpelHome=<BPEL HOME DIR>
[-DnewDbConnName=<DB CONNECTION NAME>]
[-Ddeploy=<BPEL DOMAIN>]
It shows no errors and last message is "BUILD SUCCESSFUL". Ialso shows the file is getting copied correctly:
[copy] Copying 1 file to /bastet/oracleAS/product/10.1.3/OAS/bpel/integration/orabpel/domains/default/deploy
(same with all other jar files.. )
I checked in the same directory and I can see all jar files in there.
I restarted the bpel service and go to bpelconsole but the deployed processes are not there. I checked the logfile and I can see when the default processes like TaskManager is started but there is no references to he new deployed processes.
Any ideas would be greatly appreciated!!!
Thanks in advance

Can i suggest you turn domain logging to debug, and monitor the domain log file while you deploy. That might shed some light / reveal any errors.

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?

Changes made in EMS are not reflected in EMC

Hello all,
I realise that this is 2013 discussion, but I could not find a 2010 section.
My problem is simple: any change that I make inside the Exchange Shell is simply not reflected in the Console. It doesn't appear there. It can't be searched for. Nothing.
I'd like to know how to fix this. Exchange is very broken when it is operating like this, and I pretty much cannot do anything. Customer GALs are exposed to each other, etc.... because changes won't occur even though the shell says they have.

Hi
What changes are you making? Some changes do take time as replication etc. happens in the backend. Have you tried restarting the server? do you see any changes after that?
Please also check the Application log for errors.

Error on launching BPEL Console

Hi,
I have applied MLR 7 patch (Patch # 8372141 ) on my fmw environment.
Before applying the patch:
SOA Suite - 10.1.3.1 + 10.1.3.4
OPatch 1.0.0.0.61
MLR5 patch 7714967
Before applying the patch it was working fine and no issues.
After applying the patch, I could not login to BPEL Console URL, getting the below error message
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.
Build Information:
Oracle BPEL Server version 10.1.3.4.0
Build: 0
Build time: Fri May 01 18:07:27 PDT 2009
Build type: release
Source tag: PCBPEL_10.1.3.4.0MLR7_GENERIC_RELEASE
Exception Message:
javax.servlet.ServletException - com.collaxa.cube.ejb.impl.BPELProcessManagerBean.getDefaultRevision(com.oracle.bpel.client.BPELProcessId, com.oracle.bpel.client.auth.DomainAuth)
I could not find a way to attach the log file and the log file content is too big to post it here.. (exceeds the maximum length)
Could someone help me on this ?
Thanks,
Suresh

Please post this on the BPEL forum.
http://forums.oracle.com/forums/index.jspa?categoryID=84

Javax.servlet.ServletException - On launching BPEL Console

Hi,
I have applied MLR 7 patch (Patch # 8372141 ) on my fmw environment.
Environment Details applying the patch:
SOA Suite - 10.1.3.1 + 10.1.3.4
OPatch 1.0.0.0.61
MLR5 patch 7714967
Before applying the patch it was working fine and no issues.
After applying the patch, I could not login to BPEL Console URL, getting the below error message
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.
Build Information:
Oracle BPEL Server version 10.1.3.4.0
Build: 0
Build time: Fri May 01 18:07:27 PDT 2009
Build type: release
Source tag: PCBPEL_10.1.3.4.0MLR7_GENERIC_RELEASE
Exception Message:
javax.servlet.ServletException - com.collaxa.cube.ejb.impl.BPELProcessManagerBean.getDefaultRevision(com.oracle.bpel.client.BPELProcessId, com.oracle.bpel.client.auth.DomainAuth)
I could not find a way to attach the log file and the log file content is too big to post it here.. (exceeds the maximum length)
Could someone help me on this ?
Thanks,
Suresh

Hi,
Yes you are correct. There was a mismatch in orabpel.ear file sizes. Seems post.bat script did not run properly.
Ran the below commands manually,
chmod 755 $ORACLE_HOME/bpel/system/services/lib/orabpel.ear
chmod 755 $ORACLE_HOME/bpel/system/services/lib/ejb_services.jar
chmod 755 $ORACLE_HOME/bpel/system/services/lib/ejb_ob_engine.jar
cp $ORACLE_HOME/bpel/system/j2ee/orabpel.ear $ORACLE_HOME/bpel/system/services/lib/orabpel.ear
cp $ORACLE_HOME/bpel/system/j2ee/ejb/oc4j_ejb_services.jar $ORACLE_HOME/bpel/system/services/lib/ejb_services.jar
cp $ORACLE_HOME/bpel/system/j2ee/ejb/ejb_ob_engine_oc4j.jar $ORACLE_HOME/bpel/system/services/lib/ejb_ob_engine.jar
cd $ORACLE_HOME/bpel/system/services/lib
$ORACLE_HOME/jdk/bin/jar -uvf orabpel.ear ejb_services.jar ejb_ob_engine.jar
cp $ORACLE_HOME/bpel/system/services/lib/orabpel.ear $ORACLE_HOME/j2ee/oc4j_soa/applications/orabpel.ear
Then took a backup of the folder $ORACLE_HOME/j2ee/oc4j_soa/application-deployments/orabpel
Deleted "orabpel" folder and restarted the opmn
This worked.
Thanks,
Suresh M

Task approval not reflected in BPEL Console

Similar Messages

Maybe you are looking for