Thanks Apu,

It seems that having a jdbc connection in the web admin tool creates more of a problem. I've removed all web connections and it seems to work. Thanks again Apu, I really appreciate it!


Regards, -Jeremie

Apu Shah wrote:

by doing a system.loadlibrary, you are using the native drivers. this
call should not be needed at all if you are using the thin driver, which
is a pure java (type 4)  driver.

you should be able to connect to the database using the thin driver in
the following way


            Driver d =
(Driver)Class.forName("oracle.jdbc.OracleDriver").newInstance();
            DriverManager.registerDriver(d) ;
            String connectionStr = "jdbc:oracle:thin:@192.168.0.25:1521:oradb"
            java.sql.Connection conn =
DriverManager.getConnection(connectionStr,user,pass)

that's it. no loadLibrary call should be needed at all.

apu

On Wed, 18 Feb 2004 16:14:25 -0500
blais <[EMAIL PROTECTED]> wrote:



Thanks again Apu.

Here is my core dump since i've removed the database configuration
from the web admin tool.


HTTP Status 500 -


---------------------------------------------------------------------
---

*type* Exception report

*message*

*description* _The server encountered an internal error () that prevented it from fulfilling this request._

*exception*

javax.servlet.ServletException: Servlet execution threw an exception
        filters.ExampleFilter.doFilter(ExampleFilter.java:149)

*root cause*

java.lang.UnsatisfiedLinkError: no ojdbc14 in java.library.path
        java.lang.ClassLoader.loadLibrary(ClassLoader.java:1491)
        java.lang.Runtime.loadLibrary0(Runtime.java:788)
        java.lang.System.loadLibrary(System.java:834)
        HelloWorldExample.doGet(HelloWorldExample.java:65)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
        filters.ExampleFilter.doFilter(ExampleFilter.java:149)

*note* _The full stack trace of the root cause is available in the Tomcat logs._



Note that this is going through apache. The java command which is causing this error is *System.loadLibrary("ojdbc14")*. in my servlet. Apparently if this call works, then registering an Oracle driver with *DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver()); *will also work. When this error
is received, nothing hangs at all. Thanks again for your help Apu,
you're god send!



Cheers, -jeremie


Apu Shah wrote:




i did not have to add any database connections under the tomcat web
admin tool.

catalina.properties remains the same.

is there a stack trace with an exception in any logs? (ClassNotFound
or any other such exceptions)

could you also describe what symptoms you are seeing? does the app
hang or does it return an error or are you not seeing database
updates....

apu

On Wed, 18 Feb 2004 13:46:21 -0500
blais <[EMAIL PROTECTED]> wrote:





Thanks Apu,

I am using the thin client and it's still not working. I've put
ojdbc14 in common/lib and still nothing. Did you have to add a
database connection under the tomcat web administration tool ? And


if>you did, did you include a path to your ojdbc.jar file?

I'm also wondering if maybe the catalina.properties file should be changed or if it should stay the same.

Kind Regards,
Jeremie

Apu Shah wrote:





i have multiple webapps connecting to oracle within the same tomcat
instance.

removing ojdbc14.jar from all the webapps WEB-INF/lib and keeping
only one copy of ojdbc14.jar in common/lib works for me on tomcat


5. >>


if you are connecting via oci drivers, make sure that your
LD_LIBRARY_PATH points to your oracle home. i've added the


following>>in my catalina.sh startup file:


export ORACLE_BASE=/usr/local/oracle
export ORACLE_HOME=$ORACLE_BASE/product/9.2.0
export ORACLE_TERM=xterm
export NLS_LANG=AMERICAN;
export ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data
export
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib:$ORACLE_HOME/jdb


c/>>lib:/


lib:/usr/lib:/usr/local/lib

if you're using thin drivers, this should not be required.

apu

On Wed, 18 Feb 2004 12:59:41 -0500
blais <[EMAIL PROTECTED]> wrote:







Hey All.

I've been trying to write a servlet that uses a jdbc driver to




connect>




to a remote Oracle server. I've manage to compile my own


standalone>>>app to connect to the DB. I included the ojdbc14.jar in
my>>>


classpath>and everything seemed to work fine. I can't seem to get
the same code>to work in a servlet with tomcat 5, and I'm pretty


sure>>it's because>tomcat does not know where ojdbc14.jar is. I've
put it>>in server/lib>and /bin and common/lib, but to no avail. Using the>>web tool, I've>added the ojdbc14.jar file with multiple
paths and>>i've still got>nothing. Any help would be appreciates.






I'm running this on Linux with tomcat 5, Oracle 9i and apache




1.3.29.>




Regards,
Jeremie

--
You live and learn. At any rate, you live.

-----------------------------------------------------------------


-->>>

-->To unsubscribe, e-mail:


[EMAIL PROTECTED]>>

For additional commands, e-mail:


[EMAIL PROTECTED]>>>








------------------------------------------------------------------


--->>To unsubscribe, e-mail:
[EMAIL PROTECTED]>>For additional commands,
e-mail: [EMAIL PROTECTED]>>






-------------------------------------------------------------------


-->To unsubscribe, e-mail: [EMAIL PROTECTED]


For additional commands, e-mail: [EMAIL PROTECTED]






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to