BPEL/ESB Errors to Worklist app

Hi All,
I have a requirement in which I have to bring the error message for all the errors that happen in BPEL and ESB to the worklist application. I have used BPEL fault policy and BPEL client API to implement this in BPEL and listened ESB_ERROR topic to implement this in ESB.
Now I want one 'RESUBMIT' outcome to appear in the task details if these errors are retryable. My odubts are:
1) How can I find out which errors are retryable in case of both BPEL/ESB ? I found a Retyable field in ESB_FAULTED_INSTANCE table in ORAESB ; but not sure how to use it . How can I find out the same for BPEL?
2) How do I add the Outcome 'RESUBMIT' dynamicaaly to the task whenevr the error type is retryable?
Please pour in some ideas on how to implement this....
Thanks.

Please deploy the bpel project and then you can locate it in the bpel console.
Then ,initiate the main process and only then log into the worklist app with the correct port number.
Then login with the correct user credentials and will be able to see the tasks allocated to him.
P.S.:Unless you initiate the process in BPEL Console , you cannot see the tasks for the user in worklist app.

Similar Messages

Error when trying to view details of a task in Worklist App

I am trying to view the details of a task in the Worklist app
the new window comes up, but i get an error message
oracle.bpel.services.workflow.client.WorkflowServiceClientException: javax.naming.NameNotFoundException: Unable to resolve 'TaskQueryService'. Resolved ''; remaining name 'TaskQueryService'
     at oracle.bpel.services.workflow.query.client.TaskQueryServiceRemoteClient.getWorkflowContext(TaskQueryServiceRemoteClient.java:211)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at oracle.bpel.services.workflow.client.WFClientRetryInvocationHandler.invokeTarget(WFClientRetryInvocationHandler.java:133)
     at oracle.bpel.services.workflow.client.WFClientRetryInvocationHandler.invoke(WFClientRetryInvocationHandler.java:72)
     at $Proxy242.getWorkflowContext(Unknown Source)
     at oracle.bpel.services.workflow.client.worklist.util.WorkflowFilter.doFilter(WorkflowFilter.java:157)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocation
any pointers would be appreciated

can you please check if you can access this http://host:port/integration/services/TaskQueryService/TaskQueryService?WSDL
port here is soa managed server port.

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.

Error Handling in BPEL & ESB - Rejection Handlers

