Response not recieved for the Class issue - Pega 7 Upgrade
I am currently upgrading few apps from 6.2 SP2 to 7.2.2. I am using installation and upgrade assistant (IUA) to complete the upgrade process. When the IUA executed one of the targets "Optimize Newly Exposed Columns" in the setupDatabase.xml file, it could not proceed further and is waiting for the response from the class "Rule-Obj-Flow" with a job id. I believe it run into trouble while populating the new columns for the class "Rule-Obj-Flow". I let the IUA open for about 6 hours to see if it could progress but in vain. I am keen to know if anyone of you have encountered this issue while doing the upgrade and the fix that you may have implemented.
Any help is very much appreciated!
I have attached both IUA logs and resume.properties file. The message can be found at the end of the IUA logs.txt file. The constant message that is written to the log is below:
From here the message starts popping up continuously, see below -->
[java] Response not recieved for the Class <Rule-Obj-Flow> JobID <86>.Time elapsed (milliseconds) <1799899>
[java] 2017-03-19 23:05:03,388 [ pool-2-thread-1] [ STANDARD] [ ] ( internal.util.MoveLog) INFO - Response not recieved for the Class <Rule-Obj-Flow> JobID <86>.Time elapsed (milliseconds) <1799899>
Suggestion: So if you upgrade to latest supported driver version of the jar file and also try to modify the JDBC URL as per Pega recommended. Then you can resume the upgrade process and let us know the end result.
Hope this two changes can resolve your issue and will let you know if i find any other issues with your configuration.
That's right I overlooked at the JDBC driver version section of the 7.2.2 platform support guide. It was unfortunate I used the exact JDBC driver version that is known to cause issues in Pega 7. Also I copied the JDBC URL from one of the existing UAT environments which was not suggested.
I used one of the latest version of the type 4 JDBC driver for MS SQL and updated the JDBC URL then resumed the upgrade and it did not help. It failed again at the same step on resume since some changes were already made by the upgrade process. I had to restore the whole database from production. Re-run all the upgrade procedures from the beginning and it worked just fine.
Thanks Mahesh for your thoughts, I really appreciate it.