EDI TO ECC6.0

[Former Member]

Hi Experts,

Can any one please help me what is the exact problem

FROM EDI DATA WA COMING TO SAP PI IT WILL GO TO ECC 6.0

I have an Issue like in SXMB_MONI

Error when determining the receiver: Problem while determining receivers using interface mapping: Database access error

This is the TRACE :-

Interface Mapping http://cardinalhealth.com/SNC/Enhancements Z_DespatchedDeliveryNotificationReceiverDetermination</Trace>

<Trace level="1" type="T">ResourceException occurred in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.connector.exceptions.BaseResourceException: Cannot get connection for 0 seconds. Possible reasons: 1) Connections are cached within SystemThread(can be any server service or any code invoked within SystemThread in the SAP J2EE Engine) or they are allocated from a non transactional ConnectionFactory. In case of transactional ConnectionFactory used from Application Thread there is an automatic mechanism which detects unclosed connections, 2)The pool size of adapter "SAPPX2DB" is not enough according to the current load of the system . In case 1) the solution is to check for cached connections using the Connector Service list_conns command or in case 2), to increase the size of the pool. Thrown: com.sap.aii.utilxi.sql.api.SQLResourceException: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.connector.exceptions.BaseResourceException: Cannot get connection for 0 seconds. Possible reasons: 1) Connections are cached within SystemThread(can be any server service or any code invoked within SystemThread in the SAP J2EE Engine) or they are allocated from a non transactional ConnectionFactory. In case of transactional ConnectionFactory used from Application Thread there is an automatic mechanism which detects unclosed connections, 2)The pool size of adapter "SAPPX2DB" is not enough according to the current load of the system . In case 1) the solution is to check for cached connections using the Connector Service list_conns command or in case 2), to increase the size of the pool. at com.sap.aii.utilxi.sql.api.ConnectionProvider.getConnection(ConnectionProvider.java:67) at com.sap.aii.utilxi.sql.api.DBManager.getJdbcConnection(DBManager.java:307) at com.sap.aii.utilxi.sql.api.DBManager$WrapperTransaction.getConnectionWrapper(DBManager.java:596) at com.sap.aii.utilxi.sql.api.DBManager.getDBConnectionInt(DBManager.java:333) at com.sap.aii.utilxi.sql.api.DBManager.getDBConnectionInt(DBManager.java:347) at com.sap.aii.utilxi.sql.api.DBManager.getDBConnection(DBManager.java:398) at com.sap.aii.ibrun.server.mapping.stamp.StampPersistor.getConnection(StampPersistor.java:48) at com.sap.aii.ibrun.server.mapping.stamp.StampPersistor.getCurrentStamp(StampPersistor.java:109) at com.sap.aii.ibrun.server.mapping.stamp.StampPersistor.getCurrentStamp(StampPersistor.java:69) at com.sap.aii.ibrun.server.mapping.stamp.DBGlobalStamp.getCurrentStamp(DBGlobalStamp.java:38) at com.sap.aii.ibrun.server.mapping.stamp.DBGlobalStamp.isSameStamp(DBGlobalStamp.java:29) at com.sap.aii.utilxi.pool.SynchronizedGlobalStamp.isSameStamp(Pool.java:157) at com.sap.aii.utilxi.pool.Pool.checkOut(Pool.java:54) at com.sap.aii.ib.server.mapping.execution.MappingPool$RealPool.checkOut(MappingPool.java:121) at com.sap.aii.ib.server.mapping.execution.MappingPool$RealPool.checkOut(MappingPool.java:112) at com.sap.aii.ib.server.mapping.execution.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ib.server.mapping.execution.Mapping.execute(Mapping.java:60) at com.sap.aii.ib.server.mapping.execution.MappingHandler.map(MappingHandler.java:87) at com.sap.aii.ib.server.mapping.execution.MappingHandler.map(MappingHandler.java:71) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:119) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:72) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at sun.reflect.GeneratedMethodAccessor365.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy214.processFunction(Unknown Source) at sun.reflect.GeneratedMethodAccessor401.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:183) at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:267) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:182) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:280) Caused by: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.connector.exceptions.BaseResourceException: Cannot get connection for 0 seconds. Possible reasons: 1) Connections are cached within SystemThread(can be any server service or any code invoked within SystemThread in the SAP J2EE Engine) or they are allocated from a non transactional ConnectionFactory. In case of transactional ConnectionFactory used from Application Thread there is an automatic mechanism which detects unclosed connections, 2)The pool size of adapter "SAPPX2DB" is not enough according to the current load of the system . In case 1) the solution is to check for cached connections using the Connector Service list_conns command or in case 2), to increase the size of the pool. at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:59) at com.sap.aii.ib.server.persist.gen.XiDBManagerStartUp$ServerConnectionProvider.getConnection(XiDBManagerStartUp.java:169) at com.sap.aii.utilxi.sql.api.ConnectionProvider.getConnection(ConnectionProvider.java:66) ... 52 more Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: Cannot get connection for 0 seconds. Possible reasons: 1) Connections are cached within SystemThread(can be any server service or any code invoked within SystemThread in the SAP J2EE Engine) or they are allocated from a non transactional ConnectionFactory. In case of transactional ConnectionFactory used from Application Thread there is an automatic mechanism which detects unclosed connections, 2)The pool size of adapter "SAPPX2DB" is not enough according to the current load of the system . In case 1) the solution is to check for cached connections using the Connector Service list_conns command or in case 2), to increase the size of the pool. at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:226) at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:343) at com.sap.engine.services.connector.jca.ShareableConnectionManager.allocateConnection(ShareableConnectionManager.java:54) at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:51) ... 54 more</Trace>

<Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>

</Trace>

Can asny

[Former Member · Accepted solution]

Hi, looks like this problem with PIs J2EE engine when calling the mapping program: [Unable to Get a Connection From a Data Source described on SAP help|http://help.sap.com/saphelp_nw70/helpdata/en/5c/2f2c4142aef623e10000000a155106/content.htm]. I suggest to consult your basis team.

[Former Member]

Thanks Gurus

[Former Member]

Dear Ram

You can try following if not already tried:

1. Do a Cache refresh (Delta and if required Full)

2. Try deleting and recreating your interface determination

Regards

Sourabh