Script:
Owner:
Subdir: middlewarenews
Blog ID: 93013848
Group ID: User ID: 92249378

    AMQ9213 2009 MQRC_CONNECTION_BROKEN on IBM MQ clients - Middleware News

    Thursday, August 2, 2012, 8:31 AM
    Categories: WebSphere MQ
    Posted By: Karthick

    You have WebSphere MQ clients which connect to several different MQ servers. The MQ clients are quite frequently disconnected with rc=2009, MQRC_CONNECTION_BROKEN. The clients are able to reconnect immediately. The queue managers are running well. You see no problems when issuing 'runmqsc' commands on the server.

    Symptom

    On the MQ server side you see the following message in the queue manager's error log, AMQERR01.LOG:

    AMQ9213: A communications error for TCP/IP occurred.
    EXPLANATION: An unexpected error occurred in communications.
    ACTION: The return code from the TCP/IP(select) [TIMEOUT] 660 seconds call was 11 (X'B'). Record these values and tell the systems administrator.

    Cause

    There was a parameter recently added in your qm.ini file called ClientIdle that was set to 600 secs. This caused the client connections to end after they were idle for the specified period of time + 60 seconds. After the connection is terminated at the server, the next attempt to send a request from the client side results in rc=2009.

    Resolving the problem

    You can either remove the ClientIdle parameter from the Channels stanza of your qm.ini files or you can set it to a value, which is higher than you expect your clients will be idle between calls. 
    The default path for the qm.ini file is /var/mqm/QMGRs//
    3.7 (1 Ratings)

    IBM Leap Second may cause Linux to freeze

    Tuesday, July 24, 2012, 12:01 AM
    Categories: WebSphere MQ
    Posted By: Karthick

    After adding the leap second in Linux on 30 June, 2012, your WebSphere MQ queue manager has many FDC files related to resource issues or constraints and they will commonly report rc=xecP_E_NO_RESOURCE. You may also see your queue manager hang or freeze or there may be high cpu. The FDC's are being generated on a daily basis and may have probes of XY348010 or XC272003 from xcsCreateThread but there could be other FDC's with different probes also.

    Content

    On 30 June, the Network Time Protocol (NTP) daemon scheduled a leap second to occur at midnight, meaning that the final minute of the day was 61 seconds long. We have seen several problems with otherwise unexplainable high CPU usage on Linux systems caused by the leap second at the end of June.

    WebSphere MQ does not directly make calls which experience the problem, but we do use the pthreads library (NPTL), which in turn uses futexes ("fast userspace mutexes"), which can hit this problem. Busy systems running WebSphere MQ and other products are susceptible to this problem. You can read more about the problem at these links:

    Anyone else experiencing high rates of Linux server crashes during a leap second day?

    Leap Seconds in Red Hat Enterprise Linux

    Leap second: Linux can freeze

    This problem is solved by either applying Operating System (Linux) patches, resetting the date or rebooting the system. The resolution is dependent on your level of Linux and your environment. Please consult your Linux provider for details of the solution appropriate for your system.

    As a workaround you can follow these steps

    1. Check the Linux kernel version. In theory only 2.6.22 and newer levels should be affected:
      All: uname -r
    2. Switch to root or log in as root at the console
    3. Check to see if NTP is running:
      RHEL: service ntpd status
      SLES: /etc/init.d/ntp status
    4. If NTP is running, disable it:
      RHEL: service ntpd stop
      SLES: /etc/init.d/ntp stop
    5. Set the system clock to the current time:
      All sntp -P no -r pool.ntp.org
      Or: ntpdate 0.us.pool.ntp.org
    6. If NTP was running, reenable it:
      RHEL: service ntpd start
      SLES: /etc/init.d/ntp start
    0 (0 Ratings)

    Migrating to IBM WebSphere MQ for AIX Version 7.0 - Middleware News

    Tuesday, July 10, 2012, 9:58 AM
    Categories: WebSphere MQ
    Posted By: Karthick

    If you want to migrate to WebSphere MQ Version 7.0, complete this task.

    If you migrate from a previous level of this product without first backing up your system, you cannotrevert to your previous level, so back up your system before you install WebSphere MQ Version 7.0. You can then back out the upgrade if necessary. If you back out the upgrade, however, you cannot recover any work, such as changes to messages and objects, performed by WebSphere MQ Version 7.0.

    Procedure

    1. Stop all MQ applications on the machine and the applications accessing remote machines.
    2. End all WebSphere MQ activity.
      1. Log in as a user in group mqm.
      2. Start of changeUse the dspmq command to display the state of all the queue managers on the system.End of change
      3. Use the endmqm command to stop all running queue managers.
      4. Stop any listeners associated with the queue managers, using the command:
        endmqlsr -m QMgrName
      5. To check that you have stopped all of them, enter the following:
        ps -ef | grep mq
        Check that there are no processes listed that are running command lines beginning amq orrunmq. Ignore any that start with amqi.
    3. Log in as root.
    4. Function supplied by the SupportPacs in Table 1 has been superseded by function in WebSphere MQ Version 7.0. Remove these SupportPacs before installing WebSphere MQ Version 7.0.
      Table 1. SupportPacs superseded by WebSphere MQ Version 7.0
      SupportPac NumberDescription
      MA0Y WebSphere MQ Bridge for HTTP
      Note: If you installed SupportPac MACS, remove the directory /usr/mqm/inc64 and its contents.
      Review any other installed SupportPacs for their applicability to WebSphere MQ Version 7.0.
    5. Start of change If you are migrating from WebSphere MQ Version 5.3 to WebSphere MQ Version 7.0, you must uninstall WebSphere MQ Version 5.3. If you are migrating from WebSphere MQ Version 6.0 to WebSphere MQ Version 7.0, you do not have to uninstall WebSphere MQ because the installation process does it for you. However, when migrating from WebSphere MQ Version 6.0 to WebSphere MQ Version 7.0, before installing you must ensure that you manually remove the file sets which have been retired from WebSphere MQ Version 7.0.
      • Remove the following file sets before migrating from WebSphere MQ Version 6.0 to WebSphere MQ Version 7.0:
        • mqm.msg.De_DE
        • mqm.msg.Es_ES
        • mqm.msg.Fr_FR
        • mqm.msg.It_IT
      End of change
    6. Install WebSphere MQ Version 7.0 by following the tasks set out in Start of changeInstalling a WebSphere MQ serverEnd of change.
    7. Restart WebSphere MQ.
    0 (0 Ratings)

    WebSphere MQ 7.1: How to remove a channel authentication record (CHLAUTH) - Middleware News

    Tuesday, July 10, 2012, 9:54 AM
    Categories: WebSphere MQ
    Posted By: Karthick

    You have added a channel authentication record into a WebSphere MQ 7.1 queue manager:

    DISPLAY CHLAUTH(*) TYPE(USERMAP)
    1 : DISPLAY CHLAUTH(*) TYPE(USERMAP)
    AMQ8878: Display channel authentication record details.
    CHLAUTH(*) TYPE(USERMAP)
    CLNTUSER(rivera) USERSRC(CHANNEL)

    Now you want to remove it and you try executing the following runmqsc command which you constructed using copy and paste from the above output:

    DELETE CHLAUTH(*) TYPE(USERMAP) CLNTUSER(rivera) USERSRC(CHANNEL)
    3 : DELETE CHLAUTH(*) TYPE(USERMAP) CLNTUSER(rivera) USERSRC(CHANNEL)

    You get the following error:

    AMQ8405: Syntax error detected at or near end of command segment below:-
    DELETE CHLAUTH

    The DELETE CHLAUTH does not exist and after consulting the MQ 7.1 Information Center you read that you have to use the SET CHLAUTH command with the argument ACTION(REMOVE). You try now:

    SET CHLAUTH(*) TYPE(USERMAP) CLNTUSER(rivera) ACTION(REMOVE)
    19 : SET CHLAUTH(*) TYPE(USERMAP) CLNTUSER(rivera) ACTION(REMOVE)

    But you get the following error:

    AMQ8884: Channel authentication record not found.

    You specified the attribute CLNTUSER(rivera) as it was shown in the output of the DISPLAY CHLAUTH(*), thus, you think the record should be found. You want to know what is the problem?

    Cause

    See the following section of the MQ 7.1 Information Center:

    publib.boulder.ibm.com/infocenter/wmqv7/...
    WebSphere MQ > Administering > Administering local WebSphere MQ objects > Performing local administration tasks using MQSC commands
    WebSphere MQ object names
    + Case-sensitivity in MQSC commands
    MQSC commands, including their attributes, can be written in upper-case or lower-case. Object names in MQSC commands are folded to upper-case (that is, QUEUE and queue are not differentiated), unless the names are enclosed within single quotation marks. If quotation marks are not used, the object is processed with a name in upper-case. 

    When specifying the SET command with the following value CLNTUSER(rivera) the string 'rivera' will be folded to upper-case resulting in the following value being actually used by runmqsc:
    CLNTUSER(RIVERA)
    And in this case, there is no record for the user RIVERA (the record is for 'rivera').


    Answer

    NOTICE that the userid mentioned in the CLNTUSER field of the output of the DISPLAY CHLAUTH command is NOT surrounded by single quotes.
    However, you MUST include the single quotes when specifying the value during an ACTION(REMOVE):

    SET CHLAUTH(*) TYPE(USERMAP) CLNTUSER('rivera') ACTION(REMOVE)
    1 : set CHLAUTH(*) TYPE(USERMAP) CLNTUSER('rivera') ACTION(REMOVE)
    AMQ8877: WebSphere MQ channel authentication record set.

    Additional Search Words: uppercase lowercase upper lower case

    0 (0 Ratings)

    Uninstalling WebSphere MQ on Linux - Middleware News

    Tuesday, July 10, 2012, 9:51 AM
    Categories: WebSphere MQ
    Posted By: Karthick

    Procedure

    1. Before starting to uninstall, end all WebSphere MQ activity.
      1. Start of changeLog in as a user in group mqm.End of change
      2. Use the dspmq command to display the state of all the queue managers on the system.
      3. Use the endmqm command to stop all running queue managers.
      4. Stop any listeners associated with the queue managers, using the command:
         endmqlsr -m QMgrName
      5. To check that you have stopped all of the necessary WebSphere MQ processes, type:
        ps -ef | grep mq
      6. Check that there are no processes listed that are running command lines beginning amq orrunmq. Ignore any that start with amqi.
    2. Before you uninstall WebSphere MQ for Linux you must find out the names of the packages (components) currently installed on your system. To list all the packages with their version information, enter the following:
      rpm -q -a | grep MQSeries
      rpm -q -a | grep gsk
      Note: If you have applied maintenance to the install, remove these maintenance packages before removing the base install.
    3. Some of the installed packages are dependent on others. The rpm command will not remove a package if others are dependent on it. For this reason you must uninstall the packages in such an order that each one you uninstall has no dependencies from other packages. To list all of the packages on which a named package (for example MQSeriesServer) depends, enter the following:
      rpm -q --requires MQSeriesServer
      Alternatively, remove all the components at the same time by appending all the package names to the rpm command arguments. For example, to remove the runtime, Server and SDK components, enter the following:
      rpm -ev MQSeriesRuntime MQSeriesServer MQSeriesSDK
    4. After uninstalling , you might want to delete the contents of /var/mqm, which is not removed by the uninstallation. Only do this if you do not need your queue manager data. For example, do not delete the content if you plan to migrate to a later version of WebSphere MQ.
    0 (0 Ratings)

    Page 10 of 20  •  Prev 1 ... 8 9 10 11 12 ... 20 Next

Tag Cloud

Connect w/ Others

    No blog posts have been added.