| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message Broker File Extender (File to MQ) |
« View previous topic :: View next topic » |
| Author |
Message
|
| Ching |
 Posted: Fri Sep 30, 2005 1:59 pm Post subject: Message Broker File Extender (File to MQ) |
 |
|
Apprentice
Joined: 08 Nov 2004
Posts: 25
Location: Portland, OR
|
Hello,
I'm getting some interesting error messages for MB file extender in the user.log. This is from a flow that Gets data from a file on AIX, and tries to write to MQ queue. The errors in the user.log are are MBFE_00041 and MBFE_0043.
Do any of know what these errors mean, and what to do about them?
What is the transaction utility they are referring to in the user.log?
Thanks for your help.
Sep 30 14:27:22 wbidev1 MQSIv500[1425600]: (FADWBID1.Ching1)[7198]BIP4361W: Java plug-in node warning: [com.ibm.
mbfe.messages.Messages:MBFE_00041]Session '-1466218124' reached max retry count. Node key is 'FADWBID1.Ching1.mb
fesf2m.FileInputNode'.: . : FADWBID1.64b7081b-0001-0000-0080-e55d770dfbbd: : 0: com.ibm.mbfe.InputNode: run: :
Sep 30 14:27:22 wbidev1 MQSIv500[1425600]: (FADWBID1.Ching1)[7198]BIP4361W: Java plug-in node warning: [com.ibm.
mbfe.messages.Messages:MBFE_00043]Blocking error condition detected on session '-1466218124', the session will b
e frozen. Use transaction utilities to recover data. Node key is 'FADWBID1.Ching1.mbfesf2m.FileInputNode'.: . :
FADWBID1.64b7081b-0001-0000-0080-e55d770dfbbd: : 0: com.ibm.mbfe.InputNode: run: : |
|
| Back to top |
|
 |
| f.demi |
| Posted: Tue Oct 04, 2005 3:04 am Post subject: Message Broker File Extender and poison files |
|
|
Novice
Joined: 17 Sep 2001
Posts: 10
|
Hi Ching,
the error log fragment you provided reports (as a warning) that a poison file has been detected by a FileInput node (i.e. a file for which MBFE has encountered an error that was not recovered within the
maximum number of retries configured).
Unfortunately the problem root cause description is not included in the log fragment you provided: can you have a look at older log entries for clues?
When a poison file i detected MBFE "freezes" the relevant input file and associated session data, in order to "thaw" the frozen poison file you can use the utility command (mentioned in the error message) named mbfesolve.
For more info see also "Handling poison files using mbfesolve tool" section in the product manual.
Cheers,
F. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
