Access to local DataSource tries to connect to remote server after ejb call to remote server

Question

I've run into a problem with code that worked fine under WebLogic 6.1 SP4, but I'm having difficulty migrating it to WebLogic 8.1 SP2.
          I have two weblogic instances running in separate domains (InstanceA and InstanceB). The two domains have the same crentential configured to setup the trust relationship.
          InstanceA runs on my local machine. It contains Stateless Session Beans StatelessSessionBeanA1, StatelessSessionBeanA2, and DataSourceA1
          InstanceB runs on a different machine. It contains StatelessSessionBeanB1.
          A function A1Func1 in StatelessSessionBeanA1
          1) creates an initial context to connect to InstanceB
          2) calls a method B1Func1 on StatelessSessionBeanB1
          3) closes that context to InstanceB
          4) Calls a method A2Func1 on StatelessSessionBeanA2
          5) manipulates several entity beans
          6) returns
          A1Func1, A2Func1, B1Func1 have the "Required" transaction attribute set.
          Steps 1,2,3 work fine, but on step 4, when A2Func1 attempts to get a Connection from the DataSourceA1, it gets an exception:
          java.sql.SQLException: Could not get remote server connection url = t3://(IP/port of InstanceB)
          at weblogic.jdbc.jts.Driver.createRemoteConnection(Driver.java:305)
          at weblogic.jdbc.jts.Driver.connect(Driver.java:157)
          at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
          ... enters my application code
          A2Func1 works fine elsewhere, so on a hunch, I tried making A2Func1 have the "RequiresNew" transaction attribute. This causes steps 1,2,3,4 to work, but in step 5, when the entity beans attempt to get a connection from DataSourceA1, it runs into the same exception
          java.sql.SQLException: Could not get remote server connection url = t3://(IP/port of InstanceB)
          at weblogic.jdbc.jts.Driver.createRemoteConnection(Driver.java:305)
          at weblogic.jdbc.jts.Driver.connect(Driver.java:157)
          at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
          at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247)
          Any ideas why calling out to StatelessSessionBeanB1 would cause things inside the same transaction to try to get their datasource from InstanceB? Again, this code worked fine under WebLogic 6.1
          And ideas would be appreciated.
          Thanks,
          --Andy
          

Answer 1

          As a follow up, no solution, but a workaround - we changed the transaction setting
          on B1Func1 (which was a read type method) on InstanceB's StatelessSessionBeanB1
          to NotSupported, and everything started working again.
          --Andy
          Andrew Delpha <[email protected]> wrote:
          >I've run into a problem with code that worked fine under WebLogic 6.1
          >SP4, but I'm having difficulty migrating it to WebLogic 8.1 SP2.
          >
          >I have two weblogic instances running in separate domains (InstanceA
          >and InstanceB). The two domains have the same crentential configured
          >to setup the trust relationship.
          >
          >InstanceA runs on my local machine. It contains Stateless Session Beans
          >StatelessSessionBeanA1, StatelessSessionBeanA2, and DataSourceA1
          >
          >InstanceB runs on a different machine. It contains StatelessSessionBeanB1.
          >
          >
          >A function A1Func1 in StatelessSessionBeanA1
          >1) creates an initial context to connect to InstanceB
          >2) calls a method B1Func1 on StatelessSessionBeanB1
          >3) closes that context to InstanceB
          >4) Calls a method A2Func1 on StatelessSessionBeanA2
          >5) manipulates several entity beans
          >6) returns
          >
          >A1Func1, A2Func1, B1Func1 have the "Required" transaction attribute set.
          >
          >
          >Steps 1,2,3 work fine, but on step 4, when A2Func1 attempts to get a
          >Connection from the DataSourceA1, it gets an exception:
          >java.sql.SQLException: Could not get remote server connection url = t3://(IP/port
          >of InstanceB)
          > at weblogic.jdbc.jts.Driver.createRemoteConnection(Driver.java:305)
          > at weblogic.jdbc.jts.Driver.connect(Driver.java:157)
          > at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
          > ... enters my application code
          >
          >A2Func1 works fine elsewhere, so on a hunch, I tried making A2Func1 have
          >the "RequiresNew" transaction attribute. This causes steps 1,2,3,4
          >to work, but in step 5, when the entity beans attempt to get a connection
          >from DataSourceA1, it runs into the same exception
          >java.sql.SQLException: Could not get remote server connection url = t3://(IP/port
          >of InstanceB)
          > at weblogic.jdbc.jts.Driver.createRemoteConnection(Driver.java:305)
          > at weblogic.jdbc.jts.Driver.connect(Driver.java:157)
          > at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:305)
          > at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:2247)
          >
          >Any ideas why calling out to StatelessSessionBeanB1 would cause things
          >inside the same transaction to try to get their datasource from InstanceB?
          > Again, this code worked fine under WebLogic 6.1
          >
          >And ideas would be appreciated.
          >Thanks,
          >--Andy