| Author |
Message
|
| sijian |
 Posted: Fri Jul 29, 2005 12:54 pm Post subject: AMQ7467, AMQ7468 problem |
 |
|
Newbie
Joined: 29 Jul 2005
Posts: 3
|
Environment: AIX 5.1.0.0. MQ 5.3 CSD7.
On our testing and production environment we use circular log and linear log respectively. I deleted all messages on user queues. There are very low to no user activity in my testing period. AMQ 7467,AMQ7468 is created every seconds!
We also have WBIA(CrossWorlds) adapter running (MQ to/from SAP) and WMQI running. WBIA polling frequency set to 10000. if I stop WBIA process. the AMQ 7467 and AMQ 7468 log stops. If WBIA process running, I don't see any new messages in queues. What is my problem? |
|
| Back to top |
|
 |
| csmith28 |
| Posted: Fri Jul 29, 2005 1:07 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Are any .FDC files being created in /var/mqm/errors
If so have you tried searching here and on the IBM Support Search site using the Probe ID's from those files?
Here is what the WMQ Messages Guide has to say about the AMQ errors you have reported:
| Quote: |
AMQ7468 The oldest log file required to perform media recovery of queue manager &3 is&4.
Explanation: The log file &4 contains the oldest log record required to recreate any of the objects from their media images. Any log files prior to this will not be accessed by media recovery operations.
User Response: You can move log files older than &4 |
and
| Quote: |
AMQ7467 The oldest log file required to start queue manager &3 is &4.
Explanation: The log file &4 contains the oldest log record required to restart the queue manager. Log records older than this may be required for media recovery.
User Response: You can move log files older than &4 to an archive medium to release space in the log directory. If you move any of the log files required to recreate objects from their media images, you will have
to restore them to recreate the objects. |
I hope you didn't delete any of the of your circular logs in Dev.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| sijian |
| Posted: Fri Jul 29, 2005 1:29 pm Post subject: |
|
|
Newbie
Joined: 29 Jul 2005
Posts: 3
|
| No FDC file was created for this problem. We did not delete circular log. Linear log just normal back up. Looks like problem was related to WBIA (WebSphere Business Integrate Adapter). We are using version 5.6 for mySAP. |
|
| Back to top |
|
|
| csmith28 |
| Posted: Fri Jul 29, 2005 1:37 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Sorry, I have no experience with WBIA.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| Srinivasan |
| Posted: Mon Aug 08, 2005 11:47 pm Post subject: |
|
|
Apprentice
Joined: 12 Jul 2005
Posts: 41
Location: Chennai
|
Hi,
I had the same problem with MQ in AS/400
and this looks siilar ... did u end MQ Queue manager abnormally???
and also I think QMQMCHKPT in the QIBM folder has media information which is not available now for u..
in this situation i think u have to do a cold restart of Queue manager.. in this case contact IBM for this
_________________
Srinivasan for MQ discussion |
|
| Back to top |
|
|
| dgolding |
| Posted: Tue Aug 09, 2005 12:08 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
If you're getting 7467 and 7468 entries in your AMQERR01.LOG then SOMETHING (sounds like WBIA) is generating enough loggable activity (MQGETs and MQPUTs basically) to cause this.
From memory it's normally it's every 1000 or so transactions, I think. So SOMETHING is doing a 1000 puts/gets every second or so.
What does the "10000" polling frequency mean? Milliseconds? Seconds? You could try and dump the log and see who's doing it, but it's a hellishly awkward procedure. |
|
| Back to top |
|
|
| sijian |
| Posted: Tue Aug 09, 2005 6:39 am Post subject: |
|
|
Newbie
Joined: 29 Jul 2005
Posts: 3
|
| IBM support has directed us to send log to them (MQ PMR 76459,487 000 and WBIA PMR 76883,487). After analysis by lead specialist there shows that WBIA was driving 100 times of normal API calls. Most of the API calls were "waste". The WBIA PMR was submitted for IBM to fix the problem. We have not got WBIA people back to us yet. |
|
| Back to top |
|
|
|
|
