Migration Error to 16.2

sandeepg138 over 7 years ago

Hello,

I am experiencing a Migration error when migrating to 16.2 from 16.1 version.
Below is the error:

####<Sep 9, 2016 8:08:30 AM GMT> <Notice> <Stdout> <VMRAPPIANUATAP1> <AppianServer> <Appian PoolManager.CheckInvalidConnections - 0> <<WLS Kernel>> <> <> <1473408510527> <BEA-000000> <2016-09-09 08:08:30,527 [Appian PoolManager.CheckInvalidConnections - 0] ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Failure to read socket: personalization (vmrappianuates1:5012)>
####<Sep 9, 2016 8:08:45 AM GMT> <Notice> <Stdout> <VMRAPPIANUATAP1> <AppianServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1473408525550> <BEA-000000> <2016-09-09 08:08:45,535 [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR com.appiancorp.common.config.ConfigObject - An error occurred while trying to initialize the config object...

Discussion posts and replies are publicly visible

0 sandeepg138 over 7 years ago

... com.appiancorp.process.security.InitializeAdministrator
com.appiancorp.kougar.driver.exceptions.SafeRetryException: Unable to acquire a Read connection. Safe to retry.

Note: All the Appian Engines are working fine.

Regards,
Sandeep.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 nileshr889 over 7 years ago

Hi Sandeep,

I faced the same issue on Linux machine. For this you need to change the owner of Appian installation directory. Change the owner to appian user. And then restart the jboss.
Let me know if you still face the issue.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 7 years ago

This error:

ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Failure to read socket: personalization

indicates the application server cannot communicate with the engines.

If you are 100% sure the engines report all Okay when running checkengine, then review this article: forum.appian.com/.../kb-1000.html where it is explained the importance of synchronizing appian.sec among all servers.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sandeepg138 over 7 years ago

Hello Eduardo,

So does it mean, in 16.2 Appian.sec file should be same in both Engine and Ap server. Currently Appian.sec file is different in both the servers.
Pls confirm.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 7 years ago

That is correct:

<APPIAN_HOME>\\ear\\suite.ear\\conf\\appian.sec

should be the SAME in all servers.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sandeepg138 over 7 years ago

Thanks Eduardo, I will try this and let you know this week.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 samw8931 over 7 years ago

@sandeepg138, I am running into similar issues, have you ever got the issue resolved ?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel