Discussion
1
Replies
328
Views
Posted: December 14, 2015
Last activity: April 6, 2018
Closed
Upgrade Failed with Network Adapter could not establish connection error
During the upgrade of migrated rules, the ugprade failed with the above error. The complete stack trace is given below.
[java] Using sun.misc.Perf high-resolution timer for elapsed timings [java] Using Java 5 Management beans for thread CPU timings. [java] Using Java 5 Management beans for process CPU timings: 3840000000 [java] 2015-11-20 12:33:34,043 [ main] [ ] [ ] (.access.PageDatabaseMapperImpl) INFO - DeflateStreams is turned ON. [java] 2015-11-20 12:33:34,105 [ main] [ ] [ ] (pboard.StorageStreamCommonImpl) INFO - engineCodeVersion: 07-10-17 [java] Unable to locate KeyringImpl keyring after trying: [java] <properties> [java] root-pegarules.keyring [java] WHE-304-pegarules.keyring [java] 2015-11-20 12:33:35,852 [ main] [ ] [ ] (l.access.ConnectionManagerImpl) WARN - The database pegadata is only defined in the bootstrap configuration; create a Data-Admin-DB-Name definition [java] pegarules.keyring [java] Nov 20, 2015 12:34:35 PM com.pega.pegarules.internal.bootstrap.PRBootstrap [java] SEVERE: Problem during method invocation (main) [java] com.pega.pegarules.pub.PRException: A problem occurred. [java] From: (unknown) [java] at com.pega.pegarules.deploy.internal.util.ImportImpl.main(ImportImpl.java:398) [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [java] at java.lang.reflect.Method.invoke(Method.java:606) [java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:367) [java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:408) [java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:223) [java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:272) [java] at com.pega.pegarules.pub.PegaRULES.main(PegaRULES.java:85) [java] Caused by: com.pega.pegarules.pub.PRRuntimeException: Error determining the mode of PRPC install from database. [java] at com.pega.pegarules.data.internal.PRDataProviderImpl.isMultiTenantEnvironment(PRDataProviderImpl.java:1135) [java] at com.pega.pegarules.deploy.internal.archive.ParUtilsImpl.setStageDirectory(ParUtilsImpl.java:219) [java] at com.pega.pegarules.deploy.internal.archive.ParUtilsImpl.copyFileToVfsRoot(ParUtilsImpl.java:315) [java] at com.pega.pegarules.deploy.internal.util.ImportImpl.main(ImportImpl.java:261) [java] ... 9 more [java] Caused by: com.pega.pegarules.pub.database.ConnectionException: Database-General Problem encountered when getting connection for database pegarules 17002 08006 IO Error: The Network Adapter could not establish the connection [java] From: (unknown) [java] Caused by SQL Problems. [java] Problem #1, SQLState 08006, Error code 17002: java.sql.SQLRecoverableException: IO Error: The Network Adapter could not establish the connection [java] at com.pega.pegarules.data.internal.access.ExceptionInformation.createExceptionDueToDBFailure(ExceptionInformation.java:256) [java] at com.pega.pegarules.data.internal.access.ConnectionManagerImpl.getConnectionFromDatabaseName(ConnectionManagerImpl.java:856) [java] at com.pega.pegarules.data.internal.access.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:1187) [java] at com.pega.pegarules.data.internal.access.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:1129) [java] at com.pega.pegarules.data.internal.access.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:343) [java] at com.pega.pegarules.data.internal.PRDataProviderImpl.isMultiTenantEnvironment(PRDataProviderImpl.java:1125) [java] ... 12 more
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
This issue is caused due to some host name mentioned in the JDBC URL of the PegaRUELS DB rule from which the DB is not acesssible. Changed the host name properly resolved the issue. But this is not ideal way. We use always use "use configuration in preferences" as How to connect option in the PegaRULES DB rule.