| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Missing CRLF in FileInputNode makes system hang |
« View previous topic :: View next topic » |
| Author |
Message
|
| gin123 |
 Posted: Fri Jun 27, 2014 3:40 pm Post subject: Missing CRLF in FileInputNode makes system hang |
 |
|
Newbie
Joined: 16 Apr 2014
Posts: 4
|
I have a FileInputNode that is set with the delimiter as DOS or UNIX Line End. My flow works well in general, but there is a case that can put the system in a bad state, where any further messages (valid or invalid) are sent directly to the mqsibackout folder without getting processed. This state occurs when I send a file through with no final CRLF. The only way to recover from this is to restart MB.
I recognize that this is an invalid file, but I would like the system to handle it more gracefully.
The system logged error message are:
RecoverableException BIP2111E: Message broker internal error: diagnostic information ''Looping on record in file 87c1e7f1-4501-0000-0080-d406f73eb887-1602_sys
WebSphere Broker v7003[10747976]: (ESB_BROKER.case)[4380]BIP3331S: File node 'null' in message flow 'null' cannot contin
ue running. See message '2110' for details of the problem. : ESB_BROKER.87c1e7f1-4501-0000-0080-d406f73eb887: /build/S700_P/src/DataFlowEngine/NativeTrace/Im
bNativeTrace.cpp: 723: com.ibm.broker.seekablestream.MbFileInputStream.read: :
The FileInputNode Failure output node is called just before the system freezes - is it possible to put the system back into a working state here somehow? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Jun 27, 2014 11:15 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Open a PMR with the relevant traces. It seems that the DFDL parser has a few bugs, and you might have run afoul of one. If the APAR already exists you will get it through the PMR. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sat Jun 28, 2014 12:24 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| fjb_saper wrote: |
| Open a PMR with the relevant traces. It seems that the DFDL parser has a few bugs, and you might have run afoul of one. If the APAR already exists you will get it through the PMR. |
The OP is running 7.0.0.3 so DFDL is not really the problem here.
| Code: |
WebSphere Broker v7003[10747976]: (ESB_BROKER.case)
|
Perhaps he might like to run some tests using a later FixPack of V7 to see if the problem is fixed in them. If that is not the case then the next step should be a PMR.
One alternative approach to the flow would be to read the file as a BLOB and parse it outside the FileInput Node.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| Esa |
| Posted: Sat Jun 28, 2014 3:09 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
Have you wire the File Input nodes 'End of data' terminal?
Does it make any difference if yo wire it to a passtrough node, for example? |
|
| 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
|
|
|
|
