| Author |
Message
|
| varunraot |
 Posted: Mon Apr 03, 2017 6:35 am Post subject: BFGSS0030W: MQ MFT error |
 |
|
Acolyte
Joined: 01 Jun 2011
Posts: 50
|
Scenario: I have IIB V10 message flow which makes use of FTE output node to write the file to a directory in an another server ( Server A) with the help of agent defined( say Agent A) in that server A
Recently we came across a situation where file transfer failed( From IIB to Server) with below error
"BFGSS0030W: The agent is already acting as the source agent for the maximum number of file transfer operations and unable to queue further requests due to the queued transfer limit of 1000 being reached. The new transfer will not be carried out"
This made Agent A to go a recovery state "BFGTR0063I: Transfer ID: 414d5120514d4d464751523031202020cb0ed45823616863 entering recovery, immediately, due to recoverable error: BFGTR0059I: The transfer receiver timed out waiting for data from the source agent" in the Server A
I was able to reproduce this error by creating a bottleneck by releasing more than 1000 messages to the IIB flow.
I created an agent in the server where IIB flow has been deployed and made that agent to transfer the file to the server A with the more load( 10000 messages at one shot) and to my surprise, it did not result in above error.
Not sure what is the reason for this peculiar behavior? |
|
| Back to top |
|
 |
| gbaddeley |
| Posted: Mon Apr 03, 2017 4:01 pm Post subject: |
|
|
Padawan
Joined: 25 Mar 2003
Posts: 1781
Location: Melbourne, Australia
|
The number of queued transfers will depend on how quickly they are requested, and how quickly the FTE/MFT agents are able to complete them. The limit is specified in the agent properties file.
There may also be "stuck" transfers that are unable to complete. These contribute to the queued count. Check the depth of the agents state queues.
The agent should be able to process at least 30 - 50 transfers / sec, if the files are small and the wind is blowing in the right direction.
_________________
Glenn |
|
| Back to top |
|
|
| varunraot |
| Posted: Mon Apr 03, 2017 8:21 pm Post subject: |
|
|
Acolyte
Joined: 01 Jun 2011
Posts: 50
|
Here is the thing.
Scenario 1: When an attempt was made to write the file from IIB flow ( via embedded agent i.e when the message flow containing FTE output node gets deployed to an execution group) to a directory in an another server( say B), the error BFGSS0030W occurs with uncontrolled release of more than 1200 messages. Please note that the queue depth of STATE queues were sufficient. The maxQueuedTransfers property was set to 5000.
Scenario 2: I introduced an agent in the Server A( where IIB flows are deployed). IIB flow was made to transfer the file from FTE output node ( embedded agent) to the interim folder in the server A. MQ MFT monitor was created to transfer the file from the interim folder in Server A to the actual destination directory in Server B. The error BFGSS0030W did not occur in this case with uncontrolled release of 10,000 messages. Pleas note that the maxQueuedTransfers property was set to 5000 in both the agents ( A & B)
The question here is
Why was scenario 2 worked fine with more volume compared to the first scenario with less volume ? |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Tue Apr 04, 2017 5:59 pm Post subject: |
|
|
Padawan
Joined: 25 Mar 2003
Posts: 1781
Location: Melbourne, Australia
|
| Quote: |
| Scenario 1: When an attempt was made to write the file from IIB flow ( via embedded agent i.e when the message flow containing FTE output node gets deployed to an execution group) to a directory in an another server( say B), the error BFGSS0030W occurs with uncontrolled release of more than 1200 messages. Please note that the queue depth of STATE queues were sufficient. The maxQueuedTransfers property was set to 5000. |
What is the text of the BFGSS0030W error? Was it "The agent is already acting as the source agent for the maximum number of file transfer operations and unable to queue further requests due to the queued transfer limit of 5000 being reached. The new transfer will not be carried out"
_________________
Glenn |
|
| Back to top |
|
|
| varunraot |
| Posted: Wed Apr 05, 2017 1:44 am Post subject: |
|
|
Acolyte
Joined: 01 Jun 2011
Posts: 50
|
The error was "The agent is already acting as the source agent for the maximum number of file transfer operations and unable to queue further requests due to the queued transfer limit of 1000 being reached"
Please note that the threshold "1000" was being shown even though maxQueuedTransfers property was set to 5000 in the agent.properties of Server B |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Wed Apr 05, 2017 5:22 pm Post subject: |
|
|
Padawan
Joined: 25 Mar 2003
Posts: 1781
Location: Melbourne, Australia
|
Did you restart the MFT agent after changing the properties file? The agent reads this at start up, and reports all the values it is using in its output log.
_________________
Glenn |
|
| Back to top |
|
|
| varunraot |
| Posted: Wed Apr 05, 2017 6:55 pm Post subject: |
|
|
Acolyte
Joined: 01 Jun 2011
Posts: 50
|
| Yes. Agent has been restarted post the changes in agent.properties file for maxQueuedTransfer. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu Apr 06, 2017 3:46 pm Post subject: |
|
|
Padawan
Joined: 25 Mar 2003
Posts: 1781
Location: Melbourne, Australia
|
| varunraot wrote: |
| Yes. Agent has been restarted post the changes in agent.properties file for maxQueuedTransfer. |
If you've properly changed this to 5000, the error message cannot possibly refer the old limit 1000. Does the output log show this set to 1000 or 5000 at startup?
_________________
Glenn |
|
| Back to top |
|
|
| varunraot |
| Posted: Fri Apr 07, 2017 6:25 am Post subject: |
|
|
Acolyte
Joined: 01 Jun 2011
Posts: 50
|
| Output log show this set to 5000 at startup. I verified in the output.log post start up. |
|
| Back to top |
|
|
|
|
