cancel
Showing results for 
Search instead for 
Did you mean: 

Who: Unable to get a connection from the pool#

ganimede_dignan
Contributor
0 Kudos

Hi,

I've got several messages as:

#2.0#2019 07 15 10:31:40:400#+0200#Error#/Applications/XMII# ##sap.com/xapps~xmii~ear#C0000A00004028790000000100002007#3014652000059589#sap.com/xapps~xmii~ear#com.sap.xmii.Illuminator.tools.database.ConnectionHolder#IT-JOBSYS#0##352D0BB5A5B911E986D00000002DFFFB#352d0bb5a5b911e986d00000002dfffb##0#Thread[pool-8-thread-534,5,Managed_Application_Thread]#Plain## Unable to get a connection from the pool#

#2.0#2019 07 15 10:31:40:459#+0200#Error#/Applications/XMII# ##sap.com/xapps~xmii~ear#C0000A00004028790000000300002007#3014652000059589#sap.com/xapps~xmii~ear#com.sap.xmii.Illuminator.logging.ErrorHandler#IT-JOBSYS#0##352D0BB5A5B911E986D00000002DFFFB#352d0bb5a5b911e986d00000002dfffb##0#Thread[pool-8-thread-534,5,Managed_Application_Thread]#Plain## java.lang.Throwable: Cannot create a connection to the database#

How can I check what application/transaction done it? How can I check the name of data server?

Thank you.

kaus19d
Active Contributor
0 Kudos

Could you please ask your BASIS guys to assist with default-trace file & application.log files. For now i can only suggest to check the services in "Application Resource" in your java NWA

Also check if there is a Jco created for this sort of connection

Thanks,

Kaushik

0 Kudos

Is this a new problem with an existing and stable system environment? Or are you in the middle of development and having this problem?

Regards, Mike

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member185280
Active Contributor
0 Kudos

If look at the Connection status screen (MII Menu-->Data Services-->Connection Status) you can see all the connections as well as their max used count and max wait times etc. Based on this information and the knowledge you have of the architecture and capabilities of the implementation you can adjust the pool settings on your individual Data Server connections.

FYI I think sometimes you can get messages like this because the pool doesn't have a connection ready to go but then it just spools one up and there is no actual error/failure in the transaction. You could get a performance benefit by configuring the pool to always have enough connections ready to go but you need to balance that with the pool holding extra connections that may not get used much or at all.

Oh also there can be settings on the DB side that limit the number of connection allowed so be aware of that as well.

Regards,
Christian