Bugzilla – Bug 1410
local part cannot be "null" when creating a Qname
Last modified: 2004-05-28 15:48:14
You need to log in before you can comment on or make changes to this bug.
Globus import javax.xml.rpc.namespace.QName from JAX-RPC library. There are a bug for Jaxrpc as following: In theory, if local part of the QName is null, the program should go IllegalArgumentException. But in real implementation, the null local part of the QName is acceptable. It has been fixed with the lastest jax-rpc 1.1. Correspondly, there are null local part existing in Globus implementation, which need to be fixed. When using the latest Jax-rpc 1.1 or QName class in j2ee, Globus stand-alone web container can not be started. The following error has been displayed: local part cannot be "null" when creating a QName org.globus.ogsa.repository.DefaultServiceActivator [activatePersistent:147] org.globus.ogsa.handlers.PersistentServiceHandler [invoke:212]
We tracked down the break points as following: In src/org/globus/ogsa/WSDLGenerator.Java [line 464] description = symbolTable.add(doc); Here, doc = [#document: null]. It was invoked three times when starting Globus stand-alone web container. Then in src/org/globus/ogsa/WSDL/symbolTable.Java [line 69] GSR gsr = new GSR(doc); Now, the problem is what we should fill in there.
Correction: The break point in src/org/globus/ogsa/WSDL/symbolTable.Java is [line 76] add("", gsr.getWSDLDefinition(), doc); (The "null" doc is accepted by GSR). Sheng JIANG
The "null" document comes from the line 363 of WSDLGenerator.java doc = builder.parse(wsdlURL); Here, input wsdl are http://128.16.67.1:8080/schema/ogsi/ogsi_notification_factory_service.wsdl http://128.16.67.1:8080/schema/ogsi/ogsi_notification_service_group_service.wsd l The builder.parse() return null for the parse of both files. Sheng JIANG
Fixes committed to cvs (trunk). Thanks.
I tested the latest GT3.2 alpha. It is still problem. Sheng JIANG
Are you using the latest code from cvs from trunk?
I did test with the latest cvs. I tried again with updated to Feb 10th, 2004. It still not work. Sheng
Can you give me exact stack trace, etc. because I cannot replicate this problem anymore with latest version from trunk. Maybe you set GLOBUS_LOCATION wrong?
I download the packaging, then install from it. I list my steps as following: cvs -d :pserver:anonymous@cvs.globus.org:/home/globdev/CVS/gridservices login cvs -d :pserver:anonymous@cvs.globus.org:/home/globdev/CVS/gridservices co packaging cd packaging ./make-packages.pl --gt3-tag globus_3_2a_pre5 --install=/usr/gt3.2a/ -- anonymous --faster --verbose --noparanoia [my GLOBUS_LOCATION was set to be /usr/gt3.2a as well] After installed, I run "ant startContainer" under /usr/gt3.2a with my JAVA_HOME=/usr/java/j2sdk1.5.0, get the QName errors yet. Sheng JIANG
"--gt3-tag globus_3_2a_pre5" indicates you are getting an alpha version! Remove that option from the command line.
My installation ended during the processing with the following error: make[2]: *** [checkpw.lo] Error 1 make[2]: Leaving directory `/home/sjiang/cvs-gt3.2alpha- 100204/packaging/bundle-output/BUILD/globus_cyrus-sasl-0.4/cyrus-sasl- 1.5.27/lib' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/sjiang/cvs-gt3.2alpha- 100204/packaging/bundle-output/BUILD/globus_cyrus-sasl-0.4/cyrus-sasl-1.5.27' make: *** [all-recursive-am] Error 2 ERROR: Build has failed Not creating installer because --installer= not set. Not generating binary packages because -binary not set. When I try to run "ant startContainer" with what I got, the following error displayed: org.globus.ogsa.handlers.container.ContainerHandlerHelper [shutdown:93] ERROR: Shutting down container. Container handler failed ('grim setuid program failed. [java] /usr/gt3/bin/globus-grim: error while loading shared libraries: libglobus_grim_devel_gcc32dbg.so.0: cannot open shared object file: No such file or directory') [java] java.lang.Exception: grim setuid program failed. I checked lib directory. libglobus_grim_devel_gcc32dbg.so.0 is right there. Sheng Jiang
I confirm the Qname problem is fixed. But please still help me go through the cvs installation. Sheng Jiang
Ok, that's a separate issue. Did you set the globus environment correctly? GLOBUS_LOCATION & source etc/globus-user-env.csh ? If you are still having problems please send email to discuss@globus.org