Hi guys
I have been trying to evaluate various ways for handling errors/exceptions in BPEL and ESB in Oracle SOA Suite 10.1.3.4 (Basic installation).
What i have found is that in ESB, errors can be handled at two levels: ESB routing service errors using ERROR_TOPIC and Adapter errors using RejectionHandlers. AND
in BPEL errors can be handled using in built try/catch (calling error hospital from the catch) and adapter erros using RejectionHandlers.
I tried using Rejection handlers (bpel, wsif, file) in BPEL and ESB. In BPEL they all are working fine when registered in bpel.xml.
But in ESB only the file handler is working. What i did in ESB is:
I set up an ESB which is polling a file adapter and simply putting the data into a table in database.
Then i created a BPEL (or a Webservice) which is based on http://localhost:8888/orabpel/xmllib/jca/RejectionMessage.wsdl file, taking
{http://xmlns.oracle.com/pcbpel/errorHandling}RejectedMessage as input.
Then I registered Rejection Handler in ESB's file adapter's .esbsvc (or Enpoint property- rejectedMessageHandlers):
"wsif://http//localhost8888/Error_Service/RejectionHandlerPort?wsdl|handleRejection|message"OR "bpel://default:welcome1|BPEL_Error_Handler|handleRejection|message"
I generated error in ESB by changing a column name of the table
For bpel rejection handler:
i was getting error: "<ERROR> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Rejection handler failed
Error while trying to hand off bad message to Rejection handler bpel://default|BPELProcess2|handleRejection|message due to: java.lang.Exception: Failed to create "ejb/collaxa/system/DeliveryBean" bean; exception reported is: "javax.naming.NameNotFoundException: ejb/collaxa/system/DeliveryBean not found
at com.evermind.server.rmi.RMIServerContext.lookup(RMIServerContext.java:207)
at com.evermind.server.ApplicationContext.unprivileged_lookup(ApplicationContext.java:256)
at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:196)
at javax.naming.InitialContext.lookup(InitialContext.java:351)"
It was solved by adding in server.xml - <application-server ... global-jndi-lookup-enabled="true">. But now i am getting
"Error while trying to hand off bad message to Rejection handler bpel://default:welcome1|BPEL_Error_Handler|handleRejection|message due to: java.lang.LinkageError: duplicate class definition: com/oracle/bpel/client/ejb/interfaces/IDeliveryBeanHome. Please address the underlying issue or correct/redeploy the process."
*For wsif rejection handler*:
getting error: "Error while trying to hand off bad message to Rejection handler wsif://http//localhost8888/Error_webservices/RejectionHandlerPort?WSDL|handleRejection|message due to: exception on JaxRpc invoke: serialization error: java.lang.IllegalArgumentException: getSerializer requires a Java type and/or an XML type
Please address the underlying issue or correct/redeploy the process."
I followed: Link:[http://www.oracle.com/technology/products/integration/adapters/pdf/Adapter_TN_004_Adapter_ErrorManagement.pdf]
Same bpel/wsif handlers pointing to same BPEL/J2EE services, if configured for BPEL adapters, works absolutly fine and gives proble in ESB.
Am i missing something in ESB or is there any patch need to be applied? Please help me there.
Thanks in advance.
Inder

Hi
I even installed SOA Suite 10.1.3.4 MLR#5 Advanced installation with Oracle Express dehyderation store.
I was able to use WSIF rejection handler with this upgrade... but bpel rejection handler was still a failure.
So basically i re-visited ESB documentation. it says that ESB will not support bpel rejection handler.
At least not upto now.
So Summary:
For BPEL we can use - file, wsif, bpel & aq rejection and fatal message handler.
For ESB we can use file, WSIF (10.1.3.4 with MLR#5) & aq rejection and fatal message handler.
Thanks
Inder
Keep going...

[HELP] [BPEL 11g] Customized BPEL worklist app could not work on JBoss

Dear all,
We are developing the customized Human Worklist app based on BPEL HW API 11g.
The application (some jsp pages) works fine in JDeveloper 11g. However, after deploy to JBoss, it always prompt with "NoClassDefFoundError" exception, although we have already add following 7 jar files into Classpath:
${jdeveloper.home}\Middleware\wlserver_10.3\server\lib\weblogic.jar
${jdeveloper.home}\Middleware\jdeveloper\modules\oracle.jrf_11.1.1\jrf.jar
${jdeveloper.home}\Middleware\jdeveloper\modules\oracle.webservices_11.1.1\wsclient.jar
${bea.home}/AS11gR1SOA/soa/modules/oracle.soa.fabric_11.1.1/bpm-infra.jar
${bea.home}/AS11gR1SOA/soa/modules/oracle.soa.workflow_11.1.1/bpm-services.jar
xml.jar
xmlparserv2.jar
Then we manually copy many other jars (nearly 100) under Weblogic server, but it still prompt lacking of some jar file with "NoClassDefFoundError" exception.
So, does BPEL 11g support deploy HW app outside weblogic, like JBoss? If so, what we need to set at JBoss side to run our app?
Thanks a lot.

Not sure it is available yet as I have not seen any doc for 11g.
here is the 10g instructions which may provide some pointers.
http://download-east.oracle.com/docs/cd/B31017_01/web.1013/b25947/deployment_topics012.htm
cheers
James

How does BPEL Fault Management Framework gel with ESB Error Handling ?

I see that BPEL 10.1.3.3 has pretty neat Fault Management Framework (although I have to admit it is not very well advertised).
The next logical question is: what about ESB ? Would that help in ESB error handling ? I understand that ESB has its own Error Hospital etc.; however, we have to constantly grapple with two distinct paths for any piece of integration functionality (1. ESB 2. BPEL). I guess, all of this will be moot in the 11g timeframe. Still wondering if anyone out there has somehow unified error handling for these two distinct offerings ?

It's not available in ESB, you have to implement/extend that by your self. Off course in the next release everthing will be better :-)
But, if you are able to use Oracle AIA (http://edelivery.oracle.com) You could use Oracle AIA Foundation, that has a fault 'hospital' implemented both for BPEL and ESB.
Marc
http://orasoa.blogspot.com

BPM worklist app, not working in Fusion SCM env..

I have a small BPEL+HWF app, with the BPM worklist UI component. It works well on my laptop, but when deployed on SCM FusionApp env, it fails to load the BPM app_UI?
I also noticed that the worklist app conf / ADF usage is different from my standalone laptop_SOA env and the FusionApp SOA_env. Are there any special steps to create/ register the HWF app UI in Fusion Apps Env?

It is deploying correctly, the worklist app displays my instance. Btu when I click on my worklist item, the UI does not load or display. Below is the browser error and logfile error messages.
-----Browser error-----
Not Found
The requested URL /workflow/DOO_Simulation_ProjectUI/faces/adf.task-flow was not found.
---Log file message---------
Caused By: oracle.adf.controller.ControllerException: ADFC-12002: The ADF Controller is unable to pop the top-level ADF unbounded task flow from the page flow stack.
at oracle.adfinternal.controller.state.PageFlowStack.pop(PageFlowStack.java:187. No
8. No customization to env or app. This is a user defined (but standard) BPEL process deployed. The same app works fine on my local laptop & SOA env

SOA 11g Worklist Apps Customisation and Integration with Plumtree Portal

Hi,
We want to migrate an existing application build using SOA Suite 10.1.3.3 to 11.1.1.2.0.
In the 10g application the worklist application was customised and the customised apps was linked as a remote portlet in BEA Plumtree Portal.
1)In 10g the worklist application source code is available (\SOA_Oracle_Home\bpel\samples\hw\worklistapp) for customisation but is that possible for 11g ?
(The location of the default deployed worklist apps in 11g is /../mdw_home/user_projects/domains/soa_domain/servers/soa_server1/tmp/_WL_user/worklistapp).
Can we take the source code and customize in jdev and deploy under a different contextname in 11g??
3)Our existing 10g worklist was customised a bit in terms of look and feel and for some custom authentication and it was deployed in the 10g SOA Server.
A sample jsp application was created and the login page of the custom worklist apps was linked in a inframe so that it works when integrated with the Plumtree portal as a remote portlet. And this worked perfectly in 10.1.3.3 SOA Suite.
However the 11g SOA worklist login when tagged in a jsp as an inframe in plumtree portal is giving a warning message
Warning: Unable to load content in a frame. Frame content will load at the top level. On cliicking the OK button the worklist page is opening. This is with Firefox browser . however form IE7 or 8 its timing out from portal.
As per http://newsoalife.blogspot.in/2009/09/framebusing-in-adf.html
changing the web.xml for the worklist can help.
Can anyone please let us know on the same as this appeas an unsupported one.
Regards
Ashif

Hi,
Can you check the log file.u are getting any error.can you check wf_error table also u are getting any error.
Can you check consumer in AQ tables.
Thanks,
Rahul

ESB error handling and notification features

Hello everyone,
I am newbie to oracle SOA ESB. I am an oracle apps guy.
This being my first post to this forum, I have a lot of questions. :-)
For a small intergration requirement, we are looking for a good integration tool
Some requirements are:
1) Flat files will be generated by concurrent programs on oracle apps which need to be transferred to legacy systems.
2) Pick the data from apps tables and insert them into another database. Not much translation required.
After some research, found ESB to be a good fit.
Before actually start using it, we wanted to do a couple of POCs.
So far we are using shell scripts for ftp process. We opted for an integration tool to have DB to DB transmission. Apart from this we need better error handling and error notification mechanism.
Some error conditions:
1) Unavailability of ftp server or Database server.
2) Permission issues. Say some files may not have read, write, deletion permissions. They need to be caught and notified.
3) Mandatory field missing while inserting data which is read from a flat file into a DB table etc..
My initial thoughts on error handling are:
Connection error: To retry for connection errors. If the retry fails send notification via email and also write the failed connection details into an error log file(apart from the server log file).
Data mismatch: NOtification to be sent with the error details.
I would like to know What happens to the file if the destination ftp server is unavailable while ESB is trying to FTP the file. Will ESB retain the file with itself and FTP the file once the ftp server is up?
In BPEL I could see try catch blocks which can be used to handle the errors and thus send notifications.
ESB documents introduced terms like error hospital related to error handling but I was not able to figure out a way of implementing them. As I am not well versed with XML and WSDL I am probably unable to use the fault tab which is in the routing service. I feel Oracle could have given some samples that explain about ESB error handling.
Also to my dismay, adapter docs say that there is a limitation of 7MB size for ftping. Although our file sizes often fall below this size, I would want to know if there is any workaround to over come this size constraint.
I think I put a lot of stuff in a single post and may be in the most haphazard way. Please bear with me.
Please suggest me of some documents if any related to my questions.
Would be really great if you can give me a straight forward solution to all the above problems
Hope this forum would be a great help to me.
Cheers,
Robert.

