Error when deploying a Composite Project

Hi,

I'm experiencing a problem when deploying a BPEL process (and the error does not really help me):
WARNING: (JBIMA0405)  le démarrage de l'assemblage de services CompoEmergency a partiellement réussi ; certaines unités de service n'ont pas démarré.
    * Component: sun-bpel-engine
      ERROR: (BPJBI-4001:BPELSE) BPJBI-7004:Service unit CompoEmergency-EmergencyBPELEngine failed to load deployment /home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine : BPJBI-6024:Error while loading BPEL file /home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine/EmergencyItinerary.bpel, Exception details are Cannot parse BPEL (see below):
==> Compiling XSDs failed (file:/home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine/Partners/ItineraryService/ItineraryServiceService.wsdl, file:/home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine/Partners/RoadStatusService/RoadStatusServiceService.wsdl, file:/home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine/Partners/WasteCollection/WasteCollectionService.wsdl).

I guess there is a problem with my XSD file? but which one and why? XSD files were automatically created, I did not edit anything manually.

Note that my BPEL process fails validation with the following output:
/home/chris/NetBeansProjects/ASSET/EmergencyBPELEngine/src/EmergencyItinerary.bpel:26: 8
ERROR: The variable "GetCollectionTrucksLocationIn" is not initialized, but used.
/home/chris/NetBeansProjects/ASSET/EmergencyBPELEngine/src/EmergencyItinerary.bpel:25: 8
ERROR: The variable "GetAdvisedAreasIn" is not initialized, but used.
/home/chris/NetBeansProjects/ASSET/EmergencyBPELEngine/src/EmergencyItinerary.bpel:24: 8
ERROR: The variable "GetDiscouragedAreasIn" is not initialized, but used.

This validation problem is caused by the following bug:
http://openide.netbeans.org/issues/show_bug.cgi?id=149735

Since the BPEL file looks correct, I checked "Allow build and deploy with errors" to build and deploy the project.
I don't know if the deployment problem is caused by the validation problem: it does not look like it since it would not affect the XSD files.

Regards,
Chris.

P.S: I'm using Netbeans 6.5.1

