Shulou(Shulou.com)06/02 Report--

This article introduces the relevant knowledge of "weblogic configuration database connection method". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

1. Problem description

Attachment synchronization sends a file message to the message middleware, and then deletes the corresponding attachment record in the database, repeating this process over and over again, but the recent attachment synchronization seems to have entered an endless loop, and the number of attachments in the message middleware has been increasing. You can see that the following additional number of blocking has reached 10,000, usually only a few hundred attachments a day, how can there be such a large number of attachments?

2. Analysis

Boolean successFlag = SyncManagerService.getInstance (). SendMessageToMQ (message); Log.info ("[LiEMS data synchronization engine log-attachment] send message queue end result successFlg is" + successFlag); if (successFlag) {Log.info ("[LiEMS data synchronization engine log-attachment] delete the dkdocmst_temp table record of the production library"); deleteTempData (db, detailDataObj) Log.info ("[LiEMS data synchronization engine logs-attachments] Delete the end of dkdocmst_temp table records in the production library");}

First send the file to the message middleware, and then delete the corresponding records in the database. The next synchronization will be the future attachment. How can it be sent repeatedly here? besides, the above code is put in the synchronization block.

Synchronized (SyncBizFileDataToMQService.class) {}

The initial suspicion is that the database has not been deleted successfully, so it is time to look for evidence. Open the log and find the following.

[ERROR] [2019-07-04 17:51:53] [SYSTEM] net.luculent.core.database.DBException: Connection has already been closed. With sql is delete from DKDOCMST_TEMP where DOC_ID = '1146689096949694464' and TEMP_PKVAL = '1198020'

3. Reasons

From the above, we can see that the database connection has been automatically released. There is an intuition that it takes too long to send attachments, and how long it takes for inactive connections to be released automatically. But it is not the first time that large attachments have been sent, and the configuration must have been changed on the spot. So I contacted the people on the spot. They said that they had optimized the parameters of weblogic, and all kinds of screenshots confirmed to me, but they didn't look like them. Finally, I thought that the database connection parameters of weblogic were all in the configuration file. So open the configuration file was surprised to find a configuration item Inactive Connection Time-Out, configured 60, immediately asked the scene to remove the configuration, the scene also explained to me that the configuration is based on the optimization manual, to sum up, after all, it took a long time to troubleshoot this problem, and finally attached the meaning of this parameter: https://blogs.oracle.com/saas-fusion-app-performance/inactive-connection-time-out

This is the end of the content of "how to configure database connection with weblogic". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.