Q

Problems starting JCo in Tomcat

An HTTP Status 500 error message pops up when attempting to use JCo in Tomcat. Expert Austin Sincock suggests some possible reasons.

I've got a problem using jco.jar with Tomcat. When I start my *.jsp-site I recieve following error-message (shortened):
HTTP Status 500 -
type: Exception report
message: description The server encountered an internal error () that prevented it from fulfilling this request.
exception: org.apache.jasper.JasperException: com/sap/mw/jco/IRepository

My site just had some parameters to a class that does the rest. But when I use the same class under Forte for Java 4, CE the whole thing works just perfect. Both Tomcat and Forte are using the same jre. What is it? Is it my Tomcat? I'm using 4.1. Should I reinstall it?
Using JCo in a Tomcat Web application can be a little tricky. Make sure that you have a copy of sapjco.jar in the tomcat/common/lib directory or the tomcat/shared/lib directory (depending on Tomcat version). Also, make sure that no other pointers to sapjco.jar exist in your Tomcat startup classpath. Finally, ensure that you are using the latest version of JCo (2.0.8 or higher). If the error message indicates that you are using jco.jar, thenyou are on an older release of JCo which may explain the problems you are having in Tomcat.
This was first published in July 2005

Dig deeper on SAP Java and J2EE

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

SearchManufacturingERP

SearchOracle

SearchDataManagement

SearchAWS

SearchBusinessAnalytics

SearchCRM

SearchContentManagement

SearchFinancialApplications

Close