cancel
Showing results for 
Search instead for 
Did you mean: 

JDBC lookup

0 Kudos

I tried to do a sample scenario Using this blog u201CUsing JDBC Connection Pool in XI Message Mappingu201D by William lee

/people/william.li/blog/2007/03/30/using-jdbc-connection-pool-in-xi-message-mapping

i'm getting an error while testing the mapping (mapping is success)..mapped field shows an ouput like

ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.connector.exceptions.BaseResourceException: Cannot open resource(Managed Connection) with LocalTransaction support or add a second one in the same transaction, for component "ejbContexts/sap.com/com.sap.xi.repository/sap.com/com.sap.xi.repository/MapServiceBean" in application "sap.com/com.sap.xi.repository"

any idea??? what could be the possible solution for this.

Accepted Solutions (0)

Answers (2)

Answers (2)

0 Kudos

Problem with connection sharing if J2EE transaction is running

The error message looks as follows:

Error: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.connector.exceptions.BaseResourceException: Cannot open resource(Managed Connection) with LocalTransaction support or add a second one in the same transaction, for component "webContainer/applications/sap.com/TestDB/TestDB" in application "sap.com/TestDB".

at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:59)

at jsp_in1079450298593._jspService(jsp_in1079450298593.java:78)

at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:464)

--- the remainder of trace is skipped ---

The problem is caused when there is an inappropriate attempt to open a second connection in an active JTA transaction. There is either an attempt to get a second connection from an un-shareable non-XA DataSource or an attempt to get it from another non-XA DataSource. You have to:

● Use no more than one connection from this data source while the JTA transaction is active or

● Declare the data source as shareable, depending on your application logic.

0 Kudos

Problem with connection sharing if J2EE transaction is running

The error message looks as follows:

Error: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.connector.exceptions.BaseResourceException: Cannot open resource(Managed Connection) with LocalTransaction support or add a second one in the same transaction, for component "webContainer/applications/sap.com/TestDB/TestDB" in application "sap.com/TestDB".

at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:59)

at jsp_in1079450298593._jspService(jsp_in1079450298593.java:78)

at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:464)

--- the remainder of trace is skipped ---

The problem is caused when there is an inappropriate attempt to open a second connection in an active JTA transaction. There is either an attempt to get a second connection from an un-shareable non-XA DataSource or an attempt to get it from another non-XA DataSource. You have to:

● Use no more than one connection from this data source while the JTA transaction is active or

● Declare the data source as shareable, depending on your application logic.