HELP!!! Cannot deploy J2EE application with Oracle JDBC driver...

Hi,
I am writing a J2EE application which (in theory, at least)
connects to an Oracle 9i database.
I have written a simple Java test app utilising only the
java.sql package classes (e.g. Connection, ResultSet) to directly
connect to the database. As long as the classes12.zip is in the
CLASSPATH it works fine.
Now I have written an Enterprise application (SessionBean,
Remote and Home interface and Client) which I am attempting to
deploy via deploytool.
If I include just the client jar and EJB jar in the application
it deploys okay but when I run the application (using runclient)
it produces the following error:
java.lang.NoClassDefFoundError: oracle/jdbc/OracleDriver
(It is nested within other error output but that is the core
issue).
However if I try to include the JAR libraries into the app
(classes12.jar and nls_charset.jar from $ORACLE_HOME/jdbc/lib),
then I get the following output from deploytool when I hit the
"deploy" (or "redeploy") button:
Deployment error: invalid entry compressed size
(expected 14411 but got 14580 bytes)
Can someone please tell me what is going on???
How can I deploy the J2EE application including the Oracle
JDBC Driver???
My only other option at the moment is to place all the function-
-ality in the client and not use the J2EE framework.
Any help is greatly appreciated.
Regards,
Ben New
Leftclick Software Development
[email protected]

OK Ben,
I admit I'm a bit confused. Let me see if I understand where you're
coming from.
You have written a J2EE application that includes a session bean,
correct? If so, your session bean needs to be deployed to an EJB
container. What container are you using? The Oracle 9i database
has an embedded EJB container which (theoretically) you can use.
However, as far as I know, Oracle recommends you use OC4J as the
EJB container. So again I ask, what EJB container are you using?
If, as you say, you are new to EJB, then I think you should
immediately start working wiht OC4J as your EJB container.
Did you look at the tutorial link I gave in my previous post? It
explains -- step by step -- how to create, deploy and run a J2EE
application using OC4J as the EJB container. It also has links to
introductory material for people without little knowledge of J2EE
and EJB.
I have 9iAS Enterprise Edition and 8.1.7.1.0 database server (and
OC4J) installed on my SUN machine. I cannot find any of the
utilities you mention -- "j2eeadmin","runclient" or "deploytool".
What Oracle software have you installed? What are the versions?
What platform are you using?
A J2EE application (according to the specification from SUN)
consists of modules. A module can either be a client module or an
EJB module. A client module can either be a java application client
or a web-based client (servlet or JSP). A J2EE application usually
contains one client module and one EJB module. A J2EE application
needs to be deployed to a J2EE container.
Hopefully the J2EE picture is becoming clearer. I think you need
to read some introductory material regarding J2EE if you intend
to become proficient at it.
I feel that you are under the impression that a J2EE application
is a glorified JDBC application. It isn't (as far as I'm aware).
Good Luck,
Avi.

Similar Messages

Deploying J2EE application with MDB

Hi,
I am looking for a solution to deploy a J2EE application with MDB and the resource provider as well. For now, I only see the solution to manually create a resource provider by the EM enterprise console or to add the resource provider into the application.xml in the oc4j instance.
Any help appreciated
Peter

Hi,
This looks like an incorrect AQ JMS Jar file. Please contact the AQ team if this is a known issue and if required log a tar against AQ.
Thanks
Raja

CLassCastException with oracle.jdbc.driver.OracleCallableStatement

