RMI JDBC

I am working on a client server project where the
server has access to a MS Access database, i wish to
transfer ResultSets to the Client program but cannot
because of serialisation. ok.....
>
I have in the passed broken down the resultSet on the
server side and sent the data as a Vector of Vectors,
but this is a very messy process.
You are on the right track....
This may be the only way to do it. By this i mean that the resultset data will need to be transferred to another data-structure or "data-holding" component (lke vectors, arrays, etc), and then transferring THAT across.
Do you know of some other way to transfer ResultSets
across, or is there some other type of object which
can query a database and has the ability to be
serialised.Not that i know of. Have you tried to subclass the Resultset class and make it implement serializable? It might be possible.
Another far-fetched idea: Aglets that transfer the resultset object(s) back to you.........but that's overkill

Similar Messages

Problem with get ResultSet from rmi jdbc method. Help.

Hi,
I am writing a rmi jdbc server. I got all the rmi methods working, but I am trying to get the data from the ResultSet. After the query, I set the fields in the serialiable class and return it back to the client. However, I noticed that it does called init(), but not the setField calls. When it calls the first setField in the serialiable class, the method is never called. Can anyone give some guidance.
Thanks,
Rage
This method is called from the client to set all the data in the Serialiable class and return it to the client.
public Collection fetchResultSet() throws RemoteException
System.out.println("Entering fetchResultSet");
Collection resultSetColl = new ArrayList();
QueryResultSet recordset;
try
int rowCount = 0;
ResultSetMetaData rsmd = rs.getMetaData(); // Get data dictionary information
int columnCount = rsmd.getColumnCount();
System.out.println("got column count");
System.out.println("" + rowCount + " rows, " +
columnCount + " columns");
if (rs == null) System.out.println("rs is null");
if (rs.next())
System.out.println("Parsing RS");
recordset = new QueryResultSet();
for (int i = 1; i <= columnCount; i++)
System.out.println("set Fields = "+ rs.getString(i) );
//recordset.setField(i,rs.getString(i));
String strValue = rs.getString(i);
recordset.setField(i,strValue);
System.out.println("Added recordset" );
resultSetColl.add(recordset);
catch (Exception e)
System.out.println(e.getMessage());
closeResultSet();
return resultSetColl;
Here is my Serializable Class
import java.io.*;
import java.sql.*;
public class QueryResultSet implements Serializable
private String Field1;
private String Field2;
private String Field3;
private String Field4;
private String Field5;
private String Field6;
private String Field7;
private String Field8;
private String Field9;
private String Field10;
private String Field11;
private String Field12;
private String Field13;
/** Creates a new instance of QueryResultSet */
public QueryResultSet()
init();
public void init()
System.out.println("QueryResultSet INIT()");
Field1 = "";
Field2 = "";
Field3 = "";
Field4 = "";
Field5 = "";
Field6 = "";
Field7 = "";
Field8 = "";
Field9 = "";
Field10 = "";
Field11 = "";
Field12 = "";
Field13 = "";
public String getField(int nField)
System.out.println("QueryResultSet getField()");
System.out.println("getField 1 = " + Field1);
if (nField ==1)
return Field1;
else if (nField == 2)
return Field2;
else if (nField == 3)
return Field3;
else if (nField == 4)
return Field4;
else if (nField == 5)
return Field5;
else if (nField == 6)
return Field6;
else if (nField == 7)
return Field7;
else if (nField == 8)
return Field8;
else if (nField == 9)
return Field9;
else if (nField == 10)
return Field10;
else if (nField == 11)
return Field11;
else if (nField == 12)
return Field12;
else if (nField == 13)
return Field13;
return null;
public void setField(int nField, String strField)
System.out.println("QueryResultSet setField()");
System.out.println("field #" String.valueOf(nField) " = " + strField);
if (nField == 1)
Field1 = strField;
else if (nField == 2)
Field2 = strField;
else if (nField == 3)
Field3 = strField;
else if (nField == 4)
Field4 = strField;
else if (nField == 5)
Field5 = strField;
else if (nField == 6)
Field6 = strField;
else if (nField == 7)
Field7 = strField;
else if (nField == 8)
Field8 = strField;
else if (nField == 9)
Field9 = strField;
else if (nField == 10)
Field10 = strField;
else if (nField == 11)
Field11 = strField;
else if (nField == 12)
Field12 = strField;
else if (nField == 13)
Field13 = strField;
}

You need to give us some information more. Like what rdbms are you using, what driver and how are you trying to access the resultset from java.
I do not know what are you using. One thing I can tell you for sure is that the execute method returns a boolean. If you need a resultset you should run executeQuery.
Kiros

Problem with clloudscape rmi jdbc driver

I am using Cloudscape rmi jdbc driver, where Cloudscape runs as
a separate server. I am using WL6.1 running on Red Hat Linux
7.1. I defined a Cloudscape connection pool and data source. I
have to start Cloudscape before WebLogic or I get the following
exception:
<Feb 18, 2002 11:39:42 PM EST> <Error> <JDBC> <Cannot startup
connection pool "EStoreConnectionPool"
weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: Connection refused to host: localhost;
nested exception is:
java.net.ConnectException: Connection refused
at RmiJdbc.RJDriver.connect(RJDriver.java:149)
at java.sql.DriverManager.getConnection
(DriverManager.java:512)
etc.
No surprises here: However if I start Cloudscape first and
WebLogic second, I get the following message in Weblogic:
Starting WebLogic Server ....
<Feb 19, 2002 12:58:21 AM EST> <Notice> <Management>
<Loading configuration file ./config/mydomain/config.xml ...>
<Feb 19, 2002 12:58:43 AM EST> <Notice> <WebLogicServer>
<Starting WebLogic Admin Server "myserver" for domain "mydomain">
<Feb 19, 2002 12:59:00 AM EST> <Notice> <Management>
<Starting discovery of Managed Server... This feature is on by
default, you may turn this off by passing
-Dweblogic.management.discover=false>
This copy of Cloudscape is licensed for DEVELOPMENT ONLY.
It is a violation of the license agreement to deploy this version
in a production application.
For information about licensing Cloudscape for application
deployment, contact [email protected] or call
888/595-2821 ext. 7664.
Additional licensing information can be found at
http://www.cloudscape.com/licensing.
<Feb 19, 2002 12:59:31 AM EST> <Notice> <Management>
<Application Poller started for development server.>
<Feb 19, 2002 12:59:31 AM EST> <Notice> <WebLogicServer>
<ListenThread listening on port 7001>
<Feb 19, 2002 12:59:31 AM EST> <Notice> <WebLogicServer>
<SSLListenThread listening on port 7002>
<Feb 19, 2002 12:59:32 AM EST> <Notice> <WebLogicServer>
<Started WebLogic Admin Server "myserver" for domain "mydomain"
running in Development Mode>
The console running cloudscape then contains this message:
This copy of Cloudscape is licensed for DEVELOPMENT ONLY.
It is a violation of the license agreement to deploy this version
in a production application.
For information about licensing Cloudscape for application
deployment, contact [email protected] or call
888/595-2821 ext. 7664.
Additional licensing information can be found at
http://www.cloudscape.com/licensing.
Tue Feb 19 00:56:43 EST 2002: [RmiJdbc]
COM.cloudscape.core.JDBCDriver registered in DriverManager
Tue Feb 19 00:56:44 EST 2002: [RmiJdbc] Binding RmiJdbcServer...
Tue Feb 19 00:56:44 EST 2002: [RmiJdbc] No installation of RMI
Security Manager...
Tue Feb 19 00:56:46 EST 2002: [RmiJdbc] RmiJdbcServer bound in
rmi registry
WARNING: Cloudscape (instance
c013800d-00ec-1cf6-94ca-007f00000100) is
attempting to boot the database
/app/cloudscape_3.6/database/acme/estore even
though cloudscape (instance c013800d-00ec-1cca-ed1d-007f00000100)
may still be active. Only one instance of cloudscape should boot
a database at a time. Severe and non-recoverable corruption can
result and may have already occurred.
Well, it looks like I'm damned if I do and damned if I don't.
Any suggestions?