I have worked on a few SOA Apps implementations. Some successful and some not so. It really comes down to the type of integrations.
But I would say the majority of your integration will be batch as this is what eBus is all about. If this is the case then I would recommend Oracle Data Integrator. If you go Oracle Data Integrator Suite it includes Service Bus and BPEL. ODI has an eBusiness Suite adapter as well.
The good thing about ODI is that you can use it for data conversion, that conversion can then be reused once live, so the conversion is not throw away.
In SOA 10.1.3.4 the limit of 7MB has been resolved but you must be using the file / FTP adapter for input and out, from the sounds of it you want to call concurrent programs so this probably wouldn't work.
cheers
James

Trying to debug Worklist app with JDeveloper

We managed to get the worklistapp compiling under JDeveloper. Now, I'd like to debug it.
In order to debug (by running in the OC4J container within JDeveloper), it looks like I have to run the worklistapp as a remote client (specifying REMOTE_CLIENT or SOAP_CLIENT in the BaseServlet's init function). I used REMOTE_CLIENT. I also updated wf_client_config.xml and included the ORACLE_HOME/bpel/system/services/config directory in the classpath.
When I try to run the worklist app from JDeveloper, I get a null ptr exception (the line 'wfSvcClient.getAuthorizationService(idCtx);' is returning a null value for the authorization service):
Source breakpoint occurred at line 660 of TaskList.java.
07/01/30 16:57:37 java.lang.NullPointerException
07/01/30 16:57:37      at worklistapp.servlets.TaskList.checkTabsToDisplay(TaskList.java:669)
07/01/30 16:57:37      at worklistapp.servlets.TaskList.handleRequest(TaskList.java:122)
07/01/30 16:57:37      at worklistapp.servlets.BaseServlet.doGet(BaseServlet.java:144)
07/01/30 16:57:37      at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
07/01/30 16:57:37      at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
07/01/30 16:57:37      at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:711)
07/01/30 16:57:37      at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
07/01/30 16:57:37      at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
07/01/30 16:57:37      at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
07/01/30 16:57:37      at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
07/01/30 16:57:37      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
07/01/30 16:57:37      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
07/01/30 16:57:37      at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
07/01/30 16:57:37      at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
07/01/30 16:57:37      at java.lang.Thread.run(Thread.java:595)
I also tried to use the soap client (SOAP_CLIENT in BaseServlet's init()), and I get this exception even before logging into the worklistapp:
<2007-01-30 17:05:18,001> <ERROR> <oracle.bpel.services.workflow> <::>
java.lang.NullPointerException
     at oracle.bpel.services.workflow.verification.impl.VerificationService.getWorkflowContextJAXBObject(VerificationService.java:1952)
     at oracle.bpel.services.workflow.verification.impl.VerificationService.getWorkflowContextElement(VerificationService.java:1972)
     at oracle.bpel.services.workflow.user.client.AbstractDOMUserMetadataServiceClient.createBaseType(AbstractDOMUserMetadataServiceClient.java:675)
     at oracle.bpel.services.workflow.user.client.AbstractDOMUserMetadataServiceClient.getPublicPreferences(AbstractDOMUserMetadataServiceClient.java:620)
     at worklistapp.servlets.BaseServlet.initApplicationPreferences(BaseServlet.java:555)
     at worklistapp.servlets.BaseServlet.validateSession(BaseServlet.java:185)
     at worklistapp.servlets.BaseServlet.doGet(BaseServlet.java:142)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:711)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
     at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
     at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
     at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
     at java.lang.Thread.run(Thread.java:595)
<::> ORABPEL-30721
<::>
<::> Error in invoking user metadata service operation.
<::> An client side error occured in invoking the user metadata service operation getPublicPreferences.
<::> Please check the exception error stack to identify the error. Contact oracle support if error is not fixable.
<::>
I did start up the user metadata services and runtime config services(I can see all the soap endpoints for the workflow services from a browser). But the worklist app doesn't seem to connect to the remote server. I did update my wf_client_config.xml to point to the remote server on which BPEL is located. And the wf_client_config.xml file is in the classpath.
If I deploy the worklist app on the server with bpel (specifying the parent as 'orabpel', it all works fine). I just can't get it working as a remote client.
So, any suggestions? I've been looking at threads on this forum to get to this point, but now I'm stuck.
Thanks,
Sachin

