| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| How to Ignore the L4 Health Check Data |
« View previous topic :: View next topic » |
| Author |
Message
|
| Cho Chul-hwan |
 Posted: Wed Sep 25, 2013 11:21 pm Post subject: How to Ignore the L4 Health Check Data |
 |
|
Newbie
Joined: 05 May 2013
Posts: 8
|
Hi... I have some problem.
i developed Tcpip Server flow.
TCPIPServerInput --> Compute Node --> TCPIPServerOutput Node
our system configured active-active system so, L4 Switch check the server using send health check message (SLB).
TCPIPServerInput Node made a connection every health check message.
so, the broker occured Exception, 'File table overflow' and the Broker can't make any connections.
i just want to ignore the Health Check Message so, i did wired compute node and evaluate the message in the InputRoot but there is no BLOB message the other message. just Properties in the InputRoot. so, i thought wired TCPIPOutputNode's close terminal. but exception occured again.
please help me, i already read the infocenter. it wasn't help for me.
i just wnat to ignore the health check message.
Broker version : 7.0.0.5 |
|
| Back to top |
|
 |
| McueMart |
| Posted: Thu Sep 26, 2013 2:54 am Post subject: |
|
|
Chevalier
Joined: 29 Nov 2011
Posts: 490
Location: UK...somewhere
|
| Share with us more details on the exception you are getting. It sounds like you need to write some more code in your Compute node to ignore these empty 'health check' messages. |
|
| Back to top |
|
|
| Cho Chul-hwan |
| Posted: Thu Sep 26, 2013 4:32 am Post subject: here is code and exceptions |
|
|
Newbie
Joined: 05 May 2013
Posts: 8
|
The Compute Node Code is :
IF InputRoot.BLOB.BLOB IS NULL THEN
CALL Test_Log(refEnv, 'Health Message : ');
PROPAGATE to TERMINAL 'out1';
ELSE
CALL Test_Log(refEnv, 'Real Message : ');
PROPAGATE to TERMINAL 'out2';
END IF;
That is the evaluate the Health check message
terminal 'out1' is wired TCPIPServerOutput (in)close terminal.
terminal 'out2' is wired next compute node to process the message.
sometime occurred exception and can't make the connection with the real message.
The Exception log-----------------------------
Sep 26 21:19:47 dfseais2 WebSphere Broker v7005[4723]: (BK04.SMART_EXT04)[24]BIP2628E: Exception condition detected on input nod e 'SMART_MAIN.ETCODB_NSS0001Main.TCPIP Server Input'. : BK04.985fa52d-4001-0000-0080-cae8126696b0: /build/S700_P/src/DataFlowEng ine/TemplateNodes/ImbInputTemplateNode.cpp: 555: ImbInputTemplateNode::run: ComIbmTCPIPServerInputNode: SMART_MAIN/ETCODB_NSS000 1Main#FCMComposite_1_1
Sep 26 21:19:47 dfseais2 WebSphere Broker v7005[4723]: (BK04.SMART_EXT04)[24]BIP2111E: Message broker internal error: diagnostic information 'tried to process a closed read connection but it is in use'. : BK04.985fa52d-4001-0000-0080-cae8126696b0: MbErrorH andler.java: 104: setReadInUse: :
Sep 26 21:19:24 dfseais2 WebSphere Broker v7005[3872]: (BK04.SMART_EXT04)[24]BIP3587E: No connections are available on Hostname 'localhost', Port '14001'. : BK04.985fa52d-4001-0000-0080-cae8126696b0: MbErrorHandler.java: 104: calculateDynamicProperties: :
Sep 26 21:19:24 dfseais2 WebSphere Broker v7005[3872]: (BK04.SMART_EXT04)[24]BIP2628E: Exception condition detected on input nod e 'SMART_MAIN.ETCODB_NSS0001Main.TCPIP Server Input'. : BK04.985fa52d-4001-0000-0080-cae8126696b0: /build/S700_P/src/DataFlowEng ine/TemplateNodes/ImbInputTemplateNode.cpp: 555: ImbInputTemplateNode::run: ComIbmTCPIPServerInputNode: SMART_MAIN/ETCODB_NSS000 1Main#FCMComposite_1_1
Sep 26 21:19:24 dfseais2 WebSphere Broker v7005[3872]: (BK04.SMART_EXT04)[24]BIP2111E: Message broker internal error: diagnostic information 'tried to process a closed read connection but it is in use'. : BK04.985fa52d-4001-0000-0080-cae8126696b0: MbErrorH andler.java: 104: setReadInUse: : |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Sep 26, 2013 5:22 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Change the flow to email all exceptions to the maintainers of the l4 healthcheck system.
That will cause them to rapidly decide they need to disable it for this specific port.
Then you can ignore the messages, because they won't come any more. |
|
| 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
|
|
|
|
