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 91791 - Deploy action should check/inform about conflicting of endpoints
Summary: Deploy action should check/inform about conflicting of endpoints
Status: VERIFIED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: Composite Application (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Jun Qian
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-04 04:00 UTC by Jiri Kopsa
Modified: 2008-04-29 22:23 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Kopsa 2007-01-04 04:00:53 UTC
Steps to reproduce:
* Create SynchronousSample application and deploy it.
* Create another SynchronousSample application change it's logic and SOAP-HTTP
endpoint address; and deploy it.
- In this point, the more recent application overrides the previous one.
- No warning is given.
* Runtime tab shows two deployed assemblies; two service units each.
* Run test case on first and second application. Both of them return the same
result - from the application deployed later.

User should be warned if the deployment is going to override previous endpoints
and probably provided with option to cancel the deployment. This however does
not apply to the case, when the user is only redeploying a previously deployed
application.

Setting priority to P2, because user may be significantly slowed down with this
bug; or unable to resolve this as there is no user interface to deal with this
case. Also users may hit the issue frequently while building large applications,
or when deploying to a preexisting rich JBI runtime.
Comment 1 Jiri Kopsa 2007-01-04 04:10:10 UTC
This issue describes internal endpoints, however solution for conflicts of
external endpoints should be common.
Comment 2 Jiri Kopsa 2007-01-04 04:11:16 UTC
A less severe variant of this issue is:
http://www.netbeans.org/issues/show_bug.cgi?id=91792
Comment 3 Jun Qian 2007-02-09 09:10:08 UTC
This is a JBI framework and/or JBI component issue. Please file a bug using
bugster and add the bugster # here.

I am leaving this ticket open for now because I want to verify the deployment
failure or warning when the runtime problem is fixed.
Comment 4 Jun Qian 2007-02-16 02:26:16 UTC
The bugster ID for the runtime issue is 6525801.
Comment 5 Alexei Mokeev 2007-02-16 09:58:07 UTC
Moved EP551_WAIVER_REQUEST from Status Whiteboard to Keywords, where it is
supposed to be accrding to the process.
Comment 6 astashkova 2007-02-16 16:42:35 UTC
Added to staged NB Enterprise Pack Release Notes
(http://nbstaging.czech.sun.com/community/releases/55/1/entpack_relnotes.html#91791).
Workaround provided needs verification.
Comment 7 Alexei Mokeev 2007-02-19 07:07:00 UTC
No Objections in 48 hours. Waived.
Comment 8 Alexei Mokeev 2007-03-05 17:27:14 UTC
Removed Beta EP551_WAIVER_APPROVED keyword - we are going forward to FCS.
Comment 9 Venkat Chellasamy 2007-03-19 21:32:46 UTC
Jun,
please re-verify as the runtime bug is closed
Comment 10 Jun Qian 2007-04-14 22:56:09 UTC
Confirmed that we are now getting error message when starting the second service
assembly:

run-jbi-deploy:
[deploy-service-assembly]
    Deploying a service assembly...
        host=localhost
        port=4848
        file=C:\Documents and Settings\jqian\My
Documents\SynchronousSample3\SynchronousSample3Application/dist/SynchronousSample3Application.zip
[start-service-assembly]
    Starting a service assembly...
        host=localhost
        port=4848
        name=SynchronousSample3Application
Successful execution of Start
WARNING: (JBIMA0405) Start of service assembly SynchronousSample3Application
succeeded partially; some service units failed to start.
    * Component: sun-bpel-engine
      ERROR: (BPELSE) Service unit
SynchronousSample3Application-SynchronousSample3 failed to load deployment
C:\GlassFish_b41\glassfish\domains\domain1\jbi\service-assemblies\SynchronousSample3Application\SynchronousSample3Application-SynchronousSample3\sun-bpel-engine
:Process already
registered{http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}SynchronousSample
    * Component: sun-http-binding
      INFO: (JBIMA0500) Lifecycle operation start succeeded for Service Unit
SynchronousSample3Application-sun-http-binding.

Note that since the HTTP SOAP BC serivce unit in the second service assembly is
started successfully (as shown above), and the two BPEL service units from the
two service assemblies use the same internal endpoint, when testing the second
compapp, the first BPEL will be executed. This is the correct behavior, although
it might not be immediately obvious to the end user.
Comment 11 vinathi 2008-04-29 22:23:33 UTC
Verified using 20080429-0500.
we are getting the following error message when starting the second service
ERROR: Failed execution of Start: SynchronousSample1Application
    * Component: sun-bpel-engine
      ERROR: (BPJBI-4001:BPELSE) BPJBI-7007:Service unit: SynchronousSample1Application-SynchronousSample1 failed to 
load deployment: C:\JavaCAPS6\appserver\domains\domain1\jbi\service-
assemblies\SynchronousSample1Application\SynchronousSample1Application-SynchronousSample1\sun-bpel-engine for: 
{http://enterprise.netbeans.org/bpel/SynchronousSample/SynchronousSample_1}SynchronousSample:  Service name: 
partnerlinktyperole1_myRole : Endpoint name: java.lang.Exception: BPJBI-7009:An activated endpoint already exits. {5}
    * Component: sun-http-binding
      ERROR: (SOAPBC_INIT_1) HTTPBC-E00203: Initialization failed. java.lang.Exception: HTTPBC-E00142: Endpoint 
http://localhost/SynchronousSample/SynchronousSample,service1,port1,Consumer cannot be activated because another 
endpoint with the same address location ''http://VMapakshi-Tecra.stc.com:18181/SynchronousSample'' is already active.
Cleaning up...