Remote Command execution failed

Hello,

I'm facing a issue while running a deployment against few environments. Below is the error.

2017-07-18 10:51:35,703 [Thread-22] DEBUG com.midvision.rapiddeploy.plugins.transport.remoting.server.RemoteInvocationHandler - Run the batch command in thread: 40
2017-07-18 10:51:35,704 [Thread-22] DEBUG com.midvision.rapiddeploy.domain.task.core.AbstractBatch - prepareDefinitionFile
2017-07-18 10:51:35,704 [Thread-22] DEBUG com.midvision.rapiddeploy.domain.task.core.AbstractBatch - project [XXXXXXXXXXXXXXXXXX] definition [/opt/midvision/XXXX/buildstore/20170718105129389_midvision-deploy-orchestration.xml] server [XXXXXXXXXXXXXX] environment [XXXX] instance [null] application [XXXXXXXXXXX]
2017-07-18 10:51:35,704 [Thread-22] DEBUG com.midvision.rapiddeploy.domain.task.core.AbstractBatch - deployFile [/opt/midvision/was80/buildstore/XXXXXXXXXXXXXXXXXX-XXXXXXXXX_INJECTED.jar] 
2017-07-18 10:51:35,705 [Thread-22] DEBUG com.midvision.rapiddeploy.domain.task.core.AbstractBatch - Empty argument found.
Failed RapidDeploy Deployment Request Code: 200Remoting Command Execution Error (details follow):

CommandExecutionException [RapidDeployBusinessException [com.midvision.rapiddeploy.exceptions.CommandExecutionException:  Failed RapidDeploy Deployment Request Code: 200]]

Could you please suggest from where this variable instance [null]  is getting added? I am not seeing this parameter while running deployment against few environments.

Thanks.

Arumugam Subramanian
Arumugam Subramanian
4
| 1 1 1
Asked on 7/18/17, 5:44 PM
0
vote
273 Views

Hello, I'm using RapidDeploy Version 3.5.14.

Thanks for the suggestion. it will help to narrow down the problem. How do we check the version of agent? could you please provide some options?

Arumugam Subramanian
Arumugam Subramanian
4
| 1 1 1
Answered on 7/18/17, 8:22 PM
0
vote

Hi, The 'instance' object (and references to it) was removed as part of the 3.5.0 release. It could be that you are using a version of remote agent from an earlier release (3.4 or older) and this is why you see this in the logs because the RD agent is still expecting the instance object. Without further logging info it is hard to tell.

Richard Bettison
on 7/19/17, 10:53 AM

Thanks for the suggestion. it will help to narrow down the problem. How do we check the version of agent? could you please provide some options?

Arumugam Subramanian
on 7/20/17, 5:26 AM

Hi, The 'instance' object (and references to it) was removed as part of the 3.5.0 release. It could be that you are using a version of remote agent from an earlier release (3.4 or older) and this is why you see this in the logs because the RD agent is still expecting the instance object. Without further logging info it is hard to tell.

Administrator
Administrator
10245
| 1 0 0
Answered on 7/19/17, 11:16 AM
0
vote

Hi,

Please could you indicate which version of RapidDeploy you are using when you see this error?

Best Regards

Richard Bettison
Richard Bettison
790
| 1 0 0
Answered on 7/18/17, 7:36 PM
0
vote

Your answer

Please try to give a substantial answer. If you wanted to comment on the question or answer, just use the commenting tool. Please remember that you can always revise your answers - no need to answer the same question twice. Also, please don't forget to vote - it really helps to select the best questions and answers!

Ask a Question

Keep Informed

About This Forum

This community is for professionals and enthusiasts of our products and services.

Read Guidelines

Question tools

3 follower(s)

Stats

Asked: 7/18/17, 5:44 PM
Seen: 273 times
Last updated: 7/20/17, 5:25 AM