I have set all the CLASSPATHS necessary i am SCJP2.BUt i currently started EJB using SUN J2EE Server. I used J2EE Docs Guide and deployed my first application using the CONVERTER Application as explained in documentation guide of J2EE SDK.
Please tell me wat is wrong here is the J2ee -verbose startup output.

FIRST CASE:

F:\>j2ee -verbose

J2EE server listen port: 1050
Naming service started:1050
Binding DataSource, name = jdbc/EstoreDB, url = jdbc:cloudscape:rmi:CloudscapeDB
;create=true
Binding DataSource, name = jdbc/DB1, url = jdbc:cloudscape:rmi:CloudscapeDB;crea
te=true
Binding DataSource, name = jdbc/InventoryDB, url = jdbc:cloudscape:rmi:Cloudscap
eDB;create=true
Binding DataSource, name = jdbc/DB2, url = jdbc:cloudscape:rmi:CloudscapeDB;crea
te=true
Binding DataSource, name = jdbc/Cloudscape, url = jdbc:cloudscape:rmi:Cloudscape
DB;create=true
Binding DataSource, name = jdbc/XACloudscape, url = jdbc/XACloudscape__xa
Binding DataSource, name = jdbc/XACloudscape__xa, dataSource = COM.cloudscape.co
re.RemoteXaDataSource@41fab6
Starting JMS service...
Initialization complete - waiting for client requests
Binding: < JMS Destination : jms/Queue , javax.jms.Queue >
Binding: < JMS Destination : jms/Topic , javax.jms.Topic >
Binding: < JMS Cnx Factory : jms/QueueConnectionFactory , Queue , No properties
>
Binding: < JMS Cnx Factory : QueueConnectionFactory , Queue , No properties >
Binding: < JMS Cnx Factory : TopicConnectionFactory , Topic , No properties >
Binding: < JMS Cnx Factory : jms/TopicConnectionFactory , Topic , No properties
>
Starting web service at port: 8000
Starting secure web service at port: 7000
Apache Tomcat/4.0
//**********************************************************
//--------------ERROR reading java.io.FileInputStream@f052d5
************************************************************
At Line 46 /web-app/servlet/servlet-name/

Starting web service at port: 9191
Apache Tomcat/4.0
***********************************************************
--------------ERROR reading java.io.FileInputStream@757337
************************************************************
At Line 46 /web-app/servlet/servlet-name/

Loading jar:/F:/j2eesdk/repository/groundzer0/applications/ConverterApp102808245
4573Server.jar
J2EE server startup complete.

------------END OF FILE---------------------------------

Moreover i started the J2EE SERVER and opened the browser
to direct to URL http://127.0.0.1:8080....it gave error page not found then again i point out the URL to
http://127.0.0.1:9191 again same error.

SECOND CASE:

 I deplyed the simple application which is given in J2ee SDK Guide named "CONVERTER" followed all steps as it is. following was the error during deplyment:::

F:\>deploytool
Starting Deployment tool, version 1.3.1
(Type 'deploytool -help' for command line options.)
Deploy the application in F:\j2eesdk\adeel\ConverterEJB.ear on the server localh
ost saving the client jar as F:\j2eesdk\adeel\ConverterEJBClient.jar
Sender object Deploy Tool : Deploy ConverterEJB on localhost
Remote message: Contacted Server....
Remote message: Application ConverterEJB transferred.
Remote message: ConverterEJB has 1 ejbs, 0 web components to deploy.
Remote message: Deploying Ejbs....
Remote message: Processing beans ....
Remote message: Compiling wrapper code ....
Remote message: Compiling RMI-IIOP code ....
Remote message: Making server JARs ....
Remote message: Making client JARs ....
Remote message: Deployment of ConverterEJB is complete..
Sender object Deploy Tool : client code at http://127.0.0.1:9191/ConverterEJB
Client.jar
Cannot download URL http://127.0.0.1:9191/ConverterEJBClient.jar
Status: 404

PLEASE HELP ME AND REPLY AS SOON AS POSSIBLE OR MAIL ME AT

javafarmer@rediffmail.com

The Guide seems to be an out of date copy. The ports for RI Tomcat are 8000 for http and 7000 for https (as shown in your log). 9191 is the second http service, serving out application and client jars.

Tomcat has a queer way of logging. I'd think that error is from the XML parser. Mmmm, what does that tell us?

Check your Web application to see if you have any duplicate entries *or* different entries with the same name (like a JSP names x and a servlet named x as well). If you do, differentiate the names.