ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Issues with PuTTY and JobExecution Nodes

Post new topic  Reply to topic
 Issues with PuTTY and JobExecution Nodes « View previous topic :: View next topic » 
Author Message
rhine
PostPosted: Tue Nov 17, 2015 1:56 am    Post subject: Issues with PuTTY and JobExecution Nodes Reply with quote

Novice

Joined: 17 Nov 2015
Posts: 16

Hi everyone, this is my first post here. Sorry if im not familiarized with the forum and this post is not in the best spot.

I have a message flow that among other things makes a call via PuTTY to a remote system to generate a file executing a script located in this remote system.
When i make this call, with the same commands through the system console, its all working, and after the succesful call, PuTTY closes the session.

But when these scripts are executed in MessageBroker via JobExecution Node, the log of this specific node says: The process cannot access the file because it is being used by another process.

I think the session may remain opened. Just generated the files in remote system once. After it I cannot generate them, with the same flow and scripts.

Does anyone have any idea or recommendation?

Thanks in advance.
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Nov 17, 2015 5:21 am    Post subject: Re: Issues with PuTTY and JobExecution Nodes Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

rhine wrote:
Does anyone have any idea or recommendation?


Don't use broker for this. You're almost certainly correct in that the node has spun up another command shell with a PuTTy executable running in it. Both of those processes are not under the control of broker and either could hang up for any reason.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Tue Nov 17, 2015 5:27 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

You might try creating a local script that starts putty, in the background. Then call that from jobexecution node.

This means you won't be able to tell when the script has finished from your message flow - unless you also do something in the script to send some kind of response to the flow (amqsput?)
_________________
chmod -R ugo-wx /
Back to top
View user's profile Send private message
rhine
PostPosted: Wed Nov 18, 2015 9:03 am    Post subject: Reply with quote

Novice

Joined: 17 Nov 2015
Posts: 16

The problem was the host key not being present in the cache of the remote machine. both ways.

Thank you for the help.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Issues with PuTTY and JobExecution Nodes
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.