| Author |
Message
|
| psn |
 Posted: Thu Feb 17, 2005 3:05 am Post subject: MQ Series Solaris AMQERR01.LOG File size |
 |
|
Disciple
Joined: 30 Oct 2002
Posts: 193
Location: France
|
Hi,
how it is possible to enlarge the AMQERR0X.LOG File size in the /var/mqm/qmgrs/QMANAGER/errors/AMQERR0X.LOG
thanks for your help
PSN |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Thu Feb 17, 2005 4:05 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
|
| Back to top |
|
|
| psn |
| Posted: Thu Feb 17, 2005 5:44 am Post subject: |
|
|
Disciple
Joined: 30 Oct 2002
Posts: 193
Location: France
|
last night had an MQClient Application more times 2059 MQ error but as I wanted to look what was wrong in the AMQERR01 , or AMQERR02 , or AMQERR03 files all three files were to recent . For this reason I look for a solution the files bigger to defined or defined more then 3 Files .
PSN |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Feb 17, 2005 5:57 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
2059s are usually the result of bad parameters being used by the client application.
Sometimes they are a result of too many channels being opened - for instance if the client application opened a new connection each of those 250 times and didn't disconnect any of them. Then you might run out of available client channels, depending on your queue manager setup, and the client app could get 2059s or 2009s or 2025s or etc.
| Code: |
| dis chstatus(<client channel name) saved |
might show you the channel history enough.
The error logs in the client's error directory might also have information that got moved out of the server error logs.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Thu Feb 17, 2005 5:58 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
Given that 2059's don't get logged into AMQERRxx logs I would suggest that the most recent messages in the AMQERR log would give you a pointer to the underlying problem. You mention that all three logs have a recent date on them but they should still be in time order. Start with the most recent and work backwards fixing any errors as you go. It would seem to me that the problem must be significant if it fills up all three logs that quickly.
What do the error messages that are filling the amqerr logs point to? |
|
| Back to top |
|
|
| psn |
| Posted: Thu Feb 17, 2005 6:52 am Post subject: |
|
|
Disciple
Joined: 30 Oct 2002
Posts: 193
Location: France
|
| the problem is that all 3 file are more recent as the connection error !!! for this reason I wanted to make the files bigger. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Feb 17, 2005 7:50 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| Code: |
MQMAXERRORLOGSIZE=1000000
|
On Unix, the max is 1000000, and will let the error logs grow to about 1 Meg each.
On Windows, I have set it as high as 5000000, and it works. 5 Meg Error logs.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Nigelg |
| Posted: Fri Feb 18, 2005 1:18 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
I was not going to mention this, but since Peter has let the cat out of the bag...
You MUST make sure that the env var is set in the shell of EVERY process that may write to the error logs, otherwise the log will be truncated back to 256K. Common places where the env var is not set is where the UNIX listener inetd is in use. This has to be stopped and restarted with the env var set, so that the responder processes (amqcrsta) inherit the env var setting. Also, runmqlsr, runmqsc, runmqchl, rcdmqimg and so on.
Anyway, back to the original problem...
Usual client checks...
Does amqsputc work?
Check network connectivity!
Check MQSERVER has the right channel name, host and port
If client channel table, check the qmgr name in the app matches the qmgr name and conname (host and port) in the CLNTCONN channel.
If MQCONNX, check the qmgr name, and the channel name and conname (host and port) in the MQCNO.
Check there is a listener running at the server, on the right port. |
|
| Back to top |
|
|
| psn |
| Posted: Mon Feb 21, 2005 2:05 am Post subject: |
|
|
Disciple
Joined: 30 Oct 2002
Posts: 193
Location: France
|
I think it was a network problem because it was not a 2059 but a 2009 !
Thanks
PSN |
|
| Back to top |
|
|
|
|
