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 85292 - Deployment failed. Cannot find CatalogManager.properties
Summary: Deployment failed. Cannot find CatalogManager.properties
Status: VERIFIED WONTFIX
Alias: None
Product: soa
Classification: Unclassified
Component: JBI Manager (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: Alexander Fung
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-20 01:20 UTC by Sherry Barkodar
Modified: 2006-09-28 12:37 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
loan application (93.93 KB, application/octet-stream)
2006-09-20 01:22 UTC, Sherry Barkodar
Details
server.log (703.22 KB, application/octet-stream)
2006-09-20 01:24 UTC, Sherry Barkodar
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sherry Barkodar 2006-09-20 01:20:52 UTC
1-Create EJB Module.
2-Create Web Service
3-Deploy the webservice.
4-Terstrun the webservice. In the Browser click the WSDL File to get the WSDL
URL to use it in step 7.
Open the wsdl file copy the URL location of the schema to use it in step 8.
5-Create a BPEL Prj
6-Create a BPEL Process
7-Process File > New > External WSDL Document and use the Provided URL from step 4.
8-Process File > New > External Schema and use the provided schema location in
the wsdl.
9-Process File > New WSDL. Import the above schema.
In the BPEL Process use D&D to add both wsdls to the design.
Add Receive, Assign, Invoke, Reply activity to the BPEL Process.
Build the BPEL Prj. Successful.
Create a CA add the BPEL Module.
Deploy the CA it fails:
Building jar: D:\sherrydev\SOA\del4\LoanRequestor\build\SEDeployment.jar
Expanding: D:\sherrydev\SOA\del4\LoanRequestor\build\SEDeployment.jar into
D:\sherrydev\SOA\del4\CompositeApp\src\bindingComponentASA
Expanding: D:\sherrydev\SOA\del4\LoanRequestor\build\SEDeployment.jar into
D:\sherrydev\SOA\del4\CompositeApp\src\bindingComponentASA\META-INF\catalogData\LoanRequestor
jbi-build:
Created dir: D:\sherrydev\SOA\del4\CompositeApp\build\META-INF
Building jar: D:\sherrydev\SOA\del4\CompositeApp\build\BCDeployment.jar
 copying Sub-Assembly: D:\sherrydev\SOA\del4\CompositeApp\build\LoanRequestor.jar
Create BindingComponent jar:
D:\sherrydev\SOA\del4\CompositeApp\build/com.sun.httpsoapbc-1.0-2.jar
Deleting: D:\sherrydev\SOA\del4\CompositeApp\build\BCDeployment.jar
Created dir: D:\sherrydev\SOA\del4\CompositeApp\dist
Building jar: D:\sherrydev\SOA\del4\CompositeApp\dist\CompositeApp.zip
run-jbi-deploy:
[deploy-service-assembly]
    Deploying a service assembly...
        host=localhost
        port=4848
        file=D:\sherrydev\SOA\del4\CompositeApp/dist/CompositeApp.zip
    Deploy service assembly failed. (partial success)
        MESSAGE: (SOAPBC_DEPLOY_2) Failed to deploy: java.lang.NullPointerException
D:\sherrydev\SOA\del4\CompositeApp\nbproject\build-impl.xml:207: Service
assembly deployment failed.
BUILD FAILED (total time: 4 seconds)
I will add the zipped project and the AS log file
Comment 1 Sherry Barkodar 2006-09-20 01:22:36 UTC
Created attachment 34194 [details]
loan application
Comment 2 Sherry Barkodar 2006-09-20 01:24:09 UTC
Created attachment 34195 [details]
server.log
Comment 3 Venkat Chellasamy 2006-09-20 22:03:26 UTC
server log:

[#|2006-09-19T17:02:26.812-0700|SEVERE|sun-appserver-
pe9.0|com.sun.jbi.component.com.sun.httpsoapbc-1.0-
2com.sun.jbi.httpsoapbc.HttpSoapBindingDeployer|_ThreadID=61;_ThreadName=Compos
iteApp-com.sun.httpsoapbc-1.0-2;_RequestID=b2001794-0bfe-4d1d-ad58-
e4cbcbf0039c;|Failed to deploy: java.lang.NullPointerException
javax.jbi.JBIException: java.lang.NullPointerException
	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.NullPointerException
	at com.sun.jbi.wsdlvalidator.impl.ValidatingWSDLReaderImpl.readWSDL
(ValidatingWSDLReaderImpl.java:88)
	at com.sun.jbi.wsdlvalidator.impl.ValidatingWSDLReaderImpl.readWSDL
(ValidatingWSDLReaderImpl.java:89)
	at com.sun.jbi.wsdlvalidator.impl.ValidatingWSDLReaderImpl.readWSDL
(ValidatingWSDLReaderImpl.java:89)
	at com.sun.jbi.wsdlvalidator.impl.ValidatingWSDLReaderImpl.readWSDL
(ValidatingWSDLReaderImpl.java:89)
	at com.sun.jbi.wsdlvalidator.impl.ValidatingWSDLReaderImpl.readWSDL
(ValidatingWSDLReaderImpl.java:89)
	at com.sun.jbi.wsdlvalidator.impl.ValidatingWSDLReaderImpl.readWSDL
(ValidatingWSDLReaderImpl.java:89)
	at com.sun.jbi.wsdlvalidator.impl.ValidatingWSDLReaderImpl.readWSDL
(ValidatingWSDLReaderImpl.java:89)
	at com.sun.jbi.wsdlvalidator.impl.ValidatingWSDLReaderImpl.readWSDL
(ValidatingWSDLReaderImpl.java:89)
	at com.sun.jbi.httpsoapbc.ServiceUnitImpl.createEndpoints
(ServiceUnitImpl.java:359)
	... 5 more
Comment 4 lchang 2006-09-22 00:37:40 UTC
could not reproduce this in the latest build. 0921
Comment 5 Alexander Fung 2006-09-22 20:59:11 UTC
This is the same bug with the long file name problem.  If you use the latest JDK
(or anything greater than 1.5.0_05), the error no longer exists.  I was able to
reproduce with 1.5.0_05, but with 1.5.0_08, the problem no longer exists.

The "fix" is to upgrade to the latest JDK.
Comment 6 skrishnan 2006-09-28 12:37:45 UTC
verified in with jdk1.5.0_09.