Hello,
I get a ClassCastException when I try to execute a Stored Procedure with WL6.1
and the JDriver.
I have a servlet who intanciate a Bean and call to his execute() method in this
way:
Context ctx = null;
Hashtable ht = new Hashtable();
Connection conn = null;
ht.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
try {
ctx = new InitialContext(ht);
javax.sql.DataSource ds = (javax.sql.DataSource)ctx.lookup(connPool);
conn = ds.getConnection();
conn.setAutoCommit(true);
SvcEmpEstObt empEstObt = new SvcEmpEstObt();
empEstObt.setMaxRows(100);
empEstObt.setConnection(conn);
//Get parameters from Http Get and set the JB
empEstObt.setEmpRut(request.getParameter("rut"));
empEstObt.setEmpTimeStamp(request.getParameter("timestamp"));
//Execute Service
empEstObt.execute();
/* ********* the execute() method of the jb is listed here */
public int execute() throws ClassNotFoundException, SQLException{
intreturnedRows = 0;
try {if (connection == null){
try {Class.forName(driver);
} catch (ClassNotFoundException e) {
System.err.println("ClassNotFoundException: " + e);
throw e;
connection = DriverManager.getConnection(url, user, password);
row = -1;
srv_message = String.valueOf(maxRows);
String sp = "{call SvcEmpEstObt_Pkg.SvcEmpEstObt(?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}";
oracle.jdbc.driver.OracleCallableStatement procout = (oracle.jdbc.driver.OracleCallableStatement)
connection.prepareCall(sp); // The exception is here
procout.registerOutParameter(1, Types.VARCHAR);
procout.setString(1, srv_message);
procout.setString(2, empRut);
procout.setString(3, empTimeStamp);
procout.registerOutParameter(4, Types.VARCHAR);
procout.registerOutParameter(5, Types.VARCHAR);
procout.registerOutParameter(6, Types.INTEGER);
int elemSqlType = OracleTypes.INTEGER;
int elemMaxLen = 0;
procout.registerIndexTableOutParameter(7, maxRows, elemSqlType, elemMaxLen);
elemSqlType = OracleTypes.VARCHAR;
elemMaxLen = 30;
// register the OUT parameter
procout.registerIndexTableOutParameter(8, maxRows, elemSqlType, elemMaxLen);
elemSqlType = OracleTypes.VARCHAR;
elemMaxLen = 21;
// register the OUT parameter
procout.registerIndexTableOutParameter(9, maxRows, elemSqlType, elemMaxLen);
elemSqlType = OracleTypes.INTEGER;
elemMaxLen = 0;
// register the OUT parameter
procout.registerIndexTableOutParameter(10, maxRows, elemSqlType, elemMaxLen);
// execute the call
procout.execute();
sqlWarning = procout.getWarnings();
srv_message = procout.getString(1);
returnStatus = new Integer(srv_message.substring(0,1)).intValue();
dagMessage = new DagMessage();
dagMessage.oracleMessage(srv_message);
// access the value using JDBC default mapping
empEstTitulo = procout.getString(4);
empEstUniv = procout.getString(5);
empEstNivel = procout.getInt(6);
curCodigo = (BigDecimal[]) procout.getPlsqlIndexTable(7);
curNombre = (String[]) procout.getPlsqlIndexTable(8);
curFecha = (String[]) procout.getPlsqlIndexTable(9);
curDuracion = (BigDecimal[]) procout.getPlsqlIndexTable(10);
// close the statement
procout.close();
if (curCodigo == null) {
return 0;
} else {
return curCodigo.length;
} catch (SQLException e) {
SQLException ex = e;
System.err.println("\n--- SQLException caught ---\n");
while (ex != null) {
System.err.println("Message: " + ex.getMessage ());
System.err.println("SQLState: " + ex.getSQLState ());
System.err.println("ErrorCode: " + ex.getErrorCode ());
ex = ex.getNextException();
System.out.println("");
throw e;
Does Someone has an idea why it happens ?

Hans,
Could you give us the whole text of exception?
Regards,
Slava Imeshev
"Hans" <[email protected]> wrote in message
news:[email protected]...
>
It Works! Thanx a lot ....
I was working with a previous version of my App ... I fixed the problemand now
i can Cast to weblogic.jdbc.vendor.oracle.OracleCallableStatement,
But ...
I get the following Exception:
SQL Exception:
registerIndexTableOutParameter is not supported by the
underlying JDBC driver weblogic.jdbc.pool.Connection
What I need to do ?
/* this is what i`m trying to make */
weblogic.jdbc.vendor.oracle.OracleCallableStatement procout =(weblogic.jdbc.vendor.oracle.OracleCallableStatement)
connection.prepareCall(sp);
procout.registerOutParameter(1, Types.VARCHAR);
procout.setString(1, srv_message);
procout.setString(2, empRut);
procout.setString(3, empTimeStamp);
procout.registerOutParameter(4, Types.VARCHAR);
procout.registerOutParameter(5, Types.VARCHAR);
procout.registerOutParameter(6, Types.INTEGER);
int elemSqlType = OracleTypes.INTEGER;
int elemMaxLen = 0;
procout.registerIndexTableOutParameter(7, maxRows, elemSqlType,elemMaxLen);
>
elemSqlType = OracleTypes.VARCHAR;
elemMaxLen = 30;
// register the OUT parameter
procout.registerIndexTableOutParameter(8, maxRows, elemSqlType,elemMaxLen);
>
elemSqlType = OracleTypes.VARCHAR;
elemMaxLen = 21;
// register the OUT parameter
procout.registerIndexTableOutParameter(9, maxRows, elemSqlType,elemMaxLen);
>
elemSqlType = OracleTypes.INTEGER;
elemMaxLen = 0;
// register the OUT parameter
procout.registerIndexTableOutParameter(10, maxRows, elemSqlType,elemMaxLen);
>
>
"Hans" <[email protected]> wrote:
Thanx Slava,
But I have the same problem again...
I replace oracle.jdbc.driver.OracleCallableStatement with
weblogic.jdbc.vendor.oracle.OracleCallableStatement
and I get the same ClassClastException in
weblogic.jdbc.vendor.oracle.OracleCallableStatement procout =
(weblogic.jdbc.vendor.oracle.OracleCallableStatement)
connection.prepareCall(sp);
Any ideas ??
"Slava Imeshev" <[email protected]> wrote:
Hi Hans,
You can not cast returned object to
oracle.jdbc.driver.OracleCallableStatement
when accessing oracle db via connection pool.
It can be casted to weblogic.jdbc.vendor.oracle.OracleCallableStatement.
Here is a list of methods supported by this interface:
void clearParameters() throws java.sql.SQLException;
void registerIndexTableOutParameter(int i, int j, int k, int l) throws
java.sql.SQLException;
void registerOutParameter(int i, int j, int k, int l) throws
java.sql.SQLException;
java.sql.ResultSet getCursor(int i) throws java.sql.SQLException;
java.io.InputStream getAsciiStream(int i) throws
java.sql.SQLException;
java.io.InputStream getBinaryStream(int i) throwsjava.sql.SQLException;
java.io.InputStream getUnicodeStream(int i) throwsjava.sql.SQLException;
>>>
Regards,
Slava Imeshev
"Hans" <[email protected]> wrote in message
news:[email protected]...
Hello,
I get a ClassCastException when I try to execute a Stored Procedurewith
WL6.1
and the JDriver.
I have a servlet who intanciate a Bean and call to his execute()
method
in
this
way:
Context ctx = null;
Hashtable ht = new Hashtable();
Connection conn = null;
ht.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFact
or
y");
try {
ctx = new InitialContext(ht);
javax.sql.DataSource ds = (javax.sql.DataSource)ctx.lookup(connPool);
conn = ds.getConnection();
conn.setAutoCommit(true);
SvcEmpEstObt empEstObt = new SvcEmpEstObt();
empEstObt.setMaxRows(100);
empEstObt.setConnection(conn);
file://Get parameters from Http Get and set the JB
empEstObt.setEmpRut(request.getParameter("rut"));
empEstObt.setEmpTimeStamp(request.getParameter("timestamp"));
file://Execute Service
empEstObt.execute();
/* ********* the execute() method of the jb is listed here */
public int execute() throws ClassNotFoundException, SQLException{
intreturnedRows = 0;
try {if (connection == null){
try {Class.forName(driver);
} catch (ClassNotFoundException e) {
System.err.println("ClassNotFoundException: " + e);
throw e;
connection = DriverManager.getConnection(url, user, password);
row = -1;
srv_message = String.valueOf(maxRows);
String sp = "{call SvcEmpEstObt_Pkg.SvcEmpEstObt(?, ?, ?, ?, ?, ?,?, ?,
oracle.jdbc.driver.OracleCallableStatement procout =(oracle.jdbc.driver.OracleCallableStatement)
connection.prepareCall(sp); // The exception is here
procout.registerOutParameter(1, Types.VARCHAR);
procout.setString(1, srv_message);
procout.setString(2, empRut);
procout.setString(3, empTimeStamp);
procout.registerOutParameter(4, Types.VARCHAR);
procout.registerOutParameter(5, Types.VARCHAR);
procout.registerOutParameter(6, Types.INTEGER);
int elemSqlType = OracleTypes.INTEGER;
int elemMaxLen = 0;
procout.registerIndexTableOutParameter(7, maxRows, elemSqlType,elemMaxLen);
elemSqlType = OracleTypes.VARCHAR;
elemMaxLen = 30;
// register the OUT parameter
procout.registerIndexTableOutParameter(8, maxRows, elemSqlType,elemMaxLen);
elemSqlType = OracleTypes.VARCHAR;
elemMaxLen = 21;
// register the OUT parameter
procout.registerIndexTableOutParameter(9, maxRows, elemSqlType,elemMaxLen);
elemSqlType = OracleTypes.INTEGER;
elemMaxLen = 0;
// register the OUT parameter
procout.registerIndexTableOutParameter(10, maxRows, elemSqlType,elemMaxLen);
// execute the call
procout.execute();
sqlWarning = procout.getWarnings();
srv_message = procout.getString(1);
returnStatus = new Integer(srv_message.substring(0,1)).intValue();
dagMessage = new DagMessage();
dagMessage.oracleMessage(srv_message);
// access the value using JDBC default mapping
empEstTitulo = procout.getString(4);
empEstUniv = procout.getString(5);
empEstNivel = procout.getInt(6);
curCodigo = (BigDecimal[]) procout.getPlsqlIndexTable(7);
curNombre = (String[]) procout.getPlsqlIndexTable(8);
curFecha = (String[]) procout.getPlsqlIndexTable(9);
curDuracion = (BigDecimal[]) procout.getPlsqlIndexTable(10);
// close the statement
procout.close();
if (curCodigo == null) {
return 0;
} else {
return curCodigo.length;
} catch (SQLException e) {
SQLException ex = e;
System.err.println("\n--- SQLException caught ---\n");
while (ex != null) {
System.err.println("Message: " + ex.getMessage ());
System.err.println("SQLState: " + ex.getSQLState ());
System.err.println("ErrorCode: " + ex.getErrorCode ());
ex = ex.getNextException();
System.out.println("");
throw e;
Does Someone has an idea why it happens ?

Problem with Oracle jdbc driver and jdk1.4

Hi
I have some java code which uses Oracle jdbc driver.
This code works with java 1.1.8, 1.2 & 1.3 but not with java 1.4 !
I have that exception :
java.sql.SQLException: The Network Adapter could not establish the connection
at oracle/jdbc/dbaccess/DBError.check_error(DBError.java)
at oracle/jdbc/driver/OracleConnection.<init>(OracleConnection.java)
at oracle/jdbc/driver/OracleDriver.getConnectionInstance(OracleDriver.java)
at oracle/jdbc/driver/OracleDriver.connect(OracleDriver.java)
at java/sql/DriverManager.getConnection(DriverManager.java:529)
at java/sql/DriverManager.getConnection(DriverManager.java:179)
at SimpleQuery.<init>(SimpleQuery.java:21)
at SimpleQuery.main(SimpleQuery.java:56)
when I try a getConnection...
I've tried all the jdbc drivers provided by Oracle, but it's still the same problem !
Any Idea ?
Thanks

Have you tried the drivers shipped with Oracle9i Db R2? they should work against JDK 1.4
Kuassi
Hi
I have some java code which uses Oracle jdbc driver.
This code works with java 1.1.8, 1.2 & 1.3 but not with java 1.4 !
I have that exception :
java.sql.SQLException: The Network Adapter could not establish the connection
at oracle/jdbc/dbaccess/DBError.check_error(DBError.java)
at oracle/jdbc/driver/OracleConnection.<init>(OracleConnection.java)
at oracle/jdbc/driver/OracleDriver.getConnectionInstance(OracleDriver.java)
at oracle/jdbc/driver/OracleDriver.connect(OracleDriver.java)
at java/sql/DriverManager.getConnection(DriverManager.java:529)
at java/sql/DriverManager.getConnection(DriverManager.java:179)
at SimpleQuery.<init>(SimpleQuery.java:21)
at SimpleQuery.main(SimpleQuery.java:56)
when I try a getConnection...
I've tried all the jdbc drivers provided by Oracle, but it's still the same problem !
Any Idea ?
Thanks

Problems with Oracle jdbc Driver

Hi... I'm trying to connect to my Oracle Database and I get the folowing error:
"package oracle.jdbc.driver does not exist"
I have installed Oracle 9.1.0.2 Database...
The value of the Classpath variable is:
".;c:\oracle\ora92\jdbc\lib"
What could be the problem???...
Thanks in advance.-
Alberto.-

Are you building your application from the command line? Or using a GUI? GUI's will frequently overwrite your CLASSPATH environment variable...
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

Query TImeout with ORACLE JDBC driver

I want to halt an execution of query if an query takes more than specified time. Not only the query should be cancelled but the error should be thrown at client. I am using ORACLE 11g JDBC driver.
I have used statement.setQueryTimeout() for the same. Moreover, my application is an OLTP system handling thousands of calls per second and one call is of 4 to 5 queries. Can anyone explain whether querytimeout will work in this case and its drawbacks if any.

Dear user10366531,
Your question about setQueryTimeout() has been already disscussed in this topic (Setup "QueryThreshold" parameter
(Chris Jenkins aswered).
Best regards,
Gennady

Petstore throws populateServlet error with Oracle thin driver

When i point connection pool to Oracle database, i get the following error. The
data is populated in the database, looks like when petstore is enumerating db
tables and make sure all tables exist, this error is happening. Some how, database
metadata coming as NULL. Has anybody tried petstore with Oracle JDBC driver?
thanks,
PopulateServlet Error:
java.lang.NullPointerException java.lang.NullPointerException at com.sun.j2ee.blueprints.tools.populate.web.PopulateServlet.checkTables(PopulateServlet.java:276)
at com.sun.j2ee.blueprints.tools.populate.web.PopulateServlet.doGet(PopulateServlet.java:127)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2456)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

I believe that you do not have weblogicaux.jar in your classpath.
-Selvan
Laurie Cohen wrote:
Im using Solaris 2.7 with WLS 5.1.0 and Commerce Server 2.0.1 with
current service packs on both. JDK 1.2.1_04 and the Oracle thin driver
(classes111.zip which I am told is the only one supported in this
configuration). Has anyone seen this problem? Is it that the driver is
using 1.1 and I only have 1.2 installed?
devapp01% java -classpath
/usr/local/weblogic/classes:/usr/local/weblogic/license utils.t3dbping
t3://localhost:7601 username password "" oracle.jdbc.driver.OracleDriver
jdbc:oracle:thin:@10.200.201.110:1521:q01c
Connecting to WebLogic with the WebLogic JDBC Driver
Exception in thread "main" java.lang.NoClassDefFoundError:
com/sun/java/util/collections/ArrayList
at weblogic.kernel.Kernel.declareProperties(Kernel.java:253)
at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:107)
at weblogic.common.T3Client.<init>(T3Client.java:218)
at weblogic.common.T3Client.<init>(T3Client.java:269)
at weblogic.common.T3Client.<init>(T3Client.java:323)
at weblogic.jdbcbase.t3.Driver.connect(Driver.java:121)
at java.sql.DriverManager.getConnection(Compiled Code)
at java.sql.DriverManager.getConnection(DriverManager.java:106)
at utils.t3dbping.main(t3dbping.java:115)
Thanks,
Laurie

Is Oracle JDBC driver thread safe

Is the Oracle JDBC driver thread safe?

Seems that this is not totally true.
We have a Problem with Oracle JDBC driver 9.2.0.5.0 (thin)
Using an IBM JDK 1.4
Szenario:
Thread 1 access to a CLOB via
ResulSet.getCharacterStream(int)
Thread 2 normal access via some select and
ResulSet.getString(int)
(Both using the same connection)
The following threads appear to be in a circular deadlock.
Further information can be found by looking in the Overall Thread Analysis
section of this tool.
Multi-threaded deadlock 1:
"Servlet.Engine.Transports : 6" of (sys:0x39778800) (TID:0x104590D0)
Holding Resource: oracle.jdbc.ttc7.TTC7Protocol@1ADEB358/1ADEB360
Thread Waiting: "ProcessNotificationTask" (sys:0x3C51FC18) (TID:0x103B4C40)
"ProcessNotificationTask" of (sys:0x3C51FC18) (TID:0x103B4C40)
Holding Resource: oracle.jdbc.driver.OracleConnection@1AE45160/1AE45168
Thread Waiting: "Servlet.Engine.Transports : 6" (sys:0x39778800) (TID:0x104590D0)
4XESTACKTRACE at oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java:2667)
4XESTACKTRACE at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2840)
4XESTACKTRACE at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:608)
4XESTACKTRACE at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:536)
4XESTACKTRACE at com.top_logic.knowledge.service.db.DBKnowledgeBase.getObjectsByAttribute(Unknown Source)
4XESTACKTRACE at oracle.jdbc.ttc7.TTC7Protocol.getLobChunkSize(TTC7Protocol.java:3050)
4XESTACKTRACE at oracle.sql.LobDBAccessImpl.getChunkSize(LobDBAccessImpl.java:687)
4XESTACKTRACE at oracle.sql.CLOB.getChunkSize(CLOB.java:692)
4XESTACKTRACE at oracle.sql.CLOB.getBufferSize(CLOB.java:717)
4XESTACKTRACE at oracle.sql.CLOB.getCharacterStream(CLOB.java:345)
4XESTACKTRACE at oracle.sql.CLOB.characterStreamValue(CLOB.java:1377)
4XESTACKTRACE at oracle.jdbc.driver.OracleStatement.getCharacterStreamValue(OracleStatement.java:5817)
4XESTACKTRACE at oracle.jdbc.driver.OracleResultSetImpl.getCharacterStream(OracleResultSetImpl.java:1230)
It seems that the access to the CLOB needs another,
internal SELECT to the Database and this way
TTC7Protocol and OracleConnection lock out each other.
This only happens on a true multiprocessor machine.
We tried to reprodcue it on a Single Processor
and some HyperThreading Machine but had no real sucess.
Now where can I sumbit this as a Bug ?

Deploying .jar with Oracle JDBC thin driver

I was just experimenting with a Java application that uses an Oracle JDBC driver. It runs fine in JDeveloper. However, when I deploy it to a .jar and run it from a Windows XP Command Prompt I get:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\xxx\deploy>java -jar testme.jar
Exception in thread "main" java.lang.NullPointerException
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
Is there anything special I need to do to the Deploy file? I tried including the the classes111 manifest to no avail.

Hi,
Ensure that the JVM being used is the same or at least same spec level that you built your project. JDeveloper 9.0.3 uses VM's compatible with 1.3.1 by default. It is possible that your OS path has another VM that the cmd line defaults to. Use a java -version to check this.
Also ensure that you include Oracle JDBC as a project library and when you go to create a JAR file (either simple archiver or a Client Jar) that you include the Oracle JDBC libraries from the Dependency Analyzer. I assume this is probably the missing step since your are deploying to a Jar and not an app server where you would put the driver libraries in the app server classpath.

[Oracle JDBC Driver]This driver is locked for use with embedded application

Hi
I installed Sun Java Studio Enterprise 8, and am trying to connect to my Oracle database using the attached tutorial code.
The code compiles fine, but I get the following error whenever I run the file: [Oracle JDBC Driver]This driver is locked for use with embedded application
I don't understand what is happening.
Using the Runtime navigation panel on the upper left of the IDE screen, I can right-click and connect to the database, and navigate database files, using the Oracle JDBC Driver that came with JSE8.
Name: Oracle Driver
Driver: com.sun.sql.jdbc.oracle.OracleDriver
Database URL: jdbc:sun:oracle://JAZZPUP:1521;SID=REPO
If the driver is installed, and can be used to connect to a database by right-clicking on the database definition in the Runtime panel, why can't I connect to it just using java code in the IDE. I would expect both methods to work or to fail, not one of each using the same IDE.
Many thanks and take care,
Shayne
import java.sql.*;
public class CreateCoffees {
public static void main(String args[]) {
//String url = "jdbc:mySubprotocol:myDataSource";
String url = "jdbc:sun:oracle://JAZZPUP:1521;SID=REPO";
Connection con;
String createString;
createString = "create table COFFEES " +
"(COF_NAME VARCHAR(32), " +
"SUP_ID INTEGER, " +
"PRICE FLOAT, " +
"SALES INTEGER, " +
"TOTAL INTEGER)";
Statement stmt;
try {
//Class.forName("myDriver.ClassName");
Class.forName("com.sun.sql.jdbc.oracle.OracleDriver");
} catch(java.lang.ClassNotFoundException e) {
System.err.print("ClassNotFoundException: ");
System.err.println(e.getMessage());
try {
//con = DriverManager.getConnection(url, "myLogin", "myPassword");
con = DriverManager.getConnection(url, "login", "password");
stmt = con.createStatement();
stmt.executeUpdate(createString);
stmt.close();
con.close();
} catch(SQLException ex) {
System.err.println("SQLException: " + ex.getMessage());
} //end class CreateCoffees
---

There are two similar threads:
http://swforum.sun.com/jive/thread.jspa?threadID=61327&tstart=0
http://swforum.sun.com/jive/thread.jspa?threadID=51057&messageID=188210
To summarize - the DataDirectDriver that is shipped with the IDE seems to be locked to be used inside the IDE only because of some licensing issues etc..
That's weird, I agree. I will raise a question on reasons for such a behavior.
The solution would be to use Oracle's own driver, that is distributed at no charge from their web site - http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html
HTH,
Kirill

Help - Could not load 'oracle.jdbc.driver.OracleDriver ...

I'm using oci8 to connect to the Oracle database.
URL: jdbc:oracle:oci8:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(PORT=1527)(HOST=testhost)))(CONNECT_DATA=(SID=fnoe2pa)))
When I tried to start the weblogic server, I got the following errors:
Can you suggest what I should do next (step-wise)??? Thanks, Bobby
<Sleeping in createResource()>
####<15/08/2002 14:09:43> <Error> <JDBC> <qawebmethods> <myserver>
<main> <system> <> <001060> <Cannot startup connection pool
"pool/test_myapp" weblogic.common.ResourceException:
Could not load 'oracle.jdbc.driver.OracleDriver
If this is a type-4 JDBC driver, it could occur if the JDBC
driver is not in the system CLASSPATH.
If this is a type-2 JDBC driver, it may also indicate that
the Driver native layers(DBMS client lib or driver DLL)
have not been installed properly on your system
or in your PATH environment variable.
This is most likely caused by one of the following:
1. The native layer SO, SL, or DLL could not be found.
2. The file permissions on the native layer SO, SL, or DLL
have not been set properly.
3. The native layer SO, SL, or DLL exists, but is either
invalid or corrupted.
For more information, read the installation documentation
for your JDBC Driver, available from:
http://e-docs.bea.com
     at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:212)
     at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:134)
     at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:705)
     at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
     at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:650)
     at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:360)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:285)
     at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:239)
     at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:199)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy31.updateDeployments(Unknown Source)
     at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2977)
     at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:372)
     at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:360)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy42.start(Unknown Source)
     at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
     at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
     at weblogic.management.Admin.finish(Admin.java:644)
     at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
     at weblogic.Server.main(Server.java:35)
