For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 3 replies, 2 voices, and was last updated 20 years, 6 months ago by
.
-
Posts
-
Hi,
I have configured a Datasource and Connection pool in the weblogic server. I am using a MS-Access Db and have the sun jdbc odbc driver configured in the connection pool. I notice that the weblogic.jar is required for wrapping the pool connection object which is weblogic.jdbc.wrapper.PoolConnection. So I included the weblogic.jar in the classpath of the server startweblogic.cmd file.
But when try to run the application, I am able to get a handle to the Datasource using JNDI lookup, but the next step to retrieve the connection from the datasource is throwing the java.lang.NoClassDefFoundError: weblogic/jdbc/wrapper/PoolConnection error.
Is there anything I need to set in the Myeclipse env for weblogic server configuration to get this working.
Pls Advice.
Thanks,
SriSri,
First some clarification, are you running WebLogic from MYEclipse or from your .cmd script? It sounded to me like you were using the .cmd script, but I wanted to clarify.Secondly, what code is throwing the PoolConnection exception? Is it test code you are running locally in Eclipse or is it code in your web application, running under WebLogic that is barfing?
Hi,
I configured the class path in the .cmd file and running the weblogic from MyEclipse. Even when I try running the server directly from the .cmd file outside Myeclipse, I get the same error.
I am running a test code which is a part of my web application which when deployed using Myeclipse into Weblogic environment is throwing the error.
-Sri
I configured the class path in the .cmd file and running the weblogic from MyEclipse.
MyEclipse does not use the .cmd file to launch WebLogic. You need to configure WebLogic’s connector in MyEclipse to match what you have in the .cmd file.
Even when I try running the server directly from the .cmd file outside Myeclipse, I get the same error.
Ok, then my first suggestion is to get WebLogic working standalone first, THEN copy all the settings into the WebLogic connector.
