Release Automation Deployment Error: "For input string" NumberFormatException
search cancel

Release Automation Deployment Error: "For input string" NumberFormatException

book

Article ID: 438339

calendar_today

Updated On:

Products

CA Release Automation - Release Operations Center (Nolio)

Issue/Introduction

Deployment job is in error.

In NAC logs we could see error like this : 
2026-04-01T18:50:28.245+02:00 [JobExecutorThread-5] ERROR (com.nolio.platform.server.execution.tasks.InitializeFlowCommandTask:58) - failed to initialize flow on deployer[<servername>], job[<jobid>], jobServerId[<jobserverid>], message[0].
java.lang.InterruptedException
    at java.lang.Object.wait(Native Method)
    at com.nolio.platform.shared.communication.NimiCommunicationNetwork.doSendRequest(NimiCommunicationNetwork.java:255)
    at com.nolio.platform.shared.communication.NimiCommunicationNetwork.doSendRequest(NimiCommunicationNetwork.java:201)
    at com.nolio.platform.shared.communication.CommunicationNetwork.sendRequest(CommunicationNetwork.java:110)
    at com.nolio.platform.server.deployerapi.DeployerAPI.initFlow(DeployerAPI.java:90)

 

In Agent logs in nolio_action_exe.log we could see an error like this :

2026-04-01T18:50:27.892+02:00 [Communication Msg Processor-54] DEBUG (com.nolio.platform.shared.flowcontrol.service.FlowControlService:41) - FlowControlService has been invoked with request:[FLOW_CONTROL_REQUEST:INIT]
2026-04-01T18:50:27.892+02:00 [Communication Msg Processor-54] DEBUG (com.nolio.platform.shared.flowcontrol.service.FlowControlService:45) - job[<jobid>], jobServerId[<jobserverid>], received [INIT] request.
2026-04-01T18:50:27.892+02:00 [Communication Msg Processor-54] DEBUG (com.nolio.platform.shared.datamodel.Action:426) - Next Action Execution State ResolveInParameters
2026-04-01T18:50:27.892+02:00 [Communication Msg Processor-54] ERROR (com.nolio.platform.shared.datamodel.ActionProxy:111) - For input string: "180
"
java.lang.NumberFormatException: For input string: "180
"
 at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
 at java.lang.Long.parseLong(Long.java:589)
 at java.lang.Long.parseLong(Long.java:631)
 at com.nolio.platform.shared.utils.ReflectionUtils.tryAssignFromString(ReflectionUtils.java:253)
 at com.nolio.platform.shared.utils.ReflectionUtils.setFieldInObject(ReflectionUtils.java:158)
 at com.nolio.platform.shared.utils.ReflectionUtils.setFieldInObject(ReflectionUtils.java:119)
 at com.nolio.platform.shared.datamodel.ActionProxy.createAction(ActionProxy.java:105)
 at com.nolio.platform.shared.flowcontrol.service.FlowActionProxyReplacer.createActionFromActionProxy(FlowActionProxyReplacer.java:74)
...
 at java.lang.Thread.run(Thread.java:750)

2026-04-01T18:50:27.892+02:00 [Communication Msg Processor-54] ERROR (com.nolio.platform.shared.flowcontrol.service.FlowControlService:87) - failed initialize flow for job[<jobid>], jobServerId[<jobserverid>].
java.lang.RuntimeException: Failed to create action from ActionProxy[ActionProxy[REMOTE]:ActionProxy]
 at com.nolio.platform.shared.flowcontrol.service.FlowActionProxyReplacer.createActionFromActionProxy(FlowActionProxyReplacer.java:77)
 at com.nolio.platform.shared.flowcontrol.service.FlowActionProxyReplacer.replaceSingleStepActionProxies(FlowActionProxyReplacer.java:45)
 at com.nolio.platform.shared.flowcontrol.service.FlowActionProxyReplacer.replaceActionProxies(FlowActionProxyReplacer.java:38)
 at com.nolio.platform.shared.flowcontrol.service.FlowDataFactory.initFlow(FlowDataFactory.java:93)
 at com.nolio.platform.shared.flowcontrol.service.FlowDataFactory.create(FlowDataFactory.java:85)
...
 at java.lang.Thread.run(Thread.java:750)
Caused by: com.thoughtworks.xstream.converters.ConversionException: Could not setup an action :For input string: "180
"
---- Debugging information ----
message             : Could not setup an action :For input string: "180
"
cause-exception     : java.lang.NumberFormatException
cause-message       : For input string: "180
"
-------------------------------

A non-numeric character (like a line feed) is present in an integer-type action parameter.

Environment

Release Automation 6.9.x
Microsoft SQL Server database

Cause

A non-numeric character (e.g., a hidden line feed) was introduced into an integer-based action parameter, causing a java.lang.NumberFormatException during flow initialization.

Resolution

CAUTION: Manual database updates should only be performed after a full database backup.

  1. Make sure to have a backup of database before doing the update in database.

  2. From error message convert the wrong integer value in hexadecimal string.

    Example : 180 + Line Feed becomes 043138300A

    0x04 - Number of characters
    0x31 - Ascii code 49 (character 1)
    0x38 - Ascii code 56 (character 8)
    0x30 - Ascii code 30 (character 0)
    0x0A - Ascii code 10 (Line Feed)

  3. Execute the following SQL Query in database :

    SELECT * FROM concrete_value WHERE CONVERT(VARCHAR(1000), value, 2) like '%043138300A'

    This returns the IDs and values of parameter values with problem.

    Example :

    ID      value
    752    0xACED00057400043138300A
    753    0xACED00057400043138300A
    754    0xACED00057400043138300A
    755    0xACED00057400043138300A

  4. Remove the characters 0A at the end and decrement the number of characters from 4 to 3

    Example : 
    0xACED00057400043138300A becomes
    0xACED0005740003313830

  5. Execute the update queries to correct the values.
    Example based on above example :
    UPDATE concrete_value SET value=0xACED0005740003313830 WHERE ID=752 and value=0xACED00057400043138300A
    UPDATE concrete_value SET value=0xACED0005740003313830 WHERE ID=753 and value=0xACED00057400043138300A
Powered by Wolken Software