Could be anything. May not be a JDBC error. That is the first thing you want to isolate where the problem is coming from. I would take these steps:
I assume this is an RPC call. If so... 1. Just remove all JDBC calls from the service and return a stub value in the method. If it still breaks, then you have an issue unrelated to JDBC. 2. Either way, I would invoke your service class from a command-line unit test, or something like it. Get it to work outside of Axis, then deploy it. 3. If it works outside of Axis, but breaks after being deployed, then you can start to look at all of the layers the go into calling a webservice, OS, network, Java, etc... 4. Also, do a search on the tomcat lists for this error string. You may find more info there. Do the same search for the jdbc driver you are using. BTW, It is unusual to load a db driver in the constructor of a class. Usually a DataSource or a db pool such as poolman or jakarta dbcp is a static member. While it won't fix your problem, this method will speed up your service considerably. Sat, 2002-12-07 at 16:22, Andrey Sadovykh wrote: > Hello, > I'm using AXIS and Tomcat. > I implemented a class MyClass that should be connected database > In constructor of service I'm invoking JDBC function to load a database > driver. > When I call any function of this service Tomcat goes down with following > exception: > java.net.SocketException: Connection reset by peer: JVM_recv in socket input > stream read. > > How to solve it? > > Can anybody provide me with a sample or hints, how to implement a service > connected to a database? > > It would be more than great. > > Thanks in advance, > > Andrey > > > >