I thought I'd ping this thread to see if anyone has been able to debug the Worklist application with JDeveloper. We are trying to customize the worklist application, and being able to use JDeveloper to debug would greatly help out.
However, I have still been unable to get the worklist application to be able to connect to the workflow services remotely via the SOAP_CLIENT:
wfSvcClient = WorkflowServiceClientFactory.getWorkflowServiceClient(
WorkflowServiceClientFactory.SOAP_CLIENT);
I've played around with the classpath to make sure I have all the jars (based on other similar threads in this forum), but have not had any luck yet.
From a web browser, I can specify the SOAP endpoint to the Workflow services, and am able to call the service in the browser.
I updated my wf_client_config.xml file to point to the endpoints. e.g:
<taskQueryService>
<soapEndPoint>http://myserver:8888/integration/services/TaskQueryService/TaskQueryService</soapEndPoint>
</taskQueryService>
Thanks for any help,
Sachin
The debug output:
[Starting OC4J using the following ports: HTTP=8988, RMI=23891, JMS=9227.]
C:\jdev\jdev\system\oracle.j2ee.10.1.3.40.66\embedded-oc4j\config>
C:\jdev\jdk\bin\javaw.exe -client -Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=1690 -classpath C:\jdev\j2ee\home\oc4j.jar;C:\jdev\jdev\lib\jdev-oc4j-embedded.jar -Xverify:none -XX:MaxPermSize=256m -DcheckForUpdates=adminClientOnly -Doracle.application.environment=development -Doracle.j2ee.dont.use.memory.archive=true -Doracle.j2ee.http.socket.timeout=500 -Doc4j.jms.usePersistenceLockFiles=false oracle.oc4j.loader.boot.BootStrap -config C:\jdev\jdev\system\oracle.j2ee.10.1.3.40.66\embedded-oc4j\config\server.xml
[waiting for the server to complete its initialization...]
Listening for transport dt_socket at address: 1690
Debugger connected to local process.
Jun 1, 2007 5:22:29 PM com.evermind.server.jms.JMSMessages log
INFO: JMSServer[]: OC4J JMS server recovering transactions (commit 0) (rollback 0) (prepared 0).
Jun 1, 2007 5:22:29 PM com.evermind.server.jms.JMSMessages log
INFO: JMSServer[]: OC4J JMS server recovering local transactions Queue[jms/Oc4jJmsExceptionQueue].
Ready message received from Oc4jNotifier.
Embedded OC4J startup time: 21594 ms.
Target URL -- http://192.168.89.52:8988/BPEL%20Samples-WorkListApplication-context-root/login.jsp
07/06/01 17:22:40 Oracle Containers for J2EE 10g (10.1.3.1.1) initialized
WARNING: Code-source C:\work\ProjectLaguna\ThirdParty\Oracle\SOA\10.1.3.1\j2ee\home\jazncore.jar (from <classpath> in C:\work\ProjectLaguna\dev\WorkItemList\WorkListApplcation\public_html) has the same filename but is not identical to /C:/jdev/j2ee/home/jazncore.jar (from <code-source> in META-INF/boot.xml in C:\jdev\j2ee\home\oc4j.jar). If it contains different versions of the same classes, it will be masked as the latter is already visible in the search path of loader current-workspace-app.web.BPEL Samples-WorkListApplication-webapp:0.0.0.
WARNING: Code-source C:\work\ProjectLaguna\ThirdParty\Oracle\SOA\10.1.3.1\diagnostics\lib\ojdl.jar (from manifest of /C:/work/ProjectLaguna/ThirdParty/Oracle/SOA/10.1.3.1/j2ee/home/jazncore.jar) has the same filename but is not identical to /C:/jdev/diagnostics/lib/ojdl.jar (from <code-source> (ignore manifest Class-Path) in META-INF/boot.xml in C:\jdev\j2ee\home\oc4j.jar). If it contains different versions of the same classes, it will be masked as the latter is already visible in the search path of loader current-workspace-app.web.BPEL Samples-WorkListApplication-webapp:0.0.0.
WARNING: Code-source C:\work\ProjectLaguna\ThirdParty\Oracle\SOA\10.1.3.1\lib\dms.jar (from manifest of /C:/work/ProjectLaguna/ThirdParty/Oracle/SOA/10.1.3.1/j2ee/home/jazncore.jar) has the same filename but is not identical to /C:/jdev/lib/dms.jar (from <code-source> (ignore manifest Class-Path) in META-INF/boot.xml in C:\jdev\j2ee\home\oc4j.jar). If it contains different versions of the same classes, it will be masked as the latter is already visible in the search path of loader current-workspace-app.web.BPEL Samples-WorkListApplication-webapp:0.0.0.
WARNING: Code-source C:\work\ProjectLaguna\ThirdParty\Oracle\SOA\10.1.3.1\webservices\lib\orasaaj.jar (from <classpath> in C:\work\ProjectLaguna\dev\WorkItemList\WorkListApplcation\public_html) has the same filename but is not identical to /C:/jdev/webservices/lib/orasaaj.jar (from <code-source> (ignore manifest Class-Path) in META-INF/boot.xml in C:\jdev\j2ee\home\oc4j.jar). If it contains different versions of the same classes, it will be masked as the latter is already visible in the search path of loader current-workspace-app.web.BPEL Samples-WorkListApplication-webapp:0.0.0.
WARNING: Code-source C:\work\ProjectLaguna\ThirdParty\Oracle\SOA\10.1.3.1\j2ee\home\lib\pcl.jar (from manifest of /C:/work/ProjectLaguna/ThirdParty/Oracle/SOA/10.1.3.1/j2ee/home/oc4j.jar) has the same filename but is not identical to /C:/jdev/j2ee/home/lib/pcl.jar (from system property java.class.path). If it contains different versions of the same classes, it will be masked as the latter is already visible in the search path of loader current-workspace-app.web.BPEL Samples-WorkListApplication-webapp:0.0.0.
07/06/01 17:22:42 Classpath: C:\jdev\jdk\jre\lib\rt.jar;C:\jdev\jdk\jre\lib\jsse.jar;C:\jdev\jdk\jre\lib\jce.jar;C:\jdev\jdk\jre\lib\charsets.jar;C:\jdev\jdk\jre\lib\ext\dnsns.jar;C:\jdev\jdk\jre\lib\ext\localedata.jar;C:\jdev\jdk\jre\lib\ext\sunjce_provider.jar;C:\jdev\jdk\jre\lib\ext\sunpkcs11.jar;C:\jdev\j2ee\home\oc4j-api.jar;C:\jdev\j2ee\home\lib\oc4j-unsupported-api.jar;C:\jdev\j2ee\home\lib\activation.jar;C:\jdev\j2ee\home\lib\mail.jar;C:\jdev\j2ee\home\lib\persistence.jar;C:\jdev\j2ee\home\lib\ejb30.jar;C:\jdev\j2ee\home\lib\ejb.jar;C:\jdev\j2ee\home\lib\javax77.jar;C:\jdev\j2ee\home\lib\javax88.jar;C:\jdev\j2ee\home\lib\servlet.jar;C:\jdev\j2ee\home\lib\jms.jar;C:\jdev\j2ee\home\lib\jta.jar;C:\jdev\j2ee\home\lib\jacc-api.jar;C:\jdev\j2ee\home\lib\connector.jar;C:\jdev\j2ee\home\lib\jmx_remote_api.jar;C:\jdev\j2ee\home\lib\jax-qname-namespace.jar;C:\jdev\webservices\lib\jaxr-api.jar;C:\jdev\webservices\lib\jaxrpc-api.jar;C:\jdev\webservices\lib\saaj-api.jar;C:\jdev\webservices\lib\jws-api.jar;C:\jdev\j2ee\home\lib\oc4j-internal.jar;C:\jdev\j2ee\home\lib\oems-jms-oc4j.jar;C:\jdev\j2ee\home\lib\oems-jms-client.jar;C:\jdev\j2ee\home\lib\oems-jms-server.jar;C:\jdev\j2ee\home\lib\oc4j-schemas.jar;C:\jdev\j2ee\home\lib\ojsp.jar;C:\jdev\j2ee\home\lib\oc4j_orb.jar;C:\jdev\j2ee\home\lib\iiop_support.jar;C:\jdev\j2ee\home\lib\orbbase.jar;C:\jdev\j2ee\home\iiop_gen_bin.jar;C:\jdev\j2ee\home\lib\jmxcluster.jar;C:\jdev\j2ee\home\jaccprovider.jar;C:\jdev\javavm\lib\jasper.zip;C:\jdev\j2ee\home\lib\adminclient.jar;C:\jdev\opmn\lib\optic.jar;C:\jdev\j2ee\home\jacc-spi.jar;C:\jdev\j2ee\home\jazncore.jar;C:\jdev\j2ee\home\jazn.jar;C:\jdev\jlib\ospnego.jar;C:\jdev\jlib\ldapjclnt10.jar;C:\jdev\webservices\lib\wsserver.jar;C:\jdev\webservices\lib\wsif.jar;C:\jdev\webservices\lib\orawsmetadata.jar;C:\jdev\webservices\lib\orajaxr.jar;C:\jdev\jlib\jssl-1_1.jar;C:\jdev\jlib\ojmisc.jar;C:\jdev\toplink\jlib\toplink-oc4j.jar;C:\jdev\diagnostics\lib\ojdl2.jar;C:\jdev\xqs\lib\xqs-api.jar;C:\jdev\xqs\lib\xds.jar;C:\jdev\jdev\lib\jdev-oc4j-embedded.jar;C:\jdev\j2ee\home\lib\pcl.jar;C:\jdev\j2ee\home\lib\ext;C:\jdev\j2ee\home\lib\ext\adfperfhandler.jar;C:\jdev\lib\dmsapp.jar;C:\jdev\jdev\system\oracle.j2ee.10.1.3.40.66\embedded-oc4j\applications\admin_ejb.jar;C:\jdev\j2ee\home\lib\scheduler.jar;C:\jdev\jdev\lib\jdev-rt.jar;C:\jdev\jdev\lib\ojc.jar;C:\jdev\jdev\system\oracle.j2ee.10.1.3.40.66\embedded-oc4j\connectors\datasources\datasources\datasources.jar;C:\jdev\BC4J\lib;C:\jdev\BC4J\lib\adfbinding.jar;C:\jdev\BC4J\lib\adfcm.jar;C:\jdev\BC4J\lib\adfm.jar;C:\jdev\BC4J\lib\adfmweb.jar;C:\jdev\BC4J\lib\adfs-jazn.jar;C:\jdev\BC4J\lib\adfs.jar;C:\jdev\BC4J\lib\adfshare.jar;C:\jdev\BC4J\lib\bc4jct.jar;C:\jdev\BC4J\lib\bc4jctejb.jar;C:\jdev\BC4J\lib\bc4jdomorcl.jar;C:\jdev\BC4J\lib\bc4jimdomains.jar;C:\jdev\BC4J\lib\bc4jmt.jar;C:\jdev\BC4J\lib\bc4jmtejb.jar;C:\jdev\BC4J\lib\bc4jsyscat.jar;C:\jdev\BC4J\lib\collections.jar;C:\jdev\jlib\commons-cli-1.0.jar;C:\jdev\mds\lib\concurrent.jar;C:\jdev\mds\lib\mdsrt.jar;C:\jdev\jlib\share.jar;C:\jdev\jlib\regexp.jar;C:\jdev\jlib\xmlef.jar;C:\jdev\BC4J\jlib\adfmtl.jar;C:\jdev\BC4J\jlib\adfui.jar;C:\jdev\BC4J\jlib\adf-connections.jar;C:\jdev\BC4J\jlib\dc-adapters.jar;C:\jdev\ord\jlib\ordim.jar;C:\jdev\ord\jlib\ordhttp.jar;C:\jdev\jlib\ojmisc.jar;C:\jdev\jlib\jdev-cm.jar;C:\jdev\lib\xsqlserializers.jar;C:\jdev\diagnostics\lib\ojdl.jar;C:\jdev\lib\dms.jar;C:\jdev\jdbc\lib\ojdbc14dms.jar;C:\jdev\opmn\lib\ons.jar;C:\jdev\jdbc\lib\ocrs12.jar;C:\jdev\rdbms\jlib\aqapi.jar;C:\jdev\j2ee\home\lib\ojms-provider.jar;C:\jdev\jdbc\lib\orai18n.jar;C:\jdev\lib\xmlparserv2.jar;C:\jdev\lib\xml.jar;C:\jdev\lib\xmlmesg.jar;C:\jdev\lib\xsu12.jar;C:\jdev\lib\xquery.jar;C:\jdev\jlib\osdt_core.jar;C:\jdev\jlib\osdt_cert.jar;C:\jdev\jlib\osdt_xmlsec.jar;C:\jdev\jlib\osdt_wss.jar;C:\jdev\jlib\osdt_saml.jar;C:\jdev\jlib\ojpse.jar;C:\jdev\jlib\oraclepki.jar;C:\jdev\toplink\jlib\toplink.jar;C:\jdev\toplink\jlib\antlr.jar;C:\jdev\toplink\jlib\toplink-essentials.jar;C:\jdev\webservices\lib\wsclient.jar;C:\jdev\webservices\lib\orasaaj.jar;C:\jdev\webservices\lib\xsdlib.jar;C:\jdev\webservices\lib\mdds.jar;C:\jdev\webservices\lib\relaxngDatatype.jar;C:\jdev\javacache\lib\cache.jar;C:\jdev\lib\xschema.jar;C:\jdev\webservices\lib\soap.jar;C:\jdev\sqlj\lib\runtime12.jar;C:\jdev\sqlj\lib\translator.jar;C:\jdev\webservices\lib\orawsdl.jar;C:\jdev\j2ee\home\applib;C:\jdev\j2ee\home\jsp\lib\taglib;C:\jdev\j2ee\home\jsp\lib\taglib\ojsputil.jar;C:\jdev\lib\dsv2.jar;C:\jdev\j2ee\home\lib\http_client.jar;C:\jdev\j2ee\home\lib\jgroups-core.jar;C:\work\ProjectLaguna\dev\WorkItemList\WorkListApplcation\public_html;C:\work\ProjectLaguna\dev\WorkItemList\WorkListApplcation\classes;C:\work\ProjectLaguna\ThirdParty\Oracle\SOA\10.1.3.1\bpel\lib\bpm-infra.jar;C:\work\ProjectLaguna\ThirdParty\Oracle\SOA\10.1.3.1\bpel\lib\orabpel-common.jar;C:\work\ProjectLaguna\ThirdParty\Oracle\SOA\10.1.3.1\bpel\lib\orabpel-thirdparty.jar;C:\work\ProjectLaguna\ThirdParty\Oracle\SOA\10.1.3.1\bpel\lib\orabpel.jar;C:\work\ProjectLaguna\ThirdParty\Oracle\SOA\10.1.3.1\j2ee\home\jazncore.jar;C:\work\ProjectLaguna\ThirdParty\Oracle\SOA\10.1.3.1\diagnostics\lib\ojdl.jar;C:\work\ProjectLaguna\ThirdParty\Oracle\SOA\10.1.3.1\lib\dms.jar;C:\work\ProjectLaguna\ThirdParty\Oracle\SOA\10.1.3.1\j2ee\home\oc4jclient.jar;C:\work\ProjectLaguna\ThirdParty\Oracle\SOA\10.1.3.1\bpel\lib\bicmn.jar;C:\work\ProjectLaguna\ThirdParty\Oracle\SOA\10.1.3.1\bpel\lib\bipres.jar;C:\work\ProjectLaguna\ThirdParty\Oracle\SOA\10.1.3.1\bpel\lib\uix2.jar;C:\work\ProjectLaguna\ThirdParty\Oracle\SOA\10.1.3.1\webservices\lib\orasaaj.jar;C:\work\ProjectLaguna\ThirdParty\Oracle\SOA\10.1.3.1\j2ee\home\oc4j.jar;C:\work\ProjectLaguna\ThirdParty\Oracle\SOA\10.1.3.1\j2ee\home\lib\pcl.jar;C:\product\10.1.3.1\OracleAS_1\bpel\system\services\config;C:\work\ProjectLaguna\ThirdParty\Oracle\SOA\10.1.3.1\bpel\system\services\lib\bpm-services.jar;C:\product\10.1.3.1\OracleAS_1\bpel\system\services\schema;C:\work\ProjectLaguna\ThirdParty\Oracle\SOA\10.1.3.1\webservices\client_lib\wsclient_extended.jar
07/06/01 17:22:48 log4j:WARN No appenders could be found for logger (collaxa.cube.services).
07/06/01 17:22:48 log4j:WARN Please initialize the log4j system properly.
<2007-06-01 17:22:48,504> <ERROR> <oracle.bpel.services.workflow> <::>
java.lang.NullPointerException
     at oracle.bpel.services.workflow.verification.impl.VerificationService.getWorkflowContextJAXBObject(VerificationService.java:1952)
     at oracle.bpel.services.workflow.verification.impl.VerificationService.getWorkflowContextElement(VerificationService.java:1972)
     at oracle.bpel.services.workflow.user.client.AbstractDOMUserMetadataServiceClient.createBaseType(AbstractDOMUserMetadataServiceClient.java:675)
     at oracle.bpel.services.workflow.user.client.AbstractDOMUserMetadataServiceClient.getPublicPreferences(AbstractDOMUserMetadataServiceClient.java:620)
     at worklistapp.servlets.BaseServlet.initApplicationPreferences(BaseServlet.java:556)
     at worklistapp.servlets.BaseServlet.validateSession(BaseServlet.java:183)
     at worklistapp.servlets.BaseServlet.doGet(BaseServlet.java:140)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:712)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:369)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:865)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:447)
     at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:215)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
     at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
     at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
     at java.lang.Thread.run(Thread.java:595)
