Unable to compile a BPEL process

Hi All,
When I am trying to compile the BPEL process I am getting the following error. There is nothing wrong with the BPEL process but still throwing an error.
Please help me in compiling my BPEL process.
[bpelc] The compiler has run out of memory. Consider using the "-J-mx<number>" command line option to increase the maximum heap size.
[bpelc] ORABPEL-01005
[bpelc]
[bpelc] Failed to compile classes.
[bpelc] Failed to compile the generated BPEL classes for "MyProcess".
Where can I set this -J-mx ??
Thank you.

1. Restarting jdeveloper would fix the problem.
2. Or, close the jdeveloper --> remove system folder --> restart the jdeveloper --> try again.
--Prasanna                                                                                                                                                                                                                                                                                                                           

Similar Messages

  • Error in compiling the BPEL process

    Hi,
    I am getting the following error while compiling the BPEL process. Its a simple process with a Pick activity and have two onMessage activities. One of the activity is having the correlation set and another one is not. Is that the problem ? If yes what should I do to resolve this.
    Any thoughts ?
    {color:#ff0000}[bpelc] classpath is: C:\apache-maven-2.0.9\boot\classworlds-1.1.jar;D:\workspace\Eclipse\ExternalUserWorkflow\src\test\resources\ContractorServiceFailureDeployment;D:\oracle\product\10.1.3.1\OracleAS_1\bpel\lib\orabpel-ant.jar;D:\oracle\product\10.1.3.1\OracleAS_1\bpel\lib\orabpel-boot.jar;D:\oracle\product\10.1.3.1\OracleAS_1\bpel\lib\orabpel-common.jar;D:\oracle\product\10.1.3.1\OracleAS_1\bpel\lib\orabpel-exts.jar;D:\oracle\product\10.1.3.1\OracleAS_1\bpel\lib\orabpel-thirdparty.jar;D:\oracle\product\10.1.3.1\OracleAS_1\bpel\lib\orabpel.jar;D:\oracle\product\10.1.3.1\OracleAS_1\bpel\lib\xmlparserv2.jar
    [bpelc] C:\DOCUME~1\krishnaa\LOCALS~1\Temp\bpelc1637.tmp\BPEL-INF\src\bpel\test\BPEL_BIN.java:5656: nested class bpel.test.BPEL_BIN. $BPELC_BpRpl0 must be declared abstract. It does not define java.lang.String __getInitiateCorrelationSetNames()[] from class com.collaxa.cube.engine.ext.wmp.BPELReplyWMP.
    [bpelc] public final static class $BPELC_BpRpl0 extends com.collaxa.cube.engine.ext.wmp.BPELReplyWMP
    [bpelc] ^
    [bpelc] 1 error
    [bpelc] ORABPEL-01005
    [bpelc]
    [bpelc] Failed to compile classes.{color}
    Thank you.

    It looks to me that, you have manually changed something in the BPEL process code.
    A process designed via Jdev/designer can only have one variable in inputHeaderVariable syntax.
    While Bpel standard supports calling inputHeaderVariable with two variables, if the generated file was tinkered with to add an extra variable, then this is not Jdev bug and you need to use the latest JDev 10.1.3.4.
    If you are not manually modifying or tinkering the process, then let me know what are the errors you get out of compiling that new BPEL project in JDeveloper 10.1.3.4 ?
    Hope this helps!
    Cheers
    Anirudh Pucha

  • Errors occured when compile the bpel process

    Errors occurred when compile the bpel process using bpel designer for Eclipse:
    (com.oracle.bpel.designer_0.9.13)
    using PM: bpel_jboss_101200
    More error infomation following:
    Buildfile: E:\OraBpelDEclipse3.2\workspace\AboutTest\build.xml
    main:
    [bpelc] E:\OraBpelDEclipse3.2\workspace\AboutTest\temp\bpelc762.tmp\BPEL-INF\src\bpel\p0\BPEL_BIN.java:835: Invalid expression statement.
    [bpelc] retun true;
    [bpelc] ^
    [bpelc] E:\OraBpelDEclipse3.2\workspace\AboutTest\temp\bpelc762.tmp\BPEL-INF\src\bpel\p0\BPEL_BIN.java:835: ';' expected.
    [bpelc] retun true;
    [bpelc] ^
    [bpelc] E:\OraBpelDEclipse3.2\workspace\AboutTest\temp\bpelc762.tmp\BPEL-INF\src\bpel\p0\BPEL_BIN.java:208: Method setPartneLinkBinding(com.collaxa.cube.rm.suitcase.PartnerLinkBindingDescriptor) not found in class com.collaxa.cube.engine.types.bpel.CXPartnerLink.
    [bpelc] __pl.setPartneLinkBinding(getProcessDescriptor().getPartnerLinkBindings().getPartnerLinkBinding(__pl.getName()));
    [bpelc] ^
    [bpelc] E:\OraBpelDEclipse3.2\workspace\AboutTest\temp\bpelc762.tmp\BPEL-INF\src\bpel\p0\BPEL_BIN.java:584: Undefined variable: __ctx
    [bpelc] __setOutgoingLinks(__sc, __ctx);
    [bpelc] ^
    [bpelc] 4 errors
    BUILD FAILED
    E:\OraBpelDEclipse3.2\workspace\AboutTest\build.xml:28: ORABPEL-01005
    Error in java files auto-generated when compiling ,why?
    Thanks!

    when compiled again without any change, the same errors like above are not occurs
    more info.
    Buildfile: E:\OraBpelDEclipse3.2\workspace\AboutTest\build.xml
    main:
    BUILD SUCCESSFUL
    Total time: 9 seconds
    BUT, some errors occurs in BPEL PM server and in Console the process is not available
    more Info: Because I using Chinese version,some chinese Info occurs in the error infomation ,so i have translated some character into English.
    process "AboutTest" (version "1.0") compiled sucessfully
    15:49:15,718 INFO [STDOUT] <2007-05-11 15:49:15,718> <INFO> <default.collaxa.cu
    be.engine.deployment> process "AboutTest" (version "1.0") loaded sucessfully.
    16:25:25,265 INFO [STDOUT] <2007-05-11 16:25:25,250> <INFO> <default.collaxa.cu
    be.compiler> validating "E:\OraBPELPM\domains\default\tmp\.bpel_AboutTest_1.0.jar\
    AboutTest.bpel" ...
    16:25:35,015 INFO [STDOUT] E:\OraBPELPM\domains\default\tmp\.bpel_AboutTest_1.0
    .jar\BPEL-INF\src\bpel\p0\BPEL_BIN.java:835: Invalid expression statement.
    16:25:35,015 INFO [STDOUT] retun true;
    16:25:35,015 INFO [STDOUT] ^
    16:25:35,031 INFO [STDOUT] E:\OraBPELPM\domains\default\tmp\.bpel_AboutTest_1.0
    .jar\BPEL-INF\src\bpel\p0\BPEL_BIN.java:835: ';' expected.
    16:25:35,031 INFO [STDOUT] retun true;
    16:25:35,031 INFO [STDOUT] ^
    16:25:35,859 INFO [STDOUT] E:\OraBPELPM\domains\default\tmp\.bpel_AboutTest_1.0
    .jar\BPEL-INF\src\bpel\p0\BPEL_BIN.java:208: Method setPartneLinkBinding(com.col
    laxa.cube.rm.suitcase.PartnerLinkBindingDescriptor) not found in class com.colla
    xa.cube.engine.types.bpel.CXPartnerLink.
    16:25:35,859 INFO [STDOUT] __pl.setPartneLinkBinding(getProcessDescript
    or().getPartnerLinkBindings().getPartnerLinkBinding(__pl.getName()));
    16:25:35,859 INFO [STDOUT] ^
    16:25:35,859 INFO [STDOUT] E:\OraBPELPM\domains\default\tmp\.bpel_AboutTest_1.0
    .jar\BPEL-INF\src\bpel\p0\BPEL_BIN.java:584: Undefined variable: __ctx
    16:25:35,859 INFO [STDOUT] __setOutgoingLinks(__sc, __ctx);
    16:25:35,859 INFO [STDOUT] ^
    16:25:35,859 INFO [STDOUT] 4 errors
    16:25:36,343 INFO [STDOUT] <2007-05-11 16:25:36,312> <ERROR> <default.collaxa.c
    ube.engine.deployment> <CubeProcessFactory::generateProcessClass>
    process "AboutTest" (version "1.0") compiled failed.
    16:25:36,359 INFO [STDOUT] <2007-05-11 16:25:36,359> <ERROR> <default.collaxa.c
    ube.engine.deployment> <CubeProcessLoader::create> can not compile the class .
    can not compile the bpel class generated from "AboutTest".
    16:25:36,375 INFO [STDOUT] <2007-05-11 16:25:36,375> <ERROR> <default.collaxa.c
    ube.engine.deployment> process "AboutTest" (version "1.0") loaded failed!!
    16:25:37,281 INFO [STDOUT] <2007-05-11 16:25:37,265> <ERROR> <default.collaxa.c
    ube> <BaseCubeSessionBean::logError>
    if you have installed patched in server, please check whether the proriety "bpelcClasspath" contained the patch class.
    16:25:37,343 INFO [STDOUT] at com.collaxa.cube.engine.deployment.CubeProces
    sHolder.bind(CubeProcessHolder.java:1257)
    16:25:37,343 INFO [STDOUT] at com.collaxa.cube.engine.deployment.CubeProces
    sHolder.loadAndBind(CubeProcessHolder.java:870)
    16:25:37,421 INFO [STDOUT] at com.collaxa.cube.engine.deployment.CubeProces
    sHolder.loadArchive(CubeProcessHolder.java:812)
    16:25:37,421 INFO [STDOUT] at com.collaxa.cube.engine.CubeEngine.loadProces
    sArchive(CubeEngine.java:985)
    16:25:37,421 INFO [STDOUT] at com.collaxa.cube.ejb.impl.BPELDomainManagerBe
    an.loadProcessArchive(BPELDomainManagerBean.java:390)
    16:25:37,421 INFO [STDOUT] at sun.reflect.NativeMethodAccessorImpl.invoke0(
    Native Method)
    16:25:37,421 INFO [STDOUT] at sun.reflect.NativeMethodAccessorImpl.invoke(N
    ativeMethodAccessorImpl.java:39)
    16:25:37,421 INFO [STDOUT] at sun.reflect.DelegatingMethodAccessorImpl.invo
    ke(DelegatingMethodAccessorImpl.java:25)
    16:25:37,421 INFO [STDOUT] at java.lang.reflect.Method.invoke(Method.java:3
    24)
    16:25:37,421 INFO [STDOUT] at org.jboss.ejb.StatelessSessionContainer$Conta
    inerInterceptor.invoke(StatelessSessionContainer.java:683)
    16:25:37,421 INFO [STDOUT] at org.jboss.resource.connectionmanager.CachedCo
    nnectionInterceptor.invoke(CachedConnectionInterceptor.java:186)
    16:25:37,421 INFO [STDOUT] at org.jboss.ejb.plugins.StatelessSessionInstanc
    eInterceptor.invoke(StatelessSessionInstanceInterceptor.java:72)
    16:25:37,421 INFO [STDOUT] at org.jboss.ejb.plugins.AbstractTxInterceptor.i
    nvokeNext(AbstractTxInterceptor.java:84)
    16:25:37,421 INFO [STDOUT] at org.jboss.ejb.plugins.TxInterceptorCMT.runWit
    hTransactions(TxInterceptorCMT.java:282)
    16:25:37,421 INFO [STDOUT] at org.jboss.ejb.plugins.TxInterceptorCMT.invoke
    (TxInterceptorCMT.java:148)
    16:25:37,437 INFO [STDOUT] at org.jboss.ejb.plugins.SecurityInterceptor.inv
    oke(SecurityInterceptor.java:111)
    16:25:37,437 INFO [STDOUT] at org.jboss.ejb.plugins.LogInterceptor.invoke(L
    ogInterceptor.java:191)
    16:25:37,437 INFO [STDOUT] at org.jboss.ejb.plugins.ProxyFactoryFinderInter
    ceptor.invoke(ProxyFactoryFinderInterceptor.java:122)
    16:25:37,437 INFO [STDOUT] at org.jboss.ejb.StatelessSessionContainer.inter
    nalInvoke(StatelessSessionContainer.java:331)
    16:25:37,437 INFO [STDOUT] at org.jboss.ejb.Container.invoke(Container.java
    :709)
    16:25:37,437 INFO [STDOUT] at sun.reflect.GeneratedMethodAccessor81.invoke(
    Unknown Source)
    16:25:37,437 INFO [STDOUT] at sun.reflect.DelegatingMethodAccessorImpl.invo
    ke(DelegatingMethodAccessorImpl.java:25)
    16:25:37,437 INFO [STDOUT] at java.lang.reflect.Method.invoke(Method.java:3
    24)
    16:25:37,437 INFO [STDOUT] at org.jboss.mx.server.ReflectedDispatcher.dispa
    tch(ReflectedDispatcher.java:60)
    16:25:37,437 INFO [STDOUT] at org.jboss.mx.server.Invocation.dispatch(Invoc
    ation.java:62)
    16:25:37,437 INFO [STDOUT] at org.jboss.mx.server.Invocation.dispatch(Invoc
    ation.java:54)
    16:25:37,437 INFO [STDOUT] at org.jboss.mx.server.Invocation.invoke(Invocat
    ion.java:82)
    16:25:37,437 INFO [STDOUT] at org.jboss.mx.server.AbstractMBeanInvoker.invo
    ke(AbstractMBeanInvoker.java:197)
    16:25:37,453 INFO [STDOUT] at org.jboss.mx.server.MBeanServerImpl.invoke(MB
    eanServerImpl.java:473)
    16:25:37,453 INFO [STDOUT] at org.jboss.invocation.local.LocalInvoker.invok
    e(LocalInvoker.java:97)
    16:25:37,453 INFO [STDOUT] at org.jboss.invocation.InvokerInterceptor.invok
    e(InvokerInterceptor.java:90)
    16:25:37,453 INFO [STDOUT] at org.jboss.proxy.TransactionInterceptor.invoke
    (TransactionInterceptor.java:46)
    16:25:37,453 INFO [STDOUT] at org.jboss.proxy.SecurityInterceptor.invoke(Se
    curityInterceptor.java:55)
    16:25:37,453 INFO [STDOUT] at org.jboss.proxy.ejb.StatelessSessionIntercept
    or.invoke(StatelessSessionInterceptor.java:100)
    16:25:37,453 INFO [STDOUT] at org.jboss.proxy.ClientContainer.invoke(Client
    Container.java:85)
    16:25:37,453 INFO [STDOUT] at $Proxy146.loadProcessArchive(Unknown Source)
    16:25:37,453 INFO [STDOUT] at com.collaxa.cube.engine.deployment.CubeProces
    sMonitorWork.run(CubeProcessMonitorWork.java:129)
    16:25:37,453 INFO [STDOUT] at oracle.tip.adapter.fw.jca.work.WorkerJob.go(W
    orkerJob.java:51)
    16:25:37,453 INFO [STDOUT] at oracle.tip.adapter.fw.common.ThreadPool.run(T
    hreadPool.java:267)
    16:25:37,453 INFO [STDOUT] at java.lang.Thread.run(Thread.java:534)
    16:25:37,453 INFO [STDOUT] <2007-05-11 16:25:37,453> <ERROR> <default.collaxa.c
    ube.engine.deployment> <CubeProcessMonitorWork::run> Error while loading process
    archive E:\OraBPELPM\domains\default\deploy\bpel_AboutTest_1.0.jar
    why?
    thanks

  • Unable to deploy a BPEL process with rules

    Hi All
    I created a very simple BPEL process and defined a business Rule in composite, that I call from within my BPEL process.
    I am however not able to deploy the project completely successfully.
    I am using JDEV 11g to build/deploy my projects on a SOA_Suite_11g. Note that I can deploy a project successfully if it does not have a business rule.
    This is what I see in the 'Deployment Log' tab:
    [01:49:17 PM] Deploying profile...
    [01:49:17 PM] Wrote SAR file to /Users/satinder/jdeveloper/mywork/ChapterTwo/FLThree/deploy/sca_FLThree_rev1.0.jar
    [01:49:17 PM] Deploying sca_FLThree_rev1.0.jar to soa_server1 [redunca.pvo.groundhog.com.au:8001]
    [01:49:17 PM] Processing sar=/Users/satinder/jdeveloper/mywork/ChapterTwo/FLThree/deploy/sca_FLThree_rev1.0.jar
    [01:49:17 PM] Adding sar file - /Users/satinder/jdeveloper/mywork/ChapterTwo/FLThree/deploy/sca_FLThree_rev1.0.jar
    [01:49:17 PM] Preparing to send HTTP request for deployment
    [01:49:17 PM] Creating HTTP connection to host:redunca.pvo.groundhog.com.au, port:8001
    [01:49:17 PM] Sending internal deployment descriptor
    [01:49:17 PM] Sending archive - sca_FLThree_rev1.0.jar
    [01:49:19 PM] Received HTTP response from the server, response code=500
    [01:49:19 PM] Error deploying archive sca_FLThree_rev1.0.jar to soa_server1 [redunca.pvo.groundhog.com.au:8001]
    [01:49:19 PM] HTTP error code returned [500]
    [01:49:19 PM] Error message from server:
    Error during composite deployment: oracle.fabric.common.FabricDeploymentException: oracle.fabric.common.FabricException: Error occurred during deployment of component: FLI to service engine: implementation.bpel, for composite: FLThree: ORABPEL-01010
    Process Generation Failed.
    failure to generate the BPEL process file "".
    Could not generate named BPEL process file. The exception reported was "/apps/oracle/ofm_11g/user_projects/domains/soa_dev_domain/deployed-composites/FLThree_rev1.0/sca_FLThree_rev1.0/198abebc-19d9-4df6-a712-2122b0b9730a/SCA-INF/FLI.lock (Too many open files)".
    Ensure that the file "" is a valid file to be generated.
    : Error occurred during deployment of component: FLI to service engine: implementation.bpel, for composite: FLThree: ORABPEL-01010
    Process Generation Failed.
    failure to generate the BPEL process file "".
    Could not generate named BPEL process file. The exception reported was "/apps/oracle/ofm_11g/user_projects/domains/soa_dev_domain/deployed-composites/FLThree_rev1.0/sca_FLThree_rev1.0/198abebc-19d9-4df6-a712-2122b0b9730a/SCA-INF/FLI.lock (Too many open files)".
    Ensure that the file "" is a valid file to be generated.
    [01:49:19 PM] Check server log for more details.
    [01:49:19 PM] #### Deployment incomplete. ####
    [01:49:19 PM] Error deploying archive file:/Users/satinder/jdeveloper/mywork/ChapterTwo/FLThree/deploy/sca_FLThree_rev1.0.jar
    (oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
    Any ideas..
    Thanks

    "Too many open files" issue is most likely because of a (few) Sun JDK6 bug(s). These bugs may not even get fixed in JDK6. It could hit at runtime or compile time depending on the number of jar files getting used and/or a few other variations around the use of file descriptors at a time by the JDK/JRE. One can use "lsof -p <pid>" command on Linux and see how the File Descriptors are growing when this issue is seen. E.g. use the pid of junit java process and not the main Ant java process if you want to debug at runtime. For compile time, grep on the compiler process.
    Increasing the limit of file descriptors is used as a workaround.
    How to increase per-process per-user file descriptor limit on your Linux hosted box:
    Using "limit" (csh) or "ulimit" (bash) command find out what is the value of "descriptors". As a root user (use sudo) edit /etc/security/limits.conf file.
    Close your x term and re-open (or re-connect your NX client) for this change to take effect. System re-start should not be required. If you are not able to increase the limit for some reason using these steps, try a few other things like re-starting your VNC server (or something similar), re-start your Linux box.

  • Unable to get the BPEL process in esb console

    Hi,
    I am facing an issue with code generated using artifact generator in FP 2.4.
    When I deploy a Provider ABCS process(generated through artifcat generator), it does not appear in the BPEL system of my esb console because of which i am not able to create a routing service for that BPEL process in my ESB.
    I am able to find only those bpel processes in the esb console which are not generated through artifact generator.
    kindly suggest what can be done.

    Hi GPR,
    I assume there are no compilation errors and you are able to deloy the process successfully. Do you see any errors in the log file while deploying the process? You may want to check the $SOA_HOME/opmn/logs/default~oc4j_soa~xxx.log file.
    Do you see the process in BPEL Console and able to unit-test it?
    Regards
    Rohit

  • Unable to call a BPEL Process from ESB

    Has anyone worked on Oracle ESB ?
    I've implemented an ESB Scenario where, based on some value, either it should call one BPEL process otherwise it should call another BPEL Process. But, Routing Service is unable to call either of the service.
    Can anyone help me out?
    Thanks in Advance.
    Regards

    I am able to call the bpel processes from the bpel console. I tried to use the TCP Packet Monitor but it shows waiting for connection and doesn't turn up. I checked the port number. The local server port is correct but I dont know how to check the listener port for it i.e. by default showing 1234.
    I tried to test my esb through em as a webservice but it shows the following exception after input:
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Header/><env:Body><env:Fault xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>env:Server</faultcode><faultstring>oracle.tip.esb.server.common.exceptions.BusinessEventRetriableException: An unhandled exception has been thrown in the ESB system. The exception reported is: "oracle.tip.esb.server.common.exceptions.BusinessEventFatalException: An unhandled exception has been thrown in the ESB system. The exception reported is: "java.lang.Exception: Failed to create "ejb/collaxa/system/DeliveryBean" bean; exception reported is: "javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException: Not authorized; nested exception is:
         javax.naming.AuthenticationException: Not authorized [Root exception is javax.naming.AuthenticationException: Not authorized]
         at com.evermind.server.rmi.RMIClientContext.lookup(RMIClientContext.java:64)
         at javax.naming.InitialContext.lookup(InitialContext.java:351)
         at com.oracle.bpel.client.util.BeanRegistry.lookupDeliveryBean(BeanRegistry.java:279)
         at com.oracle.bpel.client.delivery.DeliveryService.getDeliveryBean(DeliveryService.java:250)
         at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:83)
         at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:67)
         at oracle.tip.esb.server.service.impl.bpel.BPELService.processBusinessEvent(Unknown Source)
         at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(Unknown Source)
         at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source)
         at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source)
         at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(Unknown Source)
         at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(Unknown Source)
         at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(Unknown Source)
         at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(Unknown Source)
         at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(Unknown Source)
         at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(Unknown Source)
         at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(Unknown Source)
         at oracle.tip.esb.server.dispatch.BusinessEvent.raise(Unknown Source)
         at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.raiseEvent(Unknown Source)
         at oracle.tip.esb.server.service.impl.soap.EventOracleSoapProvider.processMessage(Unknown Source)
         at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:869)
         at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
         at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:460)
         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: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:303)
         at java.lang.Thread.run(Thread.java:595)
    I've setup the trackable fields also but trackable data showed me no data. When I checked the validate check box, it has shown me error in first stage i.e. in file adapter itself.
    I don't know what's the problem?
    Please help as I am struggling with this.
    Thanks & Regards

  • Problem deploying bpel process to oc4j_soa container on separate server

    Hi - after searching for a solution both here and on Metalink for some time, I've reached the point where I think I need to post my problem:
    (This might be an application server/BPEL related issue and perhaps more relevant there than JDeveloper. If so, my apologies in advance.)
    On client; Windows XP with JDeveloper 10.1.3.4.0, on server Windows Server 2003 with Oracle SOAsuite 10.1.3.
    Created a very simple bpel process (ftp get a remote file -> write locally) that I want to deploy on the dedicated SOA-server.
    From JDeveloper, the "Application Server and ESB Server connections checks out fine. But the "BPEL Process Manager Server" check failes with the error:
    "BPEL Identity Service: Failed" - Details: "oracle.xml.parser.v2.XMLParseException:Whitespace required."
    I have not found any postings/info on the "Whitespace required" error anywhere... mighty strange....
    I'm therefore unable to use the BPEL Process Deployer, it states that "Server Mode: Server is unreachable".
    I've triple-checked all ports etc. The Integration Server Connection is using port 80.
    I'm able to access and open the BPELConsole (& EM & ESB) on the server from my JDeveloper workstation.
    A "opmnctl status -l" on the SOA-server gives:
    Processes in Instance: SOAProd.aresrv136.gard.local
    ---------------------------------+--------------------+---------+----------+------------+----------+-----------+------
    ias-component | process-type | pid | status | uid | memused | uptime | ports
    ---------------------------------+--------------------+---------+----------+------------+----------+-----------+------
    ASG | ASG | N/A | Down | N/A | N/A | N/A | N/A
    OC4JGroup:default_group | OC4J:OC4JUDDI | 364 | Alive | 707857842 | 153388 | 17:33:58 | jms:12603,ajp:12503,rmis:12703,rmi:12403
    OC4JGroup:default_group | OC4J:oc4j_soa | 500 | Alive | 707857841 | 266220 | 17:33:58 | jms:12601,ajp:12502,rmis:12701,rmi:12401
    OC4JGroup:default_group | OC4J:home | 804 | Alive | 707857840 | 153080 | 17:33:58 | jms:12602,ajp:12501,rmis:12702,rmi:12402
    HTTP_Server | HTTP_Server | 2020 | Alive | 707857839 | 67188 | 17:33:30 | https1:443,http2:7200,http1:80
    I cannot find the "deploy_service" as a separate service on my server however. Only the hw_services are up and running, but it contains a "deploy" web module.
    Would be immensely grateful for any information that might help me further in solving this issue, as I'm rather stuck right now....
    Regards,
    -Haakon-

    Haakon,
    I think the BPEL forum is the better source to ask
    BPEL
    Frank

  • BPEL process deployment

    What is required to deploy a BPEL process on another machine (or oracle home)?
    Here is my current list in order, let me know if there is anything additional or if there are any short cuts/wizards to make doing this easier. Also if you don’t need to be able to recompile the program, are any of the steps (b – e) not needed / changed if you just copy over and manually deploy the jar file?
    a) Copy the workspace folder to the new machine/oracle home and then add it to the application navigator.
    b) Re-add or copy entries in the email/JMS/FTP adapter config files.
    c) Re-add task users. (Can there entries be copied from one file to the other?)
    d) Make sure all referenced local folders exist and are accessible.
    e) Make sure all referenced BPEL processes are deployed.
    This includes the User task services, they seem to be deployed when a user task is added but not when a BPEL process they include is deployed in a new environment.
    f) Compile/deploy the process.
    Thanks,
    Craig

    Hi Craig -
    Your list of steps will certainly work. However, as you suggest, you don't need to recompile the BPEL process on the new machine. You can just copy the jar (what we call the "BPEL suitcase" that is created when you compile the BPEL process. For more information on this, and the different mechanisms for deploying BPEL suitcases, see the technote at:
    http://www.oracle.com/technology/products/ias/bpel/htdocs/orabpel_technotes.tn002.html
    Regarding the user task services, these should just "do the right thing". If you are finding that you deploy a process to a new domain that uses the task service and the task service itself is not automatically deployed by the server, send us the steps to reproduce - this would be a bug (though your workaround of manually deploying the task service would be fine in the meantime).
    Beyond that, there are a few best practices that we have which may eliminate steps (c) and (d) in your list (task users and referenced local folders). We would recommend avoiding local folder references that go outside of the BPEL suitcase when possible and using URL references for things like XSDs. This way you can have a central repository that is available from all the pertinent servers.
    Alternatively, you can include the necessary files with your process in a higher level directory and have an Ant build.xml which copies them to the appropriate locations. We try to do this with our samples, so that there is a single directory (typically called xxxDemo, e.g. LoanFlowDemo) that has a master build.xml that builds all the sub-directories (which typically include a BPEL process, xxxFlow, a UI, dependent services, etc). See the samples in the orabpel\samples\demos directory for several examples of this approach that you may be able to leverage.
    Finally, regarding task users, I'm not sure if there is a simple mechanism for copying them over with our default developer install authentication. I'll check on this however - the question makes sense and we should both make this possible and ship an example where the appropriate users are created as part of the umbrella build.xml for a project. I suspect this will require a simple SQL script, but again I'll check. However, in many cases, again the best practice would be to use an LDAP or similar, globally accessible directory. Then any deployments which have access to the directory service would not require this additional step.
    Let me know if any of this doesn't make sense.
    Dave
    David Shaffer
    Dir Product Mgmt, Oracle BPEL Process Mgr
    [email protected]
    W: 650.506.1729
    http://otn.oracle.com/bpel

  • Extract BPEL process from the JAR file deployed to BPEL Server

    Hello All-
    We have a BPEL process deployed in our production environment but unfortunately we do not have a back-up copy in our test environment.
    I got the BPEL deployment JAR file from the production server but I am unable to extract the BPEL Process as well as the XSL file.
    I used WINRAR to extract but it was showing that the JAR file is not a valid archive. We need the prod deployed version of the XSL as well as the BPEL process for a change and we are unable to proceed.
    If anybody has faced similar kind of issue, please let me know how can it be resolved. Also please let me know if there are any tools which can extract the files.
    PLease note that we are on BPEL 10.1.2.0.2
    Appreciate your help and thanks in advance.
    Thanks,
    Dibya

    Hi Dibya
    jar -xvf <filename> will work as others said.
    However, please make sure you have another TEST/DEV Environment running in par with PROD.
    Always, suggested to test first on the TEST/DEV Env for applying any new patches/config changes...then appropriately migrate to actual PROD Environments.
    Also, always take a complete backup before you do some R&D on the SOA server.
    Regards
    A

  • Unable to invoke a EJB from a BPEL process

    I am unable to invoke a EJB from a BPEL process. Whenever I try to test it from the oracle EM, I get the below exception. I am using WebLogic 10.3.3, SOA suite 11.1.1.3 and JDev 11.1.1.3 .
    This is what I see from the EM....
    Non Recoverable System Fault :
    javaInterface attribute for the binding is missing or the inteface class is not available.
    Below is a part of the stack trace from the soa server log…
    Caused By: oracle.classloader.util.AnnotatedClassNotFoundException:
    Missing class: com.abc.GreetingEJBBean
    Dependent class: oracle.integration.platform.blocks.ejb.SDOEjbReferenceD
    elegateImpl
    Loader: sun.misc.Launcher$AppClassLoader@20929799
    Code-Source: /C:/Oracle_latest/Middleware/home_11gR1/Oracle_SOA1/soa
    /modules/oracle.soa.fabric_11.1.1/fabric-runtime.jar
    Configuration: /C:/Oracle_latest/Middleware/home_11gR1/Oracle_SOA1/soa
    /modules/oracle.soa.fabric_11.1.1/fabric-runtime.jar
    Piece of xml from the composite.xml
    <reference name="GreetingService"
    ui:wsdlLocation="http://123.45.218.140:7001/GreetingEJBBean/GreetingEJBBeanService?wsdl">
    <interface.wsdl interface="http://abc.com/#wsdl.interface(GreetingEJBBean)" />
    <binding.ejb uri="GreetingEJB-GreetingEJB-GreetingEJB"
    javaInterface="com.abc.GreetingEJB"/>
    </reference>
    Looks like its not able to find the javaInterface mentioned above.
    I have a simple EJB with one business method and a very simple BPEL process.
    @Stateless(name = "GreetingEJB", mappedName = "GreetingEJB-GreetingEJB-GreetingEJB")
    @WebService
    public class GreetingEJBBean implements GreetingEJB {
    public GreetingEJBBean() {
    public String greetUser(String name){
    return ("Hello " + name);
    Any help would be greatly appreciated.

    I haven't tried from a BPEL process, but I have had success (as in Lucas's blogs) of using services and references as EJB Java Interface. This is with EJB java interfaces solely of base types (i.e. String foo(String s)).
    At high level here's what I have noted so far:
    1. Per Lucas's blog, @javaInterface is not being added to the ejb.binding automatically but it's not clear to me when this is and is not required given that interface.java is specified for the reference or service. Would interface.java and @javaInterface ever be different? I've been adding @javaInterface manually anyways since Lucas is a smart guy and I'd rather avoid errors. :-)
    2. Dropping an EJB interface jar in SCA-INF/lib works, but I've had the problem that the JDeveloper SOA Plugin doesn't see those classes until I stop and restart JDeveloper. Until then, I'm confronted with the java->wsdl mapping error. I was sort of primed to figure this one out since I ran into similar issues with SOA SpringBean components.
    3. Dropping EJB interface source in SCA-INF/src is more reliable, because then I can build the project (i.e. create SCA-INF/classes) and the JDeveloper SOA Plugin seems to resolve these brand new classes immediately.
    4. I've tried to invoke an EJB java-interface reference with a slightly complicated java interface (a class parameter with some fields, one of which is an array of another class). The auto-generated WSDL doesn't look exactly right to me (but I'm new to JAXB). Mediator maps to it just fine and the project compiles and deploys normally but fails at runtime. I have not researched in depth. It's not clear to me from the documentation and release notes whether I should expect for it to work, or whether I should expect to have to create my own JAXB mapping. If the latter, I really need a good example!

  • Error compiling the BPEL classes while configuring custom approval process

    Hi,
    I get the below error, but unable to fix this. Any one who did face this issue please share your thoughts to overcome this.
    Error(45,34): Failed to compile bpel generated classes.
    failure to compile the generated BPEL classes for BPEL process "ApprovalProcess" of composite "default/SelfRegistrationApproval!1.0"
    The class path setting is incorrect.
    Ensure that the class path is set correctly. If this happens on the server side, verify that the custom classes or jars which this BPEL process is depending on are deployed correctly. Also verify that the run time is using the same release/version.
    Thanks,
    Bhaskar

    You need to keep all the custom jars at three places :
    1) Soa ext , and make sao extension jar by running ant
    2) Bpel classpath
    3) in your project as an external referrence

  • Unable to invoke an asynch Oracle BPEL process

    Im currently struggling to invoke an Oracle BPEL web service from another Oracle BPEL process.
    When creating the invoking process I pasted in the wsdl from the BPEL console to describe the invoked process rather than use the original wsdl generated by the tool.
    The wsdl is given below :
    At run time execution fails at the point where the invoking BPEL web service calls the first BPEL process, the error is a binding fault with desc : unable to find available port.
    <?xml version="1.0" encoding="UTF-8" ?>
    - <definitions name="Supplier" targetNamespace="http://xmlns.oracle.com/Supplier" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://xmlns.oracle.com/Supplier" xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing" xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:client="http://xmlns.oracle.com/Supplier">
    - <types>
    - <schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://xmlns.oracle.com/Supplier" xmlns="http://www.w3.org/2001/XMLSchema">
    - <element name="SupplierProcessRequest">
    - <complexType>
    - <sequence>
    <element name="input" type="string" />
    </sequence>
    </complexType>
    </element>
    - <element name="SupplierProcessResponse">
    - <complexType>
    - <sequence>
    <element name="result" type="string" />
    </sequence>
    </complexType>
    </element>
    </schema>
    - <schema xmlns="http://www.w3.org/2001/XMLSchema">
    <import namespace="http://schemas.xmlsoap.org/ws/2003/03/addressing" schemaLocation="http://pc1520952:9700/orabpel/xmllib/ws-addressing.xsd" />
    </schema>
    </types>
    - <message name="ReplyToHeader">
    <part name="ReplyTo" element="wsa:ReplyTo" />
    </message>
    - <message name="MessageIDHeader">
    <part name="MessageID" element="wsa:MessageID" />
    </message>
    - <message name="SupplierRequestMessage">
    <part name="payload" element="tns:SupplierProcessRequest" />
    </message>
    - <message name="SupplierResponseMessage">
    <part name="payload" element="tns:SupplierProcessResponse" />
    </message>
    - <message name="RelatesToHeader">
    <part name="RelatesTo" element="wsa:RelatesTo" />
    </message>
    - <portType name="Supplier">
    - <operation name="initiate">
    <input message="tns:SupplierRequestMessage" />
    </operation>
    </portType>
    - <portType name="SupplierCallback">
    - <operation name="onResult">
    <input message="tns:SupplierResponseMessage" />
    </operation>
    </portType>
    - <binding name="SupplierCallbackBinding" type="tns:SupplierCallback">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
    - <operation name="onResult">
    <soap:operation style="document" soapAction="onResult" />
    - <input>
    <soap:header message="tns:RelatesToHeader" part="RelatesTo" use="literal" encodingStyle="" />
    <soap:body use="literal" />
    </input>
    </operation>
    </binding>
    - <binding name="SupplierBinding" type="tns:Supplier">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
    - <operation name="initiate">
    <soap:operation style="document" soapAction="initiate" />
    - <input>
    <soap:header message="tns:ReplyToHeader" part="ReplyTo" use="literal" encodingStyle="" />
    <soap:header message="tns:MessageIDHeader" part="MessageID" use="literal" encodingStyle="" />
    <soap:body use="literal" />
    </input>
    </operation>
    </binding>
    - <service name="Supplier">
    - <port name="SupplierPort" binding="tns:SupplierBinding">
    <soap:address location="http://pc1520952:9700/orabpel/default/Supplier/1.0" />
    </port>
    </service>
    - <service name="SupplierCallbackService">
    - <port name="SupplierCallbackPort" binding="tns:SupplierCallbackBinding">
    <soap:address location="http://set.by.caller" />
    </port>
    </service>
    - <plnk:partnerLinkType name="Supplier">
    - <plnk:role name="SupplierRequester">
    <plnk:portType name="tns:SupplierCallback" />
    </plnk:role>
    - <plnk:role name="SupplierProvider">
    <plnk:portType name="tns:Supplier" />
    </plnk:role>
    </plnk:partnerLinkType>
    </definitions>

    I have got the same error.
    and if you look at your wsdl generated in xmlSpy(or something to check xml),
    you will see that the xml is not Valid!!!!
    Here is the fault by no targetNameSpace is in it(like in the first schema)
    <schema xmlns="http://www.w3.org/2001/XMLSchema">
    <import namespace="http://schemas.xmlsoap.org/ws/2003/03/addressing" schemaLocation="http://pc1520952:9700/orabpel/xmllib/ws-addressing.xsd" />
    </schema>
    This error is generated when trying to invoke a asynchronous BPEL deploy before in the engine.
    Error can be comprehensive is the Wsdl is not valid...
    When I deploy a asynchronous BPEL workflow in BPEL workflow 10.1.2, the compiler add <import namespace="http://schemas.xmlsoap.org/ws/2003/03/addressing" schemaLocation="http://$server-url$:9700/orabpel/xmllib/ws-addressing.xsd" />
    in the wsdl and is not valid.
    Anyone from the BPEL team know this , and find a solution???
    Thanks.

  • Can't invoke WS from BPEL process: Unable to locate activated endpoint

    I have a simple Calculator Web Service deployed on Glassfish, that I can access with any kind of SOAP client (e.g. soapUI). I have then created a BPEL process that invokes this external Web Service (which happens to run on the same Glassfish server, but that's largely irrelevant I suppose). I can instantiate and invoke the BPEL process (I've tried it with a dummy assign earlier just to make sure, and it runs successfully), but the BPEL process doesn't seem to be able to locate the external Web Service. I get the following fault:
    <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
    <S:Body>
    <ns2:Fault xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope">
    <faultcode>ns2:Server</faultcode>
    <faultstring>javax.jbi.messaging.MessagingException: Unable to locate activated endpoint for service connection {SigningCompositeApp}CalculatorService SignedCalculatorService.</faultstring>
    <detail>
    <ns2:exception class="java.lang.RuntimeException" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false" xmlns:ns2="http://jax-ws.dev.java.net/">
    <message>javax.jbi.messaging.MessagingException: Unable to locate activated endpoint for service connection {SigningCompositeApp}CalculatorService SignedCalculatorService.</message>
    <ns2:stackTrace>
    <ns2:frame class="com.sun.xml.ws.server.provider.AsyncProviderInvokerTube$AsyncProviderCallbackImpl" file="AsyncProviderInvokerTube.java" line="114" method="sendError"/>
    <ns2:frame class="com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider" file="AsyncJBIProvider.java" line="136" method="invoke"/>
    <ns2:frame class="com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider" file="AsyncJBIProvider.java" line="94" method="invoke"/>
    <ns2:frame class="sun.reflect.GeneratedMethodAccessor305" line="unknown" method="invoke"/>
    <ns2:frame class="sun.reflect.DelegatingMethodAccessorImpl" file="DelegatingMethodAccessorImpl.java" line="25" method="invoke"/>
    <ns2:frame class="java.lang.reflect.Method" file="Method.java" line="597" method="invoke"/>
    <ns2:frame class="com.sun.jbi.httpsoapbc.jaxwssupport.InvokerImpl" file="InvokerImpl.java" line="72" method="invoke"/>
    <ns2:frame class="com.sun.xml.ws.api.server.Invoker" file="Invoker.java" line="115" method="invokeAsyncProvider"/>
    <ns2:frame class="com.sun.xml.ws.server.InvokerTube$2" file="InvokerTube.java" line="166" method="invokeAsyncProvider"/>
    <ns2:frame class="com.sun.xml.ws.server.provider.AsyncProviderInvokerTube" file="AsyncProviderInvokerTube.java" line="80" method="processRequest"/>
    <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="595" method="__doRun"/>
    <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="554" method="_doRun"/>
    <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="539" method="doRun"/>
    <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="388" method="run"/>
    <ns2:frame class="java.util.concurrent.ThreadPoolExecutor$Worker" file="ThreadPoolExecutor.java" line="885" method="runTask"/>
    <ns2:frame class="java.util.concurrent.ThreadPoolExecutor$Worker" file="ThreadPoolExecutor.java" line="907" method="run"/>
    <ns2:frame class="java.lang.Thread" file="Thread.java" line="619" method="run"/>
    </ns2:stackTrace>
    <ns2:cause class="javax.jbi.messaging.MessagingException" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false">
    <message>Unable to locate activated endpoint for service connection {SigningCompositeApp}CalculatorService SignedCalculatorService.</message>
    <ns2:stackTrace>
    <ns2:frame class="com.sun.jbi.messaging.MessageService" file="MessageService.java" line="492" method="addressExchange"/>
    <ns2:frame class="com.sun.jbi.messaging.MessageService" file="MessageService.java" line="326" method="doExchange"/>
    <ns2:frame class="com.sun.jbi.messaging.DeliveryChannelImpl" file="DeliveryChannelImpl.java" line="209" method="send"/>
    <ns2:frame class="com.sun.jbi.httpsoapbc.InboundMessageProcessor" file="InboundMessageProcessor.java" line="268" method="sendInOut"/>
    <ns2:frame class="com.sun.jbi.httpsoapbc.InboundMessageProcessor" file="InboundMessageProcessor.java" line="479" method="executeSOAP"/>
    <ns2:frame class="com.sun.jbi.httpsoapbc.InboundMessageProcessor" file="InboundMessageProcessor.java" line="215" method="execute"/>
    <ns2:frame class="com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider" file="AsyncJBIProvider.java" line="134" method="invoke"/>
    <ns2:frame class="com.sun.jbi.httpsoapbc.jaxwssupport.AsyncJBIProvider" file="AsyncJBIProvider.java" line="94" method="invoke"/>
    <ns2:frame class="sun.reflect.GeneratedMethodAccessor305" line="unknown" method="invoke"/>
    <ns2:frame class="sun.reflect.DelegatingMethodAccessorImpl" file="DelegatingMethodAccessorImpl.java" line="25" method="invoke"/>
    <ns2:frame class="java.lang.reflect.Method" file="Method.java" line="597" method="invoke"/>
    <ns2:frame class="com.sun.jbi.httpsoapbc.jaxwssupport.InvokerImpl" file="InvokerImpl.java" line="72" method="invoke"/>
    <ns2:frame class="com.sun.xml.ws.api.server.Invoker" file="Invoker.java" line="115" method="invokeAsyncProvider"/>
    <ns2:frame class="com.sun.xml.ws.server.InvokerTube$2" file="InvokerTube.java" line="166" method="invokeAsyncProvider"/>
    <ns2:frame class="com.sun.xml.ws.server.provider.AsyncProviderInvokerTube" file="AsyncProviderInvokerTube.java" line="80" method="processRequest"/>
    <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="595" method="__doRun"/>
    <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="554" method="_doRun"/>
    <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="539" method="doRun"/>
    <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="388" method="run"/>
    <ns2:frame class="java.util.concurrent.ThreadPoolExecutor$Worker" file="ThreadPoolExecutor.java" line="885" method="runTask"/>
    <ns2:frame class="java.util.concurrent.ThreadPoolExecutor$Worker" file="ThreadPoolExecutor.java" line="907" method="run"/>
    <ns2:frame class="java.lang.Thread" file="Thread.java" line="619" method="run"/>
    </ns2:stackTrace>
    </ns2:cause>
    </ns2:exception>
    </detail>
    </ns2:Fault>
    </S:Body>
    </S:Envelope>
    For good measure, here's the WSDL (and partner link defn) for the external WS:
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions name="CalculatorWSExternal" targetNamespace="http://j2ee.netbeans.org/wsdl/CalculatorWSExternal"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://j2ee.netbeans.org/wsdl/CalculatorWSExternal" xmlns:ns="http://calculator.me.org/" xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
    <types>
    <xsd:schema targetNamespace="http://j2ee.netbeans.org/wsdl/CalculatorWSExternal">
    <xsd:import namespace="http://calculator.me.org/" schemaLocation="CalculatorWSService.xsd"/>
    </xsd:schema>
    </types>
    <message name="addRequest">
    <part name="add" element="ns:add"/>
    </message>
    <message name="addReply">
    <part name="addResponse" element="ns:addResponse"/>
    </message>
    <portType name="CalculatorWSExternalPortType">
    <operation name="add">
    <input name="input1" message="tns:addRequest"/>
    <output name="output1" message="tns:addReply"/>
    </operation>
    </portType>
    <binding name="CalculatorWSExternalBinding" type="tns:CalculatorWSExternalPortType">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="add">
    <soap:operation/>
    <input name="input1">
    <soap:body use="literal"/>
    </input>
    <output name="output1">
    <soap:body use="literal"/>
    </output>
    </operation>
    </binding>
    <service name="CalculatorWSExternalService">
    <port name="CalculatorWSExternalPort" binding="tns:CalculatorWSExternalBinding">
    <soap:address location="http://localhost:8080/CalculatorApp/CalculatorWSService"/>
    </port>
    </service>
    <plnk:partnerLinkType name="CalculatorWSExternal1">
    <!-- A partner link type is automatically generated when a new port type is added. Partner link types are used by BPEL processes.
    In a BPEL process, a partner link represents the interaction between the BPEL process and a partner service. Each partner link is associated with a partner link type.
    A partner link type characterizes the conversational relationship between two services. The partner link type can have one or two roles.-->
    <plnk:role name="CalculatorWSExternalPortTypeRole" portType="tns:CalculatorWSExternalPortType"/>
    </plnk:partnerLinkType>
    </definitions>
    Any help? I've seen someone post a similar problem on the forum at http://forum.java.sun.com/thread.jspa?threadID=5273187&messageID=10157363#10157363
    but I haven't seen any answers. Thanks!
    Edited by: tboubez on Jun 9, 2008 10:56 AM

    Check the ports of Web services and those of BPEL, as Hambo have different communication ports.
    Normally Webservices point to the port 8080 and BPEL to 18181 or 9084.
    Check and I accounts.
    Greetings.

  • Compilation error while deploying my BPEL process : ORABPEL-05215

    Hi,
    I have created a BPEL process and when I try to deploy it, am getting the following error :
    BUILD FAILED
    D:\SoftWs\JDeveloper\jdev\mywork\AIASamples\CreateCustomerPartyPortalProvABCSImpl\build.xml:79: A problem occured while connecting to server "ple-jgau.us.oracle.com" using port "7777": bpel_CreateCustomerPartyPortalProvABCSImpl_1.0.jar failed to deploy. Exception message is: ORABPEL-05215
    Error while loading process.
    The process domain encountered the following errors while loading the process "CreateCustomerPartyPortalProvABCSImpl" (revision "1.0"): Failed to compile classes.
    Failed to compile the generated BPEL classes for "CreateCustomerPartyPortalProvABCSImpl"
    If you have installed a patch to the server, please check that the bpelcClasspath domain property includes the patch classes.
    at com.collaxa.cube.engine.deployment.CubeProcessHolder.bind(CubeProcessHolder.java:285)
    Whereas, am not getting any error when I compiled the same code [I get two warnings regarding incompatible assignment of variables].
    Please help me out.
    Thanks in advance,
    Senthil.
    Message was edited by:
    emSenthil

    Hi
    I have similar problem. When I compiling process I don't have any errors only when I want to deploy see statement like below. Do You have any suggestions how to fix it?
    Thanks
    BUILD FAILED
    C:\bpel_ROTelcoNewOrder_1.0new\build.xml:79: A problem occured while connecting to server "192.168.10.205" using port "80": bpel_ROTelcoNewOrder_1.0.jar failed to deploy. Exception message is: ORABPEL-05215
    Error while loading process.
    The process domain encountered the following errors while loading the process "ROTelcoNewOrder" (revision "1.0"): BPEL validation failed.
    BPEL source validation failed, the errors are:
    [Error ORABPEL-10007]: unresolved messageType
    [Description]: in line 71 of "D:\product\10.1.3.1\OracleAS_5\bpel\domains\default\tmp\.bpel_ROTelcoNewOrder_1.0_d7fdf89a9fb1b5de9f664c2e4966239a.tmp\ROTelcoNewOrder.bpel", WSDL messageType "{urn:oracle.enterprise.crm.rf.service.InstalledProduct}UpdateInstalledProductRequest.V1" of variable "InvokeUpdateInstalledProduct_UpdateInstalledProduct_InputVariable" is not defined in any of the WSDL files.
    [Potential fix]: Make sure the WSDL messageType "{urn:oracle.enterprise.crm.rf.service.InstalledProduct}UpdateInstalledProductRequest.V1" is defined in one of the WSDLs referenced by the deployment descriptor.
    [Error ORABPEL-10007]: unresolved messageType
    [Description]: in line 72 of "D:\product\10.1.3.1\OracleAS_5\bpel\domains\default\tmp\.bpel_ROTelcoNewOrder_1.0_d7fdf89a9fb1b5de9f664c2e4966239a.tmp\ROTelcoNewOrder.bpel", WSDL messageType "{urn:oracle.enterprise.crm.rf.service.InstalledProduct}InstalledProductUpdateResponse.V1" of variable "InvokeUpdateInstalledProduct_UpdateInstalledProduct_OutputVariable" is not defined in any of the WSDL files.
    [Potential fix]: Make sure the WSDL messageType "{urn:oracle.enterprise.crm.rf.service.InstalledProduct}InstalledProductUpdateResponse.V1" is defined in one of the WSDLs referenced by the deployment descriptor.
    [Error ORABPEL-10007]: unresolved messageType
    [Description]: in line 73 of "D:\product\10.1.3.1\OracleAS_5\bpel\domains\default\tmp\.bpel_ROTelcoNewOrder_1.0_d7fdf89a9fb1b5de9f664c2e4966239a.tmp\ROTelcoNewOrder.bpel", WSDL messageType "{urn:oracle.enterprise.crm.order.service.Order}NotifyOrderShipment.VERSION_1" of variable "InvokeOrderNotify_NotifyOrderShipment_InputVariable" is not defined in any of the WSDL files.
    [Potential fix]: Make sure the WSDL messageType "{urn:oracle.enterprise.crm.order.service.Order}NotifyOrderShipment.VERSION_1" is defined in one of the WSDLs referenced by the deployment descriptor.
    [Error ORABPEL-10007]: unresolved messageType
    [Description]: in line 79 of "D:\product\10.1.3.1\OracleAS_5\bpel\domains\default\tmp\.bpel_ROTelcoNewOrder_1.0_d7fdf89a9fb1b5de9f664c2e4966239a.tmp\ROTelcoNewOrder.bpel", WSDL messageType "{urn:oracle.enterprise.crm.order.service.Order}OrderCompletionRequest.V1" of variable "InvokeOrderCompletion_CompleteOrder_InputVariable" is not defined in any of the WSDL files.
    [Potential fix]: Make sure the WSDL messageType "{urn:oracle.enterprise.crm.order.service.Order}OrderCompletionRequest.V1" is defined in one of the WSDLs referenced by the deployment descriptor.
    [Error ORABPEL-10007]: unresolved messageType
    [Description]: in line 80 of "D:\product\10.1.3.1\OracleAS_5\bpel\domains\default\tmp\.bpel_ROTelcoNewOrder_1.0_d7fdf89a9fb1b5de9f664c2e4966239a.tmp\ROTelcoNewOrder.bpel", WSDL messageType "{urn:oracle.enterprise.crm.order.service.Order}OrderCompletionResponse.V1" of variable "InvokeOrderCompletion_CompleteOrder_OutputVariable" is not defined in any of the WSDL files.
    [Potential fix]: Make sure the WSDL messageType "{urn:oracle.enterprise.crm.order.service.Order}OrderCompletionResponse.V1" is defined in one of the WSDLs referenced by the deployment descriptor.
    [Error ORABPEL-10007]: unresolved messageType
    [Description]: in line 91 of "D:\product\10.1.3.1\OracleAS_5\bpel\domains\default\tmp\.bpel_ROTelcoNewOrder_1.0_d7fdf89a9fb1b5de9f664c2e4966239a.tmp\ROTelcoNewOrder.bpel", WSDL messageType "{urn:oracle.enterprise.crm.rf.service.InstalledProduct}UpdateInstalledProductRequest.V1" of variable "InvokeUpdateIPStatus_UpdateInstalledProduct_InputVariable" is not defined in any of the WSDL files.
    [Potential fix]: Make sure the WSDL messageType "{urn:oracle.enterprise.crm.rf.service.InstalledProduct}UpdateInstalledProductRequest.V1" is defined in one of the WSDLs referenced by the deployment descriptor.
    [Error ORABPEL-10007]: unresolved messageType
    [Description]: in line 92 of "D:\product\10.1.3.1\OracleAS_5\bpel\domains\default\tmp\.bpel_ROTelcoNewOrder_1.0_d7fdf89a9fb1b5de9f664c2e4966239a.tmp\ROTelcoNewOrder.bpel", WSDL messageType "{urn:oracle.enterprise.crm.rf.service.InstalledProduct}InstalledProductUpdateResponse.V1" of variable "InvokeUpdateIPStatus_UpdateInstalledProduct_OutputVariable" is not defined in any of the WSDL files.
    [Potential fix]: Make sure the WSDL messageType "{urn:oracle.enterprise.crm.rf.service.InstalledProduct}InstalledProductUpdateResponse.V1" is defined in one of the WSDLs referenced by the deployment descriptor.
    [Error ORABPEL-10007]: unresolved messageType
    [Description]: in line 93 of "D:\product\10.1.3.1\OracleAS_5\bpel\domains\default\tmp\.bpel_ROTelcoNewOrder_1.0_d7fdf89a9fb1b5de9f664c2e4966239a.tmp\ROTelcoNewOrder.bpel", WSDL messageType "{urn:oracle.enterprise.crm.rf.service.InstalledProduct}GetInstalledProductRequest.V1" of variable "InvokeGetIP_GetInstalledProduct_InputVariable" is not defined in any of the WSDL files.
    [Potential fix]: Make sure the WSDL messageType "{urn:oracle.enterprise.crm.rf.service.InstalledProduct}GetInstalledProductRequest.V1" is defined in one of the WSDLs referenced by the deployment descriptor.
    [Error ORABPEL-10007]: unresolved messageType
    [Description]: in line 94 of "D:\product\10.1.3.1\OracleAS_5\bpel\domains\default\tmp\.bpel_ROTelcoNewOrder_1.0_d7fdf89a9fb1b5de9f664c2e4966239a.tmp\ROTelcoNewOrder.bpel", WSDL messageType "{urn:oracle.enterprise.crm.rf.service.InstalledProduct}GetInstalledProductResponse.V1" of variable "InvokeGetIP_GetInstalledProduct_OutputVariable" is not defined in any of the WSDL files.
    [Potential fix]: Make sure the WSDL messageType "{urn:oracle.enterprise.crm.rf.service.InstalledProduct}GetInstalledProductResponse.V1" is defined in one of the WSDLs referenced by the deployment descriptor.
    [Error ORABPEL-10007]: unresolved messageType
    [Description]: in line 95 of "D:\product\10.1.3.1\OracleAS_5\bpel\domains\default\tmp\.bpel_ROTelcoNewOrder_1.0_d7fdf89a9fb1b5de9f664c2e4966239a.tmp\ROTelcoNewOrder.bpel", WSDL messageType "{urn:oracle.enterprise.crm.rf.service.InstalledProduct}UpdateInstalledProductRequest.V1" of variable "VariableUpdateIPStatusInputVariable" is not defined in any of the WSDL files.
    [Potential fix]: Make sure the WSDL messageType "{urn:oracle.enterprise.crm.rf.service.InstalledProduct}UpdateInstalledProductRequest.V1" is defined in one of the WSDLs referenced by the deployment descriptor.
    [Error ORABPEL-10017]: unresolved operation
    [Description]: in line 963 of "D:\product\10.1.3.1\OracleAS_5\bpel\domains\default\tmp\.bpel_ROTelcoNewOrder_1.0_d7fdf89a9fb1b5de9f664c2e4966239a.tmp\ROTelcoNewOrder.bpel", operation "UpdateInstalledProduct" is not defined in portType "{urn:oracle.enterprise.crm.rf.service.InstalledProduct}RF_INST_PRODUCT_PortType" of <invoke> "InvokeUpdateInstalledProduct".
    [Potential fix]: Make sure the operation "UpdateInstalledProduct" is defined in portType "{urn:oracle.enterprise.crm.rf.service.InstalledProduct}RF_INST_PRODUCT_PortType" who      is defined in WSDL "http://192.168.10.203:8020/PSIGW/PeopleSoftServiceListeningConnector/RF_INST_PRODUCT.1.wsdl".
    [Error ORABPEL-10017]: unresolved operation
    [Description]: in line 1008 of "D:\product\10.1.3.1\OracleAS_5\bpel\domains\default\tmp\.bpel_ROTelcoNewOrder_1.0_d7fdf89a9fb1b5de9f664c2e4966239a.tmp\ROTelcoNewOrder.bpel", operation "NotifyOrderShipment" is not defined in portType "{urn:oracle.enterprise.crm.order.service.Order}RO_ORDER_PortType" of <invoke> "InvokeOrderNotify".
    [Potential fix]: Make sure the operation "NotifyOrderShipment" is defined in portType "{urn:oracle.enterprise.crm.order.service.Order}RO_ORDER_PortType" who      is defined in WSDL "http://192.168.10.203:8020/PSIGW/PeopleSoftServiceListeningConnector/RO_ORDER.1.wsdl".
    [Error ORABPEL-10007]: unresolved messageType
    [Description]: in line 1157 of "D:\product\10.1.3.1\OracleAS_5\bpel\domains\default\tmp\.bpel_ROTelcoNewOrder_1.0_d7fdf89a9fb1b5de9f664c2e4966239a.tmp\ROTelcoNewOrder.bpel", WSDL messageType "{urn:oracle.enterprise.crm.order.service.Order}RelateServicesToSIMContainer.V1" of variable "InvokeRelateServicesToSIM_RelateServiceToSIM_InputVariable" is not defined in any of the WSDL files.
    [Potential fix]: Make sure the WSDL messageType "{urn:oracle.enterprise.crm.order.service.Order}RelateServicesToSIMContainer.V1" is defined in one of the WSDLs referenced by the deployment descriptor.
    [Error ORABPEL-10007]: unresolved messageType
    [Description]: in line 1158 of "D:\product\10.1.3.1\OracleAS_5\bpel\domains\default\tmp\.bpel_ROTelcoNewOrder_1.0_d7fdf89a9fb1b5de9f664c2e4966239a.tmp\ROTelcoNewOrder.bpel", WSDL messageType "{urn:oracle.enterprise.crm.order.service.Order}RelateServicesToSIMResponse.V1" of variable "InvokeRelateServicesToSIM_RelateServiceToSIM_OutputVariable" is not defined in any of the WSDL files.
    [Potential fix]: Make sure the WSDL messageType "{urn:oracle.enterprise.crm.order.service.Order}RelateServicesToSIMResponse.V1" is defined in one of the WSDLs referenced by the deployment descriptor.
    [Error ORABPEL-10017]: unresolved operation
    [Description]: in line 1186 of "D:\product\10.1.3.1\OracleAS_5\bpel\domains\default\tmp\.bpel_ROTelcoNewOrder_1.0_d7fdf89a9fb1b5de9f664c2e4966239a.tmp\ROTelcoNewOrder.bpel", operation "RelateServiceToSIM" is not defined in portType "{urn:oracle.enterprise.crm.order.service.Order}RO_ORDER_PortType" of <invoke> "InvokeRelateServicesToSIM".
    [Potential fix]: Make sure the operation "RelateServiceToSIM" is defined in portType "{urn:oracle.enterprise.crm.order.service.Order}RO_ORDER_PortType" who      is defined in WSDL "http://192.168.10.203:8020/PSIGW/PeopleSoftServiceListeningConnector/RO_ORDER.1.wsdl".
    [Error ORABPEL-10017]: unresolved operation
    [Description]: in line 1747 of "D:\product\10.1.3.1\OracleAS_5\bpel\domains\default\tmp\.bpel_ROTelcoNewOrder_1.0_d7fdf89a9fb1b5de9f664c2e4966239a.tmp\ROTelcoNewOrder.bpel", operation "CompleteOrder" is not defined in portType "{urn:oracle.enterprise.crm.order.service.Order}RO_ORDER_PortType" of <invoke> "InvokeOrderCompletion".
    [Potential fix]: Make sure the operation "CompleteOrder" is defined in portType "{urn:oracle.enterprise.crm.order.service.Order}RO_ORDER_PortType" who      is defined in WSDL "http://192.168.10.203:8020/PSIGW/PeopleSoftServiceListeningConnector/RO_ORDER.1.wsdl".
    [Error ORABPEL-10017]: unresolved operation
    [Description]: in line 1947 of "D:\product\10.1.3.1\OracleAS_5\bpel\domains\default\tmp\.bpel_ROTelcoNewOrder_1.0_d7fdf89a9fb1b5de9f664c2e4966239a.tmp\ROTelcoNewOrder.bpel", operation "GetInstalledProduct" is not defined in portType "{urn:oracle.enterprise.crm.rf.service.InstalledProduct}RF_INST_PRODUCT_PortType" of <invoke> "InvokeGetIP".
    [Potential fix]: Make sure the operation "GetInstalledProduct" is defined in portType "{urn:oracle.enterprise.crm.rf.service.InstalledProduct}RF_INST_PRODUCT_PortType" who      is defined in WSDL "http://192.168.10.203:8020/PSIGW/PeopleSoftServiceListeningConnector/RF_INST_PRODUCT.1.wsdl".
    [Error ORABPEL-10017]: unresolved operation
    [Description]: in line 1964 of "D:\product\10.1.3.1\OracleAS_5\bpel\domains\default\tmp\.bpel_ROTelcoNewOrder_1.0_d7fdf89a9fb1b5de9f664c2e4966239a.tmp\ROTelcoNewOrder.bpel", operation "UpdateInstalledProduct" is not defined in portType "{urn:oracle.enterprise.crm.rf.service.InstalledProduct}RF_INST_PRODUCT_PortType" of <invoke> "InvokeUpdateIPStatus".
    [Potential fix]: Make sure the operation "UpdateInstalledProduct" is defined in portType "{urn:oracle.enterprise.crm.rf.service.InstalledProduct}RF_INST_PRODUCT_PortType" who      is defined in WSDL "http://192.168.10.203:8020/PSIGW/PeopleSoftServiceListeningConnector/RF_INST_PRODUCT.1.wsdl".
    If you have installed a patch to the server, please check that the bpelcClasspath domain property includes the patch classes.
    at com.collaxa.cube.engine.deployment.CubeProcessHolder.bind(CubeProcessHolder.java:285)
    at com.collaxa.cube.engine.deployment.DeploymentManager.deployProcess(DeploymentManager.java:804)
    at com.collaxa.cube.engine.deployment.DeploymentManager.deploySuitcase(DeploymentManager.java:670)
    at com.collaxa.cube.ejb.impl.BPELDomainManagerBean.deploySuitcase(BPELDomainManagerBean.java:445)
    at sun.reflect.GeneratedMethodAccessor91.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
    at com.evermind.server.ThreadState.runAs(ThreadState.java:620)
    at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
    at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
    at DomainManagerBean_RemoteProxy_4bin6i8.deploySuitcase(Unknown Source)
    at com.oracle.bpel.client.BPELDomainHandle.deploySuitcase(BPELDomainHandle.java:317)
    at com.oracle.bpel.client.BPELDomainHandle.deployProcess(BPELDomainHandle.java:339)
    at deployHttpClientProcess.jspService(_deployHttpClientProcess.java:376)
    at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
    at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:453)
    at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:591)
    at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:515)
    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:396)
    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:410)
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
    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.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)

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

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

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

Maybe you are looking for