I'm using evaluation version of Weblogic 8.1 and Sybase for my project. I have
created a managed server and trying to create a database connection pool. However,
i encounter the following error:
Distributed Management [1 exceptions] Error creating connection pool
sybasePool2:
Cannot load driver class: com.sybase.jdbc2.jdbc.SybDriver
I have added the above driver to the classpath. However, this problem still occurred.
If i set the target server to the default server (not managed server), it works.
It only happened in the managed server.
I have the following questions:
Is there any limitation on the evaluation version of weblogic that might caused
this problem?
Any suggestion to solve this problem?
Thanx in advance.
Regards,
Joey
Note: this question has been posted in this newsgroup before:
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jdbc&item=18651&utag=
The eval. copy doesn't have any restriction that would affect this.
You need both jConnect.jar and jconn2.jar in your classpath.
Post by Joey
I'm using evaluation version of Weblogic 8.1 and Sybase for my project. I have
created a managed server and trying to create a database connection pool. However,
Distributed Management [1 exceptions] Error creating connection pool
Cannot load driver class: com.sybase.jdbc2.jdbc.SybDriver
I have added the above driver to the classpath. However, this problem still occurred.
If i set the target server to the default server (not managed server), it works.
It only happened in the managed server.
Is there any limitation on the evaluation version of weblogic that might caused
this problem?
Any suggestion to solve this problem?
Thanx in advance.
Regards,
Joey
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jdbc&item=18651&utag=
Thanks for your reply, Stephen.
However, I've added both drivers in my classpath, but it still doesn't work. Any
idea of other solutions?
Regards,
Joey
Post by Stephen Felts
The eval. copy doesn't have any restriction that would affect this.
You need both jConnect.jar and jconn2.jar in your classpath.
Post by Joey
I'm using evaluation version of Weblogic 8.1 and Sybase for my project.
I
have
Post by Joey
created a managed server and trying to create a database connection
pool.
However,
Post by Joey
Distributed Management [1 exceptions] Error creating connection pool
Cannot load driver class: com.sybase.jdbc2.jdbc.SybDriver
I have added the above driver to the classpath. However, this problem
still occurred.
Post by Joey
If i set the target server to the default server (not managed server),
it
works.
Post by Joey
It only happened in the managed server.
Is there any limitation on the evaluation version of weblogic that
might
caused
Post by Joey
this problem?
Any suggestion to solve this problem?
Thanx in advance.
Regards,
Joey
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jdbc&item=18651&utag=
Post by Joey
Thanks for your reply, Stephen.
However, I've added both drivers in my classpath, but it still doesn't work. Any
idea of other solutions?
The class path the server uses is constructed as a commandline argument by the
startup script. The environment variable "CLASSPATH" is not used. However, if
you set an environment variable PRE_CLASSPATH, the startup script will it's value
to the classpath argument. Eg:
set PRE_CLASSPATH=\my_directory\jConnect.jar;\my_directory\jconn2.jar;
Joe
Post by Joey
Regards,
Joey
Post by Stephen Felts
The eval. copy doesn't have any restriction that would affect this.
You need both jConnect.jar and jconn2.jar in your classpath.
Post by Joey
I'm using evaluation version of Weblogic 8.1 and Sybase for my project.
I
have
Post by Joey
created a managed server and trying to create a database connection
pool.
However,
Post by Joey
Distributed Management [1 exceptions] Error creating connection pool
Cannot load driver class: com.sybase.jdbc2.jdbc.SybDriver
I have added the above driver to the classpath. However, this problem
still occurred.
Post by Joey
If i set the target server to the default server (not managed server),
it
works.
Post by Joey
It only happened in the managed server.
Is there any limitation on the evaluation version of weblogic that
might
caused
Post by Joey
this problem?
Any suggestion to solve this problem?
Thanx in advance.
Regards,
Joey
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jdbc&item=18651&utag=