Subject: Re: ogsadai globus ws core weird messages
- Next message: Amy Krause: "RE: ogsadai globus ws core weird messages"
- Previous message: Ally Hume: "RE: ogsadai globus ws core weird messages"
- In reply to: Ally Hume: "RE: ogsadai globus ws core weird messages"
- Next in thread: Amy Krause: "OGSA-DAI + Gridsphere"
- Reply: Amy Krause: "OGSA-DAI + Gridsphere"
From: Sasha Golohvastov (golohvastov@gmail.com)
Date: Jul 24, 2006 09:53
Hi Ally
Thanks for your help.
I have succeded with ogsadai portlet but I only could make it with WSRF
version of OGSA-DAI
WSI is still not working though.
I've noticed that using
DataService service =
GenericServiceFetcher.getInstance().getDataService(handle,
id);
doesn't produce any traces in log files.
I've replaced it with
DataService service =
GenericServiceFetcher.getInstance().getWSRFDataService(handle,
id);
and for some reason using getWSRFDataService(handle, id) left error message
in my log file.
It was SOAP related error I've googled it and found that it had to do with
axis.jar file version after playing with different axis.jar files I've
finally succeded.
WSI might have the same problem but there is nothing in log files and I did
not have time to check it.
Many thanks,
Sasha.
On 7/24/06, Ally Hume <a.hume@epcc.ed.ac.uk> wrote:
>
> Hi,
>
> Error messages such as "Internal fault. Consult the OGSA-DAI Service
> Provider with ID 1153524626539:2" are produced when a server side
> error occurs that is due to the server configuration or some other
> issue that the client does not necessary understand or that the server
> administrator would wish to hide from the client. One example of this
> is the inability to connect to a RDBMS.
>
> If you enable logging at the server (See "How to enable logging"
> section of the OGSA-DAI documentation) at the INFO level then you will
> see more a more detailed description of the error. You should use the
> ID returned to the client to look up the server log.
>
> Regards,
>
> Ally
>
> -------------------------------------------------------------
> Ally Hume
> Software Architect
> EPCC, University of Edinburgh
> James Clerk Maxwell Building
> Mayfield Road E-mail: a.hume@epcc.ed.ac.uk
> Edinburgh, EH9 3JZ Phone: + 44 (0) 131 651 3397
> United Kingdom Fax: + 44 (0) 131 650 6555
> -------------------------------------------------------------
>
>
> -----Original Message-----
> From: owner-users@ogsadai.org.uk [mailto:owner-users@ogsadai.org.uk]
> On Behalf Of Sasha Golohvastov
> Sent: 22 July 2006 14:25
> To: ogsa-dai-ug@cs.indiana.edu; users@ogsadai.org.uk
> Subject: ogsadai globus ws core weird messages
>
> Dear all,
>
> I have installed tomcat ws core and ogsadai wsrf on windows machine
> and
> everything works well.
> I can deploy data services, add data resource services using ant
> script
> For example
> ant listResourcesClient -
> Ddai.url=http://localhost:8080/wsrf/services/ogsadai/DataService
> works allrigt. ant databrowser works good as well - I can execute sql
> queries.
> but when I try to execute any of java source examples I receive
> following
> weird messages
>
> Exception in thread "main"
> uk.org.ogsadai.client.toolkit.exception.ServerExcepti
>
> on: Internal fault. Consult the OGSA-DAI Service Provider with ID
> 1153524626539:
>
> 2.
>
>
>
> at
> uk.org.ogsadai.client.toolkit.exception.FaultToException.getServerExc
>
> eption(FaultToException.java:51)
>
> at
> uk.org.ogsadai.client.toolkit.wsrf.WSRFDataServiceStub.perform
> (WSRFDa
>
> taServiceStub.java:561)
>
> at uk.org.ogsadai.client.toolkit.wsrf.WSRFDataService.perform
> (WSRFDataSe
>
> rvice.java:110)
>
> at SimpleExample.main(SimpleExample.java:36)
> Any ideas about this?
>
> Many thanks
> Sasha Golohvastov
>
>
- Next message: Amy Krause: "RE: ogsadai globus ws core weird messages"
- Previous message: Ally Hume: "RE: ogsadai globus ws core weird messages"
- In reply to: Ally Hume: "RE: ogsadai globus ws core weird messages"
- Next in thread: Amy Krause: "OGSA-DAI + Gridsphere"
- Reply: Amy Krause: "OGSA-DAI + Gridsphere"