Updated SQL Connection String in Process restarted process java crashes fills disk
search cancel

Updated SQL Connection String in Process restarted process java crashes fills disk

book

Article ID: 136065

calendar_today

Updated On:

Products

CA Process Automation Base

Issue/Introduction

I was working on connecting to a new database via the SQL query operator.  I used a connection string from a previous process and was getting errors. I changed the connection string to try and get it to use NTLM and started the process. A java dump was created in my c20/server directory multiple times and I ran out of disk space.  I removed the dumps and restarted and the same happened again. 

How do I kill that process so I can resume use of my machine with out dumping Java.


Environment

Release : 4.3

Component : Process Automation

Resolution

Stop the orchestrator service.

Open oasisconfig.properties in the /c2o/.config folder and add the following line to the bottom of the file:

pam.disable.bootup.recovery=true


Restart the orchestrator and navigate to the operations tab and abort the process before it recovers and restarts.


The setting can be left in the oasisconfig.properties file without harm. It does not disable recovery of processes, it just disables that recovery from happening during boot up of the orchestrator.