Happening Again: Process Deployment Issue - successful upload, but doesn't deploy

I got the following exception when I deployed it on newest release of BPS. New BPS 1.1 release will be available within this week. There is a reference to unknown partner link DISAInternalSearchPartnerLink. Here is the exception log. [2009-11-16 13:38:52,470] INFO - info: [CompilingProcess] Compiling BPEL process. [2009-11-16 13:38:52,494] INFO - WSDL at file:/home/milinda/Projects/Test/wso2bps-1.1.0/tmp/bpel/DISAInternalSearch-5/DISAInternalSearch.wsdl is a duplicate import, your documents should all be in different namespaces (its's not nice but will still work). [2009-11-16 13:38:52,600] INFO - Process {http://www.disa.mil/federatedsearch/bpel}DISAInternalSearch-5 deployed from "{http://www.disa.mil/federatedsearch/bpel}DISAInternalSearch-5". [2009-11-16 13:38:52,704] INFO - Deploying Axis2 service DISAInternalSearch [2009-11-16 13:38:52,805] ERROR - Error in deployment descriptor for process {http://www.disa.mil/federatedsearch/bpel}DISAInternalSearch-5; reference to unknown partner link DISAInternalSearchPartnerLink [2009-11-16 13:38:52,806] WARN - Deployment failed within the engine, store undeploying process. org.apache.ode.bpel.iapi.BpelEngineException: Error in deployment descriptor for process {http://www.disa.mil/federatedsearch/bpel}DISAInternalSearch-5; reference to unknown partner link DISAInternalSearchPartnerLink at org.apache.ode.bpel.engine.ODEProcess.setRoles(ODEProcess.java:714) at org.apache.ode.bpel.engine.ODEProcess.access$1000(ODEProcess.java:105) at org.apache.ode.bpel.engine.ODEProcess$HydrationLatch.doHydrate(ODEProcess.java:1344) at org.apache.ode.bpel.engine.ODEProcess$HydrationLatch.access$200(ODEProcess.java:1304) at org.apache.ode.bpel.engine.ODEProcess$HydrationLatch$2.run(ODEProcess.java:1315) at org.apache.ode.bpel.engine.NStateLatch.latch(NStateLatch.java:89) at org.apache.ode.bpel.engine.ODEProcess.hydrate(ODEProcess.java:918) at org.apache.ode.bpel.engine.BpelServerImpl.register(BpelServerImpl.java:387) at org.wso2.carbon.bpel.ode.integration.BPELServerManager.handleEvent(BPELServerManager.java:556) at org.wso2.carbon.bpel.ode.integration.BPELServerManager.access$100(BPELServerManager.java:68) at org.wso2.carbon.bpel.ode.integration.BPELServerManager$ProcessStoreListenerImpl.onProcessStoreEvent(BPELServerManager.java:532) at org.wso2.carbon.bpel.ode.integration.store.RegistryBasedProcessStoreImpl.fireEvent(RegistryBasedProcessStoreImpl.java:799) at org.wso2.carbon.bpel.ode.integration.store.RegistryBasedProcessStoreImpl.fireStateChange(RegistryBasedProcessStoreImpl.java:805) at org.wso2.carbon.bpel.ode.integration.store.RegistryBasedProcessStoreImpl.deploy(RegistryBasedProcessStoreImpl.java:396) at org.wso2.carbon.bpel.BPELDeployer.deploy(BPELDeployer.java:278) at org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136) at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:795) at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144) at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:338) at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:241) at org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:332) at org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:64) at org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:71) at org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask.run(Scheduler.java:90) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) If you want we can give you a release candidate of BPS 1.1 release.

Hi Milinda, Thanks for your quick response. I knew it was something simple, as always is the case until you find it :) However, the BPS server (my version 1.0.1) not complaining about the error got me lost. I actually would like to get a copy of the 1.1 release candidate since it seems to have better error reporting mechanism. Please let me know how I can get a copy of it. For others who might be searching the forum for similar problems (like I usually do), my deploy.xml file had invalid partnerLink attributes- a side effect of cut 'n paste from a tutorial. These names had to match the ones defined in the .bpel file. You'd think it's common sense, but I did miss it - I guess when you are dealing with something new, it could be overwhelming to miss something this simple. Oh well! Below are partial deploy.xml without proper tags since I can't seem to add xml tags in this post - they get omitted due to formatting options. Incorrect deploy.xml: provide partnerLink="DISAInternalSearch" invoke partnerLink="WorkspaceSearch" Correct deploy.xml: provide partnerLink="disaInternalSearch" invoke partnerLink="workspaceSearch"

Hi Milinda, As per your previous response, I really would like to get a copy of the candidate release of BPS 1.1. I'm running into deployment issue again just like my original posted problems and don't know what's wrong with my deploy.xml file. I think having 1.1 would report enough information to move forward. Posting questions every time with deployment issues does not make sense, nor it is productive for anyone. Please let me know how I can get a copy of it. p.s. Just so if it's easier/quicker to respond while waiting on the release, here is the latest DISAInternalSearch.zip file for you to try. With advance thanks, Tariq.

WSO2 BPS 1.1 release will be available before end of this week. I'll let you once it available for public download.

Thanks Milinda for your response. I'm on a serious time crunch to get this going. I would sincerely appreciate it if you or someone could take a minute to deploy my process and let me know what error you see so I could move on for now - while I wait for the release in the meantime. It may sound pushy, but saving a couple of days means a lot to me right now. Thanks, Tariq.

I deployed your BPEL package in both BPS versions, it worked without any error. What is the error you got?

BPS 1.1 is available for download. Please go to the link http://wso2.org/downloads/bps. Thanks Milinda

Thanks again for your prompt response. Like my original posting said, BPS says successful deployment, but I don't see the process in the list. Apparently, there was an error in my deploy.xml file. But this time I don't know what's wrong. Did you check to see if my process shows up in the list? p.s. I'm going to download the new release right now. Thanks, Tariq.

The process correctly deploys and shows up on the new release. Also, the "Try Service" link works on this release as well. But I'm not sure how to enter a complex request on the "Try It" screen - I suppose it's the entire soap body? In any case, this problem seems to have been resolved for now. Thanks for all your help, Milinda!

If Try-It prompts for a complex request, you better not use try-it tool to test your process. Please use an alternative tool such as SoapUI to invoke your process.