<::> ORABPEL-30721
<::>
<::> Error in invoking user metadata service operation.
<::> An client side error occured in invoking the user metadata service operation getPublicPreferences.
<::> Please check the exception error stack to identify the error. Contact oracle support if error is not fixable.
<::>
<::>      at oracle.bpel.services.workflow.user.client.AbstractDOMUserMetadataServiceClient.getPublicPreferences(AbstractDOMUserMetadataServiceClient.java:630)
<::>      at worklistapp.servlets.BaseServlet.initApplicationPreferences(BaseServlet.java:556)
<::>      at worklistapp.servlets.BaseServlet.validateSession(BaseServlet.java:183)
<::>      at worklistapp.servlets.BaseServlet.doGet(BaseServlet.java:140)
<::>      at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
<::>      at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
<::>      at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:712)
<::>      at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:369)
<::>      at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:865)
<::>      at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:447)
<::>      at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:215)
<::>      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
<::>      at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
<::>      at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
<::>      at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
<::>      at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
<::>      at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
<::>      at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
<::>      at java.lang.Thread.run(Thread.java:595)
<::> Caused by: java.lang.NullPointerException
<::>      at oracle.bpel.services.workflow.verification.impl.VerificationService.getWorkflowContextJAXBObject(VerificationService.java:1952)
<::>      at oracle.bpel.services.workflow.verification.impl.VerificationService.getWorkflowContextElement(VerificationService.java:1972)
<::>      at oracle.bpel.services.workflow.user.client.AbstractDOMUserMetadataServiceClient.createBaseType(AbstractDOMUserMetadataServiceClient.java:675)
<::>      at oracle.bpel.services.workflow.user.client.AbstractDOMUserMetadataServiceClient.getPublicPreferences(AbstractDOMUserMetadataServiceClient.java:620)
<::>      ... 18 more
<2007-06-01 17:22:48,536> <ERROR> <oracle.bpel.services.workflow> <::>
java.lang.NullPointerException
     at oracle.bpel.services.workflow.verification.impl.VerificationService.getWorkflowContextJAXBObject(VerificationService.java:1952)
     at oracle.bpel.services.workflow.verification.impl.VerificationService.getWorkflowContextElement(VerificationService.java:1972)
     at oracle.bpel.services.workflow.user.client.AbstractDOMUserMetadataServiceClient.createBaseType(AbstractDOMUserMetadataServiceClient.java:675)
     at oracle.bpel.services.workflow.user.client.AbstractDOMUserMetadataServiceClient.getPublicPreferences(AbstractDOMUserMetadataServiceClient.java:620)
     at worklistapp.servlets.BaseServlet.initApplicationPreferences(BaseServlet.java:556)
     at worklistapp.servlets.BaseServlet.validateSession(BaseServlet.java:183)
     at worklistapp.servlets.BaseServlet.doGet(BaseServlet.java:140)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:712)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:369)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:865)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:447)
     at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:215)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
     at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
     at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
     at java.lang.Thread.run(Thread.java:595)

