| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Can't map errors in the ExceptionList to the syslog outputs. |
« View previous topic :: View next topic » |
| Author |
Message
|
| JYama |
 Posted: Fri Aug 10, 2007 12:58 am Post subject: Can't map errors in the ExceptionList to the syslog outputs. |
 |
|
Master
Joined: 27 Mar 2002
Posts: 281
|
I'm using WMBv6.0.0.4 on AIX.
One curious thing I'm facing is that I have only one exception in the ExceptionList but there are multiple outputs in the syslog.
I thought that the errors in the ExceptionList and syslog outputs could be equally mapped, but in my case didn't.
Only I can see in the ExceptionList I got in a Trace node is as follows.
${ExceptionList} wrote this.
| Quote: |
ExceptionList received = (
(0x01000000):RecoverableException = (
(0x03000000):File = '/build/S600_P/src/DataFlowEngine/ImbMqInputNode.cpp
'
(0x03000000):Line = 1815
(0x03000000):Function = 'ImbCommonInputNode::eligibleForBackout'
(0x03000000):Type = 'ComIbmMQInputNode'
(0x03000000):Name = 'Flow1#FCMComposite_1_1'
(0x03000000):Label = 'Flow1.SAT_IN'
(0x03000000):Catalog = 'BIPv600'
(0x03000000):Severity = 3
(0x03000000):Number = 2652
(0x03000000):Text = 'Dequeued failed message. Propagating a message to t
he failure terminal'
)
) |
In my syslog, there are multiple error messages and they don't have the error code 2652 mentioned in the ExceptionList.
The syslog outputs are like this;
(This may be printed on your screen badly because it contains DBCS, sorry for your inconvenience)
| Quote: |
Aug 10 18:03:30 gtrs002 user:err|error WebSphere Broker v6004[377048]: (ESB_BK01
.EG_SatWork)[2340]BIP2628E: 入力ノード 'Flow1.SAT_IN' で例外条件が検出されました
。 : ESB_BK01.a5c50e4a-1401-0000-0080-adaf8614a89c: /build/S600_P/src/DataFlowEn
gine/ImbCommonInputNode.cpp: 1106: ImbCommonInputNode::run: ComIbmMQInputNode: F
low1#FCMComposite_1_1
Aug 10 18:03:30 gtrs002 user:err|error WebSphere Broker v6004[377048]: (ESB_BK01
.EG_SatWork)[2340]BIP2230E: ノード 'Flow1.SAT_OUT' でメッセージを処理中にエラー
が検出されました。 : ESB_BK01.a5c50e4a-1401-0000-0080-adaf8614a89c: /build/S600_
P/src/DataFlowEngine/ImbMqOutputNode.cpp: 782: ImbMqOutputNode::evaluate: ComIbm
MQOutputNode: Flow1#FCMComposite_1_2
Aug 10 18:03:30 gtrs002 user:err|error WebSphere Broker v6004[377048]: (ESB_BK01
.EG_SatWork)[2340]BIP2667E: キュー・マネージャー '' でキュー 'SAT_OUT' にメッセ
ージを書き込むときに、ノード 'Flow1.SAT_OUT' でエラーが発生しました。 状態 = '-1
' 'MQW102' '2053' '' : ESB_BK01.a5c50e4a-1401-0000-0080-adaf8614a89c: /build/S60
0_P/src/DataFlowEngine/ImbMqOutputNode.cpp: 2142: ImbMqOutputNode::putMessage: C
omIbmMQOutputNode: Flow1#FCMComposite_1_2
|
How can I map these exceptions between the ExceptionList and syslog?
Does anybody know about this?
Many thanks in advance,
Cheers |
|
| Back to top |
|
 |
| JYama |
| Posted: Fri Aug 10, 2007 2:37 am Post subject: |
|
|
Master
Joined: 27 Mar 2002
Posts: 281
|
I noticed folowing things right now.
1.
My MQInput node, which receives all exceptions rollbacked in the failure terminal, is not propagating whole ExceptionList, only one.
2.
When I 'catch' exceptions in the catch terminal of the MQInput node, there are no syslog outputs. Thus I guess this may require users to develop own error handlers.
But why the MQInput node elimiates error information through the failure terminal?
Additionally, I noticed that eliminated information existed in the syslog.
 |
|
| 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
|
|
|
|
