Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [geclipse-dev] Job submission problem 



On Tue, 2 Dec 2008, Romain wrote:



I am still trying to submit jobs through an application (call it SimExplorer) using g-eclipse.

When I use g-eclipse workspace everything is fine. When I use SimExplorer I
get the following exception:



Hi,

I see two potential problems:


Caused by: Stack dump
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
	at java.lang.Class.newInstance0(Class.java:355)
	at java.lang.Class.newInstance(Class.java:308)
	at org.apache.axis.encoding.ser.BeanDeserializer.<init>(BeanDeserializer.java:104)
Here is one. BeanDeserialiser tries to load via reflection class org.glite.wms.wmproxy.GenericFaultType. And classloader cannot instantiate it. Strange, because that class was already instantiated here: 


	at org.glite.wms.wmproxy.GenericFaultType.getDeserializer(GenericFaultType.java:90)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.apache.axis.encoding.ser.BaseDeserializerFactory.getSpecialized(BaseDeserializerFactory.java:154)
But then it was instantiated by SAX parser and the exception is while instantiating it from Axis. Maybe Axis classloader has no WMS.jar in its classpath?
The second problem is the GenericFaultType itself. This class should not be used if jobRegister() is successfull. Stack trace clearly shows, that SAX parser found GenericFaultType in WMS response. It means that WMS refused job registration. It is not easy to guess why. (If you dig deep anough in debugging axis responses you can find WMS Soap response, but it is not easy). Are you sure, that you use the same WMS with Eclipse workspace and without it? If yes, my suspecion is that it is again problem with classpath from Axis to WMS.jar. If the message send to WMS was not serialised correctly then WMS can throw GeneralFaultType. 


Regards,

Pawel

Back to the top