Question

Running BIX from command line causing issues to stream nodes

Hi,

Whenever I am running .sh file which contains code to execute BIX from command line, it is impacting Stream nodes and Queue processors are getting stopped.

also in logs I can see that the process tries to start Stream server but as this node is no where related to Stream but it caused issue in production and then we had to disable BIX node as a rollback plan.

Please let me know if someone has some idea on this.

Attaching documents,

Logs(PegaRULES.txt)

***Edited by Moderator: Lochan to update platform capability tags***

Correct Answer
August 22, 2019 - 7:15pm

Thanks all for your reply. I raised SR and got the fix. We need to add below configuration in BIX-prconfig.xml to stop this process to start streaming service.

<env name="asyncExecutor/enable" value="false" /> 

Comments

Keep up to date on this post and subscribe to comments

August 19, 2019 - 7:37am

You should separate stream nodes from other node types. Normally BIX nodes should be running in the node along with BackgroundProcessing/DataFlow/etc. In your BIX command line, you can use -DNodeType to specify the NodeType.e.g., -DNodeType=BIX.

August 20, 2019 - 2:19am
Response to KevinZheng_GCS

Thanks Kevin. I have tried this by putting into my script file. Pls see below code:

"export JAVA_HOME=/usr/java/latest/
export JAVA_HOME=/usr/java/jdk1.8.0_181-amd64
export PATH=$PATH:$JAVA_HOME/bin

driver=/opt/tomcat/lib/POSTGRESJDBC-42.2.5.jar
shDir=/efs/BIX/Configs
bixDir=/efs/BIX/Configs
userdir="-Duser.dir=/opt/app"
classpath="$bixDir:$bixDir/lib/jsr94-1.0.jar:$bixDir/lib/prbootstrap-api.jar:$bixDir/lib/prbootstrap.jar:$bixDir/lib/prdbcp.jar:$driver"

echo "Classpath - $classpath"

java -Xms512M -Xmx1G -DNodeType=BIX -cp "$classpath" -Dpegarules.config=$shDir/prconfig.xml -Dpegarules.logging.configuration=$shDir/prlog4j2.xml  -Dcom.pega.pegarules.bootstrap.properties.url="file://$shDir/prbootstrap.properties" -Dpega.prbootstrap.config=$shDir/prbootstrap.properties -Dcom.pega.pegarules.bootstrap.ignorejndi=true com.pega.pegarules.pub.PegaRULES com.pega.pegarules.data.internal.access.ExtractImpl -a "*****" -p "*****" -i 'Extract ins name'

"

but still in the logs we can see that this process is starting Stream service and stream nodes are getting affected.

Please suggest.

August 20, 2019 - 7:51am

can you attach your prconfig.xml? I would like to see if certain settings enabling this.

August 21, 2019 - 5:43am
Response to KevinZheng_GCS

Hi Kevin, PFA prconfig.xml.

August 21, 2019 - 9:33am
Response to MadhusudanS9253

Perhaps the BIX node is still listed as a Stream node? If you navigate to Configure > Decisioning > Infrastructure > Services > Stream, do you see the BIX node still listed there? If so, you can try to decommission it from that landing page.

August 22, 2019 - 7:15pm

Thanks all for your reply. I raised SR and got the fix. We need to add below configuration in BIX-prconfig.xml to stop this process to start streaming service.

<env name="asyncExecutor/enable" value="false" />