>
####<15/08/2002 14:09:43> <Info> <JDBC> <qawebmethods> <myserver>
<main> <system> <> <001082> <Creating Data Source named
jdbc/test_myapp for pool pool/test_myapp>
####<15/08/2002 14:09:43> <Info> <JDBC> <qawebmethods> <myserver>
<main> <system> <> <001070> <Checking existence of connection pool
pool/test_myapp requested by user system>
####<15/08/2002 14:09:43> <Error> <JDBC> <qawebmethods> <myserver>
<main> <system> <> <001059> <Error during Data Source creation:
weblogic.common.ResourceException: DataSource(jdbc/test_myapp) can't
be created with non-existent Pool (connection or multi)
(pool/test_myapp)>
####<15/08/2002 14:09:50> <Info> <EJB> <qawebmethods> <myserver>
<main> <system> <> <010008> <EJB Deploying file: myapp-ejb.jar>
####<15/08/2002 14:09:50> <Warning> <J2EE> <qawebmethods> <myserver>
<main> <system> <> <160007> <You are running WebLogic Server with J2EE
1.3 features enabled. The implementation of specific J2EE 1.3 features
(EJB 2.0, JSP 1.2, Servlet 2.3, and J2EE Connector Architecture 1.0)
in BEA WebLogic Server 6.1 is of a non-final version of the
appropriate specification. It is subject to change in future releases
once the specification becomes finalized. This may cause application
code developed for BEA WebLogic Server 6.1 that uses the new features
of J2EE 1.3 to be incompatible with the J2EE 1.3 platform supported in
future releases of BEA WebLogic Server.>
####<15/08/2002 14:09:59> <Error> <J2EE> <qawebmethods> <myserver>
<main> <system> <> <160001> <Error deploying application myapp-ejb:
Unable to deploy EJB: Counter from myapp-ejb.jar:
The DataSource with the JNDI name: jdbc/test_myapp could not be
located. Please ensure that the DataSource has been deployed
successfully and that the JNDI name in your EJB Deployment descriptor
is correct.
>
####<15/08/2002 14:09:59> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101053> <[HTTP myserver] Loading web app: myapp>
####<15/08/2002 14:09:59> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101059> <[myserver] Loading myapp from WAR file:
C:\bea\wlserver6.1\.\config\mydomain\applications\.wlnotdelete\wlap31483\myapp.war>
####<15/08/2002 14:09:59> <Warning> <J2EE> <qawebmethods> <myserver>
<main> <system> <> <160007> <You are running WebLogic Server with J2EE
1.3 features enabled. The implementation of specific J2EE 1.3 features
(EJB 2.0, JSP 1.2, Servlet 2.3, and J2EE Connector Architecture 1.0)
in BEA WebLogic Server 6.1 is of a non-final version of the
appropriate specification. It is subject to change in future releases
once the specification becomes finalized. This may cause application
code developed for BEA WebLogic Server 6.1 that uses the new features
of J2EE 1.3 to be incompatible with the J2EE 1.3 platform supported in
future releases of BEA WebLogic Server.>
####<15/08/2002 14:09:59> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101031>
<[WebAppServletContext(1412030,myapp,/myapp)] extracting classfiles to
C:\bea\wlserver6.1\config\mydomain\applications\.wlnotdelete\wlap31483\WEB-INF\_tmp_war_myapp:>
####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101032>
<[WebAppServletContext(1412030,myapp,/myapp)] extracted classfiles
successfully...>
####<15/08/2002 14:10:04> <Info> <HTTP Session> <qawebmethods>
<myserver> <main> <system> <> <100037> <Creating SessionContext of
type: memory for webapp: /myapp>
####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101047>
<[WebAppServletContext(1412030,myapp,/myapp)] registering classpath
servlet with initArgs 'null'>
####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101047>
<[WebAppServletContext(1412030,myapp,/myapp)] registering getior
servlet with initArgs 'null'>
####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101047>
<[WebAppServletContext(1412030,myapp,/myapp)] registering tunneling
servlets with initArgs 'wl-dispatch-policy=direct'>
####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101047>
<[WebAppServletContext(1412030,myapp,/myapp)] registering JSPServlet
with initArgs '[JspConfig:
verbose=true,packagePrefix=jsp_servlet,-compiler=javac,compileFlags=,workingDir=C:\bea\wlserver6.1\config\mydomain\applications\.wlnotdelete\wlap31483\WEB-INF\_tmp_war_myapp,pageCheckSeconds=1,superclass=null,keepgenerated=false,precompileContinue=false,compilerSupportsEncoding=true,encoding=null,defaultfilename=index.jsp,compilerclass=null,noTryBlocks=false]'>
####<15/08/2002 14:10:04> <Debug> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101097> <Registering ServletContext:
"myapp:/myapp">
####<15/08/2002 14:10:04> <Info> <J2EE> <qawebmethods> <myserver>
<main> <system> <> <160003> <Deployed : myapp>
####<15/08/2002 14:10:04> <Info> <HTTP> <qawebmethods> <myserver>
<main> <system> <> <101133> <Initializing WEB server myserver>
####<15/08/2002 14:10:04> <Notice> <Management> <qawebmethods>
<myserver> <main> <system> <> <141052> <Application Poller started for
development server.>
####<15/08/2002 14:10:04> <Notice> <WebLogicServer> <qawebmethods>
<myserver> <ListenThread> <system> <> <000202> <ListenThread listening
on port 7001>
####<15/08/2002 14:10:04> <Info> <NT Performance Pack> <qawebmethods>
<myserver> <ListenThread> <system> <> <000000> <NATIVE: NTSocketMuxer
was built on Nov 1 2001 16:39:28
>
####<15/08/2002 14:10:04> <Notice> <WebLogicServer> <qawebmethods>
<myserver> <SSLListenThread> <system> <> <000202> <SSLListenThread
listening on port 7002>
####<15/08/2002 14:10:05> <Notice> <Management> <qawebmethods>
<myserver> <main> <system> <> <141030> <Starting discovery of Managed
Server... This feature is on by default, you may turn this off by
passing -Dweblogic.management.discover=false>
####<15/08/2002 14:10:05> <Notice> <WebLogicServer> <qawebmethods>
<myserver> <main> <system> <> <000331> <Started WebLogic Admin Server
"myserver" for domain "mydomain" running in Development Mode>
####<15/08/2002 14:10:11> <Info> <NT Performance Pack> <qawebmethods>
<myserver> <ExecuteThread: '14' for queue: 'default'> <> <> <000000>
<Allocating: '2' NT reader threads>
####<15/08/2002 14:10:13> <Info> <HTTP> <qawebmethods> <myserver>
<ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'> <system>
<> <101047> <[WebAppServletContext(5367844,console,/console)] actions:
init>
####<15/08/2002 14:10:18> <Info> <HTTP> <qawebmethods> <myserver>
<ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'> <system>
<> <101047> <[WebAppServletContext(5367844,console,/console)]
FileServlet: init>
####<15/08/2002 14:10:18> <Info> <HTTP> <qawebmethods> <myserver>
<ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'> <system>
<> <101047> <[WebAppServletContext(5367844,console,/console)]
FileServlet: Using standard I/O>