BPEL Console Error after applying 10.1.3.4.0 MLR#3 patch

After the installing the mlr#3 patch for 10.1.3.4.0 the BPEL console no longer starts. ESB Control is working
The following error is displayed:
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: Sat Dec 06 02:39:55 PST 2008
Build type: release
Source tag: PCBPEL_10.1.3.4.0MLR3_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)
Looking into the logs the full error is:
java.lang.NoSuchMethodException: com.collaxa.cube.ejb.impl.BPELProcessManagerBean.getDefaultRevision(com.oracle.bpel.client.BPELProcessId,
com.oracle.bpel.client.auth.DomainAuth)
at com.oracle.bpel.client.util.ExceptionUtils.handleServerException(ExceptionUtils.java:91)
at com.oracle.bpel.client.BPELProcessHandle.getMetaData(BPELProcessHandle.java:236)
at ngDeployedProcesses.jspService(_ngDeployedProcesses.java:118)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:462)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:400)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:414)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
at com.evermind.server.http.ServletRequestDispatcher.unprivileged_include(ServletRequestDispatcher.java:160)
at com.evermind.server.http.ServletRequestDispatcher.access$000(ServletRequestDispatcher.java:51)
at com.evermind.server.http.ServletRequestDispatcher$1.oc4jRun(ServletRequestDispatcher.java:97)
at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:284)
at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:102)
at com.evermind.server.http.EvermindPageContext.include(EvermindPageContext.java:456)
at index.jspService(_index.java:104)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:462)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:518)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:400)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:414)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
at com.evermind.server.http.ServletRequestDispatcher.unprivileged_forward(ServletRequestDispatcher.java:259)
at com.evermind.server.http.ServletRequestDispatcher.access$100(ServletRequestDispatcher.java:51)
at com.evermind.server.http.ServletRequestDispatcher$2.oc4jRun(ServletRequestDispatcher.java:193)
at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:284)
at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:198)
at com.collaxa.cube.fe.DomainFilter.doFilter(DomainFilter.java:230)
at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:400)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:414)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
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.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:221)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:122)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:111)
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)
Caused by: java.lang.NoSuchMethodException: com.collaxa.cube.ejb.impl.BPELProcessManagerBean.getDefaultRevision(com.oracle.bpel.client.BPELProcessId,
com.oracle.bpel.client.auth.DomainAuth)
at java.lang.Class.getMethod(Class.java:1581)
at com.evermind.server.ejb.interceptor.MethodStateFactory.createMethodState(MethodStateFactory.java:112)
at com.evermind.server.ejb.deployment.ExposableBeanDescriptor.createMethodStates(ExposableBeanDescriptor.java:657)
at com.evermind.server.ejb.deployment.ExposableBeanDescriptor.getRemoteComponentMethodStates(ExposableBeanDescriptor.java:723)
at com.evermind.server.ejb.deployment.ExposableBeanDescriptor.getMethodState(ExposableBeanDescriptor.java:599)
at com.evermind.server.ejb.AbstractEJBObject.OC4J_getMethodState(AbstractEJBObject.java:385)
at ProcessManagerBean_RemoteProxy_4bin6i8.getMetaData(Unknown Source)
at com.oracle.bpel.client.BPELProcessHandle.getMetaData(BPELProcessHandle.java:232)
... 52 more
The steps I followed for the MLR#3 patch on Windows 32 bit were:
1) Use opatch utility for patch 7586063 - No errors displayed and lsinventory output looks fine
2) Ran the upgrade_10134_10134mlr_olite.sql & upgrade_10134_10134MLR_olite.sql scripts for BPEL and ESB (Oracle Lite used for this development install)
Any ideas how to resolve the BPEL Console error?

