the problem:
i want to access an oracle DB via a weblogic server remotely from a
standard java client (just to avoid implementing the connection
pooling stuff by my own).
the question:
do i really need to use the 35MB weblogic.jar and additionally oracles
classes12.zip in order to get this to work? are there any additional
documents about that?
using the fat weblogic jar and the oracle driver works half and half:
i can execute successfully an SQL statement but the server throws
the following exception:
<Error> <socket> <000424> <IOException on socket:
weblogic.rjvm.t3.T3JVMConnection@1c80d1c, fd: 27
java.net.SocketException: Connection reset
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at weblogic.socket.PosixSocketMuxer.readBytesProblem(PosixSocketMuxer.java:876)
at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:767)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:694)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
i am using:
- WLInitialContextFactory for JNDI lookup
- oracle 8.1.7
- weblogic7.1
- j2sdk 1.4.1
thank you for a hint.
cheers,
chris
the client is 1.4.1. the server is running on 1.4.1 too i think,
but that is not the problem.
cheers,
chris
Mitesh Patel <Mitesh...@bea.com> wrote in message news:<3EEDCF04...@bea.com>...