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.

Bug 85445 - Correlation Project fails to work
Summary: Correlation Project fails to work
Status: VERIFIED INVALID
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Project (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: kiran_bhumana
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-21 14:38 UTC by mfoster
Modified: 2006-10-03 08:56 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
BPEL project (105.96 KB, application/octet-stream)
2006-09-21 14:38 UTC, mfoster
Details
CA Project (315.07 KB, application/octet-stream)
2006-09-21 14:38 UTC, mfoster
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mfoster 2006-09-21 14:38:05 UTC
See attached project.

I have a simple "ws-receive1 -> assign1 -> ws-reply1 -> ws-recieve2 
(correlate) -> assign2 -> ws-reply2" project working with the same 
SeeBeyondService.wsdl (with PLs and Alias')

I try to run the attached project and my "Recover" test fails to join the 
running BP, I have no idea why.

A few questions....
1. Anything I have done wrong ? What is the difference between Initialise of NO 
and Initialise of JOIN ?
2. In 5.x you got a trace of all the bpel statements in the server.log - I 
can't seem to see the same in Alaska, is it possible.
3. I'd love to use the BPEL debugger but looking at the tutorial it says to 
turn on debugging in the EM - I can't find anywhere to do this, when I attach 
to the debugger currently it fails to attach.

Thanks
Comment 1 mfoster 2006-09-21 14:38:32 UTC
Created attachment 34306 [details]
BPEL project
Comment 2 mfoster 2006-09-21 14:38:56 UTC
Created attachment 34307 [details]
CA Project
Comment 3 Michael Frisino 2006-09-21 14:57:56 UTC
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.
Comment 4 Michael Frisino 2006-09-21 21:18:06 UTC
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.
Comment 5 Michael Frisino 2006-09-21 21:19:33 UTC
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.
Comment 6 Michael Frisino 2006-09-21 22:48:12 UTC
as for debugging steps: http://www.netbeans.org/kb/55/bpel_gsg_test.html#debug
Comment 7 kiran_bhumana 2006-09-22 19:54:19 UTC
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.
Comment 8 mfoster 2006-09-22 21:39:41 UTC
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.
Comment 9 kiran_bhumana 2006-09-23 00:48:57 UTC
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?
Comment 10 kiran_bhumana 2006-09-23 01:44:23 UTC
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>
Comment 11 kiran_bhumana 2006-09-23 02:23:01 UTC
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.
Comment 12 Mikhail Kondratyev 2006-10-01 15:25:49 UTC
Closing as this is caused by an existing runtime bug
Comment 13 kiran_bhumana 2006-10-03 08:56:32 UTC
runtime bug in bugster 6457028