Cocould not create pool connection. The DBMS driver exception was: Io exception: Broken pipe, dbmspipe
On-site feedback from colleagues: middleware weblogic cannot connect to the database Oracle. You can see the following in the log:
Caused by: weblogic. common. ResourceException: weblogic. common. ResourceException: cocould not create pool connection. The DBMS driver exception was: Io exception: Broken pipe
At weblogic. jdbc. common. internal. ConnectionEnvFactory. createResource (ConnectionEnvFactory. java: 256)
At weblogic. common. resourcepool. ResourcePoolImpl. makeResources (ResourcePoolImpl. java: 1180)
At weblogic. common. resourcepool. ResourcePoolImpl. makeResources (ResourcePoolImpl. java: 1104)
At weblogic. common. resourcepool. ResourcePoolImpl. start (ResourcePoolImpl. java: 244)
At weblogic. jdbc. common. internal. ConnectionPool. doStart (ConnectionPool. java: 1065)
At weblogic. jdbc. common. internal. ConnectionPool. start (ConnectionPool. java: 146)
At weblogic. jdbc. common. internal. ConnectionPoolManager. createAndStartPool (ConnectionPoolManager. java: 385)
At weblogic. jdbc. common. internal. ConnectionPoolManager. createAndStartPool (ConnectionPoolManager. java: 326)
Diagnosis process:
1. Familiar with the environment. The application server and database server are both AIX.
2. Check the connectivity between the application server and the database server, ping the ip address of the database server on the application server, ping for one minute, and there is no packet loss problem. Telnet the database server IP Address: port on the Application Server. The connection is normal.
3. log on to the database server, view the listening log listener. log, and find that the ip address of the application server is normal.
4. Disable the firewall on the database server.
5. Redeploy a domain, create a connection pool, and test. Therefore, the system is released on the newly deployed domain, and the test system is accessible.
The local diagnosis result is:It is likely that the domain is damaged.