"thorick" <[email protected]> wrote in message news:<[email protected]>...
Most likely, the OCI libraries could not be loaded.
Before continuing down this path, is there any reason
why you want to use an OCI based Driver as opposed to the
all Java Oracle thin driver ?There is indeed a valid reason for my choice.
I am currently connecting to the Oracle "Rdb" 7.0 database (located on
VMS) - not Oracle Oracle.
The SQL Service software we're currently using is version 7.1. This
version works well with the OCI8 driver (when connecting to the
database from Windows NT). This version of SQL Service however does
NOT work for the THIN driver (unless we upgrade the SQL Service to
version 7.1.5.5 - which we're not prepared to do so because it is not
stable enough from our previous test/trials). SQLSRV Version 7.1.5.5
works for THIN driver but it will result in uncommitted
transactions/unresolved connection/stopping of listener issues and
there is a need to restart the service from time to time. Oracle has
since confirmed that this is a bug that they have yet to resolve...
So we have to stick to OCI8 (THICK) for the time being. I would really
appreciate it very much if you can tell me the various OCI libraries
that I need to load (in terms of WebLogic Server config file settings
etc..).
By the way I have already installed the Oracle 8 client software on
the NT server (where WebLogic Server is) and I have also set up the
relevant SID (using the Net8 Assistant) that points to the Oracle Rdb
database on the VMS. I have also tried using SQL*Plus to connect to
the database and I can connect properly to the database. But WebLogic
simply doesn't seem to load the software.
Help...
Regards,
Bobby Brown, writing from Australia.

