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?

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.

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.

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

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

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 ?

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

Deployed processes stopped showing up in BPEL console

Hello,
Our BPEL processes stopped picking up business events; BPEL console dashboard is empty. After, restarting oc4j_soa instance on secondary node, BPEL process picked up business events. After few minutes, BPEL process showed in console.
After one day, BPEL processes disappeared from console.
Following is the error message, I see in soa_err*.log on all nodes after the last successful pick up.
Nov 5, 2010 7:18:57 PM org.collaxa.thirdparty.jgroups.blocks.ConnectionTable$Connection run
INFO: exception is java.net.SocketException: Socket closed
Nov 5, 2010 7:18:57 PM org.collaxa.thirdparty.jgroups.blocks.PullPushAdapter run
WARNING: [<null>] channel closed, exception is ChannelClosedException
10/11/05 19:22:28 oracle.oc4j.rmi.ApplicationStoppedException: Application is not in RUNNING state
10/11/05 19:22:28      at com.evermind.server.ejb.AbstractEJBHome.checkRunningState(AbstractEJBHome.java:732)
10/11/05 19:22:28      at com.evermind.server.ejb.AbstractEJBObject.OC4J_startCall(AbstractEJBObject.java:361)
10/11/05 19:22:28      at ServerBean_RemoteProxy_4bin6i8.init(Unknown Source)
10/11/05 19:22:28      at com.collaxa.cube.admin.CXLoaderServlet.init(CXLoaderServlet.java:60)
Also, EM console does not show any web services for ORABPEL application.
What do I need to do make the deployed process show up in BPEL console?
Regards,
Siva

I ran into a BPEL_OC4J_SOAP_Provider error today and it was related to my proxy. The proxy on my local machine with JDeveloper would allow a WSDL with an unqualified name through. For instance, the machine kronos:7779 would validate, compile, and deploy from my machine. But looking up the WSDL on the server would produce the above described error. When I changed the name of the server to kronos.whatever.com:7779 it worked as expected on the server.

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

Deployed Apps Not Showing in OEM

Hello!
Sometimes (this is random) when I deploy an application to OAS 10.1.2.0.2, the app will not show in OEM. It is there and you can access it, but not listed yet in OEM. You have to wait a while (several minutes) for the app to show.
Sometimes I uninstall an app (war file) and then try to install it again (using the OEM console), and I get a message saying that the app is still deployed. When this happens I deploy straight from JDeveloper 10.1.3.3.0.4157 and it seems to "overwrite" whatever is currently on OAS.
Looks like some of this information is being cached (WebCache?)...
Is there a utility I can run to force-refresh or synchronize the applications list on OAS?
Thank you!

I have similar issue, this is how I fixed it:
Fix: 1) First try to restart OAS and deploy it.
2) If step 1 does not work, stop home and manually add entry to j2ee\home\config\server.xml:
<application name="xxx" path="../applications/xxx.ear" auto-start="true" />
Restart Home, trying to deploy the application, it might still fail; however the entry popped up on OEM, and choose Redeploy afterward.
_*

Transactions Not Showing up in Console

We recently deployed new functionality in our WLS 6.1 based application. The new
functionality consists of MDB's and a Stateless Session Bean which the MDB's invoke.
The MDB's are
packaged in a separate jar file from the SSB, which is packaged in another jar
file
that houses all of our SSB's. The MDB's are transactional.
One peculiar issue we have noticed is that in the WLS Console, we do not "see"
any
transactions related to these new MDB's or the new SSB (Servers->OurServer->Monitoring
Tab->JTA Tab).
If you click on "Monitor all Transactions by Name" we are expecting to see an
entry
for each MDB's onMessage() method, in addition to any method's invoked on the
new Stateless Session Bean.
All of our other Stateless Session Bean methods are show in the "Monitor all Transactions
by Name" View.
Any insight as to why these MDB's and SSB are not showing up in this view? Are
we misconfigured in anyway?
Please let me know if you need further information, as I would gladly provide
it.
Thanks,
Al

I hope this is the last one on this topic!
With a one line script I can use the consul easily but lets say I have something really complicated like the script below. Other than fitting it on one line how can I run it from the console?
for (var i = 0; i < 10; i++) {
console.println(i);
Ctrl Enter after the } throws the following error
SyntaxError: syntax error
1:Console:Exec
undefined
Sorry for asking such pathetically basic questions

Missing xsd:choice block in process initiate page in BPEL console

Hello,
I deployed a process to Application Server 10g 10.1.3.1.0. And I wanted to initiate it from BPEL console, but from whole xml that should be there, I could only see elements, and no choice block that is also in the schema. Does anyone know what might be the problem?

Did you do a try to clear the WSDL cache? This could sometimes help.
Are you using 10.1.3.0 or updated to 10.1.3.3 with latest patch set?
Marc

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.

Deployed processes not showing in BPEL Console

Similar Messages

Maybe you are looking for