This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Correlation Project fails to work | ||
---|---|---|---|
Product: | soa | Reporter: | mfoster <mfoster> |
Component: | BPEL Project | Assignee: | kiran_bhumana <kiran_bhumana> |
Status: | VERIFIED INVALID | ||
Severity: | blocker | CC: | gbadescu |
Priority: | P1 | ||
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
BPEL project
CA Project |
Description
mfoster
2006-09-21 14:38:05 UTC
Created attachment 34306 [details]
BPEL project
Created attachment 34307 [details]
CA Project
do you see this as a runtime problem or have you identified some design time, build time issues? if it is runtime problem we/you need to file against BPEL SE on other bug tracking system. you have to re-start the BPEL SE in Debug mode before attach can succeed. this is supposed to be clear in the BPEL design guide. Not sure what tutorial you are referring to. or rather, I should say, if the steps for getting debug to work are not clear, then we/you need to file a bug against the documentation and indicate which document you are having trouble with. as for debugging steps: http://www.netbeans.org/kb/55/bpel_gsg_test.html#debug 1. I looked at the BPEL and WSDL it seems to be fine. Let me debug and get back to you. What does the log say when you run it? when correlation is "no", the incoming message will merge into the instance. when correlation is "join", the incoming message (one case) will merge into the instance, if it already exists or initialises the value if it is absent. 2. Like 5.x you should be able to turn on the logging in the appserver conf domain.xml file. If there is a issue with the content even after you enable logging, please file a bug in the bugster. 3. you can turn on the BPEL debugger by going to the NB runtime tab, go to BPEL SE, go to properties, enable debugger flag. When I run the "setStartProcess" I get back the expected result. When I run the "cancel" which should correlate it times out after 30 seconds, I don't see anything in the log but I haven't tried turning the bpel debugging on as you explain yet. When i deploy the attached project i get the following deployment exception. javax.jbi.JBIException: java.lang.Exception: An activated endpoint already has the same SOAP Address location : http://localhost:22000/SeeBeyondService at com.sun.jbi.httpsoapbc.ServiceUnitImpl.createEndpoints(ServiceUnitImpl.java:409) at com.sun.jbi.httpsoapbc.ServiceUnitImpl.deploy(ServiceUnitImpl.java:161) at com.sun.jbi.httpsoapbc.HttpSoapBindingDeployer.deploy(HttpSoapBindingDeployer.java:144) at com.sun.jbi.framework.ServiceUnitOperation.process(ServiceUnitOperation.java:145) at com.sun.jbi.framework.Operation.run(Operation.java:86) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.Exception: An activated endpoint already has the same SOAP Address location : http://localhost:22000/SeeBeyondService at com.sun.jbi.httpsoapbc.HttpSoapBindingLifeCycle.endpointDeployed(HttpSoapBindingLifeCycle.java:283) at com.sun.jbi.httpsoapbc.ServiceUnitImpl.createEndpoints(ServiceUnitImpl.java:386) ... 5 more Also, i see testStart and testRecover testcases, not setStartProcess, cancel. Are we referring to the correct project? This is not an issue with correlations at all. If the BPEL was debugged we could have caught this early on.. The while condition evaluated to false and the instance is always complete and is never waiting for the correlated message to come in. <while name="While1"> <condition>not($exitLoop)</condition> I couldn't find the corresponding bug for evaluation of expressions in the engine. There is a bug in the engine with the evaluation of some simple data types. Closing this issuzilla bug. Closing as this is caused by an existing runtime bug runtime bug in bugster 6457028 |