Error -8 when deploying JHeadStart application to Oracle Application Server

Hi,
I have developed an application using Oracle JHeadstart 10.1.3 Preview Version 10.1.3.0.78
We have Oracle Application Server 10g running in AS400. I created a connection to the server and tested. It shows the connection success.
I am trying to deploy my application to Oracle Application Server 10g but getting the following error:
Closing connection to Oc4jDcmServlet
#### DCM command did not complete successfully (-8)
#### HTTP return code was -8
Exit status of DCM servlet client: -8
Elapsed time for deployment: 30 seconds
#### Deployment incomplete. #### 25-Jul-2006 2:21:44 PM
I developed applications in JDev10.1.2 and deployed to the same server (Oracle Application Server 10g) without any problem.
But if I want to deploy application from JDev10.1.3 then I am having this error.
Can anybody help me? what might be the problem?
Thanks
Syed

Syed,
Did you generate your application with service -level property "JSP version" set to "1.2"? If not, you cannot deploy your app to a J2EE 1.3 application server like Oracle AS 10.1.2.
Steven Davelaar,
JHeadstart Team.

Error while deploying adf application on oracle cloud service

hello, i hv registered oracle cloud service for java and database. i hv created simple adf application in which there are 2 jsf pages only linked together. I m using oracle jdeveloper 11gr2. so i hv created ear file for deployment on cloud. i deployed adf application on cloud using java console. But, after uploading application, deployment was failed. I tried 3 times this, but the result was same. I checked log, where i got 3 warnings in whitelist log and error in deploy log. Those are as follows:
Warnings in whitelist log:
2013-04-14 06:57:11 CDT: Starting action "API Whitelist"
2013-04-14 06:57:11 CDT: API Whitelist started
2013-04-14 06:57:12 CDT: WARNING - There are 3 warnings(s) found for Testapp.ear.
2013-04-14 06:57:12 CDT: WARNING - Path:Testapp.ear (3 Warnings)
2013-04-14 06:57:12 CDT: WARNING - Path:Testapp.ear (3 Warnings)
2013-04-14 06:57:12 CDT: WARNING - Path:Test_ViewController_webapp.war (3 Warnings)
2013-04-14 06:57:12 CDT: WARNING - Path:WEB-INF**** (1 Warning)
2013-04-14 06:57:12 CDT: WARNING - 1:Recommended child element "login-config" missing under element /
javaee:web-app.
If you want to make your application public, you can have empty
<login-config/> in your web.xml. If you need authentication then you must
have <login-config> and its child <auth-method> element in web.xml.
Without this element(<login-config>), users may be challenged by SSO, but
the application code will be executed as anonymous user only. Line No:4.
2013-04-14 06:57:12 CDT: WARNING - Path:WEB-INF**** (2 Warnings)
2013-04-14 06:57:12 CDT: WARNING - 1:Recommended child element "jsp-descriptor" missing under element /
orcl-weblogic:weblogic-web-app.
If you have a JSP file that is not pre-compiled, The compilation errors
could be shown on the browser. It is recommended to include
<jsp-descriptor><verbose>false<****><****-descriptor> in weblogic.xml.
Line No:2.
2013-04-14 06:57:12 CDT: WARNING - 2:Recommended child element "session-descriptor" missing under element /
orcl-weblogic:weblogic-web-app.
You will be required to have distinct cookie-path, if multiple
applications are accessed with in the same SSO session or if you have
multiple applications with different auth-method(CLIENT-CERT, FORM, BASIC)
in the same service instance.
Line No:2.
2013-04-14 06:57:12 CDT: WARNING - Testapp.ear had 3 warning(s).
2013-04-14 06:57:12 CDT: INFO - Whitelist validation has completed with 0 error(s) and 3 warning(s).
2013-04-14 06:57:12 CDT: Whitelist validation passed.
2013-04-14 06:57:12 CDT: "API Whitelist" complete: status SUCCESS
and Error in deploy log:
2013-04-14 06:57:12 CDT: Starting action "Deploy Application"
2013-04-14 06:57:12 CDT: Deploy Application started
2013-04-14 06:57:15 CDT: weblogic.application.ModuleException: Failed to load webapp: Test-ViewController-context-root because of DeploymentException: java.lang.ClassNotFoundException: oracle.adf.view.faces.bi.webapp.MapProxyServlet
2013-04-14 06:57:15 CDT: WL action state: failed
2013-04-14 06:57:15 CDT: Action FAILED with WL action state: failed
2013-04-14 06:57:15 CDT: Check the server log of your Java cloud service for more info about the failure.
2013-04-14 06:57:16 CDT: Application deployment failed.
2013-04-14 06:57:16 CDT: "Deploy Application" complete: status FAILED
I am using jdeveloper 11gr2, so pls dont tell me to use jdeveloper 11gr1. because, i hv already developed an application for my final year B.Tech and i cant migrate to previous release. So there is only one way for me by generating ear file and deploying from console.
So,
I m not getting what is the problem and what will be solution for this?
What should i do?
What changes should required?
pls, help me to get out from this problem !!!!!

