Is it doc/literal? There is a bug in Axis with doc/literal services with no params.
-----Original Message-----
From: Kareem Ghazal [mailto:[EMAIL PROTECTED]
Sent: Friday, August 08, 2003 5:13 AM
To: [EMAIL PROTECTED]
Subject: Re: (500)Internal Server Error

Hello,
 
I checked the types, however one of the functions (isStarted) does not take any parameters and returns a boolean, a very simple function. and still it gives me the internal server error on that.  I deployed the service over and over and again it deploys fine, runs good on just 2 of the methods and give the error on the others.  any pointers on how to at least debug the problem, or how to go about finding out what's the source of the problem?
 
regards,
kareem
----- Original Message -----
Sent: Friday, August 08, 2003 3:56 AM
Subject: Re: (500)Internal Server Error

hi,
If I am correct, the reason wd be, the methods return type or passing parameters may be different types which not deployed properly in the deployment.
U just change the return types and parameters in to simple types and check it.
If it works then fine ,prbs with the type mapping and deployment or that type classes may not be deployed or u maynot copy those class files in to the proper places.
check and get success.
regards,
Jeyakumaran.C
----- Original Message -----
Sent: Friday, August 08, 2003 3:04 AM
Subject: (500)Internal Server Error

I'm deplying a service that has 13 methods that could be called by the client, it's deploying correctly, however it works only for 2 of the methods and gives a (500)Internal Server Error for the other ones, the following is the output for the methods that don't work:
 
Aug 7, 2003 6:47:36 PM org.apache.axis.client.Call invoke
INFO: Mapping Exception to AxisFault
AxisFault
 faultCode: {http://xml.apache.org/axis/}HTTP
 faultString: (500)Internal Server Error
 faultActor: null
 faultDetail:
        null: return code:  500
Error 500: forkjoin/FJTaskRunnerGroup
 

(500)Internal Server Error
        at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.j
ava:623)
        at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:129)
 
        at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
y.java:71)
        at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:156)
        at org.apache.axis.SimpleChain.invoke(SimpleChain.java:126)
        at org.apache.axis.client.AxisClient.invoke(AxisClient.java:182)
        at org.apache.axis.client.Call.invokeEngine(Call.java:2278)
        at org.apache.axis.client.Call.invoke(Call.java:2267)
        at org.apache.axis.client.Call.invoke(Call.java:1970)
        at org.apache.axis.client.Call.invoke(Call.java:1896)
        at org.apache.axis.client.Call.invoke(Call.java:1921)
        at org.apache.axis.client.AxisClientProxy.invoke(AxisClientProxy.java:91
)
        at $Proxy0.getFJTaskRunnerGroup(Unknown Source)
        at manager.TaskManagerProxy.getTaskExecutors(TaskManagerProxy.java:129)
        at manager.TaskManagerProxy$1.run(TaskManagerProxy.java:179)
 
so what I don't understand is how come it works for 2 of the methods and doesn't work for the others.  I'm using IBM's WSDK which uses axis.  Anybody seen something like this before? I appreciate any help.
 
kareem

Reply via email to