ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Any way to stop/reduce number of MQSI data in syslog

Post new topic  Reply to topic
 Any way to stop/reduce number of MQSI data in syslog « View previous topic :: View next topic » 
Author Message
Mateo
PostPosted: Tue Sep 09, 2003 1:42 am    Post subject: Any way to stop/reduce number of MQSI data in syslog Reply with quote

Novice

Joined: 21 Aug 2002
Posts: 24
Hi all,
We use Oracle (8i) as external database. It happend that database went down becouse of some reason and MQSI (2.1 & CSD05) started writing lots of messages (3 per 1 sec.) to syslog.log (on HP-UX). Syslog started to become very huge.
When we simulated similar problem on our development machine (we stopped Oracle instance from sqlplus) there are only few entries in syslog regarding broken connection to a database.

Is there any way to stop or reduce number of data in syslog ?
What can be couse of gettnig hundreds of entries in syslog ?

Our flow looks like this

EAI.TX.FOOTPRINT.LOG (InputNode) -> JavaPluginNode1->ComputeNode1
EAI.ENQ.FOOTPRINT.LOG(InputNode) ->JavaPluginNode1

JavaPluginNode1(failure) -> TraceNode1
ComputeNode1(failure) -> TraceNode1

JavaPluginNode1 "gathers" incomming messages and propagates 1 message per hour with statistical data. Than ComputeNode1 does instert to a database.
TraceNode1 handles errors: writes message and exception list to a file on local disk.

Mateo

sample from syslog.log:
Code:
Sep  6 23:59:55 ldce020 WMQIv210[12774]: (EAI.BROKER.default)[18]BIP2628E:Exception condition detected on input node'MESSAGE_COUNTER_30.EAI.TX.FOOTPRINT.LOG'. :EAI.BROKER.9cea8772-f700-0000-0080-8ba7cce67fee:/build/S210_P/src/DataFlowEngine/ImbMqInputNode.cpp: 1537:ImbMqInputNode::readQueue: ComIbmMQInputNode:2beddfac-ee00-0000-0080-f32528ac86cd
Sep  6 23:59:55 ldce020 WMQIv210[12774]: (EAI.BROKER.default)[18]BIP2321E:Database error: ODBC return code '-1'. :EAI.BROKER.9cea8772-f700-0000-0080-8ba7cce67fee:/build/S210_P/src/DataFlowEngine/ImbOdbc.cpp: 154:ImbOdbcHandle::checkRcInner: :
Sep  6 23:59:55 ldce020 WMQIv210[12774]: (EAI.BROKER.default)[18]BIP2322E:Database error: SQL State '27O^Z'; Native Error Code '3114'; Error Text'[DataDirect][ODBC 20101 driver][20101]ORA-03114: not connected to ORACLE:EAI.BROKER.9cea8772-f700-0000-0080-8ba7cce67fee:/build/S210_P/src/DataFlowEngine/ImbOdbc.cpp: 255:ImbOdbcHandle::checkRcInner: :
Back to top
View user's profile Send private message Visit poster's website
EddieA
PostPosted: Tue Sep 09, 2003 6:31 am    Post subject: Reply with quote

Jedi

Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
If there were differences in what was written to the logs between the 2 systems, then take a look at /etc/syslog.conf to see how the various message types, especially user.debug, messages are handled.

Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0
Back to top
View user's profile Send private message
Mateo
PostPosted: Tue Sep 09, 2003 10:09 pm    Post subject: Reply with quote

Novice

Joined: 21 Aug 2002
Posts: 24
Thanks for Your response EddieA
I had already looked and there were no differences in /etc/syslog.conf.
I have there
Code:

mail.debug              /var/adm/syslog/mail.log
*.info;mail.none        /var/adm/syslog/syslog.log
*.alert                 /dev/console
*.alert                 root
*.emerg                 *

I compared also versions of ODBC driver library but they are the same.

Mateo
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Any way to stop/reduce number of MQSI data in syslog
Jump to:  



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
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.