Actually, it happened because Cloudscape was not properly shut down. Thanks for
responding. I was having some troble with the stopCS script, but its OK now.
"Laurent Goldsztejn" <[email protected]> wrote:
>
Hi Douglass,
The evaluation version of Cloudscape is limited to one concurrent user
per session,
so only one instance of cloudscape can be running at a time. The problem
reported
here can occur if you try to run more than once instance of any product
that
uses Cloudscape -- including WLS or Cloudview. This evaluation version
of Cloudscape
is intended for test purposes only.
This error can also occur on Solaris if you stop the server using ctrl-C
or ctrl-D,
which causes a database lock to remain in place after the server has
stopped.
You can get rid of it by deleting $BEA_HOME/wlserver6.1/samples/eval/cloudscape/data/demo/db.lck
The safest way to stop the server is to use the Admin console or the
SHUTDOWN
command from the command line.
Laurent Goldsztejn
Developer Relations Engineer
BEA Support

RMI & JDBC ResultSet

I am developing a project
The basic archeiecture is like this:
a reporting tool
a virtualDB
a real DB
the reporting tool request for data from virtualDB, the virtualDB actually fetch the result for it.
The virtualDB is a remote object using RMI which can be called in the reporting tool(stub)
the virtualDB is connecting to the real DB through JDBC-ODBC driver.
Now comes the problem, when the virtualDB has the ResultSet which is return by JDBC-ODBC. I cannot pass the ResultSet from remote site to my reporting tool, at run time, it will throw NotSerializable Exception, I guess this is because the JDBC-ODBC ResultSet does not implement that interface.
So is there any way I can solve this problem to allow the reporting tool(client) receive the ResultSet that VirtualDB has got???
Thanks in advance, any comment would be a great help for me!!!

I can think of two ways:
I can unpack the resultset at the remote site, and repack them into a new ResultSet which implements the Serializble interface. However, in the case I still dont know how to let me client receive the new ResultSet, quite lost...
Another way, write all datas into XML, and pass the XML from remote site to reporting tool. It can work, but I want it to be efficient. This way is not efficient enough for me, I guess, and I do not want the overhead of creating XML.

RMI + JDBC + file transference - URGENT!!

Ol� pessoal tenho uma d�vida a qual tenho que utilizar comandos JDBC de forma remota e tenho que fazer a transfer�ncia de arquivos, algu�m tem id�ia de como fazer isso?
Entre RMI e sockets achei sockets mais complicado, o problema que RMI n�o � nada simples, algu�m poderia me ajudar?
Hello people, I have a doubt which I have that to use commands JDBC of remote form and have that to make the transference of archives, somebody has idea of as to make this?
Between RMI and sockets a think that sockets more complicated, and the problem is RMI is not simple, somebody could help me?

wanderley.drumond wrote:
Ol� pessoal tenho uma d�vida a qual tenho que utilizar comandos JDBC de forma remota e tenho que fazer a transfer�ncia de arquivos, algu�m tem id�ia de como fazer isso?
Entre RMI e sockets achei sockets mais complicado, o problema que RMI n�o � nada simples, algu�m poderia me ajudar?
Hello people, I have a doubt which I have that to use commands JDBC of remote form and have that to make the transference of archives, somebody has idea of as to make this?
Between RMI and sockets a think that sockets more complicated, and the problem is RMI is not simple, somebody could help me?Please avoid using the highly irritating word "URGENT!!" in your subject line in future.
The first question I would ask is where are these files now? Are they in a database? Or are you trying to put them into a database.
The second question is what is the client? Remote? Web? Internet?
If the files are going in/out of the database directly then the simplest solution is just straight JDBC. If there is some complication (like the client is web-based) then maybe something else is required.
I don't see RMI being a solution here. Possibly but I doubt it (on the basis that if the scenario means that the RMI solution was feasible then I would think the direct JDBC solution would also be feasible) . Maybe FTP.
I think you may need to get some English help or try on a Spanish language forum though. We'll see how it goes but I do find your question difficult to understand, I only get a general drift of what you are saying but as demonstrated by my questions above I don't really get the specifics.

Username and password with Access and JDBC application

Hello all,
I have written an application which accesses a MS Access database. I have created a dialog which asks the user for a username and password. I then include the username and password to connect to the database. I have created groups and users in the Access database and have given each user different privaleges. However, when I run my application, any user can get any privelage. I am missing something. Thanks in advance.

