IBM Support

PM61145: INVALIDDESTINATIONEXCEPTION WHEN A JMS APPLICATION ATTEMPTS TO CONNECT TO SERVICE INTEGRATION BUS USING SPRING.

Fixes are available

8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When a Java Message Service (JMS) application attempts to send
    or receive messages to or from Websphere Application Server
    v7.0.x Service Integration Bus destination, the following errors
    are logged in the SystemOut.log:
    
    [3/13/12 11:20:53:933 EDT] 0000002d CVMessageServ E
    com.aaaa.bbbbb.services.CVMessageServiceImpl
    dispatchMessageToMQ Exception caught
    
    javax.jms.InvalidDestinationException: CWSIA0116E: The
    specified value class $Proxy30 is not allowed for
    JMSReplyTo.
    
    at
    com.ibm.ws.sib.api.jms.impl.JmsMessageImpl.setJMSReplyTo(JmsMe
    ssageImpl.java:758)
    ..
    ..
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider     *
    *                  for IBM WebSphere Application Server        *
    *                  Version 7.0 and Version 8.0.                *
    ****************************************************************
    * PROBLEM DESCRIPTION: When using Spring to access a           *
    *                      destination (queue or topic) through    *
    *                      the externally available interfaces,    *
    *                      there is InvalidDestinationException.   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The Spring framework passes in dynamic proxy objects that wrap
    a real JmsDestinationImpl or any implemented object.
    This is because Spring encapsulates the Service Integration
    Bus's (SIBUS) JmsDestinationImpl in an anonymous proxy class.
    So the JmsMessageImpl.setJMSReplyTo()method throws
    InvalidDestinationException as the provided class is not an
    instance of JmsDestinationImpl.
    The fix for this issue is for SIBUS to create new queue or
    topic object based on the queue or topic name passed along
    with the proxy object.
    

Problem conclusion

  • Source code has been modified to accept a Spring proxy object
    in the JmsMessageImpl.setJMSReplyTo() method.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.25 and 8.0.0.5.  Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM61145

  • Reported component name

    WAS SIB & SIBWS

  • Reported component ID

    620800101

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-03-26

  • Closed date

    2012-04-30

  • Last modified date

    2012-08-13

  • 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

    WAS SIB & SIBWS

  • Fixed component ID

    620800101

Applicable component levels

  • R800 PSY

       UP



Document information

More support for: WebSphere Application Server
Service Integration Technology

Software version: 7.0

Reference #: PM61145

Modified date: 13 August 2012