After performing an opatch rollback I realised that I should have run the BPEL database upgrade script "upgrade_10134_10134mlr_above_mlr11_olite.sql" rather than the one listed in my previous post above.
So after reapplying the patch and running the correct script all is now working

Esb error handling

hi all,
is there any sample ESB project implementing error hospital there? i found many sites and blogs for BPEL error hospital but none for ESB. mention any site or blog for ESB error hospital sample project.
Thanks,
Terry

hi all,
is there any sample ESB project implementing error hospital there? i found many sites and blogs for BPEL error hospital but none for ESB. mention any site or blog for ESB error hospital sample project.
Thanks,
Terry

ESB Error Hospital and Rejection Handlers

Hi,
I am getting confused with ESB Error Hospital and ESB Rejection Handlers? Can anyone of you explain me what is this?
Thanks,
Gomathi

Rejection Handlers are used for adapters such as file adapter. When these fail during the invokation of the ESB, you can perform some operation, e.g. call a BPEL process. The default is to write to a default directory. But no notifications are made.
The error hospital is an error handlers for when the process fails in flight. This allows use to send notifications and retry if required, etc.
Here is a good doc on the subject.
http://www.oracle.com/technology/products/integration/esb/files/esb-transactions-errorhandling.pdf
cheers
James

Mechanism to document bpel/esb code

