created a simple EJB and exposed it as a web service using SapIde

[Former Member]

Hi guys!

can any one suggest me the internal server error i am facing

I developed an EJB and used the Web Service Creation Wizard to expose the EJB as a web service using the NetWeaver Developer Studio and successfully deployed the web service to Web AS. Then I used the Web Service Homepage to test run the web service and can view it but iam getting an internal error as follows:

the error is 500 Internal Server Error

[Former Member]

500 errors in the HTTP cycle

Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle when it communicates with your Web server:

Obtain an IP address from the IP name of your site (your site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).

Open an IP socket connection to that IP address.

Write an HTTP data stream through that socket.

Receive an HTTP data stream back from your Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.

This error occurs in the final step above when the client receives an HTTP status code that it recognises as '500'.

Resolving 500 errors - general

This error can only be resolved by fixes to the Web server software. It is not a client-side problem. It is up to the operators of your Web server site to locate and analyse the logs which should give further information about the error.

Resolving 500 errors - CheckUpDown

Please contact us (email preferred) whenever you encounter 500 errors on your CheckUpDown account. We then have to liaise with your ISP and the vendor of your Web server software so they can trace the exact reason for the error. Correcting the error may require recoding program logic for your Web server software, which could take some time.

We monitor your site for errors like 500. Please click any of the buttons below for more information.

or

Check this URL

http://www.checkupdown.com/status/E500.html

[Former Member]

Definitely there is an error in your EJB.Try to call the ejb method in your JUnit Test program and see the stacktrace.