Paul... As a followup to an earlier posting, I experienced the same problem
this weekend that Jeff made mention of in the original posting below back in
Mid January.  Also an AIX 4.3.3 but running wmq 5.3 base level code.

The AMQERR01.LOG file had many mq AMQ6209 and AMQ6183 error messages, but as
you stated in your reply,... MQ and the Qmgr in question appeared to be
fine.  Only problem was that clients attempting to connect to the Qmgr over
the weekend were getting 2059's.  The FDC file that was created was huge. 29
meg .  Was filled with references to "xecE_W_UNEXPECTED_ASYNC_SIGNAL". In
looking at the individual entries, all the return values in the FDC dump
state "OK".  Nothing giving me a clue as to what's the issue.  MQ was taken
down for a file system back up, and when restarted... all was fine. Clients
could connect.

I've emailed Jeff, since I knew he had an open PMR at the time.... to see
what the resolution was with MQ support, before I attempt to open my own
call.  Anyone experience similar issues with MQ and AIX 4.3.3 ?

jesse goode jr
valero energy corporation
[EMAIL PROTECTED]

------ snippet from Jeff's original posting -------

What I am finding in the error logs and FDC files are "AMQ6209: An
unexpected asynchronous signal (15) has been received and ignored."
Also receiving "AMQ6183: An internal MQSeries error has occurred."

The FDC file also contained Major Errorcode
"xecE_W_UNEXPECTED_ASYNC_SIGNAL"

--------------------------------


----- Original Message -----
From: "Paul Clarke" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 15, 2003 5:13 AM
Subject: Re: 2195 Error


>Hello Fellow MQer's,

>I have this weird problem with MQ V5.2, AIX  4.3.3. Our AIX Admins
rebooted the machine. After the reboot I  started MQ and the Client Server
and connected through MQ Explorer on  >WIn2K. An application team that
uses this particular server informed me  they have been getting 2195 errors
and an occasional 2059 error. I  verified that they were pointing to the
correct >queue manager and server IP and  I am at loss at what could be
causing this. The application worked fine  prior to this reboot. There
are no error messages in the log.

>Has anybody seen anything like this?

>My thought is MQ is fine. I can do an amqsput  and amqsget on the queue
the application tries to access, I can navigate around  the queue manager
through MQ Explorer and through >telnet. I'm thinking  something wasn't
loaded right in the reboot of the server, but I'm not  sure. Of course
this problem occurred late in the afternoon, so I was not  able to find
out, yet, how >the machine was rebooted.

>Thanks in advance,
>Jeff

Jeff,

If you're getting 2195 errors you should see FDC files written explaining
the problem.

Cheers,
P.

Paul G Clarke
WebSphere MQ Development
IBM Hursley

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive

Reply via email to