// ConnectToDatabase.java
// Copyleft (c) 2001 RatKing
// ��Java Bean
// E-mail: [email protected]
// This can use in JSP or Java Application or Applet
// AFTER you have setup the ODBC source in Windoz.
package rat;
import java.sql.*;
import java.util.*;
public class ConnectToDatabase{
private String driverClass = "sun.jdbc.odbc.JdbcOdbcDriver"; // JDBC-ODBC Bridge Driver
private String dbURL = "jdbc:odbc:yourdbname"; // the name of your ODBC Source's Database
private String userName = "yourname"; // user ID
private String password = "yourpassword"; // user password
private Connection connection = null; // Connection to the Database
private Statement statement = null; // Statement object
public ConnectToDatabase () {
// ��
public Connection getConnection() throws ClassNotFoundException, SQLException {
if(connection != null) {
return connection;
Class.forName(driverClass);
connection = DriverManager.getConnection(dbURL, userName, password);
return connection;
} // getConnection()
public void closeConnection() throws SQLException {
if (connection != null) {
// Makes all changes made since the previous commit/rollback permanent
// and releases any database locks currently held by this Connection object.
if (!connection.getAutoCommit())
connection.commit();
closeStatement();
connection.close();
connection = null;
} // closeConnection()
* If not connected to database...connect to database, create a statement,
* and, return the Statement.
protected void createStatement() throws SQLException, Exception {
if(statement == null) {
Connection connection = getConnection();
statement = connection.createStatement();
* This method executes a statement and returns true or false. Any type
* of Statement may be executed by this command.
public boolean execute(String sqlString) throws SQLException, Exception {
if(statement == null){
createStatement();
boolean returnValue = statement.execute(sqlString);
return returnValue;
* This method executes the statement and returns a ResultSet from
* execution of the query. Only a SELECT Statemet is applicable here.
public ResultSet executeQuery(String sqlString) throws SQLException, Exception {
if(statement == null){
createStatement();
ResultSet rs = statement.executeQuery(sqlString);
return rs;
* This method executes update statements and returns a count of
* the updates. Only a INSERTS, DELETES, and UPDATES are applicable here.
* In addition, SQL statements that return nothing such as SQL DDL statements
* can be executed.
public int executeUpdate(String sqlString) throws SQLException, Exception {
if(statement == null){
createStatement();
int returnValue = statement.executeUpdate(sqlString);
return returnValue;
* This method closes the Statement.
public void closeStatement() throws SQLException {
if(statement != null){
statement.close();
statement = null;
* If it is not connected to database, connect to database and
* create a statement and returns the Statement
* @param scrollType should be ResultSet.TYPE_FORWARD_ONLY
* or ResultSet.TYPE_SCROLL_INSENSITIVE
* or ResultSet.TYPE_SCROLL_SENSITIVE
* @param updateType should be ResultSet.CONCUR_READ_ONLY or
* ResultSet.CONCUR_UPDATABLE ;
protected Statement getStatement(int scrollType, int updateType)
throws SQLException, Exception {
Connection connection = getConnection();
// for cloudscape to work with scrollable resultsets, the autocommit
// should be false.
connection.setAutoCommit(false);
Statement statement = connection.createStatement(scrollType,
updateType);
return statement;
* If it is not connected to database, connect to database and
* create a preparestatement and returns the Statement
* @param sqlString queryString to make a statement
* @param scrollType should be ResultSet.TYPE_FORWARD_ONLY
* or ResultSet.TYPE_SCROLL_INSENSITIVE
* or ResultSet.TYPE_SCROLL_SENSITIVE
* @param updateType should be ResultSet.CONCUR_READ_ONLY or
* ResultSet.CONCUR_UPDATABLE ;
protected PreparedStatement getStatement(String sqlString,
int scrollType,
int updateType) throws SQLException,
Exception {
Connection connection = getConnection();
// for cloudscape to work with scrollable resultsets, the autocommit
// should be false.
connection.setAutoCommit(false);
PreparedStatement preparedStatement =
connection.prepareStatement(sqlString, scrollType, updateType);
return preparedStatement;
* this method executes the statement and resuts the resultSet due to
* execution of Statement.
* only SELECT Statemet is applied here.
public ResultSet executeQueryScrollInsensitiveReadOnly(String sqlString,
Vector values) throws SQLException, Exception {
PreparedStatement preparedStatement = getStatement(sqlString,
ResultSet.TYPE_SCROLL_INSENSITIVE,
ResultSet.CONCUR_READ_ONLY);
for (int i = 1; i <= values.size(); i++) {
preparedStatement.setObject(i, values.elementAt(i - 1));
// Execute a SQL statement that returns a single ResultSet.
ResultSet rs = preparedStatement.executeQuery();
return rs;
* this method executes the statement and resuts the resultSet due to
* execution of Statement. only SELECT Statemet is applied here.
public ResultSet executeQueryScrollInsensitiveReadOnly(String sqlString)
throws SQLException, Exception {
Statement statement = getStatement(ResultSet.TYPE_SCROLL_INSENSITIVE,
ResultSet.CONCUR_READ_ONLY);
// Execute a SQL statement that returns a single ResultSet.
ResultSet rs = statement.executeQuery(sqlString);
return rs;
* this method executes the statement and returns the resultSet due to execution
* of Statement. only SELECT Statemet is applied here.
public ResultSet executeQueryScrollForwardOnly(String sqlString,
Vector values) throws SQLException, Exception {
PreparedStatement preparedStatement = getStatement(sqlString,
ResultSet.TYPE_FORWARD_ONLY, ResultSet.CONCUR_READ_ONLY);
for (int i = 1; i <= values.size(); i++) {
preparedStatement.setObject(i, values.elementAt(i - 1));
// Execute a SQL statement that returns a single ResultSet.
ResultSet rs = preparedStatement.executeQuery();
return rs;
* this method executes the statement and returns the resultSet due to
* execution of Statement. only SELECT Statemet is applied here.
public ResultSet executeQueryScrollForwardOnly(String sqlString)
throws SQLException, Exception {
Statement statement = getStatement(ResultSet.TYPE_FORWARD_ONLY,
ResultSet.CONCUR_READ_ONLY);
// Execute a SQL statement that returns a single ResultSet.
ResultSet rs = statement.executeQuery(sqlString);
return rs;
* Method executeQueryScrollSensitiveReadOnly
* @param sqlString String
* @param values Vector
* @return ResultSet returns ResultSet due to statement execution
* @throws Exception
* @throws SQLException
* @see
public ResultSet executeQueryScrollSensitiveReadOnly(String sqlString,
Vector values) throws SQLException, Exception {
PreparedStatement preparedStatement = getStatement(sqlString,
ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_READ_ONLY);
for (int i = 1; i <= values.size(); i++) {
preparedStatement.setObject(i, values.elementAt(i - 1));
// Execute a SQL statement that returns a single ResultSet.
ResultSet rs = preparedStatement.executeQuery();
return rs;
* Method executeQueryScrollSensitiveReadOnly
* @param sqlString
* @return
* @throws Exception
* @throws SQLException
* @see
public ResultSet executeQueryScrollSensitiveReadOnly(String sqlString) throws SQLException, Exception {
Statement statement = getStatement(ResultSet.TYPE_SCROLL_SENSITIVE,
ResultSet.CONCUR_READ_ONLY);
// Execute a SQL statement that returns a single ResultSet.
ResultSet rs = statement.executeQuery(sqlString);
return rs;
//////////////Other things maybe useful ///////////////////
# Refer to Appendix A for more info on configuring the JDBC
# driver via setting of the DRIVER_CLASS and DATABASE_URL properties
#JDBC Driver Class
# for ODBC Driver:
#DRIVER_CLASS=sun.jdbc.odbc.JdbcOdbcDriver
# for Oracle Driver
#DRIVER_CLASS=jdbc.oracle.driver.OracleDriver
# for CloudScape Driver equipped with J2EE reference implementation
#DRIVER_CLASS=RmiJdbc.RJDriver
# for CloudScape Driver equipped with BEA Weblogic Server
DRIVER_CLASS=COM.cloudscape.core.JDBCDriver
#Database URL
# for ODBC URL
#DATABASE_URL=jdbc:odbc:tShirts
# for Oracle URL
#DATABASE_URL=jdbc:oracle:thin:@localhost:1521:ORCL
# for URL with CloudScape equipped with J2EE reference implementation
#DATABASE_URL=jdbc:rmi:jdbc:cloudscape:beeshirtsdb
# for URL with CloudScape equipped with BEA Weblogic Server
DATABASE_URL=jdbc:cloudscape:D:\\weblogic\\eval\\cloudscape\\beeshirts
#UserName to connect to database
UserName=TSHIRTS
#Password to connect to database
Password=TSHIRTS
#otherParameters
SUB_PROPERTIES=
#SQL Query
SQL_QUERY_STATEMENT = SELECT * FROM TSHIRTS.CUSTOMER
#SQL Update , if you run this program please change the id 129 to different value each time
SQL_UPDATE_STATEMENT = INSERT INTO TSHIRTS.CUSTOMER VALUES ('129','Sam','Cheng','S','123 Sam St.', 'C3','Baltimore','MD','20222','4104444444' ,'[email protected]')
#Join STATEMENT
SQL_QUERY_STATEMENT_JOIN = SELECT TSHIRTS.CUSTOMER.*, TSHIRTS.ORDERS.* FROM TSHIRTS.CUSTOMER, TSHIRTS.ORDERS WHERE CUSTOMER.CUSTOMER_ID = ORDERS.CUSTOMER_ID_FK
#OUTER JOIN for ORACLE
#SQL_QUERY_STATEMENT_OUTER_JOIN = SELECT CUSTOMER.* FROM TSHIRTS.CUSTOMER,STATE WHERE CUSTOMER.STATE(+) = STATE.CODE(+)
#OUTER JOIN for MSACCESS
#SQL_QUERY_STATEMENT_OUTER_JOIN = SELECT C.* , S.* FROM CUSTOMER C OUTER JOIN STATE S on C.STATE = S.CODE
#OUTER JOIN for MSACCESS and Cloudscape
SQL_QUERY_STATEMENT_OUTER_JOIN = SELECT C.* , S.* FROM TSHIRTS.CUSTOMER C LEFT OUTER JOIN TSHIRTS.STATE S on C.STATE = S.CODE
#SQL Statement with Like for MSACCESS
#SQL_QUERY_STATEMENT_WITH_LIKE = SELECT CUSTOMER.* FROM CUSTOMER WHERE CUSTOMER.FIRST_NAME LIKE \'*R*\'
#SQL Statement with Like for ORACLE and Cloudscape
SQL_QUERY_STATEMENT_WITH_LIKE = SELECT * FROM TSHIRTS.CUSTOMER WHERE FIRST_NAME LIKE '%R%'
#Prepared QUERY Statement
PREPARED_SQL_QUERY_STATEMENT = SELECT * FROM TSHIRTS.CUSTOMER WHERE FIRST_NAME = ?
PREPARED_SQL_QUERY_STATEMENT_VALUES = Roy
#Prepared Insert
PREPARED_SQL_INSERT_STATEMENT = INSERT INTO TSHIRTS.CUSTOMER VALUES(?,?,?,?,?,?,?,?,?,?,?)
PREPARED_SQL_INSERT_STATEMENT_VALUES =130,John,Hiller,Miller,125 S St.,C6,Baltimore,MD,20100,4104444444,[email protected]
#Prepared Update
PREPARED_SQL_UPDATE_STATEMENT = UPDATE TSHIRTS.STATE SET STATE_NAME = 'California' WHERE CODE = ?
PREPARED_SQL_UPDATE_STATEMENT_VALUES =CA
#Data base schema name
SCHEMA_NAME =TSHIRTS

Java.rmi.MarshalException when getting a Connection from DataSource

Hi, folks!
Whenever I try to get a Connection from a DataSource, I´ve got the following Exception:
"java.rmi.MarshalException: CORBA MARSHAL 0 Maybe; nested exception is:
     org.omg.CORBA.MARSHAL: vmcid: 0x0 minor code: 0 completed: Maybe
CORBA MARSHAL 0 Maybe; nested exception is:
     org.omg.CORBA.MARSHAL: vmcid: 0x0 minor code: 0 completed: Maybe
     at com.sun.corba.se.internal.iiop.ShutdownUtilDelegate.mapSystemException(ShutdownUtilDelegate.java:97)
     at javax.rmi.CORBA.Util.mapSystemException(Util.java:65)
     at weblogic.jdbc.common.internal._RemoteDataSource_Stub.getConnection(Unknown
Source)
     at com.contratacao.model.dao.DAObasico.getConnection(DAObasico.java:42)..."
In fact, the client can retrieve the DataSource´s stub, but just can´t get the
Connection.
Configuration:
1. WLS 8.1 sp2, on Windows XP, with SUN JDK 141_05 (embbeded with WLPlatorm installer)
2. Oracle 9.0.1 on Windows XP, connected through an Oracle JDBC thin driver
3. java Client on Windows XP/2000, with SUN JDK 142_03 (I´ve got the same results
with SUN JDK 141_01. I´m also using wlclient.jar.
Do you have any idea of what is causing this behavior?
I´d appreciate any help. Thanks in advance,
Marcos

"Marcos Medina" <[email protected]> writes:
This is an FAQ. The RMI JDBC driver is not supported in the thin client.
andy
Hi, folks!
Whenever I try to get a Connection from a DataSource, I´ve got the following Exception:
"java.rmi.MarshalException: CORBA MARSHAL 0 Maybe; nested exception is:
     org.omg.CORBA.MARSHAL: vmcid: 0x0 minor code: 0 completed: Maybe
CORBA MARSHAL 0 Maybe; nested exception is:
     org.omg.CORBA.MARSHAL: vmcid: 0x0 minor code: 0 completed: Maybe
     at com.sun.corba.se.internal.iiop.ShutdownUtilDelegate.mapSystemException(ShutdownUtilDelegate.java:97)
     at javax.rmi.CORBA.Util.mapSystemException(Util.java:65)
     at weblogic.jdbc.common.internal._RemoteDataSource_Stub.getConnection(Unknown
Source)
     at com.contratacao.model.dao.DAObasico.getConnection(DAObasico.java:42)..."
In fact, the client can retrieve the DataSource´s stub, but just can´t get the
Connection.
Configuration:
1. WLS 8.1 sp2, on Windows XP, with SUN JDK 141_05 (embbeded with WLPlatorm installer)
2. Oracle 9.0.1 on Windows XP, connected through an Oracle JDBC thin driver
3. java Client on Windows XP/2000, with SUN JDK 142_03 (I´ve got the same results
with SUN JDK 141_01. I´m also using wlclient.jar.
Do you have any idea of what is causing this behavior?
I´d appreciate any help. Thanks in advance,
Marcos

Connecting remote FoxPro dbf file using jdbc odbc bridge driver?

Hi all,
I am new to this topic, (even I read some threads)
I need to access some FoxPro tables (dbf files) and select some data and save to an oracle table. what is the best method to do this?
If I use java as development tool. which other drivers or methods to use beside jdbc-odbc driver?
I read from this link but I didn't understand.
http://java.sun.com/products/jdbc/faq.html#5
"5. How can I use the JDBC API to access a desktop database like Microsoft Access over the network?
Most desktop databases currently require a JDBC solution that uses ODBC underneath. This is because the vendors of these database products haven't implemented all-Java JDBC drivers.
The best approach is to use a commercial JDBC driver that supports ODBC and the database you want to use. See the JDBC drivers page for a list of available JDBC drivers.
The JDBC-ODBC bridge from Sun's Java Software does not provide network access to desktop databases by itself. The JDBC-ODBC bridge loads ODBC as a local DLL, and typical ODBC drivers for desktop databases like Access aren't networked. The JDBC-ODBC bridge can be used together with the RMI-JDBC bridge, however, to access a desktop database like Access over the net. This RMI-JDBC-ODBC solution is free.
"

Another solution by using HXTT DBF, a commercial type 4 JDBC package: You should read Remote Access Questions section at http://www.hxtt.net/en/software/dbf/faq.html#remote .

Using JDBC from an Applet

Hi,
I'm trying to connet to an Oracle database from an Applet, using the oracle jdbc thin driver.
When I'm running the applet with the applet viewer I can connet to the database. But, when I view the applet with Internet explorer 6 with the Microsoft JVM I get an exception:
Error loading class: oracle.jdbc.driver.OracleDriver
java.lang.NoClassDefFoundError
java.lang.ClassNotFoundException: oracle.jdbc.driver.OracleDriver
     at com/ms/vm/loader/URLClassLoader.loadClass(URLClassLoader.java)
     at java/lang/ClassLoader.loadClassInternal (ClassLoader.java)
     at java/lang/Class.forName (Class.java)
     at MyApplet.<init> (MyApplet.java:25)
     at com/ms/applet/BrowserAppletFrame.newInstance (BrowserAppletFrame.java)
     at com/ms/applet/AppletPanel.processSentEvent (AppletPanel.java)
     at com/ms/applet/AppletPanel.processSentEvent (AppletPanel.java)
     at com/ms/applet/AppletPanel.run (AppletPanel.java)
     at java/lang/Thread.run (Thread.java)
I've tried to:
1) Put the driver jar in the same place as the applet
2) expand the jar in the applet's folder
2) Add the jar to the archive attribute of the APPLET tag
3) Add the applet and the content of the jar to a single arhcive
but so far far nothing helped.
Thanks,
Dror B

Hi,
Did you try to use Sun's JVM? Microsoft VM is old, and probably does not contain the classes required by Oracle's driver; besides, it supports only old class format, which has evolved in Sun's JVM.
Another solution is to use the RMI-JDBC driver by http://objectweb.org.
Sincerely,
Sergei Batiuk.

Error configuring and starting Managed Server in WebLogic 10.3

Hi,
I am able to configure and start the Managed Server on windows environment. I am trying to configure Managed Server on linux environment. I am configuring the Managed Server with custom keystore. When I configured the Managed Server I specified the keystore/trustsote information in the Keystores tab of the Admin Console for Managed Server settings. Specified Private Key Alias, Password in SSL tab.But when I am starting the Managed Server from command line, I see the process looking for demo trust files and failing.
Here is the command I run to start the Managed Server:
./startManagedWebLogic.sh MyManagedServer1 https://localhost.localdomain:8443
Below is the console output:
<Mar 11, 2015 12:37:44 PM PDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.45-b01 from Sun Microsystems Inc.>
<Mar 11, 2015 12:37:45 PM PDT> <Info> <Security> <BEA-090065> <Getting boot identity from user.>
Enter username to boot WebLogic server:beaadmin
Enter password to boot WebLogic server:
<Mar 11, 2015 12:37:53 PM PDT> <Info> <Security> <BEA-090908> <Using default WebLogic SSL Hostname Verifier implementation.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/wlserver_10.3/server/lib/DemoTrust.jks.>
<Mar 11, 2015 12:37:53 PM PDT> <Error> <Security> <BEA-090132> <Could not open the keystore file /opt/wlserver_10.3/server/lib/DemoTrust.jks for read access. Exception: java.io.FileNotFoundException: /opt/wlserver_10.3/server/lib/DemoTrust.jks (No such file or directory)>
<Mar 11, 2015 12:37:53 PM PDT> <Warning> <Security> <BEA-090164> <Failed to load trusted certificates from keystore /opt/wlserver_10.3/server/lib/DemoTrust.jks of type jks>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/jre1.6.0_45/lib/security/cacerts.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Mar 11, 2015 12:37:53 PM PDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050 >
<Mar 11, 2015 12:37:54 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
<Mar 11, 2015 12:37:54 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
<Mar 11, 2015 12:37:54 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
<Mar 11, 2015 12:37:54 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
<Mar 11, 2015 12:37:54 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
<Mar 11, 2015 12:37:55 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
<Mar 11, 2015 12:37:55 PM PDT> <Warning> <Security> <BEA-090477> <Certificate chain received from localhost.localdomain - 127.0.0.1 was not trusted causing SSL handshake failure.>
<Mar 11, 2015 12:37:55 PM PDT> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at https://localhost.localdomain:8443.>
<Mar 11, 2015 12:37:55 PM PDT> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
<Mar 11, 2015 12:37:55 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Mar 11, 2015 12:37:55 PM PDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Mar 11, 2015 12:37:55 PM PDT> <Notice> <LoggingService> <BEA-320400> <The log file /h/data/local/base_domain/servers/MyManagedServer1/logs/MyManagedServer1.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Mar 11, 2015 12:37:55 PM PDT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /h/data/local/base_domain/servers/MyManagedServer1/logs/MyManagedServer1.log00015. Log messages will continue to be logged in /h/data/local/base_domain/servers/MyManagedServer1/logs/MyManagedServer1.log.>
<Mar 11, 2015 12:37:55 PM PDT> <Notice> <Log Management> <BEA-170019> <The server log file /h/data/local/base_domain/servers/MyManagedServer1/logs/MyManagedServer1.log is opened. All server side log events will be written to this file.>
<Mar 11, 2015 12:37:56 PM PDT> <Error> <Security> <BEA-000000> <[Security:090837]The configured keystore location for the PKI Credential Mapper is either null or empty.>
<Mar 11, 2015 12:37:56 PM PDT> <Error> <Security> <BEA-000000> <[Security:090815]The password provided for the keystore configured for the PKICredential Mapper was null.>
<Mar 11, 2015 12:37:57 PM PDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Mar 11, 2015 12:37:57 PM PDT> <Critical> <Security> <BEA-090403> <Authentication for user beaadmin denied>
<Mar 11, 2015 12:37:57 PM PDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user beaadmin denied
weblogic.security.SecurityInitializationException: Authentication for user beaadmin denied
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:966)
        at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
        at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
        at weblogic.security.SecurityService.start(SecurityService.java:141)
        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
        Truncated. see log file for complete stacktrace
Caused By: javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User beaadmin weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
        at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:251)
        at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        Truncated. see log file for complete stacktrace
>
<Mar 11, 2015 12:37:57 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Mar 11, 2015 12:37:57 PM PDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Mar 11, 2015 12:37:57 PM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Why is it looking for demotrust.jks file to start the Managed Server. We don't use the demo trust and cannot copy to the location it is referring to. I followed the solution provided at the below link:
http://serverfault.com/questions/106499/custom-trust-and-custom-identity-keystore-in-weblogic-10-3
There are 2 options given in the link. To update the boot.properties of the Admin Server and appending JAVA_OPTIONS to DomainEnv file. Both of these caused the failure of Admin Server. I couldn't bring up the server after these changes.I also came across posts talking about boot.properties for Managed Server. I don't see the security folder that has boot.properties for my Managed Server (verified it on both windows and linux boxes).
Thanks in advance.
-nn.

Hi Faisal,
Here is the config.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<domain xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd"
        xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security"
        xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <name>JCRMDomain</name>
    <domain-version>10.3.4.0</domain-version>
    <security-configuration xmlns:xacml="http://xmlns.oracle.com/weblogic/security/xacml">
        <name>JCRMDomain</name>
        <realm>
            <sec:authentication-provider xsi:type="wls:default-authenticatorType">
                <sec:control-flag>SUFFICIENT</sec:control-flag>
            </sec:authentication-provider>
            <sec:authentication-provider xmlns:ext="http://xmlns.oracle.com/weblogic/security/extension" xsi:type="ext:jcrm-authenticatorType">
                <sec:name>JcrmAuthenticator</sec:name>
                <sec:control-flag>SUFFICIENT</sec:control-flag>
            </sec:authentication-provider>
            <sec:role-mapper xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
            <sec:authorizer xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
            <sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
            <sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
            <sec:credential-mapper xsi:type="wls:pki-credential-mapperType">
                <sec:name>PKICredentialMapper</sec:name>
            </sec:credential-mapper>
            <sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
            <sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
            <sec:user-lockout-manager>
                <sec:lockout-threshold>3</sec:lockout-threshold>
                <sec:lockout-duration>15</sec:lockout-duration>
                <sec:lockout-reset-duration>99999</sec:lockout-reset-duration>
            </sec:user-lockout-manager>
            <sec:deploy-role-ignored>false</sec:deploy-role-ignored>
            <sec:deploy-policy-ignored>false</sec:deploy-policy-ignored>
            <sec:fully-delegate-authorization>true</sec:fully-delegate-authorization>
            <sec:security-dd-model>DDOnly</sec:security-dd-model>
            <sec:combined-role-mapping-enabled>true</sec:combined-role-mapping-enabled>
            <sec:name>myrealm</sec:name>
            <sec:delegate-m-bean-authorization>false</sec:delegate-m-bean-authorization>
            <sec:password-validator xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator"
                                    xsi:type="pas:system-password-validatorType">
                <sec:name>JCRMPasswordValidator</sec:name>
                <pas:max-password-length>31</pas:max-password-length>
                <pas:min-password-length>15</pas:min-password-length>
                <pas:min-numeric-characters>2</pas:min-numeric-characters>
                <pas:min-lowercase-characters>2</pas:min-lowercase-characters>
                <pas:min-uppercase-characters>2</pas:min-uppercase-characters>
                <pas:min-non-alphanumeric-characters>2</pas:min-non-alphanumeric-characters>
            </sec:password-validator>
            <sec:deployable-provider-synchronization-enabled>false</sec:deployable-provider-synchronization-enabled>
        </realm>
        <default-realm>myrealm</default-realm>
        <credential-encrypted>{AES}cpwhv2peqwl0Z8Ma1Jk7KlmC6d1gtCAqxnzrmR5ssybHpM9AUzbBRJ7rE7m4/7U16IHgsTMkcOr/5/abZJ4NeuHR45jdDK1EjFmnUuPssISmGkan3EIpCKHmPPIynVxh</credential-encrypted>
        <node-manager-username>wdUXiuwL5A</node-manager-username>
        <node-manager-password-encrypted>{AES}UDiZjaLOrm0y+/I9noQVURudpzmRKMBOQR2B8ofNIt8=</node-manager-password-encrypted>
    </security-configuration>
    <server>
        <name>AdminServer</name>
        <max-http-message-size>10000000</max-http-message-size>
        <ssl>
            <name>AdminServer</name>
            <enabled>true</enabled>
            <hostname-verifier xsi:nil="true"></hostname-verifier>
            <hostname-verification-ignored>true</hostname-verification-ignored>
            <client-certificate-enforced>false</client-certificate-enforced>
            <listen-port>8443</listen-port>
            <two-way-ssl-enabled>true</two-way-ssl-enabled>
            <server-private-key-alias>localhost.localdomain</server-private-key-alias>
            <server-private-key-pass-phrase-encrypted>{AES}eZnL/NM4/xJaFj8rZAE4oB2htDm3srPUsTWYtDXblvk=</server-private-key-pass-phrase-encrypted>
            <ssl-rejection-logging-enabled>true</ssl-rejection-logging-enabled>
            <allow-unencrypted-null-cipher>false</allow-unencrypted-null-cipher>
            <use-server-certs>true</use-server-certs>
            <jsse-enabled>true</jsse-enabled>
        </ssl>
        <listen-port-enabled>false</listen-port-enabled>
        <web-server>
            <keep-alive-secs>60</keep-alive-secs>
            <https-keep-alive-secs>60</https-keep-alive-secs>
        </web-server>
        <listen-address/>
        <java-compiler>javac</java-compiler>
        <tunneling-enabled>true</tunneling-enabled>
        <tunneling-client-ping-secs>45</tunneling-client-ping-secs>
        <tunneling-client-timeout-secs>40</tunneling-client-timeout-secs>
        <client-cert-proxy-enabled>false</client-cert-proxy-enabled>
        <key-stores>CustomIdentityAndCustomTrust</key-stores>
        <custom-identity-key-store-file-name>certstores/keystore</custom-identity-key-store-file-name>
        <custom-identity-key-store-type>JKS</custom-identity-key-store-type>
        <custom-identity-key-store-pass-phrase-encrypted>{AES}eZnL/NM4/xJaFj8rZAE4oB2htDm3srPUsTWYtDXblvk=</custom-identity-key-store-pass-phrase-encrypted>
        <custom-trust-key-store-file-name>certstores/truststore</custom-trust-key-store-file-name>
        <custom-trust-key-store-type>JKS</custom-trust-key-store-type>
        <custom-trust-key-store-pass-phrase-encrypted>{AES}uSkLzfC74bMCEjomgVdHtVw47iZg8BN71g7cdKr+XHo=</custom-trust-key-store-pass-phrase-encrypted>
    <overload-protection>
      <panic-action>system-exit</panic-action>
      <failure-action>force-shutdown</failure-action>
      <server-failure-trigger>
        <max-stuck-thread-time>600</max-stuck-thread-time>
        <stuck-thread-count>3</stuck-thread-count>
      </server-failure-trigger>
    </overload-protection>
    </server>
    <server>
      <name>MyManagedServer1</name>
      <ssl>
        <enabled>true</enabled>
        <listen-port>8445</listen-port>
        <server-private-key-alias>localhost.localdomain</server-private-key-alias>
        <server-private-key-pass-phrase-encrypted>{AES}eZnL/NM4/xJaFj8rZAE4oB2htDm3srPUsTWYtDXblvk=</server-private-key-pass-phrase-encrypted>
      </ssl>
      <machine xsi:nil="true"></machine>
      <listen-port>8444</listen-port>
      <listen-port-enabled>true</listen-port-enabled>
      <cluster xsi:nil="true"></cluster>
      <web-server>
        <web-server-log>
          <number-of-files-limited>false</number-of-files-limited>
        </web-server-log>
      </web-server>
      <listen-address></listen-address>
      <key-stores>CustomIdentityAndCustomTrust</key-stores>
      <custom-identity-key-store-file-name>certstores/keystore</custom-identity-key-store-file-name>
      <custom-identity-key-store-type>JKS</custom-identity-key-store-type>
      <custom-identity-key-store-pass-phrase-encrypted>{AES}eZnL/NM4/xJaFj8rZAE4oB2htDm3srPUsTWYtDXblvk=</custom-identity-key-store-pass-phrase-encrypted>
      <custom-trust-key-store-file-name>certstores/truststore</custom-trust-key-store-file-name>
      <custom-trust-key-store-type>JKS</custom-trust-key-store-type>
      <custom-trust-key-store-pass-phrase-encrypted>{AES}uSkLzfC74bMCEjomgVdHtVw47iZg8BN71g7cdKr+XHo=</custom-trust-key-store-pass-phrase-encrypted>
      <data-source>
        <rmi-jdbc-security xsi:nil="true"></rmi-jdbc-security>
      </data-source>
    </server>
    <production-mode-enabled>false</production-mode-enabled>
    <embedded-ldap>
        <name>JCRMDomain</name>
        <credential-encrypted>{AES}LNAnq4qCQQmy9rCOMN+uIZVPq1bVvPrwQqqtOScZrnYmwESt9aruHNVy4IjqMWz7</credential-encrypted>
    </embedded-ldap>
    <administration-port-enabled>true</administration-port-enabled>
    <configuration-version>10.3.4.0</configuration-version>
    <admin-server-name>AdminServer</admin-server-name>
</domain>
It has 'CustomIdentityAndCustomTrust' for both Admin Server as well as managed Server in it.
Thanks,
nn

Session migration and replication

Hi All,
I am having a hard time in configuring my application for HTTP session migration. Our weblogic server consists of two managed servers running in same cluster. Each server has an Ehcache that stores some information of user with key as session ID and value as info object. In case, if a server needs restart, we would want to take this updated info Object from cache residing on server being restarted to another managed server within the same cluster.
I browsed through many documentations online. Most of them explained about session replication but not migration. so I followed replication (I don't want a real time sync up of HTTP session. I want it to migrate if something goes wrong with one of the managed server).
However, I could not achieve this task after following the steps to configure this feature. I would appreciate a lot if someone can help me figuring out the issue here.
Here is what I did.
1) Weblogic.xml
     <session-descriptor>
<persistent-store-type>replicated_if_clustered</persistent-store-type>
</session-descriptor>
2) An implementation class of HttpSessionActivationListener, HttpSessionListener, HttSessionAttributeListener:
public void sessionDidActivate(HttpSessionEvent sessionEvent) {
// NEVER GETS CALLED
over here i would check if session has any attribute with name 'CACHE_ELEMENT'. If yes, then it is a migration case for current managed server
          Log.info(UserCacheMigrationListener.class, "inside sessionDidActivate");//
public void sessionWillPassivate(HttpSessionEvent sessionEvent) {
// NEVER GETS CALLED
Over here I would set attribute 'CACHE_ELEMENT' so that it is available for target managed server when it's sessionDidActivate is called
          Log.info(UserCacheMigrationListener.class, "inside sessionWillPassivate");
public void sessionCreated(HttpSessionEvent sessionEvent) {
THIS GETS CALLED! and I set the following attribute
sessionEvent.getHttpSession().setAttribute(UserCacheMigrationListener.class.getName(), this);
public void sessionDestroyed(HttpSessionEvent arg0) {
THIS GETS CALLED!
public void valueBound(HttpSessionBindingEvent arg0) {
THIS GETS CALLED! WHICH MEANS THAT I WAS ABLE TO setAttribute this class's instance in sessionCreatedMethod
In the above code, the setAttribute method used inside the sessionCreated(..) method successfully sets the attribute to this session. This is apparent because valueBound(..) method is called when session is created. But why does it not call the sessionWillActivate method???
3.) An entry in web.xml for this listener.
     <listener>
          <listener-class>com.xyz.UserCacheMigrationListener</listener-class>
     </listener>
4) from weblogic config.xml. I am copying all meaning stuffs from config.xml to describe as much as I can.
<server>
<name>AdminServer</name>
<ssl>
<enabled>false</enabled>
</ssl>
<listen-address>localhost</listen-address>
<network-access-point>
<name>AdminChannel</name>
<protocol>t3</protocol>
<listen-address>localhost</listen-address>
<http-enabled-for-this-protocol>true</http-enabled-for-this-protocol>
<tunneling-enabled>false</tunneling-enabled>
<outbound-enabled>false</outbound-enabled>
<enabled>true</enabled>
<two-way-ssl-enabled>false</two-way-ssl-enabled>
<client-certificate-enforced>false</client-certificate-enforced>
</network-access-point>
<data-source>
<rmi-jdbc-security xsi:nil="true"></rmi-jdbc-security>
</data-source>
</server>
<server>
<name>Node1</name>
<ssl>
<enabled>false</enabled>
</ssl>
<machine>DevMachine</machine>
<listen-port>7002</listen-port>
<cluster>DevCluster</cluster>
<replication-group>devGroup1</replication-group>
<preferred-secondary-group>devGroup2</preferred-secondary-group>
<web-server>
<keep-alive-secs>500</keep-alive-secs>
<post-timeout-secs>120</post-timeout-secs>
</web-server>
<listen-address>localhost</listen-address>
<jta-migratable-target>
<user-preferred-server>Node1</user-preferred-server>
<cluster>DevCluster</cluster>
</jta-migratable-target>
<data-source>
<rmi-jdbc-security xsi:nil="true"></rmi-jdbc-security>
</data-source>
</server>
<server>
<name>Node2</name>
<ssl>
<enabled>false</enabled>
</ssl>
<machine>DevMachine</machine>
<listen-port>7003</listen-port>
<cluster>DevCluster</cluster>
<replication-group>devGroup2</replication-group>
<preferred-secondary-group>devGroup1</preferred-secondary-group>
<listen-address>localhost</listen-address>
<network-access-point>
<name>Node2Channel</name>
<protocol>t3</protocol>
<listen-address>localhost</listen-address>
<http-enabled-for-this-protocol>true</http-enabled-for-this-protocol>
<tunneling-enabled>true</tunneling-enabled>
<outbound-enabled>false</outbound-enabled>
<enabled>true</enabled>
<two-way-ssl-enabled>false</two-way-ssl-enabled>
<client-certificate-enforced>false</client-certificate-enforced>
</network-access-point>
<jta-migratable-target>
<user-preferred-server>Node2</user-preferred-server>
<cluster>DevCluster</cluster>
</jta-migratable-target>
<data-source>
<rmi-jdbc-security xsi:nil="true"></rmi-jdbc-security>
</data-source>
</server>
<cluster>
<name>DevCluster</name>
<cluster-messaging-mode>unicast</cluster-messaging-mode>
</cluster>
<machine>
<name>DevMachine</name>
<node-manager>
<nm-type>Plain</nm-type>
</node-manager>
</machine>
<migratable-target>
<name>Node1 (migratable)</name>
<notes>This is a system generated default migratable target for a server. Do not delete manually.</notes>
<user-preferred-server>Node1</user-preferred-server>
<cluster>DevCluster</cluster>
</migratable-target>
<migratable-target>
<name>Node2 (migratable)</name>
<notes>This is a system generated default migratable target for a server. Do not delete manually.</notes>
<user-preferred-server>Node2</user-preferred-server>
<cluster>DevCluster</cluster>
</migratable-target>
------------------------------------------------------------------------------------------------------------------

Hi,
So you want to migrate your server to server.
Here are the following links which help you.
http://docs.oracle.com/cd/E15051_01/wls/docs103/cluster/migration.html
http://www.oracle.com/technetwork/middleware/weblogic/messaging/wlasm-1853193.pdf
let me know the status if you need any further help on this issue.
Regards,
Kal

Need suggestion for choosing Java development enviroment

Hi Evereyone,
I am new to Java Desktop Application.I need help on choosing proper Java technologies and development tool.
We have an existing CLIENT/SERVER based distributed control system, which was developed in C++(Server side) and VB(Client GUI).Now we are think of migrating the system to Java platform.
Here is the outline:
We want to create web based application that will run on windows and linux (linux on embedded PC).
The application should be able to support 10 � 100 users at once accessing/editing database.
We will also need to create a communication server that will run on web server P.C. that will communicate tcpip to field panels/log to db, as well as allow web screens to send/receive commands with field panels etc.
Could any one give me some suggestion about it?
I am thinking of Using J2SE 5.0, including RMI, JDBC and Swing for GUI. As for field panels, may choose J2ME.
Thank you very much in advance.

Thanks, zadok .
Actually, I don't have the system requirements neither. All I know is the following outline:
"We want to create web based application that will run on windows and linux (linux on embedded PC).
The application should be able to support 10 � 100 users at once accessing/editing database.
We will also need to create a communication server that will run on web server P.C. that will communicate tcpip to field panels/log to db, as well as allow web screens to send/receive commands with field panels etc."
It is a interview question, which need me to do research and give some suggestions. What I want to know is to figure out what kind of Java technology is necessary for developing this system because I want to make sure I head to right direction.
I know somehow it is hard to give suggestion based on this limited information.
One more thing I was confusing is the server-side architecture.
I need suggestion about sever side architecture:
a. write a dedicated server-side program, which act
as communication server to monitor and control field
panel, also act as server-side applicaiton by using
RMI to communicate with Client-side communication.
b. choose a general web server architecture. Put
everything in server side in Web Server, for example
Tomcat AS container, implementing the Communication
server as Web Service and the request from
Client-side go to Web Server first, then dispatch to
a proper web service.Why did you not include this information in the original question!
Why don't you just use Tomcat?
For your answer, "Why don't you just use Tomcat?", does it mean Tomcat without Web Service will be enough for this system development? Could you give me some detail about it?
Thank you very much, zadok.

How Do I Stop the Dial Up Box popping up

Hello all,
I am developing a three tiered RMI/JDBC application and have just about got it working over a LAN. My problem is that when my client (192.168.0.2) performs a Naming.lookup(String URL) the dial-up connection box pops up on my server computer(192.168.0.1) wanting me to connect to the internet.
If I press cancel the client connects and everything seems to work but I was hoping there was some way of stopping it occuring in the first place.
If anyone has a solution to this problem it would be much appreciated.
Thanks in advance
Suranga Fernando

You have to configure it on the server box to not auto-dial the internet.
This might help...
http://support.microsoft.com/default.aspx?scid=kb;EN-US;152220

Most efficient way to get a connection from a defined connection -pool [whole message]

Having recently load-tested the application we are developing I noticed that
one of the most expensive (time-wise) calls was my fetch of a db-connection
from the defined db-pool. At present I fetch my connections using :
private Connection getConnection() throws SQLException {
try {
Context jndiCntx = new InitialContext();
DataSource ds =
(DataSource)
jndiCntx.lookup("java:comp/env/jdbc/txDatasource");
return ds.getConnection();
} catch (NamingException ne) {
myLog.error(this.makeSQLInsertable("getConnection - could not
find connection"));
throw new EJBException(ne);
In other parts of the code, not developed by the same team, I've seen the
same task accomplished by :
private Connection getConnection() throws SQLException {
return DriverManager.getConnection("jdbc:weblogic:jts:FTPool");
From the performance-measurements I made the latter seems to be much more
efficient (time-wise). To give you some metrics:
The first version took a total of 75724ms for a total of 7224 calls which
gives ~ 11ms/call
The second version took a total of 8127ms for 11662 calls which gives
~0,7ms/call
I'm no JDBC guru som i'm probably missing something vital here. One
suspicion I have is that the second call first find the jdbc-pool and after
that makes the very same (DataSource)
jndiCntx.lookup("java:comp/env/jdbc/txDatasource") in order to fetch the
actual connection anyway. If that is true then my comparison is plain wrong
since one call is part of the second. If not, then the second version sure
seems a lot faster.
Apart from the obvious performance-differences in the two above approaches,
is there any other difference one should be aware of (transaction-context
for instance) between the two ? Basically I'm working in an EJB-environment
on weblogic 7.0 and looking for the most efficient way to get hold of a
db-connection in code. Comments anyone ?
//Linus Nikander - [email protected]

Linus Nikander wrote:
Thank you for both your replies. As per your suggestions I've improved my
connectionhandling (I ended up implementing the Service Locator pattern as a
matter of fact).
One thing still puzzles me though. Which (and why) is the "proper" way to
fetch the actual dataSource. As I stated before in the code I've seen two
approaches within the code I've got.
1. myDs = myServiceLocator.getDataSource("jdbc:weblogic:jts:FTPool");
2. myDs = myServiceLocator.getDataSource("java:comp/env/jdbc/tgsDB");
where getDataSource does a dataSource = (DataSource)
initialContext.lookup(dataSourceName); dataSourceName being the input-string
obviously.
tgsDB is defined as
<reference-descriptor>
<resource-description>
<res-ref-name>jdbc/tgsDB</res-ref-name>
<jndi-name>tgs-dataSource</jndi-name>
</resource-description>
</reference-descriptor>
in weblogic-ejb-jar.xml
From what I can understand by your answer, you don't recommend using the
JNDI-lookup way of getting the connection at all ?Correct.
The service locator that
I implemented will still perform a JNDI lookup, but only once. Will the fact
that I'm talking to an RMI-object anyway significantly impact performance
(when compared to you non-jndi-method) ?In some cases, for earlier 7.0s, maybe yes. For the very latest, it shouldn't
hurt.
>
>
In my two examples above. If i use version 1. How will the server know
whether to give me a TX-bound connection and when not to ? In version 1
FTPool maps to a pool with both TX and non-TX datasources. In version 2.
tgsDB maps directly to a TX-dataSource.
I might be asking a lot of strange questions, probably because I'm just
getting the hang of all the resource-reference issues that EJBs are
associated with.Bear with me ;)
//Linus
"Joseph Weinstein" <[email protected]> wrote in message
news:[email protected]...
Hi. As Jon said, the lookups are redundant. Because you showed that otherway,
I will infer that this code is always being run in serverside code. Good.I will give you
a third way which is much better than either of the ones you showed. Thefirst method
you showed has a problem for all but the latest sps, your jdbc objectswill all be
going through an unnecessary level of indirection because you are gettingan rmi jdbc
object which talks to the jts driver object.
The second, faster method you showed also has a serious problem! Oneshould
never call DriverManager methods in multithreaded JDBC programs becauseall
DriverManager calls are class-synchronized, including some small internalones like
DriverManager.println(), which all JDBC drivers and even the constructorfor
SQLException call, so one slow getConnection() call can inadvertantly haltall other
JDBC being done in the whole JVM! Also, for JVMs that have lots of jdbcdrivers
registered, DriverManager is inefficient because it simply sends your URLand
properties to every driver it has registered until it finds one thatdoesn't throw an
exception and returns a connection.
Here's the fastest way:
// do once and reuse driver object everywhere. Can be used by multiplethreads
Driver d =(Driver)Class.forName("weblogic.jdbc.jts.Driver").newInstance();
Then, whenever you want a connection:
public myJDBCMethod()
Connection c = null; // always a method level object
try {
c = d.connect("jdbc:weblogic:jts:FTPool", null);
... do all the jdbc for the method...
c.close();
c = null;
catch (Exception e) {
... do whatever, if needed...
finally {
// close connection regardless of failure or exit path
if (c != null) try {c.close();}catch (Exception ignore){}
Joe
Linus Nikander wrote:
Having recently load-tested the application we are developing I noticed
that
one of the most expensive (time-wise) calls was my fetch of adb-connection
from the defined db-pool. At present I fetch my connections using :
private Connection getConnection() throws SQLException {
try {
Context jndiCntx = new InitialContext();
DataSource ds =
(DataSource)
jndiCntx.lookup("java:comp/env/jdbc/txDatasource");
return ds.getConnection();
} catch (NamingException ne) {
myLog.error(this.makeSQLInsertable("getConnection - couldnot
find connection"));
throw new EJBException(ne);
In other parts of the code, not developed by the same team, I've seenthe
same task accomplished by :
private Connection getConnection() throws SQLException {
return DriverManager.getConnection("jdbc:weblogic:jts:FTPool");
From the performance-measurements I made the latter seems to be muchmore
efficient (time-wise). To give you some metrics:
The first version took a total of 75724ms for a total of 7224 callswhich
gives ~ 11ms/call
The second version took a total of 8127ms for 11662 calls which gives
~0,7ms/call
I'm no JDBC guru som i'm probably missing something vital here. One
suspicion I have is that the second call first find the jdbc-pool andafter
that makes the very same (DataSource)
jndiCntx.lookup("java:comp/env/jdbc/txDatasource") in order to fetch the
actual connection anyway. If that is true then my comparison is plainwrong
since one call is part of the second. If not, then the second versionsure
seems a lot faster.
Apart from the obvious performance-differences in the two aboveapproaches,
is there any other difference one should be aware of(transaction-context
for instance) between the two ? Basically I'm working in anEJB-environment
on weblogic 7.0 and looking for the most efficient way to get hold of a
db-connection in code. Comments anyone ?
//Linus Nikander - [email protected]

Problem in Installing PetStore 1.3

Dears, I am facing problem in installing petstore following is my console's out put.Please advise.
I am following the same instructions provided in the docs.
E:\j2sdkee1.2.1\public_html\petstore1.3>setup
Buildfile: setup.xml
init:
help:
[echo] Before running this script, please start the cloudscape database and J2EE server by running the following commands:
[echo] <change directory to j2sdkee1.3/bin>
[echo] cloudscape -start
[echo] j2ee -verbose
create_jms_queues:
[echo] Creating JMS Queues ....
[java] java.lang.NoClassDefFoundError: com/sun/enterprise/tools/admin/AdminTool
[java] Java Result: 1
[java] java.lang.NoClassDefFoundError: com/sun/enterprise/tools/admin/AdminTool
[java] Java Result: 1
[java] java.lang.NoClassDefFoundError: com/sun/enterprise/tools/admin/AdminTool
[java] Java Result: 1
[java] java.lang.NoClassDefFoundError: com/sun/enterprise/tools/admin/AdminTool
[java] Java Result: 1
[java] java.lang.NoClassDefFoundError: com/sun/enterprise/tools/admin/AdminTool
[java] Java Result: 1
[java] java.lang.NoClassDefFoundError: com/sun/enterprise/tools/admin/AdminTool
[java] Java Result: 1
[java] java.lang.NoClassDefFoundError: com/sun/enterprise/tools/admin/AdminTool
[java] Java Result: 1
create_users:
[echo] Creating users ....
[java]
[java] Group default has been added successfully.
[java]
[java] User jps_admin has been added successfully.
[java]
[java] User rcvr has been added successfully.
create_supplier_db:
[java] java.lang.NoClassDefFoundError: com/sun/enterprise/tools/admin/AdminTool
[java] Java Result: 1
create_opc_db:
[java] java.lang.NoClassDefFoundError: com/sun/enterprise/tools/admin/AdminTool
[java] Java Result: 1
core:
[echo] The J2EE SDK is now successfully configured to run the petstore application. Please restart cloudscape and the j2ee servers, and deploy all the ear files. You can do this by issuing the fo
llowing commands:
[echo] change directory to j2sdkee1.3/bin
[echo] cloudscape -stop
[echo] j2ee -stop
[echo] cloudscape -start
[echo] j2ee -verbose
[echo] change directory to petstore1.3
[echo] setup.bat deploy (or on Unix, setup.sh deploy)
BUILD SUCCESSFUL
Total time: 22 seconds
E:\j2sdkee1.2.1\public_html\petstore1.3>cd ..
E:\j2sdkee1.2.1\public_html>cd ..
E:\j2sdkee1.2.1>cd bin
E:\j2sdkee1.2.1\bin>cloudscape -stop
URL=[jdbc:rmi:jdbc:cloudscape:]
Attempting to shutdown RmiJdbc server
RmiJdbc Server RmiAddr is: //aliawan/RmiJdbcServer
WARNING: Shutdown was successful!
E:\j2sdkee1.2.1\bin>j2ee -stop
Shutting down the J2EE server.
E:\j2sdkee1.2.1\bin>cd ../public_html
E:\j2sdkee1.2.1>cd /public_html
The syntax of the command is incorrect.
E:\j2sdkee1.2.1>cd public_html
E:\j2sdkee1.2.1\public_html>cd petstore
The system cannot find the path specified.
E:\j2sdkee1.2.1\public_html>cd petstore1.3
E:\j2sdkee1.2.1\public_html\petstore1.3>setup.bat deploy
Buildfile: setup.xml
init:
deploy:
[echo] Deploying ears ....
[java]
[java] Sender object Deploytool (Main) : Neither this XML document's public nor system id's could be resolved: java.net.UnknownHostException: java.sun.com java.sun.com
[java] on parsing the doucment corresponding to class com.sun.enterprise.deployment.xml.EjbBundleNode
[java] Java Result: 1
[java]
[java] Sender object Deploytool (Main) : Neither this XML document's public nor system id's could be resolved: java.net.UnknownHostException: java.sun.com java.sun.com
[java] on parsing the doucment corresponding to class com.sun.enterprise.deployment.xml.ApplicationNode
[java] Java Result: 1
[java]
[java] Sender object Deploytool (Main) : Neither this XML document's public nor system id's could be resolved: java.net.UnknownHostException: java.sun.com java.sun.com
[java] on parsing the doucment corresponding to class com.sun.enterprise.deployment.xml.ApplicationNode
[java] Java Result: 1
[java]
[java] Sender object Deploytool (Main) : Neither this XML document's public nor system id's could be resolved: java.net.UnknownHostException: java.sun.com java.sun.com
[java] on parsing the doucment corresponding to class com.sun.enterprise.deployment.xml.ApplicationNode
[java] Java Result: 1
[echo] The petstore application is now installed.
[echo] Please restart your cloudscape database and the J2EE server, and then point your browser to http://localhost:8000/petstore to access petstore.
BUILD SUCCESSFUL
Total time: 17 seconds
E:\j2sdkee1.2.1\public_html\petstore1.3>cd ..
E:\j2sdkee1.2.1\public_html>cd ..
E:\j2sdkee1.2.1>cd bin
E:\j2sdkee1.2.1\bin>cloudscape -stop
URL=[jdbc:rmi:jdbc:cloudscape:]
Attempting to shutdown RmiJdbc server
RmiJdbc Server RmiAddr is: //aliawan/RmiJdbcServer
WARNING: Shutdown was successful!
E:\j2sdkee1.2.1\bin>j2ee -stop
Shutting down the J2EE server.
E:\j2sdkee1.2.1\bin>

Hello ali_awan,
Upon looking at the output from the console, it looks like you had a problem when you ran setup under the petstore1.3 directory. The setup echoed several times:
[java] java.lang.NoClassDefFoundError: com/sun/enterprise/tools/admin/AdminToolBecause this class was not found, the latter deployment of the Petstore .ear file was not successful. To fix this, you will first need to successfully setup petstore1.3.
The NoClassDefFoundError indicates that the class files in the package com/sun/enterprise/tools/admin/AdminTool could not be located in the system CLASSPATH variable.
Please make sure that the directory that stores the package com/sun/enterprise/tools/admin/AdminTool is included in the system CLASSPATH. This should get rid of the errors during the create_jms_queues step. And hopefully this should alleviate the problems encountered during the deployment of the Petstore ear file.
For instructions how to set your CLASSPATH variable, please visit the following link:
http://java.sun.com/j2se/1.3/install-windows.html
Hope this helps!
Ming Chou
Developer Technical Support
http://www.sun.com/developers/support

RMI JDBC

Similar Messages

Maybe you are looking for