Well, I guess you have a problem here. Check http://multikoop.blogspot.de/2012/12/deploying-adf-applications-into-oracle.html and from this
>
Note: In its current stage Oracle Java Cloud Service runs WebLogic Server 10.3.6 with the appropriate Runtime ADF 11.1.1.6. Deployment of ADF 11gR2 Applications is currently not supported. Beside this limitation some ADF Features are not supported on the Oracle Cloud. According to the Oracle Cloud Documentation it is not supported to use the following ADF features
ADF Desktop Integration
ADF mBean
ADF MDS (Seeded customizations or cross-session personalization)
ADF Mobile
ADF Active Data Services (=> No real-time ADF Web Apps in Oracles Cloud)
ADF Business Components services interfaces (web services) or events
ADF Data Controls for BI, Essbase, BAM, and JMX
Further there are some restrictions which are good to know I think
No Java Mail API (=>Sending Mails is prohibited)
No File system access by deployed applications (=>Writing files is prohibited)
No Direct use of Oracle JDBC Driver APIs
No Java Message Service (JMS)
Max Size for deployment archive 95MB
>
I hope for you that the information from the blog has changes in the meantime (blog is from end of last year). Check the current doc for the cloud ...
Timo

The error when I deploy ess application with SDM

SOS!!!when I deploy ess application with SDM(ESS05P_1-10002965.sca), It failed.please help me.
The trace file:
#1.5#00145ED221BE00F7000000B90011A07C0004421B32EEBBA8#1198584492898#com.sap.engine.services.webdynpro.WebDynproContainer##com.sap.engine.services.webdynpro.WebDynproContainer#J2EE_ADMIN#15220####0f7fa990b2e211dca62200145ed221be#SAPEngine_Application_Thread[impl:3]_173##0#0#Error#1#/System/UserInterface#Java###Failed to deploy application '''' for deployment state listener ''''.
[EXCEPTION]
#3#sap.com/essauaddr#com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook#com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to deploy the file '/usr/sap/EP1/DVEBMGS02/j2ee/cluster/server0/./temp/webdynpro/public/sap.com/essauaddr/webdynpro/Applications/com.sap.xss.hr.per.au.address.Per_Address_AU/Per_Address_AU.xml' into the database. Reason: Development Object 'sap.com/ess~au' contains already same repository content. Hint: fully qualified name of the repository VMO must be globally unique.
     at com.sap.tc.webdynpro.repository.deploy.RepositoryUpdateManager.checkVMOsExistInOtherDC(RepositoryUpdateManager.java:504)
     at com.sap.tc.webdynpro.repository.deploy.RepositoryUpdateManager.deployRepositoryContent(RepositoryUpdateManager.java:98)
     at com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook.onDeploy(RepositoryContainerHook.java:232)
     at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1007)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
     at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
     at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:215)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#00145ED221BE00F7000000BB0011A07C0004421B32EF7CEE#1198584492948#com.sap.engine.services.deploy##com.sap.engine.services.deploy#J2EE_ADMIN#15220####0f7fa990b2e211dca62200145ed221be#SAPEngine_Application_Thread[impl:3]_173##0#0#Error#1#/System/Server#Java#deploy_5029##Exception in operation deploy with application sap.com/essauaddr.#2#deploy#sap.com/essauaddr#
