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 » IBM MQ File Transfer Edition » FTE Managed call multiple JVM

Post new topic  Reply to topic
 FTE Managed call multiple JVM « View previous topic :: View next topic » 
Author Message
matuwe
PostPosted: Mon Apr 04, 2011 2:01 pm    Post subject: FTE Managed call multiple JVM Reply with quote

Master

Joined: 05 Dec 2007
Posts: 296

Hi, Can anyone help.. We have MQFte 7.0.3 running ok. but latly we noticed that fte agent hangs if we have tooooo many files to transfer. As we investigated, it was found that this could be memory related as each transfer creates/starts a new jvm.. Did we deploy this correctly? and why does it stop transferring files once it gets to maximum number of transfers.. Doesn't make sense I am hoping these multiple jvm's are caused by us.
Back to top
View user's profile Send private message
elvis_gn
PostPosted: Mon Apr 04, 2011 7:58 pm    Post subject: Reply with quote

Padawan

Joined: 08 Oct 2004
Posts: 1905
Location: Dubai

Hi matuwe,

I'm not sure if my suggestion is the right way to resolve this issue, but you could look at the agent.properties file and restrict the max transfers from/to the agent, thereby preventing the JVMs going out of control.

Regards.
Back to top
View user's profile Send private message Send e-mail
matuwe
PostPosted: Mon Apr 04, 2011 11:07 pm    Post subject: Reply with quote

Master

Joined: 05 Dec 2007
Posts: 296

Hi

Here is a sample copy of my agent.properties

1. Multiple Threads are started, each per transfer
2. When I have the max transfer set 10 and and I receive 15 file, then 10 are started and the other 5 stays in waiting/queued state and never gets transfered. The multiple java proceceses then stays in hanging state.

Code:



commandPath=/gptt/SNGFTE1/agents/SNGFTEJHB1/scripts:/usr/bin
sandboxRoot=/gptt/SNGFTE1/agents/SNGFTEJHB1/scripts:/gpfsfcb

maxSourceTransfers=1000
maxDestinationTransfers=1000
maxTransferNegotiationTime=120000
senderTransferRetryInterval=60000
agentStatusPublishRateLimit=10
maxCommandOutput=204800
monitorReportTriggerFail=true
monitorReportTriggerSatisfied=true
agentDataCompression=MQCOMPRESS_ZLIBHIGH

agentQMgrStandby=sngfte2(54131)
Back to top
View user's profile Send private message
mphillip
PostPosted: Mon Apr 11, 2011 1:20 am    Post subject: Reply with quote

Apprentice

Joined: 03 Feb 2009
Posts: 49

"maxSourceTransfers=1000
maxDestinationTransfers=1000 "


This will kill your agent. This is the number of concurrent transfers that an agent will process at once. You are telling it to have yup to 2000 transfers IN MEMORY at once.

Bring both these numbers back down to the default of 25, or better yet, down a bit lower to 10 (one chap I know thinks that 10 is a better default).
Back to top
View user's profile Send private message
Gerd-in-ZA
PostPosted: Wed Apr 27, 2011 2:21 pm    Post subject: PMR active for this Reply with quote

Novice

Joined: 13 Sep 2006
Posts: 14
Location: Johannesburg, South Africa

A client of mine is pursuing this exact situation via a PMR. You are describing two separate issues here: One is that managed calls will crank up JVMs - and many concurrent managed calls will crank up many concurrent JVMs - and the total of that may exceed your system's capacity. The other issue is that for some reason the extra transfers that cannot be scheduled immediately are never picked up later.

Given that the PMR is still under way I would expect an answer to the second issue to come out of that process; the first issue will probably become the subject of a lot of best practice advice in due course.

Please also note: A managed transfer becomes an extra thread inside the agent's JVM (which is generally cheap), but a managed call will run outside of that environment - e.g. in a JVM running the ANT engine, which then could even start other JVMs depending on what it is you do.

In view of that you may also want to think hard before setting your call to "await the outcome" of a transfer, because that will extend the lifespan of the extra JVMs significantly, locking in the resources in question.

One general word of caution: FTE is a very well thought out and comprehensive package for the issue of managed file transfer. But ...

Excuse me: BUT!!!

Properly abused, it can fill any amount of computing resources you may have or not have with an amazing ease. Ahem!
_________________
-- Gerd --
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 » IBM MQ File Transfer Edition » FTE Managed call multiple JVM
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.