pre-init:
init-private:
init-userdir:
init-user:
init-project:
do-init:
post-init:
init-check:
init:
init-deploy:
deps-jar:
init:
Building jar: /home/chris/NetBeansProjects/ASSET/EmergencyBPELEngine/build/SEDeployment.jar
dist_se:
Expanding: /home/chris/NetBeansProjects/ASSET/EmergencyBPELEngine/build/SEDeployment.jar into /home/chris/NetBeansProjects/ASSET/CompoEmergency/src/jbiServiceUnits/EmergencyBPELEngine
Moving 1 file to /home/chris/NetBeansProjects/ASSET/CompoEmergency/src/jbiServiceUnits/EmergencyBPELEngine
Moving 7 files to /home/chris/NetBeansProjects/ASSET/CompoEmergency/src/jbiServiceUnits/META-INF/EmergencyBPELEngine
deps-javaee-jar:
jbi-build:
Building jar: /home/chris/NetBeansProjects/ASSET/CompoEmergency/build/BCDeployment.jar
Duplicate PortType: {http://itineraryServ.utbm.fr/}ItineraryService
Duplicate Binding: {http://itineraryServ.utbm.fr/}ItineraryServicePortBinding
Duplicate PortType: {http://set.utbm.fr/}RoadStatusService
Duplicate Binding: {http://set.utbm.fr/}RoadStatusServicePortBinding
Duplicate PortType: {http://set.utbm.fr/}WasteCollection
Duplicate Binding: {http://set.utbm.fr/}WasteCollectionPortBinding
Duplicate Service: {http://itineraryServ.utbm.fr/}ItineraryServiceService
Duplicate Port: {http://itineraryServ.utbm.fr/}ItineraryServiceService.ItineraryServicePort
Duplicate Service: {http://set.utbm.fr/}RoadStatusServiceService
Duplicate Port: {http://set.utbm.fr/}RoadStatusServiceService.RoadStatusServicePort
Duplicate Service: {http://set.utbm.fr/}WasteCollectionService
Duplicate Port: {http://set.utbm.fr/}WasteCollectionService.WasteCollectionPort
Validating CompApp project...
Generating Service Engine Service Units...
Resolving connections...
Writing connections out to connections.xml...
Generating Service Assembly jbi.xml...
Merging component projects' catalogs...
Generating Binding Component Service Units...
  creating sun-http-binding.jar
Creating/Updating CASA...
Filtering Java EE Endpoints...
Deleting: /home/chris/NetBeansProjects/ASSET/CompoEmergency/build/BCDeployment.jar
Building jar: /home/chris/NetBeansProjects/ASSET/CompoEmergency/dist/CompoEmergency.zip
Building jar: /home/chris/NetBeansProjects/ASSET/CompoEmergency/dist/CompoEmergency.zip
run-jbi-deploy:
[deploy-service-assembly]
    Deploying a service assembly...
        host=localhost
        port=4848
        file=/home/chris/NetBeansProjects/ASSET/CompoEmergency/dist/CompoEmergency.zip
[start-service-assembly]
    Starting a service assembly...
        host=localhost
        port=4848
        name=CompoEmergency
ERROR: Successful execution of Start: CompoEmergency
WARNING: (JBIMA0405)  le démarrage de l'assemblage de services CompoEmergency a partiellement réussi ; certaines unités de service n'ont pas démarré.
    * Component: sun-bpel-engine
      ERROR: (BPJBI-4001:BPELSE) BPJBI-7004:Service unit CompoEmergency-EmergencyBPELEngine failed to load deployment /home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine : BPJBI-6024:Error while loading BPEL file /home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine/EmergencyItinerary.bpel, Exception details are Cannot parse BPEL (see below):
==> Compiling XSDs failed (file:/home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine/Partners/ItineraryService/ItineraryServiceService.wsdl, file:/home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine/Partners/RoadStatusService/RoadStatusServiceService.wsdl, file:/home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine/Partners/WasteCollection/WasteCollectionService.wsdl).
    * Component: sun-http-binding
      INFO: (JBIMA0409)  l'opération de cycle de vie start a réussi pour l'unité de service CompoEmergency-sun-http-binding.
Cleaning up...
[stop-service-assembly]
    Stopping a service assembly...
        host=localhost
        port=4848
        name=CompoEmergency
[shutdown-service-assembly]
    Shutting down a service assembly...
        host=localhost
        port=4848
        name=CompoEmergency
[undeploy-service-assembly]
    Undeploying a service assembly...
        host=localhost
        port=4848
        name=CompoEmergency
/home/chris/NetBeansProjects/ASSET/CompoEmergency/nbproject/build-impl.xml:213: Start failure.
BUILD FAILED (total time: 1 second)

[jqian]

Hi Chris,

I tried your project with GlassFish ESB v2.1 Milestone 2 and I didn't
have any deployment issue. Which version of runtime did you use?

BTW, you might want to join the open-esb users mailing list [1]. You
will get more prompt design time and runtime help from there.

Thanks,
Jun

[1] https://open-esb.dev.java.net/MailingLists.html


Chris wrote:

> Hi,
>
> I'm experiencing a problem when deploying a BPEL process (and the
> error does not really help me):
> WARNING: (JBIMA0405)  le démarrage de l'assemblage de services
> CompoEmergency a partiellement réussi ; certaines unités de service
> n'ont pas démarré.
>     * Component: sun-bpel-engine
>       ERROR: (BPJBI-4001:BPELSE) BPJBI-7004:Service unit
> CompoEmergency-EmergencyBPELEngine failed to load deployment
> /home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine
> : BPJBI-6024:Error while loading BPEL file
> /home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine/EmergencyItinerary.bpel,
> Exception details are Cannot parse BPEL (see below):
> ==> Compiling XSDs failed
> (file:/home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine/Partners/ItineraryService/ItineraryServiceService.wsdl,
> file:/home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine/Partners/RoadStatusService/RoadStatusServiceService.wsdl,
> file:/home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine/Partners/WasteCollection/WasteCollectionService.wsdl).
>
> I guess there is a problem with my XSD file? but which one and why?
> XSD files were automatically created, I did not edit anything manually.
>
> Note that my BPEL process fails validation with the following output:
> /home/chris/NetBeansProjects/ASSET/EmergencyBPELEngine/src/EmergencyItinerary.bpel:26:
> 8
> ERROR: The variable "GetCollectionTrucksLocationIn" is not
> initialized, but used.
> /home/chris/NetBeansProjects/ASSET/EmergencyBPELEngine/src/EmergencyItinerary.bpel:25:
> 8
> ERROR: The variable "GetAdvisedAreasIn" is not initialized, but used.
> /home/chris/NetBeansProjects/ASSET/EmergencyBPELEngine/src/EmergencyItinerary.bpel:24:
> 8
> ERROR: The variable "GetDiscouragedAreasIn" is not initialized, but used.
>
> This validation problem is caused by the following bug:
> http://openide.netbeans.org/issues/show_bug.cgi?id=149735
>
> Since the BPEL file looks correct, I checked "Allow build and deploy
> with errors" to build and deploy the project.
> I don't know if the deployment problem is caused by the validation
> problem: it does not look like it since it would not affect the XSD files.
>
> Regards,
> Chris.
>
> P.S: I'm using Netbeans 6.5.1

--

Jun Qian

NetBeans SOA Tools, http://enterprise.netbeans.org
Open ESB Community, http://open-esb.org

I used Glassfish and OpenESB which were installed by Netbeans 6.5.1 (full). I don't know exactly which version of OpenESB was provided. I will see if I can update then.

Regards,
Chris.

On Wed, Apr 15, 2009 at 11:44 PM, Jun Qian <Jun.Qian@...> wrote:

Hi Chris,

I tried your project with GlassFish ESB v2.1 Milestone 2 and I didn't have any deployment issue. Which version of runtime did you use?

BTW, you might want to join the open-esb users mailing list [1]. You will get more prompt design time and runtime help from there.

Thanks,
Jun

[1] https://open-esb.dev.java.net/MailingLists.html

Chris wrote:

Hi,

I'm experiencing a problem when deploying a BPEL process (and the error does not really help me):
WARNING: (JBIMA0405)  le démarrage de l'assemblage de services CompoEmergency a partiellement réussi ; certaines unités de service n'ont pas démarré.
   * Component: sun-bpel-engine
     ERROR: (BPJBI-4001:BPELSE) BPJBI-7004:Service unit CompoEmergency-EmergencyBPELEngine failed to load deployment /home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine : BPJBI-6024:Error while loading BPEL file /home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine/EmergencyItinerary.bpel, Exception details are Cannot parse BPEL (see below):
==> Compiling XSDs failed (file:/home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine/Partners/ItineraryService/ItineraryServiceService.wsdl, file:/home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine/Partners/RoadStatusService/RoadStatusServiceService.wsdl, file:/home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine/Partners/WasteCollection/WasteCollectionService.wsdl).

I guess there is a problem with my XSD file? but which one and why? XSD files were automatically created, I did not edit anything manually.

Note that my BPEL process fails validation with the following output:
/home/chris/NetBeansProjects/ASSET/EmergencyBPELEngine/src/EmergencyItinerary.bpel:26: 8
ERROR: The variable "GetCollectionTrucksLocationIn" is not initialized, but used.
/home/chris/NetBeansProjects/ASSET/EmergencyBPELEngine/src/EmergencyItinerary.bpel:25: 8
ERROR: The variable "GetAdvisedAreasIn" is not initialized, but used.
/home/chris/NetBeansProjects/ASSET/EmergencyBPELEngine/src/EmergencyItinerary.bpel:24: 8
ERROR: The variable "GetDiscouragedAreasIn" is not initialized, but used.

This validation problem is caused by the following bug:
http://openide.netbeans.org/issues/show_bug.cgi?id=149735

Since the BPEL file looks correct, I checked "Allow build and deploy with errors" to build and deploy the project.
I don't know if the deployment problem is caused by the validation problem: it does not look like it since it would not affect the XSD files.

Regards,
Chris.

P.S: I'm using Netbeans 6.5.1

--

Jun Qian

NetBeans SOA Tools, http://enterprise.netbeans.org
Open ESB Community, http://open-esb.org

[jqian]

Hi Chris,

I think you need to update your runtime, especially the BPEL SE. You can
check your component's version in the Identification section of the
component' property sheet in NetBeans.

BTW, you can get a better NetBeans/GlassFish bundle from the open-esb
website at https://open-esb.dev.java.net/Downloads.html . The BPEL SE
contained in GlassFish ESB v2.1 Milestone 2 has a build number 090410.

Regards,
Jun

Chris wrote:

> I used Glassfish and OpenESB which were installed by Netbeans 6.5.1
> (full). I don't know exactly which version of OpenESB was provided. I
> will see if I can update then.
>
> Regards,
> Chris.
>
> On Wed, Apr 15, 2009 at 11:44 PM, Jun Qian <Jun.Qian@...
> <mailto:Jun.Qian@...>> wrote:
>
>     Hi Chris,
>
>     I tried your project with GlassFish ESB v2.1 Milestone 2 and I
>     didn't have any deployment issue. Which version of runtime did you
>     use?
>
>     BTW, you might want to join the open-esb users mailing list [1].
>     You will get more prompt design time and runtime help from there.
>
>     Thanks,
>     Jun
>
>     [1] https://open-esb.dev.java.net/MailingLists.html
>
>
>
>     Chris wrote:
>
>         Hi,
>
>         I'm experiencing a problem when deploying a BPEL process (and
>         the error does not really help me):
>         WARNING: (JBIMA0405)  le démarrage de l'assemblage de services
>         CompoEmergency a partiellement réussi ; certaines unités de
>         service n'ont pas démarré.
>            * Component: sun-bpel-engine
>              ERROR: (BPJBI-4001:BPELSE) BPJBI-7004:Service unit
>         CompoEmergency-EmergencyBPELEngine failed to load deployment
>         /home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine
>         : BPJBI-6024:Error while loading BPEL file
>         /home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine/EmergencyItinerary.bpel,
>         Exception details are Cannot parse BPEL (see below):
>         ==> Compiling XSDs failed
>         (file:/home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine/Partners/ItineraryService/ItineraryServiceService.wsdl,
>         file:/home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine/Partners/RoadStatusService/RoadStatusServiceService.wsdl,
>         file:/home/chris/apps/glassfish-v2.1/domains/domain1/jbi/service-assemblies/CompoEmergency/CompoEmergency-EmergencyBPELEngine/sun-bpel-engine/Partners/WasteCollection/WasteCollectionService.wsdl).
>
>         I guess there is a problem with my XSD file? but which one and
>         why? XSD files were automatically created, I did not edit
>         anything manually.
>
>         Note that my BPEL process fails validation with the following
>         output:
>         /home/chris/NetBeansProjects/ASSET/EmergencyBPELEngine/src/EmergencyItinerary.bpel:26:
>         8
>         ERROR: The variable "GetCollectionTrucksLocationIn" is not
>         initialized, but used.
>         /home/chris/NetBeansProjects/ASSET/EmergencyBPELEngine/src/EmergencyItinerary.bpel:25:
>         8
>         ERROR: The variable "GetAdvisedAreasIn" is not initialized,
>         but used.
>         /home/chris/NetBeansProjects/ASSET/EmergencyBPELEngine/src/EmergencyItinerary.bpel:24:
>         8
>         ERROR: The variable "GetDiscouragedAreasIn" is not
>         initialized, but used.
>
>         This validation problem is caused by the following bug:
>         http://openide.netbeans.org/issues/show_bug.cgi?id=149735
>
>         Since the BPEL file looks correct, I checked "Allow build and
>         deploy with errors" to build and deploy the project.
>         I don't know if the deployment problem is caused by the
>         validation problem: it does not look like it since it would
>         not affect the XSD files.
>
>         Regards,
>         Chris.
>
>         P.S: I'm using Netbeans 6.5.1
>
>
>
>     --
>
>     Jun Qian
>
>     NetBeans SOA Tools, http://enterprise.netbeans.org
>     Open ESB Community, http://open-esb.org
>
>

--

Jun Qian

NetBeans SOA Tools, http://enterprise.netbeans.org
Open ESB Community, http://open-esb.org