Question
Infosys
US
Last activity: 24 Aug 2016 10:49 EDT
BIX process hangs sometimes
We are using PRPC 7.1.8, and BIX ruleset version Pega-BIX:07-10-17 ,
com.pega.pegarules.bootstrap.codeset.version.Pega-EngineCode=07-10-17
We run BIX process from command line
Sometimes, but not always, the process hangs, i.e. the java program simply hangs and do not return. There is no error message in the log file.
We have to kill the process and try again. Sometimes, retry is sucessful; but sometimes, retry also fails.
The hang mainly happens during bootstrap.
Is this a known issue? What may have caused this problem?
***Updated by moderator: Lochan to add Category***
Accepted Solution
Infosys
US
This issue disappered after using the latest jdbc driver for 12c database. We were using a jdbc driver for 11g db.
Pegasystems
IN
Hi Yining,
We haven't seen this issue before. Kindly share the prconfig.xml & prbootstrap.properties file along with a thread dump when the hang happens. This should provide us with details to understand the issue.
Are we sure that the BIX command line is being run with a good network access to the production database. Slow connection (network) to the database can cause such hangs.
-Rajiv
Infosys
US
Now the BIX process hangs during extracting.
There are 71670 instances to be extracted. In one run, it hangs after writing 256 instances to the output file; in second run, it hangs after writing 435 instances to the output file.
There are enough free disk space for the output folder.
The BIX log file is attached.
There is no error message in the log file. The last message is
"2016-08-16 12:37:26,705 [ apsrs3902.uhc.com] [ ] [ ] ( internal.access.ExtractImpl) INFO - XML File ICARE_ExtractWork_Output is created in /icare/bix/app/extracts"
Updated: 9 Aug 2016 2:07 EDT
Virtusa IT Consulting
AE
If process is getting hanged during bootstrap load, probably the reason could be that DB connection was not returned from the pool, so you can probably check connection pooling settings. You can also put a debug logger as com.pega.pegarules.data.internal.access.ExtractImpl in prlogging.xml file which you can find in \114819_Pega718\Additional_Products\BIX\config\prlogging.xml
Once you enable the above logger to debug, There will be a message printed in the logs as "Successfully Connected to DB: " if connection is successful else it'll throw an error.