Java Adapter services getting down in PI 7.3.1.

[phanikumar_akella]

Dear Experts

We are facing server level issues on our PI 7.3.1 system built on Oracle 11.2.0.3.0 and Linux GNU SLES-9 x86_64. Its a newly built system. Java Adapter services are getting down for one particular node. I have searched in SDN for similar kind of issues. Not much information available. Can you please look into this and support me with your suggestions. Thanks in advance.

Component Monitoring: Central Adapter Engine

15 of 23 connection(s) registered successfully
8 of 8 protocol handler registered successfully

Connection registration failed for connection RNIFAdapter on node 89687851 due to: Failed to register connection RNIFAdapter. Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Failed to load messages into Queue RNIFAdapterRecv from database. Reason: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.
Connection registration failed for connection test on node 81298551 due to: Failed to register connection test. Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Failed to load messages into Queue testRecv from database. Reason: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.
Connection registration failed for connection File_http://sap.com/xi/XI/System on node 89687851 due to: Failed to register connection File_http://sap.com/xi/XI/System. Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Failed to load messages into Queue File_http://sap.com/xi/XI/SystemRecv from database. Reason: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.
Connection registration failed for connection IDoc_AAE_http://sap.com/xi/XI/System on node 89687851 due to: Failed to register connection IDoc_AAE_http://sap.com/xi/XI/System. Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Failed to load messages into Queue IDoc_AAE_http://sap.com/xi/XI/SystemRecv from database. Reason: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.
Connection registration failed for connection HTTP_AAE_http://sap.com/xi/XI/System on node 89687851 due to: Failed to register connection HTTP_AAE_http://sap.com/xi/XI/System. Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Failed to load messages into Queue HTTP_AAE_http://sap.com/xi/XI/SystemRecv from database. Reason: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.
Connection registration failed for connection MPA on node 89687851 due to: Failed to register connection MPA. Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Failed to load messages into Queue MPARecv from database. Reason: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.
Connection registration failed for connection MPA on node 81298551 due to: Failed to register connection MPA. Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Failed to load messages into Queue MPARecv from database. Reason: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.
Connection registration failed for connection RNIF11Adapter on node 89687851 due to: Failed to register connection RNIF11Adapter. Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Failed to load messages into Queue RNIF11AdapterRecv from database. Reason: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.
Connection registration failed for connection JPR on node 89687851 due to: Failed to register connection JPR. Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Failed to load messages into Queue JPRSend from database. Reason: com.sap.engine.services.dbpool.exceptions.BaseSQLException: ResourceException occurred in method ConnectionFactoryImpl.getConnection(): javax.resource.ResourceException: (Failed in component: dbpool, BC-JAS-TRH) Cannot create connection. Possible reasons: 1)Maximum allowed connections to DB or EIS is reached. You can apply CSN Note 719778 in order to check and resolve connection leaks. 2) Configuration to DB/EIS is wrong or DB/EIS is temporary unreachable. 3) Connections are not enough for current load.

Errors reported while registering connections and/or protocol handlers

[Former Member]

Seams that something wrongs with the Post installation of the P.I.

Does worked fine before?

If not.

Execute the following steps.

1. Login into NWA  and go to Configuration Wizard
2. Execute Netweaver Initial Setup
3. Provide the information of the SLD (If does local, put the local info)
4. Upgrade the CIM contents
5. Now check this: SLD/ Development / CIM Instances / XI Integration Server / Clases, and check the systems, the PI that you have finished the initial wizard should appear now here.
6. Restart the following services:
   com.sap.xi.directory (Integration Builder/Configuration)
   com.sap.aii.af.app (Adapter Engine)com.sap.xi.rwb (Runtime Workbench)
   com.sap.xi.repository (Integration Builder/Design)
7. Go to RWB and build a Test (If you dont have the correct version of Java, Ask to PI consultant test this)

The Test should be fine.

If not, go to the Java Services Again and Start the following service:

• com.sap.aii.af.cpa.app

hope does this work.

[Former Member]

Hi,

how you've solved the problem?

Thanks

Umberto

[Former Member]

Dear Team,

I am facing the same issue in SLD(PI Java Stack).

Please find below snapshot. Please Help. Many Thanks .....

[Former Member]

Did you ever find a solution for this problem? I am facing a similar issue.

[Former Member]

Hi,

Can you please try the below changes

Change the maximum number of connections or waiting time depending on the load

.

In addition be sure the TS Timeout value is set to 300.  To check this value and change it if necessary do the following.

1. Open the Config Tool.

2. in the Config Tool, in the tree on the left navigate to cluster-data > template > instance > services > ts.

3. On the right side of the screen, verify the value of the TransactionTimeout Key.  If the value is 300 then the setting is correct.  If the value is not 300 then change it as follows.

4. Select the TransactionTimeout row.

5. In the Custom Value field enter 300.

6. Click the "Set Custom Value" button.  The table will show the new custom value.

7. Click the Save button.

8. Stop NetWeaver.

9. Start NetWeaver.  The change will now take effect

Please also check that there is no issues in the UME configuration.

Thanks

Rishi Abrol

[Former Member]

Rishi,

Thanks for the suggestions, but luckily this issue ended up being related to something wrong with the HANA driver that was uploaded into the SAP NetWeaver Administrator page. Perhaps it got corrupted or something during moving the file around or during the upload process. Anyways, I simply deleted the driver and the associated data source, recreated both and the error went away.

Thanks,

Kevin