Cant create JDBC Connections in RMI Server

Question

I am having a pretty weird problem which I am struggling with for the last three days. In the main method of the Server object, following three things are supposed to happen:
1) Creation of a JDBC Connection
2) Creation of a Remote Object and then publishing the same to Registry.
3) Creation of another JDBC Connection (exactly same as in step1)
step 1 and 2 successfully executes and the third one always errors out. I just simply get a NullPointerException.
If I comment out step 2, step 3 executes successfully. Can someone please tell me the mystery? I need your response really urgently so please help me.
TIA
Code Snippet:
 public static void main(String[] args) {
  System.setSecurityManager(new RMISecurityManager());
  try {
   Properties dbProps = new Properties();
   dbProps.put("user", "SDAWOODI");
   dbProps.put("password", "SDAWOODI");
   java.sql.Connection connection =    java.sql.DriverManager.getConnection("jdbc:oracle:thin:@wonder.cisco.com:1521:ODSDEV", dbProps);
  catch (Exception sqle) {
   System.out.println("[11111]"+sqle.toString());
  Properties props = new Properties();
  props.put("java.rmi.server.codebase", rmiCodeBase);
  System.setProperties(props);
  try {
   SchedulerRImpl schedulerR = new SchedulerRImpl(ssce_sch1);
   String nameStr = "s-sce-scheduler";
   try {
    Naming.bind(nameStr, schedulerR);
    if (Scheduler.m_debug_flag) System.out.println("[Scheduler.main] Scheduler bound with RMI registry!!!");
   catch (AlreadyBoundException abe) {
    if (Scheduler.m_debug_flag) System.out.println("[Scheduler.main] Scheduler is already bound with RMI registry ... trying RE-bind ...");
    try {
     Naming.rebind(nameStr, schedulerR);
     if (Scheduler.m_debug_flag) System.out.println("[Scheduler.main] Scheduler RE-bound with RMI registry!!!");
    catch (Exception e) {
     if (Scheduler.m_debug_flag) System.out.println("[Scheduler.main] Rcheduler RE-binding failed :(((");
  catch (Exception e) {
   if (Scheduler.m_debug_flag) System.out.println("[Scheduler.main] SchedulerR instantiation failed:((( : "+e.toString());
  Properties dbProps2 = new Properties();
  dbProps2.put("user", "SDAWOODI");
  dbProps2.put("password", "SDAWOODI");
  try {
   java.sql.Connection connection2 = java.sql.DriverManager.getConnection("jdbc:oracle:thin:@wonder.cisco.com:1521:ODSDEV", dbProps2);
   if (connection2==null) {
   System.out.println("connection is NULL");
  else {
   System.out.println("connection is NOT null");
 catch (Exception sqle2) {
  System.out.println("[22222]"+sqle2.toString());
}

Answer 1

In reply to reply #4:
You can also quote the other part of my reply when it comes to snippets. There are so many pieces of code missing from your snippet that I simply cannot guess what is wrong. (Please do not put your entire class structures here.)
We get connections in many different classes at many different times. It is after all an application that does user work and the user work involves database accesses. Some of those accesses are before RMI (to establish repositories, etc). Most are after.
This URL (jdbc:oracle:thin:@wonder.cisco.com:1521:ODSDEV) appears to use a network connection (yes?). Is the 1521 a port? Are you trying to reuse this port? (the first conn uses the same URL). What port does RMI use?
There is nothing in your snippet that stands out obviously as "this is wrong".
RMI uses networking. JDBC uses networking.
Try substituting some other networking code in place of the RMI code and see if you still get a null trying the second connection. As you say, if you leave out the RMI code the second get.conn works.
Try leaving out the first get.conn. Do the RMI and second get.conn.
Try this and try that and try some more. I once had this problem with a network printer that would not print. The code was fine. The URL was fine. The response from the network and printer were both fine. The damn thing just wasn't printing. Turns out there was this bit, yes a single bit, in one word of a property called the "start print bit". If this bit wasn't on, nothing happened. I tried every combination until I finally found it.
I wish you the best.