#1.5#00145ED221BE00F7000000BC0011A07C0004421B32EF7F24#1198584492949#com.sap.engine.services.deploy##com.sap.engine.services.deploy#J2EE_ADMIN#15220####0f7fa990b2e211dca62200145ed221be#SAPEngine_Application_Thread[impl:3]_173##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation deploy with application sap.com/essauaddr.
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:394)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:294)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
     at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:215)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Cannot deploy application sap.com/essauaddr.
     at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:330)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
     ... 13 more
Caused by: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/essauaddr. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
     at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1016)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
     at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
     ... 15 more

Check these below links
https://forums.sdn.sap.com/click.jspa?searchID=7622331&messageID=4611860
https://forums.sdn.sap.com/click.jspa?searchID=7622331&messageID=4562067
https://forums.sdn.sap.com/click.jspa?searchID=7622331&messageID=4258751
https://forums.sdn.sap.com/click.jspa?searchID=7622331&messageID=4474525
https://forums.sdn.sap.com/click.jspa?searchID=7622331&messageID=4543091
https://forums.sdn.sap.com/click.jspa?searchID=7622331&messageID=4368694
reward points if helpful

Oracle JDBC Driver to J2EE

I'm trying to install an Oracle JDBC driver to connect my application with my oracle database server, but I'm having some problems. I downloaded the drive classes from the Oracle website, but now now I need to know how to configure my j2ee server to stabilish a connection with my database.
Can anyone help me?
Thanks a lot,
Ricardo - from Brazil

Hi Ricardo,
Which JDBC driver are you trying to install. I mean which type driver?.
Anyways i am sending a general page where in you can find the installation procedure for the Oracle JDBC driver installation. Hope it is helpful to you.
Regards,
G. Gowrishankar
This link is for Installing Oracle Thin Driver
http://www.lbl.gov/Education/CSEE/cup/Su01/Sum01Web/Mo/java/orionprimer/install_jdbc.htm
This link if for installing Oracle JDBC driver
http://home.clara.net/dwotton/dba/jdbc_test.htm

HELP!!! Cannot deploy J2EE application with Oracle JDBC driver...

Similar Messages

Maybe you are looking for