Is there any mechanism to document bpel/esb code?
Thanks In Advance
priyadarshi
Edited by: pidi2008 on May 31, 2010 10:34 PM

Hi
I made a mistake.... I copied the wrong error message from the ESB console ..... The response code is 500 and not 401.......
Here is the message at ESB console :
An unhandled exception has been thrown in the ESB system. The exception reported is: "org.collaxa.thirdparty.apache.wsif.WSIFException: exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message transmission failure, response code: 500 at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeOperation(WSIFOperation_JaxRpc.java:1720) at com.collaxa.cube.ws.wsif.providers.oc4j.jaxrpc.WSIFOperation_JaxRpc.invokeRequestResponseOperation(WSIFOperation_JaxRpc.java:1466) at
and in the WSM gateway error is :
Error message - Service returns soap fault: Fault Code=[:XXXXX_yyyyPortType] Fault String=[Cannot figure out operation name. Bad SOAPAction or wsa:Action.];

BPEL transaction in custom worklist application

Hi,
How can we be sure about transaction while performing actions within worklist client?
Such an example, we developed an application by using oracle soa suite worklist api's.
Beside task updating,payload adjustion we need to do some other jobs including business logic in our java client application.
In such cases, if there is an exception at java code, it doesnt commit to database but bpel integration code performs... Is there any way which you can control all this functions calling within one transaction? I want to rollback all if you come up with an exception.
I found an xml attribute which you need to configure in wf client config.xml, we use RMI for performing actions...
participateInClientTransaction true
How does it work?
Thanks for help,
Regards...

Hi,
Every release of soa suite may have an updated version of the worklist application. So if you customize the application and upgrade your soa suite installation there may be ar risk you get into problems. However, most of the time the updated version solves existing bug and no more than that. An other issue is that if you are using the bpel libraries to connect to a bpel server the client always needs to be of the same version as the server. What you should do is:
- get the new 10.1.3.3 version of the libraries or install JDeveloper 10.1.3.3
- update your orabpel.properties file and make sure the bpel home is pointing to the new version
- update/verify the build.xml that it is pointing to the new libraries
- rebuild/compile your customized worklist app against the new libraries
- redeploy the new worklist application to the 10.1.3.3 server
Kind Regards,
Andre

BPEL/ESB Errors to Worklist app

Similar Messages

Maybe you are looking for