I've seen this problem as well against the 5.1
product.  I know that there were some changes (fixes)
put in to the 5.2 and 5.3 product to resolve this.
I'd suggest moving forward.

Ron
--- "Voges, P. (Pieter)" <[EMAIL PROTECTED]> wrote:
> Please help, any input will be appreciated.
>
> Strange new problem on unix(AIX) qmgr  connected to
> os390 and NT qmgr's.
> Happened on 30 December and 31 January. Unix ver
> 5.1, mvs and NT ver 5.2
>
> QMGR to QMGR connected through sender and receiver
> channels - disconnect
> interval 0.
>
> The following are noticed between NT and Unix even
> though the channels on
> both sides shows as "running" and messages are not
> received. Soon after
> this, no RUNMQSC commands can be entered on Unix and
> eventually the QMGR
> needs to be bounced. There are no error logs on
> Unix.
>
> What causes a connection on a port to get a
> CLOSE_WAIT status?
>
> What can be done to rectify it. When it hits this
> state soon RUNMQSC does
> not accept any input and shortly thereafter the QMGR
> cannot being brought
> down, not even with the '-i' command. After
> restarting the unix qmgr,
> everything is sorted out.
>
> ----------------------------------------------------
> Command failed: chmod a+rw /dev/null
> chmod: /dev/null: Not owner
> ----------------------------------------------------
> Press return to continue:
> 08:07:00
> all_adm@flash_boot1:/main/nedcor/home/all_adm
> >netstat -a| grep 1414
> tcp4       0      0  swift1.1414
> safeprod.it.nedn.3798
> ESTABLISHED
> tcp4       0      0  swift1.1414
> mvsprod.it.nedne.2573
> ESTABLISHED
> tcp4       0      0  *.1414                 *.*
>               LISTEN
> tcp4       0      0  swift1.32905
> safeprod.it.nedn.1414
> CLOSE_WAIT
>
> Thank you
> Pieter Voges
> MQ Support
> Nedcor Limited
> Tel: (011) 881 4410
> Sel: 083 6455 300
> E-mail: [EMAIL PROTECTED]
>
<http://dotweb.it.nednet.co.za/link.asp?names=Voges,%20Pieter>
> >
>
--------------------------------------------------------------------------
> >
>
--------------------------------------------------------------------------
> >
>
--------------------------------------------------------------------------
> > -------------------------------
> > "The contents of this electronic message and any
> attachments relating to
> > the official business of Nedcor Limited and
> subsidiaries ("Nedcor") are
> > proprietary to Nedcor. They are confidential,
> legally privileged and
> > protected by law. Views and opinions are those of
> the sender and do not
> > represent Nedcor's views and opinions nor
> constitute any commitment by or
> > obligation on Nedcor unless otherwise stated or
> agreed to in writing by
> > Nedcor.
> >
> > The person addressed in this electronic message is
> the sole authorised
> > recipient. If you have received this message in
> error, you are to delete
> > it immediately and notify the sender that it has
> unintentionally reached
> > you. You may not use or disclose the contents of
> this message to any other
> > person.
> >
> > Nedcor cannot assure that the integrity of this
> communication has been
> > maintained, nor that it is free of errors,
> viruses, interception,
> > tampering or interference. Nedcor therefore does
> not accept liability or
> > legal responsibility for the contents of this
> electronic message, its
> > non-delivery or incorrect delivery for whatever
> reason, its effect on
> > electronic devices or its transmission in an
> unencrypted medium."
> >
>
--------------------------------------------------------------------------
> >
>
--------------------------------------------------------------------------
> >
>
--------------------------------------------------------------------------
> > ---------------------------------
> >
> >
>


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

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