IBM Support

IV27873: WMQ JMS EXCEPTION "JMSCC0046: IT IS NOT PERMITTED TO CALL METHOD'GETBODYLENGTH'" RECEIVED, EVEN AFTER APPLYING APAR IV09196

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After installing the WebSphere MQ fix for APAR IV09196 on the
    WebSphere Application Server v7 and setting the Java system
    property to the name and value:
    
    -Dcom.ibm.jms.forceDeserializedJMSBytesMessagesToReadOnlyMode=
    true
    
    as per the IV09196 APAR instructions, the application continues
    receives the exception:
    
    JMSCC0046: It is not permitted to call method 'getBodyLength'
    on the message because the message body is write-only. A user
    application has attempted to read a write-only message body.
    Change the application program to remove this behavior, or call
    the reset() method first.
    

Local fix

  • change the property spelling to:
    com.ibm.jms.forceDeseralizedJMSBytesMessagesToReadOnlyMode=true
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of:
    
    - The WebSphere MQ V7.0 classes for JMS.
    - The WebSphere MQ V7.0 Resource Adapter.
    - The WebSphere Application Server V7 WebSphere MQ messaging
    provider.
    - The WebSphere Application Server V8 WebSphere MQ messaging
    provider.
    - The WebSphere Application Server V6.1 WebSphere MQ messaging
    provider who have configured the WebSphere variable
    MQ_INSTALL_ROOT to point to a WebSphere MQ V7.0 installation.
    
    who are attempting to use the JVM system property:
    
    com.ibm.jms.forceDeserializedJMSBytesMessagesToReadOnlyMode
    
    introduced in APAR IV09196.
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows) +Java +Java zOS
    ****************************************************************
    PROBLEM SUMMARY:
    APAR IV09196 introduced a JVM system property to change the
    default behaviour of a deserialized JMSBytesMessage message to
    be in read-only as opposed to the v7 default of write-only.
    This system property is called:
    
    com.ibm.jms.forceDeserializedJMSBytesMessagesToReadOnlyMode
    
    However, setting this property did not result in the
    JMSBytesMessage being put into the read-only mode, due to a
    defect in the internal mechanism used to look up the property.
    

Problem conclusion

  • This APAR solves this issue by changing the code mechanism used
    to look up the system property:
    
    com.ibm.jms.forceDeserializedJMSBytesMessagesToReadOnlyMode
    
    to ensure that the behaviour as defined in APAR IV09196 is
    adhered to.
    
    
    | MDVPARTL 7.0.1-WS-MQ-AixPPC64-FP0008       |
    | MDVPARTL 7.0.1-WS-MQ-HpuxIA64-FP0008       |
    | MDVPARTL 7.0.1-WS-MQ-HpuxPaRISC64-FP0008   |
    | MDVPARTL 7.0.1-WS-MQ-LinuxIA32-FP0008      |
    | MDVPARTL 7.0.1-WS-MQ-LinuxPPC64-FP0008     |
    | MDVPARTL 7.0.1-WS-MQ-LinuxS390X-FP0008     |
    | MDVPARTL 7.0.1-WS-MQ-LinuxX64-FP0008       |
    | MDVPARTL 7.0.1-WS-MQ-SolarisSparc64-FP0008 |
    | MDVPARTL 7.0.1-WS-MQ-SolarisX64-FP0008     |
    | MDVPARTL 7.0.1-WS-MQ-Windows-FP0008        |
    | MDVPARTL 7.0.1-WS-MQ-AixPPC64-FP0009       |
    | MDVPARTL 7.0.1-WS-MQ-HpuxIA64-FP0009       |
    | MDVPARTL 7.0.1-WS-MQ-HpuxPaRISC64-FP0009   |
    | MDVPARTL 7.0.1-WS-MQ-LinuxIA32-FP0009      |
    | MDVPARTL 7.0.1-WS-MQ-LinuxPPC64-FP0009     |
    | MDVPARTL 7.0.1-WS-MQ-LinuxS390X-FP0009     |
    | MDVPARTL 7.0.1-WS-MQ-LinuxX64-FP0009       |
    | MDVPARTL 7.0.1-WS-MQ-SolarisSparc64-FP0009 |
    | MDVPARTL 7.0.1-WS-MQ-SolarisX64-FP0009     |
    | MDVPARTL 7.0.1-WS-MQ-Windows-FP0009        |
    
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.1.10
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV27873

  • Reported component name

    WMQ AIX V7

  • Reported component ID

    5724H7221

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-09-11

  • Closed date

    2012-09-25

  • Last modified date

    2013-11-20

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WMQ AIX V7

  • Fixed component ID

    5724H7221

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDEZSF","label":"IBM WebSphere MQ Managed File Transfer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
31 March 2023